So, I have read that it's an issue with all Froyo ROM's on the EVO... You can't see paid/protected apps in the Marketplace; supposedly, the apps not showing are not verified to work on Froyo.
Could someone just patch the build_prop like they did on the Nexus One before Google released the official fix?
N1 Fix Thread for Reference: http://forum.xda-developers.com/showthread.php?t=693102
If anyone wants to tackle it, the dev of the N1 fix explained what needs to be done here: http://forum.xda-developers.com/showthread.php?t=693102
I don't have an EVO, nor am I much of a developer; but I just rooted my friend's EVO and was looking for a fix for him when I realized that the N1 had a very similar issue when it was running leaked versions of Froyo.
Just throwing it out there... I could be way off.
I think this should be easy to do. Theoretically you should be able to take buildprop swticher v0.3.1.zip and replace /buildprop/build.2.1 with the build.prop from stock and /buildprop/build.2.2 with the build.prop from CM6 and then follow the directions from that post.
I'm about to test it out myself and see if it works...
Let me know... If it does, could you post the build.prop files that you used?
EDIT: Awesome to see another SC member!
Okay, first attempt boot looped. I think build.2.1 needs to be a 2.2 build.prop modified to look like 2.1 because the stock 2.1 build.prop won't work with 2.2. Should've looked at that more instead of rushing Going to see if I can find the lines to change real quick, gotta go back to work in a few minutes...
It also cleared my Google Account settings haha... trying a new modification but may not be able to upload anything until tonight!
Thanks for your help... Can you post your build.props before going back to work? If so, I will try to work on this more if you aren't able to get it before going back.
Thanks
Just printed and compared the build.props for the N1 fix and see that there are only 2 lines that were changed. If someone wants to provide me with a 2.1 build.prop and the CM6 build.prop, I might be able to get this working.
Don't bother with it man.
I'm the one posted the Nexus thread. I already tried changing the build.prop fingerprints & it didn't fix the issue.
Only thing keeping me from using CM6
Geniusdog254 said:
Don't bother with it man.
I'm the one posted the Nexus thread. I already tried changing the build.prop fingerprints & it didn't fix the issue.
Only thing keeping me from using CM6
Click to expand...
Click to collapse
I was just about to post saying what I tried didn't work and I was hoping you'd pop in here. I was thinking about digging into it more this weekend but if you haven't been able to get anywhere I doubt I could either.
Well... that blows... Sorry guys
Wish I could've been of more help!
Geniusdog254 said:
Don't bother with it man.
I'm the one posted the Nexus thread. I already tried changing the build.prop fingerprints & it didn't fix the issue.
Only thing keeping me from using CM6
Click to expand...
Click to collapse
After you changed the lines in build.prop did you try reseting Market?
settings > Applications > Manage Applications > ALL > Market > Clear data
Geniusdog... what all does the ro.build.fingerprint line do?
spiicytuna said:
After you changed the lines in build.prop did you try reseting Market?
settings > Applications > Manage Applications > ALL > Market > Clear data
Click to expand...
Click to collapse
Yep. Even tried pushing it while still in recovery, right after wiping and flashing the ROM. Still a no go
Edit: the to.build.fingerprint is the "fingerprint" it shows when it accesses the Market. So its how the Market decides what apps to show, and sees what kind of device it is & its version
Geniusdog254 said:
Yep. Even tried pushing it while still in recovery, right after wiping and flashing the ROM. Still a no go
Edit: the to.build.fingerprint is the "fingerprint" it shows when it accesses the Market. So its how the Market decides what apps to show, and sees what kind of device it is & its version
Click to expand...
Click to collapse
We need a setting like most of the android browsers to allow us to spoof ourselves as stock 2.1 EVO.
Geniusdog254 said:
Yep. Even tried pushing it while still in recovery, right after wiping and flashing the ROM. Still a no go
Edit: the to.build.fingerprint is the "fingerprint" it shows when it accesses the Market. So its how the Market decides what apps to show, and sees what kind of device it is & its version
Click to expand...
Click to collapse
Hmmm...editing fingerprint and description *SHOULD* work but it did not work when I tried adding the fingerprint/description from Avalaunch's Froyo ROM. It seems that Ava's Froyo ROM fixed the missing apps issue. It's so very bizarre that we can't get certain market apps to show on CM6 and drives me crazy. There has to be some type of solution, I'm just not sure what it is yet
ok this is what we did on the Hero when we was with 1.5 and got the leak of 2.1 the market didnt show all the apps so we just change it with the nexus one, so i am guessing maybe we can get a 2.2nexus one build.prop and push it to the Evo, make sure to clear the market chache though , it took like 5-6hours for the apps to start showing up on the Hero!! just an Idea
jabbawalkee said:
Hmmm...editing fingerprint and description *SHOULD* work but it did not work when I tried adding the fingerprint/description from Avalaunch's Froyo ROM. It seems that Ava's Froyo ROM fixed the missing apps issue. It's so very bizarre that we can't get certain market apps to show on CM6 and drives me crazy. There has to be some type of solution, I'm just not sure what it is yet
Click to expand...
Click to collapse
Have you tried just using the whole build.prop from Ava's ROM? Should work ok since they're both 2.2, no idea if it'll fix the issue though.
datajosh said:
Have you tried just using the whole build.prop from Ava's ROM? Should work ok since they're both 2.2, no idea if it'll fix the issue though.
Click to expand...
Click to collapse
bootlooops
Edit: nvm, was incomplete.
Sense build.prop files & AOSP build.prop files don't play nice together. Neither do CDMA files & GSM files.
It takes some changes to get the phone to boot with them, or to get radio access with them.
I've already tried a stock Nexus fingerprint, but it still doesn't give access. Like I said, I even pushed the file before even booting the phone (I.E, wipe, flash CM6, push file in recovery, then reboot) and it still didn't work.
Ava's build prop comes up, but no Market. Something else is going on.
Geniusdog254 said:
Sense build.prop files & AOSP build.prop files don't play nice together. Neither do CDMA files & GSM files.
Click to expand...
Click to collapse
Duh, forgot it was Sense for a minute there. I feel like looking into it more but I'm not sure if anyone's going to find a solution.
Related
Does anyone know how I might be able to port the desire hd browser? I love the pinch to bring up windows feature. I'm currently running Skyraider 3.3. I tried extracting it from the sense hd rom and moving it to system/app but that wouldn't install. I'm sure I'm approaching it from a way too simplistic angle. Any help would be much appreciated.
Thanks
I'm not sure if you could do this...
The Desire is running the new sense, so this could be a problem?
Maybe if IncDoes chimes in he would know, or if you want to get ahold of him
Let us know how this goes!
how did you move it to your skyraider rom? if you used root explorer then you need to change permissions and then do a reboot.
jasonb1985 said:
how did you move it to your skyraider rom? if you used root explorer then you need to change permissions and then do a reboot.
Click to expand...
Click to collapse
Yeah I used Root Explorer. I changed permissions to read/write, moved out the old browser, moved in the new browser, changed permissions back, and finally did a reboot. No browser was recognized so I actually went in and hit install but it said install unsuccessful.
any luck with this?
Try this one. It is from the latest leak and does have pinch.
It is for only a deodexed ROM not stock and will work if pushed to /system/app/ with adb.
NilsP said:
Try this one. It is from the latest leak and does have pinch.
It is for only a deodexed ROM not stock and will work if pushed to /system/app/ with adb.
Click to expand...
Click to collapse
How did you port it?
Sent from my Incredible using XDA App
jdkoreclipse said:
How did you port it?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Wasn't ported. It is directly from the latest HTC Incredible leak.
NilsP said:
Wasn't ported. It is directly from the latest HTC Incredible leak.
Click to expand...
Click to collapse
It doesnt work...fc right away
Sent from my Incredible using XDA App
doesnt work for me either, thanks for that attempt tho
wowthatisrandom said:
doesnt work for me either, thanks for that attempt tho
Click to expand...
Click to collapse
Worth a try. I guess it is dependent on something else in the leaked version.
NilsP said:
Try this one. It is from the latest leak and does have pinch.
It is for only a deodexed ROM not stock and will work if pushed to /system/app/ with adb.
Click to expand...
Click to collapse
Well it took me a while to figure out how to push with adb. I didn't know you just do it in the tools folder, I thought you ran adb shell first.
I appreciate your help, but it didn't work just immediately force closes.
Thanks anyways.
Unfortunately, I'm not going to be much help, but maybe I can offer a little explanation as to why it wont work..
From what I can tell, most if not all the HTC stuff (widgets, apps, whatever) rely on some values from /system/framework/com.htc.resources.apk. Basically it is all intertwined into a giant mess. As far as I can guess, the only way to get it to work would be to figure out what values the HD browser is looking for but can't find in the stock Inc framework. Then the stock framework would have to be edited, presumably using values from the HD framework. And as you probably guessed, just trying to run the HD framework on an otherwise stock Inc rom will send you into a never-ending boot loop.
I could be way off base, but that's my understanding of it at least.
RdBrd83 said:
Unfortunately, I'm not going to be much help, but maybe I can offer a little explanation as to why it wont work..
From what I can tell, most if not all the HTC stuff (widgets, apps, whatever) rely on some values from /system/framework/com.htc.resources.apk. Basically it is all intertwined into a giant mess. As far as I can guess, the only way to get it to work would be to figure out what values the HD browser is looking for but can't find in the stock Inc framework. Then the stock framework would have to be edited, presumably using values from the HD framework. And as you probably guessed, just trying to run the HD framework on an otherwise stock Inc rom will send you into a never-ending boot loop.
I could be way off base, but that's my understanding of it at least.
Click to expand...
Click to collapse
You are on the money. On top of resources, I believe there may be a few framework classes required to get the new functionality working properly. This will be a cat and mouse game for a while. Certainly not just an apk push. You will need to make a change, log the failure, find out what its looking for, add said resource/class, rinse, and repeat.
deficitism said:
You are on the money. On top of resources, I believe their may be a few framework classes required to get the new functionality working properly. This will be a cat and mouse game for a while. Certainly not just an apk push. You will need to make a change, log the failure, find out what its looking for, add said resource/class, rinse, and repeat.
Click to expand...
Click to collapse
I tinkered with it last night on my 2.2 ROM and there are dependencies all over the place. I think I will just move forward with the leaked ROM and tinker in my spare time.
Can anyone tell me what needs to be edited in the build.prop file to remove the sprint stuff from the phone. I'm using ES File Explorer and can edit the file with this just not sure what needs to be changed.
For instance this is what is there for the screen resolution under
#Following property will be referenced by Settings.
ro.product.display_resolution = 4.3 inch WVGA resolution
Just not sure if changing it to the proper size will do the trick or is there more?
Also see the 4 references to sprint under #Welly_Fang_12/30/2010
do I just delete sprint-us and put in verizon in the four lines of code?
Okay I installed a froyo backup to compare the build.prop files and tehy are quite different.
Under #Welly_Fang in froyo there are only two lines:
ro.cdma.home.operator.numeric = 310012
ro.cdma.home.operator.alpha = Verizon
So I'm assuming this should be the same for the gingerbread build.prop though it has four lines of code referencing sprint-us not two.
Also there is no reference to screen resolution in the froyo build.prop file and when I checked settings its not listed under hardware either. So Im thinking of just changing this to 3.7 in gingerbreads build.prop and see what happens.
If any thing goes wrong I can always flash a backup.
Well when I got into the gingerbread build.prop again I noticed there were actually two #Wolly_Fang sections. One for Verizon and one for Sprint so I just deleted all the Sprint lines of code. Then under resoluton I just changed it to 3.7 and then rebooted without any problems and it says 3.7 under hardware now.
Now I just need to figure out how to get rid of Sprint in the Market app. I'm assuming that can be done by replacing the market in system apps folder, probably market updater and market provider too. I tried doing it by installing a copy of teh new market over it but that didn't work. Any one know?
kzoodroid said:
Well when I got into the gingerbread build.prop again I noticed there were actually two #Wolly_Fang sections. One for Verizon and one for Sprint so I just deleted all the Sprint lines of code. Then under resoluton I just changed it to 3.7 and then rebooted without any problems and it says 3.7 under hardware now.
Now I just need to figure out how to get rid of Sprint in the Market app. I'm assuming that can be done by replacing the market in system apps folder, probably market updater and market provider too. I tried doing it by installing a copy of teh new market over it but that didn't work. Any one know?
Click to expand...
Click to collapse
What ROM are you on?
frostincredible said:
What ROM are you on?
Click to expand...
Click to collapse
This is just rooted stock gingerbread not a custom ROM. I read that you could edit the build.prop file using just a file explorer in a thread for another phone. Now I'm trying to find how to get rid of Sprint from the market. Not sure where they put it. I could always load the kitchen back on to my laptop and buld a custom ROM again to try and get rid of it.
I've noticed that Sprint doesn't show up in the old market just the new market. Just not sure where the market is getting this info from to know to display it.
sprint was just replaced by verizon in my market today so it must have been something on googles end as i didn't do anything to change it.
[Q] app is Your device is not compatible with this item when it is :(
Ok so I tried searching and the only answers I could come up with were for a different rom (http://forum.xda-developers.com/showpost.php?p=11626645&postcount=425) as the video said I'm a noob I hate myself, it's right lol. But I can't seem to figure this out. Before I dive in I want to know if it's similar for my current ROM to these steps. I don't want to screw anything up I tried clearing the market data, and checking the adult filter. None of that helped.
Phone is HTC DHD Telus is the provider, So I rooted to Android_Revolution_HD-4G_6.1.5 without any problem. Flashed over to the suggested radio. Phone seems to be working good and fast but I can't install the app. It ran on my phone before I rooted... what am I doing wrong. Even when I find it not through the market. It takes me to the market and says "Your device is not compatible with this item" and I know that's a load of crap. If there's someone smarter then me out there (so pretty much anyone) Help please
gearhead357 said:
Ok so I tried searching and the only answers I could come up with were for a different rom (http://forum.xda-developers.com/showpost.php?p=11626645&postcount=425) as the video said I'm a noob I hate myself, it's right lol. But I can't seem to figure this out. Before I dive in I want to know if it's similar for my current ROM to these steps. I don't want to screw anything up I tried clearing the market data, and checking the adult filter. None of that helped.
Phone is HTC DHD Telus is the provider, So I rooted to Android_Revolution_HD-4G_6.1.5 without any problem. Flashed over to the suggested radio. Phone seems to be working good and fast but I can't install the fetlife app. It ran on my phone before I rooted... what am I doing wrong. Even when I find it not through the market. It takes me to the market and says "Your device is not compatible with this item" and I know that's a load of crap. If there's someone smarter then me out there (so pretty much anyone) Help please
Click to expand...
Click to collapse
I'm having same problems with other apps and an earlyer version of ARHD(6.1.2). Would sure like to know how to resolve this. I'm thinking the ROM gives back a model, android version and manufacturer to android market(and maybe more info, i'm not an expert). If this says HTC Desire HD android 2.3.3, this is good. If this says Android Revolution Desire HD android 2.3.5 and this is not the response in the list of "the app" you want to download than market says "NO"???????? Or maybe it's something else?
At least I'm not the only one who can't figure it out
From what I can gather, its the new market causing the problem.
Wait until google fix it, or install an older market and delete the updater.
Sent from The App that Time Forgot.
+1 JagDave is right!!
And you may also try :
1. Change the LCD density to 240 by editing build.prop using buildprop editor or something from the market,
2. Reboot (Normal),
3. Go to settings, then application, find market there and clear the cache and data (very important), and
4. Open Market and try to download your apps now!!
Worked for me, dont know about you but i hope it does work for you as well!!
I ended up going and swapping to CM7 cause I was having some other issues and that seemed to fix it thanks everyone!
Thread closed at OP request.
Anyone run this latest version? If so are you having any issues with it?
I have 1.09.20 on mine. Im afraid to update. Everything runs great for me. Only reason I want to update is to use the ESCEnter, Left and Right mods. I cant find them for 1.09.20 anymore.
holy **** that's old
1.11.18 works fine for me at least
suprafreak1000 said:
holy **** that's old
1.11.18 works fine for me at least
Click to expand...
Click to collapse
When you installed did you need to back up apps? Thats another reason I havent upgraded. I read the way themes were installed changed and locations changed. I dont want to lose my Jorte theming or my MIUI theming that Ive done.
Well, first off. You can always just make a nandroid of ur 1.9 rom, and just try 1.11.18. Anything you don't like and you can go right back. I always do a fresh install, and re-dl my apps manually from the market every friday. Just easier for me.
Titanium backup, or the miui app backup should work if you decide to do a fresh install.
Location of themes? Still in sdcard/miui/themes, still mtz's. They changed a way the file compresses a while back. But that doesn't hurt anything, or change.
I'm at like 160 mtz's on my sd card i've been gathering since march, none have ever gotten messed up or lost. Same with wallpapers I've collected from the theme manager.
Ive got it installed. So far no issues other than MIUI extended settings not working at all.
The YouTube app is white when I open it
best Dincredible
htcdroidincredible23 said:
The YouTube app is white when I open it
best Dincredible
Click to expand...
Click to collapse
Try going to settings/manage apps select the youtube app and turn off compatibility mode.
I will try
best Dincredible
whitedragon551 said:
Ive got it installed. So far no issues other than MIUI extended settings not working at all.
Click to expand...
Click to collapse
Read the OP of the extended settings mod thread here. It's not just a flashable zip any more, there is the zip but you also need the apk, it should explain everything. I'd select the no-overscroll mod, last time I tried overscroll there were network issues (basically no service). I'm still on 11.11 but the no-overscroll works perfectly for me.
k_nivesout said:
Read the OP of the extended settings mod thread here. It's not just a flashable zip any more, there is the zip but you also need the apk, it should explain everything. I'd select the no-overscroll mod, last time I tried overscroll there were network issues (basically no service). I'm still on 11.11 but the no-overscroll works perfectly for me.
Click to expand...
Click to collapse
Did. The ESCenter, Right, and Switched still dont work. Which was the reason I wanted to update.
whitedragon551 said:
Did. The ESCenter, Right, and Switched still dont work. Which was the reason I wanted to update.
Click to expand...
Click to collapse
Not sure what to tell you, I just updated to 11.18 to see if it works and it's fine for me. You have to reboot or reset your status bar by changing themes in the theme manager for the right/center/switched layouts to take effect.
Everything works now except the volume button. It works in recovery, but not in the rom.
Sent from my ADR3600 while driving with Tapatalk
Did some more testing. The volume also works in apps to turn down the music level and the volume works if I open the notification toggles and hit the sound button and the volume button right after.
So I just picked up a nook simple touch and am eager to root it, I've done plenty with Android on phones, never an ebook though. I've been reading the material here and had a couple questions.
1.) It looks like 1.1 firmware is needed for most of the roots here, however B&N only lists 1.2 currently. Does anyone have a mirror to 1.1 or tell me how to get that, currently I'm on 1.0.1
2.) If I can't get 1.1 are there any roots that will work for 1.2? I've been following the thread here http://forum.xda-developers.com/showthread.php?t=1346748 and it looks like it only works from 1.1 by the sound of it.
3.) Is everyone or anyone using the NoRefreshToggle? If so what do you think? Is it worth trying it out? Dangers of using it? When you toggle it off do you get greyscale back? From the sounds of the post, it's pure black and white with it on which is fine if when I disable it, it goes back to normal greyscale images.
4.) Did anyone find out how to turn off page animations in the kindle app? not a big deal, just wondering.
Thanks a lot, look forward to trying this out.
Here's a copy of nook_1_1_update.zip I pulled down from B&N a few weeks ago: http://www.mediafire.com/?h5kn1214gfjhkcg In the end I didn't need it, so I can't confirm how the upgrade works (the instructions said just put the file within the zip on an SD card and reboot)
dobbing said:
Here's a copy of nook_1_1_update.zip I pulled down from B&N a few weeks ago: http://www.mediafire.com/?h5kn1214gfjhkcg In the end I didn't need it, so I can't confirm how the upgrade works (the instructions said just put the file within the zip on an SD card and reboot)
Click to expand...
Click to collapse
Thanks for the link
Thanks for the 1.1 post link, however I updated to 1.1.2 and followed the instructions and everything seems to be ok, I can get email, install from the market place, only thing I can't do is search the market. A search just lists a blank page and doesn't find any apps, any ideas.
As for the Kindle question, after installing kindle app and seeing the performance, this isn't a big deal at all.
Still curious on the refresh toggle however, any ideas on that, have you guys tried it out? I may post there if I don't hear back.
Thanks
RubenRybnik said:
Thanks for the 1.1 post link, however I updated to 1.1.2 and followed the instructions and everything seems to be ok, I can get email, install from the market place, only thing I can't do is search the market. A search just lists a blank page and doesn't find any apps, any ideas.
As for the Kindle question, after installing kindle app and seeing the performance, this isn't a big deal at all.
Still curious on the refresh toggle however, any ideas on that, have you guys tried it out? I may post there if I don't hear back.
Thanks
Click to expand...
Click to collapse
I have checked and as you said market search functionality is absent, it seems to be broken since the Googleplay thing.
As a way to regain it, in the mean time we get an updated market working, install Searchmarket.
The NorefreshToggle is still in early stages, but works quite well for webpages, etc.
Try it, there are no risks on it, on any program when you enable the app it will work, and when you go into a menu it will return to normal grayscale.
eded333 said:
I have checked and as you said market search functionality is absent, it seems to be broken since the Googleplay thing.
As a way to regain it, in the mean time we get an updated market working, install Searchmarket.
The NorefreshToggle is still in early stages, but works quite well for webpages, etc.
Try it, there are no risks on it, on any program when you enable the app it will work, and when you go into a menu it will return to normal grayscale.
Click to expand...
Click to collapse
How do I install Searchmarket if I can't search the market for it lol ... Do I have to install it on my phone first, then transfer the apk over to the NST, then file browse and install it from /system/app ?
I tried NoRefreshToggle, it's interesting, like you said a work in progress ... Tried it with GReader unfortunatly it shuts off between Feed view and Article view which is a pain, but I think that's probably to avoid ghosting.
As for web page viewing, Opera Mini FCs on me everytime I open it, as does the stock browser, so I haven't been able to try browsing as of yet Still looking for a solution to that one.
Thanks for all the info, really enjoying the NST if NoRefreshToggle keeps getting better this could really be a killer device
RubenRybnik said:
How do I install Searchmarket if I can't search the market for it lol ... Do I have to install it on my phone first, then transfer the apk over to the NST, then file browse and install it from /system/app ?
I tried NoRefreshToggle, it's interesting, like you said a work in progress ... Tried it with GReader unfortunatly it shuts off between Feed view and Article view which is a pain, but I think that's probably to avoid ghosting.
As for web page viewing, Opera Mini FCs on me everytime I open it, as does the stock browser, so I haven't been able to try browsing as of yet Still looking for a solution to that one.
Thanks for all the info, really enjoying the NST if NoRefreshToggle keeps getting better this could really be a killer device
Click to expand...
Click to collapse
I just use the Google Play website to initiate installs to the nook (it appears in my device list as "phone")
The included Opera Mini installation never worked for me (no FC nothing). In the end I fixed it by uninstalling and reinstalling.
dobbing said:
I just use the Google Play website to initiate installs to the nook (it appears in my device list as "phone")
The included Opera Mini installation never worked for me (no FC nothing). In the end I fixed it by uninstalling and reinstalling.
Click to expand...
Click to collapse
Didn't even know you could send apps like that to your devices, never had a need to try it before. Worked like a charm ... Opera is working now as well, thanks for the tips Really enjoying Android on the NST
So are you saying you are on 1.1.2 rooted and enjoying it?
Should I downgrade to 1.1.1 and root or just go ahead with 1.1.2?
I can't wait to try this out.
Guyman2 said:
So are you saying you are on 1.1.2 rooted and enjoying it?
Should I downgrade to 1.1.1 and root or just go ahead with 1.1.2?
I can't wait to try this out.
Click to expand...
Click to collapse
I can't speak to the upgrade patch from 1.1.1, I bought my NST yesterday, it had 1.0.1 on it, I upgraded to 1.1.2 then followed the rooting instructions for 1.1.0 or was it 1.1.1 can't remember, in any case, after rooting everything seems to be working just fine
RubenRybnik said:
...for 1.1.0 or was it 1.1.1 can't remember...
Click to expand...
Click to collapse
It was 1.1.0, there was no 1.1.1
Is there any risk upgrading to 1.1.2 from 1.1.0? Would I have to reinstall google apps &c? Did anything change in between 1.1.0 and 1.1.2? (I have heard that they may have fixed the WiFi issues that were plaguing me a few months ago.)