Same question?
Just means all the samsung crap stripped away giving you more free memory
Sent from my GT-I9300 using xda premium
To be honest, this is not tablet mode at all, it has nothing to do with silly build.prop hacks. This is the first and only Android rom to feature true Hybrid mode. This rom lets you scale and project every app, every widget, even systemcomponents individually. Remember, android is modular, everything is an app: Lockscreen, navigationbar, dialogs, popups, keyboards, widgets, and your regular apps of course. Apps have the capability to switch into various designs or layouts according to the device they run on. This can result in a complete new experience as many apps will transform to the better.
Now for every element that you like chose a mode (PhoneUI, Phablet/Nexus-7UI, TabletUI) and/or a size. You are 100% independent of the system DPI which runs nicely in whatever value it has been assigned to. You do not need to boot your phone into a certain DPI. Neither will most of the changes you apply require a reboot. You will not suffer from the myriads of troubles which normally haunt you under build.prop tablet mode. Your market, phone, etc. will all work, apps won't shrink on you unless you shrink them yourself. This project will entirely transform your device, but retain the aesthetics and the feel of your phone.
Click to expand...
Click to collapse
Source: PARANOIDANDROID
yknow, something like that )
Hybrid Rom: Combinations of stuff. CM 10 cherry picks + AOSP stuff, etc.
I typed this by hand.
Related
I'd like to propose a bounty for this project to encourage our talented devs to come up with our own solution to running tablet or phone apps on our Notes without being slave to Google's DPI related red tape.
I have attached examples of some of the great tablet UI's that can be viewed comfortably on the Note so you can see the awesome advantages...
Gmail, YouTube, Settings, BeyondPod, Photoshop Touch, Sketch Pro, File Manager HD
The Goal: Use both Tablet and Phone apps without changing the default system DPI
The bounty is for a tool that will...
Provide spoofed DPI settings at a 'per app' level, meaning the user can assign a specific DPI to be used by each App they have installed.
All Apps start out with 'Default' system DPI setting.
Tool can be baked into any ROM.
Does NOT require the user to run their phone at a custom system DPI.
Can change the default system DPI if a user should wish to do so.
I'll keep a list of pledges here in this post.
PLEDGES:
GRIFFINDODD - $25 (US)
griffindodd said:
I'd like to propose a bounty for this project to encourage our talented devs to come up with our own solution to running tablet or phone apps on our Notes without being slave to Google's DPI related red tape.
I have attached examples of some of the great tablet UI's that can be viewed comfortably on the Note so you can see the awesome advantages...
Gmail, YouTube, Settings, BeyondPod, Photoshop Touch, Sketch Pro, File Manager HD
The Goal: Use both Tablet and Phone apps without changing the default system DPI
The bounty is for a tool that will...
Provide spoofed DPI settings at a 'per app' level, meaning the user can assign a specific DPI to be used by each App they have installed.
All Apps start out with 'Default' system DPI setting.
Tool can be baked into any ROM.
Does NOT require the user to run their phone at a custom system DPI.
Can change the default system DPI if a user should wish to do so.
I'll keep a list of pledges here in this post.
PLEDGES:
GRIFFINDODD - $25 (US)
Click to expand...
Click to collapse
I wast this for my galaxy s2
this would be awesome!
Im good for $10 bucks. I wish I had more.
Sent from my SAMSUNG-SGH-I717 using xda premium
This is an old thread, see DAGr8's Hybrid ROM, it's almost perfect for what we wanted here.
Paranoid android is great because it allows you to choose the UI you'd like to sue for each app.
Would it be possible to perform a similar action with an app?
For instance, I'm assuming that apps read the dpi information from the build.prop file when they launch and select the correct ui accordingly?
This might be a poor assumption but this is my limited understanding of it.
So with this assumed, would it be possible to intercept every time an app is launched and set the dpi to whatever setting that app is individually set to, allow the app to launch, then return the dpi to whatever it was?
jcspecs said:
Paranoid android is great because it allows you to choose the UI you'd like to sue for each app.
Would it be possible to perform a similar action with an app?
For instance, I'm assuming that apps read the dpi information from the build.prop file when they launch and select the correct ui accordingly?
This might be a poor assumption but this is my limited understanding of it.
So with this assumed, would it be possible to intercept every time an app is launched and set the dpi to whatever setting that app is individually set to, allow the app to launch, then return the dpi to whatever it was?
Click to expand...
Click to collapse
Bump
jcspecs said:
Would it be possible to perform a similar action with an app?
For instance, I'm assuming that apps read the dpi information from the build.prop file when they launch and select the correct ui accordingly?
This might be a poor assumption but this is my limited understanding of it.
So with this assumed, would it be possible to intercept every time an app is launched and set the dpi to whatever setting that app is individually set to, allow the app to launch, then return the dpi to whatever it was?
Click to expand...
Click to collapse
Apps generally do one or both of two things:
- Define multiple XML layouts and resources and let the OS code select the most appropriate for the device being used
- Programatically define pixel sizes of things drawn to screen, based on the density of the screen (which is available from the API, it's not a question of accessing build.prop as such)
PicomatStudios said:
Apps generally do one or both of two things:
- Define multiple XML layouts and resources and let the OS code select the most appropriate for the device being used
- Programatically define pixel sizes of things drawn to screen, based on the density of the screen (which is available from the API, it's not a question of accessing build.prop as such)
Click to expand...
Click to collapse
Right. So a ROM such as paranoid android does what? Individually alters each app you change settings for to force it to conform to that UI?
Those of us who have had our TrueSmart have learned that while this thing is crazy cool, there are a few quirks that need to be worked out.
For example, the YouTube app's Full Screen. The TrueSmart has a square, not rectangle wide screen, so the Full Screen wouldn't be quite full.
With the Xposed Framework Installed, you can install a Mod called "App Settings" and find the YouTube app, then you can make DPI (resolution) changes and click "Force Orientation > Portrait Mode". Now when using YouTube, expanding to full screen will allow for a more 'dedicated viewing experience'.
There are some apps (found in the Play Store) that you can't access without accepting the ToS (Terms of Service), and the "accept" and "decline" buttons are below the screen. In this case, you'd need to change the DPI, and possibly more settings. I even also had the same SuperSU issues that quite a lot of us had: http://forum.xda-developers.com/showthread.php?t=2656146 There are quite a few ways to fix the spillage.
Also, simply because I feel like saying something, why don't we have subsections for General, Q&A, Accessories, Development and such? meh :/
deedscreen said:
Those of us who have had our TrueSmart have learned that while this thing is crazy cool, there are a few quirks that need to be worked out.
For example, the YouTube app's Full Screen. The TrueSmart has a square, not rectangle wide screen, so the Full Screen wouldn't be quite full.
With the Xposed Framework Installed, you can install a Mod called "App Settings" and find the YouTube app, then you can make DPI (resolution) changes and click "Force Orientation > Portrait Mode". Now when using YouTube, expanding to full screen will allow for a more 'dedicated viewing experience'.
There are some apps (found in the Play Store) that you can't access without accepting the ToS (Terms of Service), and the "accept" and "decline" buttons are below the screen. In this case, you'd need to change the DPI, and possibly more settings. I even also had the same SuperSU issues that quite a lot of us had: http://forum.xda-developers.com/showthread.php?t=2656146 There are quite a few ways to fix the spillage.
Also, simply because I feel like saying something, why don't we have subsections for General, Q&A, Accessories, Development and such? meh :/
Click to expand...
Click to collapse
Thanks. If you want to make you post a [Guide] I'll add it to the Everything sticky.
Except for the rotation issue, qemu.sf.lcd_density=115 added to the build.prop also resolves the "fit" issue on almost every app as well and is the reason why I'm adding it back to the patch for all x201s.
Lokifish Marz said:
Thanks. If you want to make your post a [Guide] I'll add it to the Everything sticky...... (Cont.)
Click to expand...
Click to collapse
I'll consider turning it into a guide. Friendly tip: It may have been a mistake but please try not to quote the entire long post, it takes up extra unneeded room, a @deedscreen mention in reply or partial quote works just fine. It can make things a bit hectic. (Ex: you have a long development thread and someone quotes the long post to say "this is cool".) Nevertheless, the guide is a good idea - now if we can only figure out how to get the status bar to always show when using -say- Nova launcher. My attempts haven't gone the greatest so far. :cyclops:
Hi Loki
Don't you just love when guys learns developers how to quote OP...
BTW - request is already sent to moderators for sections inside of Omate section.
Sent from my C6903 using Tapatalk
It was before my first cup of coffee so blame it on the lack of caffeine.
The solution I've been using is Swipe Statusbar. It's not ideal but does free up the space a consistent status bar would use. A permanent status bar fix is going to most likely require the framework and related files be gone through and redone as they use a show intent versus a hide intent from what I've been told.
I do use my ppi edit and Force Orientation on my daily device. Hopefully I can make the need for the orientation lock unnecessary and have it active at all times for all apps. That would cover the majority of users and apps used and can't remember the last time I wanted an app to rotate on the x201.
I know what you mean, with that app I've tried and it covers some areas of apps and drives me insane, I can't quite win...
Im running Themer on my Moto X (stock) and sometimes it takes several attempts for a touch to register to open a given module. (Favorites, camers, etc.)
Sometimes it works ok, but sometimes the screen seems unresponsive to touch. I had it show touches in dev options but even 'direct hits' don't register and open whatever the icon is supposed to open. This seems to occur across themes. I do have widgets locked.
Am I missing something here or is this normal?
flyingj said:
Im running Themer on my Moto X (stock) and sometimes it takes several attempts for a touch to register to open a given module. (Favorites, camers, etc.)
Sometimes it works ok, but sometimes the screen seems unresponsive to touch. I had it show touches in dev options but even 'direct hits' don't register and open whatever the icon is supposed to open. This seems to occur across themes. I do have widgets locked.
Am I missing something here or is this normal?
Click to expand...
Click to collapse
Hi,
Try uninstalling Themer - delete the /sdcard/MyColorScreen/ folder (removing the Exported folder within it if you saved any themes) - then reinstall Themer.
Let us know if that helps!
I have the same problem, both before and after doing what is suggested above. The pretty themes with really small or really close selections are the worst at it.
Thank you for responding, I'll give that a try. Though it is possible that with some themes with small target zones may contribute to the issue.
Thank you!
ThemerSupport said:
Hi,
Try uninstalling Themer - delete the /sdcard/MyColorScreen/ folder (removing the Exported folder within it if you saved any themes) - then reinstall Themer.
Let us know if that helps!
Click to expand...
Click to collapse
RED ZMAN said:
I have the same problem, both before and after doing what is suggested above. The pretty themes with really small or really close selections are the worst at it.
Click to expand...
Click to collapse
Could you give us an example? We could try increasing these areas for selection.
Shades of green and coordinate are two perfect examples. I'm using a rooted Nexus 5 running droid Kang. Beautiful themes, but even with the screen showing presses I can be pressing right on something and it doesn't pick it up.
RED ZMAN said:
Shades of green and coordinate are two perfect examples. I'm using a rooted Nexus 5 running droid Kang. Beautiful themes, but even with the screen showing presses I can be pressing right on something and it doesn't pick it up.
Click to expand...
Click to collapse
Thanks for the heads up, will speak to the developers and see what they can do.
I experience the same problem on my Note II running PA.
Is there an official place to request features
Same thing, doesn't seem dependent on theme (happens across all themes I've tried), T-Mo Galaxy Note 3 running stock 4.4.2 (unrooted)
It's hit & miss, sometimes everything works, sometimes it takes 2 or 3 presses before it registers. Seems to be memory related because it generally only happens when returning to the home screen after leaving another app that uses a significant portion of RAM, though I do not have actual evidence of this.
ingenious247 said:
Same thing, doesn't seem dependent on theme (happens across all themes I've tried), T-Mo Galaxy Note 3 running stock 4.4.2 (unrooted)
It's hit & miss, sometimes everything works, sometimes it takes 2 or 3 presses before it registers. Seems to be memory related because it generally only happens when returning to the home screen after leaving another app that uses a significant portion of RAM, though I do not have actual evidence of this.
Click to expand...
Click to collapse
The developers are still looking into reducing RAM usage, hopefully this will be resolved soon.
ThemerSupport said:
The developers are still looking into reducing RAM usage, hopefully this will be resolved soon.
Click to expand...
Click to collapse
I believe this will solve the non-registering touches.
I don't think it's grid/sensitivity related, I really think it's the RAM issue.
ingenious247 said:
I believe this will solve the non-registering touches.
I don't think it's grid/sensitivity related, I really think it's the RAM issue.
Click to expand...
Click to collapse
On my device it appears to be related to adding the dock feature or persistent search box. Adding either appears to cause the problem and then removing them causes the problem to be alleviated. I ran up my RAM usage to near 90% without any problems (without the dock or search).
Another bug I would love to see fixed is Themer retaining the dock and search features when applying a new theme. It is annoying having to reconfigure the options and add everything back to the dock each time.
Edit:
I'm going to add my feature requests/changes here since I can't find a specific thread for it.
App drawer:
Horizontal or vertical scroll options perhaps with a paginated option for both
Allow Themer icon to be swapped for the play store icon
Allow for the removal of the tabs at the top entirely
Launcher screens:
Allow custom smart categories and/or folders to be used by widgets (maybe the news icon could open a folder or category I've created to show all my news apps instead of launching the themer news app only)
Allow reordering of home screens (perhaps even allow adding multiple themes at one time next to each other)
Retain custom added home screen folders and icons when changing themes
Give end user access to icons used by the theme so when customizing an icon I can use one built into my theme (I like the dialer in my dock but I would love to use my theme's dialer icon instead of the default android one)
As mentioned above:
Retain dock and persistent search options between themes but also allow themes to better resize when those options are selected (some themes get cut off slightly or the aspect ratio gets out of whack)
Hopefully that doesn't sound too demanding. I'm just trying to help make an awesome concept better
Wetzel402 said:
On my device it appears to be related to adding the dock feature or persistent search box. Adding either appears to cause the problem and then removing them causes the problem to be alleviated. I ran up my RAM usage to near 90% without any problems (without the dock or search).
Another bug I would love to see fixed is Themer retaining the dock and search features when applying a new theme. It is annoying having to reconfigure the options and add everything back to the dock each time.
Click to expand...
Click to collapse
Agreed (Bold), I would like the notification bar auto-hide to stay selected when I change themes. However, because each theme requires a different configuration to work/look properly, this might not be ideal.
For me, the problem only happens when the launcher is trying to "catch up". This indicates a memory issue IMO. Anytime the launcher is fully loaded and I'm on the main home screen(s), I do not experience any issues registering touch.
Perhaps that is the problem then. I don't use Themer as a daily driver just yet because there are a few thing I need sorted out first. The touch issue in this thread being one of them. Folder/custom smart categories, mentioned in my edit above, are another.
This also happens when I use the gesture system(Swiping up/down). Personally this is the least fluid launcher I have ever used, sad seeing that its my favorite.
I know themer is still beta but this problem has been happening for a long time now.
On the gestures, I agree there is definitely an issue.
When attempting to do the "two fingers down" or "two fingers up", it generally triggers the "pinch in" gesture. This is the only launcher I have experienced this problem with. It's not make-or-break as I know it's beta, but accurate gestures are very important to me with the way I use my phone.
I expect these will get fine tuned before they transition out of beta
I'll have to rescind my former statement(s). I did more testing
There are definitely issues with touch not registering on some themes. As I tried more and more themes, I started to see it more and more. And it's bad. 2-3 times minimum to get the touches to register, especially on the Tron looking theme (I forget it's name). There are many more themes with this issue as well, and it appears over time the more cache/data stored in the MyColorScreen folder, the less responsive the launcher becomes. It got to the point of being unusable until I uninstalled, deleted the folder and reinstalled.
This, coupled with the intense RAM usage and pretty aggressive battery drain (10-12% daily, minimum) and I have to hold off on using Themer for now.
I'm not against sacrificing one or two minor things, but to sacrifice device response + RAM + Battery is too much just to use Themer. I will wait and watch and as improvements are made I will reinstall and retry.
ingenious247 said:
I'll have to rescind my former statement(s). I did more testing
There are definitely issues with touch not registering on some themes. As I tried more and more themes, I started to see it more and more. And it's bad. 2-3 times minimum to get the touches to register, especially on the Tron looking theme (I forget it's name). There are many more themes with this issue as well, and it appears over time the more cache/data stored in the MyColorScreen folder, the less responsive the launcher becomes. It got to the point of being unusable until I uninstalled, deleted the folder and reinstalled.
This, coupled with the intense RAM usage and pretty aggressive battery drain (10-12% daily, minimum) and I have to hold off on using Themer for now.
I'm not against sacrificing one or two minor things, but to sacrifice device response + RAM + Battery is too much just to use Themer. I will wait and watch and as improvements are made I will reinstall and retry.
Click to expand...
Click to collapse
Hi,
Could you possibly provide us with some more details? What device/Android version/ROM are you using?
Also, which themes are doing this?
T-Mobile Galaxy Note 3, running stock 4.4.2, unrooted. For Theme specifics, I will have to reinstall and test for a few days. I will get back to you.
I'm trying to make a custom ROM (for now, only for x86, because I don't want to flash anything on my actual phone) and I want to modify the default UI throughout the entire system. This includes colors, outlines, corners on buttons, etc. Is there something in the AOSP source that would allow me to make these changes? I'm hoping I don't have to open the source for each individual application to change the look.
MasterPixelDestroyer said:
I'm trying to make a custom ROM (for now, only for x86, because I don't want to flash anything on my actual phone) and I want to modify the default UI throughout the entire system. This includes colors, outlines, corners on buttons, etc. Is there something in the AOSP source that would allow me to make these changes? I'm hoping I don't have to open the source for each individual application to change the look.
Click to expand...
Click to collapse
Sorry to say that but you'll have to mod each and everyone of your apps to have those changes (outlined, colors).
I've heard of a substratum theme that might fit your expectations, but I you want to do it yourself (which is more fun) you'll have to modify each and every apps. When you'll mod systemUI your modification will go "system wide" (quick settings and stuff) but the phone app won't be changed.
Have a good day
@MasterPixelDestroyer
Several XPosed Framework modules exist that do the job.
Study their source code to get an idea how to tweak system UI ( read: home screen ) is done.