Related
[size=+3]Honeycomb SDK Port - The Return [/size]
1. Introduction
So, for quite some time, we have had the excellent work done by deeper-blue, in porting the preview SDK, which whet our appetites for more Honeycomb to come. But despite Google allowing companies to ship Honeycomb devices, we have not had a source drop. As such, i felt like taking on the challenge of making the full SDK work on the nook; and now, here we are. This is build off the SDK 11 (rather than 10), and should be compatible with all real Honeycomb apps. Lets proceed.
2. Thanks & Credits
Before i go ANY further, i want to say thanks to whose people's work enabled and inspired me.
deeper-blue - It was your original modifications to the preview SDK that allowed me to get a BIG start on converting the full SDK. Honestly, i don't know how you figured out to do most of what you did, but it works!
dc13 - Your Asus Transformer system dump provided all the nice extra apps that are in use on this rom, in addition to the update framework. Thank you for your hard work!. http://forum.sdx-developers.com/eee-pad-development/ti-x-transformer-pad-v1/
rookie1 -Your dual boot Honeycomb script provided a great basis for a non dual booting script. http://forum.xda-developers.com/showthread.php?t=959461
I admit, i put together what i could with what i could find; if anyone is unhappy with what was used, please let me know and we can rectify the issue.
3. Installation
Not a whole lot to this one. Installation requires at least CWM 3.0.1.0. I am using internal CWM, so I will only certify it with that. I guess some people use CWM SD cards, but i am not sure how well it works with them.
Load the included .zip file on the SD card, and flash.
THIS WILL WIPE YOUR SYSTEM
DO NOT install this without having a good backup of Froyo or CM7.
DO NOT FORMAT BOOT
DO NOT INSTALL THIS WITHOUT HAVING A GOOD NANDROID BACKUP
Install take a few minutes, but once you are up, you will be greeted with the setup screen. Be sure to have a good Wifi around, it makes it easier to set everything up. Also, be sure to give the system a minute or two to settle when it first boots. Once you are all setup, you will be greeted with the full Android experience. Which leads me to my last bit of info.
4. Issues
Not working
- DSP (i think i jumped the gun on this one)
- From time to time, the screen may seemingly partially lock up. If this happens, please try to get an ADB logcat and post it here ("adb shell logcat > aFileName.txt"). A reboot will fix this issue.
- SD Card - RIght now, this is the big one. Not sure what about the framework change killed hte SD card, but i dont seem to see mine any more. If anyone has any ideas,lemme know
Working
SU (thank you racks11479)
SetCPU (and all other root needing things)
Audio (thank you deeper-blue)
3D
WiFi
Market (thank you PatF, et al)
Calendar (thanks Rockwig)
Gmail
- To kill the flashing red box (thank you mazook98): http://forum.xda-developers.com/showpost.php?p=13504316&postcount=109
(and more)
5. Community
So, what to do from here? Well, i will keep doing what i can, but i am by no means an expert. I invite anyone and everyone whom could possibly help make this better. If you think you can get Root or Market working - dont even ask; grab the code and mod away. If you have any advice, please share it. Android is so amazing because of the community.. lets keep it that way!
6. Links & Releases
5/9/11[/b]
This link represents a new phase of the Honeycomb build. I have adapted the framework from the posted eee Pad V3 build (linked in section 2). I feel this is a huge step up in UI, and a good push towards a daily driver. The UI is still a bit laggy, but it isn't too bad. Again, it wont be perfectly fixable until we get the source, but for now, its coming along.
Honeycomb Hybrid - RC1
http://www.multiupload.com/71K84XF6BF
Updated ramdisk made by Racks11479, that will allow SD mounting
See: http://forum.xda-developers.com/showpost.php?p=13698333&postcount=483
http://www.multiupload.com/3D9WSPUAUZ
**** ARCHIVED: DO NOT USE *****
Honeycomb SDK - RC3
RC3 Brings in the Calandar fix (thanks Rockwig), and a new build.prop (thanks xboxexpert), as well as some cleanup.
http://www.mediafire.com/?z6a2x97hlr5ve8p
Honeycomb SDK - RC2 (thanks to declain for creating an updated rollup)
RC2 brings in the fixed SU, Market, and Audio, all in one neat package!
https://rapidshare.com/files/460775452/update-HC-rc2.zip
Honeycomb SDK - RC1
http://www.mediafire.com/?czghefkha5zetab
www.unvisible.org/files/update-HC-rc1.zip - Thanks luciferii!
Su to push to allow Superuser (thanks for the info racks11479):
http://forum.xda-developers.com/showthread.php?t=953110
**Note, if pushing to xbin does not work, push the file to bin, and also set the perms there. That got it working for me**
6a: Change Log
RC3 - 5/6/11
- Fixed Calendar
- Updated build.prop
- DPI set to 140
- Installer no longer wipes out data; all future revisions will leave user partitions alone
- Cleaned up some unneeded programs
RC2 - 5/5/11
- Fixed SU
- Fixed Sound
- Fixed Market
RC1 - Release
7. Questions and Answers
With the stock Market still being funky, what options do i have?
The system can still side load apps, so any APKs you can grab can be installed with adb. Additionally, because of this,you can install other 3rd party Markets such as Slide and Amazon, which will let you install more apps.
Can i use the HC overclocked kernel?
At this time no. I have tried using the last released HS OC kernel, and something about it causes the system to hang at the boot animation. I want to look into it further though, and see if i can discover the source of the issue.
As of RC1, the kernel shipping in this package, is the same one that is found in the "HC-v4-emmc-2nd-edition" released for the preview SDK.
What is different about this release, compared to the other SDK port
The previous port was based off of the preview SDK, which Google labeled as SDK 10. The actual release of Honeycomb however, was bumped to SDK 11. This port uses that code, which means that it should be compatible with all the new new Honeycomb apps (Google body, etc). Certain things, like the Gmail for tablets, do work, and show what Honeycomb is all about.
How much more can be done on this release?
From here, the big fixes would be:
- Getting the stock Honeycomb Market to work
- Getting audio working
- Getting newer OC kernels workin
- Smothing out the UI experience as much as possible.
How can i help?
All the source that i had available is in the .zip package. Because there is no freely available source, all the work involves modifying the released binaries and framework .jars. There is additional tweaking that can be done to the ramdisk and kernel. If you feel adventurous, all of these are in the update package, and can be tweaked at your leisure. If you think you have something, don't be shy - zip it up and let us test it!
Oh, make sure you are signed in your Google account. Reboot, check for market.
Sent from my Samsung-SPH-D700 using XDA App
marcusant said:
Oh, make sure you are signed in your Google account. Reboot, check for market.
Sent from my Samsung-SPH-D700 using XDA App
Click to expand...
Click to collapse
If not, adb push zeam and try flashing cm7 gapps.
Sent from my Samsung-SPH-D700 using XDA App
marcusant said:
If not, adb push zeam and try flashing cm7 gapps.
Sent from my Samsung-SPH-D700 using XDA App
Click to expand...
Click to collapse
Gave it a try - no go. Lots of force closes going on...
I am soooo looking forward to this. No matter how great the other roms are. I just love the Honeycomb UI. Downloading now and will play around with it and hopefully will be able to contribute in someway.
Thanks,
Racks
Thanks for working on this! Hopefully the issues can be fixed soon enough.
I will poke around with it also. I ran EMMC v2 for a long time and the HC UI was just so smooth.
Thanks Madcat for taking this on.
I know this was meant for EMMC. But I just prepped and installed this to my SDcard rom and boy do I loves me some honeycomb. I assume you are aware of the red border issue? Or might it be because i'm running it off an SDcard. Don't mean to throw things off with the SD install.
Thanks,
Racks
racks11479 said:
I know this was meant for EMMC. But I just prepped and installed this to my SDcard rom and boy do I loves me some honeycomb. I assume you are aware of the red border issue? Or might it be because i'm running it off an SDcard. Don't mean to throw things off with the SD install.
Thanks,
Racks
Click to expand...
Click to collapse
Aye - i am aware of the boarder, and didn't remember if there was a way to turn it off.. It was way too long since i messed with HC...
thanks dm for getting hc back into life, im sure there will be many people come out of the woodwork to help with this, it seems like youve got it mostly there. once it gets market i will be all over this
insaneturbo13 said:
thanks dm for getting hc back into life, im sure there will be many people come out of the woodwork to help with this, it seems like youve got it mostly there. once it gets market i will be all over this
Click to expand...
Click to collapse
Hey insaneturbo13 . Did realize you were a NC owner too .
@Divine_MadcatI'm hoping to come into some free time soon, and should be able to test and contribute where i can.
Thanks,
-h8
h8rift said:
Hey insaneturbo13 . Did realize you were a NC owner too .
@Divine_MadcatI'm hoping to come into some free time soon, and should be able to test and contribute where i can.
Thanks,
-h8
Click to expand...
Click to collapse
hey yea, im now a regular here, good to see a familiar face haha
owned one of these puppies for about a month now
OK, just flashed CM7 latest Gapps. Market shows up. Signed in. Can browse. Search. But unable to install any apps.
Error I'm receiving is Google Services Framework (process com.google.process.gapps) has stopped unexpectedly.
I can install backed up apps by pushing via ADB and through a File Manager
Awesome ROM! Many people will be happy to see HC development move forward.
I was able to flash this using the SD card I use to flash CM7. I had a few keyboard FCs that was stopped when I specially picked US english. Glad to see wireless working, and the SD card slot works. Nook encoded videos play poorly, but I can't tell if its the DSP or the lack of audio. Interesting to see the differences between the final SDK and the one we had previously.
Thanks again!!!
well im currently giving it a try. Like you said, market doesn't show up but i saw that in my notification bar it said that i had updates. I clicked on it and it took me to "my apps" and installed all my paid for apps just fine . I'm not able to get to the rest of the market though.
Thank you
Many thanks Divine , Have been waiting for this for a long time. love the widgets.
I am interested in this, carry on
The amazon app market works fine.
Just a random Q, but has anyone tried these?
http://nookdevs.com/Honeycomb_Google_Apps_and_Market
http://forum.xda-developers.com/showthread.php?t=941445
I know that for streakdroid 1.9.1 and before, there's option in install.txt to enable the compatibility for gameloft games.
However, I've jump to DSC gingerbread. For now, I'm having problem with the compatibility with gameloft games..（my lcd density is 160) any idea how to fix this problem?
Thanks a lot guys ！！
Could you be more specific about encountered incompatibility?
Hmmm.. When I browse with phone, the apps couldn't be found thru the market. And if I browse from computer in the android Market, and it shows that the game is not compatible with ur device. The game is mentioned is Brothers in Arms 2. Besides that, for yesterday android market 10 cents promotion, only 9 apps are showing up for me, the one dint show is one of the gameloft game. I also tried to download the apk, and after I installed, it failed to download the data package, and said that the device is not compatible. Thanks for helping me solving the problem ya, and thanks
Have you tried using market enabler to fake mobile provider?
If this doesn't help, i'll look for another fingerprints.
I don't have it handy, but the fingerprint for a Nexus S allowed me to download Asphalt 6. I reverted back to the original though before I could test the game.
Found it!
In your build.prop, find the line that starts with ro.build.fingerprint= and replace it with this one:
ro.build.fingerprint=google/sojua/crespo:2.3.6/GRH78C/93600:user/release-keys
Reboot your phone and see if it works. Make sure you make a copy of your original build.prop though just in case.
You must be rooted to do this.
n0p & lordmorphous,
Thanks for the fast response for u guys, will try it later ^_^
Anyway, thanks u guys for the great DSC rom =)
you could try getting games from gameloft wap store??
Find out what version is compatible and download it
Someone said xperia x10 mini versions work??
I have had some luck with htc desire versions as well (just dont choose any samsungs)
older adreno phone versions should be compatible.. (reminds me I need to update my gaming thread asap)
Update:
I've tried both methods, results returned seem to be the same ><
Update 2: I think is the gameloft compatibility issue.. even installed the apk file, it still failed to download the data over wifi, mentioning that the game is not compatible with your device, ask for refund. Same happen to my fren's moto ..
I'm running DSC ROM and in order to get some apps (Sleepy Jack, Tetris Free) showing up in the Market, I changed the fingerprint to:
ro.build.description=3.06.405.1 CL150597 release-keys
ro.build.fingerprint=htc_wwe/htc_ace/ace:2.3.5/GRJ90/150597.1:user/release-keys
They were succesfully installed, so what are the reasons to change the build.prop back to the DSC default?
I think there's no reason Thank you for sharing this fingerprint.
_n0p_ said:
I think there's no reason Thank you for sharing this fingerprint.
Click to expand...
Click to collapse
Thank you for answering and off course a great ROM!
So the only thing is that the Android Market now thinks that my device is a HTC Desire HD.
FYI: In order to make the spoof fingerprint work, I also changed
ro.product.brand=htc_wwe
ro.product.name=htc_ace
ro.product.device=ace
ro.product.board=spade
ro.product.manufacturer=HTC
After editing the build.prop I've had to 'Clear data' from Market app and Google Services Framework, reboot into StreakMod to Clear cache partition, Wipe dalvik cache and Fix permissions.
Djezpur said:
I'm running DSC ROM and in order to get some apps (Sleepy Jack, Tetris Free) showing up in the Market, I changed the fingerprint to:
ro.build.description=3.06.405.1 CL150597 release-keys
ro.build.fingerprint=htc_wwe/htc_ace/ace:2.3.5/GRJ90/150597.1:user/release-keys
They were succesfully installed, so what are the reasons to change the build.prop back to the DSC default?
Click to expand...
Click to collapse
thanks ! u brighten up my days
This tweak will make the camera failed to work
Hi,
I am facing a new problem with my android market updated version 3.4.4 .If I search an item in the market,it shows the result with the message that "your device isn't compatible with this item ". But if I download the same item from the developer's site ,it works without any problem.This thing happens for free apps even original Google apps like google goggles.As a result I could not able to update it regularly. Can anybody explain me please,why this thing is happening???
HTC Explorer,android 2.3.5
idhbar said:
Hi,
I am facing a new problem with my android market updated version 3.4.4 .If I search an item in the market,it shows the result with the message that "your device isn't compatible with this item ". But if I download the same item from the developer's site ,it works without any problem.This thing happens for free apps even original Google apps like google goggles.As a result I could not able to update it regularly. Can anybody explain me please,why this thing is happening???
HTC Explorer,android 2.3.5
Click to expand...
Click to collapse
Have you changed screen density, perhaps?
What about qqlauncher pro ,ez launcher ,tencent desktop and so many apps which are all running well in my set but not allowed to download it from market.
HTC Sense 3.5, Android 2.3.5
same as op. i have changed screen density and it's annoying not being able to download/update apps that work just fine
If you changed your LCD density recently, change your LCD density back to its original number and then clear the Market data...you should be able to install those apps then...and then you can change your LCD density back to what you had it set at.
you dont have to clear the market data but it does involve a reboot, install the app, then reboot again to set the desired density again.
very annoying and long winded
Its problbly the app on the app store dosent support your current device, and the app you got from the developers site was probably modified to work on you device..
Like some apps have been modded to work on qvga and hvga phones.
Change youe product details in system/build.prop if your phone is rooted and change to anu desired phone type as needed. Be carefull of it though,and make a backup of that file first. That always do the trick don't forget change back to it's original state once the app is installed.
Sent from my blek krupuk
lexobys said:
Change youe product details in system/build.prop if your phone is rooted and change to anu desired phone type as needed. Be carefull of it though,and make a backup of that file first. That always do the trick don't forget change back to it's original state once the app is installed.
Sent from my blek krupuk
Click to expand...
Click to collapse
So, are we sure that the DPI setting doesn't matter if you change the build.prop file correctly? Or do we need to do both?
Which items did you need to change, and, what do you think is the best current choice?
I followed directions I found in one thread and edited my build.prop file, didn't work [I'm using a rooted Nook Tablet]
I installed Eris market fix and problem resolved.
Can you provide the link for eris market fix ?
HTC Sense 3.5,Android 2.3.5
superlimau said:
I installed Eris market fix and problem resolved.
Click to expand...
Click to collapse
On the Evo3D, or on a Eris?
idhbar said:
Can you provide the link for eris market fix ?
HTC Sense 3.5,Android 2.3.5
Click to expand...
Click to collapse
Here man, Try this...
https://market.android.com/search?q=eris+market+fix
Eris market fix not working for my set.
HTC Sense 3.5,Android 2.3.5
LCD modder pro from the market includes a special market that fixes it
Sent from my ARCHOS 80G9 using xda premium
I got my solution here http://forum.xda-developers.com/showthread.php?t=1515021
Your Device Isn't Compatible With This Item
I gave my step-son my Galaxy S, and when he goes to the Market, it wont let him download, or update any applications. All it says is "your device isnt compatible with this item." The phone works, like it has service..its on a plan, and its connected to HIS gmail account, it just wont let him update any of the apps. is there anything i can do about it? maybe master reset it?
styndall said:
If you changed your LCD density recently, change your LCD density back to its original number and then clear the Market data...you should be able to install those apps then...and then you can change your LCD density back to what you had it set at.
Click to expand...
Click to collapse
. This worked great for me! Your a ROM saver . Thanks and I did hit the thanks button!
It seems that since Google updated Market to Google Play, I can't access or install a bunch of apps that I want.
The two that bother me right now are 'Lookout Mobile Security' and 'Firefox for Android'. If I search Google Play, neither show up in search results. If I use the browser and go directly to either Firefox's or Lookout's site to install, I get redirected to Google Play and the Install button in both cases is grayed out and nothing happens.
And I'm very unhappy that I can no longer download the apks using my computer and side load/install it.
????????????
I'm on a standard Nook Color, with the newest stable release running in EMMC:
Android version: 2.3.7
Kernel version: 2.6.32.9
Mod version: CyanogenMod 7.1.0-encore
Build No: GWK74
Everything else works fine and I have no other problems or complaints.
Can someone give me some things to try and get this working???
(is this the correct forum for this type of problem??? or can someone please direct me to the right place?? I didn't want to post this to the development forum.)
Same problem here, with last build of Mirage.
I modified the build.prop file, identifying as HTC Vision.
Playstore (in desktop) now shows HTC Vision as my device.
But still no full access to market with my nook, I can't see gmail app, for example.
I tried again to change build.prop with Nexus S as device.
Playstore has not even noticed the change.
Any hint ?
filigi said:
Same problem here, with last build of Mirage.
I modified the build.prop file, identifying as HTC Vision.
Playstore (in desktop) now shows HTC Vision as my device.
But still no full access to market with my nook, I can't see gmail app, for example.
I tried again to change build.prop with Nexus S as device.
Playstore has not even noticed the change.
Any hint ?
Click to expand...
Click to collapse
I don't have your Rom, but never had problems with Nightly Cm7 or needed to change build.prop file.
Did you try again with flashing recommended gapps for your ROM?
Unleashed from my Revolutionized Desire HD
Yes, I flashed again gapps after having wiped cache and data, and restored stock build.prop.
Now market works again.
I think I lost full market access when I changed the resolution, using LCD resolution, though this app doesn't seem to change anything in build.prop.
Maybe the solution is there: http://forum.xda-developers.com/showthread.php?t=1580827
The market has always been weird on my Nook. It randomly decides to not allow me to install some apps one day, then will allow me to install the next. Not sure what the cause is either. Just says the device is not compatible.
filigi said:
Yes, I flashed again gapps after having wiped cache and data, and restored stock build.prop.
Now market works again.
I think I lost full market access when I changed the resolution, using LCD resolution, though this app doesn't seem to change anything in build.prop.
Maybe the solution is there: http://forum.xda-developers.com/showthread.php?t=1580827
Click to expand...
Click to collapse
Any report of a fix yet? My Nook has also weirded out after changing LCD resolution!
Taken from the samiam's old cm9 thread
If you notice that some apps are missing from the market, this may be due to the fact that these ICS builds for the nook do not include support for apps which request phone permissions. Although this ideally would be fixed by developers not requesting phone permissions for their app unless it absolutely needs to be phone-specific, you can also fix it by flashing the telephony-permissions-fix.zip file located in the misc folder. You will likely want to flash this file immediately after flashing your rom.
Click to expand...
Click to collapse
greenmuggy said:
Taken from the samiam's old cm9 thread
Click to expand...
Click to collapse
Helped with a few but not what I was hoping... bit it did help
Sent from my SPH-D700 using XDA
Anything other than the standard LCD densities will not allow access to some applications. There is a list somewhere that I had bookmarked, but must have deleted it. If you search for the densities that are standard (MDPI, HDPI, etc) and set it, it may help.
Yeah, these missing apps are most likely a result of a non-standard LCD Density. To fix this, you can install a hardcoded 160 dpi play store that does not run an LCD Density check. If for any other reasons you can't access apps (different country or whatever), this hardcoded play store will let you.
See the thread with DL links here: (http://forum.xda-developers.com/showthread.php?t=1551118)
Make a backup of your vending.apk in /system/app/, and then rename the hardcoded play store to vending.apk. Place the hardcoded vending.apk in system/app/, change permissions to rw-r--r--, and reboot. Should work right away. If not, follow the additional instructions in the link above.
I take no credit nor liability for the results of following these instructions. Make backups of every file you replace and you should be alright.
here is situation:
1. I had rooted 1.4.2 with not blocked OTA and my NT updated to 1.4.3.
2. It is obvious that root and some apps stopped working and some of them even disappeared from the device (like WinAmp for example).
3. I rooted 1.4.3 with SDcard method and it looked like things are fine until I started to get my apps back.
4. I used FIREFOX as a main browser with 1.4.2 update and after registering at Play store on rooted 1.4.3 I read that FIREFOX is incompatible with my device!!! What the hell?
5. Also, my NT registered at Play as NEW device, not the old one as I had - so it seems my serial changed or something has changed in the build.prop or somewhere else in the identification part of device.
6. Besides, after root, i started installing apps and it seems Notification bar has some sort of glitches - it does not clear all the messages and keeps the last downloaded file in the list...
Can anyone point me how to fix incompatibility issue?
---------------
Now, second situation:
7. I reverted back to 1.4.2 with the img file from this post: http://forum.xda-developers.com/showthread.php?t=1663836
8. But the thing is that I want to try 1.4.3 again
9. I downloaded official update from B&N and put it onto the SDCard
10. It boots and progress bar starts to move but at some point (25% of bar) it shows me exclamation icon with '!' and says "Please restart your device and try again..."
What is this issue and how it can be fixed?
Thanks in advance.
Honestly, I have had similar issues with the play store and my Nook on 1.4.3 but if you want to block OTA updates more effectively, I have been told that the updater cannot run if you have CWM flashed rather than the stock recovery image. When I screwed my Tablet up I found that I couldn't get it to load the acclaim_update.zip or any update files until I reflashed the stock recovery image rather than CWM.
titanshadow said:
Honestly, I have had similar issues with the play store and my Nook on 1.4.3 but if you want to block OTA updates more effectively, I have been told that the updater cannot run if you have CWM flashed rather than the stock recovery image. When I screwed my Tablet up I found that I couldn't get it to load the acclaim_update.zip or any update files until I reflashed the stock recovery image rather than CWM.
Click to expand...
Click to collapse
Can you share the links or files that get your nook back to normal state?
I've been reading and reading a lot the forum but still miss something important. Step-by-step guide would be much appreciated, if possible.
I have found the same problem. When I run CM7 on the NT from an SD card, I have no app compatibility issues. But when I run from rooted stock 1.4.3, I get the app compatibility error. I even tried pasting the build.prop file from CM7 into 1.4.3 but that did not correct the problem. The same apps are coming up as not compatible. What else is the Market looking at to determine compatibility?
Nook Color
Eustace2 said:
I have found the same problem. When I run CM7 on the NT from an SD card, I have no app compatibility issues. But when I run from rooted stock 1.4.3, I get the app compatibility error. I even tried pasting the build.prop file from CM7 into 1.4.3 but that did not correct the problem. The same apps are coming up as not compatible. What else is the Market looking at to determine compatibility?
Click to expand...
Click to collapse
This was actually a fix for Nook Color... to modify the build.prop. If you copy/pasted the entire build.prop I would think it would work.
One other thing to do is
1.) manage google play
2.) clear data
3.) uninstall updates
4.) manage google market
5.) clear data
6.) manage google services framework
7.) clear data
8.) reboot
This didn't always work and I had to do this a couple time. Not sure if which step made a difference or what order but it eventually worked. And I could see as many apps as my Captivate (Galaxy I).
Anyway, again, this worked for Nook COLOR and not Tablet. Or at least I havent figured Table yet. If you figure it out. Let me know.
My recent attempt was to copy the build.prop from Nexus and I got black screen after start up. Now I had to unbrick my device and I'm back to square one.
Good luck.. Keep me posted!!!!
@rtabasco - Good plan, but it didn't work. Even when I uninstalled the update and just used the Market app. Looks like 1.4.3 may have changed something other than the build.prop file. I'll keep poking around. It would help if the Play Store would provide a little more detail about the compatibility issue.
This just gets even more strange...
Restored with 1.4.2 image from http://forum.xda-developers.com/showthread.php?t=1663836 and Google Play (after root with sdcard method) says "FIREFOX is incompatible..."
Also tried to restore with NT_stock_1.4.2_Ribbon_Root_B&N.zip from http://forum.xda-developers.com/showthread.php?t=1494367 and Google Play still says "FIREFOX is incompatible..." Besides 'Go Weather EX' is incompatible too - this is ridiculous.
Anyone has idea how to overcome this?
PepeladZ said:
This just gets even more strange...
Restored with 1.4.2 image from http://forum.xda-developers.com/showthread.php?t=1663836 and Google Play (after root with sdcard method) says "FIREFOX is incompatible..."
Also tried to restore with NT_stock_1.4.2_Ribbon_Root_B&N.zip from http://forum.xda-developers.com/showthread.php?t=1494367 and Google Play still says "FIREFOX is incompatible..." Besides 'Go Weather EX' is incompatible too - this is ridiculous.
Anyone has idea how to overcome this?
Click to expand...
Click to collapse
What is your DPI ? Do you have an easy ( free ) way to try 160 ? . The market is your friend.
old_fart said:
What is your DPI ? Do you have an easy ( free ) way to try 160 ? . The market is your friend.
Click to expand...
Click to collapse
I am set at 160 dpi and that didn't help.
old_fart said:
What is your DPI ? Do you have an easy ( free ) way to try 160 ?. The market is your friend.
Click to expand...
Click to collapse
You mean - can I access 'build.prop' and change DPI there to 160? I probably can, but why exactly 160?
Why not default "169.33333"? As I understand CM7 has '160'?
it took me less than a minute to find this one... please do more searching and reading... thank you !
http://www.youtube.com/watch?v=uKlO9gkmsKk
PepeladZ said:
You mean - can I access 'build.prop' and change DPI there to 160? I probably can, but why exactly 160?
Why not default "169.33333"? As I understand CM7 has '160'?
Click to expand...
Click to collapse
Apart from the issue we are discussing in this thread that we can't figure out, a lot of compatibility issues with a rooted NT could be eliminated by changing the screen DPI to 160 in the build.prop file. My guess is that most of the apps were written for phones with 800x480 displays (or other dimensions that are easy multiples of 800x480). Making that change had worked for me to get access to most apps I wanted until this most recent problem that has been caused by changes in 1.4.3 or in the Play Store, or both working together.
Eustace2 said:
Apart from the issue we are discussing in this thread that we can't figure out, a lot of compatibility issues with a rooted NT could be eliminated by changing the screen DPI to 160 in the build.prop file. My guess is that most of the apps were written for phones with 800x480 displays (or other dimensions that are easy multiples of 800x480). Making that change had worked for me to get access to most apps I wanted until this most recent problem that has been caused by changes in 1.4.3 or in the Play Store, or both working together.
Click to expand...
Click to collapse
Thanks for explanation. I looked in build.prop from CW7 and DPI there is set to 160. I will try and report if this solved at least firefox problem.
old_fart said:
it took me less than a minute to find this one... please do more searching and reading... thank you !
http://www.youtube.com/watch?v=uKlO9gkmsKk
Click to expand...
Click to collapse
Thank you for video, but I was not asking how to edit text document, but rather what this change will give me.
Well, BNs build.prop has separate settings for X and Y dimensions. Following the logic, it does not matter if DPI is set via one command or via two... Anyway, simply changing to 160 DPI and rebooting did not help me with firefox compatibility in play store as well as other apps that were noted to show incompatible.
Any other suggestions and ideas would be very much welcome!