Related
Hi Everyone,
I tried to find a lot on all sections and google for a good touchwiz Mod but to no avail. So i thought of asking u guys for some insight to Mod Touchwiz for our beloved Galaxy S.
So i extracted TouchWiz30Launcher.apk to a folder. Was checking the different resources and i came across \res\anim and i saw two files fade_in_fast.xml and fade_out_fast.xml. Now they are binary XML files. So the question is can we modify or delete some values and speed up touchwiz. I dont care about the fancy transition or effects. Just raw speed. Tried ADW and Launcher Pro but i personally didnt like it. Please forgive me if this is pretty simple. Here is the code for the files.
Guys we modify these values and recompile TouchWiz30Launcher with apk manager.
XML code for fade-in
<alpha fromAlpha="resource_id:0x0" duration="resource_id:0x10e0001" interpolator="resource_id:0x10a0005" toAlpha="resource_id:0x3f800000">
</alpha>
XML code for fadeout
<alpha fromAlpha="resource_id:0x3f800000" duration="resource_id:0x10e0001" interpolator="resource_id:0x10a0005" toAlpha="resource_id:0x0">
</alpha>
check attachment for the files.
Awaiting reply. Thanks in advance.
Come on guys. No one's intrested in tweaking touckwiz.
shawn_pro said:
Come on guys. No one's intrested in tweaking touckwiz.
Click to expand...
Click to collapse
wrong attitude
shawn_pro said:
Come on guys. No one's intrested in tweaking touckwiz.
Click to expand...
Click to collapse
the truth
shawn_pro said:
Come on guys. No one's intrested in tweaking touckwiz.
Click to expand...
Click to collapse
Attention whore?
I might be running Launcher Pro, but I support that you are doing this. Cheers!
Would be useful especially since i've seen Touchwiz drain less battery compared to other launchers. IMHO.
Sent from my GT-I9000 using XDA App
Thanks for your work, may i ask how to use your file? How could i combine it into the existing launcher application?
if it matters that much to you, try picking up how binary numbering works...
Anyways, if I were to try messing around with it - I'd change that last digit in the binary sequence from a 5 to a 3...
Firstly, it isn't binary, it is Hex.
I have not tested but I guess if you change the duration to a lower number, you may get lucky but I expect that these values actually point to another resource for the actual value.
nafem said:
Firstly, it isn't binary, it is Hex.
I have not tested but I guess if you change the duration to a lower number, you may get lucky but I expect that these values actually point to another resource for the actual value.
Click to expand...
Click to collapse
Sorry, I'm not really a programmer...I just offered an idea because nobody else seemed to at the time.
Also, I thought Hex was 6-digit ranging from 0-F/digit? Or is that for colors only?
Hey guys i tried changing the values for the duration but when i over written the modded touchwiz apk to system/app folder i keep on getting Force Closes. Guess i should take a different route. Thanks for the tips guys.
Sorry guys i didnt meant to be rude or show any attitute in the above post. I respect all XDA members. I just hope my findings would be useful to someone who be looking just for it.
Not really sure what you're trying to do with this. Are you trying to remove the fade-in/fade-out animation when using the home screen? Why would you? It looks cool!
I'm interested in removing the animation as well. It looks nice indeed, but it doesn't works smooth on my ZTE Blade. It used to work without lags on my T-Mobile pulse...
After changing the values in the XML file, is it possible to reinstall the file with those changes ?
If so, I can give it a try as well...
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
Ok, so earlier on i was having a mees about with the deviceconfig.xml in the asphalt obb file.
I got some good graphics working but it added a bit of lag.
I have now created a deviceconfig.xml wich will put the game to max graphics and also be extremely smooth. (Its about the same as we have now with the latest update, if not smoother)
Basicly what i have done is....gone into device config.xml and swithed our device with the galaxy s3, our device falls under medium-hi dev class. (That class has bad graphics) and changed it with high-dev class devices (galaxy s3 max graphics) so all i have done is switched the to names around.
There are one or two graphic effects i have turned off. They are very minor and not even noticable.
So..... heres what you have to do.
1. Copy the .obb file off you're device from android/data/obb/ com.gameloft.android.ANMP.GloftA7HM/ main.101.com.gameloft.android.ANMP.GloftA7HM.obb
2. Using 7 zip right click the file and open archive, now go to data/deviceconfig/ and you will see 1 file (deviceconfig.xml) delete it. It will take anout 2 minutes to delete.
PLEASE READ If anyone is nterested in having the game the way it should be then what we need to do is tell gameloft to enable hires_map for tegra 3 on twitter. just simplyu copy and paste this to gameloft. @gameloft please enable hires_map for asphalt heat tegra 3 {nexus 7) also put it in youre review in the playstore. it seams a bit extreme but otherwise we wil never have the game the way it should be. wich is what we all thought we where getting when we purchased it.
if enough people do this then maybe they will listen. its no good one or two people doing it as gameloft seam happy with the game the way it is.
3. Now copy the new deviceconfig.xml over o where the old one was. Once again this will take about 3 minutes to copy over.
4. Now exit 7 zip, delete the obb file wich is still on youre tablet and now copy the new one over.
5. Start the game, it will tell you it needs to download 1mb of data (this normaly resets everything we have done but it wont)
6. Enjoy.
I put a lot of trying and error into this to get it working the way it is. If there are any hiccups i will once again edit this file.
UPDATE!!!!!!
Enabled msaa
enabled gamma illuminance
enable high quality car shader
maybe one or two more things.
there is not much i can do in reguards to the enviroment. allthough it does look better.
you should try a quick race on huwai and you should see the differance. i noticed a slight frame rate drop every now and then, nothing to bad though and i am enjoying the game very much the way i have this xml set up.
i reccomend you pull the xml you are using now and keep it on youre computer for backup reasons, incase you think the game is to laggy.
Link Updated [https://docs.google.com/open?id=0B2EOPJ1y9uirdlI2MG0xYkIyQjg
UPDATE 2!!!!!!
this as hire map enabled. i disabled some other graphices to make this even remotely playable. i would not reccomend you keep using this si its laggy. this is just to show you what the game should look like. infact it should look better than this but as i said i dissabled some effects.ie gamma illuminance. post process render textures. dynamic car shader.
hi es map link https://docs.google.com/open?id=0B2EOPJ1y9uirLWZMamx1cnJqN2M
please do not write back to me complaining this is laggy. i allready know this and there is nothing i can do. we allready have the best we can get with the previous release.
No one done this?
Sent from my Nexus 7 using Tapatalk 2
Thanks for your efforts, if it wasn't so late I would give it a shot. I'll give it a go tomorrow mate.
TheChaoticLlama said:
Thanks for your efforts, if it wasn't so late I would give it a shot. I'll give it a go tomorrow mate.
Click to expand...
Click to collapse
No problem, just dont want this thread disappearing further down. As i can pretty much promise it will work.
Sent from my Nexus 7 using Tapatalk 2
i am doing it right now...will post results...
I hear batman does not have that good graphics on nexus 7. I dont have the game and not sure if there is a deviceconfig.xml in the files. But if someone can check and if there is, upload it here. I would be more than happy to take a look and see wht i can do.
I hav checked nova 3 and moden combat 3 and cant see a deviceonfig.xml so there is nothing i can do with those two games. Maybe spiderman has one but i dont own that game either.
Sent from my Nexus 7 using Tapatalk 2
I'll give this a try tonight. :good:
Spiderman has very glitchy graphics and could really do with a tweek! I've deleted it off my tab to make room for Horn so can't fit it back on to check if it has one of these files.
How do i copy the .obb file it wont even let me ? o.o
i can confirm that this does work to improve the graphics of A7. most improved was the reflections off the car what was dull before has environmental reflections now. hard to tell if there has been any track or environment improvements maybe leelaa can go into detail on what he has done?
thx & cheers
---------- Post added at 11:15 AM ---------- Previous post was at 11:12 AM ----------
leelaa said:
I hear batman does not have that good graphics on nexus 7. I dont have the game and not sure if there is a deviceconfig.xml in the files. But if someone can check and if there is, upload it here. I would be more than happy to take a look and see wht i can do.
I hav checked nova 3 and moden combat 3 and cant see a deviceonfig.xml so there is nothing i can do with those two games. Maybe spiderman has one but i dont own that game either.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
TDKR graphics are not bad at all and it's actually a fun game. i will have a look at the obb for it in a few.
---------- Post added at 11:23 AM ---------- Previous post was at 11:15 AM ----------
punk2k6 said:
How do i copy the .obb file it wont even let me ? o.o
Click to expand...
Click to collapse
first have your N7 plugged into the PC. go into your my computer and in your drives list it should have your n7 as the last one. look at the file list and open the android folder two options data / obb click obb. open the folder for A7HM. you will see the a7hm obb file listed as 1.36g right click copy. right click your desktop and select paste. if you did it right a pop up should come up showing the file moving to your pc.
then follow leelaas directions.
I just tried the fix and I can also confirm that it improves some graphics, namely the reflections on your car and the motion blur effect while using NO2.
Some minor problems occurred though: on the Rio track, at some points opponent cars appeared to disappear and reappear out of nowhere. Also, the game doesn't wait for you to touch the screen to continue after you've finished a race, moving instead right on to the results screen. Both of these are relatively minor niggles considering the improvement.
Thanks, leelaa.
t_007_v2 said:
i can confirm that this does work to improve the graphics of A7. most improved was the reflections off the car what was dull before has environmental reflections now. hard to tell if there has been any track or environment improvements maybe leelaa can go into detail on what he has done?
thx & cheersQUOTE]
what i have mainly done is switched are device config withe the galaxy s3's. the galaxy s3's class in the deviceconfig.xml has all graphics turned on. the only one that isnt is use_msaa {multi sample anti alasing} i have tried with this turned on and it does improve the overall quality of the graphics slightly, but there was quite a bit of frame rate drops. it was still very playable but i wanted to keep the game as smooth as possible and at the same time keep an acceptable frame rate. if anyone would like i could upload the deviceconfig.xml with the mssa enabled? and you can decide on the performance vs graphic quality.
as for the game going straight to the results, i have noticed this too. i dont know what is causing it but really isnt a problem. as the only thing you can really do after a race is touch the screen to continue. so really i see this as saving us doing a job lol. i will take another look in the xml in about an hour and see what i can bump up.
on a side note, i put the gameplay hud in low res texture. i personaly cant notice any diferance but this improved performance.
Click to expand...
Click to collapse
ok so i have bumped every setting i can, and for some reason it plays smoother than the last one i uploaded here. i cocked up one setting though and you could only see the car wheels. but not the actual car. i would say the lightiong and enviroment is as good as we can possibly get. i dont think we will ever see these graphics on our device from gameloft. just waiting for the obb file to copy to my device so i can see if i have corrected the car issue where you can see wheals only. if all is well i will upload. i think this can be compared to ios graphics if not better.
wont be long guys
So is the link in the first post the updated version or not cos it states new link? :fingers-crossed:
spthacker said:
So is the link in the first post the updated version or not cos it states new link? :fingers-crossed:
Click to expand...
Click to collapse
You might want to wait than to have to move that big arse file again like I'm going to have to do. Thx leelaaaaaa (;
Been playing the updated graphics version on the elite kernel set at 1.6 with the 650gpu and there is no lag at all. Why the he** is gameloft dumming down the graphics for n7 owners? Total crap from dumbloft
Sent from my Nexus 7 using Tapatalk 2
t_007_v2 said:
You might want to wait than to have to move that big arse file again like I'm going to have to do. Thx leelaaaaaa (;
Been playing the updated graphics version on the elite kernel set at 1.6 with the 650gpu and there is no lag at all. Why the he** is gameloft dumming down the graphics for n7 owners? Total crap from dumbloft
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
No it is not the new link, the next one i put will be calked updated. I have been running asphalt now with max graphics. Even graphics that are not turned on by default ie use_msaa and gamma_illuminance. I want to change the actual gamma file as i think i can make the graphics look even better. This process will take about 10 minutes and i know i can do it so theres no worries there.
The only problem is my lapop screen is completely broke so i have to connect it to our tv. But my wife is eatching the soaps. Its a stupid situation, but new file will be up tonight. And trust me, you will love it
Sorry or the hold up guys.
So my next process will be......edit the gamma.txt file, and test that on one or two tracks. If that pans out the way i want it to i will upload. If it does not look as good as the one i am testing now i will revert the gmma.txt and upload.
So there may be two files you have to copy over this time.
I will update the instructions if needed.
Thank for youre patience guys.
And i am glad its working for you.
Sent from my Nexus 7 using Tapatalk 2
OP Updated guys. new .xml file available. you can also see changes i have mad. we are now at the point where there are no more graphic effects to enable. enjoy, and please report back youre experiance. thanks
leelaa said:
OP Updated guys. new .xml file available. you can also see changes i have mad. we are now at the point where there are no more graphic effects to enable. enjoy, and please report back youre experiance. thanks
Click to expand...
Click to collapse
https://docs.google.com/open?id=0B2E...lI2MG0xYkIyQjg 404 Files Not Found
Link fixed, sorry about that
Sent from my Nexus 7 using Tapatalk 2
leelaa said:
Link fixed, sorry about that
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
no probs, just sending back now
The reason why are device has the bad graphics is dow to the xml. There are 4 classes low,medium,medium hi dev and high. For a strange reason our device falls in the meium category. I dont know why this happens but its something gameloft need to sort. But they dont seem to of acknowledged this at all. Because when the game was released our device was in medium class. And it was very bad, yes fir enough they updated the game and the graphics looked slightly better and framerate- bu in other places the graphics are worse. The main thing is that our device still falls into medium class.
All they really need to do is create a tegra class and assign our device to that class along with other tegra devices. Its such a simple fix but they dont do it. They are lazy and take shortcuts by doing what i am doing now and it seems they cant even do that properly.
We bought the game that was advertised, not a work in progress.
Sent from my Nexus 7 using Tapatalk 2
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
for rom go here :http://forum.xda-developers.com/redmi-1s/development/rom-rdnextgencustomizable-fast-smooth-t3016988
for questions and other query go here:http://forum.xda-developers.com/redmi-1s/help/qa-rdnextgencustomizable-fast-smooth-t3016995
res
RESERVED
ONE
More for future
Link Please
Where is the download link brother.
vowels787 said:
where is the download link brother.
Click to expand...
Click to collapse
in development section
DPI/Resolution error, perhaps
Hi. I really appreciate the time and effort you're putting into making this custom ROM for Redmi 1s better. :good: Just one thing, though, that really annoys me.
I dont know if this is a bug or not. If this can be helped, please help me... :angel:
The thing is, icons and other screen elements on the home screen are working fine when using the native launcher. Even the screen icon sizes can be changed as per convenience. :good:
But when using Themer ( ht**s : / / play(dot)google(dot)com(slash)store(slash)apps(slash)details?id=com(dot)mycolorscreen(dot)themer ) [sorry, links not allowed ]
,,,,,,, the screen elements of that launcher/theme are not fitting the screen as they are intended to. I have attached some screenshots of the situation. The empty space thus generated is very usable, I can move icons there,,, but I want that border to occupy at least 80% screen space as it was originally intended to.
Is anybody else facing the same problem while using any other launcher??
Can it be achieved via manual DPI changing? What needs to be done? Plz help.
P.S. I dont know wether thats the case, but after some reading I found out that this could be because of the value of DPI the play store is assuming my phone to be having.... the play store DPI settings or something for my phone If so, please tell me how to change it. Very annoyed.. :|
change system dpi
shanx_verma said:
Hi. I really appreciate the time and effort you're putting into making this custom ROM for Redmi 1s better. :good: Just one thing, though, that really annoys me.
I dont know if this is a bug or not. If this can be helped, please help me... :angel:
The thing is, icons and other screen elements on the home screen are working fine when using the native launcher. Even the screen icon sizes can be changed as per convenience. :good:
But when using Themer ( ht**s : / / play(dot)google(dot)com(slash)store(slash)apps(slash)details?id=com(dot)mycolorscreen(dot)themer ) [sorry, links not allowed ]
,,,,,,, the screen elements of that launcher/theme are not fitting the screen as they are intended to. I have attached some screenshots of the situation. The empty space thus generated is very usable, I can move icons there,,, but I want that border to occupy at least 80% screen space as it was originally intended to.
Is anybody else facing the same problem while using any other launcher??
Can it be achieved via manual DPI changing? What needs to be done? Plz help.
P.S. I dont know wether thats the case, but after some reading I found out that this could be because of the value of DPI the play store is assuming my phone to be having.... the play store DPI settings or something for my phone If so, please tell me how to change it. Very annoyed.. :|
Click to expand...
Click to collapse
try this app:https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi&hl=enand chage to 320
or manually adjust it
go to system>>build.prop>>open build.prop with es file explorer editor or any other>>change dpi to 320
next time please questions in q/a thread of this rom
thanks
There are lot of KK roms, themes, etc Make lollipop based ROM... That's what everyone wants... Good luck
Sent from my HM 1SW using XDA Free mobile app