- 29 May 2011
- 1,747
- 297
On the AOSP rom I've posted or on cm-10.2?
if so on both rom's the same result?
[ROM][JB][4.3][2013-12-29] CyanogenMod 10.2
- Thread starter M1cha
- Start date
if so on both rom's the same result?
I started to use this rom for testing, I hope it can stay for a daily rom 
First, both the front and back camera works well for me apparently.
Wifi seems OK with the fix (didn't try the previous one)
Bugs I found so far:
-if you switch torch on/off rapidly the app will FC and the Led can't be switched off. With slow switching it seems to be working OK.
-Settings app FCs if I tap on Bluetooth menu without having BT on.
M1cha, let me know if these are bugs that you can't reproduce so I can make a logcat for you, otherwise it's pointless
Update: not sure if it's related, but I'm having issues restoring some apps with Helium backup (SwiftKey, Temple Run2, 9gag...) haven't experienced this issue with any other ROMs..
First, both the front and back camera works well for me apparently.
Wifi seems OK with the fix (didn't try the previous one)
Bugs I found so far:
-if you switch torch on/off rapidly the app will FC and the Led can't be switched off. With slow switching it seems to be working OK.
-Settings app FCs if I tap on Bluetooth menu without having BT on.
M1cha, let me know if these are bugs that you can't reproduce so I can make a logcat for you, otherwise it's pointless
Update: not sure if it's related, but I'm having issues restoring some apps with Helium backup (SwiftKey, Temple Run2, 9gag...) haven't experienced this issue with any other ROMs..
Last edited:
Pauldgroot
Members
- 11 Mar 2013
- 28
- 15
Restoring apps did work fine with Titanium Backup. So it might be a helium problem.
Sent from my MI 2 using Tapatalk
Sent from my MI 2 using Tapatalk
Another annoying bug: RILJ wake lock (Phone.apk) prevents phone from deep sleep. Don't know what's the root cause..
Is there a way to debug this? Or anybody else facing this issue?
Is there a way to debug this? Or anybody else facing this issue?
- 29 May 2011
- 1,747
- 297
I saw framerate configs in both camera drivers and xml-files.
But at this stage with many cams not working and random crashes I don't wnat to thing about this
Thanks for the Wifi fix, updating as we speak. Still have some weird battery percentage drops. Wipe battery stats doesn't show up under advanced either.
The framerate is still 22.75, hopping that when all the camera bugs are fixed M1cha can find a way to correct the issue.
Medina
Members
- 27 Dec 2011
- 245
- 65
Hats off my friend!
You have done the impossible.
I'm running the last build for the last few days and I have to say: you are a very skilled developer
This is high level class of development!!
And I'm happy that I could afford donating you, because you deserve it.
Now to my feedback MI2 32g model:
1.Fast fast fast!! Finally we can see our device's full potential.
2. Battery usage, same as we have with MIUI ROMS, way better then all others non-MIUI ROMS
3. Audio (volume \ quality) same as stock ROM could be better and louder with a bit tunin. What do you think?
3.5. Vibration - the same as all others
4. Camera, works gr8! Didn't have any problems what so ever. Hopefully you will find some hack to help the others and to improve the frame rate.
6. WiFi and 3g signals, I did not had problems like others, I'm very satisfied!
7. Overall look, feeling and every day use - with Xposed on board there is nothing you can't do. It looks beautiful it is very friendly and efficient. But to achieve this you need to know your way with android.
8. Charging - same as all others. Except when the phone is off I think the is a problem with that. Please confirm.
Things to improve:
// Volume.
// Camera frame rate.
// The headset problem.
// Charging problem while the phone is off.
// Bluetooth toggle bug (FC if it's off).
// OTG.
// MHL.
Again M1cha, THANKS!
It is impressive!
Sent from my MI 2 using Tapatalk 2
You have done the impossible.
I'm running the last build for the last few days and I have to say: you are a very skilled developer
This is high level class of development!!
And I'm happy that I could afford donating you, because you deserve it.
Now to my feedback MI2 32g model:
1.Fast fast fast!! Finally we can see our device's full potential.
2. Battery usage, same as we have with MIUI ROMS, way better then all others non-MIUI ROMS
3. Audio (volume \ quality) same as stock ROM could be better and louder with a bit tunin. What do you think?
3.5. Vibration - the same as all others
4. Camera, works gr8! Didn't have any problems what so ever. Hopefully you will find some hack to help the others and to improve the frame rate.
6. WiFi and 3g signals, I did not had problems like others, I'm very satisfied!
7. Overall look, feeling and every day use - with Xposed on board there is nothing you can't do. It looks beautiful it is very friendly and efficient. But to achieve this you need to know your way with android.
8. Charging - same as all others. Except when the phone is off I think the is a problem with that. Please confirm.
Things to improve:
// Volume.
// Camera frame rate.
// The headset problem.
// Charging problem while the phone is off.
// Bluetooth toggle bug (FC if it's off).
// OTG.
// MHL.
Again M1cha, THANKS!
It is impressive!
Sent from my MI 2 using Tapatalk 2
Last edited:
zxzyzd
Members
- 28 Oct 2013
- 35
- 20
Battery life for me is OK, but not great unfortunately :
Other than that, had a few issues with camera apps, normally I use moto x camera downloaded from xda, but that one doesn't work and makes the default camera not work until a reboot. Workaround: only use default camera
No wifi problems or bluetooth here though
Sent from my MI 2 using Tapatalk
Other than that, had a few issues with camera apps, normally I use moto x camera downloaded from xda, but that one doesn't work and makes the default camera not work until a reboot. Workaround: only use default camera
No wifi problems or bluetooth here though
Sent from my MI 2 using Tapatalk
Last edited:
zxzyzd
Members
- 28 Oct 2013
- 35
- 20
With Gmail synchronizing, whatsapp/Facebook messenger etc?
Sent from my MI 2 using Tapatalk
cbpbxecmecmbeh
Members
- 19 Sep 2013
- 390
- 52
I also thought it is a very good ROM. Had no problems with camera or wifi whatsoever and the battery was great. At least as good as stock MIUI. Thanx M1cha
sent from my C97
Medina
Members
- 27 Dec 2011
- 245
- 65
For those who like to raise up the volume follow this steps:
1.First thing first: BACKUP!!!
2.Use any root explorer you want to navigate to your device folders.
Open "etc" folder.
Open "snd_soc_msm" folder.
Open file " snd_soc_msm_2x_Fusion3 " file with text editor.
3.Look for:
SectionDevice
Name "Speaker"
Comment "Speaker Rx device"
EnableSequence
'SLIM_0_RX Channels':0:One
'RX3 MIX1 INP1':0:RX1
'RX3 MIX1 INP2':0:RX6
'RX4 DSM MUX':0SM_INV
'RX3 Digital Volume':1:68
'RX4 Digital Volume':1:68
'LINEOUT1 Volume':1:66
'LINEOUT3 Volume':1:66
'SLIM TX3 MUX':0:RMIX3
'SLIM TX5 MUX':0:RMIX5
EndSequence
4. The lines you want to edit are:
'RX3 Digital Volume':1:68
'RX4 Digital Volume':1:68
Only change the percentage amount, and only change it in small increments.
//I changed mine to 70.
Like this:
'RX3 Digital Volume':1:70
'RX4 Digital Volume':1:70
5. Reboot and the volume change will take effect.
Sent from my MI 2 using Tapatalk 2
1.First thing first: BACKUP!!!
2.Use any root explorer you want to navigate to your device folders.
Open "etc" folder.
Open "snd_soc_msm" folder.
Open file " snd_soc_msm_2x_Fusion3 " file with text editor.
3.Look for:
SectionDevice
Name "Speaker"
Comment "Speaker Rx device"
EnableSequence
'SLIM_0_RX Channels':0:One
'RX3 MIX1 INP1':0:RX1
'RX3 MIX1 INP2':0:RX6
'RX4 DSM MUX':0
SM_INV'RX3 Digital Volume':1:68
'RX4 Digital Volume':1:68
'LINEOUT1 Volume':1:66
'LINEOUT3 Volume':1:66
'SLIM TX3 MUX':0:RMIX3
'SLIM TX5 MUX':0:RMIX5
EndSequence
4. The lines you want to edit are:
'RX3 Digital Volume':1:68
'RX4 Digital Volume':1:68
Only change the percentage amount, and only change it in small increments.
//I changed mine to 70.
Like this:
'RX3 Digital Volume':1:70
'RX4 Digital Volume':1:70
5. Reboot and the volume change will take effect.
Sent from my MI 2 using Tapatalk 2
letsfifa
Members
- 27 Aug 2013
- 279
- 40
How can we change the in coming audio volume form calls?For those who like to raise up the volume follow this steps:
1.First thing first: BACKUP!!!
2.Use any root explorer you want to navigate to your device folders.
Open "etc" folder.
Open "snd_soc_msm" folder.
Open file " snd_soc_msm_2x_Fusion3 " file with text editor.
3.Look for:
SectionDevice
Name "Speaker"
Comment "Speaker Rx device"
EnableSequence
'SLIM_0_RX Channels':0:One
'RX3 MIX1 INP1':0:RX1
'RX3 MIX1 INP2':0:RX6
'RX4 DSM MUX':0
'RX3 Digital Volume':1:68
'RX4 Digital Volume':1:68
'LINEOUT1 Volume':1:66
'LINEOUT3 Volume':1:66
'SLIM TX3 MUX':0:RMIX3
'SLIM TX5 MUX':0:RMIX5
EndSequence
4. The lines you want to edit are:
'RX3 Digital Volume':1:68
'RX4 Digital Volume':1:68
Only change the percentage amount, and only change it in small increments.
//I changed mine to 70.
Like this:
'RX3 Digital Volume':1:70
'RX4 Digital Volume':1:70
5. Reboot and the volume change will take effect.
Sent from my MI 2 using Tapatalk 2
Thanks
Batterylife was much better on Wiui for me because i had no RILJ wakelock there, or at least it didn't occur that often.
2 days with 4-5h screen was absolutely no problem on Wiui, now RILJ wakelock kills the battery and i'm happy if i get 4-5h screen and 1 day batterylife. (mi2 with 3100mah - disabling locationaccess is not an option)
2 days with 4-5h screen was absolutely no problem on Wiui, now RILJ wakelock kills the battery and i'm happy if i get 4-5h screen and 1 day batterylife. (mi2 with 3100mah - disabling locationaccess is not an option)
I had a strange issue right now.. Since I unplugged my phone from the charger in the morning I had a msm_otg wakelock preventing the phone from sleep so I rebooted a few hours ago and deep sleep was perfect (with a short RILJ wakelock) then I recently plugged in a charger (BlackBerry wall charger) and the phone didn't recognize that I plugged it in no matter what I did. So I rebooted again with charger plugged in and now it's working fine. (although I suspect I'll have another wakelock issue again soon :-\ )
