Ok we all know we need to calibrate the battery after each ROM flash now me I am always thinking outside the box but sometimes can't answer my own questions. Battery bin file is deleted so another one can be generated but here is my question. Do one really good charge, delete file, drain and charge to 100% and now make a copy of the batterystats.bin file and if you ever flash a new Rom instead of repeating this process just reuse the file. Is this possible or should I stop thinking?..... Please only answer if you know for sure I can make guesses.
Sent from my Thunderbolt using XDA App
Related
Does anyone know if someone has created a deodex .zip file to flash via customer recovery?
For those that don't know, many of the apk files installed by an official rom will have a .odex file associated with them which slows down your phone considerably. These odex files interact with delvik cache and java VM and from what I understand wreak havoc on data access times and are largely uneccessary. Other dev platforms such as the droid x and evo have a .zip file that you can simply flash via recovery that will "deodex" your apps in system\apps folder. Basicially this zip will take your odex file and associated apk file and take the important information out of the odex and input it into the apk making just one streamlined faster file.... with all of your odex files gone, your phone will spend less time executing programs both for end user and core google apps and your phone will be way faster. Any idea if someone has developed this yet for the streak? Thanks
For others who, like me, didn't understand the question - read this.
But what I gathered from that wasn't that de-odexing speeds anything up, more that it makes it easier to make modifications.
Why are you posting this in more than one forum? This is the same as what you posted in the dev forum, right?
Sent from my Dell Streak using XDA App
alperin1 said:
Why are you posting this in more than one forum? This is the same as what you posted in the dev forum, right?
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
wasn't sure if anybody would follow what I am posting in the QA as most noobs are in here. Why do you care? I meant delete this one and go with the developer post anyway.
marvin02 said:
For others who, like me, didn't understand the question - read this.
But what I gathered from that wasn't that de-odexing speeds anything up, more that it makes it easier to make modifications.
Click to expand...
Click to collapse
Marvin my man.... deodexing more than doubles data access speeds for core google apps and makes the phone more snappy. Seen this performed on a droid x and an HTC evo... works wonders.
I just want to know if someone has developed a simple flashable .zip file that will deodex my system/app apk files so I can speed things up and modify my self. I don't care that dj steve's rom already has this done... I don't care for steves latest roms as they are very buggy on 3g, wifi, gps, notification bar hangs, drops data when wifi toggle is enacted, gmail won't sync... I got tired of messing with he streaddroid roms (for now) and went to stock 318 with just smokku's dj steve kernal mod which allows me to OC to 1.19ghz. I get 2000 quad out of that and I am happy, plus I get the added bonus of having a 99.9% stable rom. Can't wait to see what steve comes out with next. i always try his roms out first.
Thanks
You could probably copy you're system/app folder and write a simple batch script to use baksmali to deodex *.odex, use 7-zip command line to put the .dex file in the apk (I assume that is what has to happen), and then push that folder back to your phone with an adb push. I dont really want to try this because I'm on 319 and cant make a nandroid backup but since you can on 318 it never hurts to try.
Does anyone know if someone has created a deodex .zip file to flash via customer recovery?
For those that don't know, many of the apk files installed by an official rom will have a .odex file associated with them which slows down your phone considerably. These odex files interact with delvik cache and java VM and from what I understand wreak havoc on data access times and are largely uneccessary. Other dev platforms such as the droid x and evo have a .zip file that you can simply flash via recovery that will "deodex" your apps in system\apps folder. Basicially this zip will take your odex file and associated apk file and take the important information out of the odex and input it into the apk making just one streamlined faster file.... with all of your odex files gone, your phone will spend less time executing programs both for end user and core google apps and your phone will be way faster. Any idea if someone has developed this yet for the streak? Thanks
**EDIT**
I know this is a question but I thought it should go into development due to the potential of some of the dev's responding to this and posting useful developement info that we can try out and report back to the dev section. Plus, most of the trollers in Q&A probably don't know what this is or even care. Thanks
I am interested in this as well
Sent from my Dell Streak using Tapatalk
Steve's roms are pre-deodexed, just look under system/app, you can't find see any odex file, or simply perform a search on 'odex' in root explorer and the result should be none.
sharptv said:
Steve's roms are pre-deodexed, just look under system/app, you can't find see any odex file, or simply perform a search on 'odex' in root explorer and the result should be none.
Click to expand...
Click to collapse
good to know.
although if someone makes an app/file to do the job it will be handy in the future
Pleas do not post in Multiple forums about the same Topic
For the Atrix, what's the recommended way to disable the OEM AT&T boot animation?
And will this cause any problems - either with normal useage, or with future updates?
Rename the file extension from .zip to .backup. That will stop it from playing. I dont see why this would have a negative affect on your phone other than you will be missing a boot animation. If you ever want it back just rename the file extension back to .zip. But why not change it to something you like?
What it comes down to was that I didn't know anything about boot animations, and whether they were one of those things that would cause an OTA update to fail.
I have since learned more about how to adjust them. But there is still the question about whether it affects OTA updates.
Haphim said:
What it comes down to was that I didn't know anything about boot animations, and whether they were one of those things that would cause an OTA update to fail.
I have since learned more about how to adjust them. But there is still the question about whether it affects OTA updates.
Click to expand...
Click to collapse
Doubtful it would affect an ota, just keep a backup of the file incase you need it. However if you have the root access required to change the bootanimation and if you want to keep root access you should not accept an ota. When its time to update just come back to the forums.
Understood. Thanks.
WiredPirate said:
Doubtful it would affect an ota, just keep a backup of the file incase you need it. However if you have the root access required to change the bootanimation and if you want to keep root access you should not accept an ota. When its time to update just come back to the forums.
Click to expand...
Click to collapse
Great question, that animation was starting to bug me, especially cause start up is so long... ia this the same case for you guys?
Just to confirm, I would change bootanimation.zip to bootanimation.backup? Where ia this located exactly?
Thanks
Sent from my MB860 using XDA App
hluk said:
Great question, that animation was starting to bug me, especially cause start up is so long... ia this the same case for you guys?
Just to confirm, I would change bootanimation.zip to bootanimation.backup? Where ia this located exactly?
Thanks
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Correct. system/media
Here is a cool bootanimation modified for the atrix:
http://forum.xda-developers.com/showthread.php?t=1037561
Use Root Explorer or a similar file explorer to paste the bootanimation.zip in system/media after you rename the original.
I've been looking into how to remove some apks from /system/app/ in CWM-flashable zips to save myself some time when going back and forth between ROMs. I understand (I think..) that after the removal process, I will need to resign the zip using JesusFreke's testsign.jar, but I still have some questions that I couldn't find much information on.
1) What exactly does the signing process do, and why would a flash of an unsigned zip fail?
2) This may be related to Q1, and may be a silly question, but why does a zip not retain the original signing if you alter the contents of the package?
3) Would using JF's testsign.jar affect the integrity of the ROM in any way? (In other words, are there any differences between testsign.jar and the signing process used by the ROM dev?)
4) Besides resigning, is there anything I should be aware of or anything else I need to do before flashing the updated ROM?
I am entirely new to this so I apologize for my entirely noob-ish questions, but really would appreciate any help! Thanks in advance.
Just open up the zip and delete the apps you don't want, add the apps you do want, and flash.
No need to do anything else.
harlenm said:
Just open up the zip and delete the apps you don't want, add the apps you do want, and flash.
No need to do anything else.
Click to expand...
Click to collapse
Don't u need to delete the permissions and everything from updater-script. I'm new to this so do u have to?
Sent from my SGH-I777 using XDA App
Usually the updater-script just sets permissions for the whole /system/app folder with one command.
Entropy512 said:
Usually the updater-script just sets permissions for the whole /system/app folder with one command.
Click to expand...
Click to collapse
How would u do that. Sry I'm a total noob to this. I only know how to set it per app.
Sent from my SGH-I777 using XDA App
The first reply already told you how to do it. I just delete the apks using winRAR and close the file, done.
Ok, this may be answered elsewhere, I don't know. "Search is temporarily unavailable" I am trying to understand how I am supposed to work with the backup from CWM. I understand that I should have a System image that I can work in, but what I have is 3 files in its place. System.ext4.tar, System.ext4.tar.a, and System.ext4.tar.b. All three files are broken to some degree.
System.ext4.tar is a zero byte file.
System.ext4.tar.a appears to be a spanned tar file that 7ZIP/WinRAR simply think was cut-off (never asks for the second file, and complains of unexpected End of Archive)
System.ext.4.tar.b appears to be the second part of the archive, but nothing will open it.
So, how do I get to a point I have a complete archive that I can edit? Or do I need to use different software than CWM to back up the phone?
Thanks for the help guys.
waldojim said:
Ok, this may be answered elsewhere, I don't know. "Search is temporarily unavailable" I am trying to understand how I am supposed to work with the backup from CWM. I understand that I should have a System image that I can work in, but what I have is 3 files in its place. System.ext4.tar, System.ext4.tar.a, and System.ext4.tar.b. All three files are broken to some degree.
System.ext4.tar is a zero byte file.
System.ext4.tar.a appears to be a spanned tar file that 7ZIP/WinRAR simply think was cut-off (never asks for the second file, and complains of unexpected End of Archive)
System.ext.4.tar.b appears to be the second part of the archive, but nothing will open it.
So, how do I get to a point I have a complete archive that I can edit? Or do I need to use different software than CWM to back up the phone?
Thanks for the help guys.
Click to expand...
Click to collapse
Well, I found a solution for now. Fire up Linux, use cat to combine all three files, then use tar to extract the contents. Not sure why this needed split in the first place, but at least the files can be extracted.
I have managed to remove the APKs I do not want, and made a new system.ext4.tar file (all in Linux), but need to know what else I have to do to make the system image usable.
I found several guides on making a ZIP file, but I didn't want to necessarily go through all that. I backed up everything, so what I would like to know, is what all needs to change so that I can use the separate files as they are, and simply do a CWM "restore" function?
I know I sound like a complete noob at this point, and will deal with the related comments. However, please understand, I don't want the heavily modified rom packs. I simply wanted a rom VOID of all the Verizon bloatware, and have the Verizon tethering restraints removed. I have them all disabled now, and 3rd party tethering is working quite well. So I would rather not have that garbage wasting space. Right now, it looks like I may save 250MB or so.
Any help would be appreciated. Thanks.
waldojim said:
I have managed to remove the APKs I do not want, and made a new system.ext4.tar file (all in Linux), but need to know what else I have to do to make the system image usable.
I found several guides on making a ZIP file, but I didn't want to necessarily go through all that. I backed up everything, so what I would like to know, is what all needs to change so that I can use the separate files as they are, and simply do a CWM "restore" function?
I know I sound like a complete noob at this point, and will deal with the related comments. However, please understand, I don't want the heavily modified rom packs. I simply wanted a rom VOID of all the Verizon bloatware, and have the Verizon tethering restraints removed. I have them all disabled now, and 3rd party tethering is working quite well. So I would rather not have that garbage wasting space. Right now, it looks like I may save 250MB or so.
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Backups really aren't meant to be unzipped and played with. Usually bloat removal is done while booted into the system or you can unpackage a Rom and remove the bloat there and then repackage it and flash it then make your backup that doesn't contain any bloat. Using the xda kitchen tools from dsxda I believe is the name
Sent from my HTC6435LVW using XDA Premium HD app
.torrented said:
Backups really aren't meant to be unzipped and played with. Usually bloat removal is done while booted into the system or you can unpackage a Rom and remove the bloat there and then repackage it and flash it then make your backup that doesn't contain any bloat. Using the xda kitchen tools from dsxda I believe is the name
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
I think this is where some of my confusion comes from - it was never zipped. There was a group of tarred files, an MD5sum and a few other items. But nothing there was zipped.
waldojim said:
I think this is where some of my confusion comes from - it was never zipped. There was a group of tarred files, an MD5sum and a few other items. But nothing there was zipped.
Click to expand...
Click to collapse
I guess what I meant to say by "zipped" was just in general they are compressed by the recovery in a way that it knows how to go and use them to restore data to the device.