Database Users

[Q] Will this work for our WF?

Found this thread on the HTC Hero section for it's open GL will this work for our wildfire?
http://forum.xda-developers.com/showthread.php?t=899801

Yea I flashed it, noticed an improvement in playing angry birds...i think.
Sent from my HTC Wildfire using XDA App

Will it work on cm7 nightlies kevin?
Sent from my HTC Wildfire using XDA App

Yeah
Sent from my HTC Wildfire using XDA App

Yes it works with just about every ROM, but, in my view, I can't see any benefit. (I dont play Angry Birds, and, the rest of the games and LWP's don't show any benefit).

How do you do this?
Just flash it like a rom?

Well, that's what I initially did. Flash the ZIP in Post #49 in that thread. But, on reading that complete thread, I guess you have to edit the build.prop file in /system (Using Root Explorer / ADB Push Pull).
However, this is where I cant get it to work. WHenever I add the 2 lines in Root Explorer and Save Changes, the phone reboots. If I use ADB, even after pushing, when I check the same file using build.prop, no changes are visible, (The opengles.version automatically reverts back to 65536 and the line which enabled hardware acceleration of the UI is gone) and, ASI only shows OpenGL 1.0 due to this
Well, I have no idea what I am doing wrong, will try it out again and see..

I'm a newb with this.
Could someone possibly make a bit more explained guide?

Very basic guide:
* Get Root Explorer or any other file manager that can show the root folders
* Open Root Explorer, change permissions on top to R/W (Be very careful after that. Dont delete anything!)
* Locate the file build.prop under /system
* Long Press the file, Select Edit with Text Editor
* Updated: (ADB Commands Copy - Pasted from another post by kevin2516. Thanks mate )
*Make sure ADB is installed on your system and it is working. There are many guides available to install ADB, so I wont be going into that.
*Start Command Prompt (cmd), Browse to your "Tools" folder into your SDK
*Use the ADB Pull Command adb pull /system/build.prop
*This will now be saved to your tools folder. Edit is using Wordpad / Notepad++ (Not Notepad) as follows:
*Locate a line which starts with dalvik. (The first one, there are 3 of them)
Add the following 2 lines before that:
debug.sf.hw=1
ro.opengles.version=65537
* Save it.
* Push it back to System using the ADB Push Command: adb push build.prop /system/build.prop
* Reboot ADB using the adb reboot command
* Then, grab the Flashable Zip in that thread from Post #48
* Flash it as normal
Done.
Check whether it is implemented or not by going to Android System Info > System Tab > OpenGL. Here, there are 2 OpenGL versions. The first line should say 1.1, and the second should say OpenGL 1.0 ES.

With S-On you cannot change the systemfile directly I think. Thats the reason why your system not keep the change. I have write by myself a little install zip and flash it with nandroid and it works. the zip only works with wildpuzzlerom v0.8 and you can find in the thread for wpr0.8.

bgx said:
With S-On you cannot change the systemfile directly I think. Thats the reason why your system not keep the change. I have write by myself a little install zip and flash it with nandroid and it works. the zip only works with wildpuzzlerom v0.8 and you can find in the thread for wpr0.8.
Click to expand...
Click to collapse
Well, I took your flashable ZIP, removed the build.prop it contained, and replaced it with the build.prop of CM7 Nightly 2. Then, I tried flashing it, still no change.
Now, I have no idea whether I am 'allowed' to change flashable ZIP's like that or not, but, from what it is looking like, I am still unable to get this working on CM7NB2. I'll probably try making a flashable ZIP from scratch later as I get time.

bgx said:
I have write by myself a little install zip and flash it with nandroid and it works. the zip only works with wildpuzzlerom v0.8 and you can find in the thread for wpr0.8.
Click to expand...
Click to collapse
If it's simple enough, it would be nice if you could tell how to do a flashable zip (or yourself make a one suitable for CM6/7 ). I just want to test these libraries on CM7, any help is appreciated
Don't expect nothing special, I'm not a dev!

