kernel source
FEATURES for 3.0+,
Hybrid engine,
Per app Layout, this will let you choose the UI of any app, that means you can switch apps into their tablet layouts
Per app Size, scale apps individually, this is especially important if you use tablet apps, go as small or big as you like
Per app Color, this lets you select statusbar and navbar colors for apps individually, colors will shift when you jump from one app to another
Hybrid engine makes it possible to use any tablet ready app available on your phone, start with your regular Google apps and see what treasures lie hidden in them and just how well they work on your device.
You can use hybrid engine to use all available general interface UI's aswell: Phone, Phablet, Tablet. This is safe as milk, we don't change DPI, we don't trash your market, we don't shrink all your apps or force them into layouts, you don't need to edit system files for that.
Transparent bars and color pickers, new SystemUI drawables thanks to giannisgx89
Theming Engine
Statusbar Settings, Lockscreen Settings
Multiuser support
Quicksettings -> Quicktoggles
4.2 Walls and sounds, Google stock apps
As we merge back our old CMPA feature catalogue this list will grow considerably over the coming weeks
New holo-styled theme chooser
T9 dialer
New papreferences app
DONATIONS,
to molesarecoming
to D4rKn3sSyS
to jaybob413
to aaronpoweruser
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BE WARNED, 4.2.0 is not the most bugless android, the issues are known.
INSTRUCTIONS,
1. UPDATE RECOVERY
2. FACTORY RESET
3. INSTALL ROM, GAPPS, FIX-IF ANY
4. WIPE CACHE & DALVIK CACHE
5. REBOOT
PA 2.99+ UPDATES DO NOT NEED A FACTORY RESET,
BUT YOU NEED TO INSTALL GAPPS ASWELL.
Changelogs are on the paranoid andorid google+ page
Know bugs:
graphical glitch when using pie
CREDITS,
AOSP/Google, Cyanogenmod, Goo, XDA, Krebsmilk, giannisgx89, AOKP, our users, supporters and donators, everyone who's helped us in the past, heartfelt thanks to all of you!
LINKS,
Github: www.github.com/paranoidandroid
Gerrit: review.paranoid-rom.com
BANNERS,
PARANOIDANDROID 2.16 | Only Rom on Android capable of Hybrid mode | Click and see
Just in case...
Just in case...
Can't wait. Loved paranoid on my skyrocket
Sent from my Nexus 7 using XDA Premium HD app
I already have a booting PA port for the nexus 7. If you want it I can upload it for you.
Sent from my Nexus 7 using XDA Premium HD app
That's at DPI 213 at work right now so can't really play with it atm
Screen size 1280x800
Sent from my Nexus 7 using XDA Premium HD app
Ro.sf.lcd_density=213
Can't wait, thanks!
Sent from my Nexus 7 using Tapatalk 2
ahhhhhhhhhhhhhh, Can't wait!
Sweet! Love the paranoid
Sent from my Nexus 7 using XDA Premium HD app
the density is 213
edit: got ninja'd big time.....slow internet ftw? haha
molesarecoming said:
what i need to make a running build is:
1. the value of ro.sf.density in system/build.prop
2. full screensize in pixels for width and length
3. the three treshold dpis to kick off phoneUI, phabletUI and tabletUI - PA is completely independent of this, its just for reference. you can calculate it by the formula i have given in the porting topic or just drop lower/higher dpis to find them yourself. if you calculate it, the three magic shortest-width-devicepixels are: 360 (phone), 600 (phablet) and 720 (phablet).
4. i need the full data that this http://forum.xda-developers.com/showpost.php?p=27583329&postcount=12 app spits out in all three modes. especially the screenheight and the screenlayout, that long number.
if its too complicated i'll ask around and find these values on my own but it would speed up the process considerably if any of you could do it.
thx alot!
Click to expand...
Click to collapse
1. 213
2. How can I get this info?
3.
shortSizeDP < 600 = PhoneUI
601<shortSizeDP < 719 = PhabletUI
shortSizeDP > 720
Source
4. with 213 DPI I get:
Height: 880 Width: 600 Layout: 268435475 Tablemode DPI Treshold: 213 < 321
With 601 DPI I get:
Height: 259 Width: 212 Layout: 17 Tablemode DPI Treshold: 213 < 285
I will keep updating as I get the info.
There must be something wrong because the screen size was almost useless. If anythign I think it shoudl be decreased from 213 to obtain table mode or something like that.
molesarecoming said:
this goes out to all of you who would like help,
i can not imagine anything more proper than androids one and only true hybrid rom running on this device, especially since google somehow saw the need to declare it one big phone. as always, build.prop hacks suck and degrade the device so i'd really like to have it here.
problem is, i live in germany and it'll take some while until i can get my paws on it. but i thought --- i have made ports for nexus toro & toroplus and its an official aosp device, so why not just going ahead and making a build. but there's still something i need your help for and would be very obliged if you could lend me a hand, PA needs a couple of magic values to work and these must be extracted or calculated. if you would like to help out we could get a running build pretty quickly and this topic would evolve into the official PA/nexus7 build.
first, this is what the rom will bring to the table: http://forum.xda-developers.com/showthread.php?t=1717079 i guess you can easily see the benefits here, this is different than dropping your entire device into a fixed dpi and its different than hacking android.policy into displaying the dropup-notification box. it brings total freedom, scale any app/widget or systemcomponent you like, display any app/widget/syscomponent in whatever UI mode you prefer (phone, phable, tablet). this works individually on per-app basis.
second, for reference, heres a topic i made up for our porting friends: http://forum.xda-developers.com/showthread.php?t=1619582
what i need to make a running build is:
1. the value of ro.sf.density in system/build.prop
2. full screensize in pixels for width and length
3. the three treshold dpis to kick off phoneUI, phabletUI and tabletUI - PA is completely independent of this, its just for reference. you can calculate it by the formula i have given in the porting topic or just drop lower/higher dpis to find them yourself. if you calculate it, the three magic shortest-width-devicepixels are: 360 (phone), 600 (phablet) and 720 (phablet).
4. i need the full data that this http://forum.xda-developers.com/showpost.php?p=27583329&postcount=12 app spits out in all three modes. especially the screenheight and the screenlayout, that long number.
if its too complicated i'll ask around and find these values on my own but it would speed up the process considerably if any of you could do it.
thx alot!
Click to expand...
Click to collapse
As soon as my wife gets back with mines I'll get those values if anyone hasn't. On a side note.. I need to get the wife one so she can stop using mines lol
Someone send him a N7!!!
Can't wait for this rom, rocking it right now on my SGS2
SGT7, and My Rom, have this information already in the settings, you can use that. If switches between tablet and phablet mode with a switch in the settings, if you want the treshhold it is mentioned in the android development section in a thread using a jar file in the framework.
#2
Diagonal cm (in) - 18 (7)
Resolution - 1280×800
ppcm (PPI) - 85 (216)
Aspect ratio - 8:5 (4.8:3)
Source
Hyperrunner said:
SGT7, and My Rom, have this information already in the settings, you can use that. If switches between tablet and phablet mode with a switch in the settings, if you want the treshhold it is mentioned in the android development section in a thread using a jar file in the framework.
Click to expand...
Click to collapse
thx for the offer! i guess the infos coming in here will do though.
to explain myself,
pa is independent of dpi, the system will always run in the one that google chose. the treshold dpis are only good for the gui panel, we have sliders there which you use to scale apps. if you switch an app to tabUI or phoneUI, it is separate from the dpi you chose, you can get tabUI/phone/phabUI with dpi 1 or dpi 1000000. that also applys to the phone itself, tabUI means nothing else than dropping systemUI into that UI mode and still you can scale it. in essence, with PA theres no tablet mode anymore, its hybrid. each and every app runs in whatever scale and UI mode you individually give.
thx alot guys, this gives me something to work out.
Albinoman said:
I already have a booting PA port for the nexus 7. If you want it I can upload it for you.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
you can paste it here if you want, no probs. in the future though i plan this to be PA/nex7 official as i'd like to get the device for myself and build for it.
SimPup said:
View attachment 1225923
That's at DPI 213 at work right now so can't really play with it atm
Screen size 1280x800
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
one down, two to go, thx man!
Rafase282 said:
1. 213
2. How can I get this info?
3.
shortSizeDP < 600 = PhoneUI
601<shortSizeDP < 719 = PhabletUI
shortSizeDP > 720
Source
4. with 213 DPI I get:
Height: 880 Width: 600 Layout: 268435475 Tablemode DPI Treshold: 213 < 321
With 601 DPI I get:
Height: 259 Width: 212 Layout: 17 Tablemode DPI Treshold: 213 < 285
I will keep updating as I get the info.
There must be something wrong because the screen size was almost useless. If anythign I think it shoudl be decreased from 213 to obtain table mode or something like that.
Click to expand...
Click to collapse
suppose this thing has 1280x800, then 800 is the shortest side, then according to this formula: treshold_dpi = shortest-side-dp * 160 / 600
your dpi must be 213.
turns out it is, so we got phablet down,
so your treshold dpi for tabUI should be: 177-178 (800 * 160 / 720)
and for phone: 355-356 (800 * 160 / 360)
what i need you to do is boot into these dpis and comfirm your settings is either tab or phone, then start the app i linked (in portrait-view) an post the full values.
all im really looking for is the screensizes and the layout number, because as i wrote, changing dpi to get into any mode is out of style. :fingers-crossed:
Related
REQUIRED:
Device: Nexus 10 or other devices with a screen larger than 3.5"
OS: 4.2 or 4.3 Jelly Bean
Other: ROOT access with BUSYBOX installed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What does this app do?
It allows to change the resolution and the pixels density of the screen to pre-defined settings according to standard screen aspect ratios
Why is this useful?
- Watching Video on an external monitor/tv using the hdmi output will usually mirror the screen content without correcting for aspect ratio, by setting the correct resolution and pixel density of the screen to match the monitor/tv allows to fill the entire external screen and avoid the side black bars.
- Playing games on an external monitor/tv: normally, the device will render the games to the full resolution available on the device's screen. On the case of the Nexus 10, games will be rendered to its huge resolution of 2560x1600 and then it will be scaled down to the monitor/tv screen resolution wasting GPU prepossessing power and resulting on more heat and power consumption during gaming. By reducing the screen resolution to match the external monitor/tv less processing power is needed to render the game at the lower monitor/tv's resolution, many games will even use the extra processing power available for more effects or more frames per second (depending on the game, no established by this app).
- Simulate other screen resolutions and pixel density for android developers to test their applications on the physical device and observe how their application will look on other devices.
Available options:
-Manual Settings: Allows to manually select the desired resolution and pixel density according to pre-defined standard aspect ratios.
-Auto Detection: Will run in the background and will detect HDMI connections and disconnections. On a HDMI connection detected, a notification will be presented to apply the detected screen resolution and pixel density appropriate for your screen. On a HDMI disconnection, the notification will allow to return to the device's default settings.
Reboot Mode: New Soft Reboot will only reboot the graphical interface not the entire system (Fast). Normal Full Reboot (safest, use if you find interface issues with the Soft Reboot).
Screen Size: Define your screen size (affects dpi calculation). This setting comes pre-defined for the nexus 10, but you should change it to match your screen size on other devices.
HDMI Resolution Preset: Define your preferred output resolution instead of using the Auto-Detection option .
New Default Settings: The default settings will now reset the dpi value to the factory configuration. It appears that the nexus 10 comes from factory with a dpi setup to 320 instead of 300. The new reset feature should also work for other devices.
Auto DPI Selection: No more guessing work, it will select the appropriate dpi value for the selected resolution and the screen size defined on the settings.
Screen OFF feature: Allows you turn your device's screen off while keeping the output to the hdmi to reduce the power usage. To turn the screen back ON just press the power button twice or simply disconnect the hdmi.
Touchless Profile: It applies the profile automatically upon hdmi connection without user interaction.
- The profile can either auto detect the TV resolution or apply the preset resolution
- If selected, it will turn the screen off automatically when the hdmi is in use.
- On hdmi disconnection, the screen settings will automatically return to default.
What is New
New Recovery Feature: Recovers the default screen setting after an user specified number of power/charger connections. Will restore the device if the user applied a configuration not supported by the device.
To trigger the recovery feature, plug and unplug the power/charger to the device allowing ~1s between plug/unplug as many times as defined on the settings menu, default is 3 times.
v1.27:
- New Recovery Feature to restore default setting upon cycling the power connection 3 times at ~1s between connections.
- Fixed interface issues on Nexus 7 2013.
- Support for small screens up to 3.5"
- New first time setup to ensure the user select the appropriate screen size of their devices.
- Added the screen size to the current settings display.
v1.26: Improved the Preset Resolution Input dialog to avoid incorrect inputs.
v1.25: - Improved support for devices that are naturally oriented in portrait mode (i.e. nexus 7, cellphones, etc).
- Added more resolutions, specially to support smaller devices and cellphones.
- Added "Touchless Profile" option.
v1.24: - fixed a crash issue happening on devices that did not have BusyBox installed. if you don't have busybox installed, the app will now prompt you to install it.
- fixed the Auto-Brightness feature that was awakening the screen for some devices on ambient light changes.
- Added Screen Turn OFF request for support on devices where screen turn off is not yet supported.
v1.23:
-Improved screen OFF detection mode to support more devices. Allows you turn your device's screen off while keeping the output to the hdmi to reduce the power usage
v1.22:
-Screen OFF feature.
v1.21:
-Adjusted App's interface for portrait and landscape mode, and smaller screens.
-Back compatibility with JB 4.2
-Added preset button on main application
v1.2:
- Auto DPI Selection.
- Reboot Mode Selection.
- Screen Size Selection.
- HDMI resolution Preset option.
v1.01: Code cleaning
v1.0: Initial Release
Why a reboot is needed to apply the new screen settings?
- For now the safest way to restore the entire Interface with the new resolution and pixel density is to reboot the system. The new Soft Reboot should reduce considerably the time required to reset the interface.
MOD EDIT: Link to Google Play Removed due to XDA advertising paid app/theme policy. OP can check for PM from me.
This sounds like an interesting app!
Gonna try it out, but I have a few questions, does the resolution change happen only when connected to a HDMI output? Are there any benefits to having a lower res for say regular daily use of the tablet, say like not hogging the gpu or lowering the gpu temperature?
Also, according to Xda rules you shouldn't advertise paid apps here, you either have to make a free trial or this post will get removed, but I would love to keep the thread alive...
Sent from my Nexus 10 using Tapatalk 4
s1m4an said:
This sounds like an interesting app!
Gonna try it out, but I have a few questions, does the resolution change happen only when connected to a HDMI output? Are there any benefits to having a lower res for say regular daily use of the tablet, say like not hogging the gpu or lowering the gpu temperature?
Also, according to Xda rules you shouldn't advertise paid apps here, you either have to make a free trial or this post will get removed, but I would love to keep the thread alive...
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
s1m4an,
I did not know about the paid app rules for posting at this forum; however, I am planning to release a trial or beta version specially to bring support to other devices.
You can change the resolution at any moment (without HDMI connected) by opening the app and selecting the desired resolution and pixel density and then apply the changes.
The HDMI detection just allows you to change the settings to match the detected external screen automatically without having to worry about what resolution and density you should select.
Lowering the resolution will definitely reduce the GPU utilization and GPU power consumption (heat generated) especially at graphic intensive apps like games, even at 1080p the GPU needs to render half the amount of pixels than the default resolution. I have tested this with games and I generally gain frames per second or I am able to increase the detail level of the game effects. In normal usage, GPU utilization will also be reduced but I will imagine that non graphic intensive applications will not give you such drastic difference, probably watching movies will.
Another benefit is that it allows you to test how applications will look on other devices, if you are a developer.
Thanks for the comment,
Yes i would be great if there was a trial version or something like that.. It sounds interesting..
Hi forbitel, I bought your app and I like it so far. Works fine with stock 4.3 and it's a very easy way to have a true full screen 16:9 trough HDMI. Shame to Google for giving a stupid 16:10 aspect ratio to our HDTVs.
I have better results with 16:9 2560x1400 with my tv
Setting 1920x1080 creates a weird interface in the tablet. Looks like a old phone launcher...
What I would like to see in a future update is to set a favourite resolution when HDMI is detected so we don't have to go to the app every time we want to change it.
Good work!
king conan said:
Hi forbitel, I bought your app and I like it so far. Works fine with stock 4.3 and it's a very easy way to have a true full screen 16:9 trough HDMI. Shame to Google for giving a stupid 16:10 aspect ratio to our HDTVs.
I have better results with 16:9 2560x1400 with my tv
Setting 1920x1080 creates a weird interface in the tablet. Looks like a old phone launcher...
What I would like to see in a future update is to set a favourite resolution when HDMI is detected so we don't have to go to the app every time we want to change it.
Good work!
Click to expand...
Click to collapse
king conan, Great Suggestion!, I will add that to the next update.
Thanks,
forbitel said:
king conan, Great Suggestion!, I will add that to the next update.
Thanks,
Click to expand...
Click to collapse
King Conan, the preset option added to the newest update should now do what you want.
forbitel said:
King Conan, the preset option added to the newest update should now do what you want.
Click to expand...
Click to collapse
Yes I saw the update. Thank you!
I'll try in the next hours.
But now I have a problem. I use the keyboard app "Swiftkey Tablet" and even after several reboots, going to default resolution and reinstalling the app, it's size is like 3 times the normal. It's like the app thinks I'm still in 1920x1080 and not in the default 2560x1600. And I can't use it...
The stock keyboard works fine.
I'll post a screenshot later!
Edit:
Maybe reinstalling the app was not the solution (it may keep settings in SDmemory). I'll try to erase app data and reinstall.
Edit 2: Solved.
But I really want to thank you for this app. Now I can use Nexus 10 as decent multimedia player with my TV.
New problem: sometimes I have to apply and reboot up to 3 times to get the desired resolution. I have to test more...
king conan said:
Yes I saw the update. Thank you!
I'll try in the next hours.
But now I have a problem. I use the keyboard app "Swiftkey Tablet" and even after several reboots, going to default resolution and reinstalling the app, it's size is like 3 times the normal. It's like the app thinks I'm still in 1920x1080 and not in the default 2560x1600. And I can't use it...
The stock keyboard works fine.
I'll post a screenshot later!
Edit:
Maybe reinstalling the app was not the solution (it may keep settings in SDmemory). I'll try to erase app data and reinstall.
Edit 2: Solved.
But I really want to thank you for this app. Now I can use Nexus 10 as decent multimedia player with my TV.
New problem: sometimes I have to apply and reboot up to 3 times to get the desired resolution. I have to test more...
Click to expand...
Click to collapse
What specific resolution and density are you trying to set? is it through the main application window or through the hdmi notification?
I see you updated the app again.
First try and success, resolution changed fine.
I'll try more.
With this latest update everything works great. 1 reboot needed to change resolution and its very easy to have a preset one.
Sounds like a really useful app. Unfortunately I don't really want to pay for until I know it works for me. I will probably pay once the app matures after a few updates.
Sent from my Nexus 10 using Tapatalk 4
Well, the updates are coming non stop. It works perfectly fine now and the latest update brought a great new feature: Screen off with hdmi out active.
With this app we can have finally a serious media player with the nexus 10.
Congrats to the developer.
@forbitel
Can you tell me what's the shell command (that you have implemented in the app) to "soft"reboot the GUI?
king conan said:
Yes I saw the update. Thank you!
I'll try in the next hours.
But now I have a problem. I use the keyboard app "Swiftkey Tablet" and even after several reboots, going to default resolution and reinstalling the app, it's size is like 3 times the normal. It's like the app thinks I'm still in 1920x1080 and not in the default 2560x1600. And I can't use it...
The stock keyboard works fine.
I'll post a screenshot later!
Edit:
Maybe reinstalling the app was not the solution (it may keep settings in SDmemory). I'll try to erase app data and reinstall.
Edit 2: Solved.
But I really want to thank you for this app. Now I can use Nexus 10 as decent multimedia player with my TV.
New problem: sometimes I have to apply and reboot up to 3 times to get the desired resolution. I have to test more...
Click to expand...
Click to collapse
How did you solve the keyboard problem? I was seeing the same thing but could not find a solutuion.
And what screen resolution settings are you using now that will work perfectly with your TV?
How did you solve the keyboard problem? I was seeing the same thing but could not find a solutuion.
And what screen resolution settings are you using now that will work perfectly with your TV?
Click to expand...
Click to collapse
mrruin,
I have tested few popular keyboards from the market and found the following:
- Google Keyboard: Adjust the best out all I have tested, it consistently adjust with changes of screen resolution.
- SlideIT: Somewhat adjusting to the screen resolution changes, works better than Swype and SwiftKey.
- Swype: do not dynamically adjust to screen changes, some resolutions works but wont adjust to the screen on 1080p.
- SwiftKey: do not dynamically adjust to screen changes, some resolutions works but wont adjust to the screen on 1080p.
I would recommend you use Google Keyboard when changing the resolution of the device, until these keyboards are fixed for resolution changes.
Where can I get that wallpaper?? That looks really cool.
So when are you going to release the trial betsa version like you said you would ? It has been almost 2 months
Sent from my Nexus 10 using xda app-developers app
Nexus 5 slimport HDMI
Has anyone had any luck changing the HDMI resolution?
On a Nexus 5 or any other device?
I have tried all combination of settings i can think of but it either boot loops or resolution stays on 1080p.
Im guessing when it boot loops with the cable plugged in its trying to output 720p but doesn't like it much.
I'd like to provide some sort of log if would be useful.
normskilight said:
Has anyone had any luck changing the HDMI resolution?
On a Nexus 5 or any other device?
I have tried all combination of settings i can think of but it either boot loops or resolution stays on 1080p.
Im guessing when it boot loops with the cable plugged in its trying to output 720p but doesn't like it much.
I'd like to provide some sort of log if would be useful.
Click to expand...
Click to collapse
normskilight,
I haven't tested the application on 4.4 KitKat yet, I just got my KitKat OTA few minutes ago.
I will test it soon and will get back to you.
Please keep tuned.
Regards,
[[MODS-Please move to Right Section if needed, Sorry if posted in wrong section]]
I have been trying to get used to the DPI adjustments on the GPe ROM. It appears that the default DPI is set at 400 on install but using ROMToolBox (You can use your favourite app to change DPI), I was able to tweak it to the most optimum number and concluded that DPI 289 is the most comfortable to the eye and compatible with Apps. I went all the way down to early 210s and tracked it all the way up but could not find any DPI better than 289 that accommodated the application options menus, the operation of the camera on the default GPe Lock Screen and the much nicer arrangement of the icons on the App Drawer.
You can off course try to experiment with different setups and share your findings but I think I am on to something. Enjoy the Post!
AWFRONT said:
I have been trying to get used to the DPI adjustments on the GPe ROM. It appears that the default DPI is set at 400 on install but using ROMToolBox (You can use your favourite app to change DPI), I was able to tweak it to the most optimum number and concluded that DPI 289 is the most comfortable to the eye and compatible with Apps. I went all the way down to early 210s and tracked it all the way up but could not find any DPI better than 289 that accommodated the application options menus, the operation of the camera on the default GPe Lock Screen and the much nicer arrangement of the icons on the App Drawer.
You can off course try to experiment with different setups and share your findings but I think I am on to something. Enjoy the Post!
Click to expand...
Click to collapse
wrong section bro,btw try set to 290.
Agree. I've set mine to 290 as well
Sent from my C6806_GPe using xda app-developers app
not GPe, but I have SlimKat set to 280, might just tyr 290 to see what the fuss is about
EDIT:
No real difference at 290 compared to 280, except that chrome popped out of tablet mode at 290
I've used all my android phones till now (galaxy nexus, xperia z and now z ultra) at tablet LCD density (half the default setting) - 160 for ZU, rotation locked on landscape, with large font size and at times custom font types too.
Try DPI 260 its perfect
jutley said:
Try DPI 260 its perfect
Click to expand...
Click to collapse
Thanks for the share but as I stated in my original post, if we want to enjoy using our XZU at its best as a GPe ZU, then the lowest DPI we should go for is 289 for the following reasons; Lock screen is intact with camera shortcut visible, Applications Drawer is more unified and certain applications are better handled with their options/menus visible. At DPI 260 The UI is broken, lockscreen is not complete and applications with menus have their menus missing i.e try RealCalc to see what I mean.
I would really like to hear from anyone who can go much lower than the DPI of 289 and share their findings as to whether the above issues could be experienced. If not I really want to push it as low as possible to get the best out of the XZU screen real estate without compromising stability and completeness of the UI features.
AWFRONT said:
Thanks for the share but as I stated in my original post, if we want to enjoy using our XZU at its best as a GPe ZU, then the lowest DPI we should go for is 289 for the following reasons; Lock screen is intact with camera shortcut visible, Applications Drawer is more unified and certain applications are better handled with their options/menus visible. At DPI 260 The UI is broken, lockscreen is not complete and applications with menus have their menus missing i.e try RealCalc to see what I mean.
I would really like to hear from anyone who can go much lower than the DPI of 289 and share their findings as to whether the above issues could be experienced. If not I really want to push it as low as possible to get the best out of the XZU screen real estate without compromising stability and completeness of the UI features.
Click to expand...
Click to collapse
220 dpi definitely starts to break the UI on slimkat where 280 or 290 (camera on locksceen fails at 280 but works at 290) is good for most apps that I use, I then use app settings and bump a few apps down to 220-240 (gmail etc)
How on earth are you capable of doing anything with a DPI under 200? I can't imagine getting anything done with that kind of DPI when I'm walking, or even standing up. 320 (stock) is in my opinion the best since all UI elements are properly sized and they can be tapped on without having to aim for anything.
Sent from my C6833 using Tapatalk
DPI is density per pixels
so by editing it u can change the layout, text etc.
by lowering the value u can put more content in same scrn
scrnshots will help u understand if u dont get it
If u have used the aclex rom
u may hv noticed the resolution change
since some users requested it here it iis
Instruction:- Flash thru CWM
Dpi- 110 - will make things look normal smaller on screen
Dpi- 120 - the default configuration (Stock) - (can also be called recovery.zip)
If u want any other dpis request it here and ill upload it as quickly as i can
Downloads:
View attachment 2724775
View attachment 2724776
NOTICE:
The build prop used here is from my rom - T3ROM
and since i hv used a different ringtone in my rom
u will have silent ringtone after flashing this :crying:
pls change the ringtone after flashing
also the rom version will be shown as 4.1.2 as in the stock (If u have rom name it will be gone)
any1 using this will also have some tweaks tht improve responsiveness and performance :highfive:
also if u can upload stock build.prop file from stock rom
it is present in /system/
Scrnshot will be posted in a minute
Working!!
It works in my SGS thanks.
T3snake said:
DPI is density per pixels
so by editing it u can change the layout, text etc.
by lowering the value u can put more content in same scrn
scrnshots will help u understand if u dont get it
If u have used the aclex rom
u may hv noticed the resolution change
since some users requested it here it iis
Instruction:- Flash thru CWM
Dpi- 110 - will make things look normal smaller on screen
Dpi- 120 - the default configuration (Stock) - (can also be called recovery.zip)
If u want any other dpis request it here and ill upload it as quickly as i can
Downloads:
View attachment 2724775
View attachment 2724776
Click to expand...
Click to collapse
uhmm.. actually o.o
DPI is dots per inch.. used in some printers to define print quality.. techinally for screens you'd say ppi or pixels per inch.. but eh.. everyone calls it dpi so let's just say dpi..
dpi is constant for mobile devices screen... there maybe some mobile devices which allow changing dpi but i don't know about that..
dpi is the number of physical pixels on a unit inch of a screen.. calculated by the below formula..
dpi=sqrt((x^2)+(y^2))/d (x an y are no. of pixels and d is the size of screen diagonally in inch )
no. of horizontal pixels(x) of star = 240
no. of vertical pixels of star = 320
stars screen size diagonally (d) = 3.0 inches
dpi=sqrt((x^2)+(y^2))/d
dpi=sqrt((240^2)+(320^2))/3
dpi = 133.333
dpi of star is approximately 133.. and that won't change unless you change the ro.board.lcd.. just joking.. :cyclops:
for dpi.. the higher the better.. higher dpi means more pixels per inch.. which gives more sharper and clearer picture..
how awfully awesome it would be it we could change dpi to 734 for our star.. that's full HD on a 3 inch display lol
what we indirectly, change with ro.sf.lcd_density is the scaling factor, by which the ui is scaled .. ( read on about android's density independent pixels and scaling )
this may give a impression like the resolution is changed.. but unlike in monitors where actual physical resolution is changed.. this is just a hack to scale the ui
psych.half said:
uhmm.. actually o.o
DPI is dots per inch.. used in some printers to define print quality.. techinally for screens you'd say ppi or pixels per inch.. but eh.. everyone calls it dpi so let's just say dpi..
dpi is constant for mobile devices screen... there maybe some mobile devices which allow changing dpi but i don't know about that..
dpi is the number of physical pixels on a unit inch of a screen.. calculated by the below formula..
dpi=sqrt((x^2)+(y^2))/d (x an y are no. of pixels and d is the size of screen diagonally in inch )
no. of horizontal pixels(x) of star = 240
no. of vertical pixels of star = 320
stars screen size diagonally (d) = 3.0 inches
dpi=sqrt((x^2)+(y^2))/d
dpi=sqrt((240^2)+(320^2))/3
dpi = 133.333
dpi of star is approximately 133.. and that won't change unless you change the ro.board.lcd.. just joking.. :cyclops:
for dpi.. the higher the better.. higher dpi means more pixels per inch.. which gives more sharper and clearer picture..
how awfully awesome it would be it we could change dpi to 734 for our star.. that's full HD on a 3 inch display lol
what we indirectly, change with ro.sf.lcd_density is the scaling factor, by which the ui is scaled .. ( read on about android's density independent pixels and scaling )
this may give a impression like the resolution is changed.. but unlike in monitors where actual physical resolution is changed.. this is just a hack to scale the ui
Click to expand...
Click to collapse
yes of course we cant change the dpi of the screen we cant change hardware...
everyone calls it dpi i call it dpi
emulation is enough
i made it for some users that didnt wanna edit build.prop
yes 768 dpi u were talking about
the density which we can change shud be 240 which is the one used in some tabs and the most higher res devicrs like s3
it was pathetic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
statusbar looked gud
Sent from my GT-S5282 using Tapatalk
T3snake said:
yes of course we cant change the dpi of the screen we cant change hardware...
everyone calls it dpi i call it dpi
emulation is enough
i made it for some users that didnt wanna edit build.prop
yes 768 dpi u were talking about
the density which we can change shud be 240 which is the one used in some tabs and the most higher res devicrs like s3
it was pathetic
statusbar looked gud
Sent from my GT-S5282 using Tapatalk
Click to expand...
Click to collapse
you said "DPI is density per pixels" in OP and that's wrong... that's all it was about..
by changing the ro.sf.lcd_density to 240 everthing will be bigger.. cause it changes the scaling to 2x.. which will make everything (the ui) look twice as big..
psych.half said:
you said "DPI is density per pixels" in OP and that's wrong... that's all it was about..
by changing the ro.sf.lcd_density to 240 everthing will be bigger.. cause it changes the scaling to 2x.. which will make everything (the ui) look twice as big..
Click to expand...
Click to collapse
i dunno i really knew it was dots per inch as i told some users that asked me
i dunno why i wrote density
maybe because it was density
well changing density in some apps helps a lot
Sent from my GT-S5282 using Tapatalk
T3snake said:
DPI is density per pixels
so by editing it u can change the layout, text etc.
by lowering the value u can put more content in same scrn
scrnshots will help u understand if u dont get it
If u have used the aclex rom
u may hv noticed the resolution change
since some users requested it here it iis
Instruction:- Flash thru CWM
Dpi- 110 - will make things look normal smaller on screen
Dpi- 120 - the default configuration (Stock) - (can also be called recovery.zip)
If u want any other dpis request it here and ill upload it as quickly as i can
Downloads:
View attachment 2724775
View attachment 2724776
Click to expand...
Click to collapse
Wrks well except for dialer... anyways thank u...
Vortex99 said:
Wrks well except for dialer... anyways thank u...
Click to expand...
Click to collapse
Well this was mainly for u since u requested it
use exdialer it is quite fast and doesnt give problem
also u can use app settings to set dpi per app
T3snake said:
Well this was mainly for u since u requested it
use exdialer it is quite fast and doesnt give problem
also u can use app settings to set dpi per app
Click to expand...
Click to collapse
App settings works for dialer...??
Vortex99 said:
App settings works for dialer...??
Click to expand...
Click to collapse
Yes everything
>Change Screen Resolution<
Introduction:
I'm going to write this guide to teach you how to change the Screen Resolution of your Xiaomi Mi3/Mi4 AOSP/CM Based ROM to improve the graphics performance of your Mi3 without stressing your CPU/GPU while playing games.
What you need to Download:
Resolution Changer by NoMone:
https://play.google.com/store/apps/...apk&pcampaignid=APPU_1_TXl1VcrLFoWB8QXozIGIBA
Root Browser:
https://play.google.com/store/apps/...ser&pcampaignid=APPU_1_oXl1VczIG4_s8AX7-YLQCQ
Note: Default Screen Resolution of Xiaomi Mi 3 is 1080x1920FHD @480 DPI, well what we are going to do is Change it into 720x1280HD @320 to improve performance. (Don't worry about getting the icons bigger, the reason why we have to reduce the DPI on the Build.prop is to avoid glitches and make the Icons and UI at the normal size when changing the resolution, because using the Resolution Changer alone will cause some glitches on other apps )
Steps:
1. Open Root Browser; and find /system/build.prop and open it using RB Text Editor.
2. Find ro.sf.lcd_density=480 and change it to 320.
3. Click Save.
4. Open Resolution Changer; Enter 720 Width, 1280 Height, 320 DPI
5. Click Apply and wait for it to change.
6. Click Yes to Confirm and Skip on the next dialog.
7. Now exit the app and Reboot.
After rebooting, you'll see that you've changed the Screen Resolution to FHD>HD. :good:
Congratulation, to prove it do an Antutu Benchmark test and you'll see the difference. :good:
Additional Info:
(OPTIONAL IF YOU'RE USING CUSTOM DPI ON FULL HD)
If you were using a custom DPI on FULL HD for example;
You're using 400 or 380 or 370 on 1080x1920FHD Resolution,
Do these to properly change resolution to avoid getting the UI or Icons Bigger than Normal.
Example;
If you are using 400DPI on 1080x1920FHD.
400÷3=133DPI
400-133=267DPI
so the right DPI that you're going to use would be; 267DPI on 720x1280HD PLEASE, DONT FORGET to CLICK THANKS!
Everything is working almost perfectly. Some icons are larger than they used to be. But that wasn't problem. Real problem is that SwiftKey keyboard didn't scale. So I had to revert back to Google original keyboard to reset resolution back to 1080p
Sent from my MI 3W using XDA Free mobile app
Silac_8 said:
Everything is working almost perfectly. Some icons are larger than they used to be. But that wasn't problem. Real problem is that SwiftKey keyboard didn't scale. So I had to revert back to Google original keyboard to reset resolution back to 1080p
Sent from my MI 3W using XDA Free mobile app
Click to expand...
Click to collapse
Oh I forgot to write something about Swift Keyboard, Sorry since I used Google Keyboard. but aside from Swiftkey everything is fine :good:
I have done this years ago. Not only CM/AOSP but all rooted phones.
Thanks for putting some guide though. :good::fingers-crossed:
bluerain28 said:
I have done this years ago. Not only CM/AOSP but all rooted phones.
Thanks for putting some guide though. :good::fingers-crossed:
Click to expand...
Click to collapse
I wrote this guide for those who are confused and experiencing glitches when using the Resolution Changer alone and of course for the beginners
added additional info.
I just noticed. I used 294 DPI for 720x1280
bluerain28 said:
I just noticed. I used 294 DPI for 720x1280
Click to expand...
Click to collapse
Alright! ?
Initially tried this with MIUI v5, turned out to be very bad. The icons became very large and going to back to native resolution didn't help either. Fortunately I had nandroid backup.
Later I tried it on MIUI 6, it worked!
Some glitches are there:
- On recent apps screen
- camera effects selection screen
- Calender and clock icons turned invisible
- Minor glitches in clock app
Otherwise everything looks good, and performance bump is noticeable. Excited to find out how much it improves battery life.
Thanks for sharing.
pra300 said:
Initially tried this with MIUI v5, turned out to be very bad. The icons became very large and going to back to native resolution didn't help either. Fortunately I had nandroid backup.
Later I tried it on MIUI 6, it worked!
Some glitches are there:
- On recent apps screen
- camera effects selection screen
- Calender and clock icons turned invisible
- Minor glitches in clock app
Otherwise everything looks good, and performance bump is noticeable. Excited to find out how much it improves battery life.
Thanks for sharing.
Click to expand...
Click to collapse
No problem
that's why it's for CM/AOSP Based ROM but I'm glad that it worked for you though there are some glitches.
Hi im using a a33 tab with screen dpi 160 and 480x800 resolution. Can I change this to higher resolution and dpi?
sent from xda app in my s710 using tapatalk . (*ﾟ▽ﾟ)ﾉ
andywoody12 said:
Hi im using a a33 tab with screen dpi 160 and 480x800 resolution. Can I change this to higher resolution and dpi?
sent from xda app in my s710 using tapatalk . (*ﾟ▽ﾟ)ﾉ
Click to expand...
Click to collapse
You can but, I won't recommend it because it would just stress out the processor and gpu of that low-end tablet, just leave that be.
Better use gl tools
While everyone gets larger icons,i am getting small icons,small screen,and all the app including resolution changer itself says the current settings is 1080x1920 with 320dpi.
Where am i doing it wrong?
I am on cm12 latest nightly.
same problem as Jongla here, running the same CM 12 nightlies. I guess the problem is that resolution changer doesnt change anything after you apply, current settings are kept as FHD res. Maybe try a different app to do it.
QQboss said:
same problem as Jongla here, running the same CM 12 nightlies. I guess the problem is that resolution changer doesnt change anything after you apply, current settings are kept as FHD res. Maybe try a different app to do it.
Click to expand...
Click to collapse
Try this method.Its easier and works just fine.
http://nexus5.wonderhowto.com/how-t...xus-6-by-lowering-display-resolution-0159881/
thanks buddy, this one works like a charm
cool trick..
It's become blurry, not clear like before
Guys, if you're using a CM rom, just install Xposed and install the App Setting module. Then, you just choose the app, turn on the custom settings, choose the resolution and dpi you want, and the app will run with those defenitions without having to mess with the entire UI on the device...
STEP 1 : install resolution changer pro on any h2os rom from play store (kinmaricans i preffer).
STEP 2 : First do not enable it just put height = 1440 and width = 2560 and then density to 538.
STEP 3 : ENABLE IT. ENJOY
Can't it be in oxygen or any other cm based custom rom
You can't change your phone's screen resolution ahahaha that depends on the hardware. That app is just changing your DPI to change the size of UI elements.
If you could change your phone screen resolution with a simple app, why would any OEM make phones with 4k screens?
The OP2 was, is, and will always remain 1920x1080. You can always change the DPI to get smaller icons or whatever (I prefer 380, stock is 480). More the DPI, bigger your UI elements.
jash2909 said:
STEP 1 : install resolution changer pro on any h2os rom from play store (kinmaricans i preffer).
STEP 2 : First do not enable it just put height = 1440 and width = 2560 and then density to 538.
STEP 3 : ENABLE IT. ENJOY
Click to expand...
Click to collapse
That is just absolute nonsense, sorry to say that. You just make the device believe to have a 2k display, which means the GPU will have to push even more "virtual" pixels, while everything is just "downscaled". You won't get any benefits from that, in contrary you will just introduce more cluster****, by letting it run on a virtual resolution instead of it's native.
There's a reason why people with 2K phones set the virtual resolution down to 1080p, so that the GPU doesn't have to work as hard.
How this differ from changing dpi, it comes to my mind that oos doesn't like changing dp
Sent from my ONE A2005 using Tapatalk
OP, you may want to alter your thread title in the advanced edit menu to something more accurate. You will see what I mean if you read the comments here.
And members, it's fine to try to educate someone or correct them, but do it respectfully. Or don't post otherwise.
Thanks,
Darth
Forum Moderator