Database Develop

[Q] Xperia V: Weird behaviour with Cyanogenmod 10.2

Hey, I'm new here, I apologise in advance if I'm posting it at the wrong place. I also searched for similar issues, but found nothing quite like the symptoms I experience.
I have two new Xperia V phones. I unlocked both and installed Cyanogenmod 10.2 on them.
One of them is not doing any problems. The other has the following behaviour: every once in a while, when I leave it untouched for a few hours, it turns itself off. Well, I'm not sure if it's really turned off, but touching or holding the turn on button doesn't do anything. Only after I remove the battery and put it back in place can I turn the phone back on.
I noticed this behaviour happens regardless of whether I leave the phone charged (say, for the night) or it's just lying around for a few hours. I haven't been able to establish any problem pattern (like how much time of inactivity it takes before the problem kicks in).
Could anyone here help with me with my problem or give me pointers on how to further debug it?
Thanks in advance,
alteclanding

Did the problem exist when you run stock firmware?
Sent from my Xperia V using Tapatalk

No, but unfortunately I don't know how relevant it is, as I didn't really use the stock firmware for a long time -- I pretty much installed Cyanogenmod right away (after around 2 days).

alteclanding said:
Hey, I'm new here, I apologise in advance if I'm posting it at the wrong place. I also searched for similar issues, but found nothing quite like the symptoms I experience.
I have two new Xperia V phones. I unlocked both and installed Cyanogenmod 10.2 on them.
One of them is not doing any problems. The other has the following behaviour: every once in a while, when I leave it untouched for a few hours, it turns itself off. Well, I'm not sure if it's really turned off, but touching or holding the turn on button doesn't do anything. Only after I remove the battery and put it back in place can I turn the phone back on.
I noticed this behaviour happens regardless of whether I leave the phone charged (say, for the night) or it's just lying around for a few hours. I haven't been able to establish any problem pattern (like how much time of inactivity it takes before the problem kicks in).
Could anyone here help with me with my problem or give me pointers on how to further debug it?
Thanks in advance,
alteclanding
Click to expand...
Click to collapse
Next time this happens, connect the phone to your computer and see if it's recognized with ADB. If it is, then it's on, which I think is most likely the case, I've seen it happen before; phone goes to sleep and can't wake back up, which doesn't make sense if you installed the exact same ROM on both phones, and are running the same apps, but at least you can check.
If it is on, you can pull a logcat and dmesg with ADB in order to see what's going on, and even reboot the phone without having to take out the battery.

Antiga Prime said:
Next time this happens, connect the phone to your computer and see if it's recognized with ADB. If it is, then it's on, which I think is most likely the case, I've seen it happen before; phone goes to sleep and can't wake back up, which doesn't make sense if you installed the exact same ROM on both phones, and are running the same apps, but at least you can check.
If it is on, you can pull a logcat and dmesg with ADB in order to see what's going on, and even reboot the phone without having to take out the battery.
Click to expand...
Click to collapse
I've been waiting for it to happen again, and today it happened. But connecting it to my computer, I wasn't able to recognise any device with adb. Nothing on lsusb, no kernel messages, phone is completely dead until I take out battery and put it back again.
Is there any way to check logs after the phone has rebooted? Any logs before the last 'crush'?

i've been using tsubasa 10.2 for months and gave me headache for only had 5hrs battery....
it's just only 4days ago i change to this rom using the backup zip option and having back my xperia v battery to more longer battery service...

[Q] Bootloop, software or hardware caused?

Hello, Its been a long time since I don't ask anything on the forum, but in this occasion I haven't found any solution to what's happening to my Xperia Z, I'm gonna do my best to present the issue.
A couple of days ago I updated my Xperia (unlocked bootloader) from Existenz 1.5.5 to the latest 3.0 and the phone was completely fine for 2 days until it started shutting down by itself constantly and with no apparent reason, so I started to get worried, the first thing I did was try and reinstall the ROM thinking that I had some something incorrectly, I has no luck with that, on the contrary the phone died on the middle of the installation and it got bricked. My next step was to try do do everything from scratch, flashing the stock rom 10.5.1.A.0.283 to root it, install recovery and try flashing the Existenz after. I managed to do everything with lots of unwanted shuts downs in the middle but I managed. Unfortunately the phone kept on having the same problem so my last option was to try and use the Sony bridge on my mac to try and make a factory reset but it didn't let me because it detected the unlocked bootloader so I relocked it with flashtool, after that I tried again and it worked, it installed the official stock rom .101 and guess what..... same issue again, when I try to turn the phone on it shows the sony logo and turns off, if I try to turn it on connected to the AC it turns on but if I start playing with the menus and options it disconnects again, ofcourse if I turn it on connected and once it's on I disconnect it it shuts down almost instantly, At first I though the problem could be software, then hardware so I tried to check the battery status in the service app and it said good battery health so now I'm completely lost.., I've found this: http://forum.xda-developers.com/xperia-z/help/hardware-fix-xperia-z-charging-booting-t2760911 but I don't know if thats my case. I was gonna go to a sony store and ask them what could be the problem, but now I'm living in Brazil and it'd take lots of time and money to get ir fixed here.
I really need help here, sorry if I posted on an incorrect place.