3xeno said:
Very basic guide:
* Get Root Explorer or any other file manager that can show the root folders
* Open Root Explorer, change permissions on top to R/W (Be very careful after that. Dont delete anything!)
* Locate the file build.prop under /system
* Long Press the file, Select Edit with Text Editor
* Then, locate a line which starts with dalvik. (The first one, there are 3 of them)
* Add the following 2 lines before that:
debug.sf.hw=1
ro.opengles.version=65537
* Save and Exit
* Then, grab the Flashable Zip in that thread from Post #48
* Flash it as normal
Done.
Check whether it is implemented or not by going to Android System Info > System Tab > OpenGL. Here, there are 2 OpenGL versions. The first line should say 1.1, and the second should say OpenGL 1.0 ES.
Click to expand...
Click to collapse
But it's not working for CM7?
Where can i find FLashable zip? I don't understand where is post #48
Even if i find, i have read, that it's not working? Or working?

You can find the OpenGLES 1.1 Flashable ZIP in Post #48 of this thread:
http://forum.xda-developers.com/showthread.php?t=899801
I have updated my post since Root Explorer method doesnt work (No S-OFF).

3xeno said:
You can find the OpenGLES 1.1 Flashable ZIP in Post #48 of this thread:
http://forum.xda-developers.com/showthread.php?t=899801
I have updated my post since Root Explorer method doesnt work (No S-OFF).
Click to expand...
Click to collapse
You wrote : last edit: I didn't notice any difference, much like the test ran above. I'm going to revert until more knowledgeable people look at this.
if it is like you saying, then i dont have point to that **** too.
i think devs who makes this rom should instal in rom everything what can increase perfomance. so im waiting for the rom with all those things instaled.
will it happen someday?:/

vilks said:
You wrote : last edit: I didn't notice any difference, much like the test ran above. I'm going to revert until more knowledgeable people look at this.
if it is like you saying, then i dont have point to that **** too.
i think devs who makes this rom should instal in rom everything what can increase perfomance. so im waiting for the rom with all those things instaled.
will it happen someday?:/
Click to expand...
Click to collapse
Which is exactly what I said in the CM7 thread. No one here has till date, found verifiable gains, with using OpenGL on the Wildfire. Everyone reports the same thing, that there is no or absolutely negligible (Which I think is just a mind thing) change in gaming / intensive applications performance.
If you are looking for ROM's wit inbuilt OpenGLES Support, WildPuzzle has a flashable ZIP, and DS and DK Roms provides it inbuilt in its latest version. For the others, the manual method has to be followed.

[ROM][KANG] CherryKANG 0.9.4 1512max 384min [CM9] synced [11/04] Now supports goo.im!

