Related
So guys,I wanted a long time ago,in a rom far far away ( ) to change my LCD density,because I found it very cool to make my screen seem like a higher resolution one.Also,it's like it grows in size,because more things fit in the same physical space.
However,in Samsung roms(I think only the HyperDroid rom doesn't have this problem,without me being 100% sure) problems can arise when changing DPI in the build.prop .One problem was that the camera was FCing,other problems included incompatibilities with the market etc.My deterrent to lower my DPI was the non-functioning camera.
Anyway,I visited the Desire HD forums 3 days ago,and I found something rather interesting in the IceColdSandwich rom thread.So,for this one all credit goes to LordClockan(Rom and kerned developer for the Desire HD) and alienmind(He and LordClockan are on the same team,or kind of,I don't exactly know),who found out about this(Or at least that's where I heard it from).
So,to change your dpi you can go to /data/local.prop (if the file isn't there just create it with root explorer) and write this line: qemu.sf.lcd_density=xxx,where "xxx" is whatever value you want.
So,while this isn't the best superduperwow tweak ever,and while some may already know it,it is useful after all,so I thought of sharing it with you guys.
Hi,
this solution isn't working for me :-( Tried on the latest leaked ICS 4.0.3. LPH original Samsung and Pure ICS Special edition 6.1 - http://forum.xda-developers.com/showthread.php?t=1451346. Both with the same result. Nothing happened. DPI is still 240. Checked several times - name and location of local.prop file and corectness of the string qemu.sf.lcd_density=xxx (xxx is 170 in my case) Any advices, pls?
Mikous said:
Hi,
this solution isn't working for me :-( Tried on the latest leaked ICS 4.0.3. LPH original Samsung and Pure ICS Special edition 6.1 - http://forum.xda-developers.com/showthread.php?t=1451346. Both with the same result. Nothing happened. DPI is still 240. Checked several times - name and location of local.prop file and corectness of the string qemu.sf.lcd_density=xxx (xxx is 170 in my case) Any advices, pls?
Click to expand...
Click to collapse
First,I think it has to have the right permissions.Dunno which it needs exactly,but try chmod 777.Also,the dpi value must be a multiple of 8,so try 168 or 176 if you want to be close to 160.Try these and report back.
Meanwhile,I'm wondering why the thread has a 1 star rating.It's not anything spectacular,but wtf?Anyway,I ain't here for being congratulated,so be it.
EDIT:Bear in mind that nothing will change in your build.prop .There,it'll still show 240.You will just see the difference.
Has anyone tried changing the dpi on gb roms?
Sent from my GT-I9100 using xda premium
drelite08 said:
Has anyone tried changing the dpi on gb roms?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
yep tried and worked very well with this app
https://play.google.com/store/apps/details?id=com.birdapi.android.dpipro&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5iaXJkYXBpLmFuZHJvaWQuZHBpcHJvIl0.
changed to 200 dpi
looks awesome
I used build.prop Editor to add a new property and it worked like charm
Thanks
gnan10 said:
yep tried and worked very well with this app
https://play.google.com/store/apps/details?id=com.birdapi.android.dpipro&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5iaXJkYXBpLmFuZHJvaWQuZHBpcHJvIl0.
changed to 200 dpi
looks awesome
Click to expand...
Click to collapse
I tried that software (the free version) and got a soft brick so backup if you want to try it.
tolis626 said:
First,I think it has to have the right permissions.Dunno which it needs exactly,but try chmod 777.Also,the dpi value must be a multiple of 8,so try 168 or 176 if you want to be close to 160.Try these and report back.
Meanwhile,I'm wondering why the thread has a 1 star rating.It's not anything spectacular,but wtf?Anyway,I ain't here for being congratulated,so be it.
EDIT:Bear in mind that nothing will change in your build.prop .There,it'll still show 240.You will just see the difference.
Click to expand...
Click to collapse
Thanks for advices. I did everything as you said. Changed value to 176. Check premission - granted 777. The value 240 checked in the build.prop Without success It seems that system ingore this file completely. Whatever is in local.prop file, DPI is still 240
It was the same yesterday when my S2 was running on latest beta leak LPH and the same behaviour with today's official ICS from Smamsung LPQ.
I'm looking to change my build prop on my nexus 7 due to some apps and games on market saying game or app is not compatible with my device. I know the device is more than capable of running all games and is very frustrating. How do I change the build prop and what risks are involved in the procedure? CNT find much on the search for changing build prop but get un related results.
Sent from my Nexus 7 using xda premium
Sirus2012 said:
I'm looking to change my build prop on my nexus 7 due to some apps and games on market saying game or app is not compatible with my device. I know the device is more than capable of running all games and is very frustrating. How do I change the build prop and what risks are involved in the procedure? CNT find much on the search for changing build prop but get un related results.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Well first off you need to be rooted. My experience with editing the build.prop is limited to just LCD density which I think is what you're after? Anyway its easy assuming you're rooted... I just use a root file explorer like es or root explorer... set the folder or file as read/write... edit the file and change the LCD density = to whatever... 213, 160, etc.... save and exit.... reboot.... that's what I've always done anyway across all my devices
Howdy all,
I have downloaded the kernel source for the v500 tablet (lg gpad 8.3), and would like very much for somebody to copy their boot file and send me the boot.emmc.win file. (or it may be a boot.img).
I need the boot.emmc.win file for the ramdisk it contains.
I currently have a kernel with working Gamma correction for the Google Play Edition V510 Here: http://forum.xda-developers.com/showthread.php?t=2647119
And, I was hoping to do the same for the V500 edition. I am willing to see what changes I can make that would be benificial for people, like better battery life, gamma control, smoother scrolling, etc . . .
Feel free to post one here, or private message me and I will give you my email address.
Thank you, sleekmason
I can do it if you have instructions upon how to
While we haven't exactly seen eye to eye on some things I would be glad too help. Would I be able to provide this from a twrp backup? How can I get it to you?
Sent from my LG-V500 using Tapatalk
Thank you to both of you. I sent my email earlier to your private messaging here. Please do send me a copy, it would be much appreciated!
This is the boot.img that's in a backup of the stock ROM that I made using Philz recevery:
https://www.dropbox.com/s/qepievo2w0uboko/v500-bootimg.zip
Thank you everybody! Looks like I've got it! Now to do something with it . . . Stay tuned.
Good luck
Sent from my SM-N900W8 using Tapatalk
So, Check this out; The module I enable in the 510 to get gamma control is "Interface to calibrate LCD color temperature" which is the same one in the 510 that I have enabled to get gamma control on there.
AND it is already enabled in the 500 kernel. this is odd given people say they can't change it. Has anybody tried using trickster mod to change the settings?
There is one other interesting point to this story in that, the lg 500 kernel also has a setting that the 510 doesn't have that is right below the interface setting called "Interface to calibrate LCD color temperature by QLUT" which is also enabled by default in the 500 kernel.
I unfortunately do not currently own the 500 so it will be impossible to test different settings until I get it right.
If somebody with a 500 is using a linux computer (preferably using Debian Wheezy), they can easily follow the guide I wrote to "roll your own kernel" in my signature to compile and test for the 500. The info you would need for the "Anykernel" script to put it back on the 500 device should be present in the ramdisk . . . ?
Sorry I can't do more folks. Without the device it would be silly to post a recompiled kernel I am not certain about. I had hoped that the settings for the 500 would be close enough to simply duplicate, as it is a LGE patch, but no go.
Best regards, Sleekmason
I installed trickster mod. It allows changing of color saturation but don't see a gamma control.
Rolling my own kernel is a bit beyond me.
Sent from my LG-V500 using Tapatalk
My Axon 7 European (G) version shows no options in Myvoice. The US version has tons of options. Why the difference? Can I do anything to fix it?
naparama said:
My Axon 7 European (G) version shows no options in Myvoice. The US version has tons of options. Why the difference? Can I do anything to fix it?
Click to expand...
Click to collapse
The functionality is gimped in the G/EU versions.
In the EU version it's just voice unlock, US version is far more extensive, have no idea why ZTE insist on fragmenting their user base with such stupidity.
If anyone can extract the .apk from the US rom that would be appreciated.
Sent from my SM-P600 using XDA-Developers Legacy app
Me too
I live in Paris -- my phone came from Germany -- and have the same problem. Would love to know if there is a fix.
Is it possible to load the USA software onto the G version, or something similar?
naparama said:
Is it possible to load the USA software onto the G version, or something similar?
Click to expand...
Click to collapse
Yes you can apparently.
I tried to extract the apk from the full us b29 image from system.new.dat
Unfortunately ImageExtractor constantly crashes when it gets to 'E' so I can only get all the apks from A to E.
If a USA user can either extract or simply backup the apk it would be most appreciated for us G users.
Sent from my SM-P600 using XDA-Developers Legacy app
How would you do that? I have a USA version.
naparama said:
How would you do that? I have a USA version.
Click to expand...
Click to collapse
I use ES file explorer which lets you backup any user or system app to a directory.
But the playstore has many similar backup apps dedicated just to backing up apks.
You could perhaps try this one.
https://play.google.com/store/apps/...ort&pcampaignid=APPU_1_6_yUWLDtHMfQ0gSlopf4Dg
Apk Export
Should just give you a list of installed apps, and then just navigate to MyVoice and it will copy the apk.
Much appreciate if you can manage it.
Sent from my SM-P600 using XDA-Developers Legacy app
Freakstyler said:
I use ES file explorer which lets you backup any user or system app to a directory.
But the playstore has many similar backup apps dedicated just to backing up apks.
You could perhaps try this one.
https://play.google.com/store/apps/...ort&pcampaignid=APPU_1_6_yUWLDtHMfQ0gSlopf4Dg
Apk Export
Should just give you a list of installed apps, and then just navigate to MyVoice and it will copy the apk.
Much appreciate if you can manage it.
Click to expand...
Click to collapse
OK. I have the apk. How do I send it?
http://sendanywhe.re/401L2LOP
See if that works
naparama said:
OK. I have the apk. How do I send it?
http://sendanywhe.re/401L2LOP
See if that works
Click to expand...
Click to collapse
Thanks for doing that...
It won't install unfortunately.
But it has still helped me compare the US/Euro versions.
Which in turn has led me to making some progress, It led me too 2x additional apks, One which I have installed, and I can get some of the voice options, although some menus are in English, and some in Chinese.
And some options are crashing, but I can enable voice unlock, or name the assistant, sound unlock, voice memos, weather.
I will need some more time, to see what I can get working well.
I'll keep you posted.
Appreciate the help.
Sent from my SM-P600 using XDA-Developers Legacy app
Sure. Sorry it didn't work. Don't know why they just didn't sell the US version in Europe. It has most if not all the lte bands. Do keep me posted. Friend in Paris having the same problem
naparama said:
Sure. Sorry it didn't work. Don't know why they just didn't sell the US version in Europe. It has most if not all the lte bands. Do keep me posted. Friend in Paris having the same problem
Click to expand...
Click to collapse
What's got me confused is....
The apks I managed to extract from a custom rom are called...
HaloSpeech.apk this is identical to the MyVoice.apk you uploaded.
Same version, size etc but named differently....
My G version also called MyVoice.apk is slightly higher version.
These won't install or overwrite my version.
I also came across HaloSpeechBase.apk which is about 50Mb.
This seems to contain the extra and missing voice stuff and installed, and as mentioned I can get to many of the voice functions, some crash and half of them are in Chinese.
I cannot help but think there should be a USA version of this file likely called something like MyVoiceBase.apk or similar and should be about 49Mb.
So perhaps if you could look to see if there perhaps a similar file on yours.
But not sure why the custom us rom i extracted them seems to have Chinese versions. But I will try and keep digging in the meantime.
I have enabled some of the functionality., so am confident this is doable.
Sent from my SM-P600 using XDA-Developers Legacy app
I will take a look
I didn't find anything with base, but I find a Halo file. Here it is http://sendanywhe.re/1S9YPENS
And this is about 49mb
Got nougat yesterday
Hello,
Old thread, but maybe still someone can help around this problem..
I have got G version now, and some of the functions are missing of CH version as My voice, and MI-tools (with ZTE's factory shipped sound meter, calculator etc) and MI-Assistant
Also My Voice (as you called halovoice).
Anyone has it for the G version or someone could export it
from US (halospeech)
and also MI-Tools and MI-Assistant from Chinese version ?
I would really appreciate theese files!
Thanks in advance, AO
I have found several values to change based on what I found in the stock APN settings for Boost Mobile that have allowed me to send SMS over 4g while on boost mobile network.
First make sure you have flashed moped_ryder universal boost apn fix.
At the bottom of your build.prop change the following settings.
ro.cdma.home.operator.numeric=310000
ro.cdma.home.operator.alpha=Chameleon
ro.telephony.default_network=10
telephony.lteOnCdmaDevice=1
Notice that on the last line you will only be correcting a typo.
Do not change APN from moped Ryder's fix
zaduma said:
I have found several values to change based on what I found in the stock APN settings for Boost Mobile that have allowed me to send SMS over 4g while on boost mobile network.
First make sure you have flashed moped_ryder universal boost apn fix.
At the bottom of your build.prop change the following settings.
ro.cdma.home.operator.numeric=310000
ro.cdma.home.operator.alpha=Chameleon
ro.telephony.default_network=10
telephony.lteOnCdmaDevice=1
Notice that on the last line you will only be correcting a typo.
Then in /system/etc replace the apns-conf.xml file (back it up first) with the one I have attached that is pulled from Stock Galaxy S5 for Boost Mobile. Reboot, and you are finished.
Click to expand...
Click to collapse
I'm guessing this is for using a rom like lineage? Does this change allow mms as well? That's the only reason I'm not on one of them. I need mms.
I am using aokp mm. And yea, MMS is working. I wasn't even trying to fix that issue just happened to notice the different values. It's now working perfectly.
zaduma said:
I am using aokp mm. And yea, MMS is working. I wasn't even trying to fix that issue just happened to notice the different values. It's now working perfectly.
Click to expand...
Click to collapse
Hmm. I tried those steps on cosmic and I still can't send SMS or MMS. I'll try and see if lineage works. I flashed the APN fix. Made the build prop changes and replaced the config file you posted. I really liked this ROM too. But need SMS and MMS. It's the only thing keeping me on stock.
Nevermind. I can send MMS just not SMS. Now my girlfriend is wondering why I sent a funky image and can't tell her it was a test. Lol!
Kreatur3 said:
Hmm. I tried those steps on cosmic and I still can't send SMS or MMS. I'll try and see if lineage works. I flashed the APN fix. Made the build prop changes and replaced the config file you posted. I really liked this ROM too. But need SMS and MMS. It's the only thing keeping me on stock.
Nevermind. I can send MMS just not SMS. Now my girlfriend is wondering why I sent a funky image and can't tell her it was a test. Lol!
Click to expand...
Click to collapse
I am sorry you do not need to change the apns conf file. I have removed it to prevent further confusion. But I am not sure what would be different between cosmic and aokp but I have working SMS/MMS/data/calls.
Cosmic is Android 7 while I have this working on 6. That may be the difference.
zaduma said:
I am sorry you do not need to change the apns conf file. I have removed it to prevent further confusion. But I am not sure what would be different between cosmic and aokp but I have working SMS/MMS/data/calls.
Cosmic is Android 7 while I have this working on 6. That may be the difference.
Click to expand...
Click to collapse
Yeah figured it might be due to the android version. I'm going to try these steps on aokp n and see if it works. If not I'll switch to aokp mm.
Update: I can now confirm that thus doesn't seem to work on nougat ROMs. At least it didn't on cosmic or aokp. I'll go with aokp mm. I'm super excited to use any non stock ROM at this point. Thank you for sharing this information.
It's no problem, I was having a different issue with data connectivity being disabled at random with a reboot being the only fix. I'm still having that so I went back to stock.
Im having issues with boost Mobile apn too.. Though i got sms,mms,data working on resurection remix 7.1.2 rom by just flashing the apn fix ..sms wont send if i restart my phone ..it remains on sending unless i make a call n hangup right away...weird... But i cannot get data, sms, or mms to work on cosmic rom, dreamux havint tried lineage...but i was really liking the way cosmic n dreamux rom looked.
I am having issues with Fredompop, since it looks like you have dived into the APN side of things, do you know how to view the stock APN settings in the stock rom? If I update the PRL in the stock rom it works fine. So I am guessing I just need to copy the settings to lineage.
The stock rom grays out the APN settings though so I can't view them.
Any way to view them or back them up?