Please confirm if FW .475 solved all the Screen Issues - Sony Xperia Z Ultra

My screen issues after powering on from sleep have been resolved with Firmware .475

Also mine. I no longer have any funky lines when I wake the device or other strange screen issues since updating.
So so nice. Performance is fantastic.
Sent from my Sony Xperia Z Ultra

brosenz said:
My screen issues after powering on from sleep have been resolved with Firmware .475
Click to expand...
Click to collapse
My battery took a nose dive since the upgrade.. I had issues at first, but they settled down. Now with the upgrade my battery is back to being crap again.

I thought for sure it fixed my SOD. Then five minutes ago, I turned off the phone to eat something. Five minutes later, hit the power button. Dead. Power + Up required as always.

The buttery life is amazing with new update !

Fixed my curtain issue
Sent from my C6802 using XDA Premium HD app

seem like fix my touch issues also:victory::victory:

Will I get an update even if xzu hast been officially released here?
Sent from my C6802 using Tapatalk HD

kramdens said:
My battery took a nose dive since the upgrade.. I had issues at first, but they settled down. Now with the upgrade my battery is back to being crap again.
Click to expand...
Click to collapse
It'll settle again after a couple of charges. This is something most ROM flashers here knows (not saying that you should've known, but now you do).

brosenz said:
My screen issues after powering on from sleep have been resolved with Firmware .475
Click to expand...
Click to collapse
The same. Additionally the Issue with the proximity sensor was resolved also (the screen did not switched on after phone was got from face )
Sent from my C6802 using xda app-developers app

Maybe that who cant fix issues got a defective device ??

avetny said:
Maybe that who cant fix issues got a defective device ??
Click to expand...
Click to collapse
Or maybe the bug(s) are still sticking (pretty common with ROM flashing). They should do a full reset/wipe after updating and see if that solves it.

LordManhattan said:
Or maybe the bug(s) are still sticking (pretty common with ROM flashing). They should do a full reset/wipe after updating and see if that solves it.
Click to expand...
Click to collapse
100% agree ! Always full wipe !

I think one of the new features is the smart dial
Now you can search through the dial pad in the phone.
Sent from my C6802 using xda app-developers app

I didn't experience SOD on the .471 either but my experience from other devices are as follows when it comes to narrow the problem down:
1. A rogue app. If the device suddenly starts to SOD after a couple of installations, then there's an app causing it to hang when entering deep sleep.
2. Excessive undervolting (not relevant for us yet). One SOD cause is too low voltage to the CPU, causing it to lock up when it enters deep sleep. The problem can also be connected with underclocking, for example to 100 or 192 MHz.
3. Hardware failure.
4. ROM problem. There are ROMs, even official ones that are prone to SOD.
The solution is to make a full wipe and then just wait and see what happens with the device when it is completely clean. If it still suffers from SOD even if nothing is configured, then it points to a hardware problem or ROM bug. Trying a different ROM can be worth a try.
If that still doesn't solve the problem, i.e. it continues to SOD regardless of ROMs - there is a hardware failure.
If it works fine after a full wipe but then starts to experience SODs when apps are installed etc, then there is a rogue app involved.
My longest uptime on the 471 was around 5 days and 6 hours before I updated to 475. No problems during that time.

E90 Commie said:
I didn't experience SOD on the .471 either but my experience from other devices are as follows when it comes to narrow the problem down:
1. A rogue app. If the device suddenly starts to SOD after a couple of installations, then there's an app causing it to hang when entering deep sleep.
2. Excessive undervolting (not relevant for us yet). One SOD cause is too low voltage to the CPU, causing it to lock up when it enters deep sleep. The problem can also be connected with underclocking, for example to 100 or 192 MHz.
3. Hardware failure.
4. ROM problem. There are ROMs, even official ones that are prone to SOD.
The solution is to make a full wipe and then just wait and see what happens with the device when it is completely clean. If it still suffers from SOD even if nothing is configured, then it points to a hardware problem or ROM bug. Trying a different ROM can be worth a try.
If that still doesn't solve the problem, i.e. it continues to SOD regardless of ROMs - there is a hardware failure.
If it works fine after a full wipe but then starts to experience SODs when apps are installed etc, then there is a rogue app involved.
My longest uptime on the 471 was around 5 days and 6 hours before I updated to 475. No problems during that time.
Click to expand...
Click to collapse
How do I do a full wipe with SOD? Sony Bridge and PC Connect both won't continue when I click on the "continue" button at the personal data loss screen (the personal data loss disclaimer box is checked).

I ran into this issue using a mac.
Sent from my C6802 using XDA Premium HD app

dobygot said:
How do I do a full wipe with SOD? Sony Bridge and PC Connect both won't continue when I click on the "continue" button at the personal data loss screen (the personal data loss disclaimer box is checked).
Click to expand...
Click to collapse
I do the full wipe from Settings. Now I have an unlocked bootloader and can't use either Sony Update Service or Sony Bridge and I prefer to have it that way. I trust FlashTool more.
Updating without full wipe using S-US/Bridge is a pretty sure way to experience problems.

Related

Fingerprint sensor service not working

