Related
Hey guys i just recently flashed/hacked my g1 for the first time. i went from 1.5 to 4.1.99 cyanogenmod then updated to 4.2.6. i noticed i had lots of force closes. i was trying to do a downgrade to 4.2.5 to see if it fixed the problem but i was lazy to go all the way back to RC29. So this morning i boot into recovery mode (recovery-RA-v.1.2.3.img) hit the wipe data/factory reset. BAM! skipped all the gmail activation. Turn on wifi and activate my gmail account. No MORE force closes! BTW i am on AT&T with no data plan. Hopes this helps any questions just email me [email protected]
I think that may have to do with the fact tha tyou skipped a lot in between, you went from 4.1.99 to 4.2.6, I went from 4.2.5 to 4.2.6 with no problems
is it really necessary to flash so many outdated updates just to flash the latest? I just came from Dwangs1.13 and no problems so far..so many people talk about the instability of this rom that its insane.
But back to the point made earlier...i dont remember reading that flashing from previous CM versions was a requirement...
oneG said:
is it really necessary to flash so many outdated updates just to flash the latest? I just came from Dwangs1.13 and no problems so far..so many people talk about the instability of this rom that its insane.
But back to the point made earlier...i dont remember reading that flashing from previous CM versions was a requirement...
Click to expand...
Click to collapse
It's not a requirement. I have flashed the HTC image, and then directly flashed 4.2.6, without having to flash 4.1999, or any other ones before 4.2.6 and I have had no problems. I do this all the time because I jump from CM to Hero/Sense roms
Yeppers
I am with Tazz there. After bricking my phone (totally my fault), I went from stock to Rc29, to the htc-dev image, and straight to 4.2.6, with no problems. I have had force close issues in the past that were fixed with a combination of fix_permissions and reinstallation.
I had a lot of force closes and an extremely slow device with cyanogen.
By wipping, deleting, and recreating the 2 partitions (FAT32 and ext3) on my SD, all at once, I got it running right again.
Since then it's a pleasure to use.
Fascinating.. :O
Never heard of a wipe :O
Oh come on people..
Hello all;
I hope that this post is in the right place. The fix are for a problem that's been happening after you update to 3.1 when your tablet gets stuck in a connecting loop and never actually gets connected.
I searched for a while for the wifi loop fix and couldnt find anything (its probably somewhere already here but this should make it easier for noobs to find), so I called Acer and the lady was helpful and got me the solution, unfortunately she told me that this might happen again but the fix is not much of a headache and hopefully a patch will come soon.
Here is the Fix (By the way, you will not lose any data):
1) Once the tab is on, press that tiny reset button (I used a staple) and let it restart.
2) Once your tab starts up again, simply repeat step 1, apparently you have to do it TWICE in a roll.
That's it, reset your device twice through that tiny reset button and should work most of the time. No need for a factory reset.
My tablet is rooted and encrypted and it worked fine.
Im up and running again and hope you will be too!
EDIT: If it works for you, feel free to post here and let others know.
ZuzOnline
If that doesn't work try this (Some people said it did the trick)
lostsoul3471 said:
So after running into this problem myself i was going to start looking for said file and realized, no root explorer and no super manager installed (also has root level file managment) i had no way to easily pull the file out.
If nothing else, always and i mean always pick up terminal and busybox for any android device. You don't have to be a linux geek to use it, you just need to know a couple to get by.
Code:
$ su
# cd /data/misc/dhcp
# rm dhcpd-wlan0.lease
(Also works in adb shell)
That should clear the offending file to get you up and running. I would love to know if the permission fix does the trick as i travel alot and run into this more times than not between phone tethering, hotel and restaurant wifi spots. My list of saved available connections starts rivaling a teen's ipod at times.
Click to expand...
Click to collapse
This did not work on my A500. Nothing worked except a factory reset. Now re-installing all my apps. I'm NOT happy. But Acer gave me a choice between factory reset and shipping the damn thing to TX.
I'm going on vacation in a week. I want my tablet with me, so the reset was the only option. My tab is not rooted, and worked for six days after the 3.1 update. Then suddenly (maybe because I power off) the wifi got into the endless loop.
You would think that Acer TESTED this before rolling it out????
P.S. The 2nd level Acer support admitted that this double reset only works for some. They don't have any idea why.
Worked for me.
I had to do a triple reset, but it got me up and running! Thanks!
Thanks for the information. The reset twice worked perfect for me.
zuzonline said:
If that doesn't work try this (Some people said it did the trick)
Click to expand...
Click to collapse
The instruction in post #2 has worked everytime for me.. i've done it at least a dozen times.. no reboot required. Just have to go back to wifi settings and click connect again.
Soft reset did not work for me. Im not rooted so I could not del file. Had to do factory reset. Pretty messed up.
Sent from my A500 using XDA Premium App
I have deleted the dhcp.lease file and it works great now
Official but rooted 3.1
Okay, I have honestly searched everywhere - Google, the xda forums, other forums and I still can't find something to help me with this strange problem I have.
PAST SITUATION
I installed TyphooN CyanogenMod ROM v3.5.8 around a month ago and I used it with no major problems (few android.acore repeated force closes that was dealt with by re-installation). During this time, I could power the phone off and power it on with no problems.
PRESENT SITUATION
This is where things go wrong. Recently, I decided to install TyphooN CyanogenMod ROMv3.8.5 (the latest one) by booting into MGDLR, doing a factory reset, wiping the system and dalvik caches and then installing the new 3.8.5 zip file. It installed properly and I booted into Android and was enjoying the new improvements and bug fixes. I had no problems until everything started force closing suddenly so I decided maybe a reset would fix it. AND THIS IS WHAT THE PROBLEM IS It boots to the Android Logo and stops there. I waited for 30 mins but it was still stuck at the Android logo and no matter how many times I took the battery out and put it back in and rebooted it, it was still stuck at the Android logo.
HOWEVER when I did a hard reset and wiped the system and dalvik caches and installed it again, it installed fine and booted into the system. When I tried to power it off and power it on again, the same problem happened where it was stuck on the android logo.
WHAT I TRIED TO FIX IT
1) A clean installtion, did a task 29 and installed everything again. Same problem happens.
2) I did a hard reset (wiped system and dalvik caches as well) AND THIS TIME I installed the previous version I was using with no problems (v3.5.8) and I had the same problem! Even with that version it still gets stuck on the Android logo screen.
I can use the ROM perfectly and my phone works fine, but if ever I need to reboot my phone for any issue it won't start up again and gets stuck on the android logo. I have to do a hard reset and re installation for it to work again but that means all my data, files and messages will be lost each time. So you can see the inconvenience I'm facing.
WHAT I THINK IS THE PROBLEM
1) I'm using a fairly old version of ClockworkMod Recovery. That is version 3.0.2.5 (150MB with 5MB Cache as per Typhoon's Requirements). Is this the problem?
2) I didn't remove the SIM and SD card during the entire flashing/reinstallation process. Could this be it?
Should I do a clean installation (task29) and install the previous ROM version I used with no problems and see if the problem still persists or if its only since I installed the new ROM version first?
Thanks for your help. And also I'm sorry I can't post this on the Typhoon ROM thread since I still don't have 10 posts.
did you get things sorted?:cyclops:
Well not yet. I am working on it. Does anyone have a download link to the latest version of ClockworkMod Recovery with 150MB and 5MB cache? I tried the HD2Toolkit and it just doesn't work for me, I plugged in my USB, it indicated USB Debugging was on and meh, it didn't click.
Anyways, I'm going to try task29ing the phone and installing MGDLR and the version of ClockWorkMod Recovery I have and installing the previous version of typhoonmod i used without any problems at all. Hopefully it'll just be a new version of the ROM issue.
I'll post my results here soon.
SpoonyVoid said:
WHAT I THINK IS THE PROBLEM
1) I'm using a fairly old version of ClockworkMod Recovery. That is version 3.0.2.5 (150MB with 5MB Cache as per Typhoon's Requirements). Is this the problem?
2) I didn't remove the SIM and SD card during the entire flashing/reinstallation process. Could this be it?
Thanks for your help. And also I'm sorry I can't post this on the Typhoon ROM thread since I still don't have 10 posts.
Click to expand...
Click to collapse
Sadly I can't give you any new suggestions, but I can certainly rule these two out as possibilities. I've never taken out the SIM when flashing, and you can't flash without the SD card. Recovery 3.0.2.5 is actually (from what I've heard) the most stable version. Have you tried other ROMs? Although again I highly doubt it's the issue, it's worth a shot.
You might want to consider the possibility of bad blocks, from what I've heard it can cause issues such as this (I don't actually have experience with them) so check for them (a simple forum search should give you a method as to how to do this).
SpoonyVoid said:
Well not yet. I am working on it. Does anyone
Anyways, I'm going to try task29ing the phone and installing MGDLR and the version of ClockWorkMod Recovery I have and installing the previous version of typhoonmod i used without any problems at all. Hopefully it'll just be a new version of the ROM issue.
Click to expand...
Click to collapse
Okay, So I tried this. The ROM installed fine but when I tried to power off and power on again it didn't work, the same problem happened where it got stuck on the Android logo.
WHAT I DID THEN
I decided enough's enough and that I can't really use my phone with Android if in some case something happens and I have to reboot it, I'll lose all my data and I'll have to reinstall it all over again.
So I switched to Windows 6.5 version 2.10.531.1 running Radio 2.15.50.14 and everything installed perfectly and I even rebooted the phone after installation and it worked. It came on with no problems. I'm guessing this is an issue that only affects Android then.
Nigeldg said:
Have you tried other ROMs? Although again I highly doubt it's the issue, it's worth a shot.
You might want to consider the possibility of bad blocks, from what I've heard it can cause issues such as this (I don't actually have experience with them) so check for them (a simple forum search should give you a method as to how to do this).
Click to expand...
Click to collapse
Thanks for the reply. I have not tried other ROMs out of fear of bricking my phone to be honest. Typhoon ROM is like one of the easiest for a newbie to install.
And yes, when I was searching around the forum, I did come across the issue of bad blocks. Sadly, I totally forgot to check whether it was affecting my NAND before installing WinMo 6.5. I'll try and look around the forums and google on whether I can check my bad block status on WinMo 6.5 somehow. If I can't, I think I'll use WinMo 6.5 for a while now, I can't really bear having to install and reinstall and install and reinstall, I feel like it'll make the bad block situation (If I do have it) worse.
I'm going to play around with WinMo 6.5 ROMs now. But if ever there is any development on my problem, I'll post on this thread and keep people updated.
I do have one question though, will upgrading to WinMo 7.5 be affected by the bad blocks? (If I have it)
Just saying, although it doesn't really matter, it's Windows Phone 7 (not WinMo 7). One's sh*t, and one's brilliant I don't have any actual experience with Windows Phone though, so I wouldn't know.
As for your concern about bricking your phone, there isn't any way you can do that outside of flashing an incorrect radio, and if you have an EU HD2 then AFAIK there isn't really ANY way of bricking it. Try other ROMs, they have exactly the same install process as TyphooN. In fact, starting fresh from WinMo might actually help. As long as you stick to this guide and use the correct partition size, you will never really go wrong. You can obviously also check for bad blocks after you install Android again (if you decide to do so, of course).
I have quite exciting news! well for me at least
I flashed Windows Phone 7.5 on my HD2 and was very impressed with it. It worked nicely and I really liked all the features. One thing I didn't like however was the battery drainage. The battery drained in 6 hours, and the next day it took 15 hours to drain and then again it took 6 hours to drain. I realized I couldn't use a phone daily with such uncertain battery capacity.
So I decided...*breathe*...to try out Android again, the NexusHD2 ROM by tytung in particular and hope and pray I don't have bad blocks and the rebooting problem doesn't occur.
So I uninstalled WP7, repartitioned my SD card, installed Windows 6.5 STOCK and the right radio and MAGDLR, Clockwork Recovery and flashed NexusHD2 and then did the Bad Blocks thingamabob I was supposed to do and accessed the recovery.log but I couldn't find any mention of "bad blocks" or anything related to "bad". But I dunno...
Anyways the good news is NexusHD2 Gingerbread 3.5.7 works really well and I don't have the rebooting problem anymore. Just a few android.process.media force close issues that I'm trying to figure out but the main problem is gone!
SpoonyVoid said:
I have quite exciting news! well for me at least
I flashed Windows Phone 7.5 on my HD2 and was very impressed with it. It worked nicely and I really liked all the features. One thing I didn't like however was the battery drainage. The battery drained in 6 hours, and the next day it took 15 hours to drain and then again it took 6 hours to drain. I realized I couldn't use a phone daily with such uncertain battery capacity.
So I decided...*breathe*...to try out Android again, the NexusHD2 ROM by tytung in particular and hope and pray I don't have bad blocks and the rebooting problem doesn't occur.
So I uninstalled WP7, repartitioned my SD card, installed Windows 6.5 STOCK and the right radio and MAGDLR, Clockwork Recovery and flashed NexusHD2 and then did the Bad Blocks thingamabob I was supposed to do and accessed the recovery.log but I couldn't find any mention of "bad blocks" or anything related to "bad". But I dunno...
Anyways the good news is NexusHD2 Gingerbread 3.5.7 works really well and I don't have the rebooting problem anymore. Just a few android.process.media force close issues that I'm trying to figure out but the main problem is gone!
Click to expand...
Click to collapse
Good to hear that, and it's also good that you don't have any bad blocks. Even then, you shouldn't have the FC problems, so this is quite confusing.
Nigeldg said:
Good to hear that, and it's also good that you don't have any bad blocks. Even then, you shouldn't have the FC problems, so this is quite confusing.
Click to expand...
Click to collapse
Funny thing really, I did some testing and the process.android.media force closes every time I try to open the android market ONLY AFTER I have powered off and powered on the device AFTER flashing the ROM. If I don't power off the device after flashing the ROM, I don't have that problem at all and I can access the android market with no problems.
Just to be on the safe side however and since I've decided to keep on using NexusHD2 daily, I've backed up all the system files (after a clean re-installation) with Titanium backup so if ever I have to reboot the device, I can hopefully prevent the force close messages from appearing. I've also updated the android market to the latest version just for kicks.
When trying to fix the force close problems earlier, I went to the MAGDLR bootloader screen, proceeded to the CWM menu, tapped into Advanced and fixed permissions. When I booted into Android, the force close messages stopped appearing, however the android market wouldn't open. It would appear briefly and then close automatically without displaying any sort of error message. Strange.
I seriously think I haven't done the bad blocks check properly. I'm sure I have some since this phone is around two and half years old now and was passed on to me by my brother after he experimented around with it as well. I followed AngelDeath's post in the Bad Block Awareness thread but couldn't find any mention of bad blocks and found only a few mentions of the word "block" itself on the recover.log. I didn't find anything similar to his extract of his log on the first post of that thread as well. I'm doing something wrong.
SpoonyVoid said:
Funny thing really, I did some testing and the process.android.media force closes every time I try to open the android market ONLY AFTER I have powered off and powered on the device AFTER flashing the ROM. If I don't power off the device after flashing the ROM, I don't have that problem at all and I can access the android market with no problems.
Just to be on the safe side however and since I've decided to keep on using NexusHD2 daily, I've backed up all the system files (after a clean re-installation) with Titanium backup so if ever I have to reboot the device, I can hopefully prevent the force close messages from appearing. I've also updated the android market to the latest version just for kicks.
When trying to fix the force close problems earlier, I went to the MAGDLR bootloader screen, proceeded to the CWM menu, tapped into Advanced and fixed permissions. When I booted into Android, the force close messages stopped appearing, however the android market wouldn't open. It would appear briefly and then close automatically without displaying any sort of error message. Strange.
I seriously think I haven't done the bad blocks check properly. I'm sure I have some since this phone is around two and half years old now and was passed on to me by my brother after he experimented around with it as well. I followed AngelDeath's post in the Bad Block Awareness thread but couldn't find any mention of bad blocks and found only a few mentions of the word "block" itself on the recover.log. I didn't find anything similar to his extract of his log on the first post of that thread as well. I'm doing something wrong.
Click to expand...
Click to collapse
Ah that may be the problem then. You shouldn't really be touching anything immediately after flashing. Let the ROM settle for 5 minutes, complete the set up and then reboot a few times. As for why the Android Market isn't opening, once again am completely stumped, sorry. Try clearing the app data and cache then opening it again. I don't know whether or not this would work, but try to install a new play store.apk (e.g. the updated one in the HD2 Android Themes and Apps section) and try again. On no ROMs have I ever had this issue.
As for your being unsure about the bad blocks, I would be inclined to agree with you there, as it seems unlikely that after so long there would still be no bad blocks, especially if you and your brother were often flashing things.
dmesg command from a terminal emulator might give some info on the presence of bad blocks, if you haven't already tried it.
Sent from my Nexus One using xda premium
A logcat would be really useful when:
-ever your ROM gets stuck after a reboot.
- You face any random force close.
I used to have issues with the market closing without any error, it turned out to be unsupported where I was. In the new google play, it'd open, but nothing shows up. Fixed it by using DroidVPN.
Was the market working prior to this problem?
Also, have you checked the battery pins? (sometimes, they cause unpredictable problems)
You could also give cLK a shot, and see if the problem persists.
hello world!
i've been using my gt-i9300 since one year now. back then i've rooted it right away with an already rooted firmware or stock firmware.
can't remember anymore. the file was: I9300XXDLIH_I9300EPLDLJ1_I9300XXDLID_HOME.tar.md5
i hadn't had any problems. even had cwm and stuff on it.
a few days ago i've flashed this firmware onto my cellphone: I9300XXUGMK6_I9300DBTGMK2_I9300XXUGMK6_HOME.tar.md5
and after testing if all went ok i've figured out that some apps had trouble opening itself.
i've then flashed chainfire's CF-Auto-Root-m0-m0xx-gti9300.tar.md but still the problem remained.
firefox, dropbox, drweb light and a few others had problems running. so i've uninstalled firefox and drweb, reinstalled them
and the ran again.
then i thought "whynot copy the files from internal storage to the external" .. ive tried that and copied the stuff back into
the phone and the apps ran again.
so my question now is, what have i done wrong or why were there right problems or what is it that the apps
get fixed after copying them from and to the internal cellphone storage?
besides that, cf's superuser hasn't been flashed directly. i had to install it.
done the firmware/cf flash/install procedure twice and both times i had to install the stuff manually.
it's rooted now and the trick with copying the apps fixes the halting problem. but what is the real problem?
and another question i have "insane chip? YES" .. i thought samsung fixed this bug?
cheers!
'My Nexus 10 started to randomly reboot several times a day after the Kitkat update and because it is outside the warranty period I cannot get it replaced.'
It reboots no matter what is running and sometimes it reboots immediately after a power up but never enters a reboot loop.
I've tried a factory reset and running it in safe mode but that didn't stop it.
I've not been able to replicate the reboot fault until yesterday when I ran the BBC iplayer and downloaded a 1-hour Horozon video of about 650Mb and when I tried to play it I got a reboot and that happened consistantly.
I tried a complete power down and reboot then tried to play the downloaded video but it always rebooted.
I tried deleting and re-saving the video incase it was corrupt but it still rebooted.
I tried deleting the video and streaming it and I could watch it that way without any reboot.
I've tried downloading three 1-hour Horizon videos of about the same size and only one plays without rebooting.
A check of running apps shows just the keyboard and a couple of system apps but I still get the reboot when I try to play the saved video.
I thought about removing apps one at a time to see if that would solve it but I've basically got the same apps I had before the Kitkat update.
I wondered if I could undo the Kitkat update and flash the previous rom to see if that would solve it for Kitkat was not a big improvement.
I've never used a custom rom and not run anyting other than stock software.
I would be most grateful for any suggestions on how to fix this rebooting problem and whether going to an earlier version of Android is feasable and how would I do it.
PS. There is a BBC iplayer option to download videos using less resolution and when I choose that option the Horizon file size falls to 344Mb which is about half the size of the original and it solves the reboot problem when playing the saved video.
So it would seem that the BBC iplayer reboot problem is related to file size.
It's fairly easy to downgrade, just Google "nexus factory images" and you should find all the old versions of android straight from Google. There should be guides online for how to flash a factory image. Just make sure to back up all your files to your computer as it will wipe everything.
Sent from my SGH-I747M using xda app-developers app
gc84245 said:
It's fairly easy to downgrade, just Google "nexus factory images" and you should find all the old versions of android straight from Google. There should be guides online for how to flash a factory image. Just make sure to back up all your files to your computer as it will wipe everything.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Thanks for your help.
I've found the factory images and I'm now looking for a simple detailed guide how to do the downgrade.
My Nexus 10 is on 4.4.2 (KOT49H) and I think I'll try downgrading one level to 4.4 (KRT16S) to see if that solves the reboots problem and if not then I'll try downgrading further to 4.3 (JWR66Y).
Gaugerer said:
Thanks for your help.
I've found the factory images and I'm now looking for a simple detailed guide how to do the downgrade.
My Nexus 10 is on 4.4.2 (KOT49H) and I think I'll try downgrading one level to 4.4 (KRT16S) to see if that solves the reboots problem and if not then I'll try downgrading further to 4.3 (JWR66Y).
Click to expand...
Click to collapse
Here is a good guide (sorry, I would have posted it earlier but I didn't have my computer with me at the time and was posting from my phone):
http://forum.xda-developers.com/showthread.php?t=1907796
gc84245 said:
Here is a good guide (sorry, I would have posted it earlier but I didn't have my computer with me at the time and was posting from my phone):
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
Thanks for the guide link.
Unfortunately, my laptop is running Windows 8.1 and it is difficult to install the USB driver and Android Development Kit needed to flash previous Android versions, so I've given up until I can find the way to do it.
PS. I've found a way of installing the ADB and Fastboot drivers on my Windows 8.1 laptop and here is a link:
http://forum.xda-developers.com/showthread.php?t=2588979
So I'm back on track to solve my random reboots using an earlier version of Android.
I noticed the iPlayer hard crash thing too. I can play downloads, but as soon as I pause it and attempt to restart, or just slide the progress bar to move to a different part of the video, the tablet hangs then reboots. It's completely reproducible, and doesn't happen on any of my other devices.
Apart from that, my n10 has now gone 20 days since the last random reboot, so it's a lot more stable in general than it used to be!
I've found a easy way to downgrade to 4.3 and would be grateful for any opinion on how safe it is and if anyone has tried it.
http://forum.cyanogenmod.com/topic/83985-nexus-factory-images-to-revert-to-stock/
AleT said:
Apart from that, my n10 has now gone 20 days since the last random reboot, so it's a lot more stable in general than it used to be!
Click to expand...
Click to collapse
Arghh...this thing is a POS. I haven't used it in 2 months. Today I fired up chrome for some browsing. It hard locked within 5 minutes. I left it for an hour plus with the screen on and still locked up. Just frustrated. Worst Android device I've owned.
Sent from my XT1053 using Tapatalk
Either you have a faulty app or your tablets have a hardware defect. The random reboot issue, where the GPU driver would leak memory and force a kernel panic, has been fixed since Android 4.3 in July. This includes the Chrome reboot issue. I've had 2 reboots over 13 months, and both were cause by a ROM issue. I assure you, there is nothing wrong with the Nexus 10. Try a 4.4.2 factory image and see if that solves anything.
Koopa777 said:
Either you have a faulty app or your tablets have a hardware defect. The random reboot issue, where the GPU driver would leak memory and force a kernel panic, has been fixed since Android 4.3 in July. This includes the Chrome reboot issue. I've had 2 reboots over 13 months, and both were cause by a ROM issue. I assure you, there is nothing wrong with the Nexus 10. Try a 4.4.2 factory image and see if that solves anything.
Click to expand...
Click to collapse
I still get random re-boots in `safe mode` which is supposed to only allow apps installed with the system to run which leaves a bad 4.4.2 which could be checked by a re-flash of the factory image or faulty hardware.
I was planning to downgrade to 4.3 to see if that solved the re-boots but I might try a re-flash of 4.4.2 first to see if that works..
I'm not very confident about flashing and I've had the additional problem of working on windows 8.1 on my laptop.
I am running the factory image, 2nd one with same issues. I'm not necessarily disputing what you are saying but there were plenty of people telling me they had a perfect tablet when the memory leak wasn't fixed.
Sent from my XT1053 using Tapatalk
rxnelson said:
I am running the factory image, 2nd one with same issues. I'm not necessarily disputing what you are saying but there were plenty of people telling me they had a perfect tablet when the memory leak wasn't fixed.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
The memory leak was fixed but apparently, it's reappeared for me with the latest kitkat update. Quite frustrating, you'd think Google would be on top of these things. What's the point of fast updates if you're waiting months on end for a fix. If I don't powerdown my tablet when I'm finished using it I can guarantee a reboot during use. In the last 24hrs, it has rebooted on me twice while using Chrome. Quite irritating to be honest
It seems from previous posts that re-flashing 4.4.2 does not solve the reboots and I've not found a way to downgrade to 4.3 on Windows 8.1 to see if that works.
So I've tried another factory reset, but this time I've not allowed any non-Google apps to be installed other than the Photon browser which I need for flash Websites and the Re-boot logger app to record any reboots.
I'm using my Note 3 for the rest of my apps as that is still on 4.3 and doesn't have the reboot problem, but that might change after the KitKat upgrade.
I was getting at least 2 or 3 reboots a day so I should soon know if running 4.4.2 after a factory reset with just two 3rd party apps solves the problem and if so then that will suggest a rougue app. which I can reveal by re-installing the apps piecemeal.
I've just had another random reboot so I've done another factory reset but not signed in to Google so there have been no downloads and the only program I've run is Settings to increase the screen timeout to 30 - minutes.
If I still get random reboots then it is nothing to do with 3rd party apps or updates for I've not downloaded any.
That just leaves the hardware or the original 4.4.2 assuming the factory reset returns to that.
I didn't experience any reboots when not signed into google after a factory reset so I signed in and restored my tablet using Google backup.
I soon started to get reboots again, but I noticed that since the KitKat upgrade a website I use very often was sometimes automatically loading the Play store to try and get me to use their much inferier app. It doesn't happen on my Note 3 which is still on 4.3.
If I tried to close the Play store app to get back to the browser by swiping it away then it crashes and keeps trying to load over and over. If I hit the home button the Play store automatically re-appears still loading over and over, but after swiping it away several times it goes away or stops with an error message asking me to report the crash which I did and the browser is closed.
In order to fix this I disabled the Play store app so that it did not appear in my list of apps.and the website instead of loading the Play store app re-directed the browser to the Play store website which was better for I was still in the browser.
Since I stopped this particular website loading the Play store by removing it, I've just had one re-boot instead of several and my tablet is no longer overheating. I am a heavy user and have my tablet on many hours a day, so one re-boot is acceptable to me.
I've downloaded a Play store apk which I can install if needed but always remove it before using the website which tries to automatically load it.
It is a nuisance and I wish I'd stayed with 4.3, but I can live with the occaisional re-boot that might not be noticed if I only used my tablet lightly.
I'm annoyed that a website can automatically load the Playstore without me requesting it and that KitKat allows it.
I hope my experience helps others who are getting several re-boots a day.
PS
I did a factory reset then removed the Play store app before using the problem website so that it never loaded it in case that was needed.
Flashing the 4.3 factory image downgrades everything. For what it's worth, I noticed that the userdata partition is constructed differently than in 4.2.2(my last factory flash). That could have something to do with it. But also, I've been on custom ROMs since I got the tablet, yet I've never rebooted on 4.4.X. I guess try a vanillish ROM(like RastaKat) to see if that reboots.
Koopa777 said:
Flashing the 4.3 factory image downgrades everything. For what it's worth, I noticed that the userdata partition is constructed differently than in 4.2.2(my last factory flash). That could have something to do with it. But also, I've been on custom ROMs since I got the tablet, yet I've never rebooted on 4.4.X. I guess try a vanillish ROM(like RastaKat) to see if that reboots.
Click to expand...
Click to collapse
Now that I'm just getting one reboot a day and my tablet is running cooler I can live with that and I don't mind re-installing the Play store when needed for continuous updates can be a nuisance.
I finally managed to downgrade to 4.3 and I'm hoping that will solve all the problems I had with 4.4.2
But all seems well at the moment.
I'm not being booted from websites to the Play store, I can use the BBC iPlayer to download and run 1-hour videos and flash player works better.
Google has downloaded 4.4.2 (KitKat) but I'm not going to install it.