Develop Bugs

[MOD] LCD Density - Higher Resolution Screen

You can increase the density (sort of like changing monitor resolution) on your screen by simply changing the build.prop file. This gives you more viewing area on your screen. The build.prop file contains many user variables that are editable and one of them is the LCD Density. The lower the number, the higher the resolution. The default value is 240, but by simply changing it to 200, you can increase the resolution and see more emails in your email app, more app listings in the market, more room for widget alignment, crisper graphics, and much more!
UPDATE 03/25/2011: ADDED SCREENSHOTS! (finally)
PERMANENT ROOT SOLUTION:
now that we can do perm root, you can permanently change this by modifying your build.prop file located /system/build.prop. look for ro.sf.lcd_density and modify the number and save and reboot.
Recommended value is 200, though many users like 190. If you are unsure what you like, please try TEST MODE shown below!
Please be sure to download Spare Parts from the Market, and disable Compatibility Mode in the app. This will fix many, many apps from not displaying full-screen, however there are some apps that will not re-size.
This works really well if you pair it with something like Launcher Pro or ADW.Launcher, where you have control over rows/columns and resizing widgets.
Easiest Method -- Go to Market and download one of the LCD Density apps. Search "LCD Density."
Phone-Only Method:
You can use Root Explorer, or any text editor like notepad++ or text edit.
1. Open a File Manager and locate /system/build.prop
2. Make sure "/system" is mounted as R/W (in Root Explorer, click the Mount R/W button at the top.)
2A. MAKE A BACKUP!
3. Open and Edit the file.
4. Find ro.sf.lcd_density=240 and change it to desired value (recommend 200 or 190 for G2).
5. Save the file.
6. Exit and Reboot!
Click to expand...
Click to collapse
If you use a separate text editor, just copy the file to your SDCard, edit it there, and move it back and overwrite the original. I recommend backing up the original just-in-case.
ADB Method:
at the cmd prompt:
1. adb pull /system/build.prop
2. Go to SDK / Tools folder and open build.prop in a text editor (recommend WORDPAD for Windows).
3. Find ro.sf.lcd_density=240 and change it to desired value (recommend 200 or 190 for G2).
4. Save & Exit
5. go back to cmd prompt and type: adb shell mount -o remount,rw /dev/block/mmcblk0p25 /system
6. type: adb push build.prop /system/
7. exit and reboot phone!
Click to expand...
Click to collapse
[Test Mode]
If you just want to play around with the setting for test, you can do something similar to the temp-root method shown below.
Open Terminal Emulator from your phone or use adb shell from your computer:
type: setprop qemu.sf.lcd_density 200 (or 190,etc)
press enter.
type: busybox killall system_server
press enter.
it will reboot quickly with your new display. Just reboot and it'll go back to stock. Once you find something you like, you can edit the real build.prop file.
---------------------------------
[original mod / pre-perm-root]
Below is for use with Visionary temp-root app.
This is basically taken from the LCD Density Changer app and applied to visionary.sh
You can increase the density (sort of like monitor resolution) on your screen by simply changing the build.prop file. Unfortunately, since we have temp-root only, it'll revert back. The LCD Density Changer - Free app lets you modify it without editing the build.prop and uses a hot boot to apply changes...
I wanted to automate it into startup with Visionary so here's what you can put into your visionary.sh file without even having the app:
Code:
setprop qemu.sf.lcd_density XXX #change XXX to 200, 190, etc
busybox killall system_server
Example Visionary.sh script is found on Post 51. This script also contains commands for Ad Block and Overclocking which can be found in separate threads on the forum.
I use "200" for the XXX density. Some people below mention 190 as their favorite number to use. 240 is the default!
note #1: killall command will do a hot reboot of your system.
note #2: you do not need to download the app to do this. you just need visionary app from Modaco/Paul O'Brien, which is on the market.
Here are some written instructions from V1R3Z on Page 3 of this thread if you do not know how to create and push visionary.sh to your device:
http://forum.xda-developers.com/showpost.php?p=8962877&postcount=27
update 10/30:
added mounting to read/write for /system and /data to the script for users who did not have it already in their script. also some people prefer using 190 as oppose to 200.
update 11/02:
removed mounting for the /data folder as it is unneccessary. make sure you use a proper text editor and save in a format the phone can read. it's probably a better idea to make the script on the phone than in windows.
credit goes to appelflap and jdsemler who found these things.

Hey, I gave this a shot but didn't notice a difference. Do you run any other commands in you visionary script? Do you put this at the end?
Update
Checked my build.prop, still set to 240. Never used the setprop command, but notice the property in build.prop doesn't have qemu.
Sent from my T-Mobile G2 using XDA App

I find 190 to work best.

mckinlk said:
Hey, I gave this a shot but didn't notice a difference. Do you run any other commands in you visionary script? Do you put this at the end?
Update
Checked my build.prop, still set to 240. Never used the setprop command, but notice the property in build.prop doesn't have qemu.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Hi - It doesnt modify the build.prop at all actually. I also have some other commands in my script to control adfree and setcpu, but perhaps adding these commands at the beginning will help:
Code:
su
mount -o remount,rw /dev/block/mmcblkp025 /system
mount -o remount,rw /dev/block/mmcblkp025 /data

