Is there a Hero build that also has a non Rosie / Sense UI.
I am looking for the exchange calendar / people / facebook integration client but do not need the Rosie interface it always takes for ever to go back to the home screen when in some of the programs.
Thank you
It doesn't really matter if the ROM has one already, because you can push one in yourself.
Find a theme you like (should be for cupcake) and pull the launcher.apk. You need to push it to /system/app. You can do this using the terminal on your phone. put it on the root of your sdcard and type:
cp /sdcard/Launcher.apk /system/app
Then you should be able to choose the non-touch flo option when you press home. If not go to Settings > Applications > Manage Applications > TouchFlo > Clear Defaults.
Thank you for the input. Every time I try I get a force close. I guess I will keep looking.
Thank you.
most hero ROMs that are released have the stock launcher in them. Unless noted in the OP of that ROM. You can follow AdrianK's instructions for clearing defaults. once you press home again it should give you an option for touchflo3d or for Launcher. choose launcher.
I've attempted this before too, it results in a force close or bootloop.
SolemnWishing said:
I've attempted this before too, it results in a force close or bootloop.
Click to expand...
Click to collapse
Really? I've been running cyrowski's 1.1.1 Sense Hero for the past 3 days with advanced launcher pushed to /system/sd/app_s/ and Rosie removed. No FCs, but rotate is a little slow on the homescreen.
Hi guys i cant use any of the launcher at the google play eg. GO and Nova .. they work just fine but when i press the home button it just goes to the normal phone launcher .. is there a way to make GO the default launcher ??
when you install a second launcher you wil be asked wich one you would like to use when you push the home button.
select the one you want to use and set it to use always, this way it's set as default launcher.
Well. That didnt happen after installation ... it used to work fine before i reinstall the 2.3 again :/
Sent from my LG-P970 using xda app-developers app
medothe1 said:
Hi guys i cant use any of the launcher at the google play eg. GO and Nova .. they work just fine but when i press the home button it just goes to the normal phone launcher .. is there a way to make GO the default launcher ??
Click to expand...
Click to collapse
Did you have tried a home switcher APP there can you see which launcher do you have as default and can change it.
Sent from my HTC One S using xda app-developers app
clear defaults and data of your launcher
download go launcher from playstore
if not, do a factory reset or wipe cache and dalvik cache
Maybe you can arrange the Promt for default launcher to pop again without reinstalling,
you have to go to:
Settings\Applications\All\ (and enter your Default launcher)
then scroll down the screen and reset the Default actions for that app.
That will make the Default Launcher Prompt appear when you hit Home Button.
Hope to be useful, i use roms in spanish so the real Labels might not be as accurate.
Good Luck,
Happy New Year
The ROM I installed on my Eris has the GO Launcher EX as the default launcher, and while I've installed different ones, It seems that the GO launcher is stuck as the default.
Here's the ROM: http://forum.xda-developers.com/showthread.php?t=944430
Has anyone else had this issue? I've tried going into settings and uninstalling it, but it refuses to let me do so.
Use root explorer and manually go in and delete it. Its been a long time since I've used an Eris so I don't know the name of the directory it will be in.
Sent from my DROID BIONIC using Tapatalk 2
dgbowers said:
The ROM I installed on my Eris has the GO Launcher EX as the default launcher, and while I've installed different ones, It seems that the GO launcher is stuck as the default.
Here's the ROM: http://forum.xda-developers.com/showthread.php?t=944430
Has anyone else had this issue? I've tried going into settings and uninstalling it, but it refuses to let me do so.
Click to expand...
Click to collapse
In addition to the above, if you do have another launcher installed, you should be able to go into (from home) settings->applications->manage applications. Tap the "All" tab on the top, and find the entry for "GO Launcher EX". Tap it, then look for the button "clear defaults".
The next time that you hit the home button it should ask you for which launcher you want to use, with a check box control to set that one as the default.
Edit:
I'm working on a batch script to provide a different launcher as one-click script.
Hope to be ready by tomorrow, will add a step by step solution as a manual way too, thanks to all those people that were involved in rooting and launcher replacement.
Old post:
I just got my new Fire today and messed around with adb for some houres.
This is what I found regarding the replacement of the fire launcher so far:
You can hide com.amazon.firelauncher using pm hide through adb shell.
This will prevent the system from starting the launcher.
I pushed Trebuchet using adb install.
After a reboot it asks me which app to use.
I can choose Trebuchet and it will be relaunched after a reboot too.
The only problem is that the fire launcher is hard-coded to home button, and that can only be changed with superuser permissions.
Edit: I found the following looking at a logcat with fire launcher being hidden:
ActivityManager does report this when pushing the home button:
I/ActivityManager( 451): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher} from uid 1000 on display 0
So Amazon linked firelauncher to that intent.
There are two ways to start another launcher:
First: Change an APK so it calls the launcher it installs "com.amazon.firelauncher". That is a step that I can't do myself, and it is very likely not to work because we would have a conflict between the original and the fake process, as the original app is only hidden, but still known to be there.
Second: We need to find out where they stored the list of default intents that ActivityManager draws information from.
So if anybody knows anything about how that works, please help me.
Just wanted to share those steps with you, hopefully someone finds a solution for the hard-coded home button. Till then I'll just leave apps with back button to get back to Trebuchet
good work
I'm still doing some research on this and need your help guys.
Can anyone that did block the initial update run pm list packages com.amazon on his device and post the output here?
It seems like there is an application in the 5.0.1 build that does block all changes to the default activity setup concerning the launcher app.
I installed a second launcher on my Z1 compact and watched logcat as I hit the home button.
But the behavior is different from the one the fire shows, the fire instantly tries to run com.amazon.firelauncher, no matter how many launchers are installed.
So it seems like the registration as a launcher is somehow blocked and prevents ResolverActivity from showing.
Thanks to everyone
package:com.amazon.platform
package:com.amazon.photos
package:com.amazon.precog
package:com.amazon.dp.contacts
package:com.amazon.unifiedsharegoodreads
package:com.amazon.recess
package:com.amazon.platform.fdrw
package:com.amazon.whisperplay.contracts
package:com.amazon.venezia
package:com.amazon.webapp
package:com.amazon.dcp.contracts.library
package:com.amazon.device.sync
package:com.amazon.device.logmanager
package:com.amazon.firelauncher
package:com.amazon.alta.h2clientservice
package:com.amazon.socialplatform
package:com.amazon.dp.fbcontacts
package:com.amazon.h2settingsfortablet
package:com.amazon.calculator
package:com.amazon.cloud9.systembrowserprovider
package:com.amazon.kindle.otter.settings
package:com.amazon.dp.logger
package:com.amazon.ods.kindleconnect
package:com.amazon.accessorynotifier
package:com.amazon.sharingservice.android.client.proxy
package:com.amazon.weather
package:com.amazon.webview
package:com.amazon.android.marketplace
package:com.amazon.device.backup.sdk.internal.library
package:com.amazon.client.metrics.api
package:com.amazon.dcp
package:com.amazon.imp
package:com.amazon.mp3
package:com.amazon.unifiedsharesinaweibo
package:com.amazon.sync.service
package:com.amazon.fireinputdevices
package:com.amazon.csapp
package:com.amazon.logan
package:com.amazon.tahoe
package:com.amazon.tcomm
package:com.amazon.kindle.identityservice
package:com.amazon.kindle.personal_music
package:com.amazon.kindle.personal_video
package:com.amazon.identity.auth.device.authorization
package:com.amazon.kcp.tutorial
package:com.amazon.kindle.cms
package:com.amazon.kindleautomatictimezone
package:com.amazon.device.backup
package:com.amazon.geo.mapsv2.services
package:com.amazon.securitysyncclient
package:com.amazon.unifiedshare.actionchooser
package:com.amazon.whisperlink.activityview.android
package:com.amazon.device.messaging
package:com.amazon.digital.asset.ownership.app
package:com.amazon.devicecontrol
package:com.amazon.device.messaging.sdk.internal.library
package:com.amazon.providers
package:com.amazon.kindle.otter.oobe
package:com.amazon.photos.importer
package:com.amazon.geo.mapsv2
package:com.amazon.unifiedsharetwitter
package:com.amazon.tcomm.client
package:com.amazon.client.metrics
package:com.amazon.device.settings.sdk.internal.library
package:com.amazon.acos.providers.UnifiedSettingsProvider
package:com.amazon.firepowersettings
package:com.amazon.pm
package:com.amazon.wifilocker
package:com.amazon.dcp.contracts.framework.library
package:com.amazon.device.bluetoothdfu
package:com.amazon.whisperlink.core.android
package:com.amazon.kor.demo
package:com.amazon.device.messaging.sdk.library
package:com.amazon.ags.app
package:com.amazon.kindle.unifiedSearch
package:com.amazon.sync.provider.ipc
package:com.amazon.providers.contentsupport
package:com.amazon.platformsettings
package:com.amazon.device.crashmanager
package:com.amazon.application.compatibility.enforcer
package:com.amazon.kindle.rdmdeviceadmin
package:com.amazon.parentalcontrols
package:com.amazon.windowshop
package:com.amazon.avod
package:com.amazon.shpm
package:com.amazon.zico
package:com.amazon.communication.discovery
package:com.amazon.legalsettings
package:com.amazon.camera
package:com.amazon.device.settings
package:com.amazon.cloud9
package:com.amazon.device.sync.sdk.internal
package:com.amazon.unifiedsharefacebook
package:com.amazon.connectivitydiag
package:com.amazon.dynamicupdationservice
package:com.amazon.kindle.devicecontrols
package:com.amazon.kindle
package:com.amazon.application.compatibility.enforcer.sdk.library
ChrBeck said:
I just got my new Fire today and messed around with adb for some houres.
This is what I found regarding the replacement of the fire launcher so far:
You can hide com.amazon.firelauncher using pm hide through adb shell.
This will prevent the system from starting the launcher.
I pushed Trebuchet using adb install.
After a reboot it asks me which app to use.
I can choose Trebuchet and it will be relaunched after a reboot too.
The only problem is that the fire launcher is hard-coded to home button, and that can only be changed with superuser permissions.
Edit: I found the following looking at a logcat with fire launcher being hidden:
ActivityManager does report this when pushing the home button:
I/ActivityManager( 451): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher} from uid 1000 on display 0
So Amazon linked firelauncher to that intent.
There are two ways to start another launcher:
First: Change an APK so it calls the launcher it installs "com.amazon.firelauncher". That is a step that I can't do myself, and it is very likely not to work because we would have a conflict between the original and the fake process, as the original app is only hidden, but still known to be there.
Second: We need to find out where they stored the list of default intents that ActivityManager draws information from.
So if anybody knows anything about how that works, please help me.
Just wanted to share those steps with you, hopefully someone finds a solution for the hard-coded home button. Till then I'll just leave apps with back button to get back to Trebuchet
Click to expand...
Click to collapse
Someone could try this: http://forum.xda-developers.com/showthread.php?t=2760965 to change the application process name, and then install it over the Fire Launcher, it will update the file. If you ever want to go back, you can click "Uninstall Updates". Try this on Trebuchet and see if it works.
Cheksum
/system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk
It has a checksum, so not sure if an .apk renamed as com.amazon.firelauncher.apk and put back into the device would fail because of a checksum error?
Just tried and I get an error of [invalid apk file within my ADB shell]
Someone else might have better luck then me?
Haha I had the same idea some houres ago and tried to rename trebuchet to com.amazon.firelauncher using apktool.
But when trying to install it I get "Parsing error", maybe my signature is wrong or I made another mistake.
I'll add my apk so someone else can try signing and flashing it if anybody wants to.
Edit:
Just for your interest:
I compared the com.amazon app list posted here to mine: Exept for the apps that are hidden to prevent ota-update, both lists are identical.
So I still don't know what Amazon changed, but we can be sure that there is no additional app that prevents us from changing the launcher.
ChrBeck said:
Haha I had the same idea some houres ago and tried to rename trebuchet to com.amazon.firelauncher using apktool.
But when trying to install it I get "Parsing error", maybe my signature is wrong or I made another mistake.
I'll add my apk so someone else can try signing and flashing it if anybody wants to.
Edit:
Just for your interest:
I compared the com.amazon app list posted here to mine: Exept for the apps that are hidden to prevent ota-update, both lists are identical.
So I still don't know what Amazon changed, but we can be sure that there is no additional app that prevents us from changing the launcher.
Click to expand...
Click to collapse
I grabbed your apk and used keytool to generate my own cert and try installing the app, now adb install fails with the status below:
Code:
#This was run on OS X
#This generates the a key, after asking you several questions. Default passcode is "android"
keytool -genkey -v -keystore ~/.android/debug.keystore -alias trebuchet -keyalg RSA -keysize 2048 -validity 20000
#Sign the apk
jarsigner -verbose -keystore debug.keystore com.amazon.firelauncher.apk trebuchet
#install the package
hostname:user$ ./adb install com.amazon.firelauncher.apk
9433 KB/s (3427921 bytes in 0.354s)
pkg: /data/local/tmp/com.amazon.firelauncher.apk
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
Update incompatible sounds great, it means that there is just one fuse we need to break.
I did not change the version info and permissions of trebuchet, that might already be the point.
I will extract firelauncher this evening, check for version, set trebuchet to a higher version and copy all the permissions firelauncher uses with those missing permissions copied from trebuchet (which should cause the installer to ask for granting only those additional ones)
As your certs seem to work, I'll just publish the unsigned apk and you could try signing and installing again if you want to.
Seems like we are getting close to a solution.
ChrBeck said:
Update incompatible sounds great, it means that there is just one fuse we need to break.
I did not change the version info and permissions of trebuchet, that might already be the point.
I will extract firelauncher this evening, check for version, set trebuchet to a higher version and copy all the permissions firelauncher uses with those missing permissions copied from trebuchet (which should cause the installer to ask for granting only those additional ones)
As your certs seem to work, I'll just publish the unsigned apk and you could try signing and installing again if you want to.
Seems like we are getting close to a solution.
Click to expand...
Click to collapse
I just used apktool to decompile your apk, which I then inserted updated version info into (apktool.yml stores this), and after resigning, installation failed for the same reason as above. It seems that the device is detecting that the cert that I'm using is not the one used to sign the original application and failing on that. I've seen this happening when doing development on my personal apps.
This might not work, though I would love if someone could prove me wrong.
In the meantime, I was considering using pm hide to hide the default launcher and use some sort of softkey solution with a link to trebuchet or nova. I'll look into it tomorrow after I get a bit of sleep.
Edit:
Just a cursory test with an app called "overlay" and nova launcher is proving to be quite adequate. I have an on-screen overlaid app shortcut to nova launcher at all times. I will have to create app filters to stop the overlay from going in front of games and videos, but this seems to do the trick for me at least. I'll upload the overlay config tomorrow morning, but it's simple enough to figure out. I currently have com.amazon.firelauncher hidden, and after rebooting it automatically opens nova launcher and the overlay pops in about 10 seconds later.
Edit 2:
Since I don't have 10 posts yet, I'm not allowed to post links to files. It should be pretty easy to figure out how to set up Overlays though. I made my application link to nova launcher almost completely transparent and in the bottom right corner of my screen, and it works well, though there is a small delay before it gets back to the launcher.
Now that I've got the play store, Google keyboard, and a decent launcher, this is shaping up to be a good purchase.
I am very interested in this thread, but I can't understand much of what @googlegot wrote.
"Just a cursory test with an app called "overlay" and nova launcher is proving to be quite adequate. I have an on-screen overlaid app shortcut to nova launcher at all times. I will have to create app filters to stop the overlay from going in front of games and videos, but this seems to do the trick for me at least. I'll upload the overlay config tomorrow morning, but it's simple enough to figure out. I currently have com.amazon.firelauncher hidden, and after rebooting it automatically opens nova launcher and the overlay pops in about 10 seconds later. "
Could you please elaborate on this?
zavorrax said:
I am very interested in this thread, but I can't understand much of what @googlegot wrote.
"Just a cursory test with an app called "overlay" and nova launcher is proving to be quite adequate. I have an on-screen overlaid app shortcut to nova launcher at all times. I will have to create app filters to stop the overlay from going in front of games and videos, but this seems to do the trick for me at least. I'll upload the overlay config tomorrow morning, but it's simple enough to figure out. I currently have com.amazon.firelauncher hidden, and after rebooting it automatically opens nova launcher and the overlay pops in about 10 seconds later. "
Could you please elaborate on this?
Click to expand...
Click to collapse
This is a text only guide as I am writing it on mobile, I'll flesh it out in a full post after work.
This guide assumes you have the play store installed, debug drivers and adb installed, and debugging mode enabled in developer settings.
1. Download "Overlays - Float Everywhere" from the Play store.
2. Download a launcher of your choosing (I chose Nova launcher)
3. In overlays, press the "+" button to create a new profile
4. Select "Always/Manual (Global)", then enter a name for your profile (I named mine "Nova". Make sure to set it to "Always On" using the toggle below the name on the right side of the screen above "advanced settings"
5. Press the save button in the top right corner of the screen.
6. Select "Add your first Overlay", then "Application Shortcut", then select your launcher (again, I used Nova). This will create an icon on screen, which you can drag around to where you want your new home button to be. It may appear off screen at first. If so, turn your tablet to landscape orientation to get it into view.
7. Drag the icon where you would like it to be in both landscape and portrait mode, then save the location by pressing the save button in the top right corner of the icon.
8. Save the overlay by pressing the save button in the middle of the set of three buttons in the top right corner of the screen.
9. Reboot your tablet. Once it has booted you'll notice an icon for your launcher is now overlaid on every screen at all times. This is your new "home" button.
10. Plug your tablet into your computer and run the following to disable the built in launcher:
Code:
adb shell
pm hide com.amazon.firelauncher
exit
(To undo this, change "pm hide" to "pm unhide")
11. The original home button on your tablet will now produce an error when pressed and your only available launcher will now be the one you've installed. You'll need to use the new overlaid button you created to as your home button.
does this affect you leaving full-screen apps ?
(IE: a game)
if hitting your home buttons gives an error
peace
Ricci
a1yet said:
does this affect you leaving full-screen apps ?
(IE: a game)
if hitting your home buttons gives an error
peace
Ricci
Click to expand...
Click to collapse
This is an overlay, it is on top of your full screen games and videos. Your home button is broken, but the overlaid application icon is your new home button for all intents and purposes. It is a button on top of everything on screen.
googlegot said:
It is a button on top of everything on screen.
Click to expand...
Click to collapse
hmm this is interesting
thanks for this, will look into it myself :victory:
googlegot said:
I just used apktool to decompile your apk, which I then inserted updated version info into (apktool.yml stores this), and after resigning, installation failed for the same reason as above. It seems that the device is detecting that the cert that I'm using is not the one used to sign the original application and failing on that. I've seen this happening when doing development on my personal apps.
This might not work, though I would love if someone could prove me wrong.
In the meantime, I was considering using pm hide to hide the default launcher and use some sort of softkey solution with a link to trebuchet or nova. I'll look into it tomorrow after I get a bit of sleep.
Edit:
Just a cursory test with an app called "overlay" and nova launcher is proving to be quite adequate. I have an on-screen overlaid app shortcut to nova launcher at all times. I will have to create app filters to stop the overlay from going in front of games and videos, but this seems to do the trick for me at least. I'll upload the overlay config tomorrow morning, but it's simple enough to figure out. I currently have com.amazon.firelauncher hidden, and after rebooting it automatically opens nova launcher and the overlay pops in about 10 seconds later.
Edit 2:
Since I don't have 10 posts yet, I'm not allowed to post links to files. It should be pretty easy to figure out how to set up Overlays though. I made my application link to nova launcher almost completely transparent and in the bottom right corner of my screen, and it works well, though there is a small delay before it gets back to the launcher.
Now that I've got the play store, Google keyboard, and a decent launcher, this is shaping up to be a good purchase.
Click to expand...
Click to collapse
Can confirm this is working 100%. Now we have a fully functional tablet! Thanks so much for finding out about this work-around! My hat goes to you sir. :highfive:
xT29c said:
Can confirm this is working 100%. Now we have a fully funcation tablet!
Click to expand...
Click to collapse
not working 100%
working 75%
everything works fine BUT Widgets
no widgets work
crashes to "settings" when you try to install one
example
the weather channel (or event flow calendar)
drag to desktop
CRASH to the Fires "settings" window
any fix or work around for this
peace
Ricci
PS: widgets have a value of at least 25% as everyone has one on their device
and is the first thing people see when the turn their device on
25% may be too low but i had to give it a value
Has anyone tried another launcher? Maybe Google Now or APEX...
a1yet said:
CRASH to the Fires "settings" window
any fix or work around for this
peace
Ricci
PS: widgets have a value of at least 25% as everyone has one on their device
and is the first thing people see when the turn their device on
25% may be too low but i had to give it a value
Click to expand...
Click to collapse
This is exactly what happens on 2014 HDs, too. The fix is to convert launcher to system app, which requires root.
DoLooper said:
This is exactly what happens on 2014 HDs, too. The fix is to convert launcher to system app, which requires root.
Click to expand...
Click to collapse
thank you for letting me know this
I'll stop banging my head against a wall thinking I'm dum (or is it dumb ?)
LOL
thanks again
Ricci