I just found a video of someone with the exact same problem, in case in helps: https://www.youtube.com/watch?v=zkvLchJ_0oU
UPDATE: I rooted it, install recovery and once im in recovery it doesn't turn off by itself what tells me that may not be a hardware problem, at least not battery related, all this just makes me feel more confused!!
UPDATE 2: I rebooted the phone to load the recovery again and the battery indication went from 89% 2 minutes ago to 11% this second time, maybe it's hardware after all..

Battery.....
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!

I seriously don't think is the battery, I think it's something related to the energy but I'm not sure what. As I said before the battery went from 89% to 11% quite fast but when it was at 1% it stayed there for hours, if it was the battery wouldn't it had turned off? after it finally turned off I left it charging for about 12 hr and today morning I try to turn it on without it being connected and no luck, it kept shutting down after the Sony logo. Sometimes when I turn it on with the cable connected it loads the OS and I unlock the lockscreen, diconnect the cable and extraneously it stays on just with the battery power, I manage to put the ScreenOff timeout to 30 mins and it stays on all the time, as long as I don't do certain things like opening the camera, phone or sometimes it just randomly turns off from anywhere. I know it's not the rom because I've tried 4 different ones including the official installed by Sony Bridge....
If the issue is software related what could it be?? the bootloader? the bios power management? battery stats? maybe restoring TA backup(because I just relocked the bootloader using the option o flashtool, not flashing the TA backup)?
I'm concerned about buying a battery, installing it and seeing no change as I've read happened to some guys with the same problem.
I really like my phone but after this I'm not so sure i'll buy another Xperia because this has happened to so many people and apparently there's no solution, my phone is out of warranty and I life in a foreign country (Brazil) so you guys are all I have...

Same Problem Here ... Impossible to flash either from fastboot or from CWM or TWRP
Hi, I am having exactly the same problem. I was trying to revert to stock kernel from CM10.2 and was following one of the many guides here on XDA. The phone was not passing the «SONY» Logo, and immediately after such logo it simply went completely black and the phone is off. After two days of trying several things, including Fastboot of Stock ROM, fastboot of different boot.img files including Doomlord, using Sony Bridge for Mac, all of which did not solve the issue, the problem now is that when I try to flash any ROM, the flashing operation begins and then after approx 15 seconds the phone goes black and switches off. The battery is at 82%, so I am quite sure it is not a battery problem.
I am more and more convinced that the internal filesystem (or simply RAM) needs to be formatted at low level from scratch.
The only problem is that I do not know how to do it: how to do LOW LEVEL Formatting of RAM? Any instructions out there?
Any other suggestion?
Thanks

gcecchini said:
Hi, I am having exactly the same problem. I was trying to revert to stock kernel from CM10.2 and was following one of the many guides here on XDA. The phone was not passing the «SONY» Logo, and immediately after such logo it simply went completely black and the phone is off. After two days of trying several things, including Fastboot of Stock ROM, fastboot of different boot.img files including Doomlord, using Sony Bridge for Mac, all of which did not solve the issue, the problem now is that when I try to flash any ROM, the flashing operation begins and then after approx 15 seconds the phone goes black and switches off. The battery is at 82%, so I am quite sure it is not a battery problem.
I am more and more convinced that the internal filesystem (or simply RAM) needs to be formatted at low level from scratch.
The only problem is that I do not know how to do it: how to do LOW LEVEL Formatting of RAM? Any instructions out there?
Any other suggestion?
Thanks
Click to expand...
Click to collapse
It seems like there's no solution and I don't think my battery is broken so I won't try the Hardware Fix since I don't wanna break my phone more than it already is, tomorrow I'll try to go the a Sony service store and see what they think the problem is, since I unlocked my bootloader and relocked after I think they will be able to see this, I think it ain't gonna be a problem because my warranty was void long time ago, and it's 1 year anyhow.... I hope they recognize it's a sony's fault issue and they decide to fix it with no cost, very unlikely but hoping is free gcecchini, i'll keep you updated, also if you find a solution let me know.