Very nice. I just added a gscript to run it. It works like a champ.

Slows down g2 when uninstalled everything was back to normal.
Sent from my T-Mobile G2 using XDA App

I added the r/w to the /data and removed a line that killed the launcher after uninstalling bloatware. One of those steps did the trick. I love it at 190. I was so frustrated with how the resolution was better than the G1 but didn't really give me the impression with everything blown up.
Thanks for the details.
Sent from my T-Mobile G2 using XDA App

mckinlk said:
I added the r/w to the /data and removed a line that killed the launcher after uninstalling bloatware. One of those steps did the trick. I love it at 190. I was so frustrated with how the resolution was better than the G1 but didn't really give me the impression with everything blown up.
Thanks for the details.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Cool. I'll update the OP with the read-write commands.

Love the mod, thanks for the tip
any idea why after the hot reboot it causes sim checker light to email my location as if someone stole my phone and put in there sim?

Noticed the stolen report too with the kill launcher command. Must mess with the sim card negotiation and trigger something.
Sent from my T-Mobile G2 using XDA App

Forgive the noobisness, but are the icons in the app drawer supposed to look like complete ass with it set @ 190?

Trial and error results
That's what I noticed as well. ADW looks like crap and that's no lie. Some things aren't using the entire screen anymore.
One thing I've learned when it comes to having Android on the HD2 with a lcd_density of 180 is that you have to unmark compatability mode within spare parts. Since we g2 users don't have that app, we're kinda stuck.
BUT WAIT! Spare parts is on the market. Install it and then do an adb shell...
su
busybox killall system_server
AND IT DIDN'T WORK!!!
So I guess I'm gonna have to try a different density other than 190...
UPDATE:
changing the density to 200 made ADW look fantastic. Some apps still don't use the entire screen. Maybe rebooting entirely will help and actually adding these lines to visionary.sh instead of just running the commands through a shell...
UPDATE2:
Rebooting did nothing. Spare parts doesn't do anything so my question would be How do we get all apps to span across all of the screen?
My example is Weather and Toggle Widget with the Weather Forecast Add-on, the weather animation uses only half of the screen...
minotauri said:
I also have some other commands in my script to control adfree and setcpu
Click to expand...
Click to collapse
Off topic, I know but what are the commands you use for them?
This would help out a great deal!
UPDATE3:
Something went fishy. visionary.sh doesn't seem to want to work. This is what I have,
su
mount -o remount,rw /dev/block/mmcblk0p25 /system
mount -o remount,rw /dev/block/mmcblk0p25 /data
insmod /data/local/vision_oc.ko pll2_l_val=74
setprop qemu.sf.lcd_density 200
busybox killall system_server
Click to expand...
Click to collapse
Basically, it's everything in the OP with the addition of the oc command.
It was working just fine in the beginning but now it doesn't do the hot reboot unless I manually type killall system_server in adb shell or terminal emulator but oc goes through no problems either way...
I would like some clarification on something...
Is it mmcblk0p25 or mmcblkp025 cause 0p25 is what I did and it worked...
FINAL UPDATE:
So I'm really not sure what I did but with a lot of trail and error, I was able to come up with a working script...
su
insmod /data/local/vision_oc.ko pll2_l_val=74
mount -o remount,rw /dev/block/mmcblk0p25 /system
mount -o remount,rw /dev/block/mmcblk0p25 /data
setprop qemu.sf.lcd_density 200
busybox killall system_server
Click to expand...
Click to collapse
don't edit it in anyway or it won't work. I don't know why...
Sorry for floodin the thread with such a massive post but maybe it will help others. But I still want to know how to add adfree into visionary.sh so I don't have to start that up every time to0. If anyone want to throw me the command you used, I will guinea pig it into the script I just created and post it for the for everyone as well.
It's off topic but at least it will be out in the open cause I didn't see it anywhere. I know how to search...
Thank you all!

Launcherpro @ 200 looks amazing. Will keep it like that, it's like a whole new phone.
edit: thinking it's just a stock launcher problem with rendering, cause stock launcher looked like crap @ 200 too

Can someone post a couple of screen shots?

I'm using launcher pro @ 205. Looks amazing, everything aligned. I think you also need to play with your desktop columns and rows. I'm using 5x6 and manually resized widgets.

Thanks a ton to the OP. I absolutely LOVE high resolutions. Im using a density of 190 on ADW, and it looks fantastic! For some strange reason 200 and 210 were crashing the phone, 190 is running smoothly with no problems/glitches.
Sent from my overclocked T-Mobile G2 using XDA App.

Launcher Pro @ 190. This works great. Thank you.
Sent from my T-Mobile G2 using Tapatalk

I use launcher pro. but I know adw works too because I used that in the past with cyanogenmod on nexus one. you will want to change to column and row settings to full optimize the new screen density.
Sent from my T-Mobile G2 using XDA App

