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...

[Q] ADB Push/Install Cyanogenmod 6 settings.apk

Would this work? Would it give us the ability to change the clock and notification text to white so that we can use black metamorph themes?

SuperDave81 said:
Would this work? Would it give us the ability to change the clock and notification text to white so that we can use black metamorph themes?
Click to expand...
Click to collapse
try it. i know the CMwallpaper app works.
if some1 posts the apk, i'll try it. feeling lazy at 2am. can ya blame me?

This is from 6.0.0 for N1

SuperDave81 said:
This is from 6.0.0 for N1
Click to expand...
Click to collapse
cant install via app manager. i dunno if it would work thru a adb push.

adb install fails: file already exists. Do I need to chmod the existing file in a shell first?

SuperDave81 said:
adb install fails: file already exists. Do I need to chmod the existing file in a shell first?
Click to expand...
Click to collapse
could work.

okay, I've mounted system as rw and chmodded Settings.apk as 04775, but I keep getting permission denied. How do I kill running apps in adb shell?

doubt you'll be able to do the customizations but you can use the stop and start commands in adb shell.

Tried it, nothing worked after issuing the stop command in adb shell. Had to battery pull.
Sent from my T-Mobile G2 using XDA App

adb shell
$ su
# stop
# mount -o remount,rw /dev/block/mmcblk0p25 /system
# mv /system/app/settings.apk /system/app/settings.bak
# cp /sdcard/settings.apk /system/app
# start
assuming you've put the new settings.apk in your /sdcard folder.

That worked, it did push the new settings.apk. It even changed the icon when I click menu from the home screen. But when I click on settings, nothing happened . Oh well, Enomthr updated his rom so I'm happy again!

I'm not positive but I'm pretty sure the cyan settings are involved with the custom framework on cyan roms. Because the xml in order to edit things such as clock color are located in the framework-res.apk. if some of you guys are new to android or have never reallly messed areoud with apks or ne thing here's something fun to try while waiting for root. Take the framework res apk from a rom and put it on ur computer and rename it to .zip instead of .apk. and you can see you things work visually wise on your phone. This will help you a ton if you ever want to get into themeing to make custom themes when we have root.

I have actually the same question. Does it work if a push a Setting.apk into my ROM, or there are something related in framework?

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.

[ICS][Deodex] stock system apps and framework [2.007.04_COM_GEN1]

This will have to be "flashed" through adb and your a100 needs to be on the newest update.
[STOCK ROM] Official Packages It's the first link on that post. We can thank vache for that.
All bloatware is still included, also acer's MusicA.odex did not deodex and is included.
Code:
$ adb shell
$ su
# stop
# mount -wo remount /system
# rm /system/app/*
# rm /system/framework/*
# cd /mnt/external_sd/path_to_tar
# busybox tar xvf A100_2.007.04_COM_GEN1_deodex.tar -C /
Permissions should be fine as it is in tar format otherwise:
Code:
# chmod 644 /system/app/*
# chmod 644 /system/framework/*
dalvik cache will be about 20MB larger and it should be wiped
Code:
# busybox rm /data/dalvik-cache/*
# exit
$ exit
$ adb reboot
It will take a bit longer on the first boot while the cache rebuilds
For anyone that doesn't know deodexing is only useful for creating a ROM/theme.
After any theming of the apps permissions will have to be set and keep the official stock ROM in hand in case of a bootloop.
Code:
# chmod 644 /system/app/apk_package
or
# chmod 644 /system/framework/jar_package
I've been running this for a few days and have had no issues at all.
Using this method we can start building some ROMS. I would suggest using tar and maybe include a small script to flash it.
Let me know if anyone wants a full ROM package as this is only the apps and framework.
A100_2.007.04_COM_GEN1_deodex.tar - 191.05 MB
[edit] As it turns out MusicA does not work at all, it doesn't even show up in the app drawer. Some guy named Jeff Lee compiled some of the framework wrong. com.acer.android.clearfilib_tablet.jar/C:/Users/Jeff_lee/Desktop/_acer/Jeff/clearfilib_tablet.java will not work. It should be a classes.dex file in the jar archive. Oh well it looks like its fixed in ICS.
02/22/12
Here's Deodex ICS, everything deodexed without issues. But without root this will be useless. [edit] We now have root so this will be very useful
A100_0.002.00_WW_GEN1_deodex.tar - 206.06 MB

Pending...

I was meaning to do this for a few days now and I am glad to see it works.
Did you do some more testing to see how it is, performance-wise?

Icewyng said:
I was meaning to do this for a few days now and I am glad to see it works.
Did you do some more testing to see how it is, performance-wise?
Click to expand...
Click to collapse
Nothing more than opening the stock apps and using it as I normally do. Just ran linpack, it got the same result as before deodexing. It really shouldn't run any better or worse. Though odex is supposed to be faster than using the dex format. It's also zipaligned so that can also speed things up a bit to compensate.

