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
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
Just wanted to congratulate you guys on a great app.
I have a Galaxy Mega 6.3 i9205 which has a resolution of 1280x720 but unfortunately a default 240 dpi.
Most parts of various themes working correctly, its just a few items are not correctly aligned.
From experience, the 240 dpi causes problems with other launchers and changing to 320 dpi fixes those launchers but makes the rest of the interface far too big and breaks some of the menus.
I was wondering if there was a way to adjust some of the themes manually or anything else I could do?
Much appreciated.
neodoughnut said:
Just wanted to congratulate you guys on a great app.
I have a Galaxy Mega 6.3 i9205 which has a resolution of 1280x720 but unfortunately a default 240 dpi.
Most parts of various themes working correctly, its just a few items are not correctly aligned.
From experience, the 240 dpi causes problems with other launchers and changing to 320 dpi fixes those launchers but makes the rest of the interface far too big and breaks some of the menus.
I was wondering if there was a way to adjust some of the themes manually or anything else I could do?
Much appreciated.
Click to expand...
Click to collapse
Hi, it's hard to say as Themer is designed to look what phone it's on, in this case the Mega isn't fully supported. The advice we could give would to to maybe try changing the resolution as well, but we can't guarantee this will work and that you should try it at your own risk.
neodoughnut said:
Just wanted to congratulate you guys on a great app. Most parts of various themes working correctly, its just a few items are not correctly aligned. From experience, the 240 dpi causes problems with other launchers and changing to 320 dpi fixes those launchers but makes the rest of the interface far too big and breaks some of the menus.
Click to expand...
Click to collapse
ThemerSupport said:
Hi, it's hard to say as Themer is designed to look what phone it's on, in this case the Mega isn't fully supported. The advice we could give would to to maybe try changing the resolution as well, but we can't guarantee this will work and that you should try it at your own risk.
Click to expand...
Click to collapse
This is why I created a similar thread a few days ago. Themer does not play well with non-stock DPI. If widgets and other graphics could be placed relative to the display margins/center (instead of absolute pixels), they should render correctly regardless of DPI.
sublimaze said:
This is why I created a similar thread a few days ago. Themer does not play well with non-stock DPI. If widgets and other graphics could be placed relative to the display margins/center (instead of absolute pixels), they should render correctly regardless of DPI.
Click to expand...
Click to collapse
Zooper already does render things like this. Try out something like Simple Sea or Pro UI. I rebuild these themes so that the anchor points for objects are relative to the side of the screen they are on. IE Top Center, Top Left, Top Right, Center, Center Left, Center Right, Bottom Center, Bottom Left, Bottom Right.
The only things that you will likely have issue with are when Zooper adds spacing, so layers such as Regular Text thats curved, Series based layers, and Progress bars that have spacing splits. Also Regular and Rich Text, that is set to an anchor of left or right, but also has a text alignment of Center, will be off by a bit. These are all as you are saying based on absolute pixel. Everything else in Zooper is based off of DIP (device independent pixels, http://developer.android.com/guide/practices/screens_support.html#density-independence)
There is NO WAY to fix these issues without breaking every Zooper widget, be it stand alone or in Themer, that was produced before your suggested change.
We do not support non-stock DPI. So if you want to use non-stock then you are going to have to do a little leg work on your own to fix the themes on your device.
ritalin said:
Zooper already does render things like this. Try out something like Simple Sea or Pro UI. I rebuild these themes so that the anchor points for objects are relative to the side of the screen they are on. IE Top Center, Top Left, Top Right, Center, Center Left, Center Right, Bottom Center, Bottom Left, Bottom Right.
The only things that you will likely have issue with are when Zooper adds spacing, so layers such as Regular Text thats curved, Series based layers, and Progress bars that have spacing splits. Also Regular and Rich Text, that is set to an anchor of left or right, but also has a text alignment of Center, will be off by a bit. These are all as you are saying based on absolute pixel. Everything else in Zooper is based off of DIP (device independent pixels, http://developer.android.com/guide/practices/screens_support.html#density-independence)
There is NO WAY to fix these issues without breaking every Zooper widget, be it stand alone or in Themer, that was produced before your suggested change.
We do not support non-stock DPI. So if you want to use non-stock then you are going to have to do a little leg work on your own to fix the themes on your device.
Click to expand...
Click to collapse
In my original thread, I mentioned the fact that graphic elements were still irregular when DPI was changed to stock. This persisted after multiple uninstalls/reinstalls, cache & dalvik wipes. But thanks for the feedback.
Sent from my SCH-I605 using Tapatalk
Was Was thinking about getting that phone but it doesn't have a Stylus and I thought it wasn't a quad core too.
From time.... CM users await DPI support....
Hispanico
Themer for Xperia U
I have an Xperia U ST25i and i have trying to install themer on it....while i can install it. I cannot access the themes.
I know that you currently do not support Xperia U for this app.. but i just wanted to know if there is a work around to this by changing the Dpi of my screen and if so, could you point me in a direction where i can get further information. Thanks
This would be a great addition for those roms who change the default dpi. In my installation of slimkat most themes are simply unusable,
karanvir90 said:
I have an Xperia U ST25i and i have trying to install themer on it....while i can install it. I cannot access the themes.
I know that you currently do not support Xperia U for this app.. but i just wanted to know if there is a work around to this by changing the Dpi of my screen and if so, could you point me in a direction where i can get further information. Thanks
Click to expand...
Click to collapse
Full Xperia U support is on its way. You can try modifying the DPI and resolution, but we'd recommend just waiting a few more weeks, it will be worth the wait
ThemerSupport said:
Full Xperia U support is on its way. You can try modifying the DPI and resolution, but we'd recommend just waiting a few more weeks, it will be worth the wait
Click to expand...
Click to collapse
I am not the kind who nags but i really can't wait anymore to get themer on my phone..... any news ??? is there light at the end of this tunnel?
Thnx man.... That Worked
karanvir90 said:
I am not the kind who nags but i really can't wait anymore to get themer on my phone..... any news ??? is there light at the end of this tunnel?
Click to expand...
Click to collapse
There is light, it's just going to take a while :fingers-crossed: Delays in this current version pushed everything else a few weeks behind schedule.
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.
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.
Hi Guys,
I scaled my interface to small, and everything looks smaller now (better). But the size of the notifications when i pull down the notification bar looks super huge and is not affected by the overall scale of the system.
Is there any way to reduce the size of this notifications?
ROOT?
do you have root access?
guztavo1 said:
Hi Guys,
I scaled my interface to small, and everything looks smaller now (better). But the size of the notifications when i pull down the notification bar looks super huge and is not affected by the overall scale of the system.
Is there any way to reduce the size of this notifications?
Click to expand...
Click to collapse
I know your pain brother. Default dpi/scaling looks like a phone for 90year old with mega eyesight issues + steps to lower it to a good looking system are too steep, so you can have either Large or tiny option. View mode setting has zero effect on size of notifications in respect of incoming notifications and notifications appearing in in quick toggle area. Text Size @ Small makes them notifications look bit better but not ideal considering its a qhd screen..
Try going for small in both of these settings. At first View Mode/Text Size set to small seemed to tiny to handle, but I got used to it already. I would rather have small and crisp text than that default large out of place crap..
No i dont have root, but what happens if i do have root?
jemeljsh said:
I know your pain brother. Default dpi/scaling looks like a phone for 90year old with mega eyesight issues + steps to lower it good looking system are too steep, so you can have either Large or tiny option. View mode setting has zero effect on size of notifications in quick toggle area and incoming. Text Size @ Small makes them notifications look bit better but not ideal considering its a qhd screen..
Try going for small in both of these settings. At first View Mode/Text Size set to small seemed to tiny to handle, but I got used to it already. I would rather have small and scrisp text than that default large out of place scalled crap..
Click to expand...
Click to collapse
You are right, i went with small on both settings, and it does feel a bit better. Thanks for the recommendation! I must admit in some apps text is extremely tiny though (like whatsapp). But well i guess thats better than those giant notifications that annoy me all the time
But on my mate 9 it works for Notification also. Only on my new Mate 10 it is not applying. I hope for a fix in the next Updates.
Live4Racing said:
But on my mate 9 it works for Notification also. Only on my new Mate 10 it is not applying. I hope for a fix in the next Updates.
Click to expand...
Click to collapse
What do you mean by "it" ? View mode ?
Its just that on mate 10 (alp-l29 8.0.0.115 (C185):
x. View mode options have zero effect on size of notifications, however,
x. Text size options does change the size of notifications, however only Text size - small looks good, however it makes other areas in phone uber-tiny..bearable but no the perfect solution..
jemeljsh said:
What do you mean by "it" ? View mode ?
Click to expand...
Click to collapse
Reduce Text size and the notification are small. On my Mate 10 non Pro there is no affect when I'm change the Text size.
Live4Racing said:
Reduce Text size and the notification are small. On my Mate 10 non Pro there is no affect when I'm change the Text size.
Click to expand...
Click to collapse
No, you are wrong. Text size does change the size of notifications. View mode is the setting that's not working properly since it has no effect on size of notifications no matter what of 3 size options you chose.
See the screenshot I made comparing 3 different sizes of Text size, which clearly show that size of notification does change depending on the chose size of "Text size".
If View mode would work properly, meaning its options would have affect on notification size than Text size - normal could be used, but unfortunately that's not the case, so in order to have decent looking phone Text Size and View mode should both be set to Small.
I think that in development options you can lower the dpi ...
Kzyw said:
I think that in development options you can
lower the dpi ...
Click to expand...
Click to collapse
so what?!
Manual change of DPI does not give you any better results than View Mode - Small, Text Size - Small. Even the slightest change of DPI from "423" (423 is what the system sets with the mentioned settings (View Mode - Small, Text Size - Small)) messes up the whole system - for example, font in Chrome and Whatsapp jumps like crazy even @ 420 which is a small step down, so in short - messing just with DPI in development options will not give you more eye candy/more decent looking system than View Mode - Small, Text Size - Small.
I get it. In all my mobile phones I have used xposed with the appsettings module, we will have to pray for xposed to arrive soon in oreo in order to be able to touch the interface of the system. Huawei must offer better tools for the density of notifications but I do not think it will fix it
Lowering the dpi also or increasing the dp in the developer options did not change the notifications size also. I was having the mate 9 and it was working perfectly for me in this regard. There should be some update to fix this issue.
jemeljsh said:
What do you mean by "it" ? View mode ?
Its just that on mate 10 (alp-l29 8.0.0.115 (C185):
x. View mode options have zero effect on size of notifications, however,
x. Text size options does change the size of notifications, however only Text size - small looks good, however it makes other areas in phone uber-tiny..bearable but no the perfect solution..
Click to expand...
Click to collapse
Some fonts are also just to big. I also changed the text style
peepee999 said:
Some fonts are also just to big. I also changed the text style
Click to expand...
Click to collapse
+ 1000
Any updates on this?
---------- Post added at 04:04 PM ---------- Previous post was at 03:27 PM ----------
nomipakistanli said:
do you have root access?
Click to expand...
Click to collapse
how would you do it with root access?
jemeljsh said:
so what?!
Manual change of DPI does not give you any better results than View Mode - Small, Text Size - Small. Even the slightest change of DPI from "423" (423 is what the system sets with the mentioned settings (View Mode - Small, Text Size - Small)) messes up the whole system - for example, font in Chrome and Whatsapp jumps like crazy even @ 420 which is a small step down, so in short - messing just with DPI in development options will not give you more eye candy/more decent looking system than View Mode - Small, Text Size - Small.
Click to expand...
Click to collapse
I did try to change it to 450dpi its still quite big but looks better than earlier
paulalbertv said:
I did try to change it to 450dpi its still quite big but looks better than earlier
Click to expand...
Click to collapse
Set mine to 492. I noticed the notification contents to shift down when I set it to 493 or higher.
I set it to view mode normal and text size small and put dpi in developer settings to 392. It looks like as it should have been standard. Anyways, now I have to change dpi after every reboot .
Planet X said:
I set it to view mode normal and text size small and put dpi in developer settings to 392. It looks like as it should have been standard. Anyways, now I have to change dpi after every reboot .
Click to expand...
Click to collapse
Me too. I noticed dpi in developer settings reverts back to 432 every after reboot. Also auto brightness. It activates after reboot even if you turned it off. I guess we should lessen rebooting from now on. ?