Hi Ringox!!! I'm having exact problem as your's.. This all started when I upgraded to 4.4.4 . First it was giving some weird problem like when opening camera , the phone shuts down. Then a time came the device was not charging.. The device boots up when connected to wall charger. But as soon as charger is removed the phone shut's down. Without connecting the charger when I tried to power on, it shows sony logo for 1 second the shut's down. I tried installing every stock rom , custom rom, kernel etc and it didn't solve the problem. I also bought new battery but same problem. I don't think it's software or hardware or battery problem but may be bootloader is corrupted. May be when we flash bootloader ( as in samsung) we may solve this problem. But I cannot find any tutorial an instruction to flash bootloader.
Also from quickstyler thread I can confirm that I have same problem as him, the sony mobile battey test app shows same error battery temperature -30 C . But his hardware fix didn't work either.
By searching for the problem on youtube, xda, google and other sources I can confirm 1000s of people is getting this problem ..
Please developer and member , help us provide solutions and tips what we can do next...

I have news, after one month waiting for Sony to repair my phone they've finally said it can't be fixed and they said the problem is the motherboard which is approximately 130 dollars plus installation, so I decided to park my Xperia and buy a SGS4. Something interesting that happened is that now the phone starts and sounds, just with a black screen all the time with the backlight ON, maybe they fixed something and broke something else, I don't know. If anyone knows a solution to this rather than changing the motherboard I'd appreciate the answer. I wanna fix it to give it to my mother, but I won't be buying any other Sony smartphone ever again, their service is a disgrace and I couldn't be more unsatisfied with them.

Phone keeps rebooting randomly and shuts down when idle for too long (during night)