Hi guys..
I just want to say thanks to the cm team for bringing ics to our touchpads. None of the work in this rom is my own.. I have just used the great tutorials and stuff I've picked up before to compile this. All credit to everyone who put work into this!
This rom includes cherry-picks from http://review.cyanogenmod.com such as the fixes below
A wifi fix -- review.cyanogenmod.com (Although some people are reporting wifi issues still. I recommend a full wipe)
I have also compiled my own kernel into this.. which I set the default CPU speed to 1.5ghz and the default governor to ondemand. I also added HAVS support. Although I don't know if we really need it on a tab. Maybe it will help slightly with battery life?
These are settings that I like and normally run. So don't flame me!
I am looking for pointers too.. for what to do next. I would like to add the webOS style recent apps mod next. Also ROMControl would be nice from here .. some pointers on how to include would be helpful. Any help greatly appreciated
So.. please remember.. I made this for myself... to teach me something.. someone just said I should post it!All credit goes to the people that contribute to cyanogenmod.
Cheers and enjoy
Buy me a beer if your a fan! Hit donate!
IN THIS BUILD
0.9.4 --- UPLOADING AS WE SPEAK!! Check back in an hour
Hopefully now has Goo.im app support for ease of updates
Not much else (synced 11/04)
managed to put this quick one together in the midst of everything.. so not had much chance to test. let me know how it is.
DOWNLOADS
http://goo-inside.me/devs/philicibine/ Thanks for hosting! Loving the download numbers here guys .. thanks for the support
http://www.cherrykang.mythreed.com/CherryKANG/ Big thanks to @Jedipottsy for this one.
Thanks for all the support from everyone!
Gapps are not included
My antutu benchmarks have been over 6000 btw
Hit the thanks button!
Previous Builds
0.9.3
Now with 4.0.4 inside!!
New Cyanogenmod boot animation!! I left this in coz it looks cooool
Min CPU clock is 384 (No more SoD's!)
Synced 31/03
Lots of new commits so YOU MUST FLASH GAPPS AGAIN!
0.9.2
Min CPU clock is 245 now.
Synced 10/03
Lots of new commits so YOU MUST FLASH GAPPS AGAIN!
0.9.1
Synced 08/03
Netflix and YouTube HD FIXED -- Thanks to wtogami for his cherry-pick script.
0.9
Synced 07/03
Now has stylus input merged
unsure if netflix works yet (please test) and.. nope! It doesn't :'-(
CherryKANG-Bricked
AS REQUESTED -- No changes.. just a bricked kernel thanks to show-p1984
0.8.9
At last it works! Lol
Synced 28/02 should have Netflix - edit - doesn't
Wifi fix
120 dpi - see post 2 for market fix
CherryKANG wallpaper - awesome!
0.4.8a
Kernel rebaked into it. should be lots smoother now
0.4.4a
kernel and wifi fixed
nothing else changed just wanted to get back to a working state
0.4.1a
re-done kernel as last build compiled with standard cm kernel
0.4a
Removed 270 degree rotation coz it derped the bootup :-/
Recompiled the kernel and increased min cpu to 245 (sleep issues)
0.3a First CherryKANG named build! lol =D
270 degree rotation
dpi set to 132 (Requires fixed market apk)
wifi scan interval increased
0.2a
Novalauncher - hope its OK?!
Scrolling cache fix - for smoother scrolling in the browser and other apps. (Kanged from aokp github) credits to them
And a pretty tasty boot animation! From MindSplit - thanks!
Hope you likey

REMEMBER ... This is now 120 dpi. You will either need to download LCD Density Pro from the market, or see below for a free alternative!
Posted by Hockey4life0099 thanks!
or you can use the free version (or dpi changer) to modify the dpi back to 160
---------- Post added at 02:15 AM ---------- Previous post was at 02:03 AM ----------
I wrote this. It looks more complicated than it is cause i broke it down step by step. Ignore my cracked out numbering scheme, i didnt feel like shifting all the numbers down when i added more info.
1. If you dont already have it, download es file explorer
1b. go to the application settings and clear the data for the market
1c. download dpi changer and change dpi to 135(dont reboot yet)
2. go into the options on there and check the root explorer option and the mount option
3. download to TP
http://www.sundergaming.com/downloads/tabletmarketdpiunlocked.apk
4. rename the file Vending.apk
5. long press to copy the file (in ES file explorer)
6. click the star in top right corner (favorites)
7. Choose the phone (/)
8. navigate to system/app
9. paste the app
10. find the app in there called marketupdater.apk or something similar and rename it marketupdater.apk.bak
11. reboot
12. see if you can download an app like flash player. If you cant go to next step
12b. get back to system/app and click the Vending.apk and let it install.
You can mess around with the dpi if you want, but also remember that if the text is small, you can change the default text size in the settings.
The issue i encountered with this method is sometimes the fix stops working, but all you need to do to get the apps to download once again is clear your market data in the application settings. It is obviously much easier to download the app mentioned in the op, but this is for the cheapskates. your only other option is download dpi changer and just switch the dpi back to 160. That is painless but you loose out on some app compatibility and some screen real estate. I myself change the dpi to 138 and change the font size to large. Everything seems to be perfect. Best balance out there IMO.
nevertells2 said:
Do not install CM9 over CM7. Some have gotten away with it and others like yourself run into trouble. Do a clean install, that means running ACMEUninstaller. Here are some instructions I created just for an occasion such as this:
Since the release of CM9, it has become abundantly clear to me that one
needs to do a clean install of the rom to avoid all the little
nagging issues that so many folks are reporting. Whether you are
installing for the first time, upgrading from CM7 or installing
an update of CM9, one really needs to do a clean install.
Since the advent of the official CM9 nightlies, installing
the rom and the Gapps files via CWM seems to be much more
reliable. You still need to wipe the cache and Dalvik cache
before you reboot after installing any rom. If you run into
trouble after an install via CWM, then read on.
Those who know how to do it otherwise and are comfortable with that
feel free to deviate from this document.
For first time installers, you can skip this part. First thing
you need to do is a nandroid backup of your current install and
copy it over to your PC for safe keeping. Next you should backup
your apps using either Titanium Backup or My Backup Root. This will
allow you to restore all your apps after you are done with this
update. If the install goes South, you can always restore your
nandroid backup.
For the first time installers, if you have not already prepared
your PC for this project, you need to download the following:
1. ACMEInstaller2
2. ACMEUninstaller
3. Moboot 0.3.5.zip
4. ClockworkMod.zip(CWM)
5. update-cm-9.0.0-RC0-Touchpad-alpha2-fullofbugs.zip
6. UniversalNovacomInstaller.jar
7. The latest Gapps.zip
The ACME files, Moboot, CWM and the Alpha2.zip can all be found
on the OP for Alpha2 at:
http://rootzwiki.com/topic/18843-releasealpha2-cyanogenmod-9-touchpad/
The universal novacom installer and Gapps files can be found by doing a Google
search on the names above and you will find the download page. I found
the novacom installer here:
http://universal-novacom-installer.googlecode.com/files/UniversalNovacomInstaller.jar
You should download the latest Gapps.zip which
the last time I checked at the link below was 20120317:
http://wiki.rootzwiki.com/Google_Apps
First thing, open the run box on your PC and browse to the novacomInstaller
file. This is a Java executable, so treat it just like any .exe file.
However, since it does not end in .exe, when you browse to find it,
you will have to tell the browser to show "All Files." Once it is in
the run box, click on OK and the Novacomd drivers will be installed,
the Palm,inc folder will be created and the novacom.exe will be placed
in that folder. Next if the ACME files you downloaded are zips, unzip
them both into the Palm, Inc folder which you will find in the Program
files folder. If not zipped, copy both into the Palm, Inc folder. Now
your PC is prepared for installing CM9, so everything applies to first
installers and upgraders from this point forward.
First timers boot into WebOS, upgraders can do the same or boot into
your current install of Android. Connect your TouchPad to your PC
with the usb cable and open Windows Explorer on your PC. You should
see either the TouchPad as a drive, or cm_tenderloin if you are already
running a version of CM9. If you have not already created a cminstall
folder on your TouchPad do so now. Also create a folder named ICS
Install.
Next you need to copy Moboot 0.3.5 and ClockworkMod(CWM) into the
cminstall folder on your TouchPad. Now copy the rom.zip and the
Gapps.zip file into the folder you created named ICS Install. It's up
to you which rom and Gapps file you use if you are installing something
different from what is listed above. If you are copying files to the
Touchpad drive, you now need to right click the drive letter and eject
the drive when you are done. If you are copying files to cm_tenderloin,
you can just close Windows Explorer and both of you disconnect the usb cable.
Upgraders, now you need to run ACMEUninstaller and when it is done, your
TouchPad will reboot back into WebOS. Now both of you need to reboot while
holding down up volume to put the TouchPad into WebOS recovery or bootie
mode. You will know you succeeded if you see a large white usb symbol.
Now plug the usb cable back in and you should hear the PC beep indicating
the TouchPad is connected. You will not be able to see the TouchPad in
Windows Explorer, so don't try. On your PC click "RUN" and type in CMD.
This opens the command window. First timers type in the following in the
command window:
cd/ and press enter. You will see C:\
Now type cd program files and press enter. You will see C:\program files
Now type cd Palm, Inc and press enter. You will see C:\ program files\Palm, Inc
Upgraders, your novacom.exe may be in a different folder, so go browse to that folder.
Both of you enter novacom boot mem:// < ACMEInstaller2 in the command window and
hit enter. After a few seconds, you should see what is fondly called the "Double Penguin" on
the Touchpad. When the install is done, the TouchPad will boot to Moboot. Tap
the volume on the TouchPad to stop the 5 second countdown if you see one. Now
select CWM using the Home button, then Install zip file from SD card and use the
volume rocker to move down to the ICS Install folder. Select that and move to the
Alpha2.zip and select that. Start the install. When it is done, use the go back
selection to go back to the main CWM screen and select reboot.
Once Android is booted up(be patient, it takes a couple of minutes the first time),
play around with the browser, set up wifi, just to make sure your install was
successful. Now reboot back to CWM and do the same procedure to install the Gapps.zip
you copied to the ICS Install folder earlier. You're done with a clean install.
Upgraders, you know what to do, first timers, I hope you have friend around to show
you the ropes or you own an Android phone and already know the ropes. Good Luck!
P.S. I strongly suggest you make a nandroid backup of your new installation right now.
First timers, one makes a nandroid backup using CWM. Boot to CWM, select "Backup and
Restore" and select "Backup".
Click to expand...
Click to collapse
Sent from my cm_tenderloin using xda premium

what's the wifi fix ?

This one http://review.cyanogenmod.com/12342
Sent from my cm_tenderloin using xda premium

Does this have Gapps cooked into it?

No sorry... I'm using v11 though
Sent from my cm_tenderloin using xda premium

Ok thanks...

If we have CM7 installed do we do a factory reset/wipe of the caches and then install the zip directly?

dtwconsulting said:
If we have CM7 installed do we do a factory reset/wipe of the caches and then install the zip directly?
Click to expand...
Click to collapse
Yep.. I think so. I think you can also flash without a wipe.. but wouldn't recommend.. and if you do.. flash the latest gapps
Sent from my cm_tenderloin using xda premium

Cheers mate

hi, whats the webOS style recent apps mod you mention in the OP?

Drop Box link already dead
Any one have a mirror?
Thanks!

MatthewYiu said:
Any one have a mirror?
Thanks!
Click to expand...
Click to collapse
Still working for me as of 10:40am. But.... here's a mirror just in case.
http://www.mediafire.com/?q60g82098q1vh16
Gapps v11:
http://goo.gl/u9s8g
For additional related files and mods, see sprice's thread here:
http://forum.xda-developers.com/showthread.php?t=1452324

f_padia said:
hi, whats the webOS style recent apps mod you mention in the OP?
Click to expand...
Click to collapse
When u hold home.. the apps come across the screen horizontally. Looks like the card feature of webOS.
Its in AOKP so I might have a look at their github later.
Sent from my HTC Vision using xda premium

tapout27 said:
Does this have Gapps cooked into it?
Click to expand...
Click to collapse
Read much?

how about hw acceleration?

mercado79 said:
Still working for me as of 10:40am. But.... here's a mirror just in case.
http://www.mediafire.com/?q60g82098q1vh16
Gapps v11:
http://goo.gl/u9s8g
For additional related files and mods, see sprice's thread here:
http://forum.xda-developers.com/showthread.php?t=1452324
Click to expand...
Click to collapse
flashing now! =)

Hello,
is the wifi fix included in the kernel? if so, is it possible to make a only a kernel-package to flash with CWM over the standard CM9-0.6?
Thanks

Not quite sure how to do that just yet. Will look at some other kernels tomorrow
Sent from my cm_tenderloin using xda premium

coolineho said:
how about hw acceleration?
Click to expand...
Click to collapse
This is just a kang. I lack the knowledge to even attempt looking into that!
Its working the same as cm
Sent from my cm_tenderloin using xda premium

set a custom lcd density on I9305

A few have asked so...
To easily set a custom lcd screen setting...
download an app, or
create a file called local.prop containing the line below and save it in /data.
change the number in the line below to suit.
a setting of 320 made everything nice and big for my eyes.
Stock setting in Slimkat is 245.
this setting will over-ride the rom default, without changing the original files.
the below command will copy it there, then reboot to apply changes:
adb push /yourpath/to/local.prop /data
qemu.sf.lcd_density=320

Yep we know, this is nothing new and there are already hundreds of threads detailing this.
Thread closed.

Screen resolution messed up -help needed!

Hi, playing around with an app called "Resolution Changer Pro", I set my phone to 350x350 in order to try a few things how my smartwatch would behave, which has also android and 400x400.
That went OK, and I was able to get back to fullHD fine.
Then I also changed the DPI accidentally to 100 and then the phone crashed.
Rebooting results in a black screen and I can´t do anything....
With adb I tried to set the resolution back to something usable, and the reply was that the window manger is not running.
Then I tried to get hold of the build.prop with adb and checked the DPI setting there, which was 480 .. the defailt setting.
Now my android knowledge is at the edge, and I don´t have an Idea how to reset the settings back to normal.
What could I do without deleting everything and re-flashing?
Pros.. what should I do ??? :crying::crying:

Flash same rom via recovery.

maitrot said:
Hi, playing around with an app called "Resolution Changer Pro", I set my phone to 350x350 in order to try a few things how my smartwatch would behave, which has also android and 400x400.
That went OK, and I was able to get back to fullHD fine.
Then I also changed the DPI accidentally to 100 and then the phone crashed.
Rebooting results in a black screen and I can´t do anything....
With adb I tried to set the resolution back to something usable, and the reply was that the window manger is not running.
Then I tried to get hold of the build.prop with adb and checked the DPI setting there, which was 480 .. the defailt setting.
Now my android knowledge is at the edge, and I don´t have an Idea how to reset the settings back to normal.
What could I do without deleting everything and re-flashing?
Pros.. what should I do ??? :crying::crying:
Click to expand...
Click to collapse
First you have to flash TWRP in order to use terminal in recovery.
Download AROMA Filemanager from here thanks to @amarullz
Go into recovery then flash it. (don't forget to mount system partition first.)
Guide to path /system/ then select Menu->open console
type in
vi build.prop
Click to expand...
Click to collapse
Once you open the build.prop with vi , you can now use the arrow button to guide to your section.
There's two mode in vi, edit mode and connamd mode.
You have to enter "i" first to enter edit mode
Once you finish editing, press Esc on top and now you are back to command mode
Enter following command to save the file and quit:
:wq
Click to expand...
Click to collapse
Now press Close on right top then press menu and exit file manager, reboot your device.
You are done.
TIPs: Here's an useful command to delete a line that you can't use delete to eliminate
In command mode, type in following command to delete a line:
:dd
Click to expand...
Click to collapse

1. Ok, flashing the same rom did not help... this was the first thing I tried.
2. I already tried to work with my build.prop, which I downloaded with adb from the device.. I already said that in my first post.
In the build.prop the dpi setting is at 480, like I said. Modyfiying it from twrp with vi is the same as downloading it via adb and then modyfiying it locally and uploading it again..... this did not help, dpi was at 480, like I said.
Strange... right?
Where is the screen resolution saved? Dpi is in build.prop, but where is the resolution saved at?
The problem must be somewhere in the data partition, since flashing does not help. I erased system and re-flashed. no help.

maitrot said:
1. Ok, flashing the same rom did not help... this was the first thing I tried.
2. I already tried to work with my build.prop, which I downloaded with adb from the device.. I already said that in my first post.
In the build.prop the dpi setting is at 480, like I said. Modyfiying it from twrp with vi is the same as downloading it via adb and then modyfiying it locally and uploading it again..... this did not help, dpi was at 480, like I said.
Strange... right?
Where is the screen resolution saved? Dpi is in build.prop, but where is the resolution saved at?
The problem must be somewhere in the data partition, since flashing does not help. I erased system and re-flashed. no help.
Click to expand...
Click to collapse
Then you should backup before flashing or doing root permission changes.
You can now do a fully backup , data, cache anything And then flash the stock firmware via SP_FlashTool.
If you boot, then try to restore the partition one by one.

jwchen119 said:
Then you should backup before flashing or doing root permission changes.
You can now do a fully backup , data, cache anything And then flash the stock firmware via SP_FlashTool.
If you boot, then try to restore the partition one by one.
Click to expand...
Click to collapse
Ok, I did that... made a backup of all partitions, erased everything and re-flashed latest dev firmware.
Off course, everything works fine now, but all my settings and stuff are lost.
going back to my old data partition, the problem is back.
How can I get back to my old settings? What do you mean one by one?

Any way to change dpi without adb ?

I have rooted my BTV-W09 model. When I use 'adb shell wm density 320' from my computer terminal, the dpi setting is adjusted correctly, but it doesn't survive a reboot.
I tried to change the dpi setting with a build.prop editor directly on the tablet and with the Textdroider DPI app, but it doesn't work, it goes back to whatever DPI settings was implied by the display settings (from Small-400dpi to Large-480dpi).
Is there a way to permanently change the DPI setting to 320, or at least a way to do it directly from the tablet (without a computer)?

Why you not reading neighbor topics? Install Xposed, install App Settings module from here for example, activate it and setup whatever DPI you wish.

Thanks Slavon, but I'm speaking of a system-wide change, not just app by app. English is not my first language, sorry if it wasn't clear.

Sorry if I was a bit rude. Try "Pimp my rom" utility. Find it on Google Play. I worked for me and now I'm thinking of how to revert
Edit: if I got it right, this utility adds (modifies?) this key in build.prop: ro.sf.lcd_density

Not at all, I understand how it seemed like I was asking a duplicate question without looking in others threads, sorry again
And thanks a lot for the advice, I'll try Pimp my rom right away !

wlausrsker said:
Not at all, I understand how it seemed like I was asking a duplicate question without looking in others threads, sorry again
And thanks a lot for the advice, I'll try Pimp my rom right away !
Click to expand...
Click to collapse
If you just need to change density, you'd better try changing the value in build.prop first. And in case of any problems after, change the value of the key I wrote previously or restore the original build.prop from backup. Good luck.

Slavon-93 said:
If you just need to change density, you'd better try changing the value in build.prop first. And in case of any problems after, change the value of the key I wrote previously or restore the original build.prop from backup. Good luck.
Click to expand...
Click to collapse
I've tried this morning to change ro.sf.lcd_density to 320 in the build.prop and reboot. After reboot, ro.sf.lcd_density is still set to 320 but the display is still at 400dpi.
It's like ro.sf.lcd_density has no impact on the display dpi except for the display mode (tablet, phone, etc.).
Screen settings/Small + ro.sf.lcd_density=320 -> tablet mode in Chrome and 400dpi
Screen settings/Small + ro.sf.lcd_density=400 -> phone mode in Chrome and 400dpi
Screen settings/Large + ro.sf.lcd_density=320 -> tablet mode in Chrome and 480dpi
Screen settings/Large + ro.sf.lcd_density=400 -> phone mode in Chrome and 480dpi
I think maybe the DPI setting from build.prop is replaced during boot with the screen setting (Small:400dpi, Medium:440dpi, Large:480dpi). Could a init.d script could change the value after boot? I'll try tonight if the tablet allows init.d scripts to run.

Well, ok. I only quickly looked through the decompiled code. Change dpi with the app then, it'll make a backup of build. prop and try to compare both files - new and backup. I could have missed something. Just to mention, I didn't like the way tablet had behaved after changing DPI. EMUI is not well-designed for this. It's much better to set DPI for apps and leave it unmodified for system.

@wlausrsker this is covered in the apps running in phone mode thread. I posted there that the adb dpi change settings will stick after rebooting if you run the command "adb shell wm density 340 && adb reboot"*
*Use whatever density works best for you, I have found that 330 works best for me with the view mode and font set to large.

Slavon-93 said:
Change dpi with the app then, it'll make a backup of build. prop and try to compare both files - new and backup. I could have missed something.
Click to expand...
Click to collapse
johje said:
@wlausrskerI posted there that the adb dpi change settings will stick after rebooting if you run the command "adb shell wm density 340 && adb reboot"
Click to expand...
Click to collapse
johje, thanks but I tried it first and it doesn't survive reboot ("./adb shell wm density 320 && ./adb reboot" since I'm on Mac, it reboots in 400dpi).
Slavon, I've compared the files from before and after changing the dpi setting with the app, only ro.sf.lcd_density is changed, so you didn't miss anything.
Since methods successfully used by you and others don't work for me, it must be something I did differently on setting up my tablet. I used greatslon mod of TWRP and then flashed via TWRP the latest SuperSU (v2.79-SR1). Finally, I installed XposedInstaller and got xposed-v87-sdk23-arm64. Did any of you with reboot-surviving custom dpi setting used something different? (like the SRK Tool)
I'm off this weekend but I'll try next week to start over from scratch.

the reason adb change dpi and even build.prop change doesn't work is because huawei has set lcd_density in boot image. check content of /init.6x.rc
these init files are part of boot.img and will be overwritten at every boot. so what u need is a modified boot.img where this set lcd_density line is removed. Once you install that boot, you can set whatever dpi in build.prop and it will work. even adb dpi change will be persistent.
if you are on b026, i can share my edited boot.img

Thanks for the explanation bark1234, I now understand why everything I tried didn't survive reboot!
Thanks also for proposing your edited B026 boot.img but I'm on BTV-W09C100B005 and I can't find any B026 download for BTV-W09. From what I understand from other threads the latest Chinese OTA for the BTV-W09 is the BTV-W09C233B022, so I couldn't use it. Nevertheless, if you could maybe share it for others, it could help someone with the same problem on a BTV-DL09.
I tried to edit my boot.img but I'm a newbie. I've tried to extract my boot.img but I have no result with "cat /proc/mtd", so I extracted mmcblk0boot0 as a best guess. I tried to install abootimg to edit it but there's not blkid.h on Mac OS so I can't build it. If I give you what I extracted, could you maybe edit it like you did with yours? You would save me from applying at random a bunch of tutorials like I just did and hoping it will result in something usable In the meantime, I'll try and learn how to edit a boot.ini with my setup.

bark1234 said:
the reason adb change dpi and even build.prop change doesn't work is because huawei has set lcd_density in boot image. check content of /init.6x.rc
these init files are part of boot.img and will be overwritten at every boot. so what u need is a modified boot.img where this set lcd_density line is removed. Once you install that boot, you can set whatever dpi in build.prop and it will work. even adb dpi change will be persistent.
if you are on b026, i can share my edited boot.img
Click to expand...
Click to collapse
Just as an FYI, the adb dpi change initiated along with the reboot command has stuck for me after multiple reboots.

wlausrsker said:
Thanks for the explanation bark1234, I now understand why everything I tried didn't survive reboot!
Thanks also for proposing your edited B026 boot.img but I'm on BTV-W09C100B005 and I can't find any B026 download for BTV-W09. From what I understand from other threads the latest Chinese OTA for the BTV-W09 is the BTV-W09C233B022, so I couldn't use it. Nevertheless, if you could maybe share it for others, it could help someone with the same problem on a BTV-DL09.
I tried to edit my boot.img but I'm a newbie. I've tried to extract my boot.img but I have no result with "cat /proc/mtd", so I extracted mmcblk0boot0 as a best guess. I tried to install abootimg to edit it but there's not blkid.h on Mac OS so I can't build it. If I give you what I extracted, could you maybe edit it like you did with yours? You would save me from applying at random a bunch of tutorials like I just did and hoping it will result in something usable In the meantime, I'll try and learn how to edit a boot.ini with my setup.
Click to expand...
Click to collapse
If you are rooted, use flashfire app to get ur current boot.img from ur phone. and then copy it out to edit.
The tool i use for editing works on windows. i too have mac only, i have windows on vm in it.
https://www.dropbox.com/s/x46q5nzv49iauwi/Android Image Kitchen.rar?dl=1
Use above link to download tool i use.
unpackimg.bat will unpack boot img.
your init.x files will be in ramdisk, edit it there.
and then use repackimg.bat, it will create new boot.img.

johje said:
Just as an FYI, the adb dpi change initiated along with the reboot command has stuck for me after multiple reboots.
Click to expand...
Click to collapse
bark1234 said:
If you are rooted, use flashfire app to get ur current boot.img from ur phone. and then copy it out to edit.
The tool i use for editing works on windows. i too have mac only, i have windows on vm in it.
https://www.dropbox.com/s/x46q5nzv49iauwi/Android Image Kitchen.rar?dl=1
Use above link to download tool i use.
unpackimg.bat will unpack boot img.
your init.x files will be in ramdisk, edit it there.
and then use repackimg.bat, it will create new boot.img.
Click to expand...
Click to collapse
johje, it won't stuck for me, no matter how I try. Did you root by flashing the latest SuperSU? Did you installed xposed framework?
bark1234, thank you very much for the detailled explanation, I'll use Flashfire app to extract my boot.img and I'll try tomorrow at work on my Windows machine to edit it.

@wlausrsker I have not yet rooted my tablet. Once I got the dpi/phone apps issue fixed, it reduced my urgency for rooting. However, I will be rooting it soon, since a way has been found to enable the 5Ghz wireless adapter for the US version of the tablet. I will let you know if I am able to keep the dpi settings after rooting.

bark1234 said:
If you are rooted, use flashfire app to get ur current boot.img from ur phone. and then copy it out to edit.
unpackimg.bat will unpack boot img.
your init.x files will be in ramdisk, edit it there.
and then use repackimg.bat, it will create new boot.img.
Click to expand...
Click to collapse
Thanks again for the link and the explanation, it was really a painless process.
I used Flashfire app on my tablet to backup my boot.img (it resulted in a boot.lz4 file).
On my Windows machine, in a cmd window:
Code:
lz4 boot.lz4
unpackimg.bat boot
I then opened in Notepad++ the /ramdisk/init.61262.rc file to remove the line setprop ro.sf.lcd_density 560 in the on early-init and on boot sections of the file and saved.
In the cmd window:
Code:
repackimg.bat
rename image-new.img boot.img
I now have an edited boot.img to flash in TWRP. Does it seems to you that I did the editing correctly? The edited boot.img is 13.35Mb (about the same as the boot.lz4) but the extracted boot file before the unpacking was 32.77Mb. Is it normal?

13.9 is correct size. install this boot.img

For those of us following along. Does the edited boot image have to be flashed by TWRP in zip form? Or can we use Fastboot to flash it? or both will work?
I've done the edit's and have what I believe is a flashable zip. I personally like to use fastboot.
I have DPI set and holding by adb as I mentioned before but this is still nice to have.
Thanks

OP - here's a really easy way to change dpi and make it stick: https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi
I'm using it on my MediaPad M3 without issues. PS - 320 is my preferred dpi as well, but I found it caused some issues like Settings would crash. I'm using 322 now without any issue for the last couple weeks. Enjoy