Thought I'd share a 'fix' for your TouchPads if you don't want to be tied to 120 or 160 dpi (which btw look good but still..).
Now we all now the edit build.prop or dpi change apps but this one is pretty neat.
It allows you to manually set your desired DPI (f.e. 132 as the TP should be) but also comes with a solution for 'breaking' your market. The app will Fix your Market compatibility issues by modding your Market.apk into thinking you are using the market at f.e. 120 DPI. You can do this for any DPI change
Guide:
1) Install LCD Density Modder Pro here (official Android Market link)
2) Open app (only for root users but if you are running Android on your TP...)
3) set your DPI
4) Save as System DPI (perma + reboot) or
4a) Temp Apply (fast reboot and is merely there to see if your chosen DPI looks good)
5) after reboot hit "Fix Market compatibility issues"
6) Download modded Market.apk for the PDI you want the market to think you have (either 120 or 160 DPI, depends which file you installed from CM9)
7) Install Mod
8) Asks you to reboot so that the 'new' Market.apk works
9) voilá!
(note: instructions will also appear when opening app)
I hope this isn't considered something 'not done' on this forum as I am merely linking to an official apk on the market and points TP users in the right direction.
Good luck!
ps: credits go to anthonyjcasagrande aka theb1rdm4n for developing
great write up! will be sure to do this when i actually get my touchpad lol
BuddyJoe83 said:
1) Install LCD Density Modder Pro here (official Android Market link)
Click to expand...
Click to collapse
That's gotta be the most expensive app on the market, 3 dollars to change 3 digits? Craaaaaaaaaaaaazy...
If you look at it that way, yes... but handy for peeps, ofcourse can just edit the build.prop but it allows you to receive fixed market aswell for any DPI.
Anyways only posted so peeps know of it's availibility
Sent from my Galaxy Nexus using xda premium
DPI changer by innodroid is free with the same result, also on Market.
danknee said:
DPI changer by innodroid is free with the same result, also on Market.
Click to expand...
Click to collapse
That also changes your DPI for you yes, the app won't 'fix' the market issues for you though.
There is a thread out there that lets you install a modded Market.apk, but the app I describe does it both, but you are right.. there are a lot of ways to do it. This one does it in both.
Not saying this app is the holy grail but a handy tool.
I know there is a thread over on rootzwiki with instructions on how to get the market to work after changing the DPI.
Three bucks to change the DPI is a really nutz.
BuddyJoe83 said:
Thought I'd share a 'fix' for your TouchPads if you don't want to be tied to 120 or 160 dpi (which btw look good but still..).
Now we all now the edit build.prop or dpi change apps but this one is pretty neat.
It allows you to manually set your desired DPI (f.e. 132 as the TP should be) but also comes with a solution for 'breaking' your market. The app will Fix your Market compatibility issues by modding your Market.apk into thinking you are using the market at f.e. 120 DPI. You can do this for any DPI change
Guide:
1) Install LCD Density Modder Pro here (official Android Market link)
2) Open app (only for root users but if you are running Android on your TP...)
3) set your DPI
4) Save as System DPI (perma + reboot) or
4a) Temp Apply (fast reboot and is merely there to see if your chosen DPI looks good)
5) after reboot hit "Fix Market compatibility issues"
6) Download modded Market.apk for the PDI you want the market to think you have (either 120 or 160 DPI, depends which file you installed from CM9)
7) Install Mod
8) Asks you to reboot so that the 'new' Market.apk works
9) voilá!
(note: instructions will also appear when opening app)
I hope this isn't considered something 'not done' on this forum as I am merely linking to an official apk on the market and points TP users in the right direction.
Good luck!
Click to expand...
Click to collapse
I thank it's a great apk. easy
Hey guys, for ages I've been hearing people talk about changing LCD density etc and decided to give it a try using this app (free version).
Anyway, I changed the dpi on my S2 from 240 to 160 and although it looks much better in most instances, the actual homescreen/s are much smaller with only about 60% being used up.
Is this normal? I was under the impression that only the icon sizes would change but not the entire homescreen.
The dock is still at the bottom however but a large part above that is empty.
Sent from my GT-I9100T
Hey there,
just stopping by to let you know this thread has been featured on the XDA Portal
sxi200 said:
Hey guys, for ages I've been hearing people talk about changing LCD density etc and decided to give it a try using this app (free version).
Anyway, I changed the dpi on my S2 from 240 to 160 and although it looks much better in most instances, the actual homescreen/s are much smaller with only about 60% being used up.
Is this normal? I was under the impression that only the icon sizes would change but not the entire homescreen.
The dock is still at the bottom however but a large part above that is empty.
Sent from my GT-I9100T
Click to expand...
Click to collapse
is the space entirely not usable?
After you have rebooted to make the DPI changes take effect, you often have to redrag the apps (and widgets) you use from your apps screen to your homescreen(s).
When changing the build.prop I always 'clear' my homescreens to be sure and then replace what I want.
Changing your DPI however shouldn't make a big proportion of your screen not usable.
Also I can recommend this thread for 'mobile' issues since I only use this app on my Touchpad. It's the b1rdm4n's original thread about his app
PoorCollegeGuy said:
Hey there,
just stopping by to let you know this thread has been featured on the XDA Portal
Click to expand...
Click to collapse
Hey, cheers for letting me know and submitting it
Hadn't seen it myself but hope TP (and more Androidusers) will use it.
My TouchPad is currently running at 160dpi (having previously manually edited it to 120 then manually edited it back to 160)
When I run the app and select a different DPI I hit apply, it reboots and the TP is still at 160 dpi. The app appears not to work at all.
Anyone have any idea why?
stuart_f said:
My TouchPad is currently running at 160dpi (having previously manually edited it to 120 then manually edited it back to 160)
When I run the app and select a different DPI I hit apply, it reboots and the TP is still at 160 dpi. The app appears not to work at all.
Anyone have any idea why?
Click to expand...
Click to collapse
If you manually edited your build prop, you might want to try to flash Dalingrins 120 or 160 DPI.zip (it's in his original Rootzwiki thread) to original (build.prop) settings.
After that, start the app again, change the DPI and hit "Save as System DPI (Reboot)". I think you already did that but I didn't manually edit the build.prop before using this app so it might have something to do with there, I am not sure though since it was a direct hit for me when using this app.
Nice idea.
I flashed the 120dpi package, rebooted and the TouchPad had changed to 120dpi as expected. I then ran LCD Density Modder and it correctly reported 120dpi.
I changed it to 132dpi in the app and hit "Save as System DPI", it asked for, and got root permission, rebooted the TouchPad and once again I am back at 120dpi.
The app just doesn't do anything for me
stuart_f said:
Nice idea.
I flashed the 120dpi package, rebooted and the TouchPad had changed to 120dpi as expected. I then ran LCD Density Modder and it correctly reported 120dpi.
I changed it to 132dpi in the app and hit "Save as System DPI", it asked for, and got root permission, rebooted the TouchPad and once again I am back at 120dpi.
The app just doesn't do anything for me
Click to expand...
Click to collapse
Sorry to hear.
Hmm last suggestion: manually set the DPI to 132 (editing build.prop yourself), reboot. At this point ignoring the app.
If the DPI is succesfully set as 132 open the app, click fix market compatible function, let it download the modded market.apk (let it think market is set at 120 DPI) and reboot.
I know you are not fully using the app as it's supposed too then but just trying to help you
Sent from my Galaxy Nexus using xda premium
Yes, a bit overpriced.... as in way overpriced....
Couple of questions:
1) Does the app disable the Market Updater so you won't get a newer market next time Google pushes one?
2) Has the app fixed the problem with the original patch from rootzwiki, in that after some time, apps _still_ revert to not compatible, and you have to clear market data. Or is it just downloading that apk that anyone can go get for free?
BuddyJoe83 said:
is the space entirely not usable?
After you have rebooted to make the DPI changes take effect, you often have to redrag the apps (and widgets) you use from your apps screen to your homescreen(s).
When changing the build.prop I always 'clear' my homescreens to be sure and then replace what I want.
Changing your DPI however shouldn't make a big proportion of your screen not usable.
Also I can recommend this thread for 'mobile' issues since I only use this app on my Touchpad. It's the b1rdm4n's original thread about his app
Click to expand...
Click to collapse
Yeah, the empty space on the homescreen/s is not usable. I tried removing then replacing widgets but still the same thing. Might try again later with a fresh rom flash.
Sent from my GT-I9100T
Need to get this on my twin brother's TouchPad.
sxi200 said:
Yeah, the empty space on the homescreen/s is not usable. I tried removing then replacing widgets but still the same thing. Might try again later with a fresh rom flash.
Sent from my GT-I9100T
Click to expand...
Click to collapse
Yup, this happens to me in portrait mode as well. very annoying!
Photo for proof.
{
"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"
}
That's as far down as they'll go. In landscape mode its not like this
Related
This question is directed to anyone who knows the inner workings of the vending.apk and the android market itself. Through another post about density settings, it seems pretty apparent that, while having density set at 161 allows all the apps in the market to show up, there are still plenty of apps that won't actually RUN unless you are set at 160/159. So it turns into a Catch 22 situation. I know I have used device spoofing via an altered build.prop (or an apk that does the same) for getting apps to appear that are 'proprietary' to other, specific devices, but I'm wondering if it MIGHT be possible to spoof the market into reading our Nooks at being 161 devices, while we are actually at 160 while within our rom (I'm on CM7). This has probably been proposed somewhere else, but I couldn't locate a thread...Anyone have any input about this possibility? If something like this is NOT possible, please let the users know also, if you have a minute. Thanks for looking...(Idea..could we get a secondary "market161" .apk created that we could use indepedently of the one in the latest Gapps to achieve the desired effect?)
You could write a widget that toggles ro.sf.lcd.density in build.prop between two values, and then use Tasker to toggle the widget when you open the Market (and flip it back when you leave it). But I'm not sure if the Market checks the value in build.prop or what the device is currently using, so it might require a reboot instead.
My Density is set at 200 and everything works just fine (including both Market and Maps).
Mine is set at 240 (need new glasses?) and everything seems to be ok
Trust me...there are enough that don't run at 200....otherwise I wouldn't have bothered posting. 160 seems to be magic for compatibility/scaling, and 160+X gets best market access.
Sent from my PC36100
ganovim said:
Mine is set at 240 (need new glasses?) and everything seems to be ok
Click to expand...
Click to collapse
I actually would assume the 240 would work.. since it's 1 of the 3 native android app densities that devs mass market through compatibility mode to ensure mucho marketshare (120,160,240)..but the icons and such at 240 are just too huge ...can't do it...reminds me of those physical phones with humongous buttons that people have in their house. When I see someone using a new tablet, like take the Galaxy, I can tell pretty much immediately whether they're running stock from the look of their homescreen...Huge, ghastly, labeled icons +(bloatware)=someone not using their device to the full potential, and that makes my inner nerd sad. Nope, even if I go blind I won't do 240....if only because "it just LOOKS stock. The same reason SPB mobile lasted about a week on my nook.
Sent from my PC36100
Sent from my PC36100
FrasierCrane said:
You could write a widget that toggles ro.sf.lcd.density in build.prop between two values, and then use Tasker to toggle the widget when you open the Market (and flip it back when you leave it). But I'm not sure if the Market checks the value in build.prop or what the device is currently using, so it might require a reboot instead.
Click to expand...
Click to collapse
Thanks...this is exactly what kind of info I needed...new project...sigh..will give it a shot after work tonight...Thanks.
Sent from my PC36100
Sent from my PC36100
FrasierCrane said:
You could write a widget that toggles ro.sf.lcd.density in build.prop between two values, and then use Tasker to toggle the widget when you open the Market (and flip it back when you leave it). But I'm not sure if the Market checks the value in build.prop or what the device is currently using, so it might require a reboot instead.
Click to expand...
Click to collapse
BTW..Is Tasker's U.I. still absolutely archaic? I love all the possibilities from the app.. but it's such a nightmare to use. Is there any other 1 out there that might be easier on the brain?
Sent from my PC36100
mazook98 said:
I actually would assume the 240 would work.. since it's 1 of the 3 native android app densities that devs mass market through compatibility mode to ensure mucho marketshare (120,160,240)..but the icons and such at 240 are just too huge ...can't do it...reminds me of those physical phones with humongous buttons that people have in their house. When I see someone using a new tablet, like take the Galaxy, I can tell pretty much immediately whether they're running stock from the look of their homescreen...Huge, ghastly, labeled icons +(bloatware)=someone not using their device to the full potential, and that makes my inner nerd sad. Nope, even if I go blind I won't do 240....if only because "it just LOOKS stock. The same reason SPB mobile lasted about a week on my nook.
Sent from my PC36100
Click to expand...
Click to collapse
You're really making me want to track you down so I can change your density settings just to mess with you
Sent from my SAMSUNG-SGH-I897 using Tapatalk
wretchedlocket said:
You're really making me want to track you down so I can change your density settings just to mess with you
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
It would be SO on....
Sent from my Nook Color (zoom2) using Tapatalk
mazook98 said:
BTW..Is Tasker's U.I. still absolutely archaic? I love all the possibilities from the app.. but it's such a nightmare to use. Is there any other 1 out there that might be easier on the brain?
Sent from my PC36100
Click to expand...
Click to collapse
It's a pain sometimes, since everything is buried under submenus. I don't think there's anything else comparable, though.
The reason I have the density set at 161 isn't because apps are filtered. It was due to a bug in the Market apk and the Maps apk. Maps 5.1.x would crash on startup on tablets with LCD density 160. Google has fixed this with the most recent version. Unfortunately, Google has not fixed the Market yet. Tablets+160 causes the "my apps" list to not populate.
dalingrin said:
The reason I have the density set at 161 isn't because apps are filtered. It was due to a bug in the Market apk and the Maps apk. Maps 5.1.x would crash on startup on tablets with LCD density 160. Google has fixed this with the most recent version. Unfortunately, Google has not fixed the Market yet. Tablets+160 causes the "my apps" list to not populate.
Click to expand...
Click to collapse
Thanks so much for saving me from making this a bigger issue than it is...I don't need " my apps " to populate since I'm tethered to my Evo about 95% of the time, where they naturally all populate ...I'll just bump it down to 160 permanently, and if ever it becomes something I absolutely need, Ill just bump it back....Thanks for all your amazing work..Donation on the way when I get home from work.
Sent from my PC36100
Maybe im the only one, but whats the visual difference between 160 and 161? why is 160 better?
john10101 said:
Maybe im the only one, but whats the visual difference between 160 and 161? why is 160 better?
Click to expand...
Click to collapse
There are just some apps that wont run / scale correctly unless its at 160... they will just hang and load 4 ever or force close unless they are set at 1 of the 3 native densities for android application development... at least that's what I can glean.. no difference though in appearance, unless you're a cyborg.
Sent from my PC36100
oh this is why my app list wouldnt populate. it doesnt bother me most of the time. everyone seems to have their dpi set for so low. i have mine at 132.33 if i remember it right. can't be any bigger than 140 for sure.
can anyone give me an example of an app that crashes or does not show up on the market due to density conflicts?
the reason i ask is because i run hyperdroid on my HD2 at the default 167. this setting is just plain awesome compared to the 240. i have never had an issue with apps not showing up or crashes / anything due to resolution at this size.
or is this one of the default dev res' and i'm just talking nonsense.
let me know so i can test on my hd2.
pxldtz said:
can anyone give me an example of an app that crashes or does not show up on the market due to density conflicts?
the reason i ask is because i run hyperdroid on my HD2 at the default 167. this setting is just plain awesome compared to the 240. i have never had an issue with apps not showing up or crashes / anything due to resolution at this size.
or is this one of the default dev res' and i'm just talking nonsense.
let me know so i can test on my hd2.
Click to expand...
Click to collapse
Here's one...Try "Fruit Slice" at 161....then try it at others if you want...then run it at 160.
Sent from my PC36100
With the talk of Samsung releasing the SGSII line with just about the lowest resolution on the market, has anyone been using an LCD Density changer (or just changed the density) to effectively give a better resolution?
How are the results? Does it cause any issues in apps or what not?
I have unfortunately touchwiz can't handle the change, i mean it still works but it doesn't adapt to the new size, neither does the dialer. tried turning off compatibility mode in spare parts, but that did nothing.
Here is a screenie from when I was running CM7.1 nightly 9 with ADW EX launcher set to 8x8 homescreen with DPI set to 200
The dialer was compressed, but nothing that some editing of the numerical PNG files in contacts.apk couldn't fix. It worked fine, no force closes anywhere.
Super simple to do, just use Root Explorer to edit /system/build.prop and change the line:
Code:
ro.sf.lcd_density=200
...save + exit and reboot.
The smaller the number, the more compressed the pixels. My Dell Streak 5 default is dpi 160, so using a 4x4 touchwiz homescreen at 240 dpi is taking some getting use to.
Some market apps will refuse to install at anything other than stock dpi. Not a big deal, revert changes + reboot + install + mod dpi again + reboot + done.
For the record, I'm using UnNamed 1.1 this week at stock DPI (and amazed that I kinda like TW4)
Okay im looking at that line so how do i edit it? Forgive me im new to this stuff /
SGS2 rooted and Overclocked to 1.5ghz stock rom p
No prob. Using Root Explorer, navigate to /system/ and make sure to hit the button in the top right "Mount R/W"
Long press "build.prop" and select Open in Text Editor
Make the change to the line "ro.sf.lcd_density=240" to whatever you want (200 probably works best)
Hit Menu softkey and choose "Save & Exit"
Root Explorer will automatically save a backup copy of build.prop
Reboot your phone to apply DPI change.
There is also a free root file manager called Super Manager, but I haven't used it.
I came from a dell streak as well so the stock 240 density was WAY too big for me. Mine is set to 200 now and like it much better! But i ditched TW and i'm currently running UnNamed + ADWex.
nickshertzer, i'm currently attempting to edit the Phone.apk so the dialer stretches out. How did you go about doing this? I've got the Phone.apk decompiled, can't it be fixed by editing the dip values in the .xml files?
I found this thread with a script to edit the dialer for the I9000 that i'm attempting to use as a rough guide.
nickshertzer said:
Here is a screenie from when I was running CM7.1 nightly 9 with ADW EX launcher set to 8x8 homescreen with DPI set to 200
The dialer was compressed, but nothing that some editing of the numerical PNG files in contacts.apk couldn't fix. It worked fine, no force closes anywhere.
Super simple to do, just use Root Explorer to edit /system/build.prop and change the line:
Code:
ro.sf.lcd_density=200
...save + exit and reboot.
The smaller the number, the more compressed the pixels. My Dell Streak 5 default is dpi 160, so using a 4x4 touchwiz homescreen at 240 dpi is taking some getting use to.
Some market apps will refuse to install at anything other than stock dpi. Not a big deal, revert changes + reboot + install + mod dpi again + reboot + done.
For the record, I'm using UnNamed 1.1 this week at stock DPI (and amazed that I kinda like TW4)
Click to expand...
Click to collapse
Nick I tried your method several different ways and have been going around an around with this for several weeks on our phone and also Sprint version too and the revert back does not stick or still allow to download/update the apps from the market. Tried restarting, clearing cache and resetting the market data and restarting but it still would persist and not allow the updates and incompatibility. The only success I experience is right after I update to a newer version of ROM or clean install all together (which for obvious reasons) resets the phone and then allows the update actions. It is just very frustrating that the DPI change would hinder "Certain Apps" from updating. Anyone have ideas on a future solution besides Nicks input on the manual fix? I think we have brilliant screens with lots of potential for various display options and I miss using the 200dpi settings, but application updates and use of the market is much more important for daily use.
---------- Post added at 11:27 AM ---------- Previous post was at 11:20 AM ----------
fone_fanatic said:
I came from a dell streak as well so the stock 240 density was WAY too big for me. Mine is set to 200 now and like it much better! But i ditched TW and i'm currently running UnNamed + ADWex.
nickshertzer, i'm currently attempting to edit the Phone.apk so the dialer stretches out. How did you go about doing this? I've got the Phone.apk decompiled, can't it be fixed by editing the dip values in the .xml files?
I found this thread with a script to edit the dialer for the I9000 that i'm attempting to use as a rough guide.
Click to expand...
Click to collapse
I have used the dialer files from this thread you mentioned and it all works fine on this ROM the only down side is once you theme that it changes to the themed dialer and goes with the 240 adjusted dialer. I would hope you could share your input and steps (If not too complex) to allow themers to integrate into their themes for multi dpi users.
No need to edit build.prop, this app does it for you:
http://www.appbrain.com/app/lcd-resolution-(root)/com.wemobs.android.lcdresolution
My biggest issue is the fact that the market sometimes won't let you install stuff at non240 densities.
poofyhairguy said:
No need to edit build.prop, this app does it for you:
http://www.appbrain.com/app/lcd-resolution-(root)/com.wemobs.android.lcdresolution
My biggest issue is the fact that the market sometimes won't let you install stuff at non240 densities.
Click to expand...
Click to collapse
this has been posted as an issue, go here and star it to bring it to the attention of the android devs.
qwertyaas said:
With the talk of Samsung releasing the SGSII line with just about the lowest resolution on the market, has anyone been using an LCD Density changer (or just changed the density) to effectively give a better resolution?
How are the results? Does it cause any issues in apps or what not?
Click to expand...
Click to collapse
Lowest res on the market? 800x480 is the industry standard at the moment. Not the best, but certainly not the lowest.
Sent from my Galaxy S II (i777) using XDA Premium.
I use 180 on a daily basis. In order to get around the dialer issue. I replace contacts.apk in Unnamed 2.21 with the one from Mikey's Serendipity 8.2 works perfectly except for the already in-call dialer pad which i rarely ever use is still small but the regular dialer is now stretched to full screen. It comes down to editing a .xml file or two if you want to attempt yourself.
Hperdroid has touchwiz that works on 160. it is my understanding most market things work with that density
Sent from my GT-I9100 using xda premium
I am running the CM7 lastest nightly and I have my lcd density to 220. It makes everything look not so huge as it normally is on 240. It does not break anything as far as I can tell.
hekoman said:
I am running the CM7 lastest nightly and I have my lcd density to 220. It makes everything look not so huge as it normally is on 240. It does not break anything as far as I can tell.
Click to expand...
Click to collapse
How does the dialer look at 220? I'm running Turkbey, and everything looks great and proportional at 200 and 220 except for the dialer. It becomes offset to the left, so I'm just keeping it at stock 240.
Sent from my Galaxy S II (i777) using XDA Premium.
Man_Cave_Tech said:
How does the dialer look at 220? I'm running Turkbey, and everything looks great and proportional at 200 and 220 except for the dialer. It becomes offset to the left, so I'm just keeping it at stock 240.
Sent from my Galaxy S II (i777) using XDA Premium.
Click to expand...
Click to collapse
I use my phone at 220 without any issues. I have stopped using the stock dialer since I tried DW contacts. It didn't have any problem when I switched from 240 to 220.
People having issues with stock dialer at 220 could try it out.
Sent from my AT&T Samsung Galaxy S II
jazzboyrules said:
I use my phone at 220 without any issues. I have stopped using the stock dialer since I tried DW contacts. It didn't have any problem when I switched from 240 to 220.
People having issues with stock dialer at 220 could try it out.
Sent from my AT&T Samsung Galaxy S II
Click to expand...
Click to collapse
Ok, thanks for the input. I'll give that a try when I get home from work tonight.
Sent from my Galaxy S II (i777) using XDA Premium.
I've been using a LCD Density of 185 for as long as I can remember. It's rare now to see an app that doesn't like a custom lcd density setting. Occasionally I run into an app on the market that doesn't like it, and I get the banner at the top of the screen. Since I edit the build.prop for my density setting I have to keep an app handy just incase I get the market issue. But it's an easy fix- use app to get back 240 density> manage applications> market> clear data. Open market> download desired app! Love 185. Probably wouldn't go any lower personally but... for the most part, most apps will happily still work and fill the screen
What do we won lowering the density?
RatusNatus said:
What do we won lowering the density?
Click to expand...
Click to collapse
User preference. By lowering the density you virtually make the screen bigger. (More can fit on the screen)
sent from my Galaxy SII
Coreym said:
User preference. By lowering the density you virtually make the screen bigger. (More can fit on the screen)
sent from my Galaxy SII
Click to expand...
Click to collapse
But it's not the same using a launcher that gives you more columns and rows?
Just saying
Saludos desde Ecuador
]Lcd density changer, works on our phone, using the Rom below unless lee's released an update from 2.0.0 , and v1 kernel
I have adjusted from default 240, I'm assuming that's dpi, to 220, I ain't tried other sizes, do so at your own risk,
You can find the lcd density changer in the android market for free or for those who cba to look
http://www.google.co.uk/url?sa=t&rc...mYjvBA&usg=AFQjCNEN3t4vBQFSYa4Iu6KPcP4cK_i54g
gav-collins1983 said:
]Lcd density changer, works on our phone, using the Rom below unless lee's released an update from 2.0.0 , and v1 kernel
I have adjusted from default 240, I'm assuming that's dpi, to 220, I ain't tried other sizes, do so at your own risk,
Click to expand...
Click to collapse
Where is it mate?
harpss1ngh said:
Where is it mate?
Click to expand...
Click to collapse
LCD Density in short and easy words, changes the view of the screen, adjusting the screen density higher will make your screen appeared zoomed out more, allowing you to see more, and lowering it should make everything enlarged.
I'm sure he meant "where to download it?"
harpss1ngh said:
Where is it mate?
Click to expand...
Click to collapse
Sorry in the android market
nickiberli said:
I'm sure he meant "where to download it?"
Click to expand...
Click to collapse
just a question,
if you wrote something, there is a picture and a text under your post.
How have you made it?
Cant find any option at profile settings to this too
protomanez said:
LCD Density in short and easy words, changes the view of the screen, adjusting the screen density higher will make your screen appeared zoomed out more, allowing you to see more, and lowering it should make everything enlarged.
Click to expand...
Click to collapse
It's the opposite lowering the number, lowers fthe density, hussy like a pc with dpi
Philstadt said:
just a question,
if you wrote something, there is a picture and a text under your post.
How have you made it?
Cant find any option at profile settings to this too
Click to expand...
Click to collapse
That's in your signature settings mate
gav-collins1983 said:
That's in your signature settings mate
Click to expand...
Click to collapse
so, and thats the option I can't find^^
Philstadt said:
so, and thats the option I can't find^^
Click to expand...
Click to collapse
Geh zu User CP oben in der kontrollleiste, da gibt's dann die Einstellung edit signature. ;-)
Sent from my HTC EVO 3D using XDA App
Philstadt said:
just a question,
if you wrote something, there is a picture and a text under your post.
How have you made it?
Cant find any option at profile settings to this too
Click to expand...
Click to collapse
Click the quick links button then head down to edit signature
Click the quick links tab next to "user cp" , then go down the dropdown box til you see "edit signature" , hope that helps
gav-collins1983 said:
]Lcd density changer, works on our phone, using the Rom below unless lee's released an update from 2.0.0 , and v1 kernel
I have adjusted from default 240, I'm assuming that's dpi, to 220, I ain't tried other sizes, do so at your own risk,
You can find the lcd density changer in the android market for free
Click to expand...
Click to collapse
Why no direct link to the market app???
detovenaar said:
Why no direct link to the market app???
Click to expand...
Click to collapse
http://www.google.co.uk/url?sa=t&rc...mYjvBA&usg=AFQjCNEN3t4vBQFSYa4Iu6KPcP4cK_i54g
there you go
wew nice one!!
works perfect with LeeDroids 2 and LeeDroids kernel
first option (do not reboot) didnt worked, i had to use the "kill" option (it performs a reboot then)
density at 200:
works perfect at htc sense with alot of widgets (no space left lol).
just some small (expected) things like a small "space" above the app drawer menue
{
"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"
}
or white space left, next to the dialer
---------
however, at density 180 the device doesnt boot up anymore (stuck at bootscreen)
batterypulldown helped ^^
w/ 260 ive no issues.
w/ 280 (WOW THATS BIIIG) everything is fine (except at the dialer: the no. 3 / 6 / 9 / # are "squeezed" and smaller, seems like the dialer img size is kinda fixed, so its getting squeezed ^^
w/ 300 (for blind peoples xD?) everything is fine, but dialer and some text inside of widgets (or text / names under apps at the homescreen) are more squeezed... .
Not sure if people know, but instead of installing another app you can just open your build.prop in the system folder and edit the line:
ro.sf.lcd_density=220(whatever number)
I don't see the point of installing another app just so I can change something that can be changed with a quick .prop edit. Also it can be changed in any ROM, its a system default line of code that is on every android system. Even if you only have your phone rooted with the stock ROM it can still be done.
DahIzzo said:
wew nice one!!
works perfect with LeeDroids 2 and LeeDroids kernel
first option (do not reboot) didnt worked, i had to use the "kill" option (it performs a reboot then)
density at 200:
works perfect at htc sense with alot of widgets (no space left lol).
just some small (expected) things like a small "space" above the app drawer menue
or white space left, next to the dialer
---------
however, at density 180 the device doesnt boot up anymore (stuck at bootscreen)
batterypulldown helped ^^
w/ 260 ive no issues.
w/ 280 (WOW THATS BIIIG) everything is fine (except at the dialer: the no. 3 / 6 / 9 / # are "squeezed" and smaller, seems like the dialer img size is kinda fixed, so its getting squeezed ^^
w/ 300 (for blind peoples xD?) everything is fine, but dialer and some text inside of widgets (or text / names under apps at the homescreen) are more squeezed... .
Click to expand...
Click to collapse
Wow, thanks for the input
Swifty76 said:
Not sure if people know, but instead of installing another app you can just open your build.prop in the system folder and edit the line:
ro.sf.lcd_density=220(whatever number)
I don't see the point of installing another app just so I can change something that can be changed with a quick .prop edit. Also it can be changed in any ROM, its a system default line of code that is on every android system. Even if you only have your phone rooted with the stock ROM it can still be done.
Click to expand...
Click to collapse
^^ What he said.
PLUS the permissions needed by this app don't make any sense:
NETWORK COMMUNICATION
FULL INTERNET ACCESS
Allows an application to create network sockets.
PHONE CALLS
READ PHONE STATE AND IDENTITY
Allows the application to access the phone features of the device. An application with this permission can determine the phone number and serial number of this phone, whether a call is active, the number that call is connected to and the like.
i dont care (alot) about the permissions: there are Privacy Controll apps like LBE for this
DahIzzo said:
Click to expand...
Click to collapse
I'm wondering what app is blurted out in your screen..
Via My HTC Evo 3D On The Now Network From Sprint.
Thought it might benefit everyone if we had a thread covering the customizations you've added for apps to DAGr8's Hybrid ROM. This could be useful for everyone to pre-setup a hyb.prop -- and especially DAGr8 for putting together a useful out of the box hyb.prop file.
Please list only the apps you've added or modified (not your whole hyb.prop) and tell us if you're running in tablet mode or not.
Here's the one's I've added or customized. I'm running tablet mode @ 192 dpi
# MY APPS
hy.com.anddoes.launcher.dd=192
hy.com.anddoes.launcher.pro-1.dd=192
hy.com.anddoes.launcher-1.dd=192
hy.com.speedsoftware.rootexplorer.dd=280
hy.com.siriusapplications.quickboot.dd=240
hy.com.box.android.dd=240
hy.com.qs.enhancedemail.dd=280
hy.com.sand.airdroid.dd=260
hy.com.adobe.reader.dd=320
hy.com.zonewalker.acar.dd=260
hy.com.twitter.android.dd=260
hy.com.jb.gosms.dd=260
hy.com.jb.gosms.it.dd=260
hy.com.jb.gosms.theme.kxnt.icecream.dd=260
hy.com.infinitecampus.mobilePortal.dd=320
hy.com.latedroid.ultimatejuice.dd=260
hy.com.latedroid.juicedefender.dd=260
hy.com.bw.xplayer.ui.dd=240
hy.com.functionx.viggle.dd=280
hy.com.wunderkinder.wunderlistandroid.dd=260
hy.VVM_release_aligned.dd=320
hy.SMemo.dd=192
hy.SNote.dd=192
hy.SMemoLite.dd=320
hy.com.asusresized.weather.dd=140
hy.com.jrummy.liberty.toolboxpro.dd=240
hy.com.asksven.betterbatterystats.dd=260
hy.ClockPackage.dd=280
hy.net.tsapps.appsales.dd=260
hy.tv.wpn.biokoda.android.emitfree.dd=280
great thread idea!
I havent added too many, its pretty nice as it is, but heres what ive got.
Running in Tablet mode @ 196dpi
hy.com.speedsoftware.rootexplorer.dd=260
hy.com.anddoes.launcher.dd=196
hy.com.snote.dd=196
hy.com.android.venezia.dd=196
hy.asusresized.weather.dd=140
hy.android.vending.dd=196
Once i start restoring the rest of my apps, im sure i will add more
I just posted in the ROM thread a way to update hyb.prop a bit easier if you have alot of apps using Excel. Not done on phone though.
http://forum.xda-developers.com/showpost.php?p=25978711&postcount=4799
anyone have luck with the AOSP Calender?
I noticed it is in System/Apps as Calender.Apk
I tried hy.com.calender.dd=240, but no dice...
hy.com.android.calendar.dd=
pfd278 said:
hy.com.android.calendar.dd=
Click to expand...
Click to collapse
hmm... i guess i may have prematurely thanked you lol.
while this seems to be the logical entry for calender, it hasn't changed after a reboot... still 320...
do you have it working at a lower dpi?
Not sure if someone already has covered this:
The asus weather resized that comes in various AOSP widget repacks
To get to the save button on setttings.
hy.weather.resized.ics.dd=180
That will allow the 'save' button to show on screen.
Now question.
What's the difference between # SYSTEM and # APPS?
Is there a sure way to find the app name? Like the calendar example higher up it's different.
thinguy said:
Not sure if someone already has covered this:
The asus weather resized that comes in various AOSP widget repacks
To get to the save button on setttings.
hy.weather.resized.ics.dd=180
That will allow the 'save' button to show on screen.
Now question.
What's the difference between # SYSTEM and # APPS?
Is there a sure way to find the app name? Like the calendar example higher up it's different.
Click to expand...
Click to collapse
hmm i didnt think the save button showed at 180... i have mine at 140, and it works just fine.
i assume #SYSTEM are the apps in System/Apps
and #APPS are in Data/Apps
edit#2: and i feel like an idiot once again.
hy.calender.dd is already under #system, and its already set to 320 lol. dont i just feel smart
thinguy said:
Now question.
What's the difference between # SYSTEM and # APPS?
Is there a sure way to find the app name? Like the calendar example higher up it's different.
Click to expand...
Click to collapse
Those are just comments. Just there to help you visually organize groupings. You can delete them and just have one list.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
I didn't want to post this here but not getting help anywheres else...but where do we actually change the dpi settings? Do we use root explorer? And what is the build that changes the over tab layout?
Sent from my SAMSUNG-SGH-I717 using xda premium
nash2000 said:
I didn't want to post this here but not getting help anywheres else...but where do we actually change the dpi settings? Do we use root explorer? And what is the build that changes the over tab layout?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Install RC4 and they hybrid_213.zip. That will put the files in your /system with a lot of the settings pre-populated.
The OP of the ROM has a breakdown on the files
I use ES file explorer to manage files and edit.
Just go into settings of ES and setup root and /system access.
e30andrew said:
hmm... i guess i may have prematurely thanked you lol.
while this seems to be the logical entry for calender, it hasn't changed after a reboot... still 320...
do you have it working at a lower dpi?
Click to expand...
Click to collapse
have it running at 180, but that wasn't controlling it, had changed hy.Caledar.dd to 180 earlier when I was editing the system dpi, and forgot I did it.
changed hy.Calendar.dd back to 320 and the calendar changed sizes.
thinguy said:
Install RC4 and they hybrid_213.zip. That will put the files in your /system with a lot of the settings pre-populated.
The OP of the ROM has a breakdown on the files
I use ES file explorer to manage files and edit.
Just go into settings of ES and setup root and /system access.
Click to expand...
Click to collapse
When I download the 213 zip I can not locate it anywhere...your talking about the 213 zip on the first page right...I've downloaded it a few times and can't find it
Sent from my SAMSUNG-SGH-I717 using xda premium
nash2000 said:
When I download the 213 zip I can not locate it anywhere...your talking about the 213 zip on the first page right...I've downloaded it a few times and can't find it
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Probably your download folder but it would depend on what you're using to download it.
pfd278 said:
have it running at 180, but that wasn't controlling it, had changed hy.Caledar.dd to 180 earlier when I was editing the system dpi, and forgot I did it.
changed hy.Calendar.dd back to 320 and the calendar changed sizes.
Click to expand...
Click to collapse
strange.
I dunno if you saw my edits above- but DaG already had hy.calender.dd=320 listed, so whenever i added one, it was ignored.
I ended up changing the original hy.calender.dd=320 to 213, and now it is perfect
{
"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"
}
pfd278 said:
have it running at 180, but that wasn't controlling it, had changed hy.Caledar.dd to 180 earlier when I was editing the system dpi, and forgot I did it.
changed hy.Calendar.dd back to 320 and the calendar changed sizes.
Click to expand...
Click to collapse
So you have calendar running?
Details Please!
What updates (AOSP, hybrid?) are you running?
What are your overall DPI settings?
thinguy said:
Probably your download folder but it would depend on what you're using to download it.
Click to expand...
Click to collapse
No joke...its no where's to be found. I ended up using the browser and it finally downloaded and I located them.
Sent from my SAMSUNG-SGH-I717 using xda premium
Did the same thing, but during one of my many edits, I changed his entry, and added the other one during another edit after pulling info from the manifest xml of the calender app. Didnt check calender every edit, thought I found it, hehe.
---------- Post added at 10:51 PM ---------- Previous post was at 10:42 PM ----------
thinguy said:
So you have calendar running?
Details Please!
What updates (AOSP, hybrid?) are you running?
What are your overall DPI settings?
Click to expand...
Click to collapse
Running the Inverted AOSP calender from the ROM OP. Flashed the 2_Hybrid213.zip
user default dpi 213
system default dpi 180
pfd278 said:
Did the same thing, but during one of my many edits, I changed his entry, and added the other one during another edit after pulling info from the manifest xml of the calender app. Didnt check calender every edit, thought I found it, hehe.
---------- Post added at 10:51 PM ---------- Previous post was at 10:42 PM ----------
Running the Inverted AOSP calender from the ROM OP. Flashed the 2_Hybrid213.zip
user default dpi 213
system default dpi 180
Click to expand...
Click to collapse
What are you using in your build.prop density?
What dpi is everyone using on there keyboard settings. 213 is fine on the Samsung keyboard but makes for tiny keys on swype and swiftkey x/beta changing it to 260 pushes part of the keyboard off screen. When i changed default.user.prop (or whatever it is) in hyb.prop the phone wouldn't boot leaving me to reflash.. Any idea are welcome
Sent from my SAMSUNG-SGH-I717 using xda premium
HEY Guys I Present you MultiROM_v2.5 Beta 4.1.2 on VZW VRAMC3 stock firmware
{
"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"
}
This Rom use Xperiacles mod to Change from Tablet, Phablet, or Phone UI w/Floating Multiwindow with just a click of a app and a reboot.
The ROM is based off the latest ota VRAMC3....so no gps or INTL ROM troubles
Its optimized for tablet at 160dpi with 200dpi optimized TWlauncher with Landscape...but you can change to whatever dpi or UI mode you want, thanks to Xperiacles mod!!!!!., No need to install Xpoesd...Xposed framework with App Settings and app settings preferences baked in and active at boot up. Touchwiz launcher 6x6 optimized and sized for 200 dpi 1280x820 with Rotation, tablet dialer and contacts, Multi dpi white Samsung keyboard that works on all three UI's. Tablet MMS, DownloadsUi, Task manager, Music player, My files, Multi window, Note 8 wallpaper chooser, etc........If you plan on messing with the dpi of TW Launcher, I recommend installing a backup launcher as TW will FC sometimes when you change dpi..Just clear Touchwiz home app data and it should stop.
you can also enable or disable home or back button in status bar on tablet mode via the UI Switcher. Once you enable or disable turn off the screen via power button and turn back on to take affect. Also you can change the quick launch icon on the statusbar(screen shot icon) to another shortcut or disable it for space with the quick lauch setting in Settings app.
IF YOU PLAN ON USING PHONE UI WITH THIS ROM (WICH I DONT KNOW WHY YOU WOULD) I LEFT THE STOCK APPS IN THE /SYSTEM/APP AMD THEY ARE ALL RENAMED TO WHATEVERAPP.BAK, BEFORE SWITCHING TO PHONE MODE AT LEAST CHANGE SecContact.bak back to SecContact.apk AND CHANGE PERMISSIONS..THENCHANGE SecTabletContacts.apk to bak AND DO THE SAME FOR MESSAGING APP...THEN SWITCH TO PHONE UI WITH UI CHANGER APP SO AT LEAST UR DIALER AND MESSAGING WORKS
One small instruction...before or after flashing, use root explorer on phone ...or 7zip with a pc.Navigate to system/etc/ . Got to the apns-config.xml, long press if using root explorer and select "open with text editor" or if on a PC use notepad++ and you will se a couple lines that read
mmsc="http://mms.vtext.com/servlets/mms?X-VZW-MDN=5555555555"
Just change the 5555555555 to you telephone number so it looks like
mmsc="http://mms.vtext.com/servlets/mms?X-VZW-MDN=412699776"
If you do this before you flash your fine. If you use root explorer make sure you save the edit, then change permissions to rw r r . Then reboot and you'll send MMS fine****If you don't do this you'll be able to text and receive MMS, but not send MMS*****Also if you want to revert to stock phone MMS app you will not need this fix because this is a stock Verizon based ROM.....
Beside that just boot in recovery
If coming from version1 just wipe cache and dalvik
If coming from another ROM Do a full wipe(Data,Cache and Dalvik) You can wipe System also if coming from a AOSP or INTL ROM
Flash ROM ....wait patiently and Reboot
First boot takes a while also...your not boot looping
After first boot If you don't like the set UI or dpi, change it via the ui switcher app and reboot
Experiment and if any of the app layouts look off.... change dpi to your liking via xposed App Settings app
Stock phone apps run best at 240-320 dpi and tablet apps 160dpi to 213dpi with [email protected] 1600x900 or1280x820
Download V1: http://www.androidfilehost.com/?fid=23043426517778694
7/19 Download V2.5: http://www.androidfilehost.com/?fid=23050663588004609
Changelog
7/19:Fixed xposed app settings to work on boot without changing permissions
Fixed siszing issues with system ui (Multi window traybar in tablet and in phablet at 220dpi notification pull down fits screen)
Added the original apn-conf.xml to system/etc and renamed to apn-conf.bak in case you wanna use stock or 2nd party messaging apps
Aded xposed xtoggles(gives you the ability to theme notification toggles(thanks xperiacle)
Added xposed x backroud (gives you the ability to change the backround almost anywhere..still in beta though..(thanks xpericale)
Added xposed multiwindow apps manager **important** this app will not work to add/remove apps to the traybar in tablet and phablet..but if you go to settings of the app on the top right hand corner it gives us the ability to resize floating windows to our liking, then reboot for changes to work
Some more fixes I cant think of.....
Next update will include aroma and some more tweaks and fixes..this is a work in progress. Deckoz is working really hard to get settings to work in dual pane without a work around.
Also if you use the shortcut fix for dual pane settings you can download a app called icon changer from the market(its free) and it gives you the ability to change and rename icons with stock or custom icons on touchwiz. Just use it to create a settings shortcut and use the stock settings icon and name the shortcut settings and you have a stock settings icon that launches dual pane settings!!!!!
*******This is a Beta release, you may find bugs***********This is a Beta release, you may find bugs**************
Bugs; Right now Settings will only work single pane at any DPI but the DP/Resolution must be at 480x 854 or will FC. Deckoz2302 and I are currently trying to find a fix for dual pane and he is pretty close. If you want settings in DualPane tablet mode the work around for now is change dpi to 160dpi @ 1280x820 with Xposed App Settings, then clear data of settings in App Settings. Now go to widgets and select settings shortcut/display click the icon and settings will launch fine in dual pane.Thanks to Deckoz2302
Xposed APP settings not stickingSome are problem having trouble with the xposed app settings not sticking. Here is the fix
All credit goes to Fabio R. : http://forum.xda-developers.com/show...&postcount=363
And stg13 for finding the link and posting on our thread....and bkdodger for re-writing it
Open root explorer (or similar file manager of your choice)..
Root directory go to: data/data/
find this folder: dev.robv.android.xposedmods.appsetting then long press to change permissions rwxrwxrwx (ok)
Enter dev.robv.android.xposedmods.appsetting folder (you will see two folders cache & shared_prefs)
Long press cache folder ( fix permissions to rwxrwx--x)(ok)
Long press shared_prefs folder (fix permissions to rwxrwxrwx)(ok)
Enter shared_pref folder should be only one folder inside named
ModSettings.xml (change permissions rw-rw-r--)ok
Reboot
Now remember this is a BETA...If you find a bug, instead of Whinning about it, PM me about it.... or help Fix it, or ask if someone knows how to fix it. I am aslo looking for anybody with dev skillz or knowledge of androird to currently help me make this ROM better.. Please PM me if interested
Thanks:Xpeiacle-for this wonderful mod..it would be possible with out you. Beans- for base deodexed rom. Deckoz2302- for helping and guiding me in right direction on settings delima. And all the people that PMd me to help and all the people from my multi ui thread for your suggestions and support.
Guess I was the only nut in my time zone awake tonight/this morning to download this lol. Havent had a chance to really test everything yet but so far she's running beautifully! Thank you for your hard work and all your help! I plan on staying with this rom for quite a while.
Sent from my SCH-I605 using XDA Premium HD app
Ibkevin said:
Guess I was the only nut in my time zone awake tonight/this morning to download this lol. Havent had a chance to really test everything yet but so far she's running beautifully! Thank you for your hard work and all your help! I plan on staying with this rom for quite a while.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
EDIT nvrmnd...dl works now...
I have big plans for this ROM......Just wanted to give some people a lil treat that have been asking to help out...
Sent from a unlocked and cocked GN2!!!!!!!!!!!
I'll be hopping on board to get this rom up and running with most of the functions our other roms have but geared toward tablet.
Biggest thing right now is getting a fully unlocked settings to include all or most of the hidden menus as well as launch in tablet mode
Deckoz2302 said:
I'll be hopping on board to get this rom up and running with most of the functions our other roms have but geared toward tablet.
Biggest thing right now is getting a fully unlocked settings to include all or most of the hidden menus as well as launch in tablet mode
Click to expand...
Click to collapse
Im glad you hopped on the train my man.........The future will bring good things
Sent from a unlocked and cocked GN2!!!!!!!!!!!
Flashed the ROM, almost all setup...definitely looking forward to the dual view settings !
ROM has a great start for sure!
Have it set up and running. Love the fact that besides the mms edit, you don't have to edit or adjust anything else.
I used the UI Switcher to set it to tablet mode at 213 DPI, and its running smoothly.
Thanks for all the hard work guys!
Running nicely so far. Is there a way to remove apps from multi window yet?
Sent from my SCH-I605 using xda premium
No major problems so far on my end. Minor graphical bugs but Running extremely nice.
Sent from my SCH-I605 using xda app-developers app
Sound doesnt work for me
With another kernel it does.
Cant hide home or other button from ui switcher
Sent from my SCH-I605 using xda app-developers app
BlueHarford said:
Sound doesnt work for me
With another kernel it does.
Cant hide home or other button from ui switcher
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Sounds weird...Its works fine for me. Stock kernel was working fine. After you enable or disable home or back buttons with UI switcher you need to turn off screen via power button and then it should work. Also you can change or disabler the quick launch icon on the status bar(Screen shot) via quick launch option in settings.
No more one handed operation?
Sent from my SCH-I605 using Tapatalk 2
Works well...however
Still thinks it's a tablet in the market....
Not too, too bad, assuming I can change the dpi setting to match the settings for a phone (320 dpi). Also trying to make the phone work in any configuration is tough (at least I'm feeling dumb). What could the proper dpi for the phone be? (works in tablet mode, but if I switch to phablet or phone it craps out. I tried setting it to 320 dpi...I might not be doing something right)
Otherwise, feels really good and fast..
bigmixxx said:
Still thinks it's a tablet in the market....
Not too, too bad, assuming I can change the dpi setting to match the settings for a phone (320 dpi). Also trying to make the phone work in any configuration is tough (at least I'm feeling dumb). What could the proper dpi for the phone be? (works in tablet mode, but if I switch to phablet or phone it craps out. I tried setting it to 320 dpi...I might not be doing something right)
Otherwise, feels really good and fast..
Click to expand...
Click to collapse
If you use the ui switcher it tells u tablet, phablet or phone dpis....Our phones stock dpi is 320 though...but in phone mode stuff like tablet dialer might FC because its ment for tablet or phablet..If you like normal phone mode .I lwft the phone apps in system/app.Just navigate there with root explorer and rename the tablet app to xxxxx.bak and the stock ap to xxx.apk, set permissions and reboot
Sent from a unlocked and cocked GN2!!!!!!!!!!!
bigmixxx said:
Still thinks it's a tablet in the market....
Not too, too bad, assuming I can change the dpi setting to match the settings for a phone (320 dpi). Also trying to make the phone work in any configuration is tough (at least I'm feeling dumb). What could the proper dpi for the phone be? (works in tablet mode, but if I switch to phablet or phone it craps out. I tried setting it to 320 dpi...I might not be doing something right)
Otherwise, feels really good and fast..
Click to expand...
Click to collapse
Insructions for phone mode are now in OP but all tablet apps will work in phablet mode..just not phone mode.......
Sent from a unlocked and cocked GN2!!!!!!!!!!!
Also as stated in the op. THIS IS JUST A BETA RELEASE...IF YOU FIND A TRUE BUG PLEASE PM ME. ONLY FOR TRUE BUGS...I APPRECIATE ALL FEEDBACK TO MAKE THIS ROM BETTER
Sent from a unlocked and cocked GN2!!!!!!!!!!!
I noticed that I can't seem to change the DPI to 165 and make it stick, and the back and home buttons persist regardless of what I do. Initially after disabling them they were gone, then after a reboot they came back to stay. These are minor though.
Overall this ROM is great. I have been using Moon, but never could get the GPS to work. It works perfect with this ROM, it's now my daily driver. I'm really looking forward to the final product.
Great job....running nicely. Can't wait to see where it goes with updates. :thumbup:
N2 Tap'd
Question on using App Settings with xPosed - I cannot seem to get my changes to stick. I have edited permissions on the modsettings.xml file in data/data/de.robv.etc - any other suggestions?
---------- Post added at 09:26 AM ---------- Previous post was at 09:02 AM ----------
stg13 said:
Question on using App Settings with xPosed - I cannot seem to get my changes to stick. I have edited permissions on the modsettings.xml file in data/data/de.robv.etc - any other suggestions?
Click to expand...
Click to collapse
This worked for me... http://forum.xda-developers.com/showpost.php?p=40364125&postcount=363 - my changes are now sticking.