SORRY TITILE SHOULD BE: [Q] [REQ] Method of UNIVERSAL Tablet UI Mod for ICS/JB, the forum won't let me mod that...
I don't really want to ask similar questions again... I've been looking SOOOOO hard on the internet for this, but all I got are all kinds of ParanoidAndroid ports for other devices, device- and ROM-specific mods not universally applicable and (finally) this thread Link showing a likely but very vaguely descripted method to enable tablet UI for ICS.
I know E4G has already got satisfactory ROMs for this purpose, but I have an HTC Incredible S (no separate Q&A forum for it), which hasn't got AOKP-JB (it has tablet UI included in settings) yet. It's now on CM10.
So I'm asking: how to enable tablet ui for any ICS/JB ROM? (It's OK even if it requires modding framework/services.jar/etc.)
Hope mates here can help for a bit. Thanks
Fixed for ya
XDA Moderator
kennyglass123 said:
Fixed for ya
XDA Moderator
Click to expand...
Click to collapse
Thanks sir.
Sent from HTC Incredible S @ CM10
Lower the DPI in the build.prop.
ro.lcd_density=XXX or something like that.
Sent from my SPH-L710 using Tapatalk 2
That's what I mostly saw in Google which simply doesn't work no matter how low I've changed that. Neither will other build.prop hacks work
Sent from HTC Incredible S @ CM10
AndyYan said:
That's what I mostly saw in Google which simply doesn't work no matter how low I've changed that. Neither will other build.prop hacks work
Sent from HTC Incredible S @ CM10
Click to expand...
Click to collapse
Hrmm....check around in the /data folder to see if there is a local.prop. That would be the only thing i could think of that would override the build.prop, but usually that has to be manually created anyways. What is the default density of CM set to on the Inc S?
zanderman112 said:
Hrmm....check around in the /data folder to see if there is a local.prop. That would be the only thing i could think of that would override the build.prop, but usually that has to be manually created anyways. What is the default density of CM set to on the Inc S?
Click to expand...
Click to collapse
1. build.prop density changes work but DOES NOT bring device into tablet, only shrinks display...
2. IncS has a default density of 240 as most WVGA phones.
3. /data/local.prop not found.
Thank you sir for replying and giving possible solutions But does the answer really goes in .prop files? I mean, in the ParanoidAndroid thread link I provided, 2nd post says for ICS some changes can be done to some .jar framework to lock the preference, but the guide doesn't tell which and exactly how... Could anyone shed light on that?
Sent from HTC Incredible S @ CM10
AndyYan said:
1. build.prop density changes work but DOES NOT bring device into tablet, only shrinks display...
2. IncS has a default density of 240 as most WVGA phones.
3. /data/local.prop not found.
Thank you sir for replying and giving possible solutions But does the answer really goes in .prop files? I mean, in the ParanoidAndroid thread link I provided, 2nd post says for ICS some changes can be done to some .jar framework to lock the preference, but the guide doesn't tell which and exactly how... Could anyone shed light on that?
Sent from HTC Incredible S @ CM10
Click to expand...
Click to collapse
How low have you tried setting it? Eventually, it will enter tablet mode. Try intervals of 20(make a nandroid before hand just in case) I can't remember if WVGA screens need 120, 160, or 180.. one of those should do it though. Tell ya what, I'll try on my Epic which is on CM 10.1.
At 240 is normal
At 180 its almost got a GS3 feel to it. Very spacious.
I skipped 160 and 140.
At 120 it has entered Hybrid UI.
Everything below that point( down to at least 20, which isn't usable lol) is still the Hybrid UI.
I guess that's why on JB, you have to mod the framework. Google is moving away from the traditional tablet ui.
On ICS though, the DPI change will work. I know that for sure. Lol
Sent from my SPH-L710 using Tapatalk 2
zanderman112 said:
How low have you tried setting it? Eventually, it will enter tablet mode. Try intervals of 20(make a nandroid before hand just in case) I can't remember if WVGA screens need 120, 160, or 180.. one of those should do it though. Tell ya what, I'll try on my Epic which is on CM 10.1.
At 240 is normal
At 180 its almost got a GS3 feel to it. Very spacious.
I skipped 160 and 140.
At 120 it has entered Hybrid UI.
Everything below that point( down to at least 20, which isn't usable lol) is still the Hybrid UI.
I guess that's why on JB, you have to mod the framework. Google is moving away from the traditional tablet ui.
On ICS though, the DPI change will work. I know that for sure. Lol
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Is that so? Once on my Epic at CM9 I tried a dpi as low as 120 and the SystemUI just FCs again and again. This time on IncS I had the density also changed to 120 but it enters a Nexus-7-ish phablet mode, and things have become way too small to operate on.
And BTW, the calculated tablet threshold DPI for WVGA is 128.
Damn that Google, I don't so care about Nexus 7 using the phablet UI (it should, really) but why the hell is Nexus 10 doing the same, you wanna make it a giant phone?! AND you removed tablet mode support just because of this?! How utterly childish
Sent from HTC Incredible S @ CM10
AndyYan said:
Is that so? Once on my Epic at CM9 I tried a dpi as low as 120 and the SystemUI just FCs again and again. This time on IncS I had the density also changed to 120 but it enters a Nexus-7-ish phablet mode, and things have become way too small to operate on.
And BTW, the calculated tablet threshold DPI for WVGA is 128.
Damn that Google, I don't so care about Nexus 7 using the phablet UI (it should, really) but why the hell is Nexus 10 doing the same, you wanna make it a giant phone?! AND you removed tablet mode support just because of this?! How utterly childish
Sent from HTC Incredible S @ CM10
Click to expand...
Click to collapse
Here is how I did it on Ainol Tablets. Smali code editing in android.policy.jar and services.jar.
I have no idea though if it is "universal" or not but it worked on multiple tablets.
fuser-invent said:
Here is how I did it on Ainol Tablets. Smali code editing in android.policy.jar and services.jar.
I have no idea though if it is "universal" or not but it worked on multiple tablets.
Click to expand...
Click to collapse
Thank you for finally supplying a legit-looking tutorial. Now, however, I'm concerned with the problem of how to transform a tablet with tablet UI to the Nexus-7-ish phablet UI. Now via build.prop hacks I'm only able to achieve phone UI and I want to know if the same method works and what modification in the parameters this needs to be altered... Thank you all again
Sent from HTC Incredible S @ CM10.1
AndyYan said:
Thank you for finally supplying a legit-looking tutorial. Now, however, I'm concerned with the problem of how to transform a tablet with tablet UI to the Nexus-7-ish phablet UI. Now via build.prop hacks I'm only able to achieve phone UI and I want to know if the same method works and what modification in the parameters this needs to be altered... Thank you all again
Sent from HTC Incredible S @ CM10.1
Click to expand...
Click to collapse
The reverse method should work. Just look for the PhabletUI code and make sure that the relevant sections in the guide I linked to in my thread point the device towards PhabletUI instead. You could also do the same for PhoneUI if you wanted.
If at any point you want to convert the new JB 4.2 UI back to Tablet UI, I used the Tabletizer Alpha app here. When it was done, I did have to move the update.zip to my computer and repackage/resign it for my tablet as well as edit the update-script but the jar files worked.
fuser-invent said:
The reverse method should work. Just look for the PhabletUI code and make sure that the relevant sections in the guide I linked to in my thread point the device towards PhabletUI instead. You could also do the same for PhoneUI if you wanted.
If at any point you want to convert the new JB 4.2 UI back to Tablet UI, I used the Tabletizer Alpha app here. When it was done, I did have to move the update.zip to my computer and repackage/resign it for my tablet as well as edit the update-script but the jar files worked.
Click to expand...
Click to collapse
Great thanks for the tip!
Sent from HTC Incredible S @ PACman v20
Related
So I was playing around with the build.prop, and decided to play with the LCD density. I discovered that if you bring it down, (I just cut it in half from 320 to 160, I don't know what the smallest/biggest it can be is) after rebooting Ice Cream Sandwich will look like how it does on a tablet!
I don't know if everyone already knew this or anything, but I thought it was cool and I bet that someone would be interested in making it work!
The problem is, immediately upon booting, system.ui force closes, meaning that you don't have navigation buttons anymore... I'm no developer, so I don't know why it dies, or how to fix it, but hopefully someone does, because this would be a fun ROM to try!
http://youtu.be/nx0bC-6vxMY
same thing happens if you set it to 240 dpi
try it...things won't b so tiny
Sent from my Galaxy Nexus using xda premium
mrfuzzie23 said:
same thing happens if you set it to 240 dpi
try it...things won't b so tiny
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks for testing that, now my question is what's the best way to revert back to how it was? I just reflashed my ROM, but I'm sure there's gotta be a better way...
patrick848 said:
Thanks for testing that, now my question is what's the best way to revert back to how it was? I just reflashed my ROM, but I'm sure there's gotta be a better way...
Click to expand...
Click to collapse
There is an app called LCD Density Changer that I used to use on my Nook Color. It required root and idk if it works on ICS or not.
the way I did it was I ran gscript to remount /system.. which happily force closes after its done so u can leave to another app, then used total commander to fix the build.prop.. I had a copy of build.prop renamed to build.prop.old sitting in /system... on hindsight u could use a script to do this for u..
Sent from my Galaxy Nexus using XDA App
You can change it in Rom Toolbox by JRummy16
240 will run things in tablet mode. If you have errors running some apps like YouTube put in landscape mode first. Also dpi 241 works well but not many tablet apps work
Sent from my Galaxy Nexus using XDA App
IT WOULD BE GREAT TO USE IT IN TABLET MODE W/ SOFT KEYS WORKING. I HAVE BUTTON REMAPPER AND USE VOL -/+ as back/menu. BUT IM PRETTY SURE TELEPHONY AKA PHONE CALLS DONT WORK AT 160 DSI BUT! 120 DSI SHOULD HAVE WORKING CALLS IN ANDROID 4.0.2 AND 4.0.3.
Phone calls work fine at 160.
Easiest way to revert it to have two build.props:
Build.prop and build.prop160
Use root explorer to rename the file you want
I also use the softkeys for root app to get onscreen buttons
If you get a fc loop for any other dpi just use adb push build.prop /system/ to fix
Making sure you have a backed up build.prop in your adb folder.
This looks good lol hope somebody picks up on this asap!
Sent from this GN on 4GLTE!
That's pretty cool, but this thread probably doesn't belong in development as nothing has been developed.
Please don't post in the wrong topic. It pisses me off.
shenye said:
Please don't post in the wrong topic. It pisses me off.
Click to expand...
Click to collapse
Sorry, thanks for moving it.
Credits goes to st.matt, he gets full credit for the programming. He seemed a little busy, so I thought I'd spread the news so you guys can implement into your builds.
st.matt said:
Also just a run-down of how it works for anyone that is interested:
I use three different elements to get it working. Firstly, I use a small addition to surfaceflinger to set a system property (sys.orientation.landscape) to 1 when it is in landscape mode (either 90 or 270 degrees rotation) and 0 when it is in portrait mode (0 degrees rotation).
When this is set an init service will start depending on the value of sys.orientation.landscape, which in turn starts a script (/system/etc/rotate_lights.sh) which takes the brightness value from the expected led class (ie. if it's changing to landscape it will look at /sys/class/leds/button-backlight-portrait/brightness) and then set this to the new orientation's led class.
The third part is a small modification to the lights lib which also checks that system property when making changes to the button backlight brightness so that it sets it to the correct class.
Click to expand...
Click to collapse
The necessary files/code are on Virtuous' ICS vivo repository: https://github.com/vivo-ICS/android_device_htc_vivo, and you will also need the patched proprietary libsurfaceflinger.so that references to the changes.
Any way to make this backward compatible with cm7.2?
Un1c0de said:
Any way to make this backward compatible with cm7.2?
Click to expand...
Click to collapse
made a CM7.2 kang for you Inc2 users.
All I did was put in the latest commits as of March 03 2012 and added the rotating softkeys. I can't really test it because I don't have an Inc2, so back up your data in case you are not sure if it will work.
You can flash this without wiping if you are on 7.x already.
For the IncS, I know the rotating buttons for them are not perfect. Sometimes you have to toggle the brightness to get it working. Other times it might take a few seconds to rotate instead of immediately. This is because this script was originally written for ICS roms in mind, but it's backwards compatible with GB.
http://www.mediafire.com/?lggqggdx1m4n656
Wow thanks Kaijura. Downloading now, will post back with results
Sent from my Incredible 2 using xda premium
Thanks Kaijura for posting the info, and the CM7 build. Appreciate it a lot
Is this rom dependent? It will only work on cm 7.2? has anyone tried it on miui? Or any other roms?
Sent from my Incredible 2 using xda premium
Ihatepullups said:
Is this rom dependent? It will only work on cm 7.2? has anyone tried it on miui? Or any other roms?
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Will be trying on miui.us shortly.
Never mind its beyond my knowledge and time.
Sent from my Incredible 2 using xda premium
knipp21 said:
Will be trying on miui.us shortly.
Never mind its beyond my knowledge and time.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Ah, that blows would have been cool... Hey if someone points me in the right direction, I'll try: I know how to use adb and the sdk and I'm an experienced ROM'aholic
Sent from my Incredible 2 using xda premium
Awesome. Hopefully I have time tonight to check it out. Thanks
knipp21 said:
Will be trying on miui.us shortly.
Never mind its beyond my knowledge and time.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Ihatepullups said:
Ah, that blows would have been cool... Hey if someone points me in the right direction, I'll try: I know how to use adb and the sdk and I'm an experienced ROM'aholic
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
its different for miui, because we dont build it from source and cant cherry pick commits
miui is more like a sense rom port that uses cm9 or another aosp rom as a "base"
any significant changes have to be done in smali, which is more involved than java source....i k nowwhat has to be changed (or at least part of it) and where for rotating buttons in miui by diffing the builds from aerovan before and after it was implemented but it was a no go on my part...and didnt seem worth the effort to keep pursuing it atm
I tried this yesterday. My phone wouldn't get past the HTC boot screen. I ended up having to pull the battery and reflash my current ROM.
zohner said:
I tried this yesterday. My phone wouldn't get past the HTC boot screen. I ended up having to pull the battery and reflash my current ROM.
Click to expand...
Click to collapse
Hmm, well I guess that didn't work. If you push /system/lib/libsurfaceflinger.so from an earlier working build you should probably be able to boot.
I just copied the file over from the vivo build which seems that it doesn't work with the vivow.
Guess the vivow surfaceflinger is done differently.
kaijura said:
made a CM7.2 kang for you Inc2 users.
All I did was put in the latest commits as of March 03 2012 and added the rotating softkeys. I can't really test it because I don't have an Inc2, so back up your data in case you are not sure if it will work.
You can flash this without wiping if you are on 7.x already.
For the IncS, I know the rotating buttons for them are not perfect. Sometimes you have to toggle the brightness to get it working. Other times it might take a few seconds to rotate instead of immediately. This is because this script was originally written for ICS roms in mind, but it's backwards compatible with GB.
http://www.mediafire.com/?lggqggdx1m4n656
Click to expand...
Click to collapse
Just tried a flash over but didnt work for me. I guess I can always try a wipe and install.
This wouldn't be hard to add to Miui -- as long as they have no weird additions to libsurfaceflinger. You just need the patched liblights, patched libsurfaceflinger (built for CM), script in /system/etc and changes to init.vivo.rc (or init.vivow.rc for Inc2).
Requires no changes to smali or framework.
The other thing is that if someone wants to clean it up and submit it to CM then the MIUI team will pick it up themselves (someone already did this but didn't seem to have to skill / couldn't be bothered to clean it up to their standards and also didn't really submit it correctly).
I would do this but I don't really have the time these days.
Also: I suspect the problem with the lights not working sometimes could be solved just by adding the conditional I have that checks first to see if the brightness is zero to both orientations (in rotate_lights.sh). I will have a quick look at this soon.
just wanted to share a slight modification in the script. When the brightness level is set to the least the leds turn off completely. The attached script makes sure the leds do not turn off completely at this instance. Unzip the file and replace the file in your /etc/ folder. You may want to make a backup of your existing rotate_lights.sh just in case. Ensure the permissions on the file are the same as before after copying.
Just realized that the settings work only the first time when the phone is rotated. I guess I need a better fix. Sorry, remove the attachment as it has undesired issues. Fix No damn good.
Hi there, I'm kind of new. I've recently been modifying the dpi on our device and I can't tell you how amazing it makes the screen look. However, on cm9, any dpi lower than 190 causes the phone to crash so calls cannot be made or received.
Other phones have mods for this, however, flashing these causes all sorts of issues with service all together. Is anyone up for making one? I'm on my phone right now, but if you need a link I can post when I get home. Hope this is in the right section, thanks.
Sent from my SPH-D700 using Tapatalk 2 Beta-2
shockvaluejj said:
Hi there, I'm kind of new. I've recently been modifying the dpi on our device and I can't tell you how amazing it makes the screen look. However, on cm9, any dpi lower than 190 causes the phone to crash so calls cannot be made or received.
Other phones have mods for this, however, flashing these causes all sorts of issues with service all together. Is anyone up for making one? I'm on my phone right now, but if you need a link I can post when I get home. Hope this is in the right section, thanks.
Sent from my SPH-D700 using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
cm9 seems to have problems with alot more than just the phone with anything under 182. So if you're planning on going lower than that you might be in for a headache. I agree with stuff looking better at lower densities tho. I have my cleangb rom set at 160. Aokp seems to go to lower densities without as much difficulty, and has a lot more options than cm9, is very stable, and better on battery. In fact, LCD density is an option in rom control in system settings on aokp, so there's no need for a 3rd party app to change it. Maybe you should try flashing that and playing with it for a while, see what you think. Its basically cm9, just, better. IMHO at least. There's a thread for it in the dev section if you're interested. Peace nd happy flashing.
Thank you, I'll definitely give that a try as soon as possible. Do you know if aokp can spoof the dpi so the market is still usable?
Sent from my SPH-D700 using Tapatalk 2 Beta-2
Not sure what you mean exactly, but I've never had a problem using the market on aokp, and my LCD density is set to 175. What program are you using to change the density? Sometimes the actual app can cause the problem. If your rom doesn't have the option to change density then the best two apps you can use, in my experience, are rom toolbox and blade buddy. Both have free versions that allow you to change a lot of settings. And, just to make sure we're on the same page, when you say dpi, you are reffering to LCD density, correct? Meaning the lower the number the bigger your screen appears (icons and text look smaller). Whereas the default value is 240. Just making sure we're talking about the same thing.
Sent from my SPH-D700 using xda premium
186 is my sweet spot
Sent from my MIUI V4 Epic 4G via Tapatalk 2 beta 4
Are you having any issues with the phone or market apps? Which rom are you using? I think different densities look better with different roms. For instance, IMO, miui doesn't look good with anything under 220, but on the other hand, I have cleangb set to 160 and it looks great. Although I had to use spare parts + to make the text bigger, and the stock phone app won't change density, so when you open it, the dialer only takes up a small portion of the screen. I'm looking for a decent custom dialer to fix that. Any suggestions?
Sent from my SPH-D700 using xda premium
Hi,
I've made a small change in to the framework-res.apk (and SystemUI.apk for JellyBean) in order to have the navigation bar the same size as the status bar.
This was only tested with stock JRO03C and IMM76I. Proceed with the usual nandroid backup prior to apply.
Files with .jb.zip are ment to be used with JRO03C. Those without are for IMM76I.
Put me in a boot loop on bamf rom. Yes I wiped cache and dalvic. Had to nandriod
I dont think that this will work on other ROM's other than stock(for which it was made) due to the different framework-res. If anyone tries it be sure to make a backup
Would love to get this on bamf..
There should be a way to make it work on all roms
__________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Try using cm9s framework that might make it a universal flash for all roms
__________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Just wondering, what exactly did you change in framework to get it to that size?
AOKP already has this feature built in the ROM for over a month now.
The reason why it's not working for you guys is because the OP states,
This was only tested with stock IMM76I. Proceed with the usual nandroid backup prior to apply.
Click to expand...
Click to collapse
Meaning it'll ONLY work for stock IMM76I. If you're on other ROMs, those ROMs have a modified SystemUI.APK. So it's causing problems.
There should be a way to make it work on all roms
Click to expand...
Click to collapse
It won't because like I said before, every ROM does something different to SystemUI.APK so it won't work. AOKP has this feature built in
zephiK said:
AOKP already has this feature built in the ROM for over a month now.
The reason why it's not working for you guys is because the OP states,
Meaning it'll ONLY work for stock IMM76I. If you're on other ROMs, those ROMs have a modified SystemUI.APK. So it's causing problems.
It won't because like I said before, every ROM does something different to SystemUI.APK so it won't work. AOKP has this feature built in
Click to expand...
Click to collapse
I'm not stupid but there is a way to make it flash able for a roms, bc I wouldn't mind trying to add a link to my port if this was possible but then again I can also make just for miui
__________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Anon9mouz said:
I'm not stupid but there is a way to make it flash able for a roms, bc I wouldn't mind trying to add a link to my port if this was possible but then again I can also make just for miui
__________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Click to expand...
Click to collapse
I never said you are stupid. But every ROM in the world having this small "mod" with the SAME EXACT SystemUI.APK is impossible. That's like saying that every ROM must have the same framework-jar.apk.
Various ROMs in the dev forum already have this feature. And it's even better, you get to CHOOSE what size you want it to be (46,40,36,30).
It's easy to do this mod yourself. That way you can do it on whatever rom you are running. It can be done in 2 or 3 minutes once you know what to type. GUIDE HERE.
Link to working apktool for ICS HERE. Take framework-res.apk from your rom and place it in the same directory as apktool. Type 'apktool if framework-res.apk'. Then type 'apktool d framework-res.apk', make the changes in the guide, type 'apktool b framework-res'. You will get your new apk inside that directory.
mwalt2 said:
It's easy to do this mod yourself. That way you can do it on whatever rom you are running. It can be done in 2 or 3 minutes once you know what to type. GUIDE HERE.
Link to working apktool for ICS HERE. Take framework-res.apk from your rom and place it in the same directory as apktool. Type 'apktool if framework-res.apk'. Then type 'apktool d framework-res.apk', make the changes in the guide, type 'apktool b framework-res'. You will get your new apk inside that directory.
Click to expand...
Click to collapse
^^ either that or download a ROM with this feature. AOKP is one of them. You can control the size of the nav bar in ROM Control (you can change it back if you like as well). Very easy to do.
Don't most custom roms have this option in settings? I'm on liquidsmooth and have seen this on most of the roms I've used in the past few months. There are tons of options but I use 36px (I've used lower but accuracy comes into play).
Liquidsmooth also lets you set custom icons on the fly, nav transparency, background colors, icon colors, etc. Pretty slick.
player911 said:
Don't most custom roms have this option in settings? I'm on liquidsmooth and have seen this on most of the roms I've used in the past few months. There are tons of options but I use 36px (I've used lower but accuracy comes into play).
Liquidsmooth also lets you set custom icons on the fly, nav transparency, background colors, icon colors, etc. Pretty slick.
Click to expand...
Click to collapse
Same with AOKP.. tbh most LS features are from AOKP's "ROM Control"
I think people are missing the point. Despite the fact that this phone is a modder's dream, there are good reasons why someone would want to keep their phone on the stock ROM (stability, not having to "re-do" your phone once a day/week, if it ain't broke why fix it) but still might want to do little tweaks here and there if possible.
Example: I wanted to see the battery % on the notification bar, but could not justify the 2-3 hours of work reinstalling 100+ apps and tweaking endless system settings on my daily driver phone just to get it, regarelss of what else was in whichever ROM I'd download to get it.
So, even though I don't plan to use this particular mod, I'm glad there are people working on tweaking stock roms and will encourage them as much as possible.
Here's a modified framework for a small nav bar for those on CM9. I have a Verizon CDMA Nexus so it should work fine on Toro. Not sure how it will fair on others...so be cautious.
I also included one that minimizes the nav bar to 0.0 dp for a full screen experience. This should keep the ICS action bar overflow menu displayed for compatible apps. Works best with LMT launcher or GestureControl.
Flash in CWM. As always, make a back up! Enjoy!
Also included a CM9 stock framework if you want to revert back.
Zephik maybe you should tell everyone one more time that aokp has it, just in case
Archpope said:
I think people are missing the point. Despite the fact that this phone is a modder's dream, there are good reasons why someone would want to keep their phone on the stock ROM (stability, not having to "re-do" your phone once a day/week, if it ain't broke why fix it) but still might want to do little tweaks here and there if possible.
Example: I wanted to see the battery % on the notification bar, but could not justify the 2-3 hours of work reinstalling 100+ apps and tweaking endless system settings on my daily driver phone just to get it, regarelss of what else was in whichever ROM I'd download to get it.
So, even though I don't plan to use this particular mod, I'm glad there are people working on tweaking stock roms and will encourage them as much as possible.
Click to expand...
Click to collapse
I think you're exaggerating a bit there. I installed AOKP b31 some time ago and apart from trying out b35 yesterday, I'm still on b31 all that time before on a single flash without having to 'redo'. Also, if you're rooted you can just use Titanium Backup for all those apps. Currently running 350+ apps and using TiBu only takes 30 minutes unattended.
I agree that some people prefer stock, but those people are the ones that will never have any intention of flashing anything on their phone.
Sent from my Galaxy Nexus using XDA
Thanks its nice to be able to tweak the look of stock ics
Works great with ARHD4.0.1, thank you
Sent from my Galaxy Nexus using xda premium
Hey guys. Just got my SGS2 i love it and the roms are great! i just noticed one issue. When i change my build.prop dpi to 160, a lot of the CM9 tweaks "disappear" im currently on THIS rom and i love it. but i did notice changing the DPI screws up any CM9 ROM. i may just switch to aokp but i prefer CM9..
Ive cleared cache but that didnt do anything.. I am honestly surpised to see how changing the DPI screws a lof of things up... i had no problem changing DPI on my HD2. Any and all help is appreciated thanks guys!
Oh id also like to mention the bottom lights fail to light up as well.
Yeah, those issues are known. AOKP had a phone FC problem with anything lower than 200 DPI.
tzbigworm said:
Yeah, those issues are known. AOKP had a phone FC problem with anything lower than 200 DPI.
Click to expand...
Click to collapse
That explains why it would FC.. thanks man. Is it just a SGH-T989 issue or a AOKP CM9 wide issue?? I think i remember the phone FCing when i had AOKP on my HD2. Thanks for the info! i realized that i'll just change my settings, then change the DPI and they settings still stick!
Just want people to know that upon further investigation I've come to conclude the issue with 160 lies in the fact that android thinks it's a tablet xP so I just set to 162 and everything is just amazing and I love this phone! ^-^
Sent from my Galaxy SII T-mobile using Tapatalk
Does your phone.apk still work at 162? I was under the impression that the phone.apk would not work with DPI less than 180 without installing a modified version.
tzbigworm said:
Yeah, those issues are known. AOKP had a phone FC problem with anything lower than 200 DPI.
Click to expand...
Click to collapse
False. Where does people get these number from? I'm using aokp at 190 dpi with no problem
Sent from Samsung Galaxy SIV
Rod3 said:
Does your phone.apk still work at 162? I was under the impression that the phone.apk would not work with DPI less than 180 without installing a modified version.
Click to expand...
Click to collapse
Yes it does able to execute calls, group calls and everything working perfectly. This would have been my biggest pet peeve with ics but now I'm loving it!
Sent from my Galaxy SII T-mobile using Tapatalk
EDIT: Just tried using the phone, like actually making a call, and on CM9 it FC'd however the call went through. Ugh this really bothers me... i wonder why its FCing im gonna logcat
EDIT NUMBER 2: ^^
Well i figured it out. Having a resolution of 162 causes phone.apk to force close. BUT
THERE IS A SOLUTION (Found it in a couple of minutes on google) It is located here i used the phone0264.apk one and its perfect
Second issue, i tried downloading youtube from the market and it came up "device incompatible" which i knew from my HD2 is caused by "odd" DPI values, so i used a "hacked" market which forces a DPI size to the market. Its attached
To install:
Just rename phone0624.apk to Phone.apk and replace the original and make sure permissions are RW-R--R--
To install market, rename it to, Phonesky.apk and again assign the same permissions.
REBOOT
and all shall be swell again