Hello, I rooted my Kindle Fire very successfully and installed the Jelly Bean OS and GAPPs. Added Go Launcher EX, have access to most everything except for two minor issues and I'm not sure if they would have the same root cause or not.
1. When downloading/installing Kindle for Android, I get an error: Unknown error code during application install "-24". I did complete a factory reset and wipe all memory (cache, davilek) during each flashing process and this is the only app that has this error.
2. Google Search Widget with Go Launcher Ex Transparency, without transparency or with the default search widget or button force closes as well as Chrome for Android. I can use the built in browser.
Overall, very happy with the changes and using the Jelly Bean OS (my Galaxy Nexus and Kindle match now). These are minor.
Android Version: 4.1.1;
Release codename: REL;
API LEVEL 16;
CPU AB12: armeabi;
HARDWARE: omap4430;
Device: Otter
ID JRo03C
Many hours were dedicated to setting it up and wiping/factory reset would be a bummer at this point. Any work-arounds or updates in the pipe?
Thanks,
Jan
Related
Greetings,
(Today is Monday, 07.01.2013 and this post describes my question about using Kindle Fire 2 with apk-downloader 1.4.0 + Google Chrome 24.)
I want to apologize if this is a well known question, but I could not find anything relevant between the loads of info about Kindle Fire 1 and Kindle Fire HD. The question is: is it possible to use the last version of APK downloader (1.4.0) with Chrome 24 or 23 to download apks from Google Play for Kindle Fire 2.
I tried to follow the steps, described on the author's page but ultimately I failed. Here's what I did.
1. I did clear install of Windows XP in Virtual PC (in case the software turned to be malware)
2. I installed the last version of Chrome (24.xxx).
3. ...downloaded apk-downloader 1.4.0 and dragged it onto the extensions page of chrome, which initiated installation of the extension. Went ok.
4. ...ensured that one of my two ancient Google accounts (from the time before phone registrations and etc...) is accessible with the proper username and password (no google wallet of whatsoever personal information in it).
5. Downloaded Redphx's Device ID application via friend's phone - and installed it on kindle with Easy Installer (found on amazon appstore).
This was the first glitch - the device id application failed to show any device id. So I went on to 6
6. I found AIDE on Amazon Appstore and wrote a small application to retrieve the value of Secure.ANDROID_ID. I did that, because I read in some post that TelephonyManager.getDeviceId(); returns null on tablets that do not have cellular connectivity.
7. Entered the account info and the AndroidID into the plugin and went on Google Play. Whenever I'm on an app download page, the plugin icon appears, but also in the webpage under the application name I get "You don't have any devices." Clicking the plugin button in urlbar fails with error 400 "Bad request"
I guess, that either the android_id is not what google wants or the whole thing with apk downloader is a scam. Do You have any ideas? Some clever algorithm to generate fake device ids maybe? My friend's phone (Samsung Galaxy II) seems to download apks that mostly work when installed on my kindle. But I hate to be obtrusive enough to ask for his device id.
Here is a secondary question. Everybody seems to hide their device_id. If someone has Your device_id can he do something nasty?
.
Your question can best be addressed in the proper forum http://forum.xda-developers.com/forumdisplay.php?f=1789 .
I forgot to launch XMBC before freezing the KFTV launcher, and now my system's just stuck on the amazon logo. Luckily I've installed the CM and launcher so can get an IP address and the recovery boot menu. Anyone know the command to re-enable the KFTV launch? I know the updates are: pm enable com.amazon.dcp - but I imagine there's a similar command for the KFTV launcher.
edit: I can't get into the root of the Android system, only "~ #" - so I can't run the command to view disabled services/apps. I've already tried to install the bueller custom ROM again but that didnt help. Do I need to factory reset?
In the end I factory reset the box, disabled the update sites in my router, and rebooted. back to normal operation. FYI - re-installing a bueller ROM didn't work.
Hi there...
I have just factory reset my Nexus 5X after installing the 6.0.1 January update and after running the initial setup wizard, I now have a "Device Policy" app in my launcher which wasn't there before.
Did something go wrong during setup or is this normal in the latest update?
Side note: My default ring and notification tones were set to none after setup, this is strange... did not restore anything
Update:
I did another factory reset and now everything is fine. No Device Policy app, ringtones are set correctly.
Seems that interrupting the initial App installation (Like Google Docs etc.) also interrupted other configuration steps or whatever...
Error message:"Unfortunately, system ui has stopped."
All I did was unlock my galaxy tab 3 lite and the error appeared. Also I gone onto the recovery menu and tried to wipe cache although I just receive an error and my tablet turns back on.
Can someone help????!!!!!!!
Me too, when i hold down home button for recent apps switcher.
BUT- it works in landscape mode!
Seemed to start after recent Google update.
Rooted 310 with bloat removed, Google Now launcher on Touchwiz.
It is a google error. They have tried to add search functionality to recent apps screen. I would just uninstall updates for google search app.
What will happen if I do uninstall google apps updates?
After months of trying I managed to change launcher on RKa701 device.
As owners of this device already know, another launcher can be installed on this device but you cannot set it as default because it will stuck, or wont launch or will not be displayed correctly. It simply conflicts with factory launcher and make unit unusable.
Factory launcher is very ugly but the problem with it is not just that , but unit needs it because radio, music, bluetooth and other apps wont work without it. As you can swap factory music app with another one you cant do that with radio and bluetooth.
Im not responsible if you mess something with your device. Proceed at your own will.
So here we go:
1. Root your device with latest kingroot ( i used latest 5.2 version) . Dont worry we will uninstall it later
2.When rooted it will ask for all kind of permission allow
3. With root explorer or some other app go to system/priv app and make a backup of launcher2.apk-copy it somwhere.
4. Download apk file of some launcher (can be any-we wil install our main launcher later) and put it in system/priv app. I used nova and renamed it to "launcher2" just in case. Install nova.
5. reboot or (if you want to uninstall root for good-choose factory reset) . After boot up nova launcher should be loaded instead main launcher. But WE ARE NOT FINISHED.
If you try to start radio, bluetooth or music app you will find that it cant be done because you removed factory launcher. The good thing is it should be booted, but it is not necessary for it to work in the background all the time.
6. So, install launcher2 that you backed up in step 3. It is now installed but it is not system app anymore.
7.Now. If you dont want to stick with nova launcher install the one you will use. I find car launcher pro best one out there.
8. Now, from google play download "autostart and Stay" app from google play. Install it.
9. Set service toggle of "autostart and Stay" to on.
11. In the app settings check "smart service on boot" and "pooling interval" on 5 seconds.
10. By usign "+" sign add launcher2.apk and launcher you choosed to use. On launcher2 make sure that "autostop" on boot completed is choosed and for the launcher you choosed "autostart" and "stay".
11. If you didnt do it already, using system app remover uninstall kingroot.
11. Reboot.
Thats it.
What we did?
With "autostart and Stay" we loaded but then stopped factory launcher and by checking "stay" we ensured that launcher we choose to use cant be stopped in the background by any other process-If you want you can choose "persist" instead of "stay" and set pooling interval on 60sec. It means that after using any other app more than 60 sec , you will be kicked out on home screen, but other apps you started wont be killed. It means that you can start radio or music, choose your track or tune and it will be working in the background even after you have been kicked to home screen. If you want to watch video, just extend pooling interval. 60 sec is enough for everyday use.
Thats it. Bye