I have a rooted Kindle that I have restored with the methods in the stickied thread, and recently whenever starting any launcher other than the stock Amazon one, the launcher instantly crashes with a "Force Close" window. The only launcher that does not do this is GO Launcher - that opens for a total of 2 seconds then restarts itself. I have no idea what could be causing this - any help would be appreciated!
my gf's KF does the same thing, mine no.
Same here with Go Launcher, uninstalled, and installed ADW I bought on these 10c google promo, and it's working fine.
Feels like I'm on Android now.
Not me sorry for your problems I love my go launcher wouldn't change it for a thing.
Related
Thanks in advance all who give time to explain things.
Here goes:
Problem: NC always launches org launcher and I have to search for zeam launcher
I used [NC][1.2][1.3] ManualNooter 4.6.16 to set me up. NC is 1.3, did the updates and all, fix permissions, and it booted up and loaded just like the forum said. After going to sleep and waking up, it just stays on the NC home's launcher. I have to search and find Zeam Launcher or any app. Even after a shut down and reboot, it will go to the home launcher. I looked to set zeam as the default launcher, as one does on a smartphone, but that isn't an option. I tried to set the N key for short and long press, for ZEAM launcher, but that doesn't work either. The N button just puts me back to home launcher.
You can try this: http://forum.xda-developers.com/showthread.php?t=1356206
It's for the Nook Tablet but I'm sure it will work.
---------------------------------
Sent from my LG Optimus V using Tapatalk
Hey all,
Weird thing just started happening yesterday on my Nexus. Whenever I power on the tablet, I am prompted for the default launcher choice. This shows up on the lockscreen, so somehow the unit is forgetting that adw is my default launcher. Once I make the choice, all is good. Just bugs me that I have to do that everytime.
I am rooted, and used that to change my screen density settings to get a real tablet look rather than the enlarged phone look. No problems there as this just started yesterday. I have installed home switcher and that did not do the trick. Could it be a conflict with a recently installed app?
Any insight or ideas would be greatly appreciated!
I'm not sure but things you can try:
Goto adwlauncher app settings and unset defaults and sleep tablet, and reset defaults on the lockscreen with always
Convert adwlauncher to a system app and repreform the above. (Requires root) may not help, but I believe this may cause adwlauncher to run quicker and not throw anr's although I haven't seen 1 anr on my nexus 7 yet!!
Disable the stock launcher. Settings, apps, all, launcher, force stop, disable. (No root req'd)
You can also try clearing the defaults here first to see of it helps.
Sent from my Nexus 7 using Tapatalk 2
Thanks for the reply Joe!
Your ideas prompted a little targeted searching and I discovered I could 'freeze' the stock launcher (disable it) using Titanium Backup. My Nexus booted right into ADW as I wanted.
Thanks!
Sent from my Nexus 7 using Tapatalk 2
First off, I am a NOOB. So take what I did with a grain of salt, it may not be right. If I could get a senior member to check this out as well. I installed 2 launchers, go launcher hd and adw launcher ex. Then installed wallpaper wizardii, now I can use my pictures to set the background. You have to use "no scroll" in the settings. I am still playing with the functions, and it looks better on go launcher hd than adw launcher ex, but it works.
Rooted kfhd , step by step set up.
Do you have to be rooted to install launchers? I am un rooted and it never shows up in my app list. I can side load just fine, just not launchers. Tried Nova and go had.
TheDoolster said:
Do you have to be rooted to install launchers? I am un rooted and it never shows up in my app list. I can side load just fine, just not launchers. Tried Nova and go had.
Click to expand...
Click to collapse
if you are rooted, if you move the apps to system/app you can change there permissions. This allows for you to change the launcher to any launcher by default. So that when you press the home button you don't have to be forced back into the amazon launcher. Completely different from side loading the apps. I highly recommend it if you prefer a different launcher like me.
iMJets said:
if you are rooted, if you move the apps to system/app you can change there permissions. This allows for you to change the launcher to any launcher by default. So that when you press the home button you don't have to be forced back into the amazon launcher. Completely different from side loading the apps. I highly recommend it if you prefer a different launcher like me.
Click to expand...
Click to collapse
Ok thank you, I did not know that I had to change the permissions and file location. I am going to root my Fire tomorrow and then I will do that.
iMJets said:
if you are rooted, if you move the apps to system/app you can change there permissions. This allows for you to change the launcher to any launcher by default. So that when you press the home button you don't have to be forced back into the amazon launcher. Completely different from side loading the apps. I highly recommend it if you prefer a different launcher like me.
Click to expand...
Click to collapse
Word to the wise--DO NOT set your new launcher as default until you are very sure it is working ok. You can get stuck in the boot loader and believe me it is no fun!
Ok I have rooted it and installed apex and it is very nice. Everything is working smoothly. Now i might go make a theme pack to make it look like stock ics. What are the dangers of modifying framework-res.apk?
Chelle01 said:
Word to the wise--DO NOT set your new launcher as default until you are very sure it is working ok. You can get stuck in the boot loader and believe me it is no fun!
Click to expand...
Click to collapse
that what I've meet yesterday, it make me scare. Go laucher not working, it show not working, it show stop, then press stop, and stop again & again I can't get in to anything. Luckily, there is a star sympol, which you can get in to Silk browser, after that you can scroll down notify , get in to setting and clear Go laucher default.
Sent from my KFTT using xda app-developers app
hungcolin said:
that what I've meet yesterday, it make me scare. Go laucher not working, it show not working, it show stop, then press stop, and stop again & again I can't get in to anything. Luckily, there is a star sympol, which you can get in to Silk browser, after that you can scroll down notify , get in to setting and clear Go laucher default.
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Although I can only make out half of what you wrote - I can confirm I too had this problem with Apex ("Apex has stopped working"). Luckily, I was able to get into my email through the favorites star and clear defaults. I dont know why, but the Apex launcher will not work for me.
caponea6 said:
Although I can only make out half of what you wrote - I can confirm I too had this problem with Apex ("Apex has stopped working"). Luckily, I was able to get into my email through the favorites star and clear defaults. I dont know why, but the Apex launcher will not work for me.
Click to expand...
Click to collapse
Had the same problem with nova launcher, had to change to Go launcher
Blurry kindle wallpapers
For anyone whose having a trouble finding a good unblurrywallpaper for you Kindle Fire (if using a launcher):
Search the Google Play store for an app called Wallbase
Once installed, go to Settings --> Resolution --> Select "2560x1600"
Find a wallpaper you like and set it as you wallpaper. WALA! You can also save it so you can ur wallpaper while offline via Wallbase.
I hope people who have problems with blurry Kindle wallpapers get to see this. I was surprised when I found this out! GOOD LUCK!
I changed to 305ppi working fine
then I revert back to 149 (the device's native) now my launcher would force close all the time.
Now I can't launch anything, can't even change back
what could I do.... please help!!!
I had a problem where the launcher would crash repeatedly and I'd have to hit Ok or something. The system did work though so I was able to navigate to settings, while constantly hitting OK (to accept my launcher had crashed again).
In settings I was able to remove the Set as default option from the launcher and so the next time I hit Home I was asked to select a launcher - Here I chose another one and all was OK.
I installed ADW launcher and it launched just fine, but the stock browser, holo, go, and the likes are not, ADW is the only one
Also I couldn't get Chrome to run anymore, constantly crash, just like the stock launcher....
The icon in ADW is also 75% smaller, which I have no clue to fix or reverse this
grr
I noticed on the android 11 final version, and with a fresh install that when setting a home launcher that ain't the OnePlus original launcher. after different amount of time the when going to home, the phone keeps asking for the "what app to set to default"
So with the OnePlus launcher it sticks and won't ask ever again for default launcher.
But with 4 different launchers, Microsoft, Nova and more, after second and more, up to 20 times going to home screen, it asks for what app to set to default launcher?
Any one more than me experiencing this issue?
It's quite annoying to keep seeing the default launcher.... So please write here if you having this issue.
There's another thread regarding that issue and I've posted an answer: https://forum.xda-developers.com/showpost.php?p=83684893&postcount=5.
I had this problem too. I solved it by setting Nova Launcher as default in the Nova Launcher settings... Afterwards i can see it in my OP8pro standard apps as well...
Cheers
Clark
I did that too. However, sometimes the machine switches to the OP Launcher - it must be some kind of error in the system.
Have Nova as default and still watching 11 behavior...
Deliting the launcher and reinstalling, then first time it says would u want nova launcher as default say yes and solved at least for me. Hope messages from developers
I don't know what happened to my phone, but since a few weeks I didn't experienced this issue anymore.