Database Develop

Phone heating up and restarting

My Xperia SP has a problem: when running benchmark software, when updating multiple apps from the store and sometimes when running stock camera app, the screen turns reddish, slowly dims until it turns off, and the phone restarts, getting very hot in the process. From what I see it's not above 43 degrees, but I think that when it locks up the temperature monitor app also freezes so it doesen't exactly record the actual heat.
When the phone cools off, it's good to go, but until then it restarts all over if I try to use it.
I had this problem using Arch Xperia, CM 11, and a few other ROMS. Now I flashed stock 4.3 CE, using Flashtool, and I have the same problem.
The phone was bought second hand, so no warranty.
Can I do anything about it?

I saw this on my phone in the past but only way this happend to me was that:
1. I was on williamskernel (i dont know how it performes to another people but to me its quite unstable)
2. I was on alpha cm12 and that happened to me under load
btw on cm11 and stock for me ist perfectly stable, phone never crashed like that but when i play heavy games like portal then i have 45-55 degrees celsias .
If you have this problem on stock flashed by flashtool from PC i think that it may be a HW problem.

i had this problem in 4.3 .205 stock and other customs roms based on .205 kernel.
Now i am on .207 kernel with archxperia 1.0.5 and i havent experienced something like this.
Also im using undervolt to 1566 to avoid high temperature during gaming.
I think is your ftf , which one are u using?

I downloaded the ftf from here:
http://forum.xda-developers.com/showthread.php?t=2311964
Yesterday, when I posted my problem, I had 12.1.A.1.205_CE1 - JB 4.3
In the mean time, I decided to try 4.1.2 JB and flashed 12.0.A.2.254_CE .
This one seems to have worked fine in the last couple of hours. I tried to run as many apps as possible to determine it to restart, but it just warmed up a little and kept going. So it seems it's ok.
Also, I had an unlocked bootloader and before I flashed 4.1.2 I locked it back again. If that has anything to do with it.
The problem is that it askes for a system update and if I do it, it will probably take me all the way to 4.3, and maybe the same problems. That notification is so annoying

That sounds like a hardware problem. Is your phone in a case? Maybe it's restricting the airflow to the device.

b3cks89 said:
I downloaded the ftf from here:
http://forum.xda-developers.com/showthread.php?t=2311964
Yesterday, when I posted my problem, I had 12.1.A.1.205_CE1 - JB 4.3
Click to expand...
Click to collapse
download 4.3 using flashtool (devices/check updates) and try

Yes, it is in a case. But with 4.1.2. it doesen't seem to have problems anymore so I hope it's a software issue.

Nathan rd said:
download 4.3 using flashtool (devices/check updates) and try
Click to expand...
Click to collapse
Will try this today. It should take me to 207, right? The phone OTA update service gives me an upgrade to 205, which I understand is problem-prone.

205 was alright, I think it was 201 that had problems. Still, it's probably best that you go for the latest firmware, which is 207.

[Q] XT1092 Frequent random reboots after OTA

About a week ago, I received an update to 22.121.1.victara_retgb.retgball.en.GB retgb. Since then, I've been having multiple random reboots every day. ..
I've tried formatting cache, still reboots. Tried running in safe mode to see if it were external apps, still reboots. Tried a factory reset yesterday and downloaded my apps again, still reboots.
Are there more people experiencing these reboots? Is there a way I can rollback the ota (I don't have a backup)?
And another small thing. I noticed how it says GB all over my FW version name. However, I'm Dutch, bought my phone retail in The Netherlands, shouldn't the version be something like nl.NL, or eu.EU ?

Try doing a factory reset, but don't install your apps. If it does not reboot when your apps are not there, it means that one of your apps is causing the reboot. To figure out which app install apps 1 by 1 to see if it reboots. Repeat until you find the app that causes the reboot.
As far as the version GB. Have you flashed any firmware? If not, then GB is fine, it does not change by itself which means you are on the correct firmware.
Sent from my XT1095 using Tapatalk

AGISCI said:
Try doing a factory reset, but don't install your apps. If it does not reboot when your apps are not there, it means that one of your apps is causing the reboot. To figure out which app install apps 1 by 1 to see if it reboots. Repeat until you find the app that causes the reboot.
As far as the version GB. Have you flashed any firmware? If not, then GB is fine, it does not change by itself which means you are on the correct firmware.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I was hoping there would be an easier solution, but I'll do another factory reset this evening and install 1 app per day (if i'm still without crashes). I did sideload the OTA to 5.0 when it became available a couple of months back, but I think that was a link to a french OTA.
I will update this thread when I know more...