I was using sensorly, and when I locked the screen it attempted to block it when it asked me a question. My phone vibrated for a few seconds as it fought to overcome the fingerprint screen (and failed)
The fingerprint scanner wont initialize (always ready... but never really). I have to reboot(haven't yet). I can't stop the process/service either... no idea why.
Anyone know of any fixes?
Rooted 1.8.3 stock
Sent from my MB860 using XDA App
mine randomly stops working (lame, right?) and rebooting always fixes it for me
I own a Nokia N810... from my experience rebooting kills the life of your battery with these kinds of devices, and this happens like once every 2 days for me
winky! said:
mine randomly stops working (lame, right?) and rebooting always fixes it for me
Click to expand...
Click to collapse
Same here.
Mgamerz said:
I own a Nokia N810... from my experience rebooting kills the life of your battery with these kinds of devices, and this happens like once every 2 days for me
Click to expand...
Click to collapse
When you say life of battery do you mean it discharges more energy than it would if you didnt reboot it? Or do you mean the battery itself will die months sooner than it would have.?
Battery capacity lowers over time. Booting that thing clocked it at 400Mhz (the top speed) for about 5 minutes, eating up a whopping 5-20% of the battery.
I noticed my battery lasted less and less every time it crashed and rebooted (it does it so much now that its pretty useless (read: every 10 or so minutes) - thanks nokia)
I have a feeling its the same way with Lithium Batteries too... The battery life is about 40 minutes (if im lucky) and I used to get like a day (of moderate use).
winky! said:
mine randomly stops working (lame, right?) and rebooting always fixes it for me
Click to expand...
Click to collapse
Meee 3 dammit!
Sent from my MB860
winky! said:
mine randomly stops working (lame, right?) and rebooting always fixes it for me
Click to expand...
Click to collapse
Same but only since 1.83 Hopefully it is fixed in a future update.
Sent from my MB860 using Tapatalk
Its impossible to kill the fingerprint reader service. I find that kind of strange.
Sent from my MB860 using XDA App
That kind of makes sense. I think the fingerprint service might be an integral part of the system so you can't fully kill the process... Kinda like the android process.
And the comment about battery dying after a reboot faster is true. If you reboot a phone, especially these android beasts with 1ghz+ processors, revs up the processor to max, essentially eating up a large chunk of battery because it would be running at max for 5-10+ minutes. It's crazy. So unless you wanna do a lot of charging, don't restart too much.
Sent from my SGH-T959 using XDA App
I mean like the life of the battery.
New: 16 hours of use
200 reboots later :4 hours of use
Sent from my Motorola Atrix 4G on the network with the most backhaul, whatever that is
I notice mine doing this as well the fingerprint scanner even got really hot at one point crazy must be a 1.83 thing
Sent from my MB860 using XDA App
Well on one hand I'm happy to see it's not just me. On the other hand it sucks that it consistently happens. For me if I continually run my finger on the scanner on a reboot it will unlock the screen. Then, after a bit (or a few locks) it will stop working and just say "Initializing Fingerprint Scanner" or something along those lines. I ended up disabling it and using a pattern as a screen lock.
For me it happened after installing a ROM that had 1.8.3 as its base. I've seen some previous mentions of the issue I'm seeing and tried their fixes but they haven't worked. I'm eager to see this get fixed. Otherwise I really like the device.
I use widgetlocker and once in a while it won't work when I first wake it up but if I hit the back key and go to the default lockscreen it initializes right away and I can use the scanner.
Holy run-on sentence, Batman! Sorry
Sent from my MB860 using XDA App
I may have been able to reproduce it. Unlock your phone, then immediately lock it, then immeditely wake it. Killed the fingerprint sensor.
Sent from my Motorola Atrix 4G on the network with the most backhaul, whatever that is
Mgamerz said:
I may have been able to reproduce it. Unlock your phone, then immediately lock it, then immeditely wake it. Killed the fingerprint sensor.
Sent from my Motorola Atrix 4G on the network with the most backhaul, whatever that is
Click to expand...
Click to collapse
Yeah for me, and maybe this is a similar state/situation, I find it really happens when I swipe the unlock screen after waking the phone up rather than the fingerprint sensor.
It happens to me sometimes.
But instead of rebooting my device, I go to Settings -> Location & security -> Change screen lock. There I use my password/pin and then I wipe my fingerprints already registered and start all over again.
My system update is the one before 1.5.7 I guess (the android updates are called OTA ### right?)
Hope it helps someone who doesn´t reboot the device.
Thanks

[Q] Sleep of Death

Whenever my phone goes to sleep, and I try and turn on the screen again, it simply reboots. This occurs in airplane mode with nothing enabled as well
Unlocked, CM7. I flashed different roms and they all had this, I don't think it happened on stock.
Any fixes? All the threads I've seen have no real info
Seems like your system files might be corrupted. Wipe system partition from fastboot or cwm then reflash your rom. Any time I had weird stuff happen on a rom, I wipe the system then it goes away. Hope this helps you get rid of this issue. Good luck!
Sent from my MB860 on CM7.2.0 Stable
Doesn't work, just wiped system, cache and dalvik, then flashed rom and sod's still happen.
I have also tried flashing several radios, all with sod's. Any suggestions?
wakelock
I had this problem on stock and every rom I tried (this was actually the reason I unlocked) I installed wakelock app from the market. I set it on partial wakelock. I think it keeps phone from going into deep sleep. It worked for me. I think it may make battery life a bit worse but having to pull battery sucks. Since I also have the issue on stock I am prob sending it in on warranty
affiatic said:
I had this problem on stock and every rom I tried (this was actually the reason I unlocked) I installed wakelock app from the market. I set it on partial wakelock. I think it keeps phone from going into deep sleep. It worked for me. I think it may make battery life a bit worse but having to pull battery sucks. Since I also have the issue on stock I am prob sending it in on warranty
Click to expand...
Click to collapse
So you've had SODs since you got the phone? Wakelock seems to work, but kills the battery.
For anyone who does NOT have SODs what modem/radio are you using?
Yes had them since I got the phone. Wakelok fixed it for me. Battery life is not horrible. It still last me like 14 hrs moderate use. I have tried radios and everything else I could thing of. Think mine is hardware related. That is why I am sending it in. I was surprised to find out it was still under warranty
I've just noticed that when mine shuts down, it gives a green notification first, then when I try turning the screen it, it reboots.
Unfortunately, my phone is out of warranty, I bought it used
SODs still happen in airplane mode.
Try wakelock and post if that fixes it.
Call Motorola directly. I bought two used. Had the same problem. They replaced them both with new units.
Motorola Android Department
1-800-734-5870
Just don't say anything about buying it used.
Good luck.
As posted above, wake lock works but uses battery.
I live in Canada and am out of warranty, would I still be able to call?
It's worth a try. You have nothing to lose.
Sent from my MB860 using xda premium
I had the same problems.. but mine happens when phone gets above 35°C.. So I activate wakelock at this time until i see temp is lower than that.. after that I disable wake lock.. it's a pain in the ass.. but it is better than pull the battery out once every 15 min..
javinavas said:
I had the same problems.. but mine happens when phone gets above 35°C.. So I activate wakelock at this time until i see temp is lower than that.. after that I disable wake lock.. it's a pain in the ass.. but it is better than pull the battery out once every 15 min..
Click to expand...
Click to collapse
Is there something specific about 35C, and are you sure it is exactly that?
I have installed 2.3.6 Bell and I still get reboots, anyone have a link to stock 2.2.1 Bell SBF that I can try?
sometime 35 sometime 36.. but above that temp.. sod kills me.. under that temp phone runs smooth..
I'm a system enginner but I haven't program in years.. I'm thinking seriously in create just a services to read temp and launch a wake lock when temp reache some level..
I'm pretty sure I will help lot of people but aint sure when i can start doing some work
dancom96 said:
Whenever my phone goes to sleep, and I try and turn on the screen again, it simply reboots. This occurs in airplane mode with nothing enabled as well
Unlocked, CM7. I flashed different roms and they all had this, I don't think it happened on stock.
Any fixes? All the threads I've seen have no real info
Click to expand...
Click to collapse
my phone would not actually reboot but in went into SOD (sleep of death) so every time this has happened to me i installed a new kernel or reinstalled the one i had.........always rectified the issue.
Same issue
I had the same problem when I flashed CM9 and then when I downgraded back down to CM7, I tweaked the kernels I used and changed my UV settings and it hasn't happened since. Perhaps flash a different kernel and see if that works?
jediknightbrodie said:
I had the same problem when I flashed CM9 and then when I downgraded back down to CM7, I tweaked the kernels I used and changed my UV settings and it hasn't happened since. Perhaps flash a different kernel and see if that works?
Click to expand...
Click to collapse
Tried several of them, this seems to happen on stock 2.3.6 as well.
I flashed a stock sbf to return to stock. Still had the sleep of death. Reboots after and during phone calls, and touch screen problems. I believe it is hardware related.

Slow wake up

When I lock the screen of my Galaxy S3, then press either the power button or the home button to show the lockscreen, about half the time it takes about 2 seconds to show the screen after button press. I've searched and seen S-Voice caused this problem so I disabled that. I also removed my SD card and rebooted but the same issue still occurs.
Any way to fix this because my HTC One X didn't have this problem...
Thanks.
wman2 said:
When I lock the screen of my Galaxy S3, then press either the power button or the home button to show the lockscreen, about half the time it takes about 2 seconds to show the screen after button press. I've searched and seen S-Voice caused this problem so I disabled that. I also removed my SD card and rebooted but the same issue still occurs.
Any way to fix this because my HTC One X didn't have this problem...
Thanks.
Click to expand...
Click to collapse
Flash other ROM can make it faster...
Or tune off power saving mode.
photomrq said:
Flash other ROM can make it faster...
Or tune off power saving mode.
Click to expand...
Click to collapse
Power saving mode is already off. I don't particularly want to flash a ROM unless I have to because I've had warranty troubles in the past. Are you certain a ROM would fix it? Which ROM?
And I also tune lock screen off.
Do you install any power save app??
Two Whole Seconds close your eyes and count to ten not worth the bother wait for JB release ,
jje
I get this also. Got it on the Stock ROM and ARHD. I have also seen this on my gf's Galaxy Ace, but only when upgraded to GB. On Froyo (Yes, that old version) it turns on instantly. So think it might be a Samsung thing. Not yet tried an AOSP ROM on my S III yet so may give that a go as itching to get some Jelly Bean on it.
Hello! I am new to xda forums and this is my first post
I also have a problem with slow wake up time from sleep after flashing the latest Synergy rom. Any ideas why this lag happens?
Thank you in advance!
this lag is killing me. it's mega retarded that high end phone is having this kind of bug.
any rom without slow wake lag to reccommend?
bojler said:
this lag is killing me. it's mega retarded that high end phone is having this kind of bug.
any rom without slow wake lag to reccommend?
Click to expand...
Click to collapse
Is a one second lag really spoiling your experience? Then flash to a non TW rom.
Sent from my GT-I9300 using xda app-developers app
kofiaa said:
Is a one second lag really spoiling your experience? Then flash to a non TW rom.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Lag is hardware-related looks like. Present on CM10 based ROMs as well. On stock-based disabling S-Voice helps just a little bit when it comes to waking up from Home button...
Killing me as well. :\ What I getting used to is to press Home while pulling phone out - straight away so by the time I get it in position to work with, the screen is either already on or will be on in a 200-500 ms.
Still this is a most frustrating "feature" of SGS3 that will most likely force me to look for replacements once those are available on the market.
The issue is still present even in the latest Paranoid Android ROM.
After tweaking a bit, I found that if you have WiFi enabled, will cause this lag.
Just disable the WiFi and you get instant screen wake up.
inteq said:
After tweaking a bit, I found that if you have WiFi enabled, will cause this lag.
Just disable the WiFi and you get instant screen wake up.
Click to expand...
Click to collapse
No difference here
Sent from my GT-I9300 using xda premium
This problem annoys me to death too. I've tried many ICS/JB stock ROM and custom ROM (including CM10), but none of them could solve the problem.
I did notice some trend: right after a reboot, the screen turns on fairly quickly. Then after turning on the network (mobile data or wifi) and use facebook or other apps that access network for a few minutes, the delay starts to increase to the usual ~2sec. Looks like some network process might be causing the problem. FYI, My cousin's Note 2 don't seem to have this problem.
Any hacker out there can give some hints or help find out what process might be the culprit?
it's because the phone goes into deep sleep, to prevent this you can download a app that named softlocker. you may get not as good batterytime.
mingan84 said:
it's because the phone goes into deep sleep, to prevent this you can download a app that named softlocker. you may get not as good batterytime.
Click to expand...
Click to collapse
"not as good" would be too soft of a term. It'll kill your battery life probably
mingan84 said:
it's because the phone goes into deep sleep, to prevent this you can download a app that named softlocker. you may get not as good batterytime.
Click to expand...
Click to collapse
From what I see, I don't believe deep sleep is the problem. My LG P500 (running ICS) goes into deep sleep all the time (per CPU spy et al), and it never has this problem. Seems to me like something else is causing this...
ligu said:
From what I see, I don't believe deep sleep is the problem. My LG P500 (running ICS) goes into deep sleep all the time (per CPU spy et al), and it never has this problem. Seems to me like something else is causing this...
Click to expand...
Click to collapse
no other brands have this problem. only samsung, thats so strange.
I too suffer from wakeup delay of 1-2 seconds and it's driving me crazy.
After 2 long years I had to live with majestically f**ed up LG Optimus 2X, I finally decided to throw that junk away and get a phone that works as expected, phone performance of which would be equal to it's price (and the price was not something that limited me).
Now I own a phone which even though is snappy and nice and everything, takes ages to wake up. And what pisses me off the most is that Samsung is OK with that, because obviously majority of the customers / owners is OK with that. How is that possible ffs. Low end devices for fraction of that price resume from deep sleep almost immediatelly (in time I don't consider waiting). How's that this is not a big issue ?!
Sorry, I'm just frustrated
EDIT: To add something constructive ... the deep sleep really is the problem here. If the phone doesn't go to deep sleep, wake up to lockscreen is instantaneous (try that by yourselves with SoftLocker app). It's believed that S3 suffers from this issue because of the way the GSM modem is integrated with (or in ? I am not sure) Exynos4 - source.
I just smacked my phone in the table, while in my pocket and now I"m experiencing the same problem. Is this even possible, or I had it before and just didnt notice till now?!

Holy hell Batman at the Battery Drain!

Is anyone else getting Android OS around 50-60% battery use?
I have tried every ROM included going back to stock. I have ran the phone with nothing but Stock and no apps installed for a day and still get the same drain so I can only assume its a kernel issue.
I am not familiar with LG products in the slightest, but I had a yellow screen of death the other day...something I have never seen in my years with samsung android products. Anyone have any idea what this is maybe it is pointing to a hardware issue?
LG made a great phone, but I don't think I will keep it much longer. Locked boot loaders, no sources, and history of terrible updates have me regretting purchasing this phone. I tried my hand at building a working jb release when I first got the phone and it is going to take a skill set I do not have and I hate waiting on a company to do what they've never done in the past..
jivy26 said:
Is anyone else getting Android OS around 50-60% battery use?
I have tried every ROM included going back to stock. I have ran the phone with nothing but Stock and no apps installed for a day and still get the same drain so I can only assume its a kernel issue.
I am not familiar with LG products in the slightest, but I had a yellow screen of death the other day...something I have never seen in my years with samsung android products. Anyone have any idea what this is maybe it is pointing to a hardware issue?
LG made a great phone, but I don't think I will keep it much longer. Locked boot loaders, no sources, and history of terrible updates have me regretting purchasing this phone. I tried my hand at building a working jb release when I first got the phone and it is going to take a skill set I do not have and I hate waiting on a company to do what they've never done in the past..
Click to expand...
Click to collapse
Easy, brother. I have only had one of my apps/utilities run higher than AndroidOS ever on this phone; however, that said, I think there is a problem with the way it's being calculated. I'm getting really good battery life with good sleep and still AndroidOS shows the highest by far. I know that's abnormal for it to be so high and still get good battery life, but it is what it is.
Edit: you've installed the fast dormancy toggle, right? As for the yellow screen, I've seen it once in my two months with the phone, just rebooted and carried on. Forgot what they said it was...but it is here in this forum somewhere.
Sent from my LG-E970 using xda app-developers app
I was just about to post something similar. Andriod OS being high kind of makes sense if nothing else is using the battery, although you would expect that number to fall significantly with increased screen on time and heavy app usage, which it doesn't ever seem to.
I've been having horrible battery drain lately. I'm currently traveling for business, and just use my OG for web surfing and stuff when I'm in my hotel. I leave the phone in airplane mode, with WiFi on. About two weeks ago, when I was on The Base 0.4 in that same configuration, my battery would drain maybe 1% an hour while I was sleeping.
Recently I've been on The Base 0.7.3, and my battery drains over 5% an hour while I'm sleeping. This means no screen on, no apps running, and even turning WiFi off! How does it use that much battery when it's not doing anything? Now, I'm not entirely sure what kernel I'm running. The first time I installed The Base 0.7.3 I used sk8's kernel. After getting poor battery life, I reflashed 0.7 and 0.7.3, this time choosing the freegee kernel. I'm not actually sure if the kernel changed though.
Anyway, I think I'll post again tomorrow with some screenshots from Better Battery Stats+ and CPU Spy.
I'm wondering if this recent botched update had the battery fixes we need. Hopefully they'll re-release it soon.
Jank4AU said:
Easy, brother. I have only had one of my apps/utilities run higher than AndroidOS ever on this phone; however, that said, I think there is a problem with the way it's being calculated. I'm getting really good battery life with good sleep and still AndroidOS shows the highest by far. I know that's abnormal for it to be so high and still get good battery life, but it is what it is.
Edit: you've installed the fast dormancy toggle, right? As for the yellow screen, I've seen it once in my two months with the phone, just rebooted and carried on. Forgot what they said it was...but it is here in this forum somewhere.
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Yea I've tried fdt but I think it has to be kernel related drain issues
Sent from my LG-E970 using Tapatalk 2
Digil said:
I was just about to post something similar. Andriod OS being high kind of makes sense if nothing else is using the battery, although you would expect that number to fall significantly with increased screen on time and heavy app usage, which it doesn't ever seem to.
I've been having horrible battery drain lately. I'm currently traveling for business, and just use my OG for web surfing and stuff when I'm in my hotel. I leave the phone in airplane mode, with WiFi on. About two weeks ago, when I was on The Base 0.4 in that same configuration, my battery would drain maybe 1% an hour while I was sleeping.
Recently I've been on The Base 0.7.3, and my battery drains over 5% an hour while I'm sleeping. This means no screen on, no apps running, and even turning WiFi off! How does it use that much battery when it's not doing anything? Now, I'm not entirely sure what kernel I'm running. The first time I installed The Base 0.7.3 I used sk8's kernel. After getting poor battery life, I reflashed 0.7 and 0.7.3, this time choosing the freegee kernel. I'm not actually sure if the kernel changed though.
Anyway, I think I'll post again tomorrow with some screenshots from BatteryStats+ and CPU Spy.
I'm wondering if this recent botched update had the battery fixes we need. Hopefully they'll re-release it soon.
Click to expand...
Click to collapse
When I would get bad drain, which has happened several times, I could narrow it down to a couple things in order to solve the problem.
In my case it would always happen after installing Google+. Uninstall and reboot would usually fix the issue. If I got drain on a fresh install without g+ installed, I found that if I installed the 2.2 kernel separately as a stand alone zip, that would fix it. Don't know why but it may work for you too.
I don't have screen shots, but today I recharged at 38% after 3:10 of phone use and 1:55 screen on time and about 15 hours off charger. That's with Wi-Fi on the whole time and Bluetooth for about 9 hours. I have my work exchange account on active sync with push notifications. Facebook and Twitterer to 4 hour intervals. I'm underclocked to 1350 and using powersave gov with deadline.
Sent from my LG-E970 using xda app-developers app
jivy26 said:
Yea I've tried fdt but I think it has to be kernel related drain issues
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
Believe you are correct. There were issues on the Samsung Infuse and even the international SGS3 for a while... it was referred to as 'memory leak.' Has been worked out by devs on XDA. You can put memory leak in the XDA search above... it's above my pay grade.
Edit: It's great to see another RD here... hope you will reconsider keeping the phone and stay !!
Jank4AU said:
When I would get bad drain, which has happened several times, I could narrow it down to a couple things in order to solve the problem.
In my case it would always happen after installing Google+. Uninstall and reboot would usually fix the issue. If I got drain on a fresh install without g+ installed, I found that if I installed the 2.2 kernel separately as a stand alone zip, that would fix it. Don't know why but it may work for you too.
I don't have screen shots, but today I recharged at 38% after 3:10 of phone use and 1:55 screen on time and about 15 hours off charger. That's with Wi-Fi on the whole time and Bluetooth for about 9 hours. I have my work exchange account on active sync with push notifications. Facebook and Twitterer to 4 hour intervals. I'm underclocked to 1350 and using powersave gov with deadline.
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Thanks for pointing me in the right direction. I have Google+ uninstalled, but part of me thinks Google Now may be partially the culprit (although why that would be the case with all radios off, I don't know).
I'll try a fresh install of the 2.2 kernel and see if that helps. Thanks.
I can't speak for anyone else but FDT did wonders for my battery life. I was only able to go about 12 hours prior to disabling FD.
Sent from my Optimus G
Digil said:
Thanks for pointing me in the right direction. I have Google+ uninstalled, but part of me thinks Google Now may be partially the culprit (although why that would be the case with all radios off, I don't know).
I'll try a fresh install of the 2.2 kernel and see if that helps. Thanks.
Click to expand...
Click to collapse
I always install GNow, love the inverted version.
Sent from my LG-E970 using xda app-developers app
johnbyebye said:
I can't speak for anyone else but FDT did wonders for my battery life. I was only able to go about 12 hours prior to disabling FD.
Sent from my Optimus G
Click to expand...
Click to collapse
This is good for sure... it's just that compared to other phones, Android OS and Android System should not be that high.
Pony Express said:
This is good for sure... it's just that compared to other phones, Android OS and Android System should not be that high.
Click to expand...
Click to collapse
That's what leads me to believe it's a faulty measure...
Sent from my LG-E970 using xda app-developers app
Jank4AU said:
That's what leads me to believe it's a faulty measure...
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
^^^ This is indeed worth considering.... I think the question then becomes why is it consistent among the 3 roms we are using? Maybe when JB source is out and something is built from source all will be good.
Pony Express said:
^^^ This is indeed worth considering.... I think the question then becomes why is it consistent among the 3 roms we are using? Maybe when JB source is out and something is built from source all will be good.
Click to expand...
Click to collapse
I would be less inclined to believe it is a faulty measure if we had a different ROM not built off stock (AOKP/CM10) that could produce different values. However, I seriously doubt anything built into either of the two custom ROM's is geared toward normalizing that reading. That's why they are both the same as the stock AndroidOS percentages. Jivy is probably right that it's a kernel issue. With the size battery we have, imagine the potential if it is a true reading (androidOS out-of-control) and we can get it under control down the road. We're talking double the current best battery life you've ever had on this phone at the very least.
Sent from my LG-E970 using xda app-developers app
+1
LOL
v
v
v
+43
Get BetterBatteryStats, select Since unplugged and Alarms to see what is waking the device (making it not go into a deep sleep). eBay was a big culprit for me.
The wakelock that keeps the phone awake during background data transfer (screen off) lasts 6 seconds (I am guessing it does it in multiples of 6s) regardless of how long the sync takes. Everytime email, facebook, gmail, drive, picasa, twitter, g+, google maps, ebay, calendar, contacts.. whatever wakes the phone to check something, it will be a minimum of 6 seconds.. This adds up over the course of the day and it is counted in the Android OS. Shut down syncs you don't absolutely want/need and this number will go down. All phones with the Snapdragon S4 Pro has it, especially the Nexus4. It seems they've done some kernel work to fix/reduce it but I havent really looked into it since I don't have that phone. I've seen complaints in the Droid DNA forum as well.
snacsnoc said:
Get BetterBatteryStats, select Since unplugged and Alarms to see what is waking the device (making it not go into a deep sleep). eBay was a big culprit for me.
Click to expand...
Click to collapse
This. EBay for me too. BetterBatteryStats is your friend.
Anyone else experiencing scrolling lag or delay. Clearing cache and wiping dalvik fixes it but the issue returns after about two days.
Sent from my LG-E970 using Tapatalk 2
jivy26 said:
Anyone else experiencing scrolling lag or delay. Clearing cache and wiping dalvik fixes it but the issue returns after about two days.
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1987032

(SOLVED) ZU heating after 4.3 update

If anyone is experiencing this problem, I hope the following steps may help.
I would like to express my appreciation to XDA members, who have commended and helped out with this. Credits go to @LordManhattan and @abuihsan . Many thanks for your help.
1/ Do a re-flash: I always thought my device was a c6802, after I flashed c6833, it helped.
2/ Do a factory reset/ Cache wipe/ Dalvik Wipe/ in recovery or in the phone settings.
3/ Install SD-Maid and clean the mess from the programs, also take a look at APPCONTROL to see which is running. You can freeze it here.
4/ Install Performance control to Underclock your CPU. Believe me, 1.7Ghz is far too enough for all the tasks you need.
5/ Use more pwerful tool, like Titanium Backup to stop all the backgound-running apps. You just need to leave the one which were in GREEN color.
6/ Use Wakelock Detector to see which apps get your phone out of deepsleep. Mostly they are Facebook and Messenger. My advice: Disable Facebook notice and if you don't use chat quite often, don't install facebook messenger.
Hope these help.
Personally I had tried a lot of methods, including checking the processes and re-insert the memory card but no such helps. Therefore, if you need any advice or any comments, feel free to send me an PM or reply here, I will gladly help you out, like what the community had helped me our of my situation.
Hi everyone,
Recently I just bought a ZU from a local vendor here. It runs 4.2.2 with no problem. However, I want to get rid of the *new system update* and I also want to use the xperia Themes, I decided to upgrade to 4.3.
My phone model is C6802, and I chose the file here : http://forum.xda-developers.com/showthread.php?t=2453921
The upgrade went through fast and smooth, as I had experienced in many Sony devices.
However, after getting to 4.3, I had noticed some problems as follow:
+ Heat: Device heats up very fast, even left alone. Just imagine you have the phone on 100% battery lying on your table, a moment later it heats up and the battery drops dramatically.
+ Battery drop: Just as mentioned above, the battery drops quickly. I do not expect extreme battery life on this device, but since 4.3, it is too low, I can barely make it to 6 hours without doing anything consuming battery.
+ Process: When checking the battery, I notice that most of the process that takes up battery is Android OS, which nearly 50-60%. I use the phone frequently to answer SMS and call, sometimes play games. I think that the most used applications should be the bad-ass screen?
I am running on the 14.2.A.0.290 with R4B.
Anyone had experienced this problem before, or know a solution to fix? Will clearing the Dalvik Cache help? I had re-flash several times but the problem is still there.
Many thanks in advance.
Click to expand...
Click to collapse
Sounds like somethings has gone wrong in the update process.
Have you tried backing up all your data and doing a factory reset?
I do not think clearing Dalvik will help you here, sounds like something else is acting up. You could try to install one of the apps designed to detect what is causing the wakelock.
I'm not at my Android tablet at the moment, but I think I used this when I had this problems myself on my Galaxy Note: https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector
Sent from my iPad mini using Tapatalk HD
fjevel said:
Sounds like somethings has gone wrong in the update process.
Have you tried backing up all your data and doing a factory reset?
I do not think clearing Dalvik will help you here, sounds like something else is acting up. You could try to install one of the apps designed to detect what is causing the wakelock.
I'm not at my Android tablet at the moment, but I think I used this when I had this problems myself on my Galaxy Note:
Sent from my iPad mini using Tapatalk HD
Click to expand...
Click to collapse
First of all, thanks for your reply and suggestion.
I had tried to flash the roms multiple times, but the problem still exists. Furthermore, I even flash back to 4.2.2 and the problem is still there. The phone heats up slowly and battery runs out pretty fast.
I had installed the Wakelock Detector on my device and I will update the situation tomorrow, I will leave it there for a night and see the status tomorrow.
Did you wipe after updating? I had the same issue when i updated to 4.3.
Correct me if I'm wrong, but as long as he's been downgraded to 4.2.2 again, he'd have to wipe. At least that is how it was on my Xperia Z.
-KJ
this might not be related, but I've been noticing much worse battery life today than normal! i normally only drop about 50% in 24 hours, but today I've dropped 30% in just a few hours. Android OS seems to be doing it...
no real heat issue tho, maybe slightly warmer from whatever the OS is doing, but nothing too major. running stock rooted 4.3
had that on my Xperia Z on a 4.1 or 4.2 build (dunno which one). Sounds strange, but simply turning off the sync fixed the problem, give it a try :laugh:.
Hope it also helps on your XZU.
LordManhattan said:
Did you wipe after updating? I had the same issue when i updated to 4.3.
Click to expand...
Click to collapse
At first I did not choose to wipe Data in Flashtool, then I flashed again, this time I checked everything.
the problem still exists.
UPDATE:
Yesterday after working hours, I had rooted and installed BetterBatteryStats, Performance Control to monitor the system. I also had WaveLockDetector and Titanium Backup installed.
It appeared that the CPU runs all the time, in the highest state (2.15 Ghz), the phone never goes to DeepSleep and Awake all the time.
On Performance control, I had underclocked the CPU to 1.5Ghz and the temperature seems to be cooler.
I had tried to freeze a lot of applications via Titanium backup but so such luck.
Still researching.
However, many thanks to your kind replies. At least I know that I'm not alone with this problem :good:
justsomebody said:
At first I did not choose to wipe Data in Flashtool, then I flashed again, this time I checked everything.
the problem still exists.
UPDATE:
Yesterday after working hours, I had rooted and installed BetterBatteryStats, Performance Control to monitor the system. I also had WaveLockDetector and Titanium Backup installed.
It appeared that the CPU runs all the time, in the highest state (2.15 Ghz), the phone never goes to DeepSleep and Awake all the time.
On Performance control, I had underclocked the CPU to 1.5Ghz and the temperature seems to be cooler.
I had tried to freeze a lot of applications via Titanium backup but so such luck.
Still researching.
However, many thanks to your kind replies. At least I know that I'm not alone with this problem :good:
Click to expand...
Click to collapse
I ever had no deep sleep problem with 4.3, even in stamina and airplane mode, and with location-off too, I checked with BBS and found the 'trigger' is a process under google now app. I use GREENIFY and get the google now hybernated. Everything fines now and I still can use google now as it only hybernated when not in use : )
abuihsan said:
I ever had no deep sleep problem with 4.3, even in stamina and airplane mode, and with location-off too, I checked with BBS and found the 'trigger' is a process under google now app.and get the google now hybernated. Everything fines now and I still can use google now as it only hybernated when not in use : )
Click to expand...
Click to collapse
hey, thanks for your reply. I did the same to you, even with Titanium backup to ensure this will never shows up again, but CPU keeps throtlling at 100%. I still can not find an answer to this 100% thing. now the phone is quite hot in my pocket, I decided to put in my bag and even turn off to keep it from heating.
I will try another rom and update.
justsomebody said:
hey, thanks for your reply. I did the same to you, even with Titanium backup to ensure this will never shows up again, but CPU keeps throtlling at 100%. I still can not find an answer to this 100% thing. now the phone is quite hot in my pocket, I decided to put in my bag and even turn off to keep it from heating.
I will try another rom and update.
Click to expand...
Click to collapse
do you use any cleaner/task killer app? before trying other rom or update, maybe you need to uninstall it, reboot recovery and wipe cache and see the result.
I don't know if this is relevance but while using greenify I also uninstall the previous cleaner app and replace with another one that I think is better.
now my c6833 has great deep sleep.
abuihsan said:
do you use any cleaner/task killer app? before trying other rom or update, maybe you need to uninstall it, reboot recovery and wipe cache and see the result.
I don't know if this is relevance but while using greenify I also uninstall the previous cleaner app and replace with another one that I think is better.
now my c6833 has great deep sleep.
Click to expand...
Click to collapse
Hi, Thanks again for your advice.
Would you please give me the name of the cleaner apps that you think are way better?
Are you running on 4.3 stock or on some modified roms?
justsomebody said:
Hi, Thanks again for your advice.
Would you please give me the name of the cleaner apps that you think are way better?
Are you running on 4.3 stock or on some modified roms?
Click to expand...
Click to collapse
The thing is, you don't need a task killer/cleaner app. It was useful way back on Android 2.1/2.3, but you shouldn't use it at all on 4.0+. You're actually making things worse.
mine has been heating up as well. the battery isn't draining like how yours is, but any kind of use will heat the top back side of the phone. I checked and after killing all apps, my cpu load was still around 65%. is that normal? no custom flash here. locked bootloader. updated through pcc normally. I'd imagine this is why 4.3 isn't running as buttery smooth like everyone else.
Sent from my C6833 using xda app-developers app
ij0rgei said:
mine has been heating up as well. the battery isn't draining like how yours is, but any kind of use will heat the top back side of the phone. I checked and after killing all apps, my cpu load was still around 65%. is that normal? no custom flash here. locked bootloader. updated through pcc normally. I'd imagine this is why 4.3 isn't running as buttery smooth like everyone else.
Sent from my C6833 using xda app-developers app
Click to expand...
Click to collapse
No, that's not normal. Mine's around 20-30 degress celsius (depending on what i'm doing). Even streaming 1080p videos shouldn't make it hot or even mildly hot. When i had the heating problem, two cores would always be stuck at 2150 MHz. Now one core is active at 960 MHz when the screen is on. CPU load is around 20 and 60% (single core). Temperature is currently at 26 degrees. Also, stop killing apps and processes. Most of them are set to start automatically, so when you kill them over and over again, they'll start again and they'll use even more battery. Android is built to manage resources very well on its own, and it's not operating like Windows or any other computer OS. Just leave it alone unless something has gone rouge and you don't have a choice.
I'm on stock 290, rooted and extremely debloated.
- Current battery level: 88%
- Current uptime: 3 h 30 min
- Current screentime: 1 hour (browsing etc.)
LordManhattan said:
No, that's not normal. Mine's around 20-30 degress celsius (depending on what i'm doing). Even streaming 1080p videos shouldn't make it hot or even mildly hot. When i had the heating problem, two cores would always be stuck at 2150 MHz. Now one core is active at 960 MHz when the screen is on. CPU load is around 20 and 60% (single core). Temperature is currently at 26 degrees. Also, stop killing apps and processes. Most of them are set to start automatically, so when you kill them over and over again, they'll start again and they'll use even more battery. Android is built to manage resources very well on its own, and it's not operating like Windows or any other computer OS. Just leave it alone unless something has gone rouge and you don't have a choice.
I'm on stock 290, rooted and extremely debloated.
- Current battery level: 88%
- Current uptime: 3 h 30 min
- Current screentime: 1 hour (browsing etc.)
Click to expand...
Click to collapse
hmm... yea that sounds like the problem i am having. im noticing two cores stuck at 2150mhz with a third kicking in here and there. how were you able to fix it? just a fresh install of .290?
so as far as the apps go, i have Du Battery Saver installed and the "optimize" button is supposed to clear up some of the background junk. are you saying that i should leave the optimize button alone and just let android figure itself out?
ij0rgei said:
hmm... yea that sounds like the problem i am having. im noticing two cores stuck at 2150mhz with a third kicking in here and there. how were you able to fix it? just a fresh install of .290?
so as far as the apps go, i have Du Battery Saver installed and the "optimize" button is supposed to clear up some of the background junk. are you saying that i should leave the optimize button alone and just let android figure itself out?
Click to expand...
Click to collapse
What i'm saying is that you should uninstall that crappy app. Task killers were useful three years ago when Android devices had slow processors and low amount of RAM. What you're doing now is killing everything everytime you tap that button. WHY do you want to do that? What's the point of having 2GB of RAM when you don't want to use it? Are you always killing processes on your computer too? Would you do it if your computer had 32GB of RAM with 30GB available? Unused RAM is wasted RAM. Android is a modern OS that can handle this on its own. If you only have 300MB RAM left and you want to play Asphalt 8 which requires (i'm guessing) 500MB RAM, Android will find the oldest and less frequently used process and kill it. It's that easy.
You can read more about it here and here.
LordManhattan said:
What i'm saying is that you should uninstall that crappy app. Task killers were useful three years ago when Android devices had slow processors and low amount of RAM. What you're doing now is killing everything everytime you tap that button. WHY do you want to do that? What's the point of having 2GB of RAM when you don't want to use it? Are you always killing processes on your computer too? Would you do it if your computer had 32GB of RAM with 30GB available? Unused RAM is wasted RAM. Android is a modern OS that can handle this on its own. If you only have 300MB RAM left and you want to play Asphalt 8 which requires (i'm guessing) 500MB RAM, Android will find the oldest and less frequently used process and kill it. It's that easy.
You can read more about it here and here.
Click to expand...
Click to collapse
gotcha. I get what you're saying.
now that that is settled, what to do about the original problem? phone is still heating up.
Sent from my C6833 using xda app-developers app
ij0rgei said:
gotcha. I get what you're saying.
now that that is settled, what to do about the original problem? phone is still heating up.
Sent from my C6833 using xda app-developers app
Click to expand...
Click to collapse
I think it'll be a little easier if you tell us what you've done till now. We have no idea what you've tried and not tried.
Sent from my Z Ultra
LordManhattan said:
I think it'll be a little easier if you tell us what you've done till now. We have no idea what you've tried and not tried.
Sent from my Z Ultra
Click to expand...
Click to collapse
ok. so I haven't done anything at all to remedy the situation. I figured I'd ask about it before messing it up myself. I upgraded to .290 via pcc. it updated fine with no errors. once it was done updating, it was hot and battery was diminished. I had seen on another thread that most people had that happened so I didn't see it as an issue, just a side effect of the update process.
I have been checking back to see if anyone was having heating issues with 4.3 after the update and didn't hear about it until I had seen this thread. the OP stated he flashed .290 on his 6802 and is rooted. I am not, so I wasn't sure if the steps he was taking were the same given my 6833 being completely stock.
Sent from my C6833 using xda app-developers app

Categories

Resources