Database Develop

[Xperia T Q] Advantages of .223 FW comparing to the old .195?

Hello. I have to ask this question because I'm not sure about the sense of updating to newer FW since I haven't found any changelog. Yesterday I've reflashed .195 again because the battery life was pretty "interesting" on .223 during week of usage. Like the Extended Standby Mode was broken or something. On .195 it was normal for me to charge the battery to 100% (~4180mV or more shown by Curvefish's battery widget), unplug the phone, leave it for the night (7 hours of my sleep time) then wake up, go to work 6am, leave the phone again in the locker and during the break (8.30am) battery was still 100%. But on .223 it was normal for the battery to be at 95/93% while using the phone the same way I had already described. It's really strange. By the way I used Advanced Stock Kernel, for both FWs. V4 for .195 and V5 for .225.
Does the same things happen to you? Is there any other thing that make .223 a better FW worth flashing?
Tapatalked from Poland using Xperia T.

Funny, but I've been considering downgrading to 195 as I found battery, WiFi and responsiveness all slightly better, the only irritating but was that power off sometimes did reboot instead of shutdown!
Be interesting to hear what others think??
sent from my T, which is so good it nearly makes the tea. ;p

I have downgraded my tx from 212 to 197 for same reasons
Sent from my LT29i using xda app-developers app

