Oi,
I'm currently at 540 dpi set via build.prop + a few apps modified by working (yay) AppSettings. When sleeping the phone, for the first second or two, everything looks okay, before the hour font goes crap. The date font stays fine tho, so do the notification icons. Trying to force stock (640) dpi setting on aod/clock, AodEx processes won't help. Has anybody noticed/figured out a way how to handle this?
I just did leave everything normal, and set stuff like systemui to the dpi i want with AppSettings, works fine for me.
I modified it through ADB and I see the same results. It looks like there is a differently sized black outline of the time that should be there.
I can live without always on display but i find alot of apps have enlarged resources. Most notably in the play store.
Related
I searched and could not locate any information on how to resolve the screen pixel density issue with the Honeynook demo...so I started to play around with different settings by editing the build.prop...dozens of FC's later I stopped and decided to give it a rest...
However one day while on the bus to work, I decided to try using LCD density from the market...this worked!
...but a funny thing happened, when I dropped the density over 180 the Honeycomb launcher was replaced by what looks like ASOP lock screen and black status bar with white fonts , I then installed LauncherPro...check out the screen shots. (Playing around with higher settings changes the status bar to grey with black fonts, I did not screenshot those)
Then I started looking for a way to change the wall paper and show Picasa pictures. I found a thread with an APK to 3D Gallery which worked...screen shots below.
I'm not a dev; just tinkering with these ROMs...thought it might be informational as I have seen multiple threads where they mention how Honeycomb is not for phone devices...obviously there seems to be some phone stuff in there.
- Big thanks to Deeper-Blue for making this ROM
- Dalingrin for the 1.1Ghz Kernel
- Cicada for sparking my interest in froyo on this
- Samuelhalff for all the emmc posts, I learned a lot!
Anyone I missed…my bad, but thanks!
- my colors are all inverted, some setting i must have mised using the screenshot app-
What you did was changed the LCD density to a cell phone density. Honeycomb is designed to change the IU from tablet to phone based on density settings. The max you can change it to and keep the tablet format is 160. anything beyond that changes the ui to a 2.2 like UI
wtorres141 said:
I searched and could not locate any information on how to resolve the screen pixel density issue with the Honeynook demo...so I started to play around with different settings by editing the build.prop...dozens of FC's later I stopped and decided to give it a rest...
However one day while on the bus to work, I decided to try using LCD density from the market...this worked!
...but a funny thing happened, when I dropped the density over 180 the Honeycomb launcher was replaced by what looks like ASOP lock screen and black status bar with white fonts , I then installed LauncherPro...check out the screen shots. (Playing around with higher settings changes the status bar to grey with black fonts, I did not screenshot those)
Then I started looking for a way to change the wall paper and show Picasa pictures. I found a thread with an APK to 3D Gallery which worked...screen shots below.
I'm not a dev; just tinkering with these ROMs...thought it might be informational as I have seen multiple threads where they mention how Honeycomb is not for phone devices...obviously there seems to be some phone stuff in there.
- Big thanks to Deeper-Blue for making this ROM
- Dalingrin for the 1.1Ghz Kernel
- Cicada for sparking my interest in froyo on this
- Samuelhalff for all the emmc posts, I learned a lot!
Anyone I missed…my bad, but thanks!
- my colors are all inverted, some setting i must have mised using the screenshot app-
Click to expand...
Click to collapse
I just got my One X+ yesterday.
Coming from a HD2 (Leo) this is a great leap forward! BUT: I need/want a lot of icons/text/pictures/... on my screen. (My hd2 used to be at 160dpi)
So; I rooted the One X+ and changed density to 240, which looks nice. I als installed ADW Launcher since a) I like it better and b) sense doesn't seem to work with other LCD density.
Now here's my problem: although I don't want/need sense anymore, it's off course still running in the background and is thus still producing quite a few error messages. ("HTC Sense was closed unexpectedly. ......"). Is there any way to solve this? I don't really mind Sense running in the background, but off course the error messages bother me a lot!
Can I a) block those errors somehow or b) get the 240dpi-look in another way than I got it now?
Thanks!
(also: I lost the htc flashlight app somehow and I can't install it back with the apk file (it just says: app not installed). any thoughts on that?)
I am running 250 dpi with go launcher. I don't have any sense related errors. where are you getting errors?
For reference: the errors occured just after bootup (after dialing pincode, two or three errors). Then, when I went into ES File explorer, or when I went to settings (every settings page concerning sense, like display settings etc...). Two subsequent (identical) errors.
Also, after restart, android didn't seem to remember my launcher app-preference, so I got the "Complete action using.." error. Chose "ADW Launcher EX" and tapped "always use". It remained ok untill next restart, so it didn't really bother me... Strange thing: when I chose Sense and tapped "always use" it DID remember after reboot....
Now, I first did a factory reset: nothing changed, same errors.
Then I reread your post, dashingdon, and thought: let's try some stuff...
I set the dpi to 250: no win...
I set the dpi back to 320, deleted ADW, rebooted, installed Go Launcher, set to 240 dpi: no win...
I then set the dpi to 250 and voilà: this seems to work! (need to fiddle a little more, but after 5 restarts I yet have to get my first error) I now hope play store won't mind the new lcd density...
Thank you for your help!
to all others: If you would know another solution, I'd still like to hear, since I like ADW better...
Zoomb said:
I then set the dpi to 250 and voilà: this seems to work! (need to fiddle a little more, but after 5 restarts I yet have to get my first error) I now hope play store won't mind the new lcd density...
Click to expand...
Click to collapse
If play store starts giving you incompatibility issues , just uninstall the updates for "Play Store" , clear cache and let android re-install it. that should fix.
Moderators... Please close/delete this thread.. As listed in 2nd post, there exists already another thread describing the same issue, although self-appointed moderator there claims the question isn't worthy of any help anyway...
_-------------------------------
When LCD density is lowered 240 and below, notification drawer is inaccessible... U get to see icons of new notifications received, but when u try to pull notifications drawer down, ur screen becomes dim, as though a 50% transparent notification drawer without any border has been pulled down, but no way u can select or see any of the notifications.
Anyone know a way around this?
Quick settings on right side status bar pull down appears to be OK.
SCREENSHOTS ENCLOSED FOR DETAILS:
1. Normal View.
2. Inaccessible Notification drawer (when left side of status bar is pulled down)
3. Accessible Quick Settings (when right side of status bar is pulled down)
I tried the following LCD densities:
320 - normal density - everything is fine.
300 - fine
280 - endless systemui FC
250 - as above
240 all the way down to 160 - inaccessible as described in the beginning of this post.
I generally use my phone at half the original LCD Density - 160 for ZU, with large fonts, irrespective of the ROM loaded at the time on my phone (from the days of galaxy nexus and xperia z before ZU)
I'd noticed that 4.3 stock Sony firmware had other problems when LCD density was lowered below 220 - semcphone few other Sony apps used to crash.. But with KitKat, app Sony apps work fine even at 160, but I am only unable to access notifications... Which is nonetheless an important part of android.
I am using KitKat since November, ran every build of ever custom ROM posted here or on too.I'm since...have been waiting for Sony KitKat firmware to release for a stable environment, but 300 or 320 is the only LCD density on this firmware where everything works perfectly (as opposed to 4.3 which at least offered a use able experience all the way down to 220) which isn't an option as it does not offer me any of the advantages I am used to at near half density such as tablet ui / split view framework n such..
None of the aosp/cm based Roms produce such problems even at 160... Certain things like carbon fibers (on carbon rom ) used to fc... But for such individual elements, I could just run at a higher DPI with app settings xposed module... I can't do that here, because setting systemui or android system at 300 and everything else at 160 is totally pointless..
So if anyone knows how to fix this inaccessible notification drawer and so that I may be able to use the phone with everything working as it should at 200 or less, please reply.
Please don't tell me not to lower my LCD density - that's my choice and is the reason why XDA exists - to surpass limits, not to learn to live within limits.
ok
me too i have this problem
http://forum.xda-developers.com/showthread.php?t=2690673
Does everyone's Facebook app UI become like the screenshot I attached below? I found out that this is a DPI thing. With DPI set to 320 (stock value), then Facebook UI is messed up. IF screen DPI is set to 325 or above, then the layout becomes normal. The thing is, at 325 DPI., stock apps' UI (like Contacts) will be messed up. per-app DPI settings using an Xposed module doesn't help either. So catch 22. This annoying bug has persisted since v47 or around that number, I have filed several reports but still to no avail.
If enough Z Ultra users report this then maybe Facebook devs will fix it.
* I'm on Stock 5.1.1 latest firmware
Yup, FB is the same for me but I don't think it's a bug in Facebook. There is an app in system called "com.android.overlays_305dpi" or sth which I presume sets some apps to be displayed as if the phone had 305dpi set but that is just a wild guess.
After much (very much) frustration, I have managed to find a combination of settings (minimum width in developer options /zoom/font size) that allows all my apps to display correctly. Except now the homepage looks like this:-
Is there any way to change either the icon dpi/size alone or have the whole screen dedicated to the icons because I never use Discover (so its wasted space)?
Thank you.
What combination of settings? (minimum width in developer options /zoom/font size)
I'm really sorry, I can't remember what I was using because it was unusable like that.
I now use Labs/Bixby routines to change the resolution automatically when I use the apps that were previously giving me problems. It's not a perfect solution but it's better than it was.
Plus, I don't think that the minimum dpi settings actually stick correctly on this tablet, unless I am doing something wrong.