So, I've tried several things now...
- Factory Reset with backup restore
- Factory Reset without backup restore and only install Whatsapp
- Factory Reset without backup restore and no apps installed except for pre-installed apps.
In between all resets I also cleared the cache, just to be sure...
But none of all the options have any effect. I had contact with Motorola support and they told me there is absolutely nothing wrong with the update and they've never heard of this before and I should wait for the 5.1 through the official notification and not attempt to flash any other firmware or sideload any other OTA.
The GB firmware is because I returned my device due to a broken headphone input and they probably just switched the phone out with another one which so happened to have GB firmware...
I really hope I can update to 5.1 soon and the issues will be gone as this is not something desirable for retail firmware...

Marshmallow Released

After more than 10 months after release, BLU has promised on delivering the marshmallow update. I just saw the notification today at around 4:00PM CMT.
Currently updating!

9000RPM said:
After more than 10 months after release, BLU has promised on delivering the marshmallow update. I just saw the notification today at around 4:00PM CMT.
Currently updating!
Click to expand...
Click to collapse
Screen Shots Please....

I just updated last night. Everything running smoothly. I had the phone rooted previously but the one click root app got removed in the update process. If anyone has success rooting after the upgrade, I'd love to know about it.

I upgraded this morning and I've been having lots of issues with my installed apps, like Facebook, Messenger, Whatsapp and more, and of course I lost Root which was previously accomplished by KingRoot which doesn't work anymore.
Also I noticed that during the update process, particularly while flashing the firmware, it was flashed using my TWRP recovery and afterwards it got removed.
I'm sure that if I start fresh by performing a factory reset, all will be fluid and in working order, minus TWRP and Root of course, at least for the time being.
All in all, the update to Mashmellow seems to be awesome, some new features.
Cheers!

I'm having issues with the update. It downloads just fine and when I go ahead and try to install...it just spins around on "unzipping" and then proceeds to restart..or turn off for that matter. The phone turned off...I didn't do anything to it just let it sit there for a while and then I saw the charge icon show up (the one you see when the phone is off and charging) at which point I started the phone up. The phone did not update and I can basically repeat the process. There is 4.30 GB of space free and no SD card. What do I do?
EDIT:
So I tried again, kept at it and it eventually worked. Updated just fine but now there are doubles of all folders in the phone. When I plug it into my computer, all the folders (Music, Download etc etc) are showing up twice with the same contents in the each of them...
What...is...going...on?

Was pretty laggy at first. Decided back up my files and do a factory reset. Works much better now.

disChapo said:
Was pretty laggy at first. Decided back up my files and do a factory reset. Works much better now.
Click to expand...
Click to collapse
Yeah, mine is working flawlessly after a factory reset! Much improvement compared to Lollypop!
Anyone found a Root for Marshmellow yet?

Unless Blu changed something other than the interface I'd guess TWRP won't be working on MM anytime soon. It's a problem seen in the Gionee phone and I would expect the same to happen to the Blu. As for root and a custom recovery (although not a great one) you could try following these instructions: https://forum.hovatek.com/thread-15270.html
I've played a bit with the Gionee Marshmallow firmware on my Vivo XL during the past month or so, and one thing that really bugs me is that it seems to be shipping with a kernel that is way older than it should be on an MM release. And the OTA service that is known for leaking info also seemed to still be present in the updated firmware.
Can someone who's got the Blu update check if these two things are the same for the Blu release please? Enter device info in the settings menu and check the Kernel version for me. And, if you guys manage to get root, check if AdupOTA is still lurking in there.

batoussai said:
Can someone who's got the Blu update check if these two things are the same for the Blu release please? Enter device info in the settings menu and check the Kernel version for me.
Click to expand...
Click to collapse
Kernel Version: 3.18.19
Build Number: MRA58k
Custom build version: BLU_V0030UU_V07_GENERICM14-11-2016

Does anybody with TWPR/root upgraded to official 6.0 successfully? What's exact procedure/steps?
I have my Blu Vivo XL with TWRP now, in last (small) OTA update a few months ago, I tried flashing back to original recovery and rom, but still failed OTA.

OTA VS Flash via Odin Update

Hi guys,
Which method is better? OTA update or Odin update? If I do OTA I'd do a factory reset but I still think there'd be 'remnants' of previous OTA especially in this case moving from Nougat to Oreo.
Because I did the OTA update, factory reset but now I'm facing battery draining faster than normal.

Battery draining.........
For one, I prefer a full wipe, none of the update stuff, so Odin would be my method.
Second, Battery draining after recently flashing is normal, You need to allow time for the device to settle. The kernel needs to do alot processes after a flash and normally you dont see decent battery until 24 hours.

dave7802 said:
Battery draining.........
For one, I prefer a full wipe, none of the update stuff, so Odin would be my method.
Second, Battery draining after recently flashing is normal, You need to allow time for the device to settle. The kernel needs to do alot processes after a flash and normally you dont see decent battery until 24 hours.
Click to expand...
Click to collapse
Yeah, I'm flashing the firmware via Odin now. Hopefully that resolves it.
That could be it too, as it was factory reset so it was still 'setting up'.
Thanks