eww245 said:
This will have to be "flashed" through adb and your a100 needs to be on the newest update.
[STOCK ROM] Official Packages It's the first link on that post. We can thank vache for that.
All bloatware is still included, also acer's MusicA.odex did not deodex and is included.
Code:
$ adb shell
$ su
# stop
# mount -wo remount /system
# rm /system/app/*
# rm /system/framework/*
# cd /mnt/external_sd/path_to_tar
# busybox tar xvf A100_2.007.04_COM_GEN1_deodex.tar -C /
Permissions should be fine as it is in tar format otherwise:
Code:
# chmod 644 /system/app/*
# chmod 644 /system/framework/*
dalvik cache will be about 20MB larger and it should be wiped
Code:
# busybox rm /data/dalvik-cache/*
# exit
$ exit
$ adb reboot
It will take a bit longer on the first boot while the cache rebuilds
For anyone that doesn't know deodexing is only useful for creating a ROM/theme.
After any theming of the apps permissions will have to be set and keep the official stock ROM in hand in case of a bootloop.
Code:
# chmod 644 /system/app/apk_package
or
# chmod 644 /system/framework/jar_package
I've been running this for a few days and have had no issues at all.
Using this method we can start building some ROMS. I would suggest using tar and maybe include a small script to flash it.
Let me know if anyone wants a full ROM package as this is only the apps and framework.
A100_2.007.04_COM_GEN1_deodex.tar - 191.05 MB
Click to expand...
Click to collapse
Great work eww245! I am definately interested.....just noticed your thread today.

Is there a way to do this on the tablet itself?? Thanks for the work....
Sent from my ADR6400L using xda premium

BrothaJINC said:
Is there a way to do this on the tablet itself?? Thanks for the work....
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Probably but be prepared for a lot of force closings. I suggest you immediately end it with reboot ex: # busybox tar x.... ; reboot
and don't use stop, the screen will go black. Good Luck

So just put in the code above on a terminal then reboot. And have the file on the sdcard
Sent from my ADR6400L using xda premium

BrothaJINC said:
So just put in the code above on a terminal then reboot. And have the file on the sdcard
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Yep, not sure if your on ICS but I haven't tested it yet.

No I'm trying to get to ics... I'm on gen2.... Will post back how it went.... Thanks for the help...
Sent from my ADR6400L using xda premium

Using this method we can start building some ROMS. I would suggest using tar and maybe include a small script to flash it.
Let me know if anyone wants a full ROM package as this is only the apps and framework.
A100_2.007.04_COM_GEN1_deodex.tar - 191.05 MB
hello eww245, i am not familiar with this and at the risk of sounding like a total newb, how would one go about this....what i mean is could you just give the basics to get me started....how would we get past the acer signature and checksums? thanks so much for your hard work

oneovakindoldys2 said:
Using this method we can start building some ROMS. I would suggest using tar and maybe include a small script to flash it.
Let me know if anyone wants a full ROM package as this is only the apps and framework.
A100_2.007.04_COM_GEN1_deodex.tar - 191.05 MB
hello eww245, i am not familiar with this and at the risk of sounding like a total newb, how would one go about this....what i mean is could you just give the basics to get me started....how would we get past the acer signature and checksums? thanks so much for your hard work
Click to expand...
Click to collapse
As far as signatures, all the apks and jars are signed but unless you sign them with all the same keys, files will have to be added / replaced in the archive. They are just zip files.
One tool baksmalli code.google.com/p/smali/ allows the code to be extracted into smalli code, which is quite difficult to read. That's what I used to deodex the files, but something like adding a reboot menu to the long press power button is possible.
Another, ApkTool code.google.com/p/android-apktool/ Will decode all the xml files and extract the images. With that it's possible to change or add string values. Like new translation values or changing text that's already there.
The eaisest edit would be just replacing images. So using 7zip or if you use linux xarchiver works good. As I mentioned above if the apks/jars are unzipped and rezipped the signature changes. So the images will have to be replaced in the archive.
I haven't experiment much yet my self, I tried to change the autobacklight values without any effect, but I did manage to add a CRT power off effect to the framework-res.apk.
Good luck hopefully this helps.

