I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
They dont't need to support non standard dpi but they should let applications to show up in Market. This is the reason I downgraded the Market version on my phone, but this is not a solution. I hope Google will let the users decide what dpi is best for them.
Yep but as long as they fear claims and complaints nothing may happen...
At the same time the 2 persons I've been dealing with have been very cooperative and asked me lots of questions. Gave them app details, logs and after a few weeks they came back with this conclusion.
Which sort of makes respect them, after all, I'm only one of nearly 200 million Android users!
blackspp said:
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
Click to expand...
Click to collapse
Seen a couple of these pop up so far. The problem has been affecting me for a while now, but I just figured out what caused it last week. Lots of people (myself included) seem to have thought nobody else had this problem.
Post: Changing DPI and new market makes apps incompatibility
Post: [Q] Cannot update multiple installed apps, is it the new market?
blackspp said:
Yep but as long as they fear claims and complaints nothing may happen...
At the same time the 2 persons I've been dealing with have been very cooperative and asked me lots of questions. Gave them app details, logs and after a few weeks they came back with this conclusion.
Which sort of makes respect them, after all, I'm only one of nearly 200 million Android users!
Click to expand...
Click to collapse
I'm almost surprised it took so long for them to notice that trend, considering they surely have facilities to notice trends in their databases. Score one for XDA! (Very cool of Google to provide such tailored support, though!)
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
schizo said:
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
Click to expand...
Click to collapse
To "permanently" change your DPI to "XYZ", add these lines to /data/local.prop:
Code:
ro.sf.lcd_density=XYZ
qemu.sf.lcd_density=XYZ
(Note: If /data/local.prop does not exist, you may create it yourself.)
- OR -
If you would prefer that the change not persist when flashing a new ROM, you could edit /system/build.prop, which should already contain the "ro.sf.lcd_density" property unless you're on a 160dpi device. /system/build.prop will be overwritten any time you flash a new ROM, even if you do not wipe first.
Both of these methods will require a reboot for changes to take effect.
---
Alternately, if you would like to avoid editing system files by hand, there is an app called Blade Buddy which allows you to modify various properties in /data/local.prop, including LCD density.
To save your changes from Blade Buddy, tap Menu -> Save. If you choose not to reboot, you can then tap Menu -> Apply to apply the changes in RAM and restart the UI to see them in action. (Applying density without rebooting seems to be hit-or-miss.)
---
Regardless of how you set your LCD density, the Market will exhibit the incompatibility bug.
As a workaround, I have set my density "permanently" with Blade Buddy and use LCDDensity for Root to revert to default once and a while, so I can launch the Market and get all my updates. LCDDensity for Root is designed specifically to change density temporarily, on-the-fly, and on as many devices as possible.
Thanks, Mr. Bezeek. Actually what I'm looking is the permanent solution of not having to temporarily switch back and forth. As for editing .props I already have experience before with my Streak. Hehehehe
But still, thanks anyway and hope you not offended. I like it the way you help others in precise and detailed manner. Keep it up, bro *thumbs_up*
Not a problem, just doing my bit to make sure the information is out there.
As far as avoiding the temporary switching goes, I'll be on vacation for the next week, but I intend to try a little hacking when I get back, to see if I can find a way to spoof the dpi. That is, if Google doesn't throw us a bone in the meantime.
Users have reported that older versions of the Market still work. The one shipped with the latest OTA for my Evo worked for me, and I suspect that any version released before they changed the Market UI will. YMMV.
Just thought I'd toss this out there... I have a Droid X. When running MIUI 1.8.19 on it, I don't have this problem. I can set my density to 200 and the newest market (3.1.3) still works as expected. Seems as though with all the other ROMs I've tried (both blur and 2nd init), I couldn't access a lot of stuff unless I set density back to 240. I can't remember for sure, but I might have been able to set stock .602 (rooted) to 200 with no problems as well - but I'm a little iffy on that. So it would seem that MIUI has done something (perhaps not intentionally) to work around the problem. I just wish I had the smarts to figure out what that might be.
Edit: I realize that this is not a Droid X forum, but I was thinking this info might help somehow. Thanks.
tslovejoy1969 said:
Just thought I'd toss this out there... I have a Droid X. When running MIUI 1.8.19 on it, I don't have this problem. I can set my density to 200 and the newest market (3.1.3) still works as expected. Seems as though with all the other ROMs I've tried (both blur and 2nd init), I couldn't access a lot of stuff unless I set density back to 240. I can't remember for sure, but I might have been able to set stock .602 (rooted) to 200 with no problems as well - but I'm a little iffy on that. So it would seem that MIUI has done something (perhaps not intentionally) to work around the problem. I just wish I had the smarts to figure out what that might be.
Edit: I realize that this is not a Droid X forum, but I was thinking this info might help somehow. Thanks.
Click to expand...
Click to collapse
Good to know! Being able to compare a "working" ROM to mine will surely make it easier to identify a workaround.
Nice info never noted this before!! yeah i dint get any updates over a last few weeks. Im at 200 dpi.
I've been switching back to 240 periodically to get updates, not a big deal to me, but would be nice if things worked normally. My only real issue with running lower dpi (160 here) is that some apps don't scale properly. IE the Dialer.
blackspp said:
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
Click to expand...
Click to collapse
Thank for this information! I've been wondering why some standard apps weren't compatible.. It's weird, since they work if you side load them ...
I hope google finds a solution.
---------- Post added at 02:59 PM ---------- Previous post was at 02:51 PM ----------
I just switched from 190dpi to 160. Angry birds seasons is now compatible( wasn't with 190dpi)
Dank U vriendelijk
Wow. This has been driving me crazy trying to work out why apps where missing. Guess I need to swap to 240 occasionally for updates.
I am using 200 / 192 DPIs from day one. (3 months). its working fine.I never faced incompatibility issue with market. however some games doesn't run correctly which usually i don't play.
i have a workaround idea, and i started a thread to discuss here: http://forum.xda-developers.com/showthread.php?t=1288150
The google support thread for this is here: http://code.google.com/p/android/issues/detail?id=19744#makechanges
I still have this issue and if you do a web search you'll see that many still do. Reply in the support thread to raise awareness ! or if you have a workaround please share You also might want to check out his Idea thread, if you have some developing skill please help.
schizo said:
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
Click to expand...
Click to collapse
I came from a streak as well and it's this is the biggest annoyance I've had with the sgsii.
The reason why i enjoy Android over any other mobile OS is because i can tailor the OS to how i want it. Not allowing me to download apps because I'm using a non standard density is crippling.
For now, i urge everyone to go to the google support thread and simply press click the star. No need to comment (unless you found a fix), the more stars the issue gets, the more likely Google will look into it.
Seems to be fixed with the latest market version.
Sent from my GT-I9100 using XDA App
Ke11ett said:
Seems to be fixed with the latest market version.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
yeah i seem to be ok ive just got the version from androidpolice last night. im on 3.3.11 now, still cant install stuff from the website though says my phone is incompatible for everything lol
Related
First I want to thank thor2002ro for ClockworkMod Recovery and making flashing and updating fast, easy and safe, also vache for providing 3.1 update, sc2k for an easy and quick way to root any version of the A500, last but not least Interphaze Solutions (whoever he is) for the Acer Recovery Installer.
I just updated (from stock 1.141.01_EMEA_GEN3 to 4.010.22_COM_GEN1) IT works, no wifi issues, GPS now takes a lot to get location, and seeing a lot of performance improvements and fixes, was late and delayed 5 times but here it is and we are enjoying it.
Thus I wonder why no one even bothers to make a change log or something... like all the changes and improvements:
Acer_ A500_4.010.22_COM_GEN1 Applies to all Android 3.1 Acer Official Updates, OTA or Leaked (installed yourself).
New Apps
Kobo
eBook store and eBook reader
Movie Studio
Video editor
Updated Apps
Youtube
Moved fullscreen button, HD button, play button, slower double tap needed to go fullscreen/back higher performance, Cache fixed and higher cache, doesn't stutters/chops/drop frames at start or when OSD shows up (volume, controls, etc).
Flash 10.3
Music
Better looking, UI improvements, it finally updates, Google Music Beta
MusicA
Better looking, UI improvements, lots, better "listening" (now it can identify Japanese music played through my phone, SWEET).
NFS Shift
Icon changed, now is more visible and have HD on it, who knows what else is changed
Improvements/Fixes
UI is faster, more responsive, doesn't stutters like before.
Wifi Icon in notification bar now shows net activity.
Support for ACC+ streaming (or whatever uses winamp in shoutcast radio streams).
720p videos play smoothly, some 1080p videos too (simple profile ones I think, needs confirmation).
New Video Codecs Support, now MKV videos plays with Mobo Player (didn't worked before).
Video intro for games pre installed now always plays (before they crashed, but didn't force close the game)
Auto-brightness works now, it just changed its behavior, its not longer "instant", takes a while.
Recurring Issues
Randomly waking up/screen turns on
Mic still SUCKS (srly did Acer even test it by recoding someones voice and playing it back just to hear how well/awful sounds?)
New Issues
GPS wasn't broken, now it is (can see 7 sats but only onle lock after 2min and really poor signal)... maybe has something to do with GEN3 now updated to GEN1 thus missing something, can someone confirm.
Youtube widget is micro and deformed, there is a fix here in XDA.
New bloatware, or at least more packet, includes 2 songs and 2 videos (maybe 720p haven't checked) to show off in retails maybe.
You can help to make this a lot more complete, please contribute, post your discoveries, findings or changes you noticed.
And finally excuse my crappy english, as you can easily tell its not my native language, any correction and recommendations are very welcome.
Reserved for more space (I got this recomendation from a friend thank you).
Plus bump
Google+
"Huddle" is installed when installing Google+, which does *not* cone pre-installed on 3.1 - sounds like you already had it there. Installing Google+ creates two shortcuts - Google+ and Huddle
Speaking of, if anyone wants a Google+ invite, dm me - I got a few to burn
Huddle is part of the Google+ mobile app. It's for group chats.
* damn, someone beat me to posting this by a few minutes... serves me right for not refreshing
I also updated the "Vache" way from stock 1.141.01_EMEA_GEN3 to 4.010.22_COM_GEN1.
One problem - now seems to be fixed - I had on 1.141.01 was the following :
Could only connect to our company (outsourced) Exchange-Server 2007 via IMAP whereby whenever I would forward a message, the forwarded-message would "loose" the original content when send. .
I did try and (bought) Touchdown TAB, which is great, but for some reason does not allow me to retrieve/sync older messages.
Marcher
speaking of the autobrightness
Seems to only work if I set brightness to a level in the middle and reboot. Once I touch the slider again no auto bright until reboot. Any fix for this anyone is aware of?
dgoemans said:
Huddle is part of the Google+ mobile app. It's for group chats.
* damn, someone beat me to posting this by a few minutes... serves me right for not refreshing
Click to expand...
Click to collapse
Lol quick post ownage
entropy.of.avarice said:
Seems to only work if I set brightness to a level in the middle and reboot. Once I touch the slider again no auto bright until reboot. Any fix for this anyone is aware of?
Click to expand...
Click to collapse
After a while I noticed that auto brightness WORKS!!!, but its no longer "instanly", it takes awhile, give it a minute.
To test it try to put half brightness then turn on auto brightness, after a while turn off auto brightness and BOOM goes the light, so it works just changed its behavior bad auto brightness, bad
Thank you all for your contributions, updating ASAP!
I think two things mentioned in the OP *could* be hardware issues. I'm on my third A500 after returning the second one because the microphone would barely pick up my voice. This new one records my voice rather well, but voice to text is still a bit spotty (I blame the google servers for that). Another thing I have noticed is that the auto brightness on this unit actually works quite well whereas on the older unit it barely worked, if at all. I can change the brightness all the way up or down, turn the auto on and within a second or two it sets it to something more appropriate. If I cover the sensor the display dims, if I hold it towards the window it brightens. It works like an auto brightness should work. I still have 3.01 on the new unit and am waiting for the OTA update to come, whenever that is...
The second unit was manufactured in may, this unit is manufactured in april. I suggest if you have concerns about auto brightness and microphone, see if you can test another one at the store.
One question for those having issues with the microphone and auto brightness? Did you apply a screen protector? If so, was it a wet application type?
Rob
entropy.of.avarice said:
Seems to only work if I set brightness to a level in the middle and reboot. Once I touch the slider again no auto bright until reboot. Any fix for this anyone is aware of?
Click to expand...
Click to collapse
My new A500 has an auto brightness that seems to work perfectly. I tried what you said and it still works ok. The unit I returned a few days ago had a bad microphone and the auto brightness didn't seem to work well - or at all.
Rob
URL for download the update.zip please...
You didn't read the 1st post did you...
Justray said:
First I want to thank thor2002ro for ClockworkMod Recovery and making flashing and updating fast, easy and safe, also vache for providing 3.1 update, sc2k for an easy and quick way to root any version of the A500, last but not least Interphaze Solutions (whoever he is) for the Acer Recovery Installer.
Click to expand...
Click to collapse
We recomend you to do a back up first, update to 4.010.22 and after a while acer tells you theres a new update 4.010.30, thats it, you're updated and good to go, 100% stock... I still recommend a custom rom, they rock.
i want a google + invite
mikehe said:
i want a google + invite
Click to expand...
Click to collapse
What does that have to do with Acer changelog?
WereCatf said:
What does that have to do with Acer changelog?
Click to expand...
Click to collapse
Nothing, a user here offered google+ invites... and thats it
Wow, .38 and .38 already out!!! come on guys what's changed?, anything new? what's fixed? please cooperate
I haven't updated yet, wroking, waiting to get home to get .38 and .39... they're here in XDA for download
I just rebooted my iconia and didn't started , as usually be calm and don't worry, after a second try it worked.... didn't even updated yet... I feel like using windows
Justray said:
I haven't updated yet, wroking, waiting to get home to get .38 and .39... they're here in XDA for download
Click to expand...
Click to collapse
I have a hunch that there might be a problem if these are available for download freely...
remember before when increment updates are specific to what rom you're currently started from ??
users might just download the latest "increments" ... I wondered if that might screw up their device due to incompatibility ( starting rom build number )
???
WereCatf said:
What does that have to do with Acer changelog?
Click to expand...
Click to collapse
I offered g+ invites by direct message - have plenty to use up and wanted to share with XDA. Op mentioned g+ apps, figured it was a good time to share some g+ love with the interwebsb
UnicornKaz said:
I have a hunch that there might be a problem if these are available for download freely...
remember before when increment updates are specific to what rom you're currently started from ??
users might just download the latest "increments" ... I wondered if that might screw up their device due to incompatibility ( starting rom build number )
???
Click to expand...
Click to collapse
I'm quoting myself from another thread:
Well, I installed CWM, acer recovery, rooted and went from 3.0 (from stock 1.141.01_EMEA_GEN3 - 4.010.22_COM_GEN1) to 3.1 (.22), then unrooted to go for .30, rooted, got .38, updated (didn't need to unroot, didn't need to root again).
The history of my life
Click to expand...
Click to collapse
And I think the issues (reboot frozen) was due acer recovery or CWM... software highly experimental is prone to fail time to time... And nothing that a factory reset plus unnistalling recovery and cwm doesn't fix. I think but don't bet on it.
entropy.of.avarice said:
I offered g+ invites by direct message - have plenty to use up and wanted to share with XDA. Op mentioned g+ apps, figured it was a good time to share some g+ love with the interwebsb
Click to expand...
Click to collapse
I appreciate your love
According to this PDF file from Acer Global...
http://global-download.acer.com/GDF...A TAB&Step3=A500&OS=ALL&LC=en&BC=ACER&SC=PA_7
Major change notices:
1. Support for EAS - Exchange Active Sync.
2. USB Host improvements:
a. USB mouse support with cursor.
b. MTP camera support.
3. Adds media CODECs for WMV/WMA.
4. Improves media player capabilities for MPEG-4 simple profile.
5. Adds 1080p HDMI output to HD display.
6. User agent selection in browser settings allowing you to force using
desktop view.
Click to expand...
Click to collapse
Justray said:
....
I just updated (from stock 1.141.01_EMEA_GEN3 to 4.010.22_COM_GEN1) IT works, no wifi issues, GPS now takes a lot to get location, and seeing a lot of performance improvements and fixes, was late and delayed 5 times but here it is and we are enjoying it.
Thus I wonder why no one even bothers to make a change log or something... like all the changes and improvements:
Acer_ A500_4.010.22_COM_GEN1 Applies to all Android 3.1 Acer Official Updates, OTA or Leaked (installed yourself).
New Apps
Kobo
eBook store and eBook reader
Movie Studio
Video editor
...
You can help to make this a lot more complete, please contribute, post your discoveries, findings or changes you noticed.
And finally excuse my crappy english, as you can easily tell its not my native language, any correction and recommendations are very welcome.
Click to expand...
Click to collapse
I got the Android 3.1 OTA update last night. I'm in Australia and my new build is Acer_A500.4.010.40_COM_GEN1
Wonder what the difference is?
As well as getting Kobo (which I don't want as I already have Kindle) I also got Zinio in the update, which "allows" me to buy magazine subscriptions which I can't get on my Kindle because Amazon won't sell them to me in Oz.
So far (less than 24 hours) everything seems to be okay except that Kaiten mail seems to be stuck somewhere. Dunno if its related.
Hello.
Im currently using Cognition V1.31, this rom includes the new Market.
What happens when I changed the DPI is that some apps wont install trough market, it says that my device is not supported. (The install button isnt present)
If I delete the new Market, and replace it with the old market everything works again.
Apps that wouldn't install using new market and DPI is, Skype and Lookout
Anyone else that have the same issues?
Yeah, Im having this problem with a lot of apps. I didn't know it was because of the DPI change, i thought it was just the new market that was having these problems?
Set dpi to 240, install apps and then set dpi back to desired custom dpi
For me it happens also with old market app.
Keeping the old market until its fixed.
Sent from my GT-I9100 using XDA Premium App
App incompatibility with custom dpi = Android bug?
I'm on an Evo, but have the same problem. I spoke to the developer of one affected app, (AutoKiller,) and to the best of their knowledge the incompatibility issue is not related to their code.
The problem is also evident at market.android.com, which identifies many apps as incompatible as of late, when using custom dpi scaling.
After picking through the manifest files of a handful of apps, I've found no relation between the apps that exhibit this problem, or even anything that sets them apart from apps that will still install normally. AutoKiller even specifies in the manifest that any density screen should be supported. Additionally, there is no apparent connection to the target and required SDK versions.
I'm about ready to call this an Android bug, maybe a Market bug, even. The Android Dev Guide page on "Supporting Multiple Screens" implies that valid ranges for an hdpi display are between 200 and 279. I tested this range on my Evo and found that not a single framework resource breaks within it. Immediately outside this range - i.e. 199 or 280 - certain screen elements fail to display properly.
Honestly, it's getting annoying really fast. If I have some more time to look into it later, I may file a bug at Google Code. At the very least, the cause of this "incompatibility" nonsense should be documented in the Android Dev Guide, so that it can be anticipated, understood, and avoided when appropriate.
(I can't post links yet, so find the "Supporting Multiple Screens" document @ developer.android.com/guide/practices/screens_support.html if interested.)
Im running on an Xperia Play with a DPI of 200 (Default: 240) and cant download essential apps that have said bug (Ex. Facebook). Hopefully we find a solution.
I thought I was the only one with this problem. I just recently started using Gingermod asop rom and everything was working perfect until I changed DPI and tried to update some apps.
doesnt do anything with the dpi but.
http://amip.tools-for.net/wiki/android/marketaccess
It's not a bug, it's a feature. The market checks your device resolution against what the dev reported to work. If it's too high the app might not work at all or draw incorrectly. Some apps have HD versions which work with higher DPI's check those out.
GIR said:
It's not a bug, it's a feature. The market checks your device resolution against what the dev reported to work. If it's too high the app might not work at all or draw incorrectly. Some apps have HD versions which work with higher DPI's check those out.
Click to expand...
Click to collapse
Devs I have spoken to report that they have NOT intended for this to happen. Additionally, I have yet to find a single APK which suffers from this problem and has DPI constraints defined within its AndroidManifest.xml.
I have ripped apart over half a dozen apps trying to find the cause of this, and as a matter of fact, the first one I opened up explicitly specifies compatibility with ANY screen density.
Feature? That's not what it's called when even the devs don't have control over it.
(For clarity, an optional declaration in an application's AndroidManifest.xml is what determines screen density constraints, if any. By default, applications willingly install and run on any screen density for which they have fitting resources. From the dev's standpoint, these densities are not measured in exact pixels, but instead in named ranges (ldpi, mdpi, hdpi, and xhdpi.) When outfitted with resources that match the screen density range, the system scales resources at runtime to meet its exact needs. For more information about how Android handles screen density, please review the article I referenced before.)
You guys are on the right track.
Custom dpi (lcd density) seems to cause the "incompatible" problem with the new market.
http://forum.xda-developers.com/showthread.php?t=1196417
Going back to 240 dpi and clearing market data makes everything work as it should.
You can then go back to your custom dpi, but most users are reporting the problem comes back after a while.
Thanks for the heads-up - I had no idea it would have been from the DPI setting.
It would be great if there were a way to spoof density, so the market always identifies at 240dpi, (or appropriate.) Switching and rebooting all the time sucks. Anyone with some smali skills want to try hard-coding it into the new Market.apk? I will be trying, but I've had zero luck with APK modding thus far
Sent from gingerbread-evo-deck
Google is apparently aware of the problem and considering what to do about it. Post: "Anyone with different LCD density and Market issue, look here"
In the meantime, I have found that doing a soft-reversion to 240 with LCDDensity For Root when I want to run updates is not too much hassle.
thanks bazofia
bazofia said:
Set dpi to 240, install apps and then set dpi back to desired custom dpi
Click to expand...
Click to collapse
Thanks man!
Check out this thread, worked for me:
http://forum.xda-developers.com/showthread.php?t=1839871
Just download one of the attached files and flash in CWM.
Sent from my GT-I9100
Device Info:
Nook Color running B&N 1.2 (Android 2.2.1)
ManualNooter 4-6-16
OC at up to 1.2GHz using Froyo 1.2 dalingrin OC emmc 090111
Problem: Text in some apps cannot be seen (ie Titanium Backup "Filters" screen).
Observations: This problem seems to happen with B&N Software Versions ABOVE 1.2 (I am currently running 1.2 because of this issue).
Search Results: I've only found mention of this problem (or something close to it) in two places: HERE and HERE.
Recommended Fix or Workaround: NONE
I just inherited a Nook Color about three weeks ago, it was reset to factory defaults (B&N 1.1). The person I got it from was running B&N Software version 1.2 with the latest recommended ManualNootered version (manualnooter-4-6-16) at that time. He could not get B&N Version 1.3 to work right. When I got the Nook, the first thing I did was to update it to B&N 1.3 and root it with the latest ManualNooter procedures, which worked great (the procedures had been updated since the person I got it from had tried to root B&N 1.3). Thanks GabrialDestruir!
One of the first apps I purchased was Titanium Backup. I noticed in Titanium's Filters screen there were Radio Buttons that had no text next to them. I was brand new to Android and had a lot to learn, so I made note of this issue to return to later. When I finally got around to addressing this issue, I discovered others had the same problem, but so far it was not addressed within the development community.
In my experimenting I have crashed and re-rooted the device many times, so I know the problem is consistent. I was becoming frustrated and asked the previous owner if he had the same issue with B&N 1.2. He did not. As of this morning, I have returned to B&N Software Version 1.2 and I can now see all the text that was invisible before - in every app I've tested and remembered had the issue.
The specifications above are the only changes needed to reproduce the problem. As soon as I was up and running, I downloaded Titanium Backup from Market. When I rooted the Nook using B&N Software version 1.2, all text was visible. Following the procedures to get the system up to the same place with B&N 1.3, the text problem reappears (text disappears).
Any help with this problem would be greatly appreciated. If you have any questions for me or if I have forgotten a critical piece of information, please do not hesitate to post what you need here, I will be checking it daily.
Thank you for your time, effort, and help XDA! You've made a complicated procedure very simple.
I am experiencing the same problems with dialog boxes in many apps and widgets. I too have tried to find a solution.
Sent from my BNRV200 using Tapatalk
milliman said:
I am experiencing the same problems with dialog boxes in many apps and widgets. I too have tried to find a solution.
Sent from my BNRV200 using Tapatalk
Click to expand...
Click to collapse
Changing the dpi in build.prop to 160 helps, but does not cure the problem.
framitz said:
Changing the dpi in build.prop to 160 helps, but does not cure the problem.
Click to expand...
Click to collapse
Can I do that with LCD resolution?
This has always been a problem with the stock ROM, IIRC it's because typical Android text is Black and it's White on the stock ROM, therefore by default it's White on White in some apps.
If you don't need the Read to Me kids books or Magazines, use CM7 and the Nook market app, it doesn't have this problem and does much more.
khaytsus said:
This has always been a problem with the stock ROM, IIRC it's because typical Android text is Black and it's White on the stock ROM, therefore by default it's White on White in some apps.
If you don't need the Read to Me kids books or Magazines, use CM7 and the Nook market app, it doesn't have this problem and does much more.
Click to expand...
Click to collapse
Yea, so far, that's what I figured - the Nook is using a white background and if a program does not explicitly define the background and foreground text colors, but assumes the background is black, this is when the problem occurs.
I guess what I was wondering is if there is a way to change the default background color for the Nooks to black, and the default foreground text color to white. I read somewhere about "theme-ing," though, like I said, I am new to Android, could theme-ing be a solution?
I don't get your second statement. I already use CM7 (but only so far as for booting to use ManualNooter), and I have no idea what "Nook market app" you are referring to, or the Kid Reading stuff - do you meant the stock B&N stuff?. Am I missing a key concept here?
Or, possibly, are you suggesting I use CM7 to install a different ROM and skip the Nooter method altogether? I was actually beginning to research this - I can do without all the B&N stuff, it doesn't work right anyway and I have disabled much of the B&N apps. If flashing a different ROM fixes this and "does much more," I'm all for it. It will just take me doing a little more research and someone confirming this is what you are referring to.
khaytsus said:
This has always been a problem with the stock ROM, IIRC it's because typical Android text is Black and it's White on the stock ROM, therefore by default it's White on White in some apps.
If you don't need the Read to Me kids books or Magazines, use CM7 and the Nook market app, it doesn't have this problem and does much more.
Click to expand...
Click to collapse
I see! I will have to see if I can dig into the nook a little deeper and see if I can do anything about that. It is annoying but I'm not annoyed enough to change to CM7 yet! Plus I have a People subscription that I am enjoying ATM.
Trasd..You are using CWM to boot to manual nooter. CM7 is something else.
Anemailname said:
Trasd..You are using CWM to boot to manual nooter. CM7 is something else.
Click to expand...
Click to collapse
Ah, thank you, I was wondering how some people were runnig higher versions of Android - now I know.
Is it weird I love this stuff?
Well, as they say, back to the drawing board....
EDITED
The theory below is NOT the problem, but I left it up because I cannot delete it and is serves as reminder. Sorry.
ORIGINAL
I have made a discovery; the problem seems to happen, not because of background color assumptions, but when styles are used (an app developer, who was kind enough to debug and redesign his app for me, discovered this).
I am almost to the point in my self-education with Android and Java programming that I can verify this myself, but I am not quite there yet. If someone does verify this, could you please post your findings here?
As you can tell, I haven't flashed the ROM yet, and may not for awhile. It's running OK and I really want to concentrate on programming for the time being.
As more and more developers use styles though, I may not have a choice.
First, please excuse any typos made by me. I'm running an expired version of Swiftkey, which doesn't give me any autocorrect features. (this is actually relevant to my problem.) I just weny out today and purchased a prepaid google play card to make some more purchases when, behold, I find that the paid version of swiftkey is no longer "compatible" with my nook color. I found that to be true with the majority of apps that I have installed. (out of hundreds of apps, only about 35 of them claim to be compatible w/ my nook color. Of course, these apps aren't truly incompatible. I already have all of them downloaded and running flawlessly on my nook. So why the influx of "incompatible" apps? Has anybody else had this problem?
One thing I would note is that I changed my device model to a nexus 7. I did this for various reasons. For one, I needed to access some google books on my nook, but tey weren't compatible with ereaders (the nook is registered as an ereader), they were compatible with tablets though, so I edited some system files, cleared the cache and data for both the play store and google books, and I ended up getting the books that I wamted on my nook. I could see how this could cause problems with compatibility, but my nook had been altered for about 2+ weeks and nothing has happened to the play store since I changed the system files (that I know of). After all, if a problem would have decided to arise, it would have done so when I replaced the market cache, not randomly during a weekday. I'm next to certain that this sky-rocketed incompatibility did not originate at the time of alteration, as I just downloaded jetpack joyride only a day or two before it showed up as incompatible with my nook in the play store. I believe that I've only had this problem for the better of 3 days. Has anybody else haf this problem too?
System specs are the default of verygreen, though I'm currently running a nightly build of cm7. I think all this info is in my signature already. Note that I haven't changed anything on my tablet except for dpi density (set it back to 160), as I considered the possibility that it could have been caused by dpi problems, which it apparently isn't. This was after I notoced the increase of incompatible apps.
Again, take note that many of these "incompatible" apps are already installed and running fine on my nook color.
I'm sorry if I don't have very much helpful information. I'm confused, worried, and tired. When writing this, I could have even been half asleep. Please forgive me if I'm acting like an idiot.
Anyways, has anybody else had this problem? Cn anybody recreate my problem? Does anybosy have a way to fix this problem? Please let me know ifbyou can help
Sent from my Nook Color using the XDA Android app. The original text got deleted.
I'm running mirage 7.2 , on my Nook. I just checked and jetpack joyride is listed as compatible.
Sent from my MB860 using xda app-developers app
Running Swiftkey (purchased) on my NC running MirageKang CM7. Downloaded and installed it day before yesterday, I think.
When you changed your device to a Nexus 7... exactly what edits did you do?
You say you edited some system files as well...
If someone wants to give me the information in the Devices Thread in my signature, I will include Nexus 7 in the devices.dat for the IMEI Generator
DizzyDen said:
When you changed your device to a Nexus 7... exactly what edits did you do?
You say you edited some system files as well...
If someone wants to give me the information in the Devices Thread in my signature, I will include Nexus 7 in the devices.dat for the IMEI Generator
Click to expand...
Click to collapse
ro.product.model=Nexus 7 (with space)
ro.product.manufacturer=asus
ro.product.device=grouper
Confirmed from my second stock Nexus 7 with a broken screen already. Got a hug from an 8 year old wearing a wrist watch...the thing is FRAGILE! You should see my Nook Color, man. I dropped this thing on concrete several times already, the corner is busted in and the power button busted off a year ago, but the thing is running strong.
No wifi chip since my son dropped it in the bathtub though...let's see the N7 live through that.
I posted this here instead of in your Device Thread so people would know you got it. Maybe the wrong thing, idk...
(and bonus info..if you shake my Nook it rattles from the rice that is still shaking around in there from Project Dry...like Project Butter except more like Project Roadrunner...)
Are you sure you wiped data off Google play before changing the screen density.
Sent from my MT11i using xda app-developers app
mateorod said:
ro.product.model=Nexus 7 (with space)
ro.product.manufacturer=asus
ro.product.device=grouper
Confirmed from my second stock Nexus 7 with a broken screen already. Got a hug from an 8 year old wearing a wrist watch...the thing is FRAGILE! You should see my Nook Color, man. I dropped this thing on concrete several times already, the corner is busted in and the power button busted off a year ago, but the thing is running strong.
No wifi chip since my son dropped it in the bathtub though...let's see the N7 live through that.
I posted this here instead of in your Device Thread so people would know you got it. Maybe the wrong thing, idk...
(and bonus info..if you shake my Nook it rattles from the rice that is still shaking around in there from Project Dry...like Project Butter except more like Project Roadrunner...)
Click to expand...
Click to collapse
Thanks, added to devices.dat... will be uploaded in my devices thread in a minute.
SacTappingUni said:
I just weny out today and purchased a prepaid google play card to make some more purchases when, behold, I find that the paid version of swiftkey is no longer "compatible" with my nook color. I found that to be true with the majority of apps that I have installed. (out of hundreds of apps, only about 35 of them claim to be compatible w/ my nook color. Of course, these apps aren't truly incompatible. I already have all of them downloaded and running flawlessly on my nook. So why the influx of "incompatible" apps? Has anybody else had this problem?
Click to expand...
Click to collapse
I'm having a similar problem. Just changed from a rooted Nook Color running 1.X to a CM7 MiRaGe. Many apps are incompatible. So wiped/reinstalled everything. Before connecting to a Google account, I gave my NC a IMEI, thinking that would help. No luck. (With DizzyDen's IMEI generator, I tried NookColor stock 1.4.X, DizzyDen's CM7 settings, and Samsung Galaxy Tab.) Example incompatible app: Chrome.
Other ideas?
Thanks in advance...
Jake5Snooze said:
I'm having a similar problem. Just changed from a rooted Nook Color running 1.X to a CM7 MiRaGe. Many apps are incompatible. So wiped/reinstalled everything. Before connecting to a Google account, I gave my NC a IMEI, thinking that would help. No luck. (With DizzyDen's IMEI generator, I tried NookColor stock 1.4.X, DizzyDen's CM7 settings, and Samsung Galaxy Tab.) Example incompatible app: Chrome.
Other ideas?
Thanks in advance...
Click to expand...
Click to collapse
Chrome will not work with CM7 because that app is built for ICS Android 4.0 and up only. I looked over the permissions for that app.
DizzyDen said:
When you changed your device to a Nexus 7... exactly what edits did you do?
You say you edited some system files as well...
Click to expand...
Click to collapse
I changed the device info and manufacturer info and whatnot to match the Nexus 7.
In later news, after it was set to 160 dpi for a night, it deleted a couple of my apps and data caches in many of my important apps. Then it let me purchase swiftkey. But after setting my dpi back to 180, it showed as incompatible again. Making the dpi density is causing this?
Setting the dpi to 180 will definitely cause app incompatablity. The play store only likes 120, 160, 240 and now 172 for their new tablet. Most apps aren't compatible with nonstandard dpis. You can set to 160 in puild.prop, go to settings -> apps and clear data for google play. Then go into the market and download happily. When finished, change back to 180. You will have trouble updating the apps without changing back but it does work. Clearing the data just Makes google look again at your system. Otherwise, it takes a while before the changed dpi registers with the playstore.
Yes, non standard (160, 240 are "standard") density (dpi) settings will cause compatability issues.
Well, I guess that we've figured out the problem. I don't have anything against setting my dpi to 160. It's just that Google Play Music will only work if my nook's dpi is set to 180 or more. I supposed I'll have to find another fix for Google Play Music. Thanks guys!
Hi all, I bought an m3 a couple of weeks ago and the interface for all my apps show up as they would on a phone display rather than on a tablet.
My question is, if I root the device and just put straight android on, would I be able to specify that this is a tablet device rather than a phone? Or even, are there 2 versions available to install? Or is all this built into the hardware?
I know you can shrink the size of text and the general look within settings but that's not the issue. it's how the apps function .e.g. on some apps if I click on a link it takes me to another page rather than just popping up on a side bar. I had a Samsung previously, identical screen size and I can see the difference.
Any help is much appreciated
Thanks
Dig around on this forum, there are a few threads. If you are rooted there are ways to change the DPI which will trigger the apps to correctly display tablet mode. Less severe than loading a ROM.
Here is one of them:
https://forum.xda-developers.com/mediapad-m3/help/huawei-mediapad-m3-chrome-running-phone-t3487236
portisgreg said:
Hi all, I bought an m3 a couple of weeks ago and the interface for all my apps show up as they would on a phone display rather than on a tablet.
My question is, if I root the device and just put straight android on, would I be able to specify that this is a tablet device rather than a phone? Or even, are there 2 versions available to install? Or is all this built into the hardware?
I know you can shrink the size of text and the general look within settings but that's not the issue. it's how the apps function .e.g. on some apps if I click on a link it takes me to another page rather than just popping up on a side bar. I had a Samsung previously, identical screen size and I can see the difference.
Any help is much appreciated
Thanks
Click to expand...
Click to collapse
Hi!
Unlikely it is a known issue. Nothing you can do except changing the dpi to 325. If you do that all apps run in tablet mode but if you restart the tab it goes back over 400 dpi so it's not a perfect solution.
Thanks for the replies I've managed to root it and I got a really terrible rom (the only one I could find in the forums)
A couple more questions:
1. the density settings don't stay even if you root - it there any way to keep them?
2. are there any better ROMs than this?
Thanks
Greg
Ok!
So here's the latest build from Huawei with Android 7.0.
I accept no liability as it's clearly a pre-release with glitches etc but I've not found any issues yet
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1224/g490/v80058/f2/full/update.zip
I used the Huawei Firmware Finder Team Tool to find it.
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
portisgreg said:
Thanks for the replies I've managed to root it and I got a really terrible rom (the only one I could find in the forums)
A couple more questions:
1. the density settings don't stay even if you root - it there any way to keep them?
2. are there any better ROMs than this?
Thanks
Greg
Click to expand...
Click to collapse
adb.exe shell wm density 330 && adb reboot
https://forum.xda-developers.com/me...chrome-running-phone-t3487236/page3?nocache=1
famedoro said:
adb.exe shell wm density 330 && adb reboot
https://forum.xda-developers.com/me...chrome-running-phone-t3487236/page3?nocache=1
Click to expand...
Click to collapse
thanks but it doesn't retain the settings after reboot still
Nougat doesn't solve this problem.
Sent from my BTV-W09 using Tapatalk