[SOLVED] How to fix the TW Oreo battery calibration issue.

so for some reason upgrading to oreo really messes up the battery calibration for me. at first, everything will be fine, but after a few reboots and using the phone, the battery percentage is everywhere. I'll plug my phone to charge and the percentage will rise as if it were seconds. I love oreo to bits, and I prefer it over nougat obviously. I used Odin to flash a stock rom, and still it's happening. anyone know what we can do to fix this? I know others here have the same problem.
EDIT (09/03/2019):
some people have mentioned ways to try and fix the problem, so I decided to make this a thread to try and find a solution to the calibration issue.
How can I participate?
You can participate by (briefly):
*submitting a solution you have found
*submitting an idea that may potentially work
*testing the fixes or ideas submitted
What else?
*solutions that are submitted are to be tested and confirmed if they work or not.
*ideas can also be tested, but at your own risk. make sure to make a backup of your current rom and storage if you don't want to lose anything.
*also submit what model you have (unless this applies only to the G610F model - we cant tell).
we can do this. I am tired of android nougat (android N doesn't have this issue).
EDIT (14/04/2019)
so, now that our phone actually recieved OneUi, theres no point for this thread android Pie doesn't have this problem, which is fantastic. thanks for those who contributed!
ill keep this thread around in case there are some bois out there who still prefer oreo for whatever odd reason.
but honestly tho, oneui is perfect.
PEACE!!
EDIT 13/05/2019
SOLVED!! (FINALLY)
right now im running oreosama rom, with no issues, no problems at all - i have (accidentally) found the solution to this battery problem!
the solution is very simple - download a stock oreo rom from sammobile or updato, and then flash its bootloader with odin. the battery calibration issue occurs cause the bootloader is still based on nougat. that issue goes away once you upgrade.
there you go folks - happy oreo flashing!!

lor3tz said:
so for some reason upgrading to oreo really messes up the battery calibration for me. at first, everything will be fine, but after a few reboots and using the phone, the battery percentage is everywhere. I'll plug my phone to charge and the percentage will rise as if it were seconds. I love oreo to bits, and I prefer it over nougat obviously. I used Odin to flash a stock rom, and still it's happening. anyone know what we can do to fix this? I know others here have the same problem.
Click to expand...
Click to collapse
I have the same problem after an OTA update.

officially from samsung?

Try to use Battery Calibration app on CHPlay of SuperThomasLab, read instruction and follow that, i am in TW Oreo and my battery is OK although it stills rarely mess up

I have this problem and I don't know why. I have Android 8.1 official

I had the same problem but .. its gone after flashing oreosama rom and in other TW roms that supports USSD CODES (including the stock) I used *#0228# and it worked everything was ok

Can you give more details?
AhmedKhamis67 said:
I had the same problem but .. its gone after flashing oreosama rom and in other TW roms that supports USSD CODES (including the stock) I used *#0228# and it worked everything was ok
Click to expand...
Click to collapse
i could give this a try. im desperate to get my phone fixed lol.

AhmedKhamis67 said:
I had the same problem but .. its gone after flashing oreosama rom and in other TW roms that supports USSD CODES (including the stock) I used *#0228# and it worked everything was ok
Click to expand...
Click to collapse
so I updated the post. anyways, I tried your idea. I downloaded oreosama and used the ussd code. I thought everything was fixed, then suddenly it gave the usual problems. so your solution did not really work. is there any way we could like port the nougat battery files over to oreo?

If you try to delete battery.bin?
Maybe it would help you.

Drain to 0% and charge your phone to 100%. While plugged in, dial *#0228# and press 'Quick Start'. It would be better if you are on stock ROM. Do it 1 or 2 times and you are good to go. Works like charm for me.

do i dial the ussd code once the phone has reached 100%? how do i know if theres a battery calibration issue?

Beytullah61 said:
If you try to delete battery.bin?
Maybe it would help you.
Click to expand...
Click to collapse
somebody test this

lor3tz said:
somebody test this
Click to expand...
Click to collapse
It worked on my phone.

I think you need to replace the battery with new one

Before doing make sure battery is at 100%
1. Go to root/data/system.
2. Delete all the files which have a name that starts with battery.
3. Delete the Dropbox folder.
4. Reboot to TWRP.
5. Go to Wipe -> Advanced Wipe. Choose dalvik and cache partitions and then wipe them.
6. Reboot and check.
For TWRP and root users ..

op post edit~

guys, ive finally fixed the problem. check the OP to see how!

Help, all of your methods are not work on my phone. My phone is charged too quickly to 100% and after restart the battery is draining to 10%.

did you upgrade the bootloader to Oreo?

lor3tz said:
did you upgrade the bootloader to Oreo?
Click to expand...
Click to collapse
Yeah.