I can't get it to work I pushed the script and it was successful I can see it in terminal but it's not setting my density.

PlatinumMOTO said:
I can't get it to work I pushed the script and it was successful I can see it in terminal but it's not setting my density.
Click to expand...
Click to collapse
Reboot device and run visionary...

[GUIDE] Update CM without losing custom /system changes (ex Swype, keymap)

There's a really simple way to prevent CyanogenMod from overwriting your custom /system changes during an update. Create the file '/system/etc/custom_backup_list.txt' with a list of files within /system that you don't want to be overwritten.
For example, to prevent CM from wiping out Swype, open adb shell and type this:
Code:
mount -o remount,rw /system
cd /system/etc
echo lib/libSwypeCore.so >custom_backup_list.txt
echo app/Swype.apk >>custom_backup_list.txt
cd /
mount -o remount,ro /system
If you use teferi's custom keymap, do this:
Code:
mount -o remount,rw /system
cd /system/etc
echo lib/libSwypeCore.so >custom_backup_list.txt
echo app/Swype.apk >>custom_backup_list.txt
echo usr/keylayout/vision-keypad.kl >>custom_backup_list.txt
echo usr/keychars/vision-keypad.kcm.bin >>custom_backup_list.txt
cd /
mount -o remount,ro /system
Then the next time you flash CM, your changes to /system will still be there. If you want to see why this works, take a look at /system/bin/backuptool.sh
Hope this helps

Thanks! This is great; now I can easily keep my Email.apk that doesn't require me to enter a alphanumeric password every time I want to use the phone.

CM probably needs to overwrite build.prop but I've been changing the LCD density in this file. Is there a way to use a seperate file to override the lcd density so that i can let CM overwrite build.prop but still maintain lcd density after a flash?

Whatever commands you put in /data/local/userinit.sh will run at boot. So in adb shell, type this for a density of 215:
Code:
cd /data/local
echo setprop qemu.sf.lcd_density 215 >userinit.sh

awesome! thank you!
Don't suppose you would know how to get the CM update to not install/auto delete after installation apks like ADWLauncher and wifi calling?

Thank you!
This may be the long lost solution to my Swype and Cyan Problems. The new Release Candidates are destroying my swype and not liking it's return after installing the new Cyan. So, if this can basically help me update without losing much, it's a god send. Especially the LCD density.
You're a genius.
Thank you.
Hmm, seems the issue is still persistent. Thanks though.

Should userinit.sh and custom_backup_list.txt survive the upgrade or should they both be included in the backup list file?
Sent from my HTC Vision using XDA App

If you look at the actual script, it seems that it ignores the backuptool if .installscript exists, and in practice, I've noticed that nothing gets saved when flashing via ROM Manager. Is this, in fact, what's happening, and is there a way around it?

sundar2012 said:
awesome! thank you!
Don't suppose you would know how to get the CM update to not install/auto delete after installation apks like ADWLauncher and wifi calling?
Click to expand...
Click to collapse
You can put the following in /data/local/userinit.sh:
mount -o rw,remount /system
for apk in ADWLauncher.apk MS-HTCVISION-KNT20-02.apk
do
rm -f /system/app/$apk
done
for package in com.android.launcher
do
pm uninstall $package
done
mount -o ro,remount /system
exit 0
Click to expand...
Click to collapse
I haven't tried this for removing the Wifi Calling app, so ymmv. I remove a much larger set of apps myself (facebook, email, live wallpapers, amazon mp3 store, DSPManager, FileManager, Browser). http://wiki.cyanogenmod.com/index.php?title=Barebones has a list of apps that can be removed safely.

@cparekh -- what e-mail app is that? Or did you just use the pre-OTA's Email.apk app?

Rc4 has the trackpad wake fm radio and speaker led fixed its workng very smooth better than rc3
Sent from my HTC Vision using XDA App

sundar2012 said:
awesome! thank you!
Don't suppose you would know how to get the CM update to not install/auto delete after installation apks like ADWLauncher and wifi calling?
Click to expand...
Click to collapse
Just delete them from the cmupdate.zip before flashing. Cwm recovery doesn't require sig so u don't have to worry about resigning it.
OP: nice find, I'm sure ill use it at some point.

This is driving me crazy because I know I have used this command before but i cannot get it to work now... What is the deal?
Code:
$ mount -o remount,rw /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Rooted using gfree on this phone. On my previous phone I used wpthis and did not have a problem. Anyone know what I need to do to mount rw?

cparekh said:
Thanks! This is great; now I can easily keep my Email.apk that doesn't require me to enter a alphanumeric password every time I want to use the phone.
Click to expand...
Click to collapse
I need that apk
Sent from my HTC Vision using XDA App

Used this method to when going from stock to CM 6.1.1 and could not get it to work. I had to push/install manually from ADB.
Anyone had any luck? I did what the OP said then flashed. Was I supposed to do anything after flashing wiping and then flashing (CM & gapps)?

