hello guys i wanna know what things i can delete and what things i can not delete in int.d and build.prop from sense based roms can someone give me a list?
What's in init.d will likely vary across any rom, sense based or not. Not sure about build.prop as never changed it, but i'm guessing it's not the same for all roms either.
For instance, init.d likely contains an app2sd script of some sort, perhaps even some tweaks which the dev might want to include. some are probably harmless, but deleting something you don't know about might make the phone unusable...
So therefore we can't just give you an definitive list of just what you can or can't delete....you could just nandroid backup and try yourself...
my return questions would be:
- why do you even want to delete things from init.d or build.prop
- what are you trying to actually achieve by doing so?
- ultimately, is it even worth it...
eddiehk6 said:
What's in init.d will likely vary across any rom, sense based or not. Not sure about build.prop as never changed it, but i'm guessing it's not the same for all roms either.
For instance, init.d likely contains an app2sd script of some sort, perhaps even some tweaks which the dev might want to include. some are probably harmless, but deleting something you don't know about might make the phone unusable...
So therefore we can't just give you an definitive list of just what you can or can't delete....you could just nandroid backup and try yourself...
my return questions would be:
- why do you even want to delete things from init.d or build.prop
- what are you trying to actually achieve by doing so?
- ultimately, is it even worth it...
Click to expand...
Click to collapse
1-i want to delete the old tweaks that can bad interact whit a tweaks package 2-those tweaks are for balanced gaming not hard gaming 3- yes, it worth a try
Related
So should I put it up on here?? It's just my own little build, nothing special, few things removed, some things added, but I don't know if its worth putting it out in the "wild"...
Basically a rooted 2.2-r1 AOSP build (FRF91 gapps), some bits removed, others added, modded my old A2SD+ release from when 2.1 was rooted ages ago (original one to move dalvik-cache across to sd), busybox, su, blah blah... Usual flavours... but I'm still working on it, options, compiles (kernel too, I need to find out how to add UV support, or HAVS if its better?? but have no idea where this information is...)
Don't really want to add too much choice though, there are plenty out there now, so not sure if it's worth releasing it, or just keep it private for me and friends
[to mods] - Sorry if this is in the wrong place, but I felt its a Q which needs an A... or an O (opinion)... Feel free to move if required.
PaulW21781 said:
So should I put it up on here?? It's just my own little build, nothing special, few things removed, some things added, but I don't know if its worth putting it out in the "wild"...
Basically a rooted 2.2-r1 AOSP build (FRF91 gapps), some bits removed, others added, modded my old A2SD+ release from when 2.1 was rooted ages ago (original one to move dalvik-cache across to sd), busybox, su, blah blah... Usual flavours... but I'm still working on it, options, compiles (kernel too, I need to find out how to add UV support, or HAVS if its better?? but have no idea where this information is...)
Don't really want to add too much choice though, there are plenty out there now, so not sure if it's worth releasing it, or just keep it private for me and friends
[to mods] - Sorry if this is in the wrong place, but I felt its a Q which needs an A... or an O (opinion)... Feel free to move if required.
Click to expand...
Click to collapse
Worth uploading mate, not going to harm the community
Tuxility in the market http://www.appbrain.com/app/tuxility/com.grimmvarg.android.tuxility
News: I have discovered that editing the settings.db is not very usefull and might make your system unstable. I have therefor decided to choose a less generic way of letting users access edit system settings, like wifi sleep time etc.. Should be done in a day or two
The userbase has grown a lot these last days, which means a lot more feedback. No big bugs as of yet, but please post any issues you find, so I can fix them And off course feature requests!
Tuxility
Hey guys!
Im creating an app for the Samsung galaxy s, Ive only been working on it for a few days, but a few features have found there way into it:
- Flashing a kernel without pc, while phone is on. ( ref: http://forum.xda-developers.com/showthread.php?t=765724)
- Back up your current kernel
- Phone codes (view battery stats and various tests of hardware)
- Backing up and restoring /efs
- Reboot to Recovery, Download and standard mode
- Cleaning battery stats
Features to come:
- Toggle Mediascanner on/off
- Editing system settings
- Full System information
- Change system Font
- Sensor dump (for fun)
- Improved GUI, with colors and an icon
- Place backups on external_sd if it exists (thanks _renaud_)
- Add tools for calibration of screen/battery etc..
Requirements:
- Root
- A Samsung Galaxy S (all variants) running Android 2.1 and up.
Why am I releasing this?
Well for one to share the kernel-flashing feature (thanks to supercurio for this). Also to get feedback on what works and not. But more importantly to get feedback on what to add or change about feature and code (which is located here, yes I know my github tree is suboptimal ). I'm used to Java but pretty new to android. So any feedback on the code is appreciated
NOTES ABOUT THE KERNEL FLASHING
I hacked together a filechooser to pick the zImage you want to flash. And you can flash only zImages or Tars including zImage.
The filechooser sets /sdcard/download/ as starting DIR so i suggest you unpack your zImage there. Bakups are stored in /sdcard/.tuxility/backup
And the notice of no responsibility
I take no responsibility if my app breaks your phone, (not that it should, but now i said it) and you try this software at your own risk. On a related note, the code and the app is released under GPLv3. I will however, do all i can to help
Logging is on, so have a look in logcat if something is not working and let me know
I hope someone will find this usefull, and find the time to give me som feedback
Known issues:
The settings file seems to be located elsewhere on the galaxy tab. So if anyone with a tab wants to help me out finding this, that would be great
If flashing kernel fails, and log show "not enough space on device" remove any folder in /cache named "2010-*" that contains a zImage. This is fixed irelease 1.2, I thought that /cache was cleaned at boot, but this was not the case.
The way that all this work
The backup features are pretty straight forward, using a system shell I give a cp/cat/tar command wherever it is suitable. For instance /efs needs to be tared to keep uid and permissions.
For reboot i issue the "reboot <mode>" as root
The kernel install uses the procedure from this thread http://forum.xda-developers.com/showthread.php?t=765724 and copies a binary file to /apps and uses it to install the new kernel image.
All backups are stored in /sdcard/.tuxility/backup
A SMALL WARNING
Just like anyone will tell you, remove all lagfixes when flashing a new kernel if you are not _sure_ that the new kernel you are flashing support your old lagfix, ktnx
CHANGELOG
V1.2
- Huge code cleanup
- Now using flash_image to flash kernel, thanks to koush!
- no more screen distortion after flash
- No forced reboot after flash
- Better execution controll
- Added phone codes
- Removed edit settings.db (this is to risky, no replacement on the sketch board)
- Starting on feature to fetch latest kernel
V1.1
- Install kernel from tar archive
- Finally have an icon
- A bit more restructuring of code
Android Market will not allow me to use sub 1 versions.. :/
V0.21:
- Restructured the menu, for later additions
- Added remove batterystats
- Backup Kernel now sets date in filename
- Improved filechooser, will not install files with a file extension
- Big cleanup of code
GrimmVarg I will follow your work very closely !
Wow, this is good. CWM doesn't backup the kernel, and with this app, one can easily do it. Would be absolutely wonderful if it can be included in the CWM recovery menu.
Thanks and will try it soon.
Is it somewhat like this?
http://forum.xda-developers.com/showthread.php?t=775154
Regards
miro666 said:
Is it somewhat like this?
http://forum.xda-developers.com/showthread.php?t=775154
Regards
Click to expand...
Click to collapse
Yes and no, Its the same concept but different features, except the Secret codes list which I havent implement and the wiping of batterystats. I used SGStools my self before I started on Tuxility, its a very usefull app.
I am making tuxility mostly to get all the features that i need in one app, as I feel that most of these utility apps both overlap on features and miss a few essential features, like flashing a new kernel for instance. So my goal is for Tuxility to be a feature full alternative that cover all common needs, and in addition has specialized features for a give rom/kernel.
Thus feature requests are most welcome
Can you publish this to Android Market?. Further updates are easier that way. Thanks for making this.
hacksome said:
Can you publish this to Android Market?. Further updates are easier that way. Thanks for making this.
Click to expand...
Click to collapse
Yeah. As soon as I get an icon and rewrite the code for executing shell commands i'll push to market
please flash,
pda
modem
csc
withtout pc, send .apk
thanks
Yeah Mr....
great idea ... bring sgstools, spareparts and some features missing in cwm together ... absolutely welcome!!!
gwaan doin this great job!
My20 said:
please flash,
pda
modem
csc
withtout pc, send .apk
thanks
Click to expand...
Click to collapse
c0llal0 said:
Yeah Mr....
great idea ... bring sgstools, spareparts and some features missing in cwm together ... absolutely welcome!!!
gwaan doin this great job!
Click to expand...
Click to collapse
Yeah, If its possible it would be nice. Ill look into it later. Right now Ive been getting help by mikebeecham to make an icon for the app as i plan to release it to market tonight. But I want to implement the possibility to maipulate the settings.db first. So.. yeah. Hoping to get it done while my girlfriend is at the theater
Install and backup kernel works fine.
Really nice
Just wanted to let you know i used this to flash Supercurio's VooDoo lagfix kernel. Easy and painless!
Thank you for this tool.
Sent from my GT-I9000 using XDA App
Thanks for the super cool all in one app..
looks fantastic - definitely going to give it a whirl!
Just wanted to throw this out there.
This app works on the Galaxy tab as well. trying to view settings causes a FC however backing up the kernal worked
looks great.
backup also csc and eventually modem would be very nice.
socksfelloff said:
Just wanted to throw this out there.
This app works on the Galaxy tab as well. trying to view settings causes a FC however backing up the kernal worked
Click to expand...
Click to collapse
Glad to hear it! Could you tell me if if backing up settings.db work? Might be that this file is located elsewhere on the tab. And if so I need to do some digging to find as I dont own a tab my self
zoubidou said:
looks great.
backup also csc and eventually modem would be very nice.
Click to expand...
Click to collapse
Yeah, after i get settings maipulation to work and get a little bit better look an the app, ill be looking to try and both backup and install full firmware
i just tried a kernel update.
i used speedmod version 11 cwm.
i stated wrong file format. sorry for that.
In the description for many ROMs devs say they are optimized, zipaligned, de/odexed, etc. What do they mean by optimized? In other words, what are different ways other than zipaligning and odexing that a ROM could be modified for better performance?
Thanks
cengator said:
In the description for many ROMs devs say they are optimized, zipaligned, de/odexed, etc. What do they mean by optimized? In other words, what are different ways other than zipaligning and odexing that a ROM could be modified for better performance?
Thanks
Click to expand...
Click to collapse
Zipaligning helps with RAM, I use a script to zipalign every time my phone boots
Deodexed I believe makes it so u can remove system apps...ect
Overall it speeds up the phone. Try the odexed and the deodexed versions of the stock Rom. U will see a difference
Sent from my HTC Incredible using XDA App
superchilpil said:
Zipaligning helps with RAM, I use a script to zipalign every time my phone boots
Deodexed I believe makes it so u can remove system apps...ect
Overall it speeds up the phone. Try the odexed and the deodexed versions of the stock Rom. U will see a difference
Sent from my HTC Incredible using XDA App
Click to expand...
Click to collapse
Thanks. Yeah, I know what zipalign and deodexing are. If a dev says his rom is "optimized, zipaligned, and deodexed," he is doing something additional besides those two. I'm wondering what that might be.
Generally image optimization. Although some dev's actually do improvements such as stripping the extra localizations. Stock images are already optimized unless you edit them, well all the ones I've check anyway.
i do all kinds of stuff and still don't know what zipaligned means/does
When devs say they optimized there rom or framework etc... It means they ran a tool such as apk manager (what I use) to compress all the images in an apk to be the smallest size they can get them without losing quality. This will speed up the build for maximum performance and less ram usage.
Other people say there apks are Reengineered. This means that there apks have all unused lanuages removed for even better performance.
Odexing means Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace files (not having to worry about odexes). Odexed builds such as stock roms cannot be themed for the most part.
Zipalign is an archive alignment tool introduced first time with 1.6 Android SDK (software development kit). It optimizes the way an Android application package (APK) is packaged. Doing so enables the Android operating system to interact with the application more efficiently, and hence has the potential to make the application and overall the whole system much faster. Execution time is minimized for zipaligned applications, resulting is lesser amount of RAM consumption when running the APK.
Hope this helps,
Incubus
Wow! Thank you very much! That is very informative. Regarding deodexing, other optimizations being equal, would an odexed rom have greater performance than a deodexed rom?
Sent from my ADR6300 using Tapatalk
incubus26jc said:
When devs say they optimized there rom or framework etc...
Click to expand...
Click to collapse
What does the difference in framework mean?
I found this website( http://androidforums.com/incredible-roms/155282-incredible-rom-list.html ) to try and find some new roms to use, because i'm stuck at the white screen of death on my Dinc. See this post if you want to help ( http://forum.xda-developers.com/showthread.php?t=1023358 )
BUT my actual question is what does framework mean? Are all of those "frameworks" listed compatible with my phone? I know that the Dinc uses the "Sense UI"...are these the same? Can I install "vanilla" framework ROMS on my Droid Incredible? If I do, is there certain things that won't work? Sorry for all the newbish questions, but I'm already soft bricked and want to know before I go messing around with stuff again. Seems I only knew just enough to get me into trouble and bring me to a white screen, and I don't want to do further damage.
Thanks a ton.
Hello Comm. and Devs,
For our Archos there are now many custom rom-images and experimental distris of linux and so on and every "rom" has its own kernel and init which have to be flashed and it seems it is only possible to have one kernel and one init.
I want to test as many roms, plasma, ics alpha, ubuntu, 3.2.80 with busybox and adobe, etc. for shorter or for everytime. And when Archos brings ICS finally i want to upgrade of course, without losing apps and settings etc.
Now i am on rooted 3.2.79 with chainfire 3d and i dont know if it makes senes to upgrade to 3.2.80 custom rom from surdu. Okay, vibrator and so on and some goodies, sounds nice, therefore i want to test and perhaps revert it later.
Which roms are compatibel with each other and which not?
Which rom is how much recommend?
What are the differences between these inits (kernel seems often to be the same seen by its size i think) - is there the possibility and the evidence to merge the inits somehow?
Or is there a kind of general initramfs one could take for most roms?
What rom has which kernel in which version and same for initfs?
What are there for possibilities that every image gets it adequate kernel and initfs?
Many of us want multi boot which i think is not really (?) supported for gen9 .
What should be done for compatibility if i want a kind of multiboot?
It would be nice if this would give a set of infos for us all.
Well, no, kernels are not the same. We're not 100% sure for Archos ones, they're currently closed source, but looking at what they fixed in the different releases, I believe there have been changes. Plasma is definitely using a different kernel, ics will require a completely new 3.0 kernel and probably require clear data.
So what you're looking for is not really possible, not matching kernel with firmware is not a good idea. The only exception would be Ubuntu, but that's it.
what about multi-boot menu from open aos?
There are roumors that people have it work but it is not supported.
Dont want to mess all up.
Do you know something or have experiences?
svennimann said:
what about multi-boot menu from open aos?
There are roumors that people have it work but it is not supported.
Dont want to mess all up.
Do you know something or have experiences?
Click to expand...
Click to collapse
Sorry - about this with multiboot i see there is already a thread.
Well cyanogen 7.2 is out. Repost, because I posted in the wrong section previously.
I think I'm going to build a lightweight rom go launcher based rom off of it. First try ever I've done a lot of experimenting.
I intend on removing languages, apps that I never have had any remote desire to use (vpn, fmradio, that kind of thing), and create a basic high performance mod.
I'd like to incorporate the tiamat kernel somehow. Also I'd like to force smartassv2, and custom calibration settings, but I'm having a bit of a hard time finding where those settings are saved in the zip.
Does anyone know where the file is saved, for adjusting autobrightness defaults?
I'd would like to zipalign it, and if I can, odex it.
Also I am going to try to run PNGout on all of the PNG files.
Anyone have any suggestions on best tools to do all of these things from a windows or ubuntu based linux perspective? I know how to remove the APKs, and using PNGout seems pretty straight forward.
I'm not opposed to recompiling, if thats the best method to odex.
Also, any suggested performance optimizations?
Build.prop flags?
There are plethora of tools in the chef section.
Sent from my Go Senseless Classic Conflagration Evo
Angelus359 said:
Well cyanogen 7.2 is out. Repost, because I posted in the wrong section previously.
I think I'm going to build a lightweight rom go launcher based rom off of it. First try ever I've done a lot of experimenting.
I intend on removing languages, apps that I never have had any remote desire to use (vpn, fmradio, that kind of thing), and create a basic high performance mod.
I'd like to incorporate the tiamat kernel somehow. Also I'd like to force smartassv2, and custom calibration settings, but I'm having a bit of a hard time finding where those settings are saved in the zip.
Does anyone know where the file is saved, for adjusting autobrightness defaults?
I'd would like to zipalign it, and if I can, odex it.
Also I am going to try to run PNGout on all of the PNG files.
Anyone have any suggestions on best tools to do all of these things from a windows or ubuntu based linux perspective? I know how to remove the APKs, and using PNGout seems pretty straight forward.
I'm not opposed to recompiling, if thats the best method to odex.
Also, any suggested performance optimizations?
Build.prop flags?
Click to expand...
Click to collapse
The best tools to use to start learning to make create your own roms is use the kitchen,it will zipallign and deodex all that good stuff,like the guy above me said, theres alot of other guides and tools here that will help you with your venture....