I flashed romaur 4.x, each version also found very hot and crazy battery draining issue even full wipe in recovery.
Finally, found the NFC couldn't start and the option missed in setting, know that there's got a new firmware for NFC, so I tried factory reset and the update pop up after reboot....
then..... problem solved..... although the battery still use faster than 434....
Related
Hello. As some of you may remember - I have serious problems with wakelocks and it's related to a "SMSDispatcher" service (for those who are interested - http://forum.xda-developers.com/showthread.php?t=2138980).
I had no issues at all on ICS before I upgraded to official JB. Great battery life, huge screen-on time, ~3 days on battery with small usage was something normal for me.
But after upgrading to JB I started to get wakelocks. Loads of wakelocks. I checked battery stats - the Dialer apk showed up. I installed Better Battery Stats and it showed me that "SMSDispatcher" prevents my phone from goind into deep sleep. I thought it was a bug so I flashed back my .195 4.0.4 FW. And guess what. The problem was still there. It... transfered from JB to ICS?! I have this problem for 3 weeks now and even today I still don't know how can I get rid of this.
I tried wiping every partition on the phone including both SD's. Tried deleting contacts on SIM card. Tried deleting all contacts from GMAIL and manually adding them again. Tried flashing stock JB and use my T without restoring ANYTHING. But I haven't tried one thing:
Yesterday I installed unofficial CM10 (from original android development subforum). Almost clear android could have bringed a peace to me finally. It runs great but not perfect. Why? I still have SMSDispatcher issue. LOADS of wake-ups from the Dialer apk (sometimes it shows as com.android.phone, sometimes as RILD).
What I discovered is that on ICS these wakelocks are shorter than on JB. About 1/1,5h of wakelocks for ~22h on battery. On Jelly Bean it was 3h for 8h on battery.
As far as I remember on 4.0.4 .195 FW there was -19 baseband. Both official JB and CM10 use -33 baseband which may be a problem, I don't know.
So my next step in my long path to get rid of this annoying bug is changing to ICS baseband.
And my question is - which files shoud I pull from .195 stock SONY 4.0.4 FW?
I tried to flash baseband using flashtool but the baseband didn't change. It's still -33. So I probably need binaries/files pulled from ICS and I don't know which ones.
Can you help me? Maybe with your help I could finally get rid of this or at least make the problem less annoying...
Can you just flash an ICS firmware and exclude everything except baseband?
Not sure if it wise but it may help you.
romcio47 said:
I tried to flash baseband using flashtool but the baseband didn't change. It's still -33.
Click to expand...
Click to collapse
I already did that. No result.
Another idea - is it possible to repair software on the phone with unlocked BL?
EDIT:
Ok, found Jozinek's thread with .ftf to relock my bootloader. I will try to repair my software and see if this fix my problem.
Problem solved. It was my old SIM card's fault. It was more than 6 years old and I had to manually cut it from mini-SIM to micro-SIM shape. I probably damaged its inside structure or something. I went to my carrier and requested a new SIM card factory cut to a micro-SIM shape and now everything is ok! No strange wakelocks at all!
Hi mate!
I just was wondering after all that u've experienced what do you thing about JB , which is better for performance and battery life management ICS or JB? I'm just thinking is it worth it to upgrade to JB or stay on ICS
Stay on ICS if you don't like charging your phone once a day (in good scenario). Or twice.
ICS has definitely much better working Extended Standby Mode. It gives you amazing battery life sometimes. I'm on JB because of better multitasking and higher RAM available but speaking about the battery - ICS wins. JB just has to be fixed and tweaked by SONY. It's just a first public release. So bugs are something common. We have to wait.
Hello, i have lg 4x hd . After test 4.4 Kitkat i flash stock rom and after day i flash Enoxv10 rom. And phone start to be very fast hot, battery drain - 1% per 1 minute, phone is unusused, no sim and no wi-fi, screen of. I try flash another rom, 4.4 , v20a, v20b , v10f and nothing. I noticed that the microfone and any sound not work. Any solutions? I attach log cat , is very intresting ...
http://www76.zippyshare.com/v/19000599/file.html
Are you 100% sure that when you flashed stock kdz you didn't get any errors?
yes, any errors, phone normal reboot after flash and log is correctly
Feautures, not bugs
;L
Sent from my LG-P880
Don't spam. Before this phone works fine ...
OK, well i can reproduce the battery drain (even when phone is idle), heating issues to the point of shut-down on any ROM. My Sim-card wont load up on boot and usually takes toggling flight mode a few times, try that.
No wifi after flash just sounds strange, may actually be a HW problem
Sent from my LG-P880
I have recently flashed a new ROM over my GE android revolution ROM and since then I have been getting strange Android System Battery drain from what seems to be my light/proximity sensors. I have no idea what app is causing this problem because even after a fresh wipe and install of a completely new ROM I still get the same issue. I have tried a lot and I really have no other options than to reach out for help. I heave searched and found no solutions.
I am experiencing a battery drain issue after updating to MIUIv23. I don't know whether its only me or all of you. I am posting here to know whether there is any way of reverting to v16 or any better way to solve this battery drain issue. Any help will be much appreciated.
Thank you
before reverting , check under battery use ,which app or device is using the battery most, some times it could be some spurios app, try cleaning your cache to clear them
if that doesnt work try factory resetting and installing your apps
You can always revert to the previous MIUI version by formatting your phone using MiFlash (check MIUI forum for more details).
Hy guys,
I'm facing some issues with my Z3C. I bought it 2 weeks ago, unlocked bootloader, installed twrp, flashed CyanogenMod 12.1 Nightly on day 3. Updated CM twice with OTA since then.
My problem is that the "sim" card (GSM/LTE) is randomly not noticed by my phone, like if its removed. I checked the sim tray, everything is stable and well seated, the sim is also OK, never had an issue with it. I just have it in my pocket or on the desk, pick it up to do something and there is already a No SIM icon on the status bar, and "Emergency calls only" If I lock the phone. Only a restart solves it.
I could not find any noticeable trigger which would lead me to the source of the problem. Sometimes its OK for 2 days sometimes it happens 2 times a day. The really frustrating part is that when the sim "disconnects" the phone starts to heat up significantly. I usually only notice it because my phone is burning my pocket. Also it looses around 20% battery before I notice it. After the restart everything is fine, the phone cools down.
Went to the Cyanogen forums for some possible solution for the problem, they suggested that I should try to update my baseband to the latest version, and if that still doesn't help, do a full wipe / clean install of CM nightly. I tried downloading the latest firmware using FlashTool and XperiFirm, creating an ftf, and flashing only AMSS_FSG, AMSS_FS1, AMSS_FS2 included into the flash ( I only wan't to flash the baseband ?!?).
My question would be: Anyone else had this problem and managed to fix it somehow? If not, anyone could please help me with a small guide how to ONLY update the baseband of my Z3C (D 5803) running CM 12.1 nightly on twrp recovery?
When I tried the flash above, my baseband version did not change. Currently I'm on "8974-AAAAANAZQ-00005-40" Baseband version, and I would like to move to the latest most stable one.
Thanks for the help in advance!
If it were my Z3c, I would flash back to stock completely and then reflash with Cyanogen. This is a device on which you have the freedom to do that, and that gets the job done safely. Backup your CM install, and then flash everything.