rraxda said:
This is driving me crazy because I know I have used this command before but i cannot get it to work now... What is the deal?
Code:
$ mount -o remount,rw /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Rooted using gfree on this phone. On my previous phone I used wpthis and did not have a problem. Anyone know what I need to do to mount rw?
Click to expand...
Click to collapse
Make sure you have root in the shell by typing su.

cparekh said:
Thanks! This is great; now I can easily keep my Email.apk that doesn't require me to enter a alphanumeric password every time I want to use the phone.
Click to expand...
Click to collapse
IConrad01 said:
@cparekh -- what e-mail app is that? Or did you just use the pre-OTA's Email.apk app?
Click to expand...
Click to collapse
chubb16 said:
I need that apk
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I am also interested in that apk

How can I backup progress on Angry Birds? Drives me nuts starting back over when I reflash CM

Titanium backup. You can use it to restore the app and the data. Usually i just restore the data to a fresh install.

JM6 & LCD Density

Hi there,
anyone could confirm?
Tab fw JM6 rooted ok with SuperOneClick
If I try to change LCD density with LCD Density Changer, nothing happens, it doesn't work
Same issue with Spare Parts, the program starts but then force close
Is there any other sw out there to change LCD density that works with JM6?
thanks

It's because BusyBox isn't installed. Go to LCD Density - Settings - Select make LCD my system density. As soon as you tick the box, it will say Cannot complete without busybox and will direct you to the market.
Download Busybox and all root apps will work.
Unlike Z4root, SuperOneClick doesn't install busybox, you need to do it manually.

great, thanks!

Or alternatively you can edit the build.prop and select the density you want in there, without adding any 3rd party programs.

I've set lcd density to 180
I've also installed LauncherPro with all widgets
The People widget is very big, is there any chance to resize it or put more than one widget in the same page (ex. People and Facebook widget)

spanky said:
I've set lcd density to 180
I've also installed LauncherPro with all widgets
The People widget is very big, is there any chance to resize it or put more than one widget in the same page (ex. People and Facebook widget)
Click to expand...
Click to collapse
Launcher pro paid version (sounds like you have it) has the ability to resize the widgets. Click and hold it in position, as if you are moving it, then release and you should be given the option to resize. Not sure how well it will work with changes to LCD density though.

bisto321 said:
Launcher pro paid version (sounds like you have it) has the ability to resize the widgets. Click and hold it in position, as if you are moving it, then release and you should be given the option to resize. Not sure how well it will work with changes to LCD density though.
Click to expand...
Click to collapse
Some widgets react OK to being sized differently than their expected size, but in my experience most get fairly mangled. What I think you actually need is to increase the number of rows and columns on your desktop to accommodate the increased screen real estate. You will need to switch to Launcher Pro or ADW though. I'm running a density of 200, with 6 rows and 7 columns which works well. A lot of the Samsung widgets seem to come in at 3 rows wide, which means that with a 6 row desktop you can now put 2 of them side by side.

I'm using ADW.Launcher with 200 instead of 240 LCD density, it works beautifully well in both portrait and landscape orientations !
Sent from my GT-P1000 using XDA App

Never had any issuewith widgets not working after changing the density, especially LPP widgets. They worked perfectly at 200 on the Tab and my Desire
Sent from my GT-P1000 using XDA App

If I change it to anything below 240 and open the stock email app, I get a little gap in the bottom when its in landscape. That's the only reason I don't use it
Sent from my GT-P1000 using Tapatalk

ayman07 said:
If I change it to anything below 240 and open the stock email app, I get a little gap in the bottom when its in landscape. That's the only reason I don't use it
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Agree that's a pitty, but then again I'm pleased to notice that most Galaxy Tab apps works without to much scaling problems on all densities. That's a big difference with the Galaxy S phone variants. On the Galaxy S variants most Samsung apps get all f'ed up with a different density.
I hope Google will support variable densities in the upcoming Android versions.

While a friend was using my tab, they changed the density to 100 (Thanks!). This caused my tab to reboot constantly and I cannot keep it on long enough to change LCD Density back.
Can anyone give me the files need to push from adb to change my density back to normal? Is it build.prop or something like that?
EDIT: I managed to adb pull my build.prop and edit it, but when I try to push it back I get permission denied.
when trying to mount with adb shell using mount /system -o rw,remount I get a usage error.