Personal I found .223 to be really helpful. For one thing, I had camera random freezing issue when saving to SD card on .195. After I switched to .223, I never experience the same problem again. (Although in some cases, the SD card would disappear, but after checking error in windows, it's fine so far)
It's just my $.02
Sent from my LT30p using xda app-developers app
---------- Post added at 07:19 PM ---------- Previous post was at 07:14 PM ----------
For people who are wondering about battery level, I think the later FW (.223) may actually report more realistic result.
The reason is that when in extended standby mode, the phone is still not completely shutdown, i.e. the cell antenna still needs to be active for receiving call or sms. The timer still needs to be alive for time based event, such as alarm. All of them will use small amoint of charge. For over 6 hours, it only uses 5-7% of battery, I think it's fair.
I find it strange if these sensors working for continuously 6 hours without using 1% of the battery.
Sent from my LT30p using xda app-developers app

I literally can't see any difference, battery life is the same for me, never had the reboot issue

I am still waiting for Sony to push this update to my phone, No update via PC Companion or OTA. Has this update not been pushed to the UK devices yet?

Is the phone plugged in to power/usb when it reboots from a power off?

What are your WiFi issues on .223?
I didn't even try older version, but on .223 my WiFi is very unstable. Signal reception going up&down very sharply. I'm talking of e.g. -35 to -68dBM variations with the phone right next to the access point, and plenty of disconnections if further away. Verified with Inssider.
All this with a d-link 802.11n router. (Don't bother with "dlink are crap" cause it worked fine with all my cellphones since 5 years ago.)
No problems though with other devices, my notebook picks up good signal everywhere and there are no variations.

try changing the channel
I've seen funny results with my tablet and wifi until I changed the channel on my router. It might be the same with your phone also. I have no detailed explanation except that it worked fine after.

Wobba-Lee said:
I am still waiting for Sony to push this update to my phone, No update via PC Companion or OTA. Has this update not been pushed to the UK devices yet?
Click to expand...
Click to collapse
I'm in the UK, AFAIK .195 is the latest but I just used the central european .223 rooted ftf to upgrade
Sent from my LT30p using Tapatalk 2

matt4321 said:
I'm in the UK, AFAIK .195 is the latest but I just used the central european .223 rooted ftf to upgrade
Sent from my LT30p using Tapatalk 2
Click to expand...
Click to collapse
Yep its in the UK. I'm on O2 and got an over the air update over WiFi late last night.

thenext1 said:
What are your WiFi issues on .223?
I didn't even try older version, but on .223 my WiFi is very unstable. Signal reception going up&down very sharply. I'm talking of e.g. -35 to -68dBM variations with the phone right next to the access point, and plenty of disconnections if further away. Verified with Inssider.
All this with a d-link 802.11n router. (Don't bother with "dlink are crap" cause it worked fine with all my cellphones since 5 years ago.)
No problems though with other devices, my notebook picks up good signal everywhere and there are no variations.
Click to expand...
Click to collapse
Yeah I had similar problems too on .223! While sitting in my room it was normal on .195 to have one bar of WiFi signal (without counting the dot). On .223 the signal was lost>found>lost>found... every few minutes... even when not moving at all.
Besides, my friend has Xperia T too and he noticed the same problem about battery - like something was broken... maybe radio? Maybe deep sleep? I don't know.
Also another very interesting thing is that when comparing battery stats in settings it seems that .223 has got screwed up baseband/radio. 9 hours of deep sleep results in many signal drops. I remember the cellular signal was like greeeeeeeeeeeen>yellow,red,yellow,reeeeeeeed,yellow>greeeeeeeeeen>and again... many quick yellows and reds...
And on .195? See for yourself, today screenshot after coming out from work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So the 80% sure conclusion is - Sony, you messed up the battery pretty hard for a few users with this update...
Tapatalked from Poland using Xperia T

sproyd said:
Yep its in the UK. I'm on O2 and got an over the air update over WiFi late last night.
Click to expand...
Click to collapse
Just got an update alert from PC companion to .223 fw for a UK sim free Xperia T

So is it worth updating to .223? I've just had the update show up in pcc
Sent from my Nexus 7 using Tapatalk 2

del1701 said:
So is it worth updating to .223? I've just had the update show up in pcc
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Not sure yet... Need to check if there is a ftf file for .195 before I update + do the usual backups etc

ruwsoft said:
Not sure yet... Need to check if there is a ftf file for .195 before I update + do the usual backups etc
Click to expand...
Click to collapse
There are plenty in the all in one thread. First thread in this section. Post 3

Well I updated via ota this morning, everything seems ok so far
Sent from my Nexus 7 using Tapatalk 2

thenext1 said:
What are your WiFi issues on .223?
I didn't even try older version, but on .223 my WiFi is very unstable. Signal reception going up&down very sharply. I'm talking of e.g. -35 to -68dBM variations with the phone right next to the access point, and plenty of disconnections if further away. Verified with Inssider.
All this with a d-link 802.11n router. (Don't bother with "dlink are crap" cause it worked fine with all my cellphones since 5 years ago.)
No problems though with other devices, my notebook picks up good signal everywhere and there are no variations.
Click to expand...
Click to collapse
I got the phone with original 195 ROM (LT30a), switched to 223(CE) and now I'm back to 195 (Rogers). better battery life, stable wifi connection and LTE is back comparing to 223(CE) . Got the same problem with wifi while on 223 like you describe.

[BATTERY IMPROVEMENT] Works every time half the time :)

DISCLAIMER AS PER USUAL: YOU DO IT AT YOUR OWN RISK.
Although procedure itself is simple enough, but as alway, anything involving flashing, especially firmware has it's risks.
Oki doki. Time to come out in the open
Prelude. I was hard pressed to get 4h screen on time in 10-12h off charger. Then i screwed something up (irrelevant ) and had to reflash stock images.
Now my next findings are sure to attract so flaming from more experienced users that will say "it's placebo", "it doesn't work like that" etc. While I don't have screenies to confirm pre flash stats, i have gathered a few post flash stats. Here we go.
Some cycles are missing, since i either accidently deleted screenies or forgot to take them. But that should give you a general idea. WiFi used mainly, apart from last cycle, where 12 were on data only and the rest was while connected to wifi and reading a book in fbreader.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
And this is ROM/KERNEL i used before and after flashing images. Note, kernel has been updates since, but it didn't make much difference.
So for me it's fairly conclusive, reflashing stock images has GREATLY improved my battery life. I had a few chats and we came to a conclusion that it is possible that at the factory device has simply not been flashed "properly", mass flashing differs from your usual .img flashing normally.
What you think...Well, it's up to you for decide. I know few more people who've done the same, and while their improvement is not as drastic as mine, it is still an improvement.
Please vote AFTER you try it, and after min of 2 cycles.
How to in post no2

Simply follow this great guide by efrant. Keep in mind it will wipe your storage, so backup all the pics and other stuff.
Before you do it, take below quote into consideration if you use google wallet.
dacho said:
Oh yes, you have to reset Google wallet before you flash it. You would log into Google wallet then settings and click reset wallet. I remember this from galaxy nexus days.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
efrants guide
People who are more experienced will know how to cut corners If you don't know what you are doing, I suggest you follow efrants guide to the letter. This way you'll learn a fair bit too.
Same process for every images version. Also, I ALWAYS do it for any images update, since I'm not a believer in patching. I might be wrong, but hey, it works for me. So my personal recomendation would be to redo this after every new OTA.
So:
1. Backup your "SD" contents.
2. Flash ALL stock images as per efrants guide (or any other way if you know how to)
3. You are most likely to get stuck on boot. Hold power button, shut down, reboot into recovery. Once you see broken droid hold power button and tap +vol. Once in recovery do factory reset. If you don't get stuck on boot, still do it.
4. Boot on stock. It's a good idea to transfer your rom and kernel onto sd now since you can't mount sd in recovery.
5. Reboot into bootloader and proceed to push recovery and then flash your previous setup (ROM/KERNEL)/
How to push recovery.
Code:
fastboot flash recovery recovery-image-name.img
I will not tolerate any flaming, just report if it worked for you or it didn't. If you want to stir some **** you better go elsewhere. Chit chat related to the topic is approved and appreciated
I want to mention DowntownJeffBrown, DirtyHamster, ctowe, Jayrod1980, siloner, estallings15 and anyone else I forgot (just remind me in the thread) for being the beta bunnies Thank you.​

I'm gonna try this and report thre results. Were you on auto-brightness, sync, gps...? Give us some more infos about what your configurations are
Thank you for the tip, I'll try.

sorcio91 said:
I'm gonna try this and report thre results. Were you on auto-brightness, sync, gps...? Give us some more infos about what your configurations are
Thank you for the tip, I'll try.
Click to expand...
Click to collapse
All on auto, the only two things i have disabled is gnow and location reporting (which is primarily used for gnow anyway) and had that disabled from day one. The rest of the settings are irrelevant, since they are the same from before i reflashed stock.

Interesting, be good to see what others report.
If i hear a few good reports, i might take the plunge next week.
Edit: might just be Rasbean jelly giving you good battery life!

Cool, I'll give it a try and see what it does!
I'm struggling to get +4 hours of battery life ATM, so let's hope this helps.

superleeds27 said:
Interesting, be good to see what others report.
If i hear a few good reports, i might take the plunge next week.
Edit: might just be Rasbean jelly giving you good battery life!
Click to expand...
Click to collapse
It's not. Wait till some Americans who done the same thing wake up
There are about 4-5 more people who report the same, that's why i decided to share. Had to make sure first that it's not a fluke.

Re: [BATTERY IMPROVEMENT] Works 100% so far.
The thing that's helping battery life here isn't the reflash, it's the factory reset that happened when you did it.

Rusty! said:
The thing that's helping battery life here isn't the reflash, it's the factory reset that happened when you did it.
Click to expand...
Click to collapse
I would tend to agree. But which would be the cause, removed culprit user installed app(s) or something not set as intended from factory as a result of mass flash/ reset etc at factory? Or both?
Maybe even a difference between OTA updating new units after setup or before?
Would be easy to test the theory by just doing a factory reset without re-flashing and see if it makes a difference.

Rusty! said:
The thing that's helping battery life here isn't the reflash, it's the factory reset that happened when you did it.
Click to expand...
Click to collapse
I did think of that. Thing is flashing ROM fresh IS factory reset. Factory reset doesn't do more than delete all the data and maybe reflash /system. So i disagree with you here Rusty. Think about it. I took my time to carefully evaluate changes, and you might know from my time in Sensation forum that I do look into things before posting it.
clockcycle said:
I would tend to agree. But which would be the cause, removed culprit user installed app(s) or something not set as intended from factory as a result of mass flash/ reset etc at factory? Or both?
Maybe even a difference between OTA updating new units after setup or before?
Would be easy to test the theory by just doing a factory reset without re-flashing and see if it makes a difference.
Click to expand...
Click to collapse
See above.
Also, apps have nothing to do with it, since my (and other people) setup is identical to what it was before doing that.
And thanks to the person voting NO. I guess following simple request is too difficult.
If you guys are sceptical, do it before you do next fresh install since you don't lose anything and report back.

undercover said:
I did think of that. Thing is flashing ROM fresh IS factory reset. Factory reset doesn't do more than delete all the data and maybe reflash /system. So i disagree with you here Rusty. Think about it. I took my time to carefully evaluate changes, and you might know from my time in Sensation forum that I do look into things before posting it.
See above.
Also, apps have nothing to do with it, since my (and other people) setup is identical to what it was before doing that.
And thanks to the person voting NO. I guess following simple request is too difficult.
If you guys are sceptical, do it before you do next fresh install since you don't lose anything and report back.
Click to expand...
Click to collapse
Thanks for posting this! Very interesting if others are experiencing the same. I will try it when I get time. What do you think is the improvement? Did you restore a nandroid or did you manually reinstall everything? Thx bro!

Re: [BATTERY IMPROVEMENT] Works 100% so far.
jonup said:
Thanks for posting this! Very interesting if others are experiencing the same. I will try it when I get time. What do you think is the improvement? Did you restore a nandroid or did you manually reinstall everything? Thx bro!
Click to expand...
Click to collapse
I can vouch for this experiment that we somehow agreed to without even hesitating lol.
Personally, i manually installed EVERYTHING. no nandroid or titanium back up. Before i would get roughly 9hr phone usage with 2.5-3 hrs battery. After going through this i now get 13-14hrs phone usage with 4-4.5 screen on. I know that's normal for some but compared to what i had before, is an improvement. This was just in the first cycle. I'm on my second and wool report back when I'm done
Sent from my Nexus 4 using xda premium

As it stands i can hit 5 n half hours with round a day standby.
Would it be worth doing?

Re: [BATTERY IMPROVEMENT] Works 100% so far.
superleeds27 said:
As it stands i can hit 5 n half hours with round a day standby.
Would it be worth doing?
Click to expand...
Click to collapse
Not sure. But someone already had very decent battery life and extended it by another 0.5-1h screen on. I guess you wouldn't lose anything if you tried. Just a half an hour of setting things up.
Sent from my Nexus 4 using Tapatalk 2

Re: [BATTERY IMPROVEMENT] Works 100% so far.
undercover said:
Not sure. But someone already had very decent battery life and extended it by another 0.5-1h screen on. I guess you wouldn't lose anything if you tried. Just a half an hour of setting things up.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
+1 I've seen their posts.
Make a nandroid. You have nothing to lose but time. It's the weekend anyway.

Dont want to say anything but on screenshoots there is practically no apps other than browser or taptalk, play a game, watch a clip on YT, listen to some music ohh and switch off WiFi. Phone is to be used outside where you dont have a WiFi, At home I have my Laptop that is far much better than than a phone to read stuff, and XBox that is far much better for gaming....
I could probably pull 8h screen if I switch everything off sans WiFi and just have web browser opened on one page.
Ohh And I'm on stock since day 1 + had to reflash image due to kernel net being compatibile with screen sensitivity driver .... No changes, What you have on images wont repeat itself outdoors.
Look at that screen where you dont have WiFi on. Your usage dropped by 8hrs screen time by 1hr and still no phonecalls, txt, nothing really.... just chrome
I get 3hrs 30min screen + 17hrs usage with music in bacground, quick game + and reading, no reception for about 8hrs or if there is any its 1bar....(and that drains the battery)

Re: [BATTERY IMPROVEMENT] Works 100% so far.
MattSkeet said:
Dont want to say anything but on screenshoots there is practically no apps other than browser or taptalk, play a game, watch a clip on YT, listen to some music ohh and switch off WiFi. Phone is to be used outside where you dont have a WiFi, At home I have my Laptop that is far much better than than a phone to read stuff, and XBox that is far much better for gaming....
I could probably pull 8h screen if I switch everything off sans WiFi and just have web browser opened on one page.
Ohh And I'm on stock since day 1 + had to reflash image due to kernel net being compatibile with screen sensitivity driver .... No changes, What you have on images wont repeat itself outdoors.
Look at that screen where you dont have WiFi on. Your usage dropped by 8hrs screen time by 1hr and still no phonecalls, txt, nothing really.... just chrome
I get 3hrs 30min screen + 17hrs usage with music in bacground, quick game + and reading, no reception for about 8hrs or if there is any its 1bar....(and that drains the battery)
Click to expand...
Click to collapse
Ok. I think I have to explain something. This is absolutely not about how or what for phone is used. I used it in the same way before I flashed images.
Concentrate on the MAIN thing. Same usage, same rom and kernel, same settings, same apps. The only difference is battery life after flashing stock images files. Immediately.
Sent from my Nexus 4 using Tapatalk 2

Re: [BATTERY IMPROVEMENT] Works 100% so far.
undercover said:
Ok. I think I have to explain something. This is absolutely not about how or what for phone is used. I used it in the same way before I flashed images.
Concentrate on the MAIN thing. Same usage, same rom and kernel, same settings, same apps. The only difference is battery life after flashing stock images files. Immediately.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, he totally missed the point. Same usage, but better battery life. This is not a battery life comparison thread.

Re: [BATTERY IMPROVEMENT] Works 100% so far.
estallings15 said:
Yeah, he totally missed the point. Same usage, but better battery life. This is not a battery life comparison thread.
Click to expand...
Click to collapse
Spot on.
Screenies are there just to show consistency.
Sent from my Nexus 4 using Tapatalk 2

Re: [BATTERY IMPROVEMENT] Works 100% so far.
Well, I guess poll won't reflect true outcome. This is annoying since I do it for you guys. I get no benefit from sharing that, I don't ask for donations or thanks, don't ask for credit. I just want people to enjoy great battery life I'm enjoying.
"Thanks" guys....
Sent from my Nexus 4 using Tapatalk 2

AOSP roms = possible problems

I have been following most of the AOSP threads fairly closely to see people's experiences and I have seen a disturbing amount of people report bricked phones. The odd thing about it is that these bricks didn't occur during the process of flashing a rom. They all happened (or most of them at least) while trying to power on the phone after it was turned off or in deep sleep. Here are links to posts by DIFFERENT AOSP rom users who all experienced similar issues (one of these posts contain links to 3 other posts):
http://forum.xda-developers.com/showpost.php?p=42682374&postcount=78
http://forum.xda-developers.com/showpost.php?p=42654173&postcount=434
http://forum.xda-developers.com/showpost.php?p=42681918&postcount=436
http://forum.xda-developers.com/showpost.php?p=42557657&postcount=417
I personally have run Slim's rom for a good 4-5 hours w/o problems. However, I went back to Sense shortly thereafter. I'm not trying to cause some kind of panic but on the same hand I don't want to see people sitting around with a $500 desk ornament. Bottom line is we are responsible for what we do with our phones and as a result we should do as much research as possible before flashing anything. Look before you leap!
Edit: Here is an additional means to record your brick experience:
smac7 said:
I made this to try to pinpoint the issue. This way we can collaborate with all one owners, not just sprint.
If you have this issue, please add your info.
Here is the form
https://docs.google.com/forms/d/17NmaM3zhWueTxI_y7f1U7N6Er6tprd22I8_f3aIYmCw/viewform
Here is the responses
https://docs.google.com/spreadsheet/ccc?key=0AkLYIbykddrAdF9TMXBXaXZjMFhEczlSYUhoVDNHU1E#gid=0
Let me know if i should add any other crucial questions. I encourage people to post this in other threads when relevant.
Edit: page is open for public sharing
Click to expand...
Click to collapse
Thanks goes out to the user who took the time to do this.

Yep just be careful guys the only warning I had to something strange happening was that my phone didn't charge at all when I turned it off (to try and charge it fast) it still charged while powered on however. But once it died that was it. Also no overclocking or system setting where really changed in my case.
Here's how I got a replacement went in and told them it wouldn't turn on and I myself at the time thought it was the battery so they said that could be it but again I wasnt to sure and neither where them. I ended up paying 50$ without tep
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTCONE using Tapatalk 2

Alex1123 said:
Yep just be careful guys the only warning I had to something strange happening was that my phone didn't charge at all when I turned it off (to try and charge it fast) it still charged while powered on however. But once it died that was it. Also no overclocking or system setting where really changed in my case.
Here's how I got a replacement went in and told them it wouldn't turn on and I myself at the time thought it was the battery so they said that could be it but again I wasnt to sure and neither where them. I ended up paying 50$ without tep
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
That's some messed up stuff.... You shouldn't have had to pay since it was a "hardware" issue. It should've been covered under the manufacturers warranty.

Lol it was but I needed a phone fast and didn't go through HTC
Sent from my HTCONE using Tapatalk 2

Alex1123 said:
Lol it was but I needed a phone fast and didn't go through HTC
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
I know but whenever i've had a problem like that it's always been a free fix through sprint......

yeah I am in the same boat, I believe I was the first to report this. At first I thought it was just me and I passed it off as nothing. Since I've got my replacement I've watched people starting to trickle in with the same exact problem on AOSP I would definitely avoid flashing AOSP until the cause is narrowed down and solved if possible. As I said before it would be a damn shame not to run AOSP on this mighty device, but I have to stick with sense for now and hope that this problem is squashed soon.

Wow really? How upsetting. I'll have to keep an ear open. If there is any news regarding this issue please share
Sent from my HTCONE using xda app-developers app

Has anyone on a NON AOSP rom run their battery down and had it die? Did it charge? I know on a few other phones it was actually the recovery that had this issue. I would try it myself but as I have my phone through work, replacing it is a bit more complicated.

I work for sprint and had a guy come in who bricked his phone. A simple relock of the bootloader and an ruu flash and bam phone was up and working fine. Is that not working for aosp bricks? I've personally haven't had any problems out of aosp roms
Sent from my HTCONE using xda app-developers app

That makes sense. Thanks
Sent from my HTCONE using xda app-developers app

socalnative1 said:
I work for sprint and had a guy come in who bricked his phone. A simple relock of the bootloader and an ruu flash and bam phone was up and working fine. Is that not working for aosp bricks? I've personally haven't had any problems out of aosp roms
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
you are not able to relock the bootloader. we're talking total shut down, no power, no charge, no recovery, no bootloader, no fastboot adb devices, not a thing period point blank. i have the dead device still, and for the life of me cannot get it to do anything. I have been on my replacement for 2 weeks now running sense. hopefully the cause and solution are near.

Well... I was thinking of trying an AOSP ROM, but I guess I will hold of on that thought.
Sent from my HTCONE using Tapatalk 4 Beta

felacio said:
Well... I was thinking of trying an AOSP ROM, but I guess I will hold of on that thought.
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm with you on that

Until we get more kernel sources/reliable code out of HTC, playing with AOSP can be a dangerous game. And tbqh, it could well be OP's fault (not saying it is, but it can be). Flashing custom software of any kind is going to give your carrier/OEM an easy way out if anything goes wrong, which everyone really should keep in mind before making the jump.

What recovery are the "bricked" users running. TWRP or CWM?

Yeah I had my battery die completely on a sense Rom, but I was easily able to charge it and turn it back on 2 minutes later.
Sent from My Only "One"

Glad I'm doing a lot of reading before I make the jump back to HTC. Seems like the One is more of a pain in the ass to Develop (safely) for than the GS3. Looks like I'll be sticking to sense for a while.

For once in all of my android ownership, I'm not really pressed to switch to aosp so this isn't a huge deal for me. The phone is already blazing fast and I actually enjoy and use a lot of the features HTC has implemented into Sense 5. And HTC's browser is the smoothest I've ever used. I do hope someone figures out the problem though. Hate to see more people get bricked.
Sent from my HTCONE using xda premium

Kraizk said:
What recovery are the "bricked" users running. TWRP or CWM?
Click to expand...
Click to collapse
So far, only TWRP users have reported this issue.

I don't want to be Mr. Obvious but I'm assuming that you guys have already tried the trick of putting your phone under a bright light, etc etc

I am loosing my mind! Note eating battery and superslow

Hi!
My Note has for a quite long time now been slow, laggy and eating battery.
Didn't mind, had a car charger, suspected old battery and clogged storage.
About a week ago it came to a complete stop, taking 30 sec to open facebook.
And typing in Swiftkey an impossibillity, having keystrokes on a 5-10sec lag.
So finally i got a new battery, whiped the phone clean.
Flashed the phone with a fresh rom (Team Union JB XXLT4 V7)
Installed my apps manually, making shure no crap cache was brought.
Formatted internal storage and got a new 32Gb SanDisk Ultra card.
Fresh start, fast phone right? no.
Apps still unusably slow, typing on swiftkey impossible without lagging.
Battery from a full charge last about 6h with light usage.
Would like to stay on TW only for the MHL capability, but now i am open to anything.
Can't really afford a new phone, so if this can't get resolved ill switch to my old 3GS.
What do i do now?
What can i try?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The screenshots are from different days and scenarios, but changing governor or other settings gives me about the same result.
Just listened to som music, and some light surfing, thats about all. Battery blames is all on the screen and os about 33% & 33%.

YOu should try AOSP/AOKP Roms!!!

I think one of the apps you have is causing the problem.
When i had the same problem it turned out to be the podcasting app i had.
https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats&hl=en
Or go to the terminal and run top, see whats eating the cpu.

have you try to replace new battery ?!

NoteboyTech said:
YOu should try AOSP/AOKP Roms!!!
Click to expand...
Click to collapse
Thanks for the reply, but i am afraid ill have the same issues.
Azeazezar said:
I think one of the apps you have is causing the problem.
When i had the same problem it turned out to be the podcasting app i had.
https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats&hl=en
Or go to the terminal and run top, see whats eating the cpu.
Click to expand...
Click to collapse
Good suggestion, i'll run top once in a while, see i find anything.
nokia2002 said:
have you try to replace new battery ?!
Click to expand...
Click to collapse
Well, yeah couldn't find any original though, and don't want to wait weeks for a shipment, so got a copy brand "ENERGY" spacy logo and made here in Thailand. Only 2350mAh compared to the original 2500mAh.
Found that the new battery didn't really make any difference, about the same.
So worried i got new but crappy battery I'm now back on original, without any noticable change.
Considering getting a external charger and carrying the spare battery, that is not really a solution either.
Got get this phone working reliably soon, or i need to find a replacement.
Appreciate the tips, and ill try and make a study with "top" and get back to you guys.
Maybe i have a energy hog after all...

It's a pain in the butt, but it looks like the only way to resolve it is to do a clean wipe, then install each
app one by one, giving yourself a day or two of usage. Sucks, but it sure sounds like one app is
screwing up another one. Any chance you can (shudder) use a "memory cleaner/program closer"
after you use each app, to make sure it's closed as a test? Sounds like something sure is
interacting with something else.

USe Greenify and hibernate all apps!!!

Check your Google account settings. If you have sync Internet ticked disable it.
Sent from my GT-N7000 using XDA Premium 4 mobile app

You think you have it bad? I'm only getting 4.5 hours
Sent from my GT-N7000 using xda app-developers app

JellybeanSandwich said:
You think you have it bad? I'm only getting 4.5 hours
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Really?
I thought my battery life was bad. 7h15m with 45 min screen time after charging my battery is at 67%
That is with wifi and bluetooth (with music playing) on and connected.
GPU overclocked and lowest step 200mhz(from 133 and max 400) and cpu up to 1550 Mhz.(okay, i did reduce the voltages, sue me)
and google location service on.
On original battery (dec 2011), that is about to die (screen starts glitching around 30%)
Somehow you are doing it wrong.

You would be surprised at what a speed deference you will get and battery life with aosp roms I have used tw and aosp and always go back to aosp based when tw starts to get laggy. But as most have said most likely a app causing your problem you should try install new Rom with all wipes inclueding preload I think thats what its called and make sure that media scan is not always running
Sent from my GT-N7000 using XDA Premium 4 mobile app

I'm pretty dependant on my camera for my kids. From my readings of AOSP threads, the camera app has never really worked well? Or am I misinformed?
Sent from my GT-N7000 using xda app-developers app

I do not use the camera that much, but i have not had problems with it.
Focal does crash for me and makes me reboob my phone.

Azeazezar said:
Really?
I thought my battery life was bad. 7h15m with 45 min screen time after charging my battery is at 67%
Click to expand...
Click to collapse
With a new battery original OEM just purchased yesterday, I am at 4h10m with 55 minutes screen time at 64%
This is much better.
Sent from my GT-N7000 using xda app-developers app

Just an update everyone:
I'm currently at 7h15m with 2 hours screentime.
The battery is at 38%
I will have to chalk this up to a worn battery being replaced by a real Samsung battery and not a knockoff 3rd party battery.
Sent from my GT-N7000 using xda app-developers app

Batteries make a big difference and as for cm roms and the camera they work great
Sent from my GT-N7000 using XDA Premium 4 mobile app

How about tying to read or post on the battery thread in Q&A instead of posting new threads in the wrong section?

This didn't start out as a battery discussion
Sent from my GT-N7000 using xda app-developers app

AndroidSlave said:
How about tying to read or post on the battery thread in Q&A instead of posting new threads in the wrong section?
Click to expand...
Click to collapse
JellybeanSandwich said:
This didn't start out as a battery discussion
Click to expand...
Click to collapse
How about reading the first post AndroidSlave?
What's this snarkyness that's infected xda?
Shure wasn't around back in the WM days.
This is and or was a very "General" issue with my phone, as i am still not entierely shure is a plain software issue.
However i've made the switch to a or the PA-rom out of desperation.
Still too early too tell, as it is first day after flash, but feels smoother.
What is driving me mad on PA is the lack of lockscreen-homebutton-torch.
Also a bit dissapointed in "Screen Mode" dynamic mode missing.
Missning SPen->screenshot->notetaking is bugging me aswell, but i'm shure ill find some replacement thing for that.
EDIT:
You, know what.
I apoligise if i posted this in the wrong place.
And no bad intentions towards you AndroidSlave.
I just feel that it's the place of a MOD and not of a user to make these claims.
Please just use the report button in if you feel like this, instead of posting a retorical question.

I know, right? What's up with the uninformed snark?
Sent from my GT-N7000 using xda app-developers app

[Q] 14.2.A.0.290 (4.3) System slowdown and RAM issues

Hi guys,
Been on 14.2.A.0.290 4.3 for a few days now, minimal mods - rooted and recovery installed.
For some reason, every so - often (about 8-10 hours), my phone would become slow - and RAM usage skyrockets. WHen it happens I cant tell which apps are offending as all of them are "restarting".
If i restart the phone, everything is fine again.
Its still perfectly usable, I just want to find out if its the ROM (Stock), or whether its a setting, or whether it is an app doing it.
Is there a good application to help me track the health of the apps?
cheers

Since you're rooted, BetterBatteryStats may be of some use, but it's not necessarily a wakelock-related problem.
Maybe you just need something simple like https://play.google.com/store/apps/details?id=jp.vviki.android.SysLoadLogger&hl=en?

xasbo said:
Since you're rooted, BetterBatteryStats may be of some use, but it's not necessarily a wakelock-related problem.
Maybe you just need something simple like https://play.google.com/store/apps/details?id=jp.vviki.android.SysLoadLogger&hl=en?
Click to expand...
Click to collapse
Thanks for the heads up on those apps
Its not wakelock related I dont think. as the phone isnt reporting long wake times, nor is there really a dramatic crash in battery life. its just simply slows down, I think its app related
Just did a wipe, i'll see how I go.
thanks!
anyone else have theories?

http://forum.xda-developers.com/showpost.php?p=48924824&postcount=296
TL;DR: Bug in 4.3, you can't fix it (workaround in post, not exactly a fix), either roll back to 4.2, or wait for 4.4.

MohammadAG said:
http://forum.xda-developers.com/showpost.php?p=48924824&postcount=296
TL;DR: Bug in 4.3, you can't fix it (workaround in post, not exactly a fix), either roll back to 4.2, or wait for 4.4.
Click to expand...
Click to collapse
can that also be the cause of bad battery life? if system server is running in several copies? 4.2.2 had better battery life for me.

shteren said:
can that also be the cause of bad battery life? if system server is running in several copies? 4.2.2 had better battery life for me.
Click to expand...
Click to collapse
Have you gone through 1 or 2 charge cycles? Updates/flashing typically clears battery stats and makes the indicator unreliable for a bit.

shteren said:
can that also be the cause of bad battery life? if system server is running in several copies? 4.2.2 had better battery life for me.
Click to expand...
Click to collapse
More RAM being locked away means apps will relaunch instead of resume, that needs more CPU cycles to switch apps.
I've also noticed that some servers (MediaScanner is part of MediaServer) restart and that may or may not trigger a scan, and that triggers Sony's Photo Analyzer service, both these stress the CPU.
If the leak is fixed, battery life will most likely be better. Standby time is awesome for me, I really suggest doing the workaround in the post I linked. It makes 4.3 a bit more usable.
Sent from my Sony Xperia Z1 using Taptalk

MohammadAG said:
http://forum.xda-developers.com/showpost.php?p=48924824&postcount=296
TL;DR: Bug in 4.3, you can't fix it (workaround in post, not exactly a fix), either roll back to 4.2, or wait for 4.4.
Click to expand...
Click to collapse
Thanks for that info Mohammad.
To be honest, restarting my phone every 12 hours is ok with me. The battery life I'm getting on 4.3 (at least on this build) is miles better than 4.2 and though its slightly annoying, I'm willing to deal with it at present as there is no other impact.
Your script appears a bit beyond me in terms of understanding, so I may look at trying it later down the road.
cheers.

sephstyler said:
Thanks for that info Mohammad.
To be honest, restarting my phone every 12 hours is ok with me. The battery life I'm getting on 4.3 (at least on this build) is miles better than 4.2 and though its slightly annoying, I'm willing to deal with it at present as there is no other impact.
Your script appears a bit beyond me in terms of understanding, so I may look at trying it later down the road.
cheers.
Click to expand...
Click to collapse
I would have expected more people with 4.3 to have commented about this, anyone else having this issue?

sephstyler said:
I would have expected more people with 4.3 to have commented about this, anyone else having this issue?
Click to expand...
Click to collapse
Since seeing this thread, I've kept an eye out for it. I've been on 290 for about 4 days without seeing this problem, not a single reboot in that time. Not sure what makes you guys so special.

xasbo said:
Since seeing this thread, I've kept an eye out for it. I've been on 290 for about 4 days without seeing this problem, not a single reboot in that time. Not sure what makes you guys so special.
Click to expand...
Click to collapse
"special"
exactly, which is why I think there is more to it.
Can you help me with some details? Did you flash an FTF for your .290? or OTA? - Which country/region is your Z1 from?
Rooted? Bootloader unlocked?
thanks in advance

sephstyler said:
"special"
exactly, which is why I think there is more to it.
Can you help me with some details? Did you flash an FTF for your .290? or OTA? - Which country/region is your Z1 from?
Rooted? Bootloader unlocked?
thanks in advance
Click to expand...
Click to collapse
Sure. I have a C6906 sourced from Telus in Canada, but running on AT&T LTE in the US.
I think when I first had the phone, it was 534; I performed two OTA updates to reach 290. I ran 290 for a couple days before digging into flashing, at which point I messed around for a while before flashing 257 generic CA, then OTA'ing to 290. That brings us to today, 100% stock, no root, LB. Probably the only potentially relevant app I've installed since is the Snapdragon BatteryGuru app.
Anything else you can think of?

Actually i've had this problem on stock rom and monx, now I have iHackers2 with LB running for 72 hours and no ram leak, at least not noticible one.
Sent from my C6903 using Tapatalk

xasbo said:
Since seeing this thread, I've kept an eye out for it. I've been on 290 for about 4 days without seeing this problem, not a single reboot in that time. Not sure what makes you guys so special.
Click to expand...
Click to collapse
xasbo said:
Sure. I have a C6906 sourced from Telus in Canada, but running on AT&T LTE in the US.
I think when I first had the phone, it was 534; I performed two OTA updates to reach 290. I ran 290 for a couple days before digging into flashing, at which point I messed around for a while before flashing 257 generic CA, then OTA'ing to 290. That brings us to today, 100% stock, no root, LB. Probably the only potentially relevant app I've installed since is the Snapdragon BatteryGuru app.
Anything else you can think of?
Click to expand...
Click to collapse
You might not have noticed it, but it's probably there. You can use the phone without restarting it, it just starts getting annoying to use.
shteren said:
Actually i've had this problem on stock rom and monx, now I have iHackers2 with LB running for 72 hours and no ram leak, at least not noticible one.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
iHackers2 is based on 290, so if you had it on stock, you have it on iHackers2. A RAM leak is a RAM leak, and it needs to be fixed by Sony.

MohammadAG said:
You might not have noticed it, but it's probably there. You can use the phone without restarting it, it just starts getting annoying to use.
iHackers2 is based on 290, so if you had it on stock, you have it on iHackers2. A RAM leak is a RAM leak, and it needs to be fixed by Sony.
Click to expand...
Click to collapse
well your logic holds true, and yet, i'm 72 hours without restart on iHackers 2 and i can easely clean my ram up to 700mb if needed.
when i was on stock after 12 hours ram whould go down to 200mb and i couldn't clean it no matter what...
more than that the launcher used to go slow in stock once the ram got bloated, but now for days i don't see any slowness in phone and the ram is free...
so i don't know what to say... obviously i'm on stock kernel because i run locked BL, so it shouldn't be different than stock .290 rom.
but it is, perhaps the problem lies somewhere else than the kernel. something in the firmware.

MohammadAG said:
You might not have noticed it, but it's probably there. You can use the phone without restarting it, it just starts getting annoying to use.
Click to expand...
Click to collapse
I have been watching my RAM usage as well and even when I posted last night, I still had the typical 600MB free. I would notice a laggy phone and it simply hasn't happened.
@shteren, did you OTA or flash to stock 290? Maybe not relevant, since you saw it on monx as well, which uses a custom kernel. Or, maybe iHackers changed something in their kernel to fix the problem?

xasbo said:
I have been watching my RAM usage as well and even when I posted last night, I still had the typical 600MB free. I would notice a laggy phone and it simply hasn't happened.
@shteren, did you OTA or flash to stock 290? Maybe not relevant, since you saw it on monx as well, which uses a custom kernel. Or, maybe iHackers changed something in their kernel to fix the problem?
Click to expand...
Click to collapse
Download OS Monitor from thr Play Store. If there are two lines with Android System then you have the leak.
This isn't a kernelspace issue, it's a userspace one.
Sent from my Sony Xperia Z1 using Taptalk

MohammadAG said:
Download OS Monitor from thr Play Store. If there are two lines with Android System then you have the leak.
This isn't a kernelspace issue, it's a userspace one.
Sent from my Sony Xperia Z1 using Taptalk
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just one...
Sent from my C6903 using Tapatalk

MohammadAG said:
Download OS Monitor from thr Play Store. If there are two lines with Android System then you have the leak.
This isn't a kernelspace issue, it's a userspace one.
Sent from my Sony Xperia Z1 using Taptalk
Click to expand...
Click to collapse
Looking for "Android System" is too broad, there's a few process which will be lumped in under that label. However, I only have one system_server process:
Code:
[email protected]:/ $ ps | grep system_server
system 830 338 1155140 224112 ffffffff 00000000 S system_server
[email protected]:/ $

shteren said:
Just one...
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Sort by memory. If there's only one, I'm really stumped
xasbo said:
Looking for "Android System" is too broad, there's a few process which will be lumped in under that label. However, I only have one system_server process:
Code:
[email protected]:/ $ ps | grep system_server
system8303381155140224112ffffffff00000000Ssystem_server
[email protected]:/ $
Click to expand...
Click to collapse
That's odd, I wonder what's triggering this bug then.
Sent from my Sony Xperia Z1 using Taptalk