I need some help from more experienced Android users. About a month ago I rooted my Kindle Fire and installed 4.1 Jelly Bean as my new OS. Over the past week my keyboard has been constantly crashing and I have no idea why. Whenever I type in a word box the keyboard will randomly disappear and I will have to select the box multiple times for my keyboard to return. I installed Go Keyboard and it didn't help. Do any of you have an idea of what it might be?
Full wipe minus your external storage/sdcard and reflash Rom.
Thepooch said:
Full wipe minus your external storage/sdcard and reflash Rom.
Click to expand...
Click to collapse
I figured that would be the solution. I cleared my cashes and installed the newest update. Everything seems to be working a lot better now.
Related
I'm having some major connectivity issues after flashing to Jelly Bean (the one posted by bigxie).
Google Talk doesn't work. The app opens but I (and all my contacts) stay offline even after it says "signing in".
Google Now doesn't work at all by swiping up from home button (I don't see any cards), but I can do searches by pressing mic button in search bar.
Sync isn't working unless I go into my gmail app and press refresh manually.
Can't download apps from Play I get message: Error processing purchase. [DF-BPA-09]
I think it has to do with my wifi and signal bars are grey instead of blue (not connected to google server). I'm not sure what else I can do to get the connection. I can still use internet browsing (on both wifi and HSPA+) and send SMS messages
I was thinking of giving one of the other posted ROMs a try. I just want stock Jelly Bean to work
Currently: "Jellybean 4.1 JRN84D Stock, Rooted, Busybox, Deodexed + New Radio!" from bigxie
Baseband: i9250UGLC1 (I also tried XXLF1)
Bootloader: JRN84D
Kernel: 3.0.31-ge8de0e2
What else can I try or do to get connectivity working?
Did you do a wipe after installing? I haven't had even a remote sign of a problem on my GNEX since flashing Jelly Bean.
asawoszc said:
Did you do a wipe after installing? I haven't had even a remote sign of a problem on my GNEX since flashing Jelly Bean.
Click to expand...
Click to collapse
Hmm I did my wipe before installing the ROM. I suppose that makes the difference then eh (sorry only 3rd ROM I've ever flashed)?
If I just go into recovery now and do a factory reset I would keep my JB install right (along with radio/root fix)? Then I would just have to reinstall all my apps via titanium backup/restore?
I'll differ answering to someone with more knowledge/experience than myself. But once on any version doing a factory wipe/reset will just erase your data. You'll just get a clean version of Jelly Bean.
Did you flash this one?
Had the same thing. Flashed the JB-radio again, wiped cache and dalvik, reboot and had my blue bars back.
I need advice about updates received after installing Jandycane Version 1.8.0
I have just installed Version 1.8.0 (jandycane_otter-v1.8.0_0xD34D.zip) and gapps-jb-20120726-signed.zip on my rooted 1st generation Kindle Fire.
No problem, everything went okay. http://forum.xda-developers.com/images/smilies/laugh.gif
However shortly afterwards I got GooManager update notices. I clicked on these and got the following downloads:
jandycane_otter- 20121020.0xD34D.zip
and
gapps-jb-20121011-signed.zip (downloaded twice for some reason?)
As a rookie I am unsure if I should flash these updates – unsure if the downloads are correct – as I thought Version 1.8.0 was the last version and the corresponding link for gapps the last version, and these I have just installed? http://forum.xda-developers.com/images/smilies/confused.gif
Or are there separate updates that are not listed – and these updates are correct and I should flash them? http://forum.xda-developers.com/images/smilies/confused.gif
I would be very grateful for advice on this, my thanks
Flash away my friend the updates are good just make sure you wipe before flashing.
Sent from my Amazon Kindle Fire using xda premium
Procedure clarification for updates
soberarmy said:
Flash away my friend the updates are good just make sure you wipe before flashing.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Ah, okay, thanks very much for the reply and answer. But before I do this I had better check about the “wiping”.
Do I have to wipe "everything" again?
- Cache and Dalvik Cache (and also a Factory Reset) ? Or just one of these?
Then I run the 2 updates?
Can you please confirm exactly what I have to do – don’t want to go messing it up now I have got this far!
And I would assume that every time there is an update notice from GooManager I can trust it – even if these are not listed on the jandycane page, and that I also have to do the same wipe and steps each time?
Another question while I am here. I installed a couple of apps, but I keep getting a message when I open the app that says: “no more room on this home page” (or something like that)? Any ideas, experience of this? (but maybe not so important)
and thanks
Great stuff
Aarief Zee said:
Only wiping cache and dalvik cache is required in this case. Some people will insist on doing a factory reset, but if you're flashing a newer version the same ROM then it's an optional step. Try this first, and if things go a bit haywire then only do it again with a factory reset.
Is this an error when opening the app or right after installing it? If it's the latter then go to your Play Store, go to Settings and tick off "auto add widgets".
Click to expand...
Click to collapse
Thanks, I really appreciate your, and all the other, help I get. I’m like a Jelly bean myself when it comes to doing this stuff – always quivering!
Deleted just the Cache and Delvik cache- that worked – I’m updated – GREAT! Just to be sure I also made a backup first - don't know if this was right, but!
The app thing was only just after installation – but I haven’t tried it yet with this update.
One other thing I notice with the Jelly Bean is that it sometimes (quite often) goes very fast into sleep mode – sometimes I don’t even get time to put in my password and it is already asleep. The screen setting was at 1 minute before the update, I had changed it to 2 minutes, but even so it went into sleep quite fast! Certainly quicker than either 1 or 2 minutes! I notice that the update is the same – but I have not messed about with it yet. I don’t know how others experience this, and what setting time they put in?
However I am really happy with my new KF, here in Germany it was useless to me before (did not know this before I bought it). But thanks with all your help I now have a great Android, Thanks so much!
App issue on newly installed and updated jandycane JB
I am really happy with my KF after the jandycane JB install (and update) – My deepest thanks to everyone for this!
I am having a apps issue though, sometimes I get the message: “unfortunately (name of app) has stopped” ?
Usually the app starts the next time though, but now “Amazon Kindle App” just keeps giving me the same message, and won't open at all, or only opens very briefly before the message comes?
I was getting this “unfortunately (name of app) has stopped” message before I first downloaded and tried Kindle app.
As for the Kindle app, I am not sure if I have caused some kind of conflict issue by downloading other eBook readers (Play books, Aldiko, Free kindle books, Kobo)?
Has anyone else had this experience? Know the solution?
*** AMAZON KINDLE APP was a conflict issue!!!! When downloaded app Google Play Books I allowed it to synchronize with other readers - Kindle app clearly does not like this at all and won't work!!
Hi - I got everything installed and set up just fine on my Kindle Fire, with one glaring exception - I cannot get the Google Apps to install. Whenever I try to install them, I get a message that the zip files could not be extracted...but the zips for the ROMs install flawlessly. I have sideloaded the apps as instructed elsewhere in the forums, but anytime I launch a Google app, I get the login screen, it hangs for a few minutes, and then gives me a message that my "phone may not be provisioned for data services". WiFi is fully functional, and nothing else ever gives me a networking error.
I have tried multiple Google app file bundles, multiple Google system framework APKs, and cannot get past this problem. I have cleared the cache and the Dalvik cache before every installation, et al.
Any help would be appreciated - the work on this is absolutely incredible. The fact that I am able to use a Kindle Fire that my daughter tired of after a month for an Android tablet at work is amazing. Exchange works great - it would be even better if I could get Google Play and the associated Google Apps running though. Thanks a million in advance.
What ROM are you using? Which TWRP version are you using?
.....when you hit the walls of sanity, you have no-where to go.....
ROM / TWRP Kindle Fire
guitarman2010 said:
What ROM are you using? Which TWRP version are you using?
.....when you hit the walls of sanity, you have no-where to go.....
Click to expand...
Click to collapse
Guitarman - I am using Hashcode's ROM and TWRP 2.2.2.1. Thanks again for any help this!
gdoggg said:
Guitarman - I am using Hashcode's ROM and TWRP 2.2.2.1. Thanks again for any help this!
Click to expand...
Click to collapse
I had the exact same problem a week or two ago. I ended up wiping everything (except SD partition), re-flashed the ROM and had success. I was getting the same message when trying to connect initially to Google. I'm a big fan of starting over fresh to solve problems lol.....after the fresh flash I side loaded the Gapps I wanted. The ROM was cm10 alien and I also use the same TWRP.
Sent from my rooted SCH-R880 POS
Merry Xmas to all
My Kindle Fire 1st Generation is rooted and now boasting JB 4.4 ROM. Everything worked perfectly until last night when Kindle App stopped working ("Unfortunately, Amazon Kindle has stoped" message). I have tried to reinstall the ROM, wipe the cache and dalvik, install 4.4.2 ROM, downgrade to 4.3 ROM and nothing has worked. Everything else is working fine.
Any ideas or similar experiences?
Cheers everybody.
Dr Feelgood
Yes, I had the same problem, but I was able to get it to work by downloading Build.prop Editor from the Play store and using it to change the ro.product.manufacturer line from Amazon to Samsung. I'm guessing Amazon intentionally stop their non-stock apps from working on Amazon devices to avoid people using non-stock apps by mistake, but hopefully changing this workaround will work for you.
cklass said:
Yes, I had the same problem, but I was able to get it to work by downloading Build.prop Editor from the Play store and using it to change the ro.product.manufacturer line from Amazon to Samsung. I'm guessing Amazon intentionally stop their non-stock apps from working on Amazon devices to avoid people using non-stock apps by mistake, but hopefully changing this workaround will work for you.
Click to expand...
Click to collapse
I, too, had the same problem, and your fix with Build.prop editor worked for me! Thanks, thanks, thanks.
There is also a "change to nexus7" zip file in the cm11 thread that probably does the same thing. This is nice because you just add it into the rom/gapps flash. The cm11 rom was the last one I tried to fix this issue before I found "the fix". Now I have to go back and setup HellFire because I haven't found a way to remove the lock screen in CM11.
DrFeelgood75 said:
Merry Xmas to all
My Kindle Fire 1st Generation is rooted and now boasting JB 4.4 ROM. Everything worked perfectly until last night when Kindle App stopped working ("Unfortunately, Amazon Kindle has stoped" message). I have tried to reinstall the ROM, wipe the cache and dalvik, install 4.4.2 ROM, downgrade to 4.3 ROM and nothing has worked. Everything else is working fine.
Any ideas or similar experiences?
Cheers everybody.
Dr Feelgood
Click to expand...
Click to collapse
It turns our non working Kindle app was the least of the problems I had. Shortly after that problem I started getting message SystemUI stopped working and then the screen would flash. 5 or 6 reinstallments, full wipes and the likes later I realised that the ROM was the culprit as after installing HellKat 4.4.2, problem seems to be gone. As for Kindle App, I think problem was latest update which was not compatible with 4.4. I stopped the app from getting new updates and its working for now. Had a glance in quite few Kindle related forums and its seems people agree with that as so many complained of app stoping after getting the update.
As for now, Kindle Fire is happily running HellKat 4.4.2 with lovely red theme. We will see how it goes.
GodSpeed
So I just installed CM 10.1.3 and now my kindle app, amazon mp3 app and HBO go apps all crash. I had previously changed the build.prob file to enable access the HBO go, but the amazon apps always worked fine. I just tried to edit build.prob andi I keep getting told that the file is read only. I have tried root explorer and file expert. Any ideas?
cklass said:
Yes, I had the same problem, but I was able to get it to work by downloading Build.prop Editor from the Play store and using it to change the ro.product.manufacturer line from Amazon to Samsung. I'm guessing Amazon intentionally stop their non-stock apps from working on Amazon devices to avoid people using non-stock apps by mistake, but hopefully changing this workaround will work for you.
Click to expand...
Click to collapse
This also resolves same crash on Rooted Kindle Fire (1) running 4.3.x
Thanks!!
app crashes
Found this
Kindle app crashing has a workaround: http://forum.xda-developers.com/showthread.php?p=48928053#post48928053
Short answer:
download Build.prop Editor from the Play store and use it to change the ro.product.manufacturer line from Amazon to Samsung.
Testing now...
I have a Kindle Fire HD 8.4.6, rooted with Hashcodes 2nd Bootloader guide and TWRP and Seokhun's excellent instructions. I am having a problem with the soft navigation keys consistently disappearing upon booting up. I have since restored my origional backup files, but retain the 8.1.4 bootloader and SuperSU.
Can someone help me retain the disappearing navigational keys?
When you came to cm from amazon os did you factory wipe? Also try clearing your dalvik cache and cache from twrp's wipe menu. If that doesn't work I'd redownload the ROM and check it's md5sum before flashing.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thanks for your quick reply, Stunts. You and Hash and Seokun and the other devs are amazing.
What I think happened was that I experienced the disappearing soft keys (perhaps after downloading some software that tried to automatically clear memory and space ) and loaded a more user friendly android launcher, while trying to retain the amazon interface for my wife, which integrated with the recovery partition or root system of the boot.
I believe I resolved this (after 6 successful boots after 0 for 5) using Hashes 8.4.3 update @ http://forum.xda-developers.com/showthread.php?t=2142241. I am guessing that file updated the bootloader, which seems to have resolved my initial problem.
However, the "Upgrade Your Kindle " box is still grayed out. So, If I did want to go back to 8.4.6, what would you suggest?
Ah that button is usually greyed out, it's meant for if you follow amazon's instruction on their site and put their update file on your sdcard, if you do that then it would let you hit it. That method should still work I believe if you want to update it. Keep in mind that would unroot it and possibly get rid of custom recovery, but it's been a while so I don't remember if it gets rid of custom recovery, then again I just woke up and I haven't used amazon os for the better part of a year now.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I followed Amazons directions, placed the .bin file in internal memory, but the "Upgrade Your Kindle" box is still grayed out.
Did u ever at some point disable ota's?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
You guys are awesome. After allowing OTA updates, with the update .bin file in internal memory, the Update My Kindle button was activated. However, 8.4.3 with the Holo launcher seems to be working great. Thanks so much!