eww245 said:
As far as signatures, all the apks and jars are signed but unless you sign them with all the same keys, files will have to be added / replaced in the archive. They are just zip files.
One tool baksmalli code.google.com/p/smali/ allows the code to be extracted into smalli code, which is quite difficult to read. That's what I used to deodex the files, but something like adding a reboot menu to the long press power button is possible.
Another, ApkTool code.google.com/p/android-apktool/ Will decode all the xml files and extract the images. With that it's possible to change or add string values. Like new translation values or changing text that's already there.
The eaisest edit would be just replacing images. So using 7zip or if you use linux xarchiver works good. As I mentioned above if the apks/jars are unzipped and rezipped the signature changes. So the images will have to be replaced in the archive.
I haven't experiment much yet my self, I tried to change the autobacklight values without any effect, but I did manage to add a CRT power off effect to the framework-res.apk.
Good luck hopefully this helps.
Click to expand...
Click to collapse
Thanks alot Eww, I will do some research on this and see what I can come up with. In the meantime, I have a question [mission actually...lol] for anyone that might have some knowledge. I have been working on cracking fastboot and nvflash on our a100 so we can flash custom roms. I have come to the conclusion that our fastboot/nvflash is locked/disabled in the default prop and init. I have been working on this in my spare time....anyway, this is the progress i have made so far ....i have extracted the leaked ics release, decompressed it, extracted the boot image, unpacked it and used split_boot to seperate the ramdisk from the kernel and made the changes that I thought were necessary. I then used mkboot and finally got it gzipped up without any errors. I now have an edited boot.img for the a100 that should enable fastboot operation, however I have no way to get it back on to the tablet.....tis is the dilemma! Any suggestions with merit will certainly be appreciated. thanks again

How do get cm7 to boot? i flashed it on safestrap 3.05 but all i get is black screen. also check y D3 rom Collection filled the best D3 roms https://www.mediafire.com/folder/b0gq735hrqxx6/Droid_3_ROMS

[Q] Accidentally modified Framework

Like a dummy I tried to rename framework-res while using my nexus so I could replace it with an edited one (deb rooted, stock 4.4.4 rom, franco -17 kernel)
Now Im trying to ADB in to rename the original file so it will boot again.
I'm connected to the nexus in ADB but when I try to pull or rename the file I always get some sort of error.
I was able to adb push a framwork file I downloaded on my computer but it still wouldnt boot. Im assuming it was bad.
Any help is much appreciated!
thanks!

Rhatfield25 said:
Like a dummy I tried to rename framework-res while using my nexus so I could replace it with an edited one (deb rooted, stock 4.4.4 rom, franco -17 kernel)
Now Im trying to ADB in to rename the original file so it will boot again.
I'm connected to the nexus in ADB but when I try to pull or rename the file I always get some sort of error.
I was able to adb push a framwork file I downloaded on my computer but it still wouldnt boot. Im assuming it was bad.
Any help is much appreciated!
thanks!
Click to expand...
Click to collapse
The reason it would not boot with the one you pushed to the device is probably because you have to set permissions correctly after the push. Framework res should probably be set to rw-r--r--
Run this after the push, or if the file is still on the phone, run it now.
Code:
adb shell
su
chmod 644 /system/framework/framework-res.apk

SwoRNLeaDejZ said:
The reason it would not boot with the one you pushed to the device is probably because you have to set permissions correctly after the push. Framework res should probably be set to rw-r--r--
Run this after the push, or if the file is still on the phone, run it now.
Code:
adb shell
su
chmod 644 /system/framework/framework-res.apk
Click to expand...
Click to collapse
I will give it a shot the second I get home! Thank you so much for the help. So by default files pushed to the system do not have full read and write permissions?
Thanks again!

Rhatfield25 said:
I will give it a shot the second I get home! Thank you so much for the help. So by default files pushed to the system do not have full read and write permissions?
Thanks again!
Click to expand...
Click to collapse
Yes, most of the time, pushed files will copy with bad permissions. Every time I've ever edited a system APK, I've had to subsequently set permissions before it would act correctly. Might not be 100% your issue, but it's definitely worth a shot.

SwoRNLeaDejZ said:
Yes, most of the time, pushed files will copy with bad permissions. Every time I've ever edited a system APK, I've had to subsequently set permissions before it would act correctly. Might not be 100% your issue, but it's definitely worth a shot.
Click to expand...
Click to collapse
Well now Ive run into a new problem. When I SU to get root access it tells me that /sbin/sh isnt found.
I rooted the n7 with cf autoroot.
this would be a whole lot easier if twrp would mount the tablet so I could just upload and flash a zip to update it.

Well I was able to sideload the boot animation herehttp://forum.xda-developers.com/showthread.php?t=2591471 just to confirm that sideload was working. I rebooted and it worked but still will not get past the boot animation.
The framework file simply needs to be put in /system right? so the command would look like
abd sideload framework-res.apk /system
Is that right?

Rhatfield25 said:
Well now Ive run into a new problem. When I SU to get root access it tells me that /sbin/sh isnt found.
I rooted the n7 with cf autoroot.
this would be a whole lot easier if twrp would mount the tablet so I could just upload and flash a zip to update it.
Click to expand...
Click to collapse
What about trying to use the terminal emulator in twrp?
Rhatfield25 said:
Well I was able to sideload the boot animation herehttp://forum.xda-developers.com/showthread.php?t=2591471 just to confirm that sideload was working. I rebooted and it worked but still will not get past the boot animation.
The framework file simply needs to be put in /system right? so the command would look like
abd sideload framework-res.apk /system
Is that right?
Click to expand...
Click to collapse
You need to fix the framework file before you can boot. Try running the permission command without su first.