Develop Bugs

[REQ] Modified CM9 phone.apk for custom DPI

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

CM9 160 DPI issues...

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

Auto-rotate bug on sgh-T989D?

Hey guys! Was just wondering if I was the only one with the same problem?
First rom I installed with this new phone was AOKP jb build-1.
Was messed, because the auto-rotate was inversed. When it was supposed to be portrait, it was displaying landscape, etc.
Then I downloaded the great TDJ's rom, and there again, had some issue.
Was turning landscape when I was landscape, but when I was putting my phone back in portrait mode, wasn't coming back to it..............
So I had everytime to get out of the app. Decided to just remove auto-rotate. Heard it was something about a file in lib folder that was set for T-Mobile phones, so it wasn't working fine for Telus' version.
Now I'm on ErickWill's version of JB, still the same. If I turn my phone 90 degree side, it'll come to landscape mode, but if I want it back to Portrait, no way I can get to it without exiting the application.
Any known fix for that?
Thanks!

The devs are working on some sort of ratational correspondence tracking module emulator script to correct this. Try searching for "rotation fix"...don't think anyone has done that yet! Be sure and report back. Mods please make this a sticky. I think we are on to something here.
Sent from my SAMSUNG-SGH-T989 using xda premium

A few others have used the JB rotation fix from the AT&T's Skyrocket thread on their T989 and reported that it does work. =) You can try if you'd like: http://forum.xda-developers.com/showthread.php?t=1779819

xjaynee said:
A few others have used the JB rotation fix from the AT&T's Skyrocket thread on their T989 and reported that it does work. =) You can try if you'd like: http://forum.xda-developers.com/showthread.php?t=1779819
Click to expand...
Click to collapse
Didn't work for me.. I'll keep searching! If anyone has something, feel free to post up D:

switchfo0t said:
Didn't work for me.. I'll keep searching! If anyone has something, feel free to post up D:
Click to expand...
Click to collapse
Hm. Maybe if you used the instigator x kernel with it, it may work. Most that have said it worked used both. I have yet to try to rotation fix, but I'll probably try tomorrow and let you know!
Sent from my SGH-T989 using xda app-developers app

[Q] Nexus screen buttons

Does anyone know if there is a working app mod or hack to enable the incredible2 to have nexus-like on-screen buttons and disabling the lights and functions of the hardware buttons like on ParanoidAndroid has it?

cowboyv said:
Does anyone know if there is a working app mod or hack to enable the incredible2 to have nexus-like on-screen buttons and disabling the lights and functions of the hardware buttons like on ParanoidAndroid has it?
Click to expand...
Click to collapse
This is the main reason I stick with PA. If someone can mod the framework of the rom you are using, it may be option, but most of the roms don't have that built in. You might mention it in the thread of the rom you use and see if someone can hook you up.

Yeah, I'm wondering if maybe you can copy and paste the frameworks folder from PA rom to the other rom and if that would activate the on screen buttons.

I doubt that would be a good idea, but I'm not the one to answer that one.
Sent from my Incredible 2 using xda premium

cowboyv said:
Yeah, I'm wondering if maybe you can copy and paste the frameworks folder from PA rom to the other rom and if that would activate the on screen buttons.
Click to expand...
Click to collapse
Just a warning, that very well may put your phone into a boot loop, if you decide to try it......BACKUP first
Sent from my Incredible 2 using xda app-developers app

@Phantom: according to this thread it's just a matter of decompiling framework-res.apk, making some changes and then recompiling the whole thing, which is why I'm thinking maybe it is as simple as copying/pasting the apk.
@Tricsuit: Yeah, I know. I already learned my lesson and before attempting stupid ideas like this one, I run a full back up of the rim, settings, apparently and data, and then make sure to save the back up file in my box to be able to retrieve it from my computer just in case something else hiccups.

cowboyv said:
@Phantom: according to this thread it's just a matter of decompiling framework-res.apk, making some changes and then recompiling the whole thing, which is why I'm thinking maybe it is as simple as copying/pasting the apk.
@Tricsuit: Yeah, I know. I already learned my lesson and before attempting stupid ideas like this one, I run a full back up of the rim, settings, apparently and data, and then make sure to save the back up file in my box to be able to retrieve it from my computer just in case something else hiccups.
Click to expand...
Click to collapse
Thanks for the share m8, I will try to look into this one more over the weekend. If you decide to give it a go with a copy and past let me know how it works out.

Yeah, I'm on call for the next couple of days so I won't be able to play with the rom, but if I'm able to make it work I'll post it here. :beer:

Welp, I began to toiler around with this, succeed in decompiling res-framework.apk, changing the bools, arrays and dimens values and added the menu images, basically all the way down to step 5, but I can't seem to recompile it back into .apk... uhm... a little help guys? ^^;

[Q] [REQ] Method of UNIVERSAL Tablet UI Mod for ICS/JB

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