ninja4hire said:
While a friend was using my tab, they changed the density to 100 (Thanks!). This caused my tab to reboot constantly and I cannot keep it on long enough to change LCD Density back.
Can anyone give me the files need to push from adb to change my density back to normal? Is it build.prop or something like that?
EDIT: I managed to adb pull my build.prop and edit it, but when I try to push it back I get permission denied.
when trying to mount with adb shell using mount /system -o rw,remount I get a usage error.
Click to expand...
Click to collapse
Not sure why your remount isn't working assuming you have root permissions. I presume you've typed something like this?
Code:
# su
# mount -o remount,ro -t rfs /dev/block/stl9 /system
(apologies if I'm teaching you to suck eggs), or are you trying to do it directly via adb? If so then you could always copy the build.prop file from /system to something writeable like /mnt/sdcard - edit it (or pull it with adb and edit it) then remount /system as rw and copy it back. Lots of ways really.
An alternative which I often use when not near a computer is to just edit the file using Root Explorer - a very useful tool though may not be an option for you right now if you can't actually launch the device . btw - I had issues with LCD Density app after the flash of the latest EU JM6 FW and found the manual edit was the only way it would persist over reboots. Not sure if that's just local to me as no-one else seems to have issues, but something to bear in mind if it happens to anyone else.

paulshields said:
Not sure why your remount isn't working assuming you have root permissions. I presume you've typed something like this?
Code:
# su
# mount -o remount,ro -t rfs /dev/block/stl9 /system
(apologies if I'm teaching you to suck eggs), or are you trying to do it directly via adb? If so then you could always copy the build.prop file from /system to something writeable like /mnt/sdcard - edit it (or pull it with adb and edit it) then remount /system as rw and copy it back. Lots of ways really.
An alternative which I often use when not near a computer is to just edit the file using Root Explorer - a very useful tool though may not be an option for you right now if you can't actually launch the device . btw - I had issues with LCD Density app after the flash of the latest EU JM6 FW and found the manual edit was the only way it would persist over reboots. Not sure if that's just local to me as no-one else seems to have issues, but something to bear in mind if it happens to anyone else.
Click to expand...
Click to collapse
yeah the problem goes deeper. So I figured out that my tab is no longer rooted, and I can't root it again because I cannot put it back into debug mode. The system restarts itself before I can get to that screen.
I managed to adb pull, but I can't push back because I cannot gain permission. This may be the second tab I return for a new one.

ninja4hire said:
yeah the problem goes deeper. So I figured out that my tab is no longer rooted, and I can't root it again because I cannot put it back into debug mode. The system restarts itself before I can get to that screen.
I managed to adb pull, but I can't push back because I cannot gain permission. This may be the second tab I return for a new one.
Click to expand...
Click to collapse
Are you able to launch an app before your tab reboots?

unfortuately not really. I have been able to get to the launcher menu for a second, but then it reboots.

ninja4hire said:
yeah the problem goes deeper. So I figured out that my tab is no longer rooted, and I can't root it again because I cannot put it back into debug mode. The system restarts itself before I can get to that screen.
I managed to adb pull, but I can't push back because I cannot gain permission. This may be the second tab I return for a new one.
Click to expand...
Click to collapse
If you can get an adb pull then you should be able to run a root script. There is a script posted in this section for installing clockworkmod via a Windows bat file or a Linux/OSX shell script. I personally had issues with the recovery part of the script and would not recommend running the whole process, but the bits that do the rooting worked well for me. It was simply a case of removing the section that added the recovery files and then it rooted fine. You could try that. Edit the run.sh or run.bat file and remove the section that pushes the recovery files. For run.sh you'd delete
Code:
if [ "$buildid" == "FROYO" ]; then
echo Push clockworkmod redirector files to device
echo
$adb push bin /system/bin/
echo Set permissions on clockworkmod redirector files
$adb shell chmod 755 /system/bin/recovery
$adb shell chmod 755 /system/bin/recoveryfiles
$adb shell chmod 755 /system/bin/recoveryfiles/*
$adb shell chmod 755 /system/bin/recoveryres
$adb shell chmod 755 /system/bin/recoveryres/*
echo
fi
or for run.bat remove
Code:
IF "%buildid%"=="FROYO" (
echo Push clockworkmod redirector files to phone
echo.
adb push bin /system/bin/
echo Set permissions on clockworkmod redirector files
adb shell chmod 755 /system/bin/recovery
adb shell chmod 755 /system/bin/recoveryfiles
adb shell chmod 755 /system/bin/recoveryfiles/*
adb shell chmod 755 /system/bin/recoveryres
adb shell chmod 755 /system/bin/recoveryres/*
echo.
)
Your mileage may vary and I take no responsibility etc etc (I've only tested the Mac/Linux script and not the Windows batch file), but may be worth a punt before you look at returning it.

ninja4hire said:
unfortuately not really. I have been able to get to the launcher menu for a second, but then it reboots.
Click to expand...
Click to collapse
****, I know the problem. That's why I advice users in the help (i'm the developer of LCD Density Changer) to first do a preview before changing the system density. I used to have a so called boot monitor exactly for these problems.
I will put up an extra warning in the app or maybe force a preview before users can safe the density. Anyway, sorry for the trouble.
But why don't you flash some new firmware with odin or with kies?

Thanks paulshields, I'll try what you said and post my results.
appelflap said:
****, I know the problem. That's why I advice users in the help (i'm the developer of LCD Density Changer) to first do a preview before changing the system density. I used to have a so called boot monitor exactly for these problems.
I will put up an extra warning in the app or maybe force a preview before users can safe the density. Anyway, sorry for the trouble.
But why don't you flash some new firmware with odin or with kies?
Click to expand...
Click to collapse
Unfortunately I am using the VZW tab and there is no firmware yet. If all else fails I can wait, for something to come out for my the my tab. Also don't worry I am not blaming you or anyone for that matter. Hopefully I get this fixed!

The script doesn't seem to be working. I think it's because I'm not in debug mode (which I can't get to). Thanks anyway.

Screen calibration config

I'd like to know where are stored the parameters of the screen calibration.
I ask this because at every reboot they reset to factory default so I want to mod it directly.
Kisses to all

seems to be stored in
Code:
/data/data/org.isageek.dasbrennen.CalibrateScreen/databases/calvalues
which is a sqlite database (which I know nothing about!)
You could try making a copy of it before and after rebooting and see if it changes (binary diff). If it does, maybe you could replace it on every boot in your userinit .sh
If not, maybe the CalibrateScreen app just needs to be started to load the custom values, but you could probably do that on startup too.

mmec2 said:
seems to be stored in
Code:
/data/data/org.isageek.dasbrennen.CalibrateScreen/databases/calvalues
which is a sqlite database (which I know nothing about!)
You could try making a copy of it before and after rebooting and see if it changes (binary diff). If it does, maybe you could replace it on every boot in your userinit .sh
If not, maybe the CalibrateScreen app just needs to be started to load the custom values, but you could probably do that on startup too.
Click to expand...
Click to collapse
Thank you very much for your reply, however I was trying to figure out the place where these values are stored into android system and not into the app... because I think that the app it's only a bridge for the real calibration of the system... or maybe I'm wrong?

TuoNonno said:
Thank you very much for your reply, however I was trying to figure out the place where these values are stored into android system and not into the app... because I think that the app it's only a bridge for the real calibration of the system... or maybe I'm wrong?
Click to expand...
Click to collapse
For some reason, I assumed it was a built in part of the system, but it's not!
Anyway, your question has got me interested now, so I took CalibrateScreen.apk from Scoot's CM6.1 build, decompiled the apk with apktool and searched the source for "write"
I believe the values you are looking for are
Code:
/sys/class/vogue_ts/xmin
/sys/class/vogue_ts/xmax
/sys/class/vogue_ts/ymin
/sys/class/vogue_ts/ymax
(found in CalibrateScreen/smali/org/isageek/dasbrennen/CalibrateScreen/Calibrator.smali)
so you could just add
Code:
echo NUMBER > /sys/class/vogue_ts/xmin
etc. etc.... to your userinit.sh

mmec2 said:
For some reason, I assumed it was a built in part of the system, but it's not!
Anyway, your question has got me interested now, so I took CalibrateScreen.apk from Scoot's CM6.1 build, decompiled the apk with apktool and searched the source for "write"
I believe the values you are looking for are
Code:
/sys/class/vogue_ts/xmin
/sys/class/vogue_ts/xmax
/sys/class/vogue_ts/ymin
/sys/class/vogue_ts/ymax
(found in CalibrateScreen/smali/org/isageek/dasbrennen/CalibrateScreen/Calibrator.smali)
so you could just add
Code:
echo NUMBER > /sys/class/vogue_ts/xmin
etc. etc.... to your userinit.sh
Click to expand...
Click to collapse
you are the man! You solved a issue that was drilling me since months!
Many many thanks!

It wooooooooooooooorks! HUAHAHAHAHA!
step by step:
1) calibrated screen with screencalibration app.
2) copied
Code:
/sys/class/vogue_ts/xmin
/sys/class/vogue_ts/xmax
/sys/class/vogue_ts/ymin
/sys/class/vogue_ts/ymax
/system/bin/userinit.sh
to sdcard root
3) edited userinit.sh with notepad++ like that:
Code:
#!/system/bin/sh
#
# Fix su so that we use the one supplied with the build. This allows the Superuser Permissions app to do it's stuff
#
/bin/umount /bin/su
/bin/umount /system/bin/su
busybox mount -o rw,remount /system
echo 708 > /sys/class/vogue_ts/xmin
echo 3660 > /sys/class/vogue_ts/xmax
echo 257 > /sys/class/vogue_ts/ymin
echo 3551 > /sys/class/vogue_ts/ymax
chmod 04777 /system/bin/su
chmod 04777 /sys/class/vogue_ts
busybox mount -o ro,remount /system
/bin/mount --bind /system/bin/su /bin/su
4) created a androidupdate.tar file with 7zip containing system/bin/userinit.sh
5) dpad during startup, installed androidupdate and fixed permissions
Happy ^^

could you upload the standard calibrate file to me ?
I dont understand why my kaiser seem to be crazy because touch screen seem to be rotate 90 degrees. it mean .... the app button ( in the center of the bottom screen ) will become middle of the left screen. I mean if I want to touch app button, I must touch the middle left of the screen
I cant do anything with this !!!
Fuk my kaiser >.< sorry for my bad emotion !!!

dai_thang said:
could you upload the standard calibrate file to me ?
I dont understand why my kaiser seem to be crazy because touch screen seem to be rotate 90 degrees. it mean .... the app button ( in the center of the bottom screen ) will become middle of the left screen. I mean if I want to touch app button, I must touch the middle left of the screen
I cant do anything with this !!!
Fuk my kaiser >.< sorry for my bad emotion !!!
Click to expand...
Click to collapse
Sure, here it is, install it like a normal update from dpad menu on boot (remember to fix permission after the install)

thanks for your quick response ! however, my fukin kaiser didnot change in positive way. Comparing to my friend device, I realize that different Kaiser has Different compatibility. I try 3 panel mode but the screen did not work well ! How can I mod a unique sceen calibration for me ? I mean rotate 90 degree counter clockwise T_T ?
I'm waiting for for help, TuoNonno, my own hero !

dai_thang said:
thanks for your quick response ! however, my fukin kaiser didnot change in positive way. Comparing to my friend device, I realize that different Kaiser has Different compatibility. I try 3 panel mode but the screen did not work well ! How can I mod a unique sceen calibration for me ? I mean rotate 90 degree counter clockwise T_T ?
I'm waiting for for help, TuoNonno, my own hero !
Click to expand...
Click to collapse
LOL...
have you tried to follow the instruction that I posted above to extract the correct values for your touch? remember also to do the calibration with the sliding keyboard closed!

TuoNonno said:
It wooooooooooooooorks! HUAHAHAHAHA!
step by step:
1) calibrated screen with screencalibration app.
2) copied
Code:
/sys/class/vogue_ts/xmin
/sys/class/vogue_ts/xmax
/sys/class/vogue_ts/ymin
/sys/class/vogue_ts/ymax
/system/bin/userinit.sh
to sdcard root
Happy ^^
Click to expand...
Click to collapse
How can I generate this information ???
What did U mean .... by saying "copied" ?

Those are the steps I did, so I wrote "copied".
Just follow those steps, nothing more to do
Basically, you need to run the calibration screen app, then you copy the 5 files in "/sys/class/vogue_ts" to your sd card root in order to be more handy and do those steps.

dai_thang said:
thanks for your quick response ! however, my fukin kaiser didnot change in positive way. Comparing to my friend device, I realize that different Kaiser has Different compatibility. I try 3 panel mode but the screen did not work well ! How can I mod a unique sceen calibration for me ? I mean rotate 90 degree counter clockwise T_T ?
I'm waiting for for help, TuoNonno, my own hero !
Click to expand...
Click to collapse
actually i cant speak english properly. but ill try to answer ur questions.
i have a stupid solution for the problem of calibrating the screen. i use Incubus26Jc's Super Froyo 2.2 [Deodexed] [RLS15] on my kaiser.
i do the screen calibration once a week. for the screen calibration on my android, will appear a black screen with two red dots on the screen to the left top, and bottom right. all i have to do is touch one red spot twice, until the recalibration text does not appear. (or other writings that tell you to re-calibration).
finished ...!!! what i have to do is press the "OK" to apply. i hope now ur screen is not mad anymore.

TuoNonno said:
It wooooooooooooooorks! HUAHAHAHAHA!
step by step:
1) calibrated screen with screencalibration app.
2) copied
Code:
/sys/class/vogue_ts/xmin
/sys/class/vogue_ts/xmax
/sys/class/vogue_ts/ymin
/sys/class/vogue_ts/ymax
/system/bin/userinit.sh
to sdcard root
3) edited userinit.sh with notepad++ like that:
Code:
#!/system/bin/sh
#
# Fix su so that we use the one supplied with the build. This allows the Superuser Permissions app to do it's stuff
#
/bin/umount /bin/su
/bin/umount /system/bin/su
busybox mount -o rw,remount /system
echo 708 > /sys/class/vogue_ts/xmin
echo 3660 > /sys/class/vogue_ts/xmax
echo 257 > /sys/class/vogue_ts/ymin
echo 3551 > /sys/class/vogue_ts/ymax
chmod 04777 /system/bin/su
chmod 04777 /sys/class/vogue_ts
busybox mount -o ro,remount /system
/bin/mount --bind /system/bin/su /bin/su
4) created a androidupdate.tar file with 7zip containing system/bin/userinit.sh
5) dpad during startup, installed androidupdate and fixed permissions
Happy ^^
Click to expand...
Click to collapse
Awesome! my Kaiser 100 now holds screen calibration, even after a dead battery or a power cycle. Really enjoying Dark_Prince's Froyo 2.2.2 on this AT&T tilt. But the method of creating a androidupdate.tar did not work for me. The update reported it worked as a success, then a fix permission seemed to finish, but still no calibration save.
This is what worked on my device:
As TuoNonno said I copied the four files containing the needed values, and in the end I went to market and got a file manager that had root permissions and edited ' /system/bin/userinit.sh ' to reflect the values those four files held.
my userinit.sh on my device now looks like this:
Code:
/bin/umount /bin/su
/bin/umount /system/bin/su
busybox mount -o rw,remount /system
echo 1345 > /sys/class/vogue_ts/xmin
echo 3387 > /sys/class/vogue_ts/xmax
echo 334 > /sys/class/vogue_ts/ymin
echo 3615 > /sys/class/vogue_ts/ymax
chmod 04777 /system/bin/su
chmod 04777 /sys/class/vogue_ts
busybox mount -o ro,remount /system
/bin/mount --bind /system/bin/su /bin/su
Not sure if that is the 'proper' way to fix, but it surely seems to work - I no longer have to use the physical buttons to navigate to and open the screen calibrate app.
Thank you to all that had a part in developing this fix. The knowledge of the gurus on this forum is outstanding!

[Q] LED: Making hardlink to /green/brightness for /blue

I'd say this shouldn't be too difficult, but I can't get it done.
In order to get a white notification LED instead of green (white = blue + green), I want to make /sys/devices/platform/leds-microp/leds/blue/brightness to be a hardlink to /sys/devices/platform/leds-microp/leds/green/brightness. Should be enough to fire up the blue LED whenever the green one is on.
Problem here is that I can't seem to get the right permissions (/blue folder had 777).
1) on "ln /sys/devices/platform/leds-microp/leds/green/brightness /sys/devices/platform/leds-microp/leds/blue/brightness" adb returns "File exists" but I can't remove it (Operation not permitted, while permissions are 666).
2) but on "ln /sys/devices/platform/leds-microp/leds/green/brightness /sys/devices/platform/leds-microp/leds/blue/brightness.test" adb returns "No such file or directory"
3) trying to remove /sys/devices/platform/leds-microp/leds/blue/brightness returns "Operation not permitted"
What other than "adb connect" & "adb remount" & "adb shell" & "su" can I do?

Are you in recovery?
What about chown?
Sent from my HTC Desire using xda premium

Hey, thanks for replying.
Chown: currently the files have owner 1000 and group 1000, but changing them to 0 or 1 doesn't do anything for the problems described above.
/sys/devices/platform/leds-microp does not exist when in Recovery mode. My original idea was to add some lines in a file in system/etc/init.d, just like the LED fix for LEDmeKnow (quoted below):
Code:
#!/system/bin/sh
busybox chmod 666 /sys/devices/platform/leds-microp/leds/amber/blink;
busybox chmod 666 /sys/devices/platform/leds-microp/leds/amber/brightness;
busybox chmod 666 /sys/devices/platform/leds-microp/leds/blue/brightness;
busybox chmod 666 /sys/devices/platform/leds-microp/leds/green/blink;
busybox chmod 666 /sys/devices/platform/leds-microp/leds/green/brightness;
I wanted to add the following, but this doesn't work, probably for the same reason that I get those error messages by adb:
Code:
busybox chmod 777 /sys/devices/platform/leds-microp/leds/blue;
busybox rm /sys/devices/platform/leds-microp/leds/blue/blink;
busybox rm /sys/devices/platform/leds-microp/leds/blue/brightness;
busybox ln /sys/devices/platform/leds-microp/leds/green/blink /sys/devices/platform/leds-microp/leds/blue/blink;
busybox ln /sys/devices/platform/leds-microp/leds/green/brightness /sys/devices/platform/leds-microp/leds/blue/brightness;

What ROM are you on?
I don't have:
/sys/devices/platform/leds-microp/
either.
Edit.
Mine is /sys/devices/virtual/leds/lcd-backlight/subsystem

I've never seen a ROM without it. It's not there when in Recovery, but it is when booted normally. That's why I wanted to create the hardlink via a busybox script in /etc/init.d
Currently using Tabasco's Silky ROM 2.1, so a Sense (v1) ROM, but have seen it in every GB ROM I've tried (LeeDroid, InsertCoin, AceS... haven't checked CyanogenMOD or yours, though, so I cannot rule out it's a Sense thing, but I really think it's just there, but not in Recovery mode, as the files are created on boot-up).
By the way, it would make more sense if the /sys/devices/virtual/leds/lcd-backlight/subsystem is for the backlight of the screen instead of the notification LEDs I'm talking about.

Modest bump

rootSU said:
What ROM are you on?
I don't have:
/sys/devices/platform/leds-microp/
either.
Edit.
Mine is /sys/devices/virtual/leds/lcd-backlight/subsystem
Click to expand...
Click to collapse
ltGuillaume said:
I've never seen a ROM without it. It's not there when in Recovery, but it is when booted normally. That's why I wanted to create the hardlink via a busybox script in /etc/init.d
Currently using Tabasco's Silky ROM 2.1, so a Sense (v1) ROM, but have seen it in every GB ROM I've tried (LeeDroid, InsertCoin, AceS... haven't checked CyanogenMOD or yours, though, so I cannot rule out it's a Sense thing, but I really think it's just there, but not in Recovery mode, as the files are created on boot-up).
By the way, it would make more sense if the /sys/devices/virtual/leds/lcd-backlight/subsystem is for the backlight of the screen instead of the notification LEDs I'm talking about.
Click to expand...
Click to collapse
not a major contributing factor but: maybe it's because you're using AOSP and he's using all Sense ROM's, but even then I wouldn't see why it would be :/
I'll just shut up and go sit in my dark corner now lol

That's what I meant with that I can't rule out it's a Sense thing, but still, I don't think so.