Related
Okey dokey, my phone is making my brain hurt. three days ago, my phone was going haywire. I was rooted with UNL3ASH3D 1.4 and RedNinja theme, working well. All of a sudden everything Force Closes. I was getting so many FC's I could put the FCC out of business. When I would unlock my screen, my launcher wouldn't load and the only thing I could do is get Advanced Task Killer to open from the Status Bar. Everything kept popping up Force Closing, Android system, google framework, Moto services. So I decided to FXZ back to stock. While it was on step 14/15 I decided to let it run its course and I stepped outside. Windows decides to restart itself in the middle of re-programming and drained my battery dead so I couldn't fix it. Last night I went and bought the battery dock + extra battery from the VZW store. Charged up the battery all the way, popped that baby in my Bionic and FXZ'd my way to glory. Or I thought so at least. My phone gets done, reboots, and even loads up my old wallpaper so it had to have some kind of connection or something. You know, you can see the wallpaper from the lock screen. Ok remember, my phone is fully back to Factory Settings now. I unlock the screen and what happens? FC FC FC FC FC FC. Everything starts Force Closing again. So someone tell me, would I be right in assuming this is a problem with the phone? Do you guys think I would be able to turn it in and file a warranty claim? Am I just the devil himself to all Android phones? I don't know. I'm starting to think that maybe I should buy a prepaid Net10 phone with a graphics processor from the 80s.
lemonoid said:
Okey dokey, my phone is making my brain hurt. three days ago, my phone was going haywire. I was rooted with UNL3ASH3D 1.4 and RedNinja theme, working well. All of a sudden everything Force Closes. I was getting so many FC's I could put the FCC out of business. When I would unlock my screen, my launcher wouldn't load and the only thing I could do is get Advanced Task Killer to open from the Status Bar. Everything kept popping up Force Closing, Android system, google framework, Moto services. So I decided to FXZ back to stock. While it was on step 14/15 I decided to let it run its course and I stepped outside. Windows decides to restart itself in the middle of re-programming and drained my battery dead so I couldn't fix it. Last night I went and bought the battery dock + extra battery from the VZW store. Charged up the battery all the way, popped that baby in my Bionic and FXZ'd my way to glory. Or I thought so at least. My phone gets done, reboots, and even loads up my old wallpaper so it had to have some kind of connection or something. You know, you can see the wallpaper from the lock screen. Ok remember, my phone is fully back to Factory Settings now. I unlock the screen and what happens? FC FC FC FC FC FC. Everything starts Force Closing again. So someone tell me, would I be right in assuming this is a problem with the phone? Do you guys think I would be able to turn it in and file a warranty claim? Am I just the devil himself to all Android phones? I don't know. I'm starting to think that maybe I should buy a prepaid Net10 phone with a graphics processor from the 80s.
Click to expand...
Click to collapse
after the FXZ did you do a factory reset or did you just reboot?
Just reboot. That's what I've always done, I've FXZ'd it three times. I don't even know how to do a factory reset after I FXZ it.
lemonoid said:
Okey dokey, my phone is making my brain hurt. three days ago, my phone was going haywire. I was rooted with UNL3ASH3D 1.4 and RedNinja theme, working well. All of a sudden everything Force Closes. I was getting so many FC's I could put the FCC out of business. When I would unlock my screen, my launcher wouldn't load and the only thing I could do is get Advanced Task Killer to open from the Status Bar. Everything kept popping up Force Closing, Android system, google framework, Moto services. So I decided to FXZ back to stock. While it was on step 14/15 I decided to let it run its course and I stepped outside. Windows decides to restart itself in the middle of re-programming and drained my battery dead so I couldn't fix it. Last night I went and bought the battery dock + extra battery from the VZW store. Charged up the battery all the way, popped that baby in my Bionic and FXZ'd my way to glory. Or I thought so at least. My phone gets done, reboots, and even loads up my old wallpaper so it had to have some kind of connection or something. You know, you can see the wallpaper from the lock screen. Ok remember, my phone is fully back to Factory Settings now. I unlock the screen and what happens? FC FC FC FC FC FC. Everything starts Force Closing again. So someone tell me, would I be right in assuming this is a problem with the phone? Do you guys think I would be able to turn it in and file a warranty claim? Am I just the devil himself to all Android phones? I don't know. I'm starting to think that maybe I should buy a prepaid Net10 phone with a graphics processor from the 80s.
Click to expand...
Click to collapse
I would probably do the FXZ one more time and if the problem persists, then I think you know it's a hardware issue - warranty at that point.
Good luck and let us know how it turns out.
lemonoid said:
Just reboot. That's what I've always done, I've FXZ'd it three times. I don't even know how to do a factory reset after I FXZ it.
Click to expand...
Click to collapse
Do a fxz and then boot into recovery and do a factory reset. Then report back! good luck!
Fyi a fxz doesn't wipe data like previous sbfs from Droid x and other moto phones
Sent from my DROID BIONIC using XDA Premium App
^^^Everything they said.
Also, stop using Advanced Task Killer.
mistawolfe said:
Also, stop using Advanced Task Killer.
Click to expand...
Click to collapse
Yeah, task killers are the devil for root users.
Yeah I usually have ATK disabled, but last time I did my Titanium Restore I forgot that it was in one of my profiles, I was doing some mods/tweaks to some apps and that was in my tweaker profile. But anyways on to the issue at hand, I did go into recovery and do a factory reset and it fixed it. I didn't FXZ again, I figured if a factory reset should do the trick, and it did since I had already FXZd.
lemonoid said:
Yeah I usually have ATK disabled, but last time I did my Titanium Restore I forgot that it was in one of my profiles, I was doing some mods/tweaks to some apps and that was in my tweaker profile. But anyways on to the issue at hand, I did go into recovery and do a factory reset and it fixed it. I didn't FXZ again, I figured if a factory reset should do the trick, and it did since I had already FXZd.
Click to expand...
Click to collapse
I would just uninstall it and never use it again. ATK that is...
Sent from my DROID BIONIC using xda premium
I would just like to commend you for not immediately going to Verizon for a warranty replacement. It is people who replace before researching the cause of their problems that cause us to be presented with these phones with locked bootloaders. So, again, kudos on asking questions and figuring it out without replacing the phone. If only everyone would follow suit.
Sent from my DROID BIONIC using xda premium
I can't stand not being able to fix something that is broken, especially when i broke it and even more so when its an Android device. People who take the easy way out just show me that they don't like to learn. ever since my Eris i have been trying to fit in time to learning more about Android, programming and software development. Warranty replacement would void my commitment to learning. So thanks for the kudos bro. Just wish that more people got enjoyment from learning.
Sent from my DROID BIONIC using xda premium
lemonoid said:
I can't stand not being able to fix something that is broken, especially when i broke it and even more so when its an Android device. People who take the easy way out just show me that they don't like to learn. ever since my Eris i have been trying to fit in time to learning more about Android, programming and software development. Warranty replacement would void my commitment to learning. So thanks for the kudos bro. Just wish that more people got enjoyment from learning.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
THIS... omfg this is exactly how I feel. :-D
I was following these instructions http://forum.xda-developers.com/showthread.php?t=1305891
And under step 3 section where it says create a folder called cminstall, I was unclear if that was on the TP or on my PC. I created it on my pc. I follwed the rest of the steps and when I ran novacom my TP did it's install thing and then at the very end there was a message
"no cminstall dir found, nothing to install.
Power off when ready"
I guess cminstall was supposed to be on the TP. No I can't turn it off. I tried the power button, I tried the power and volume up button, and the center button and the up button, nothing.
Am I hosed? If I can't turn it off how do I web doctor it to get back to webOS?
Try to press Power + Home for 20-30 sec. Then it should go to power off.
Afterwards start fresh.
justfor4 said:
Try to press Power + Home for 20-30 sec. Then it should go to power off.
Afterwards start fresh.
Click to expand...
Click to collapse
Yeah I just found that button combo on the webos nation forum. Dammit I just made a useless help me thread.
Well, though that this its true, the issue is solved.
And this is thankfully a good thing...
Great
I had an old palm pre and it was impossible to brick. I did the metadoctor a few times to upgrade to webos 2.0 and when something went wrong, I just used the webos doctor to fix it. Palm was really good about that. Webos is awesome, but the lack of apps killed it.
Sent from my GT-I9100 using Tapatalk
lvpre said:
I had an old palm pre and it was impossible to brick. I did the metadoctor a few times to upgrade to webos 2.0 and when something went wrong, I just used the webos doctor to fix it. Palm was really good about that. Webos is awesome, but the lack of apps killed it.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Yeah lack of apps is why I went to CM7.
BTW after a TP reboot and refollowing the steps I am now on CM7!
VGSmatt said:
Yeah lack of apps is why I went to CM7.
BTW after a TP reboot and refollowing the steps I am now on CM7!
Click to expand...
Click to collapse
Why don't u test the xronified version? U will be happier
+1 happy user of xronified version
klear72 said:
Why don't u test the xronified version? U will be happier
Click to expand...
Click to collapse
What makes xron better? After only one day, I like cm way more then webos!
Leoisright
VGSmatt said:
What makes xron better? After only one day, I like cm way more then webos!
Click to expand...
Click to collapse
Too many..or only...Leoisright !!! I've never known anyone who works much as he did and now with the help of MiSfit it will be even better
http://forum.xda-developers.com/showthread.php?t=1321335
What makes xron better?
Click to expand...
Click to collapse
It's faster+beter games support+some fixes like wi-fi. Check benchmarks of cm a3.5 and latest xronified version
VGSmatt said:
What makes xron better? After only one day, I like cm way more then webos!
Click to expand...
Click to collapse
the rom developer leo has been so enthusiastic and has been pushing updates one after the other in a regular basis and the rom is fast. you will see it when you try it . moreover few more devs have just joined the development which in my opinion is going to make the rom rock
ok before i got to into cm7, i made the jump to xron. You guys were right, its pretty fantastic.
You can't brick your TouchPad.
It's not possible.
Yeah, I may have panicked a little when all the button combos I knew weren't working. Then I found the correct button combo on the webos forum.
I'm having an issue. I was prompted to update to webOS 3.0.4. Long story short after and hour and a half with the black HP screen coming and going I decided something probably wasn't right. I downloaded webOS doctor and am trying to run it, but for the life of me I can't get my PC to see my TP. My PC keeps making the "USB connecting" sounds. I think the problem is that it's looping between the HP logo and total black screen.
F***ing HP and their ****ty software! Anyone have any ideas on what I can do? I've tried holding menu/power and it just keeps looping
Thanks in advance
edit: got it working, here's what I did thanks to webOS support:
Hold power and press center button 15 times. This turns device into a powered off state.
Hold power and volume up to enter USB mode
Download and run webOS doctor.
After about a total of 3 hours of thinking my TP was dead, I kind of have a new found love for it, lol
btw, why didn't i get any way to access the internet? i had to download firefox from the market to go online. did xron come with gapps or not?
also i downloaded google reader and it force closes after reading a couple posts.
VGSmatt said:
btw, why didn't i get any way to access the internet? i had to download firefox from the market to go online. did xron come with gapps or not?
also i downloaded google reader and it force closes after reading a couple posts.
Click to expand...
Click to collapse
Xron comes with Gapps but Leo replaced stock browser with Dolphin (which is better). There is a problem if random FCs but they are so much less then what I had in CM7...as Xron is also based on CM7...you will see few bugs...but overall it made my TP so useful..
i agree, this is so much better then before. i don't see dolphin in my app drawer, no matter, firefox is working fine.
yip, it is better and if you want some eye candy the SPB shell 3D is really cool
kind of strange, i just installed cm9 on a new touchpad. everything seems to work like normal, except sometimes it will reboot itself when at the slide to unlock screen. it only seems to reboot then, and only when the backlight shuts off on the lock screen, and never when i am actually using android.
anyone got any ideas?
hm. maybe i should have posted this somewhere else
x000x said:
kind of strange, i just installed cm9 on a new touchpad. everything seems to work like normal, except sometimes it will reboot itself when at the slide to unlock screen. it only seems to reboot then, and only when the backlight shuts off on the lock screen, and never when i am actually using android.
anyone got any ideas?
Click to expand...
Click to collapse
Try changing from 'slide' to either 'pin' or 'none'. I think you can do that either in settings or in security. If you want to keep 'slide', I really don't know the answer to your problem.
Good luck.
x000x said:
kind of strange, i just installed cm9 on a new touchpad. everything seems to work like normal, except sometimes it will reboot itself when at the slide to unlock screen. it only seems to reboot then, and only when the backlight shuts off on the lock screen, and never when i am actually using android.
anyone got any ideas?
Click to expand...
Click to collapse
Probably redundant to ask, but which ROM and did you full wipe? It could also possibly be a battery problem; perhaps try another ROM and see if the same issue comes up.
it was just the cm9 nightly. there was nothing else on it but webOs. it was brand new, took it out the box, installed cm9 nightly, gapps. other than than i didnt do anything else to it. when at the slide to unlock, the screen shuts itself off after maybe 15 seconds and i'm assuming goes into a low power state. i'm kind of wondering if that low power 'trigger' is what is causing the reboot. its never happened to my other touchpad.. its really strange
Funny how these problems seem to come and go. Mine used to do the same thing when I first got it, but one day it just stopped having that problem.
Sent from my cm_tenderloin using xda premium
envy
-SGA- said:
Funny how these problems seem to come and go. Mine used to do the same thing when I first got it, but one day it just stopped having that problem.
Click to expand...
Click to collapse
Oh how I envy you. I uninstalled Android, formatted my touchpad, loaded it up in WebOS Doctor and security wiped everything. Then I reinstalled android and immediately cleared the caches and did a backup. From the backup, no matter what ROM I install (all the latest versions), I get random reboots all the F$&#-ing time. There doesn't seem to be anything I can do. Minimum and maximum CPU values don't alleviate the problem. It's frustrating beyond belief.
You should try deleting and remaking the media partition, where android is stored, through novaterm. Then webos doctor it, and reinstall android. No matter what ROM I used to have a scratchy sound from the speakers with the screen off until I did that, and now it has not happened since. It might help your RR problem. I know even acme uninstaller doesn't clean everything!
Sent from my aokp_tenderloin using xda premium
hm. i've never fiddled with novaterm before, is it related to novacom? would just running webos doctor work just as well? i'm thinking i'll just start from a clean slate. even use new cm9 downloads etc.
-SGA- said:
You should try deleting and remaking the media partition, where android is stored, through novaterm. Then webos doctor it, and reinstall android. No matter what ROM I used to have a scratchy sound from the speakers with the screen off until I did that, and now it has not happened since. It might help your RR problem. I know even acme uninstaller doesn't clean everything!
Sent from my aokp_tenderloin using xda premium
Click to expand...
Click to collapse
Try this link : http://forum.xda-developers.com/showthread.php?t=1426244
I hope it helps.
well i did a factory wipe and ran webos doctor. while at the webos screen to create an account it rebooted itself. i'm thinking it might be a hardware issue. this is not looking good.
hey everyone!
my phone went a little crazy by randomly shutting off while using cm10 so I decided to restore to a stock non-root nandroid I made around 8 months ago. Everything went well up until the point I rebooted: I unwittingly had set up a text lockscreen password that I had since then forgotten (who remembers passwords from 8 months ago?!). So I went in CWM, did a factory data reset and rebooted. I turned off the screen and turned it back on to BAM! the lockscreen again... And the fracked up thing is that there isnt even a "forgot password" gmail confirmation option thing at the bottom so I'm completely locked out of my phone! Is there anything I can do other than buy that $4 screen lock bypass exploitation app??
Any help would be greatly appreciated!
h2whoa said:
hey everyone!
my phone went a little crazy by randomly shutting off while using cm10 so I decided to restore to a stock non-root nandroid I made around 8 months ago. Everything went well up until the point I rebooted: I unwittingly had set up a text lockscreen password that I had since then forgotten (who remembers passwords from 8 months ago?!). So I went in CWM, did a factory data reset and rebooted. I turned off the screen and turned it back on to BAM! the lockscreen again... And the fracked up thing is that there isnt even a "forgot password" gmail confirmation option thing at the bottom so I'm completely locked out of my phone! Is there anything I can do other than buy that $4 screen lock bypass exploitation app??
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Maybe try another factory reset (sucks I know) and this time after boot go into security settings and turn off the screen lock before your screen turns off. If you just try and change the password you'll be prompted for the old one first. That being said, I haven't used stock in so long I can't promise this will work either.
Those random reboots you got with CM10 were common with older versions and the other variants such as Pacman, Slimbean, etc, but the latest one I haven't had that happen and I've been using it a week. I only say this because stock is just makes this phone crawl IMO.
ArtfulDodger said:
Maybe try another factory reset (sucks I know) and this time after boot go into security settings and turn off the screen lock before your screen turns off. If you just try and change the password you'll be prompted for the old one first. That being said, I haven't used stock in so long I can't promise this will work either.
Those random reboots you got with CM10 were common with older versions and the other variants such as Pacman, Slimbean, etc, but the latest one I haven't had that happen and I've been using it a week. I only say this because stock is just makes this phone crawl IMO.
Click to expand...
Click to collapse
Haha, thanks, not an absolute fix but at least it works. Kinda strange since I read that CWM factory resets wipes out everything including lockscreen passes... And my phone wasn't rebooting, it would just shut off randomly, battery would drain at horrifying speeds (from 99% to 0 after a 7 minute phone call) (I also had the latest ver). I was thinking that I could maybe restore stock rom and send it back to samsung or provider since its still under warranty
EDIT: I'm gonna try Samsung Remote Screen Unlock and see if that works. Plus I just checked my battery: It's as swollen as Rosie O'donnell at Mandarin, which explains the crappy battery life.
h2whoa said:
Haha, thanks, not an absolute fix but at least it works. Kinda strange since I read that CWM factory resets wipes out everything including lockscreen passes... And my phone wasn't rebooting, it would just shut off randomly, battery would drain at horrifying speeds (from 99% to 0 after a 7 minute phone call) (I also had the latest ver). I was thinking that I could maybe restore stock rom and send it back to samsung or provider since its still under warranty
EDIT: I'm gonna try Samsung Remote Screen Unlock and see if that works. Plus I just checked my battery: It's as swollen as Rosie O'donnell at Mandarin, which explains the crappy battery life.
Click to expand...
Click to collapse
If you're rooted you can remove gesture.key using adb shell but I forget where exactly it is. Google it
Sent from my Nexus 7 using xda app-developers app
h2whoa said:
Haha, thanks, not an absolute fix but at least it works. Kinda strange since I read that CWM factory resets wipes out everything including lockscreen passes... And my phone wasn't rebooting, it would just shut off randomly, battery would drain at horrifying speeds (from 99% to 0 after a 7 minute phone call) (I also had the latest ver). I was thinking that I could maybe restore stock rom and send it back to samsung or provider since its still under warranty
EDIT: I'm gonna try Samsung Remote Screen Unlock and see if that works. Plus I just checked my battery: It's as swollen as Rosie O'donnell at Mandarin, which explains the crappy battery life.
Click to expand...
Click to collapse
Hate to hear that and you're not the only one to mention swollen batteries around here lately either. Good luck to you!
theAPANT said:
If you're rooted you can remove gesture.key using adb shell but I forget where exactly it is. Google it
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
yeah... can't root, need this phone to be as stock as can be if I'm to get it replaced (or at least the battery). Btw, Is there a way to possibly remove CWM in case they check recovery?
PS: Totally irrelevant but I keep reading about a CM10.1 rom for this phone; I've searched far and wide but I can't seem to find it! Could anybody point me in the right direction?
h2whoa said:
yeah... can't root, need this phone to be as stock as can be if I'm to get it replaced (or at least the battery). Btw, Is there a way to possibly remove CWM in case they check recovery?
PS: Totally irrelevant but I keep reading about a CM10.1 rom for this phone; I've searched far and wide but I can't seem to find it! Could anybody point me in the right direction?
Click to expand...
Click to collapse
Yes the easiest way to get rid of cwm is to flash the stock file. Go to http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G there are, i believe two methods, one using Odin the other flashing something in recovery. Just read. As for cm10.1 camcory is working on it so is smartguy. Even i compiled it but it doesn't boot all the way. Check insomniaforums.org that is probably where it will be posted
Sent from my Nexus 7 using xda app-developers app
CM10.1 boots fine and runs smooth but not yet ready for release. There is a few broken items in it I believe if I recall but cannot restore it due to limited battery till I get home to verify what was wrong. Be patient and when ready public will know about it.
Sent from my SGH-T679 using xda premium
afwolfpacked said:
CM10.1 boots fine and runs smooth but not yet ready for release. There is a few broken items in it I believe if I recall but cannot restore it due to limited battery till I get home to verify what was wrong. Be patient and when ready public will know about it.
Sent from my SGH-T679 using xda premium
Click to expand...
Click to collapse
Bluetooth and camera dont work. I'm saying my own personal build doesn't boot yet but I'm trying some stuff. Right now I'm working on aokp 4.1.2 to get that fixed all the way, mainly because i like aokp and I'm stuck on 4.2.2
Sent from my Nexus 7 using xda app-developers app
Every so often my Kindle Fire 7 hd will shut off. Not reboot. It will completely turn itself off. It is very random. Sometimes it works for a while and the boom it happens. Doesn't seem to matter what I'm doing at the time. Sometimes it is when I unlock the screen...sometimes when the screen rotates...other times when I'm opening an app, or using an app.
There were times that after it would shut off I would turn it back on and it would almost be finished started up, but then turn itself off. I would have to plug it in in order for it to completely boot up.
One thing I've noticed is I don't seem to have any issues when the unit is plugged in. Could be just a coincidence though. The battery is 50%+ when this happens.
It started this about a week ago or so. At that point I had used KFFirstAide to put 7.2.3 on and was running Nova as my launcher. I thought it might be a ROM issue so I installed TWRP and put Kinology on it. Well, it is still happening.
So, it seems like I might have to make a call to Amazon (although I bought it Oct. 2012, so I doubt it is under warranty). I assume I will need to get the whole thing back to stock...unless someone here has a different suggestion).
Thanks for any insights/help you might be able to provide!
Dave.
I have a similar issue where my Kindle now wants to shut down as I open the case????? This is a new problem and I've also noticed that the battery life is getting worse. Anyone else having these problems and got any ideas on how to fix?
Steve
Sent from my KFHD7 using xda app-developers app
@galearned is dealing with a similar issue regarding a KFHD7. I think the three of you should get together to try and find a common denominator.
Slangster said:
I have a similar issue where my Kindle now wants to shut down as I open the case????? This is a new problem and I've also noticed that the battery life is getting worse. Anyone else having these problems and got any ideas on how to fix?
Steve
Sent from my KFHD7 using xda app-developers app
Click to expand...
Click to collapse
Galearned here: I am running CM10.1 on my KFHD7 and do not have any shut down issues as far as I know but, regarding battery life, the unit is pretty bad compared to the KFHD8 also running cm10.1.
I traveled to Cleveland this last weekend and took my KFHD8 with me.
I used the KFHD8 the entire trip on the plane (several hours of fooling around and shopping on Ebay (free ebay on the plane).
I also used the KFHD8 both Saturday and Sunday extensively and Sunday evening, I checked the battery and it was down to 20%.
Until then, I did not plug in to any power supply.
I know for sure the KFHD7 would never had gotten that far.
One thing I have not checked is how quickly the battery drains on both units while doing the same tasks.
Most of the comparisons including the one I posted, indicate that while asleep, the KFHD continues to drain loosing several points over night.
If you leave the KFHD7 asleep for several days, the battery will be down to the 20% level or lower.
The KFHD8 will not loose more than a single point after several days setting asleep.
_________________________________
Update : CM 10.1 Deepsleep release 07/26/2013
Loaded this 07/26/2013 version last night on KFHD7 and configured wifi to be off while asleep as usual.
Tablet was fully charged at 11M and at 7AM still showed battery at %100%.
Very Very nice. Looks like Hashcode came through again............
So, you're saying the shutdown issue ceased after installing CM?
I have the same problem, running CM 10.1
I just flashed CM 10.1 a few days ago and just started to have these random shut offs... usually when the battery is around 60%. I thought it was the ROM, but seeing you guys have the same problem, I´m thinking there is something else involved. I never had those shut offs on stock.
Well, exactly same problem with no apparent solution. I think the problem started when upgraded to 7.3.1. After that I disabled OTA, tried to uninstall all applications added by me, disabled all notifications, etc.. but the problem is not solved
Elgari said:
Well, exactly same problem with no apparent solution. I think the problem started when upgraded to 7.3.1. After that I disabled OTA, tried to uninstall all applications added by me, disabled all notifications, etc.. but the problem is not solved
Click to expand...
Click to collapse
Are you on Stock OS? If so, have you changed the Kindle's DPI? When I was on stock, I changed my DPI to 213 (same as Nexus 7) and started having random rebooting issues. Changing the DPI back to default (240) fixed the problem.
Just my two cents
Ph0enix_216;47286524 you on Stock OS? If so said:
Thank you for your post. I m on stock OS, but I dont know how to change DPI!!
Click to expand...
Click to collapse
Elgari said:
Thank you for your post. I m on stock OS, but I dont know how to change DPI!!
Click to expand...
Click to collapse
If you don't know, then I'm guessing that you never changed it, which means that it's probably not the problem. However, if you want to check, download ES File explorer from the Play Store, and navigate to "/system." There should be a file there called "build.prop." Open it, and look for this line (the value should be set at 240).
Code:
ro.sf.lcd_density=240
Ph0enix_216 said:
If you don't know, then I'm guessing that you never changed it, which means that it's probably not the problem. However, if you want to check, download ES File explorer from the Play Store, and navigate to "/system." There should be a file there called "build.prop." Open it, and look for this line (the value should be set at 240).
Code:
ro.sf.lcd_density=240
Click to expand...
Click to collapse
Thank you! I did what you said but, exactly as you anticipated, it was properly configured.
But the problem persists and I can not find any solution anywhere!
Elgari said:
Thank you! I did what you said but, exactly as you anticipated, it was properly configured.
But the problem persists and I can not find any solution anywhere!
Click to expand...
Click to collapse
You could reflash the entire system image. Download Kindle Fire First Aide (it's in the "General" section of this subforum) and follow the steps there. Once it's set up, select the option 3 (assuming that you have a KFHD), which will let you choose to restore to either the 7.2.3 or 7.2.1 OS. It says "fastboot," but I don't think you need a fastboot cable for it.
OR, if you have TWRP enabled, you can go here and download Amazon OS 7.4.6, but comes pre-rooted and has OTA updates disabled. Put this on your SD card, reboot into recovery, and wipe your current ROM and install this.
Ph0enix_216 said:
You could reflash the entire system image. Download Kindle Fire First Aide (it's in the "General" section of this subforum) and follow the steps there. Once it's set up, select the option 3 (assuming that you have a KFHD), which will let you choose to restore to either the 7.2.3 or 7.2.1 OS. It says "fastboot," but I don't think you need a fastboot cable for it.
OR, if you have TWRP enabled, you can go here and download Amazon OS 7.4.6, but comes pre-rooted and has OTA updates disabled. Put this on your SD card, reboot into recovery, and wipe your current ROM and install this.
Click to expand...
Click to collapse
I already did the first option you mention, but did not solve the problem.
I will try with the second option. I do not know if I am able to make it!!
And yes, I have KFHD (and I make a factory cable).
Thanks again!
Elgari said:
I already did the first option you mention, but did not solve the problem.
I will try with the second option. I do not know if I am able to make it!!
And yes, I have KFHD (and I make a factory cable).
Thanks again!
Click to expand...
Click to collapse
If you tried the first option, and you're still experiencing the problem, then it might be something you're doing, such as installing a specific app or mod or something.
Ph0enix_216 said:
If you tried the first option, and you're still experiencing the problem, then it might be something you're doing, such as installing a specific app or mod or something.
Click to expand...
Click to collapse
Yes, I think that too! In last month I uninstall all my apps one by one but I do not find the problem either!!
Did you think to have OTA disabled can cause the problem?
I hope tomorrow read To learn about TWRP and try with that.
Elgari said:
Yes, I think that too! In last month I uninstall all my apps one by one but I do not find the problem either!!
Did you think to have OTA disabled can cause the problem?
I hope tomorrow read To learn about TWRP and try with that.
Click to expand...
Click to collapse
OTA shouldn't be the cause. Lots of people have had OTA disabled without any problems. Honestly, I have no clue what the problem is
Ph0enix_216 said:
OTA shouldn't be the cause. Lots of people have had OTA disabled without any problems. Honestly, I have no clue what the problem is
Click to expand...
Click to collapse
Well, the problem the problem has worsened which led me to decide install TWRP.
I read about TWRP and second bootloader and try three times with Hashcode´s method but I cant do it. I´m very frustrated for my inability!!!
Thanks anyway for your help.
Have any of you tried calibrating your battery?
Sent from my JellyBeer Fire HD
Krsmqn said:
Have any of you tried calibrating your battery?
Sent from my JellyBeer Fire HD
Click to expand...
Click to collapse
I tried to install TWRP but after three attempts I could not do it and bricked my KF. So I install everything new with KFFA. The bad news is that the problem continued. I'm starting to believe it's a battery problem and not a problem of the apps. Yesterday its worked all day (with tunein radio) without problem and just spent 20% of battery. But today when I wanted to put to work again made the same problem.
How can I calibrating the battery as you suggest? I think the problem is for this side.