Related
The problem: After installing AOSP 1.6, I noticed protected apps weren't showing in Market, including some I had bought in 1.5. I restored my 1.5 backup and found the same thing. Instructions on this thread (http://forum.xda-developers.com/showthread.php?t=605028) were able to get my apps back in 1.5, but upon reflashing 1.6 I was back to square one.
Update:
----------
I started fresh to test things out, trying both AOSP 1.6 and gbhil's modded AOSP 1.6. I wiped, then flashed and booted, then flashed gbits and booted, then setup my google creds, then rebooted and flashed superuser, then installed busybox then rebooted.
That's my baseline. From that point, I observed:
- Market showed a limited amount of apps. One time My Downloads had all my apps, but upon trying to install one I got a "Download unsuccessful" error. I'm assuming when the download was initiated my fingerprint was sent out, and then Market filtered My Downloads to reflect that unofficial fingerprint. Meaning, most apps were missing again.
- I updated build.prop with the fingerprint from stock 1.5 (see below for instructions). I downloaded a random app (Twidroid Free) so it'd send out my "new" fingerprint, and thus remove the filter limiting my apps. Soon after all apps were appearing again. Be patient here, sometimes it doesn't update instantly. One gave a download error, but trying to install it again solved it.
- Just to test, I edited my build.prop back to whatever was default with the 1.6 rom I was using, then rebooted. My Downloads still showed everything, but as soon as I installed any random app, that unofficial fingerprint was sent out and my apps were limited again.
I don't know enough about Market to know the repercussions of what I did - does it think I have 1.5, so will it be showing me only 1.5 compatible apps? Either way, I'd rather have access to all 1.5 apps than only some 1.6 apps. And aren't most (not all, but most) 1.5 apps backwards compatible with 1.6 anyway? So the only real downside is 1.6+ apps will be hidden. If someone has the fingerprint for an "official" 1.6 device, they could change their fingerprint to that and conceivably have the best of both worlds (protected apps AND 1.6+ apps).
How To Change Your Build Fingerprint:
--------------------------------------------
1. Connect your phone.
2. Pull /system/build.prop | For Mac users: ./adb pull /system/build.prop ./
3. Using your favorite editor, find the line that starts with ro.build.fingerprint and put a # in front of it.
4. On a new line, put: ro.build.fingerprint=sprint/htc_heroc/heroc/heroc:1.5/CUPCAKE/85027:user/release-keys
5. Save the file.
6. Remount the filesystem as read/write | For Mac users: ./adb remount
7. Log into the phone | For Mac users: ./adb shell
8. Exit the shell by typing: exit
9. Now push the file back. | For Mac users: ./adb push ./build.prop /system/build.prop
10. Reboot | For Mac users: ./adb reboot
11. Go to Market, and install something to send out the new fingerprint.
12. Within a few minutes you should see all apps. If not, try rebooting. If still not, try clearing Market's cache (Settings->Applications->Market->Clear Cache)
--------------------------------------------
Hope this helps someone.
-TM
This affects the MoDaCo rom I installed, and the AOSP 1.6 rom I was playing around with. Things like WeatherBug Elite, and tons of other stuff are hidden from the Market. In the case of MoDaCo, which I installed overtop my existing 1.5 stock (after backing up of course) the apps ran fine since they were grandfathered in from the stock rom, but still weren't listed in the marketplace. I'd really appreciate any help, as these speedy roms are useless if I can't run any of my apps on them.
search is king
this should help you
Link here
This reply isn't valid anymore and may be deleted.
Can you please post the code for this. I'm having a hard time getting this to work. Thanks
dathryl said:
Can you please post the code for this. I'm having a hard time getting this to work. Thanks
Click to expand...
Click to collapse
Code for what? What problems are you having?
Newbie question, how do you "pull" the file. I'm on shell but don't know what to input in order to edit the file.
PRGUY85 said:
Newbie question, how do you "pull" the file. I'm on shell but don't know what to input in order to edit the file.
Click to expand...
Click to collapse
You need to have ADB installed (which you do if you've rooted your phone, as ADB is required to do so). So you'd need to go into a command prompt (Windows) or Terminal (Mac), navigate to your adb/tools directory (that has adb.exe in it) and type "adb pull fileonyourphone fileonyourcomputer". Obviously replace fileonyourcomputer with the actual paths and filenames of what you're pushing/pulling. When you push the file back to the Hero, you swap the syntax, so it'd be "adb push fileonyourcomputer fileonyourphone".
OK, sorry again for noobness...
He says adb remount as read write, how do I do that?
He says log in to the phone...how do I do that on the shell?
So just to be sure, this fix will allow me to download the apps that I just can't find on the market that my friends with stock Heros can, right?
Someone recommended a new twitter client (twicca) but I couldn't open it on the market and I'm assuming it's because I'm running AOSP 1.6.
Thanks.
I just did this, and it seemed to work, but when Weatherbug Elite was downloading the phone went into the "Android" boot screen and just looped it over and over. After a battery pull it still won't boot up, and it keeps getting stuck at the boot screen. Is there anyway to fix this?
sure is nice to have sufbs back.
thanks for this.
Thanks, worked like a charm.
I updated my new kindle fire, then rootet it successfully.
After that i installed the Ice Cream Sandwich 4.0 and made it the default launcher.
But this failed, when i now start the kindle fire i get caught into the loop of this error:
! Sorry
The application Ice Cream Sandwich 4.0 (process androd.process.acore) has stopped unexpectedly. Please try again. [Button: force close]
Which i can press, and then the loop starts again.
I am a noob, so please how do i get rid of this launcher ? I could need a reset or factory default or whatever, but the normal ways dont work, because i cant reach them anymore. Any Ideas how to fix this ?
/edit: I have access to my device with adb shell. so i think i can somehow change the default launcher, if someone tells me which file to change because i have no idea which is the right.
You need to figure out what the package name is "adb shell pm list packages" without quotes. Once you figure out what the package name is you can "adb uninstall name.of.package"
Hard reset it with power button.
Guide - How to hard reset Kindle Fire?
Fyi.....I just tried the hold power for 20 seconds hard reset, and it doesn't work......
Sent from my Kindle Fire using Tapatalk
I've had this problem with a different launcher and posted my solution here : http://forum.xda-developers.com/showthread.php?t=1361138
... don't worry... you can fix it... all you need to do is install another launcher or uninstall the ICS launcher... and you may be wondering how you can do that if you can't get to a usable screen.
You can still install/uninstall apps using the adb service you used while rooting. FoxDog66 mentioned how to do this if you know the package name. In my case, I could not find out the package name of the offending package, so what I did was install another launcher via the same method I installed my google apps to the sys/apps folder. with another launcher installed, I get a choice again which launcher should run when turning on.
I suggest you try foxdog's suggestion first, but if you can not find the package name then get another launcher.apk install file like GOlauncher or ADW Launcher and push or install that app the way you see google apps being pushed via the following method:
Download GOlauncher http://61.145.124.93/soft/3GHeart/golauncher/v2.68/go_launcher_ex_v2.68.apk
now make it a system app:
adb remount
adb push c:\androidApps\go_launcher_ex_v2.68.apk /system/app/go_launcher_ex_v2.68.apk
adb reboot
After reboot you should be able to choose your launcher of choice. Don't make anything default until you know you like it!!!
Now that GO Launcher just installed via my method makes it a system app. You can't uninstall system apps in the normal way, so use a program like Titanium Backup to make that pushed launcher app a NON-system app (moves it and makes it easy to uninstall the way other apps do). Titanium Backup is just a great program to have if rooted.
Good Luck.
how to uninstall buggy launcher which is set to default
Thanks for helping me.
Yes thats exactly my problem and i am now trying to follow your instructions.
The hardware reset works, but it will not get rid of the launcher.
So i try to find out the right application name to uninstall it. But *blush* i have not idea which is the right name and i dont want to uninstall something randomly.
I have some very basic skills with linux which i uses 10 years ago or so, so i am able to make a list which i attached here.
OK, i am now trying to do this:
adb remount
adb push c:\androidApps\go_launcher_ex_v2.68.apk /system/app/go_launcher_ex_v2.68.apk
adb reboot
but "adb remount" gives me back a
remount failed: Operation not permitted
I need to look closer how to install and uninstall packages now.
/edit: what i can do is:
adb shell
$
su
#
so this looks like to me that i am superuser. I also see the file system, and i can do some stuff with this shell, but its very limited because this shell is different from the shells i knew long time ago.
/edit:
ok, found something:
i am in the file system in
/data/app
here i have 3 apk:
net.adisasta.androxplorer-1.apk
mobi.SyndicateApps.ICSv2-1.apk
mobi.SyndicateApps.ICS-1.apk
and i think this is the package i installed.
/last edit:
OK folks. SUCCESS..
I just did adb uninstall mobi.SyndicateApps.ICSv2 and i immidiatly got success and got rid of the fail launcher.
VERY NICE and a warm THANK YOU for helping me.
I think i will try more now -- hehe.
Just tasted some blood now. Probably i will be soon here with the next problem. But i really appriciate your help. Hopefull soon i will be more into it and be able to help other noobs, too.
Also if someone needs german help because of language barrier, i can help translating.
Best Regards
Usurpine
Glad you got it fixed
A few tips.... adb remount just remount's the system partition read-write which isn't needed unless the app is installed to /system/app (it also does not work. It does work with doomlord's kernel, i think because of the insecure ramdisk)
The "./" part of your command just means to run in the current directory, if you have fastboot or adb in path then you don't need that part and you can also run the commands from any directory. if you don't have them in path then you would need to have what you wanted to flash, boot, whatever in the same directory as fastboot/adb. To check if something is in path (let's say fastboot) you can type "which fastboot" and it will either tell you where it is (something like ~/Android-sdk/platform-tools/fastboot) or it will say, couldn't find fastboot and it will list out a bunch of directories.
One last thing, you can chain commands together with "&&" so say i want to "fastboot boot newboot.img" i would plug my kindle in, press the disconnect button that pops up on the kindle then type in terminal "adb reboot && fastboot boot newboot.img" if/when the first command runs successfully then it will run the second command. If it does not run successful, it won't run the second command. Also, for me, adb reboot takes a few seconds to work and fastboot waits for the device for a few seconds also.
Hope this is useful, I'm not always good at explaining things. I'm also not a Linux pro lol these are just a few things i have learned that are pretty useful
Well, this is useful. Basically you are talking about how to work with linux. Once i understood that inside my kindle there is just a typical linux i can take one of my old linux books and use any command (like the && and other stuff).
I am not a pro with linux (forgot almost everything) but now i know how to look after it and be able (limited) to use it after some testing.
That said, i now was able to do a lot of funny stuff with my kindle, i installed tons of applications just to look how it works (and it works great) and uninstalled them after that.
Now i can watch movies, listen music, play games and can do almost everything what you normally cannot do with a kindle due to amazons restrictions.
What i want to know is how i can extend the linux inside my kindle so it is using a shell which can do even more stuff, like a ksh (korn shell) or something. A shell with commands like i can find in a "normal" linux installation. Is that possible ?
And how about installing a more linux like grafical userinterface ? Or use the kindle as a normal linux pc, just for fun ?
Ummm..... Have you looked at busybox? It is possible to port command line tools to Android. I've seen things like cURL and lynx that worked. Porting and compiling is a little out of my league (wish it wasn't lol, I'd like a updated cURL binary with https support) i know bash scripts work, I've written a few and "run-parts" (part of busybox) will run a directory of scripts.
You should get into (or look into) custom Android development and/or kernel development. There is a lot that can be done
Help, im a real newbie
usurpine said:
I updated my new kindle fire, then rootet it successfully.
After that i installed the Ice Cream Sandwich 4.0 and made it the default launcher.
But this failed, when i now start the kindle fire i get caught into the loop of this error:
! Sorry
The application Ice Cream Sandwich 4.0 (process androd.process.acore) has stopped unexpectedly. Please try again. [Button: force close]
Which i can press, and then the loop starts again.
I am a noob, so please how do i get rid of this launcher ? I could need a reset or factory default or whatever, but the normal ways dont work, because i cant reach them anymore. Any Ideas how to fix this ?
/edit: I have access to my device with adb shell. so i think i can somehow change the default launcher, if someone tells me which file to change because i have no idea which is the right.
Click to expand...
Click to collapse
Please help me, I really have no experience and I followed a link that made it look very easy to install the ICS Launcher. Now I keep getting that same page and it's driving me up the wall.
I have tried the adb so I can uninstall the faulty apk myself but my mac wont detect it even though it still mounts.
Iv done the adb devices but the list is empty.
Please help me in a very easy way to understand.
hi all i installed the rocketrom v7 this morning and well ive been playing and messed something up. i installed ROM Toolbox pro and i wanted to see if i could get dungeon defenders second wave controls to fit the screen correctly so i can play it, so i edited the LCD density setting from 320 to 280 and after the reboot went to make a call and the call dialer isnt full screen any more its less due to the hack.. ive not even tried the game yet but i went back into ROM Toolbox pro and fount that i cant set it back at 320 as the slider only maxes at 280
please advise me on this, is their a solution without wiping rom?
You have root I presume - just edit /system/build.prop - the "density" might be in there twice - change both.
You can edit it using a shell (su root first) or using adb:
adb remount /system
adb pull /system/build.prop
<edit>
adb push build.prop /system
<reboot>
phedders said:
You have root I presume - just edit /system/build.prop - the "density" might be in there twice - change both.
You can edit it using a shell (su root first) or using adb:
adb remount /system
adb pull /system/build.prop
<edit>
adb push build.prop /system
<reboot>
Click to expand...
Click to collapse
Or just reflash the rom and wipe cache an dalvik cache afterwards and reboot.
phedders said:
You have root I presume - just edit /system/build.prop - the "density" might be in there twice - change both.
You can edit it using a shell (su root first) or using adb:
adb remount /system
adb pull /system/build.prop
<edit>
adb push build.prop /system
<reboot>
Click to expand...
Click to collapse
worked a charm. set back to 320 and now all is good and new
ps is their a way to set PER app density.. ie have a single app run at different settings, i would like to keep 280 but seen as stuff like dialer/spen/email ect doesn't work well with it keeping 320 default but a few apps like games with a lower value of 240/280 that would be epic for me ?
ps yes im fully rooted mate
DAMIEN123_666 said:
worked a charm. set back to 320 and now all is good and new
ps is their a way to set PER app density.. ie have a single app run at different settings, i would like to keep 280 but seen as stuff like dialer/spen/email ect doesn't work well with it keeping 320 default but a few apps like games with a lower value of 240/280 that would be epic for me ?
ps yes im fully rooted mate
Click to expand...
Click to collapse
The only ROM that can do that is ParanoidAndroid.
You can also just use an alternative dialer, like Go dailer, that is what i do on lower density
LordManhattan said:
The only ROM that can do that is ParanoidAndroid.
Click to expand...
Click to collapse
friedje said:
You can also just use an alternative dialer, like Go dailer, that is what i do on lower density
Click to expand...
Click to collapse
hmm interesting, i have read ParanoidAndroid rom is glitchy with gps ect, i would like that rom but i need stability over features at the min,
hmm is their a link that list all galaxy note stock apps that aint 240/280 compatible so i can research them all and get the correct versions
sofar i know the dialer/email isnt working good
DAMIEN123_666 said:
hmm interesting, i have read ParanoidAndroid rom is glitchy with gps ect, i would like that rom but i need stability over features at the min,
hmm is their a link that list all galaxy note stock apps that aint 240/280 compatible so i can research them all and get the correct versions
sofar i know the dialer/email isnt working good
Click to expand...
Click to collapse
Also, if you have custom dpi and want to use stock dialer there is a setting in accessibility to enable one handed operation. This will rescale the dialer pad to full usability again.
V 0.3 of paranoid does indeed have a couple of glitches with GPS (although I upgraded from v0.2 and don't experience it], but v0.2a is totally bug free and well worth a look. In the latest couple of pages on the thread there's a link to someones dropbox for the download. Highly recommend it!
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!
WTF !!!
Hello,
I have used the rom tool box pro to setup the lcd to 160 instead of the default setting and now my phone doesn't finish booting, i am stuck at the error message "unfortunately Touchwiz has stopped" disapperas and then another one shows up "Unfortunately, System UI has stopped" ... due that the launcher has stopped responding and i had luckily usd USB DUBEG option earlier i could thru ADB reboot to firmware mode taker a NANDROID backup ... deleted dalvik and cache partitions didnt help , and finally did a hard reset / factory default thru the boot loader
result is:
factory reset worked and had to setup the phone again, but the LCD density is still 160, after I finished the new phone setup am stuck again at the above two messages immediately after setup is done !!!!!
What can i do now especially that i cannot connect thru ADB since the phone settings is not set to USB Debug ........
Thanks
KhodorSoueidan said:
Hello,
I have used the rom tool box pro to setup the lcd to 160 instead of the default setting and now my phone doesn't finish booting, i am stuck at the error message "unfortunately Touchwiz has stopped" disapperas and then another one shows up "Unfortunately, System UI has stopped" ... due that the launcher has stopped responding and i had luckily usd USB DUBEG option earlier i could thru ADB reboot to firmware mode taker a NANDROID backup ... deleted dalvik and cache partitions didnt help , and finally did a hard reset / factory default thru the boot loader
result is:
factory reset worked and had to setup the phone again, but the LCD density is still 160, after I finished the new phone setup am stuck again at the above two messages immediately after setup is done !!!!!
What can i do now especially that i cannot connect thru ADB since the phone settings is not set to USB Debug ........
Thanks
Click to expand...
Click to collapse
Hard reset should have corrected the setting, not sure why it didn't. If you're on stock kernel, don't try it again in case of hard brick. I would suggest flashing again with pc Odin. There have been some people who've managed to create a flash able zip with stock buildprop file and stock dpi, but you'll have to search for that, not sure if it was ever achieved, worth a go.
Sent from my GT-N7000 using xda premium
I just got the CM10 installed on an sd card using bokbokan's images. Everything works great. But the Kindle app thinks it is running on a phone and everything looks super big. I can change the text size and some options but I like the tablet UI much better. Nook app does the same.
So I got this app called LCD Density and tried changing mine from the default 240 to 300. The whole Android UI adjusted itself and looked better (smaller) but the Kindle app and the Nook app were unaffected.
1. Is there a way to put these apps into Tablet mode?
2. Is there a way to stick the new density across reboots using this app?
TIA.
yelloguy said:
I just got the CM10 installed on an sd card using bokbokan's images. Everything works great. But the Kindle app thinks it is running on a phone and everything looks super big. I can change the text size and some options but I like the tablet UI much better. Nook app does the same.
So I got this app called LCD Density and tried changing mine from the default 240 to 300. The whole Android UI adjusted itself and looked better (smaller) but the Kindle app and the Nook app were unaffected.
1. Is there a way to put these apps into Tablet mode?
2. Is there a way to stick the new density across reboots using this app?
TIA.
Click to expand...
Click to collapse
Don't use the LCD app. On CM10 it is ok to change /system without worrying about resetting your device. So go to /system and look for build.prop. Edit that file with your root file manager. There is a line that ends ...density=240. Change that to 300. But you will have to edit it every time you flash a new ROM. The way to get around that is to create a file in /data named local.prop. Put this line in it.
qemu.sf.lcd_density=300
That will not get overwritten in a rom flash.
The kindle and nook apps detect how they should display themselves based on lcd density and screen size. The only way to get them into tablet mode is to REDUCE density not raise it. So you need to make a choice, higher density and phone mode, or lower density and tablet mode.
Sent from my Nook HD+ Running CM10 on SD
That's it. The problem was the app -- it wasn't changing the density correctly. I just changed it to 160 in the system/build.prop and everything switched to the tablet mode. Kindle and the Nook app work so much better but the UI looks less usable. I changed the system font to Huge and that helped a little. Two more questions:
1. Do you know what is the minimum density where Android still thinks it is a tablet? Is it 180? 200? We already know it switches to phone mode at 240. Of course, I can experiment if I can't find out.
2. Does the Nook HD's native dpi matter at all? You know how the desktop LCD screens have a native mode resolution where everything looks sharp and non-native mode where it maps the OS pixels to native pixels and everything looks blurry? I am wondering if something like that is going on here and I will have to do some dpi -> dip math to find out what is best for the Nook HD.
Thanks again.
Edit: Googling revealed 213 is the magic number. Tried 210 but I still got phone ui. Next I tried 200 and got a tablet ui with everything nicely usable. For someone else, you might want to try 190 or 180.
create or modify files in root directory
leapinlar said:
Don't use the LCD app. On CM10 it is ok to change /system without worrying about resetting your device. So go to /system and look for build.prop. Edit that file with your root file manager. There is a line that ends ...density=240. Change that to 300. But you will have to edit it every time you flash a new ROM. The way to get around that is to create a file in /data named local.prop. Put this line in it.
qemu.sf.lcd_density=300
That will not get overwritten in a rom flash.
The kindle and nook apps detect how they should display themselves based on lcd density and screen size. The only way to get them into tablet mode is to REDUCE density not raise it. So you need to make a choice, higher density and phone mode, or lower density and tablet mode.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
I am new to android OS, and I apologize for the following simple question: how do I gain access for creating and modifying a file in /data in my rooted Nook HDPlus (with the set of files and steps you provided. thank you.) I tried to use the Root Browser to create a file in /data for changing my lcd density, but each time I was denied access. Do I need to somehow log into my device as a superuser (how), or do I need to change the setting (how)? Thanks again for your time, expertise, and patience.
cool2know said:
I am new to android OS, and I apologize for the following simple question: how do I gain access for creating and modifying a file in /data in my rooted Nook HDPlus (with the set of files and steps you provided. thank you.) I tried to use the Root Browser to create a file in /data for changing my lcd density, but each time I was denied access. Do I need to somehow log into my device as a superuser (how), or do I need to change the setting (how)? Thanks again for your time, expertise, and patience.
Click to expand...
Click to collapse
Are you sure you are rooted? And when you started root browser the first time, did it ask for root access and did you grant it? Open the superuser app and see if it lists root browser as being granted superuser access. If it does not, go to settings, applications, my apps, root browser and clear the data for it. Then restart root browser and if really rooted it will ask for superuser access.
Sent from my Nook HD running CM10.1 on Hybrid SD
leapinlar said:
Are you sure you are rooted? And when you started root browser the first time, did it ask for root access and did you grant it? Open the superuser app and see if it lists root browser as being granted superuser access. If it does not, go to settings, applications, my apps, root browser and clear the data for it. Then restart root browser and if really rooted it will ask for superuser access.
Sent from my Nook HD running CM10.1 on Hybrid SD
Click to expand...
Click to collapse
Following the steps you outlined, it all worked out. My Nook HD+ now is in higher resolution. The Root Browser was not in the Superuser listing, somehow. Again, thanks for the help.
I used ADB shell to tinker with my device's DPI.
I set it to 200, and TouchWiz and the system UI stopped working. I tried resetting the phone to see if they adjusted to the new DPI but they didn't. Now I can't get into ADB shell because I can't give the authorization because the UI crashes.
Any ideas on how to reset the DPI? My S5 is not rooted.