Related
Hello all, First, I searched the forums for my answer with no such luck, that being said if Im repeating a question thats been asked I apologize. I have a problem with keeping android stable. I have flashed with different versions of windows several times all with success. I do however, prefer the android system, I find that it runs much better, faster and has better perks. Everytime I flash following the original how to, I run in to a couple similar problems.
The first is when I hit the power (not hold the power) the back light cuts off and the keyguard enables, the screen goes dark all as it should. Depending on the time ( the longer it is the worse it is) when I hit the power key to revive my phone, I often get a white screen, then it waits , then it goes dim, Sometimes If I hit the power button several times it eventually comes back to the key guard option, but others I have to remove the battery and reboot. This is the major problem, as I cant use my phone when I need it. This problem seems to get worse the farther it gets away from the flash date, e.g..,, after a brand new flash it works pretty good and then it goes downhill from there.
Second, it seems to lock up when I let it charge overnight, not always (but most of the time) I get up, click the power button to revive the phone and I have a white screen before me that is frozen solid. This like the previous problem seems to be linked to the distance from the last flash.
I hope that its something Im doing wrong, as Im currently using wmobile 6.5 and since Ive had a taste of the droid os, my wm phone is just disappointing. And as I was unsuccessful in finding a post that adequately describes my problem ,Im hoping that there is a way around this .
I have tried, Incubus Superfroyo, Wrym warm donut, and Cyanogens build. Im sure Ive tried others, they just escape me, I was re-flashing daily until I went back to windows. I truly hope someone out there has encountered what I have and has a solution. thank you all for what you do, these forums have been extremely valuable and helpful.
Sounds like you have the wrong panel type selected. Is it set to auto? if it is, try setting it to 2 instead. That cleared up the problem for me.
Tried all panels all have the same problem.
Well thanks for all the many replies. I give Ive tried everything on this site and m android is still really glitchy. Guess it will be windows until I get perhaps a phone capable of running android smoothly.
What kind of phone do you have?
Sent from my HTC Vision using XDA App
do you have an SD card you can try to boot from and share your settings?
What we need to know is which kernel you're using, or an image of the kernel you currently have. Also, we need to know which radio version you're using, as this can have detremental effects on stability as well.
Personally, I have been using radio version 1.70.19.09, which seems to be the most stable with kernel .25 IMHO.
I have also "personalized" ThoughtlessKyle's "Fat-Free Froyo", adding/removing apps that I need or don't use respectively (navigation, QQPlayer, Pandora, etc.).
Currently, I think I might be one of the only people not experiencing any issues with this phone running Android 2.2.1. I do get the occasional "hang" (I wait for it to finish what it's doing instead of force close), but that usually has something to do with network coverage or an app requesting something from an unopened port.
Old phone, new OS and runs smooth as could be expected.
Next for me will be the HTC HD2 (if I get one at the right price, the tilt was free)...
I know, I know that MANY PEOPLE THINK OF THE WAKE UP WHITE JIBBERISH SCREEN as NEVER WORKING.
PoXFreak said:
What we need to know is which kernel you're using, or an image of the kernel you currently have. Also, we need to know which radio version you're using, as this can have detremental effects on stability as well.
Personally, I have been using radio version 1.70.19.09, which seems to be the most stable with kernel .25 IMHO.
I have also "personalized" ThoughtlessKyle's "Fat-Free Froyo", adding/removing apps that I need or don't use respectively (navigation, QQPlayer, Pandora, etc.).
Currently, I think I might be one of the only people not experiencing any issues with this phone running Android 2.2.1. I do get the occasional "hang" (I wait for it to finish what it's doing instead of force close), but that usually has something to do with network coverage or an app requesting something from an unopened port.
Old phone, new OS and runs smooth as could be expected.
Next for me will be the HTC HD2 (if I get one at the right price, the tilt was free)...
Click to expand...
Click to collapse
Ill try that combination and post my results. The latest I tried was
Scoot CyanogenMod 6.1.2 RLS6 with 2.6.32 still no joy, white screen crashes and hang ups. and it seems progressively worse the longer the rom is on the phone. To whomever asked what phone I have, its the at&t tilt II
srlebonv said:
Ill try that combination and post my results. The latest I tried was
Scoot CyanogenMod 6.1.2 RLS6 with 2.6.32 still no joy, white screen crashes and hang ups. and it seems progressively worse the longer the rom is on the phone. To whomever asked what phone I have, its the at&t tilt II
Click to expand...
Click to collapse
I can't help you regarding panel selection but, please have Radio ROM version 1.65 or higher. And do give my fresh foryo a go with 2.6.25 kernel (everything is there in the thread on how to use it with 2.6.25 kernel).
the WHITE GLITCHY SCREEN IS THE PROBLEM WITH ANDROID DRIVERS. Install with Data on SD Card often causes lockups / force closes.
I am using panel type 1 and white glitchy screen stays for like half of a second and next moment I get a nice clean keylock screen. I don't know but its like 20th time I am explaining the problem related to LCD
Change Panel Type, Get a compatible Radio version (1.65.x or HIGHER)
You say that often install with data on the sd card causes lock ups and freezes. Can you explain further what you mean ?
dark_prince said:
I can't help you regarding panel selection but, please have Radio ROM version 1.65 or higher. And do give my fresh foryo a go with 2.6.25 kernel (everything is there in the thread on how to use it with 2.6.25 kernel).
the WHITE GLITCHY SCREEN IS THE PROBLEM WITH ANDROID DRIVERS. Install with Data on SD Card often causes lockups / force closes.
I am using panel type 1 and white glitchy screen stays for like half of a second and next moment I get a nice clean keylock screen. I don't know but its like 20th time I am explaining the problem related to LCD
Change Panel Type, Get a compatible Radio version (1.65.x or HIGHER)
Click to expand...
Click to collapse
Ok, so I installed your version of froyo, the accompanying 2.6.25, the radio that you use. For the most part the hanging up is fixed. Now the second problem is still in place. Sometimes when Its been in hibernation(or whatever you would call when you hit the power button once ) when I attempt to refresh my phone (hitting the power button once) nothing happens, the green light is still blinking at the top but the screen stays blank, normally have to remove the battery and restart to get back to using the phone. Is this a sleep setting? or is this something Ive done wrong during the installation.
Hey guys, i need some advise here!
For weeks, i anxiously waited for the mailman to bring my my GNex and for a few days im very happy with it. Unfortunatly, the major plus of android, it never freezes, isnt true for my brand spanking new Gnex!
Seeming randomly, the phone freezes, refusing all input from the screen and the On/Off button. This happens about every 20 hrs.
Ususally i advise people with this problem to exchange their phone with a different one, but im afraid i wont get a stock 'yakju' build back in return, so want to try to fix (or at least determine) the problem first.
Can you guys give me some tips on how to get to the bottom of this?
Thanks in advance!
Info:
Model: Galaxy Nexus (GSM)
Android version: 4.0.1
Smalbandversion: I9250XXKK1
Kernel: [email protected] #1
Build: ITL41F (yakju)
And again, it's all stock
...
i had a lot of problems with the 4.0.1 fw, have you tried updating the phone to 4.0.2 it solves a lot of bugs!
I tried to update the phone through the system update menu in the settings, but it listed my phone as 'up to date'. I find this is odd, since i have a Nexus ánd the Google build
Is there a way of updating the phone without a lot of hassle?
I looked into it, in the Netherlands the 4.0.2 update should roll out in a few days. If it isn't, I'm going to flash it myself! Were your problems with 4.0.1 similar to mine e.g. crashes and freezes?
Sent from my Galaxy Nexus using XDA App
In my experience most of the time when that happened was caused by 3rd party apps that weren't ics optimized.
Sent from my Galaxy Nexus using XDA App
Well freezes and crashes maybe, but the whole phone unresponsive? Isn't there a try/catch somewhere which prevents this kind of 'dirty code' to crash the whole OS, anyway there should be.
Also, ( I forgot to mention this in #1) the phone reboots sometimes while its active as well as when its idle. The rebooting is always paired with a loud *click*
Sent from my Galaxy Nexus using XDA App
Same problem
Panatella said:
Also, ( I forgot to mention this in #1) the phone reboots sometimes while its active as well as when its idle. The rebooting is always paired with a loud *click*
Click to expand...
Click to collapse
That exact thing happened to me yesterday as well (running 4.0.1). I pulled down the notification bar, clicked on the email notification, and when the notifybar started collapsing again, the animation stopped, sound was caught in a loop, and two seconds later my phone rebootet with a clicking sound (I hope that it was just the speaker reacting strangely to the sudden signal loss...!)
The same day, the Nexus kind of crashed while I was streaming internet radio to my bluetooth speaker. The music kept on playing fine, but I wasn't able to turn on the screen. Even holding the vol+/- and power buttons only shut the phone down, but I couldn't restart before I removed the battery.
I really hope this is gonna be fixed with the 4.0.2 / 4.0.3 firmwares. This thing is crashing a little too often right now, for my taste
I'm getting the same problems as noted above. I've just picked up the nexus to move away from Apple's iPhones, but I'm left wondering I've made a serious mistake in doing so. An added problem is that the crash has also occurred when I've been recharging the battery while asleep- so the alarm I set did wake me.
Honestly, it's an unreliable product. I'm a customer, not a Samsung lab rat.
Got the same issue. 2 crashes in 4 days. Not a huge problem for me yet, but 4.0.3 better fix it.
Well most of my problems went away when i updated my phone. You should definitely try to update. Personalty I went straight for 4.0.3. The best ROM i've tested is definitely Android Open Kang Project :http://rootzwiki.com/topic/11455-rom-android-open-kang-project-maguro-build-13/
Everything just went so smooth and bugfree as far as i can tell. And i love the quick setting he put in notification bar.
You can see how to unlock your phone here using the gn toolkit :
http://forum.xda-developers.com/showthread.php?t=1392310
I had those kinds of crashes, too. My phone would crash maybe once every 3-4 hours on 4.0.1... doing anything. Whether it be idle, with no extra services (factory reset), or while composing messages. Anything would do it.
Anyway, I rooted the phone and I've been on Bigxie's ROM since V1 (AOSP 4.0.3) and the issue stopped, for the most part, except for an idle reboot every 18-28hrs. Suspecting it was kernel related, I swapped out the Apex kernel and threw on Franco's... since then, my phone can run for almost two days (of moderate usage) without a charge.
Any of you guys enabled 'force 2d hardware acceleration'? I don't know how relevant it is, but all my problems went away when I stopped to use this function.
Sent from my Galaxy Nexus using XDA App
Uv'ing too low can crashes also.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
Well this is exactly what is happening to me on my phone, it reboots every 2 days or so. sometimes it becomes completely unresponsive, the keyboard doesnt open up or of it does, it doesnt accept any input
even the settings page starts crashing, i dont know what is going on
it works ok otherwise but this crashing and becoming unresponsive is really driving me crazy. i have 4.0.1 as i am in the UK and since they are not releasing 4.0.3 for such a long time here, it means the fixes available in it is not really for stability and maybe they are for LTE version available in the US
Also, I dont have the 2d acceleration checked off already, so not sure what else to do to fix it. should i return the phone???
dhruvraj said:
Well this is exactly what is happening to me on my phone, it reboots every 2 days or so. sometimes it becomes completely unresponsive, the keyboard doesnt open up or of it does, it doesnt accept any input
even the settings page starts crashing, i dont know what is going on
it works ok otherwise but this crashing and becoming unresponsive is really driving me crazy. i have 4.0.1 as i am in the UK and since they are not releasing 4.0.3 for such a long time here, it means the fixes available in it is not really for stability and maybe they are for LTE version available in the US
Also, I dont have the 2d acceleration checked off already, so not sure what else to do to fix it. should i return the phone???
Click to expand...
Click to collapse
U sure it's not a software u installed recently? For me changing back to the stock music player fixed the random crashing.
In general, I can say some apps are not stable at all.
I experience random crashes too, although they coincide with the sudden loss of signal, as described in these threads:
http://forum.xda-developers.com/showthread.php?t=1390816
http://forum.xda-developers.com/showthread.php?t=1387943
http://forum.xda-developers.com/showthread.php?p=20816554
I have started to make some logs to try to identify the cause of this problem. I use Log Collector for making a log and No Signal Alert to obtain a time stamp when the signal drops. What I see in the logs is that just before the signal drops I notice an entry in the log something like "process:com.lookout has died". Could this have something to do with the Lookout app I have installed or is it just coincidence that the app and a certain Android process have the same name?
By the way, does anybody know if there are websites or people who can analyze the logs I have created? Most of the content is mumbo jumbo to me and a knowledgeable person might be able to shed some more light on what happens inside the phone and what might trigger this problem.
I just upgraded to 4.0.2 on Thursday, but the problem persists.
Android version 4.0.2
Baseband Version: I9250XXKK6
Kernel Version: 3.0.8-gaaa2611
[email protected]#1
Build Number: ICL53F
ICS stock; non-rooted
Well i guess you tried already to remove the lookout app right?
My GSM Nexus with stock 4.02 (unrooted) freezes randomly too.
When it occurs i cannot switch the screen on using the power button. Only thing that helps in this state is pulling the battery.
Iam starting to get extremely annoyed by Google/Android because my previous smartphone the Nexus One was also buggy ever since the Gingerbread update while beeing perfect with Froyo.
It's definately my last Android device if this will not be fixed with 4.03.
The phones are way too expensive to be a happy participant of a perpetual Google beta.
b4cksl4sh said:
My GSM Nexus with stock 4.02 (unrooted) freezes randomly too.
When it occurs i cannot switch the screen on using the power button. Only thing that helps in this state is pulling the battery.
Iam starting to get extremely annoyed by Google/Android because my previous smartphone the Nexus One was also buggy ever since the Gingerbread update while beeing perfect with Froyo.
It's definately my last Android device if this will not be fixed with 4.03.
The phones are way too expensive to be a happy participant of a perpetual Google beta.
Click to expand...
Click to collapse
Are you sure it's the OS not some buggy/incompatible apps? I've had the phone since launch and it never froze even once. Stock 4.02 too.
And you should try out different OS. Then you will know what suits you.
Hi,
I recently bought a Galaxy Nexus and rooted it right then and there. A couple of weeks later it went into the bootloop (disease) and I had to restore my phone from scratch (loosing all my SD card stuff as well ). So I decided to go with AOKP M4.
Again a couple of weeks later AOKP just freezes while I was trying to access Maps. No buttons work and the screen stays ON. Had to pull out the battery to bring the phone back to life.
This time I said, let's go for ARHD 3.0... all works fine and I flash to ARHD 4.0 with complete superwipe. Then last night it freezes again when I was trying to access GTalk. Same thing, had to pull the battery out to bring it back to life.
Now I'm wondering if there's a problem with the GAPPS on the GNex? Or there's something else brewing in the background while I carry on my daily tasks. The phone is great, but this freezing is making me go crazy.
If you guys have had similar issues before, and have found any solutions to those, I'd appreciate your help in that.
Thanks.
could be one of your apps
I had a few lockups on stock 4.0.1 when I first got my phone, but after it updated to 4.0.4, and my subsequent move to custom ROMs I haven't had any issues with my phone freezing.
IINexusII said:
could be one of your apps
Click to expand...
Click to collapse
This. Were there any shared circumstances between your lockups? I noticed that my phone lockups on 4.0.1 all occurred under the following circumstances: I was listening to music and writing a text message when a new message was received. Every time.
I definitely haven't had any freezes like that so far for the life of my 3 months. It certainly sounds like something unique with your setup is following you around. An app most likely.
Hmmm ... thanks for your help. I have seen the phone freeze twice in two days. Battery pull restores it every time however.
I don't have anything installed which plays around with my settings (ex: setcpu etc.) Except Tasker!
I can try disabling the app for a week to root cause it!
Thanks.
Sent from my Galaxy Nexus using Tapatalk 2
I tried to google any related threads to the symptom that my N7 2013 shows, but so far couldn't find any. So I decided to start a new thread to see if I'm the only one in this.
As the thread title suggests, the screen freezes randomly and comes back to life after a few seconds later. It doesn't seem to be happening continuously, but the interval between one and the next one should be something like half an hour, give or take. Funny thing is, when it happens, it does recognize all the inputs made on the screen while frozen and once the screen starts responding again, everything I have done in the meantime appears on it afterwards such as typing, swiping, etc.
I suspect it started happening after I installed the newest firmware, JLS36I, but can't be sure as I have received in the fairly early stage of rollout--pretty much on the same day Google started rolling it out, which was just a few days after I got my N7 2013.
I've experienced pretty much the exact same issue on mine, build JSS15R, not sure why though?
This happens occasionally on my Nexus 4, running CM10.2...ive read that its an issue with 4.3 all together.
i don't see a 30 min window like you experience. mine is about 10 seconds.
Just loaded last nights update and we'll see if it continues.
On my N7; ive never had it happen.
racenrich said:
This happens occasionally on my Nexus 4, running CM10.2...ive read that its an issue with 4.3 all together.
i don't see a 30 min window like you experience. mine is about 10 seconds.
Just loaded last nights update and we'll see if it continues.
On my N7; ive never had it happen.
Click to expand...
Click to collapse
Didn't know it's a known issue with Android 4.3. But it's somewhat odd that I never had such problems with Nexus 4 and Nexus 7 2012 although both are on 4.3. And it seems I was a bit ambiguous or misleading with the description. Mine is also about a few seconds, between five to ten second each, but it seems like it happens every half an hour if I use the device continuously. Is it somewhat similar to your N4?
iam_emailer said:
I tried to google any related threads to the symptom that my N7 2013 shows, but so far couldn't find any. So I decided to start a new thread to see if I'm the only one in this.
As the thread title suggests, the screen freezes randomly and comes back to life after a few seconds later. It doesn't seem to be happening continuously, but the interval between one and the next one should be something like half an hour, give or take. Funny thing is, when it happens, it does recognize all the inputs made on the screen while frozen and once the screen starts responding again, everything I have done in the meantime appears on it afterwards such as typing, swiping, etc.
I suspect it started happening after I installed the newest firmware, JLS36I, but can't be sure as I have received in the fairly early stage of rollout--pretty much on the same day Google started rolling it out, which was just a few days after I got my N7 2013.
Click to expand...
Click to collapse
I have the exact problem... I did the touch screen test with no problem.. I would say not hardware issue? Seems like the proccesor freze will trying to load something...
Same problem
I have the same problem also ... input text, playing game ... one day have around 2 time screen freezing ~ any1 have the solution ?
It seems like you are not alone. Mine is acting just the same. After a continuous gaming there would be this weird frozen screen which would magically turn back to normal and not happening again after maybe around an hour.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Me too. Not frequently but from time to time. Especially when I lay the device down .... Its useless sometimes. I can't believe Google can't fix this. I'm running 15r
Sent from my Nexus 7 using Tapatalk 4
I experience the same thing about once for every hour of use. The screen will freeze for about 5 seconds, although the power button is able to turn off the screen the device is otherwise unresponsive.
This was happening in every rom, stock or otherwise for me and I was about to return it then I flashed v10 of Paranoid Android and the problem hasn't reoccurred in 2 days so far. Hoping it stays that way.
Same problem here...
It's the device hanging while it performs an IO operation- the storage on the Nexus 7 isn't particularly fast, though it is faster than the last-gen N7 which was about a million times worse for random device freezes than this model.
Same problem here, was thinking of flashing CM to see if it was any better.
Same issue here, but i notice this today, it was working fine the last couple of weeks after the last update
Well, I had the 6 Pro for about 36 hours. It kept rebooting randomly, even after a factory reset, so it's going back for an exchange.
Has anyone else had this issue?
skyman631 said:
Well, I had the 6 Pro for about 36 hours. It kept rebooting randomly, even after a factory reset, so it's going back for an exchange.
Has anyone else had this issue?
Click to expand...
Click to collapse
No definately not, here the worst I have experienced is some app crashes, they probably aint android 12 ready, and some pretty big lag moments
I don't have any issues. Do you have the November update yet?
For some strange reason, I noticed exactly this aswell (one time, this morning). I was working out and my phone laid on the table, when I saw it lit up because it restarted for no reason.
I guess it's a software bug.
And no, there was no automatic system update - I checked, I'm still running the old version.
copong said:
I don't have any issues. Do you have the November update yet?
Click to expand...
Click to collapse
Is there a bugfix list of any sort about the most recent sytsem update?
I tried to find one, but as of now I have been unsuccessful.
No, nothing at all either. Mine also installed silently at some point. I recall a notification asked for a reboot yesterday morning.
No, not had one random reboot since I got it on Tuesday.
Nothing here either. Good luck!
copong said:
I don't have any issues. Do you have the November update yet?
Click to expand...
Click to collapse
I had the November update and all apps had been updated as well. It would freeze and then reboot.
I did a factory reset and did not restore any of my apps, just ran it with the factory apps, and it still did it. Since no one else is having the issue, I'm feeling confident it was a bad unit. I had the 128 gb version.
It's back to the pixel 5 for another week or so. I had to exchange that after I got it too because of a bad proximity sensor. Either I just have really bad luck or Google needs to tweak their quality control department.
Weird unexplainable OS crashes like that are usually due to faulty hardware, potentially RAM
If you're having issues, do yourself a favor and keep an itemized list (on your device, word doc on pc, somewhere) and notate the following for each occurrence:
-date / time
-the fault (self reboot, major lag, over heated, fast battery discharge, etc.)
-what you had to do to clear it (rebooted, closed app, powered off/on, etc.)
When talking with Google about a replacement, having THIS information ready to read off will make it extremely hard from them to give you any grief about you needing a warranty replacement.
An itemized list of faults is MUCH better evidence that you need a replacement than "well, it rebooted a few times last month"
copong said:
Weird unexplainable OS crashes like that are usually due to faulty hardware, potentially RAM
Click to expand...
Click to collapse
I am inclined to agree here, but my years of working with Windows and Android incl. rooting and using custom roms and kernels want to disagree here. There can be half a gazillion software based reasons for an OS crash, especially with a buggy release like Android 12. Not sure if you participated the beta, but it reminded me of Windows 11. There was a buggy beta build with about 100 bugs, they fixed 20, called it a day and released it. Now we new P6 owners can play beta testers Volume 2 for Google.
One very important thing here is also: Did you guys set up your phone "clean" or did you copy over your old phone by cable or did you use backup?
Any of these things can cause issues.
I, for example, used a cable to transfer all file and apps from my P4 XL to my P6 Pro. It's possible that this is the rootcause for some issues, or maybe it's not. Maybe there are even problems that occur only if you transfer your files from specific phone models to this one, you never know.
Morgrain said:
I am inclined to agree here, but my years of working with Windows and Android incl. rooting and using custom roms and kernels want to disagree here. There can be half a gazillion software based reasons for an OS crash, especially with a buggy release like Android 12. Not sure if you participated the beta, but it reminded me of Windows 11. There was a buggy beta build with about 100 bugs, they fixed 20, called it a day and released it. Now we new P6 owners can play beta testers Volume 2 for Google.
Click to expand...
Click to collapse
Sure, but the OP stated the crashes are happening right after a factory reset, and anecdotal evidence on this thread suggests it's not widespread. It does point to some sort of hardware problem.
I'm having exactly the same issue!
I got the phone today and booted it up for the first time. I selected my language and as soon as I pressed get started it froze, then got stuck in a bootloop. I fixed that by factory resetting from within recovery.
Once I'd gotten through the setup it crashed again when I clicked on the apps button in the optional setup. Because of this I factory reset and set the phone up for a third time.
Third time I got through setup with know issues but the phone freezes/reboots roughly once every two hours. I've been searching all day to see if anyone else has mentioned this issue.
I guess this phone is going in for replacement. Does anyone happen to know how long that takes/ if I'm going to be without a device for long?
They told me 3-5 business days to get a replacement. I expect mine early next week.
skyman631 said:
They told me 3-5 business days to get a replacement. I expect mine early next week.
Click to expand...
Click to collapse
Do you have to send the old device back first?
skyman631 said:
Well, I had the 6 Pro for about 36 hours. It kept rebooting randomly, even after a factory reset, so it's going back for an exchange.
Has anyone else had this issue?
Click to expand...
Click to collapse
I just had 3 random reboots today. Phone just laid on the side of my table on my laptop, doing nothing. It was in the span of probably ~10 minutes each reboot. A strange observation I made - now that I removed my phone from the back of my laptop and laid it directly on the table, no more reboots. Maybe it's a coincidence, maybe it has something to do with the magnets of my Laptop (has quite a lot inside). Not sure what to make of this. It kinda feels like a software buggy-thing, but it's odd that it sometimes just comees and goes. It also only appears to be in absolute idle. I had my phone working yesterday for about 12 hours, incl. using it constantly with navigation, and it never faltered for once. That's why I'd say it's a software thingy, if it had something to do with hardware, it would reboot/fail when under load. But it doesn't.
Had 4 total reboots as of now (had the phone since 27.10).
First reboot was yesterday (28.10) morning when working out, phone laid idle around, booted up.
And now again 3 reboots, morning, laid around, did nothing.
So I've had probably a dozen in two days. I take my phone out of my pocket and attempt a fingerprint unlock only to be told that my PIN is required after a restart. At first I wasn't sure if it was actually rebooting until last night. It prompted me for my pin and upon entering it, the screen locked up for about 20 seconds and it rebooted.
This morning I woke up and was yet again greeted with the "PIN required after restart" and less than 20 minutes later it was the same thing. Only once hav I witnessed the "G" boot animation, but everytime I see my UI loading. So I'm not sure if it's always a full reboot or some times it's just the UI crashing. Everything on my device is stock.
cloudraker said:
So I've had probably a dozen in two days. I take my phone out of my pocket and attempt a fingerprint unlock only to be told that my PIN is required after a restart. At first I wasn't sure if it was actually rebooting until last night. It prompted me for my pin and upon entering it, the screen locked up for about 20 seconds and it rebooted.
This morning I woke up and was yet again greeted with the "PIN required after restart" and less than 20 minutes later it was the same thing. Only once hav I witnessed the "G" boot animation, but everytime I see my UI loading. So I'm not sure if it's always a full reboot or some times it's just the UI crashing. Everything on my device is stock.
Click to expand...
Click to collapse
Did you transfer your old phone over with a cable, or backup, or did you start "fresh"?
Maybe we can narrow it down if it's software or hardware problem.
Morgrain said:
Did you transfer your old phone over with a cable, or backup, or did you start "fresh"?
Maybe we can narrow it down if it's software or hardware problem.
Click to expand...
Click to collapse
I did a partial transfer. I was coming from an iphone 12 so I transferred photos and contacts only. And I transferred via cable.