I have boot loader v1.4a and twrp v2.2.2.1. I have installed Stock Jelly Bean 4.1.2_r1 for the Kindle Fire [10-10] and i am using it for more then 6 months and i didn't have any problem not even with wifi or sleep, it was working perfectly and i was using the tablet a lot so i am sure it is well tested and had no problems at all. But since two weeks ago the screen started to lock randomly while using the tablet. For example i was playing a game and the virtual joystick locked it self but then i realize and the back, home and recent apps buttons are also not usable but the game was going on, so i click the hard key on the bottom to lock the screen and when i click again to unlock and i slide the lock to unlock the screen the game is paused and when i resume everything continue with no problem but then after a while it happen again and it happen on random games or apps. I don't know what is the problem if anyone has solution or similar problem please write to me.
alokin said:
I have boot loader v1.4a and twrp v2.2.2.1. I have installed Stock Jelly Bean 4.1.2_r1 for the Kindle Fire [10-10] and i am using it for more then 6 months and i didn't have any problem not even with wifi or sleep, it was working perfectly and i was using the tablet a lot so i am sure it is well tested and had no problems at all. But since two weeks ago the screen started to lock randomly while using the tablet. For example i was playing a game and the virtual joystick locked it self but then i realize and the back, home and recent apps buttons are also not usable but the game was going on, so i click the hard key on the bottom to lock the screen and when i click again to unlock and i slide the lock to unlock the screen the game is paused and when i resume everything continue with no problem but then after a while it happen again and it happen on random games or apps. I don't know what is the problem if anyone has solution or similar problem please write to me.
Click to expand...
Click to collapse
One suggestion is to do a full wipe (factory reset, cache, dalvik and system) and go with a much newer ROM Many issues have been cleared up in the last six months.
Thanks for the reply i was thinking the same but i tried to fix it first, but as you say i will give it a try on the new 4.2.2
alokin said:
Thanks for the reply i was thinking the same but i tried to fix it first, but as you say i will give it a try on the new 4.2.2
Click to expand...
Click to collapse
You might be pleased with the improvement in the battery consumption department
Sent from my SCH-R880 using xda app-developers app
Related
Has anyone else had issues with the Kindle App on the Galaxy Nexus? It will open a few times, but finally freezes while attempting to start. When I reinstall or restart, it will start fine, but that's not really a viable option.
Also, I've been trying out n64oid, and the performance isn't really usable, which is odd, cause it runs on slower phones just fine. What are the chances of an update, and has anyone else experienced this?
n64oid works great for me.. been playing paper mario very well.
Hmm. I went back and tried some of my other roms, and they are working fine. Might just be Re-Volt and Goldeneye. I'll try redownloading them to see if its just the rom, but they might just be buggy.
Still looking to see if anyone else has had the kindle issue.
xNEM3S1Sx said:
Hmm. I went back and tried some of my other roms, and they are working fine. Might just be Re-Volt and Goldeneye. I'll try redownloading them to see if its just the rom, but they might just be buggy.
Still looking to see if anyone else has had the kindle issue.
Click to expand...
Click to collapse
I've had the Kindle app lock up a few times on ITL41F stock and stock/rooted rom, you can tell right away as it goes black instead of loading the splash-screen, killing the process and then restarting works reliably, it seems to lock up more frequently if you leave a book/ newspaper/ magazine open in the app and then switch to another app.
+1 for Kindle freezing. Annoying but don't forget we are early adopters of ICS and as such a lot of apps will not function correctly for quite some time.
Sent from my Galaxy Nexus using XDA App
rgbc said:
I've had the Kindle app lock up a few times on ITL41F stock and stock/rooted rom, you can tell right away as it goes black instead of loading the splash-screen, killing the process and then restarting works reliably, it seems to lock up more frequently if you leave a book/ newspaper/ magazine open in the app and then switch to another app.
Click to expand...
Click to collapse
My app still shows the splash screen, but doesn't go any further. (The guy reading the book under the tree)
wynthewun said:
+1 for Kindle freezing. Annoying but don't forget we are early adopters of ICS and as such a lot of apps will not function correctly for quite some time.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
in fact it ain't only you GNexus users
it used to regularly freeze up my Atrix; or slow it down all the time
No idea how or why thats happening......haven't tried the kindel app on my mum's G2 or any other phone yet
Kindle not working for wife and I either
We both got Verizon GNexus and I think we are going to try contacting Amazon to let them know something's up. We'll inform them of the dedicated thread on XDA if it helps.
smrtdrmmr said:
We both got Verizon GNexus and I think we are going to try contacting Amazon to let them know something's up. We'll inform them of the dedicated thread on XDA if it helps.
Click to expand...
Click to collapse
Awesome. Hopefully they can sort this out quickly , since the google books apps is lackluster. We really need a known issues thread on here, with updates on how close we are to a fix.
+1 on Kindle issue.
Sometimes opens successfully.
Sometimes freezes on splash screen.
Can't go from Kindle to another app then back to Kindle (multitask), just get black screen.
Have to force-close Kindle to get it working again.
I use the Kindle app daily so I hope they can work it out fast.
+1 on Kindle freezing. I can't find a rhyme or reason for it. When it's frozen I don't even see a running process for it. I have to reboot to fix. very annoying.
Update on my end after getting a GNexus:
Kindle is now very very smooth! No reboots or abnormal freezing like on my Atrix.
GPU forced acceleration is forced on in my dev settings
Still having problems on Gnex LTEs
Kindle app starts up but eventually will freeze and require forced shutdown after navigating away/minimizing it and then returning. No new version released, so either we are a limited number of users and Amazon doesn't need to address it yet, or something is wrong with our setup and we are a minority amongst 4.0.2 users.
Running stock ICS haven't touched anything.
Every time I am in an app and click the home button it loads a blank home screen then takes a while to load everything on my home screen. It didn't use to do this, only started in the past few days. Any ideas?
Sent from my Galaxy Nexus using xda premium
Crazy CS said:
Running stock ICS haven't touched anything.
Every time I am in an app and click the home button it loads a blank home screen then takes a while to load everything on my home screen. It didn't use to do this, only started in the past few days. Any ideas?
Click to expand...
Click to collapse
I was having that issue after I installed a live wallpaper (Microbes). Got rid of that and it went back to normal.
Don't have a live wallpaper installed.
Sent from my Galaxy Nexus using xda premium
Are you using a custom launcher?Did you touch anything in developer options?
Did you install an app before it started acting up? It may not be fully compatible with 4.0 and causing issues. Also, have you tried to do a simple restart?
Found the issue. It was easy battery saver. Got rid of it and its fine now.
Sent from my Galaxy Nexus using xda premium
it case it happens again, what your experiencing is home screen redraw. it happens when the android system kills the launcher to save up memory.
this means that when you press home to go back to the launcher, it has to refresh, and redraw everything. and the more you have on your homescreens, and the more apps/widgets you have installed the longer it takes.
i've noticed it happening a lot on my phone when i'm switching between apps and then press home. It's normal for third party launchers but very strange for the stock one to have this so often.
I've had the exact same problem of late (also with the stock app-draw), I imagine it's a case of pinpointing the suspect app that's causing this. It's pretty serious though, a good 2 or 3 seconds and even then it's super choppy until the home screens are redrawn... The joys of early adoption :\
I was just searching to see if anyone else was experiencing this. I get the same over here.
I had similar issue. Something ate all my RAM, but it wasn't listed in 'running apps' in settings . Reboot fixed it
well folks, the sooner you go onto custom ROM the better. I tried ignoring these (and several other issues you are about to encounter) but the list was getting endless
I've bigxie and franco kernel now (4.0.3), not difficult to install, and now most of the STOCK issues are gone...
Is anyone having any issues with their 2013 N7 freezing? I've had it completely freeze up on me once, and several time just today it has had major input lag (like 2-3 seconds later) or would just not accept input. It hasn't been localized to any particular app.
Is this a common problem? Should I just go exchange mine?
Seems like a software issue which can be easily remedied.
Username invalid said:
Seems like a software issue which can be easily remedied.
Click to expand...
Click to collapse
When I first got my new Nexus 7 I did notice some "freezes" and unresponsiveness. Touches that would go unrecognized (links in the browser, back button). did a factory reset and watched it in case I decided I needed to exchange it. But it is seemed to improve and I rarely run into the freezing.
I've so far not returned/exchanged it, but an still keeping an eyes on it.
I have most certainly experienced a heavy freeze period while typing on the onscreen keyboard. While typing in all the credentials on first set-up I experienced moments of almost 20 seconds of non-response, followed by all input entering as if it was lagged out network style.
Rooting and flashing a new rom, this has yet to happen. This is why I love Android so much... its community knows that it is Unix and treats it as such.
Yea mines freeze sometimes
Sent from my Nexus 7 using Tapatalk 4 Beta
yeah sometimes mine locks up for like a good 15 seconds.. hitting the power button doesn't shut the screen off either.. then when it unfreezes, it does everything I did lol like pull down the bar, hit home, and the screen off
Sent from my Samsung Galaxy S4 using Tapatalk 4 Beta
jayochs said:
yeah sometimes mine locks up for like a good 15 seconds.. hitting the power button doesn't shut the screen off either.. then when it unfreezes, it does everything I did lol like pull down the bar, hit home, and the screen off
Sent from my Samsung Galaxy S4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Same issue. I think I will factory reset it + install cleanrom with the jassy kernel and see if it helps. If not, I will swap it. I love this thing! Its getting more love than my ipad atm, but I think I can make room for both of them in my already-gadget-overloaded life lol.
Gabik123 said:
Is anyone having any issues with their 2013 N7 freezing? I've had it completely freeze up on me once, and several time just today it has had major input lag (like 2-3 seconds later) or would just not accept input. It hasn't been localized to any particular app.
Is this a common problem? Should I just go exchange mine?
Click to expand...
Click to collapse
I have seen this several times with the Swipe keyboard. Since going back to SwiftKey it has not happened.
Gabik123 said:
Same issue. I think I will factory reset it + install cleanrom with the jassy kernel and see if it helps. If not, I will swap it. I love this thing! Its getting more love than my ipad atm, but I think I can make room for both of them in my already-gadget-overloaded life lol.
Click to expand...
Click to collapse
I was wondering if its really the kernal that's causing the freezing. My N7 2013 right now freezes after about 15 minutes of turning it on, and the only way to unfreeze is by holding down the power for 10 seconds. My tablet will constantly do this after each turn on, but once I placed it in safe-mode there is no freezing. I am thankful that mine doesn't have the touch screen issue though! but this freezing problem is really driving me bonkers.
I nodded off for a few minutes the other day when I had FBReader up and when I woke up and tried to exit it was non-responsive. I get the impression FBReader forces the screen to stay on, but perhaps everything else goes to sleep anyway? That's the only freeze I can remember seeing.
So I am having this problem since 4.4.3 and 4.4.4 update. Once or twice a day the screen won't respond to touch. Should I use a custom kernal or this might be a hardware problems.
Sent from my Xperia U using XDA Free mobile app
Ameer Shimoga said:
So I am having this problem since 4.4.3 and 4.4.4 update. Once or twice a day the screen won't respond to touch. Should I use a custom kernal or this might be a hardware problems.
Sent from my Xperia U using XDA Free mobile app
Click to expand...
Click to collapse
How do you fix it when it happens? Do you have to restart? Does the touch fail or does the tablet freeze?
Honestly not very sure what you could do, besides maybe trying a factory reset? That would work if a software problem.
What about cleaning it and removing any screen plastic guard.
U can say it freezes then I have to restart it. This is happening after two factory resets.
Sent from my Xperia U using XDA Free mobile app
Firmware fix: http://forum.xda-developers.com/showthread.php?t=2428133, read and follow the op very carefully.
...if it does not help, or you think it may be internal:
http://forum.xda-developers.com/showthread.php?t=2535835
mdamaged said:
Firmware fix: http://forum.xda-developers.com/showthread.php?t=2428133, read and follow the op very carefully.
...if it does not help, or you think it may be internal:
http://forum.xda-developers.com/showthread.php?t=2535835
Click to expand...
Click to collapse
OK I'll try..
Sent from my Xperia U using XDA Free mobile app
Same issue here, I think.
Just purchased a refurbished Nexus 7 (official factory refurbished) from Amazon. My touch screen works great for a day or so, but eventually touch stops working altogether and sometimes requires a hard-reboot (holding the power for 10-seconds). Downloaded a touch screen test app which works great (even with ten fingers on the screen), tracking well on all parts of the screen. It's just like the touch atrophies over time until it stops working.
First thing I did to the tablet after getting it was to unlock the bootloader and load stock/rooted 4.4.4. Is there some way to update the touchscreen firmware that I'm missing?
I don't want to open this thing up and muck with the hardware for fear of damaging it. I'm holding out hope that there is a software fix, because rebooting fixes it right up.
nebhead said:
Same issue here, I think.
Just purchased a refurbished Nexus 7 (official factory refurbished) from Amazon. My touch screen works great for a day or so, but eventually touch stops working altogether and sometimes requires a hard-reboot (holding the power for 10-seconds). Downloaded a touch screen test app which works great (even with ten fingers on the screen), tracking well on all parts of the screen. It's just like the touch atrophies over time until it stops working.
First thing I did to the tablet after getting it was to unlock the bootloader and load stock/rooted 4.4.4. Is there some way to update the touchscreen firmware that I'm missing?
I don't want to open this thing up and muck with the hardware for fear of damaging it. I'm holding out hope that there is a software fix, because rebooting fixes it right up.
Click to expand...
Click to collapse
Look 2 posts up from yours.
mdamaged said:
Look 2 posts up from yours.
Click to expand...
Click to collapse
Oops - I looked at the link to the hardware fix, but not the firmware fix. Thanks, I'll give this a try first.
Firmware fix above seems to have alleviated the issue for me. At least I haven't seen the issue over the last several days, which is good news. Hopefully that holds up over the long term. :good:
Like several others I had Netflix playing last month and had it switch to a tiny screen in the upper left corner. Simply rebooting the box took care of it and I think it happened one or 2 more times then went away completely.
2 days ago it appeared again,cthen again and again. I needed to exit Netflix to fix it each time. Remembered someone said disabling autoplay worked so I did that but it didn't work. EVERYTIME you play a title the next title displays as a tiny screen. Clearing data and rebooting doesn't fix it even temporarily. It happens on both aftvs. They run preroot 51.1.4.0 and have been for awhile.
Does anyone else suddenly have this issue? Has anyone got a fix? Its a weird one--my best guess is an orientation glitch where it thinks its on a device with a much smaller screen like a phone.
Edit--not a valid theory. What's happening is at the end of an episode (credits rolling) Netflix will minimize the show to the upper left. That's where the glitch occurs. It just keeps playing video in that screen. If you stop it before that screen appears the video plays fine. We pay for this. I think we should have a little room to make tiny modifications (like disabling the tiny screen view) That would be useful instead needing to wait for bug fixes.
KLit75 said:
Does anyone else suddenly have this issue?
Click to expand...
Click to collapse
Yep. Two chats and three phone calls later, Amazon is supposed to deliver another Fire TV tomorrow. But then, I was seeing other oddities as well (blue screen, skipping, not responding to remotes, ...).
wellersl said:
Yep. Two chats and three phone calls later, Amazon is supposed to deliver another Fire TV tomorrow. But then, I was seeing other oddities as well (blue screen, skipping, not responding to remotes, ...).
Click to expand...
Click to collapse
Thanks! That might not be an option for me (well it is but I risk getting one without rootablefirmware) Mine is stable otherwise. I have to say though I'm a bit freaked out over what I'm hearing--between this forum and another site, I count 4 people in 24 hours complaining their aftv won't power on. My newest one is less than 2 months old. I'm hoping that issue is related to newer firmware and I don't have a ticking time bomb.
KLit75 said:
Thanks! That might not be an option for me (well it is but I risk getting one without rootablefirmware) Mine is stable otherwise. I have to say though I'm a bit freaked out over what I'm hearing--between this forum and another site, I count 4 people in 24 hours complaining their aftv won't power on. My newest one is less than 2 months old. I'm hoping that issue is related to newer firmware and I don't have a ticking time bomb.
Click to expand...
Click to collapse
You're rooted right? I assume you have CWM installed. Here is my suggestion. Completely rid your FTV of Netflix. Clear cache/data from the app, then uninstall it. Reboot to CWM and clear both cache and dalvik, then reboot. Install Netflix and see if that helps. As for the ticking timebomb, I fear the same thing. Mine is running near perfect and I would absolutely hate to start from scratch again.
xm41907 said:
You're rooted right? I assume you have CWM installed. Here is my suggestion. Completely rid your FTV of Netflix. Clear cache/data from the app, then uninstall it. Reboot to CWM and clear both cache and dalvik, then reboot. Install Netflix and see if that helps. As for the ticking timebomb, I fear the same thing. Mine is running near perfect and I would absolutely hate to start from scratch again.
Click to expand...
Click to collapse
Thanks. I try your suggestion when I can and report back here.
I'm really hoping its combo of defective boxes and new firmware causing those aftvs to die. I plan on installing android whenever there's a stable release. Had enough of fire is and the drama. Running a lollipop ROM on 2012 KFHD with overclocked kernel and its just night and day--fast, responsive LOADED with features and minimal bugs.
KLit75 said:
Thanks. I try your suggestion when I can and report back here.
I'm really hoping its combo of defective boxes and new firmware causing those aftvs to die. I plan on installing android whenever there's a stable release. Had enough of fire is and the drama. Running a lollipop ROM on 2012 KFHD with overclocked kernel and its just night and day--fast, responsive LOADED with features and minimal bugs.
Click to expand...
Click to collapse
In my experience you can't rely on clearing the app data alone. Sometimes things persist in the system cache/Dalvik. It looks like progress is coming along on CM12. That would be awesome to have!
KLit75 said:
I count 4 people in 24 hours complaining their aftv won't power on.
Click to expand...
Click to collapse
Are there any indications why? Optimistically, it's just the wall wart. More than one decent device has been forced to wear the bag of shame for the lack of a good power supply.
xm41907 said:
You're rooted right? I assume you have CWM installed. Here is my suggestion. Completely rid your FTV of Netflix. Clear cache/data from the app, then uninstall it. Reboot to CWM and clear both cache and dalvik, then reboot. Install Netflix and see if that helps. As for the ticking timebomb, I fear the same thing. Mine is running near perfect and I would absolutely hate to start from scratch again.
Click to expand...
Click to collapse
UPDATE--This suggestion above worked! I wiped Dalvik cache and the tiny screen went away. I do this fairly regular on my phone with TWRP. Don't know why it never occurred to me here. Probably smart to do this every once in awhile if you have CWM, at the very least it can't hurt. Thanks again!