Hello everyone,
This is my first post on XDA so please forgive me if I'm doing something wrong.
So my story, I got a refurbished unit at Swappa, I updated to the newest version directly (G920TUVU3DOI1) and it was working fine for the first week or so. Then the reboots started happening, I didn't give it too much thought but looked into it anyways.
At first I thought it was a problem with the WiFi and I tried to keep it off for a while, and it did work for a day but again the restarts kept happening, and now with the phone turning off during the night (no apparent loss in battery mind you).
Then I went to rooting and custom kernels.
I installed unikernel v8-0002 through Odin3_v3.10.6 and I tried removing some Samsung apps with TitaniumBackup in case there was some conflict happening but the restarts kept happening.
Then I installed a custom ROM, "XtreStoLite_ROM_v2.4_Deo-Mod-Edition_XXU3COI9_G920-5-F-I-T-W8-K-L-S" to be more specific.
And to my surprise it worked great, no restarts or shutdowns for about 2-3 weeks, it was great!
But then out of the blue the restarts started happening, they started slow, about 2-3 a day.
But after a few days they went to 10-20 and after that 100-200 a day.
Something was definitely wrong. So I installed the original firmware again (G920TUVU3DOI1_G920TTMB3DOI1_G920TUVU3DOI1_HOME) and booted to the stock firmware, restarts kept happening of course (didn't expect them to stop).
So I retreaded my steps and installed multiple other kernels (Unikernel V9, Vindicator, multiple different flavors of them). Also I installed multiple ROMs (Arrow_ROM_v6.0.0, and DN5 - S6 FLAT - EDGE v4 OJ5 - deodex) but nothing seems to work;
I did multiple wipes, storage wipes, cache wipes, factory resets (from GUI and twrp-2.8.7.2-zeroflte) but every time the same thing happens.
I did notice that the phone stutters and freezes, a behavior that I have not experienced before.
I installed CatLog and got multiple log files when the phone restarts but all of them are different and there is no "pattern" to be found (at least in first inspection). I want to upload them but my post count prohibits it.
Please let me know what can I do, I will reply to your questions ASAP so at least I can get some light into what is happening.
Thank you!

I'm in the same boat. Never had a problem before. Received my phone back from Samsung after a screen repair and now, doesnt matter what rom, kernel, patch, it always ends in random reboots. Most often when I'm scrolling or if a page is loading something in the background. It does a lot of hot reboots (not full shutdown and start ups) so its quick but infuriating. Tried everything, slowly losing my patience.
Any idea what it could be? Something related to Knox? Bootloader/Modem?

#3
Hello, I am too having the same problem. Even after a factory reset

phone turns off by itself

Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?

terragady said:
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
Click to expand...
Click to collapse
Honestly, there's not enough information to understand exactly why it's happening. You need to get a logcat in the time before the reboot; unfortunately, logcats get erased during a reboot so it might be a little tricky getting it if the reboot is seemingly random. Someone had posted this as a possible way of getting the log:
"Retrieving the logs is tricky, since the log cache gets erased on reboot. If the phone reboots even while sitting on a charger, try running adb logcat continuously (you will need Android SDK and USB drivers installed and configured on your PC.) When the phone reboots, look at the last several pages in the command prompt window for any errors or abnormalities."
Click to expand...
Click to collapse
Otherwise, it's hard for anyone to help. I'm not much help in actually figuring out the issue, but I know if you can get the log, someone else probably can help.
For more information on logcats: Logcat Tutorial

Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.

terragady said:
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
Click to expand...
Click to collapse
Check in advanced to see if schedule off is on

Nope it's off

Happened to me to on 4.0.2. Rebooted twice a day.
Solution to me was Qualcomm flash back to stock 3.5.1 and uodate from internal to 3.5.4. OTA 4.0.2.
The theard "how to unbrick".
Not one reboot until now in days.

I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?

terragady said:
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
Click to expand...
Click to collapse
It's possible. Not necessarily the reason, but it might be. Either uninstall the app or freeze it using Titanium. Greenify might also work, but that allows the app to start itself up and potentially continue the issue. See if that stops the crashes for a couple of days.

The problem is that it doesn't happen often and only when I quit the game and lock the phone immediately after that. I am not sure if that's a reason though, just guessing because it happens after this last time. I will uninstall this game anyway, it's just time eater

Xiaomi MI A2 turns off when unplugging

Hi.
Today appeared some problems with my A2. When I woke up and unlocked phone it turned off. Yesterday everything worked perfectly fine. I tried like 20 times, everytime the same scenario- turns on, but when I type PIN, home screen is loading, and phone goes down. It may look like bootloop, but its not typical, cuz it goes farther than just booting screen. So I tried to fix, wiped phone, set lang. to Polish, and it dumps again, but I've read somewhere, that it might be language issue, so I wiped it once more and set English. It seemed to be working, but then I unplugged it from my PC (charging only) and it turned off immediately. Worth mentioning is fact, that battery is 92%. What may cause this? Is this some soft problem? Or more like battery issue?
Update: Phone works unplugged, but only on lock screen. Turns down when I unlock.

Ashu14 said:
Hi.
Today appeared some problems with my A2. When I woke up and unlocked phone it turned off. Yesterday everything worked perfectly fine. I tried like 20 times, everytime the same scenario- turns on, but when I type PIN, home screen is loading, and phone goes down. It may look like bootloop, but its not typical, cuz it goes farther than just booting screen. So I tried to fix, wiped phone, set lang. to Polish, and it dumps again, but I've read somewhere, that it might be language issue, so I wiped it once more and set English. It seemed to be working, but then I unplugged it from my PC (charging only) and it turned off immediately. Worth mentioning is fact, that battery is 92%. What may cause this? Is this some soft problem? Or more like battery issue?
Update: Phone works unplugged, but only on lock screen. Turns down when I unlock.
hi i have the same problem with my mi a2. i can turn it on when is on charger but when i want to unlock the screen and to move something on screen is turning off. when i unplug the charger turning off too. do you found solution on your problem ?
Click to expand...
Click to collapse

Hello, I have the same problem. I now have to carry an external battery with me, because plugging it in is the only thing that wakes up my phone. If I don't have a charger, then I have to hold power for 30; seconds to force reset. It's really annoying, causing me to miss calls and alarms. Anyone know of any fixes? Thanks

Hey,
I am facing the exact same problem. Though I had an additional problem. My phone didn't charge when I plugged it in until I restarted it. Factory resedidn't help either.

In both your cases the problem is your wifi even if you dont understand it ...
if you can unlock your phone quickly and toggle off wifi the phone wont reboot or loop
your persist partition is damaged from changing between pie and android 10 ..
look around for a flashable zip to repair your persist ( it does it exist )
or take the long root and use miflash to flash persist by modifying certain files in stock fastboot rom folder
but next time explain your problem better
--- what did you do -- change version ( update or downgrade ) -- did you root -- do you have twrp -- what version of android-- did you return to stock from custom or vice versa --- etc etc etc

KevMetal said:
In both your cases the problem is your wifi even if you dont understand it ...
if you can unlock your phone quickly and toggle off wifi the phone wont reboot or loop
your persist partition is damaged from changing between pie and android 10 ..
look around for a flashable zip to repair your persist ( it does it exist )
or take the long root and use miflash to flash persist by modifying certain files in stock fastboot rom folder
but next time explain your problem better
--- what did you do -- change version ( update or downgrade ) -- did you root -- do you have twrp -- what version of android-- did you return to stock from custom or vice versa --- etc etc etc
Click to expand...
Click to collapse
tried with wifi toggle off but didn't work.
didn't tried persist partition
tried update software but still didn't work.
if there any hardware issue please let me know.