With all these new "hero" builds coming out/updates for them, it is important to have optimal settings. Many people are not sure how to do this so I thought I would take my time to write a quick how to.
I have also attached a user.conf that is setup with comp cache and backing swap, swappiness of 80. I set the cpu scaling from 384 to 528 Mhz. You may edit this with notepad++ if you would like swap instead. Just open the user.conf with notepad++ and make the changes you want (the file is pretty self explanatory) Just be sure to set compcache to 0 along with backing swap
Place the "user.conf" on your sd root, and use the commands mentioned below
P.S. I apologize in advance to the moderators if you feel this is not in the appropriate place or not necessary, just trying to make things a little bit easier
In Terminal type:
Code:
$su
#sh /system/bin/rwsystem
#cp -f sdcard/user.conf /system/bin/user.conf
*If your ROM does not support "rwsystem"* use:
Code:
mount -o remount,rw /dev/mtd/mtdblock3 /system
Once again, I have attached a user.conf along with the JAC kernel that includes the script which allows you to use "rwsystem" (If your ROM supports the kernel)
Here is the link to the JACSki kernel with ttc_smokee's gps fix and Soul Life's script which will allow you to use "rwsystem"
http://www.4shared.com/file/133261717/84fd2884/JACHEROSki_Kernal-_Update.html
*Just like anything else on this site, I am not responsible for you bricking or damaging your device*
CHeErs
Post here if you would like any kind of walkthrough for "dummies" reguarding user.conf's or user.init's or
kingklick said:
*If your ROM does not have a kernel that supports "rwsystem" use
Code:
mount -oremount,rw /dev/mtd/mtdblock3 /system
Click to expand...
Click to collapse
You missed the space between -o and remount...
cx92001 said:
You missed the space between -o and remount...
Click to expand...
Click to collapse
works as-is
some progs accept arguments like that
some don't
mount happens to be one that does
alapapa said:
works as-is
some progs accept arguments like that
some don't
mount happens to be one that does
Click to expand...
Click to collapse
Good to know. Thanks
alapapa said:
works as-is
some progs accept arguments like that
some don't
mount happens to be one that does
Click to expand...
Click to collapse
yah it does work without the space, thanks, but i edited the space in anyway to prevent more posts like that
Are these edits needed/beneficial for those not interested/using hero ROMs?
I recall MikeTaylor had a file, but i know so little on what these can do. Thanks for doing this man.
s15274n said:
Are these edits needed/beneficial for those not interested/using hero ROMs?
I recall MikeTaylor had a file, but i know so little on what these can do. Thanks for doing this man.
Click to expand...
Click to collapse
Not needed, however I'd say most would argue they are beneficial changes for most ROMS... ie) cyanogen uses comp cache on his builds.
and no problem man my pleasure. My way of giving back to this great site
If you do not know how to edit these files post here and ill make you a user.conf to your liking
kingklick said:
With all these new "hero" builds coming out/updates for them, it is important to have optimal settings. Many people are not sure how to do this so I thought I would take my time to write a quick how to.
I have also attached a user.conf that is setup with comp cache and backing swap, swappiness of 80. I set the cpu scaling from 383 to 528 Mhz. You may edit this with notepad++ if you would like swap instead. Just be sure to set compcache to 0 along with backing swap
P.S. I apologize in advance to the moderators if you feel this is not in the appropriate place or not necessary, just trying to make things a little bit easier
In Terminal type:
Code:
$su
#rwsystem
#cp -f sdcard/user.conf /system/bin/user.conf
*If your ROM does not have a kernel that supports "rwsystem" use
Code:
mount -o remount,rw /dev/mtd/mtdblock3 /system
Once again, I have attached a user.conf along with the JAC kernel that will allow you to use "rwsystem" (If your ROM supports the kernel)
Here is the link to the JACSki kernel which will allow you to use "rwsystem"
http://www.megaupload.com/?d=K39IKK7A
*Just like anything else on this site, I am not responsible for you bricking or damaging your device*
CHeErs
Click to expand...
Click to collapse
Rwsystem is not kernel dependent, its a script I wrote that made its way into a few other builds. Just a script which resides in bin or xbin directory, nothing more or less.
soulife said:
Rwsystem is not kernel dependent, its a script I wrote that made its way into a few other builds. Just a script which resides in bin or xbin directory, nothing more or less.
Click to expand...
Click to collapse
o ok kool. I was mislead by a few others saying it was in the new JAC kernel silly people.... Anyway thanks for the fix soul life
you did a great thing by adding that script
Just changed the "kernel file" to the kernel with gps fix.
cheers!
More Detailed HOW-TO
Thanks for the post. I am in middle of (will take about a year, LOL) writing a HOW-TO on user.conf settings so that it will be easier to understand what needs editing and what settings are best. Currently, I am using a 64MB linux-swap with compcache and have been playing around with tweaking the settings to make my phones run "perfectly." This is much more difficult than it sounds when you take into account the various options such as backing swap, linux swap, swap files, compcache and swappiness settings. This all, of course, is system and user dependent. I use my G1 and my myTouch differently and have different apps installed on each so therefore, my settings are different for both. I still haven't come up with the perfect strategy but I am pretty close.
How about expanding this out (I don't mind actually posting it) to include more details on what each setting means and what the possible benefits/problems are with each. I use this (http://forum.xda-developers.com/showthread.php?t=542899) userinit.sh file along with the user.conf. I wrote one script to pull the user.conf from system/sd to my SD card and one that pushes it back to system/sd when I'm done with it. I use "Text Edit" to edit the user.conf right on my phone so I do not need to use ADB and Notepad++. This takes the PC out of the picture so I can tweak the settings wherever I happen to be.
I don't think there is ONE user.conf file that is good for everyone. It all depends on what the user's intentions are with his or her phone. Your default swappiness is set to 80 but that can vary. I am up in the air on that one testing between 30 and 100. But like I said, user dependent.
AndroidAppCritic said:
Thanks for the post. I am in middle of (will take about a year, LOL) writing a HOW-TO on user.conf settings so that it will be easier to understand what needs editing and what settings are best. Currently, I am using a 64MB linux-swap with compcache and have been playing around with tweaking the settings to make my phones run "perfectly." This is much more difficult than it sounds when you take into account the various options such as backing swap, linux swap, swap files, compcache and swappiness settings. This all, of course, is system and user dependent. I use my G1 and my myTouch differently and have different apps installed on each so therefore, my settings are different for both. I still haven't come up with the perfect strategy but I am pretty close.
How about expanding this out (I don't mind actually posting it) to include more details on what each setting means and what the possible benefits/problems are with each. I use this (http://forum.xda-developers.com/showthread.php?t=542899) userinit.sh file along with the user.conf. I wrote one script to pull the user.conf from system/sd to my SD card and one that pushes it back to system/sd when I'm done with it. I use "Text Edit" to edit the user.conf right on my phone so I do not need to use ADB and Notepad++. This takes the PC out of the picture so I can tweak the settings wherever I happen to be.
I don't think there is ONE user.conf file that is good for everyone. It all depends on what the user's intentions are with his or her phone. You default swappiness is set to 80 but that can vary. I am up in the air on that one testing between 30 and 100. But like I said, user dependent.
Click to expand...
Click to collapse
o ok very kool. Although, I did mention in my OP the HEro ROMs and what not, so I figured most people interested would be in the HEro scene. These settings seem to work best for me on 75% of the hero ROMs Ive flashed. DOesnt mean its "right" just whats worked for me. Just wanted to give back to this great site, and help the new comers because we have all been there at some point
P.S. PM me what you think I shoulld change/add to this thread to make it offical. Thank you in advance
ChEerS
Yeah, I just noticed the Hero thing. I suppose that I would like to see (somewhere on XDA either here or a new post) a very detailed explanation of all the possible settings, what they do and how they may or may not affect each other. When I was first trying all of this out I had to search very long to find explanations. If a noob wanted to know what swappiness was, for example, they would have a difficult time finding a good explanation. Even the experts can't agree so how is a novice supposed to understand it.
Perhaps this would be a good place for people who know to informally contribute and it can eventually be moved to its own thread, a sort of compache, linux-swap, backing swap, swappiness manual. A one-stop shop for all things memory related with links to the various XDA threads that can help them accomplish what they want to do.
My G1 and myTouch fly right now with next to no lag but it took me quite some time to get all the settings the way I like it (sort of, still perfecting them). I want the same for everyone.
AndroidAppCritic said:
Yeah, I just noticed the Hero thing. I suppose that I would like to see (somewhere on XDA either here or a new post) a very detailed explanation of all the possible settings, what they do and how they may or may not affect each other. When I was first trying all of this out I had to search very long to find explanations. If a noob wanted to know what swappiness was, for example, they would have a difficult time finding a good explanation. Even the experts can't agree so how is a novice supposed to understand it.
Perhaps this would be a good place for people who know to informally contribute and it can eventually be moved to its own thread, a sort of compache, linux-swap, backing swap, swappiness manual. A one-stop shop for all things memory related with links to the various XDA threads that can help them accomplish what they want to do.
My G1 and myTouch fly right now with next to no lag but it took me quite some time to get all the settings the way I like it (sort of, still perfecting them). I want the same for everyone.
Click to expand...
Click to collapse
Yeah I agree cuz when I was trying to root my phone and stuff around fiveish months ago... and I had to do the whole runaround because there was not any good organized information like now it is pretty close. But we definitely have a ways to go to get some good stuff for n00bs... lets get it done.'
AndroidAppCritic said:
Yeah, I just noticed the Hero thing. I suppose that I would like to see (somewhere on XDA either here or a new post) a very detailed explanation of all the possible settings, what they do and how they may or may not affect each other. When I was first trying all of this out I had to search very long to find explanations. If a noob wanted to know what swappiness was, for example, they would have a difficult time finding a good explanation. Even the experts can't agree so how is a novice supposed to understand it.
Perhaps this would be a good place for people who know to informally contribute and it can eventually be moved to its own thread, a sort of compache, linux-swap, backing swap, swappiness manual. A one-stop shop for all things memory related with links to the various XDA threads that can help them accomplish what they want to do.
My G1 and myTouch fly right now with next to no lag but it took me quite some time to get all the settings the way I like it (sort of, still perfecting them). I want the same for everyone.
Click to expand...
Click to collapse
yah for sure bro. Maybe you and me should put a detalied one together... This was intended to be a crude easy guide for pure n00bs who just want a "faster" phone. Most n00bs are not too concerned with what "swappiness" is and the technical difference between CC or linux-swap. Thats just my opionion though brother
Sorry if this is a stupid question but what exactly do I do with the two files? Do I rename the kernal update as update.zip and run that after I'm done installing the Hero ROM of my choice (I was looking at doing drizzy's)? Then what do I do with the user.conf file?
markdt098 said:
Sorry if this is a stupid question but what exactly do I do with the two files? Do I rename the kernal update as update.zip and run that after I'm done installing the Hero ROM of my choice (I was looking at doing drizzy's)? Then what do I do with the user.conf file?
Click to expand...
Click to collapse
Ima change the OP thanks anyway, if you have recovery 1.4 you can actually flash "any" zip meaning it does not need to be renamed. MOst ROMS now have this kernel built in, however MOdaco 2.2 DOES NOT, so if you plan on using modaco 2.2, flash this kernel. FLash MOdaco (or whatever ROM is missing this kernel) THEN flash the kernel right after without rebooting.
as far as the user.conf goes, put it on your root and use the commands i provided in the OP.
ChEeRS
Related
Is there instructions on creating a post-flash (or hard reset) install script? I'd like to have it run the cingular WAP cab, and maybe a couple others. I think I've been all over, but haven't seen anything...
Thanks!
Also - does anyone have a package or cab for camera 3.3???
Hi Matt... there are a couple of options...
First off, you could go the route that Faria does in his kitchen - effectively an Extended ROM folder under Windows. When the ROM install has finished and you've done the screen align, it runs the Extended ROM contents - just like the customisations you get in most operator ROMs. The advantage of doing it from a subfolder under Windows is that it works for G4 users as well as G3.
The other alternative is to actually flash your Extended ROM (this is what I've done, as mine is G3).
With the right files in Windows and Windows\Startup (CheckAutoRun.exe and CheckAutoRun.lnk respectively) and the registry entries set up for the appropriate location (I can tell you what these need to be), it will run no problem.
Is this what you're looking for? Faria also has a nice couple of utils that run during customisation and let you choose which operator's settings (GPRS and MMS) you wish to install. I guess these just run the appropriate CAB file based on your choice.
I am happy to help you set this up if it would be of assistance, having spent the last couple of days trying to get all this stuff up and running.
JoelC said:
Hi Matt... there are a couple of options...
First off, you could go the route that Faria does in his kitchen - effectively an Extended ROM folder under Windows. When the ROM install has finished and you've done the screen align, it runs the Extended ROM contents - just like the customisations you get in most operator ROMs. The advantage of doing it from a subfolder under Windows is that it works for G4 users as well as G3.
The other alternative is to actually flash your Extended ROM (this is what I've done, as mine is G3).
With the right files in Windows and Windows\Startup (CheckAutoRun.exe and CheckAutoRun.lnk respectively) and the registry entries set up for the appropriate location (I can tell you what these need to be), it will run no problem.
Is this what you're looking for? Faria also has a nice couple of utils that run during customisation and let you choose which operator's settings (GPRS and MMS) you wish to install. I guess these just run the appropriate CAB file based on your choice.
I am happy to help you set this up if it would be of assistance, having spent the last couple of days trying to get all this stuff up and running.
Click to expand...
Click to collapse
It sounds like your first point is what I was looking for - but up till now I've avoided adding / manipulating the extended rom to prevent issues related to it's use. I guess I'll have to cross that bridge sooner than later!
Is there a "howto" anywhere on it? I'd like to add the option for users to select post installation packages to run, in a nice and "foolproof" way - such as themes, WAP cabs, or whatever. Kinda like "drop your post install cabs in this folder" and it'll go ahead and add them during the rom build, then execute the install after flashing.
Thanks!
mattk_r said:
It sounds like your first point is what I was looking for - but up till now I've avoided adding / manipulating the extended rom to prevent issues related to it's use. I guess I'll have to cross that bridge sooner than later!
Is there a "howto" anywhere on it? I'd like to add the option for users to select post installation packages to run, in a nice and "foolproof" way - such as themes, WAP cabs, or whatever. Kinda like "drop your post install cabs in this folder" and it'll go ahead and add them during the rom build, then execute the install after flashing.
Thanks!
Click to expand...
Click to collapse
search lol i'll try and dig it up for you since i should probably do the same thing
try this of course editing it to where you want it to point:
Code:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"
notyourdaddy said:
search lol i'll try and dig it up for you since i should probably do the same thing
try this of course editing it to where you want it to point:
Code:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"
Click to expand...
Click to collapse
I just found this link that has an extended rom in it. It makes a lot of sense, especially the txt file that directs the installation and then initiates a reset. Getting warmer!
http://forum.xda-developers.com/showthread.php?t=309922
So here's what I'm thinking - just initial thoughts:
Have a folder with the base applications that are used every time like AutoRun.exe.
The user places the cab(s) in the "add files to ext rom" folder.
They run an exe that reads the directory file contents, verifies file type, copies the files to the extended rom folder, and displays the list. I'd write it in VB, since I'm most comfortable with file system operations in that language...
They change the list based on the order they want them installed using up and down arrows to sort priority.
The click OK, and it creates the config.txt file, including all necessary commands such as reset and whatnot.
That way when they build, it's all good to go.
Any thoughts?
Slightly off topic but does anyone have a .CAB for TomTom6 (or know how to edit/make one) that doesn't require user input during the installation?
I am not looking for a hacked version of TomTom, just how to prevent it asking me where to install. .CABs that run from the Extended ROM can't ask for user input or it will crash the extended ROM installation as we know; I just don't know how to edit the ttn.cab to stop it asking.
Thanks
Andy
Hi Matt,
It does sound like the first option is the best - it's also the only way to get G4 compatibility. I think your idea to write a VB app is a good one - let the user choose which CABs to install to ExtRom, but I think u need to be very clear what you want to achieve. As this `ExtRom` is not actually in the proper extended Rom, but just a folder under Windows, you gain nothing really by installing programs from here, best just keeping it for operator specific settings and such.
The other issue with extended Rom installations, of any type, is that the config file must run to completion. if you put in cab files that require user input, the install will fail (at least from a proper extRom, maybe ok in this scenario, I don't know); likewise cabs that require or initiate a soft reset will cause an ExtRom install to crash. So, this sorts of limits what cabs can be used. mine puts in personal reg settings; no operator settings as I use wifi not gprs or mms.
Also - and I hope I'm not out of line here, or misunderstanding you - Faria has something that does exactly what u need in his fake ExtRom... u cld always ask him nicely for use of it, or r u looking forward to the coding?
My only other thought is the extra support burden a complex fake extrom scenario would generate, especially if ppl don't understand its purpose and stick stuff in that causes problems...
I hope this has made some sense - past my bedtime and I'm knackered LOL. Just my 2 cents, y'know?
Good work and all the best
JoelC said:
Hi Matt,
It does sound like the first option is the best - it's also the only way to get G4 compatibility. I think your idea to write a VB app is a good one - let the user choose which CABs to install to ExtRom, but I think u need to be very clear what you want to achieve. As this `ExtRom` is not actually in the proper extended Rom, but just a folder under Windows, you gain nothing really by installing programs from here, best just keeping it for operator specific settings and such.
The other issue with extended Rom installations, of any type, is that the config file must run to completion. if you put in cab files that require user input, the install will fail (at least from a proper extRom, maybe ok in this scenario, I don't know); likewise cabs that require or initiate a soft reset will cause an ExtRom install to crash. So, this sorts of limits what cabs can be used. mine puts in personal reg settings; no operator settings as I use wifi not gprs or mms.
Also - and I hope I'm not out of line here, or misunderstanding you - Faria has something that does exactly what u need in his fake ExtRom... u cld always ask him nicely for use of it, or r u looking forward to the coding?
My only other thought is the extra support burden a complex fake extrom scenario would generate, especially if ppl don't understand its purpose and stick stuff in that causes problems...
I hope this has made some sense - past my bedtime and I'm knackered LOL. Just my 2 cents, y'know?
Good work and all the best
Click to expand...
Click to collapse
That's really good info, because I'm climbing the learning curve as fast as I can here to get a good grasp on what the extended rom is, as well as how to use it. I appreciate the conditional warnings... better to know ahead of time than find out following a problem.
I'd rather use the true extended rom (as I understand it anyway), so I don't loose any additional space for the BuildOS programs. That is, assuming the extended rom is a seperate memory location than the base...
In another thread, someone is going to post that tool. I'm really interested in how it works.
If I can get all the concepts together, I hope to get a solid tool that will improve functionality in the ROM, without adding complexity or trouble... and I greatly appreciate the help!
Interesting thread...guys, you just gave me some new ideas.
Before that...there's one thing that's bothering me...
Can we use ExtendedRom on a G4 or not...lol I thought not, until me an Boto made a clean one from a G4 ExtRom and when Boto flashed it it worked , and he has a G4. Why we always say that we don't use an Extended Rom for G4 users ?
Normaly, a G4 should/would brick when flashing IPL/SPL not Extended Rom, am I right ?
We are shrinking the OS space to integrate features of the ExtendedRom in order to all people use it but is it that true ?
Ok, now back to my idea .. I want that in my next rom to include an extended rom, of course and make it that way so when you first start your PDA, it will act like when installing windows on the PC , asking you which apps or what options you want to use. I think i can manage to do that...still the question remains ...will G4 users be able to use it ?
Sorry for the delay writing back... I've been over in the G4 subforum trying to find out if they can flash Extended Rom. Some ppl have reported success using Faria's tutorial. Hopefully this is the case - what u said about IPL/SPL flashing is right, this seems to be a real problem, but if u can flash a radio-only Rom, why not Extended Rom?
What did u and Boto flash onto his G4? Blank Extrom or a cooked one?
Perhaps what we need is a guinea pig to try this out for us...!
JoelC said:
Sorry for the delay writing back... I've been over in the G4 subforum trying to find out if they can flash Extended Rom. Some ppl have reported success using Faria's tutorial. Hopefully this is the case - what u said about IPL/SPL flashing is right, this seems to be a real problem, but if u can flash a radio-only Rom, why not Extended Rom?
What did u and Boto flash onto his G4? Blank Extrom or a cooked one?
Perhaps what we need is a guinea pig to try this out for us...!
Click to expand...
Click to collapse
I took the Ext Rom from the Wizard Love Rom and i edited the config.txt and deleted cabs ...that's it
Well, if it flashed OK... sounds like it might be usable after all But tell me, is Boto's G4 CID locked or unlocked? It's all very uncertain, but some of the G4 posts lead me to believe this may make a difference
ADB100 said:
Slightly off topic but does anyone have a .CAB for TomTom6 (or know how to edit/make one) that doesn't require user input during the installation?
I am not looking for a hacked version of TomTom, just how to prevent it asking me where to install. .CABs that run from the Extended ROM can't ask for user input or it will crash the extended ROM installation as we know; I just don't know how to edit the ttn.cab to stop it asking.
Thanks
Andy
Click to expand...
Click to collapse
All I did for TomTom is install as normal and then copy the Navigator directory and My Documents\TomTomto my storage card where the maps, postcodes etc. are located. After any ROM upgrade all I need to do is create a shortcut in the start menu pointing at \Storage Card\Navigator\TomTom Navigator.exe No user input needed other than to pair the bluetooth gps and define a serial port.Hope this helps, it has worked for me after every change in ROM which has been quite a lot recently.
wizzzard said:
All I did for TomTom is install as normal and then copy the Navigator directory and My Documents\TomTomto my storage card where the maps, postcodes etc. are located. After any ROM upgrade all I need to do is create a shortcut in the start menu pointing at \Storage Card\Navigator\TomTom Navigator.exe No user input needed other than to pair the bluetooth gps and define a serial port.Hope this helps, it has worked for me after every change in ROM which has been quite a lot recently.
Click to expand...
Click to collapse
Thanks for that but it isn't what I was really after.... I am just trying to automate everything. I have flashed my ROM that many times recently and going through the install of TomTom each time is a bit of a pain. I have got a couple of .CABs in the Extended ROM OK and these work fine, I just thought it would be nice if I could get TomTom in there as well.
Andy
I didn't want this to turn into a "how-to" thread, but I'm still scratching for hard info on the extended rom, and as many questions out there, it might be a good one to clarify some details...
As I understand it now, there's two forms of "extended ROM":
1. The true extended rom "similar to the radio ROM"
There is some "trigger" that runs the contents of the extended rom, such as AutoRun.exe?
2. The 'psuedo' extended rom that is basically a post install script to run cabs.
The contents of the folder under windows are run from a trigger that resides in the startup folder - similar to a runonce in Windows on first boot?
Does this sound close?
Also, where does the 'true' extended rom reside? Does it use the portion of memory reserved for the OS, or is there another portion just for it? (so if by adding applications to the extended rom, your available storage memory will remain unchanged - less the installed application?)
I'm presuming then by the 'psuedo' extended rom, that it does consume ROM space, but simplifies post-flash cab installations - assuming you follow the rules...
From what I see, by using the 'psuedo' ER, you waste space by keeping the installation files in addition to the installed application files.
If I'm wasting space and time by asking these questions and you know of a good extended rom tutorial, please direct me to it. I have spend some time tonight searching, but a definitive guide still eludes me... Thanks!
Sorry, coming into this thread late, but you have seen this thread, right?
http://forum.xda-developers.com/showthread.php?p=968417
While it may not directly answer some of the questions, the tools and info in the tutorial may shed some light on this subject (or give you a direction to start digging further).
mfrazzz said:
Sorry, coming into this thread late, but you have seen this thread, right?
http://forum.xda-developers.com/showthread.php?p=968417
While it may not directly answer some of the questions, the tools and info in the tutorial may shed some light on this subject (or give you a direction to start digging further).
Click to expand...
Click to collapse
OMG, I'm getting senile... I came across this months ago, but at that point didn't know what I was looking at... and didn't see it just now in any stickies... thanks man.
mattk_r said:
OMG, I'm getting senile... I came across this months ago, but at that point didn't know what I was looking at... and didn't see it just now in any stickies... thanks man.
Click to expand...
Click to collapse
Yeah, never figured out why that one was never made a sticky. I just know to go look at Faria's sig and it (and a few other good links) are in there
Hi All,
Here is my second contribution to the Android community, android2sd!
I tried to make the installation a bit more straight forward and the readme very verbose.
There is NO going into recovery and wiping of the Android to install this construct. (Of course you can if you want to have a clean slate to build from but it is by your choice only!)
Remove .zip from filename, then unrar (sorry to zip users, zip was too big) the package and copy the android2sd.sh install script to the Android say /data/local and make executable with something like chmod 0750 and copy the android2sd.img install image to the sdcard. (Detailed instructions are in the readme file.) Once the install is complete, you can delete both install files.
Execute the script {where ever you installed it}ie:
/data/local/android2sd.sh and follow the instructions.
Included are several of my scripts (updated from the ones in data2sd) and the rules still apply, adjust or remove as you see fit. The readme explains them all.
I have noticed an improvement in speed based on the install, but you can judge for yourself and tweak as you see fit!
The construct uses Overlay Profiles to overlay the Android system and thus any changes to the Android once loaded, are actually done to the overlay profile thus you have like a safe mode which is the untouched Android under the overlay.
Hope you find it useful!
Darkstrumn
Darkstrumn said:
Hi All,
Here is my second contribution to the Android community, android2sd!
I tried to make the installation a bit more straight forward and the readme very verbose.
There is NO going into recovery and wiping of the Android to install this construct. (Of course you can if you want to have a clean slate to build from but it is by your choice only!)
Remove .zip from filename, then unrar (sorry to zip users, zip was too big) the package and copy the android2sd.sh install script to the Android say /data/local and make executable with something like chmod 0750 and copy the android2sd.img install image to the sdcard. (Detailed instructions are in the readme file.) Once the install is complete, you can delete both install files.
Execute the script {where ever you installed it}ie:
/data/local/android2sd.sh and follow the instructions.
Included are several of my scripts (updated from the ones in data2sd) and the rules still apply, adjust or remove as you see fit. The readme explains them all.
I have noticed an improvement in speed based on the install, but you can judge for yourself and tweak as you see fit!
The construct uses Overlay Profiles to overlay the Android system and thus any changes to the Android once loaded, are actually done to the overlay profile thus you have like a safe mode which is the untouched Android under the overlay.
Hope you find it useful!
Darkstrumn
Click to expand...
Click to collapse
Damn man. Good work.
sounds interesting, what is this all about?
brilliant?!? I think.
So basically, this is a non-destructive method that enables us to run new roms on the G1 without flashing? Am I reading this right? If so... wow.
edit: or, erm... maybe not... i think i've been up too long. Gonna have to watch this thread to get a better grasp on this. interesting nonetheless.
Rename To RAR
Darkstrumn said:
Remove .zip from filename, then unrar (sorry to zip users, zip was too big) the package and copy the android2sd.sh install script to the Android say /data/local and make executable with something like chmod 0750 and copy the android2sd.img install image to the sdcard. (Detailed instructions are in the readme file.) Once the install is complete, you can delete both install files.
Click to expand...
Click to collapse
very interesting .. at first i failed to see this part as i'm sure many pay skip over the whole "rename to rar" thing - LOL - so this loads profiles from the SD to the phone
for anyone having trouble with the whole "rename" process try this:
http://files.lucidrem.us/jf/android2sd.rar
as i know windows with hidden file extensions does not allow a rename easily
So what exactly does this do? I see install instructions, but no description.
Overlay Profiles...
tr.slate said:
So what exactly does this do? I see install instructions, but no description.
Click to expand...
Click to collapse
Well,
I've worked up the natural progression to this XXX2SD business, and have made an Android2SD construct which can expand the Android similarly to the the previous constructs, but puts /system, /data and /cache on sd.
So let me explain the overlay thing:
An overlay profile is a snapshot of the Android file system, namely /system, /data, and /cache.
The initial profile is called 'android2sd' and is a snapshot of your android at the time of install, plus the file system structure as explained in the readme adding the mnt/ dir structure and additional scripts in bin/ (which you can remove or adjust as you need).
Typically I reckon folks would only have the one profile and under it your original Android. But you can create additional profiles and set them up however you like. The overlay is overlayed on top of the Android file system with any changes or edits to the system affecting the profile and not the Android under.
The effective change is that the /system /data/, cache are moved to the sdcard thus expanding them to however large your sdcp2 is; on a class 6 card also improving access time.
A second benefit is that the underlying Android is safe from alteration and can be booted into like a 'safe mode'. (It can also serve as the base for new profiles, or you can make new profiles from active overlays. These snapshots can serve as a form of backup, but that is a fringe benefit.
It cannot protect the Android from update.zip installs exactly, as those will modify the Android directly, but say you try a theme and it gafs your 'droid...you can reapply the firmware update to clean out the theme, then copy the desired profile back to the Android and restore the Android to the state of the profile. (I would recommend having a 'base' profile of the Android but not using that as an active profile which will thus serve as a backup) Note: To restore the Android as described above, you cannot restore using a profile with 250+ apps in /data as the Android doesn't have the space for it!
Originally I used unionfs for the overlays but it was too slow.
Hope that explains things here; the readme has far more detail.
I've gotta go, but if I see that I've been as clear as mud, I'll try to explain better when I have more time.
Hmm just out of curiosity: What are you using now? Bind mounts?
I got a little bit lost in setup, I am not sure if I had problems because I was using Cyanogens latest or something else but either way Im going back to JF to try this.
I installed it using the "-COMMIT" addition
But when I made it to installing/linking apps things wouldnt link
Maybe I will let a few other people try it first.
More info...
[email protected] said:
Hmm just out of curiosity: What are you using now? Bind mounts?
Click to expand...
Click to collapse
Yes. Originally it was to have a multi profile layered system using unionfs: union0 the ro base snapshot and union1 the rw profile containing the copy-on-write data. But as the tests went on, the unionfs was too slow to use for /data; Android is unforgiving of unresponsiveness and was ANR'ing the apps that didn't respond fast enough.
The faster bind mount means that union1 is now not used and union0 is rw.
The reason I wanted the union0,union1 path was that the union0 could serve as base and various profiles could be layered over any part of the file system granting "Lego" like flexibility in how the user could adjust their a2sdLoader.sh script (the android2sd loader which controls the overlay process).
You could have a pristine base and several "change" profiles that you layered to your liking and could change any sub layer to different effect.
While you still can under this paradigm, it is not as compact.
But the unionfs option is not completely done away with. It can still be used for the above layering but shouldn't be used for that apps and package system.
An example of the layering I'm on about:
The Android 0-layer which the base layer is a snapshot of.
The base layer is pristine (fully configured settings, but minimal apps loaded, maybe a particular base launcher layout and wallpaper).
A change profile containing my apps and package system
A change profile containing a version of etc with reconfigured bluetooth settings.
A change profile with a theme (manually installed, or snapshot to profile and restored to pristine)
Now I could take these 4 profiles and arrange several different setups:
'base' with all apps loaded, themed with custom bluetooth
'base' with all apps loaded, themed with normal bluetooth
'base' with all apps loaded with custom bluetooth
'base' with all apps loaded with normal bluetooth
'base' with all apps loaded
'base' themed with with custom bluetooth
'base' themed with normal bluetooth
'base' with custom bluetooth
'base' with normal bluetooth
...
Those would be set to serve as the ro union0 and the rw union1 which will hold the copy-on-write changes to the overlay (which preserves the sub layers)
You could have several more theme profiles and have a script that randomly chooses one at boot...
You could simply use the overlay to protect a favored configuration. Should anything untoward happen such as accidentally damaging the packages.xml file while experimenting with the system, you could simply delete the change profile, make a new blank change profile and the damaged files are undone.
The things one can do with the overlay concept are limited only by your imagination and need (and if they slow down app processing too much causing ANR's)
It vary well could if done correctly allow one to have multiple roms as profiles and switch them based on the selected profile, but I have yet to experiment on that...I reckon that is my next move! (Note that this path would have a high space cost as the roms are about 40MB zipped!)
brandenk said:
I got a little bit lost in setup, I am not sure if I had problems because I was using Cyanogens latest or something else but either way Im going back to JF to try this.
I installed it using the "-COMMIT" addition
But when I made it to installing/linking apps things wouldnt link
Maybe I will let a few other people try it first.
Click to expand...
Click to collapse
Taken from [Rom] CyanogenMod:http://forum.xda-developers.com/showthread.php?t=518851
"DO NOT RUN ANY OTHER APPS2SD APPLICATIONS ON THIS BUILD. YOU WILL BREAK YOUR SYSTEM. THEY ARE NOT NECESSARY BECAUSE THIS ROM WILL DO A2SD AUTOMATICALLY AND BETTER!"
The android2sd construct pretty much falls into the A2SD category and thus is likely the reason you had issues with the install.
My Android is based on JF 1.51... and thus your mileage will vary based on the rom you are using. I reckon with a rom derived from theh JF roms, the install may work as intended.
As I go into the next construct build process, I will see if I can't make it multi-rom compatible (to support multi-rom profiles) I'm sure it will take some time to do as I would have to use my actual Android to test with, but no worries!
Hope that helps a little. Sorry it's not better news though.
An excellent "misuse" of this concept would be to run ion (picking it for its speed and almost stock nature) with a hero overlay (picked due to known instability as we are still developing it) so that ion would serve as a "safe mode" for when you crash hero.
I have a spare phone if i crash this and a secondary sd for if that gets corrupted. Let me know if you need help testing.
twistedumbrella said:
An excellent "misuse" of this concept would be to run ion (picking it for its speed and almost stock nature) with a hero overlay (picked due to known instability as we are still developing it) so that ion would serve as a "safe mode" for when you crash hero.
Click to expand...
Click to collapse
Interesting thought, and if this could be done, I suppose it would be possible to have bluetooth working in ION while using a Hero overlay?
Request for feedback...
Hi All,
Those who've installed android2sd, how is it going?
Can you give some pros and cons of your experience so I may improve things going forward? (Hopefully no cons exists!)
I know that roms that already make use apps2sd will encounter issues as the apps2sd and android2sd function similarly and thus step on each other. I may be able to detect this condition and adjust for it going forward...we'll see.
Thanks in advance for your input!
Darkstrumn
LucidREM said:
very interesting .. at first i failed to see this part as i'm sure many pay skip over the whole "rename to rar" thing - LOL - so this loads profiles from the SD to the phone
for anyone having trouble with the whole "rename" process try this:
http://files.lucidrem.us/jf/android2sd.rar
as i know windows with hidden file extensions does not allow a rename easily
Click to expand...
Click to collapse
Thanks for putting the rar up, XDA wouldn't take the .rar and I didn't want to signup to a file-share site just yet.
And it being seemingly natural to make windows show file extensions, it didn't cross my mind to make a note about that.
Thanks again!
Darkstrumn said:
Thanks for putting the rar up, XDA wouldn't take the .rar and I didn't want to signup to a file-share site just yet.
And it being seemingly natural to make windows show file extensions, it didn't cross my mind to make a note about that.
Thanks again!
Click to expand...
Click to collapse
How come no one is trying this? It seems to me an excellent idea and would be really cool to boot mutipe roms if someone figures that out. I'm not testing this because I'm using appstosd and didn't want conflicts...but no one else with jf1.51 Rom is testing this idea?
Just curious
so wait a second. let me get this straight ... if I have a class 6 8gb card i might be able to install a hero build without rosie or widgets with the original launcher on the sd card that might actually come sorta, kinda, a little close to a speed that might be bearable? at least for like 5 minutes?
Can this be adapted to install bigger roms such as hero without the dangerspl .
XD
Ill try this with ion later tonight
wow this is beautiful work! now to test it!
Im trying so hard to understand this lol.. Correct me on my errors but from what i read this is my hypothesis on what i think this does..
This is like a apps2sd but with data and that type thing from the build we are using? And you Said this takes snapshots So we can create several profiles of the phone? Like for example have a profile with some apps loaded and another profile with all removed and be able to switch between them at will?
Is it possible. I have a magic so no keyboard here... I cant execute the commands needed to perform switchrom.sh. If it could be integrated in the menu it wold be much appreciated.
It seems more complete backup as it packages the /system/sd folder...
You can execute commands with the adb shell command. So you are only limited to where adb is, ie next to a computer/laptop.
I know cyan has mentioned adding the ability to select a nandroid back up to restore to his next recovery image, i just figured with how actively he is developing his donut rom he hasnt had time. I am sure once things slow down with the rom we will get his next recovery image "when its ready"
if possible this would be a wonderful addition to the already elegant recovery image, not that going into terminal or using adb is overly difficult especially the way the script is setup, but im always looking to have it one click shorter
zambezy said:
Is it possible. I have a magic so no keyboard here... I cant execute the commands needed to perform switchrom.sh. If it could be integrated in the menu it wold be much appreciated.
It seems more complete backup as it packages the /system/sd folder...
Click to expand...
Click to collapse
And this is why I think the HTC Magic is a step down from the G1. Both the same except one has a keyboard and the other doesn't... pointless.
However... good request.
jugg2000 said:
And this is why I think the HTC Magic is a step down from the G1. Both the same except one has a keyboard and the other doesn't... pointless.
However... good request.
Click to expand...
Click to collapse
It also has more memory...
mer6 said:
It also has more memory...
Click to expand...
Click to collapse
Memory is not such a big issue, running aps2sd and linux-swap makes the G1 cope just as well with everything. I would say that my G1 runs faster than my wife's Magic with the same cyanogen ROM.
IMO the biggest "upgrade" is the battery: much longer life and charges faster. HUGE difference!
Another nice feature is the glowing trackball (I'm jealous).
OK, enough with this off-topic. I second the request for integrating switchrom in the recovery. (and I would like to add a request for the ability to restore ANY nandroid backup).
pascanu said:
Memory is not such a big issue, running aps2sd and linux-swap makes the G1 cope just as well with everything. I would say that my G1 runs faster than my wife's Magic with the same cyanogen ROM.
IMO the biggest "upgrade" is the battery: much longer life and charges faster. HUGE difference!
Another nice feature is the glowing trackball (I'm jealous).
OK, enough with this off-topic. I second the request for integrating switchrom in the recovery. (and I would like to add a request for the ability to restore ANY nandroid backup).
Click to expand...
Click to collapse
lol cyanogen is pretty busy, I'm sure hes fiddling with Roms so much he finds little time for anything else, this including recovery images which have
"switchrom" built into them
Wouldn't this a better directed at amen_ra in the magic section?
twistedumbrella said:
Wouldn't this a better directed at amen_ra in the magic section?
Click to expand...
Click to collapse
well id like that feature in a recovery image too. it would make it a lot more convenient and cyan is the man when it comes to recovery images (and everything g1)
i love switchrom... i got a second g1 last night, got it rooted, new spl, new radio, and got everything up and running. decided to pull one of my backups from my actual g1 and try to flash it. pulled it from my normal g1, put it on sdcard/switchrom/ and voila! it worked. now im immediately back to where i was. switchrom definitely makes things a little easier.
palosjr said:
i love switchrom... i got a second g1 last night, got it rooted, new spl, new radio, and got everything up and running. decided to pull one of my backups from my actual g1 and try to flash it. pulled it from my normal g1, put it on sdcard/switchrom/ and voila! it worked. now im immediately back to where i was. switchrom definitely makes things a little easier.
Click to expand...
Click to collapse
... you can easily do that with nandroid.
persiansown said:
... you can easily do that with nandroid.
Click to expand...
Click to collapse
i know. just letting it be known that it works
persiansown said:
... you can easily do that with nandroid.
Click to expand...
Click to collapse
Nandroid doesn't backup your ext partition with all your apps.
I don't know how anyone would integrate switchrom, you still need to type to name your backups. I personally would like it just for the fact I wouldn't have to mount system/sd then type the path out and what not
pascanu said:
OK, enough with this off-topic. I second the request for integrating switchrom in the recovery. (and I would like to add a request for the ability to restore ANY nandroid backup).
Click to expand...
Click to collapse
Dumfuq has taken the great innovations started by devsk and, IMO, completed the switchrom script. You can now backup/restore only nandroid, only ext, or both, along with other advanced options included. This script is not in that thread's OP, so you need to go HERE to get it. I've already PM'd cyanogen about it, so he's aware.
B-man007 said:
well id like that feature in a recovery image too. it would make it a lot more convenient and cyan is the man when it comes to recovery images (and everything g1)
Click to expand...
Click to collapse
That's nice... even though the original op request was due to the lack of hardware keyboards, which a G1 has. You go ahead and put all your faith in one guy who is busy as is, and ill release the integrated switchrom version I made to everyone else k?
Speaking of which
Zero Enhanced Recovery Images:
G1: http://twistedumbrella.slackdev.com/Zero_DRC-1.0.img
MT3G: http://twistedumbrella.slackdev.com/Zero_HRC-1.0.img
To use switchrom on these, run "sh sbin/switchrom.sh"
This will list the available commands for future use
This is only until I integrate the menu option directly
Original Thread: http://forum.xda-developers.com/showthread.php?p=4365404#post4365404
twistedumbrella said:
That's nice... even though the original op request was due to the lack of hardware keyboards, which a G1 has. You go ahead and put all your faith in one guy who is busy as is, and ill release the integrated switchrom version I made to everyone else k?
Speaking of which
Zero Enhanced Recovery Images:
G1: http://twistedumbrella.slackdev.com/Zero_DRC-1.0.img
MT3G: http://twistedumbrella.slackdev.com/Zero_HRC-1.0.img
To use switchrom on these, run "sh sbin/switchrom.sh"
This will list the available commands for future use
This is only until I integrate the menu option directly
Original Thread: http://forum.xda-developers.com/showthread.php?p=4365404#post4365404
Click to expand...
Click to collapse
Impressive and quite amusing at the same time. Great work Twisted.
twistedumbrella said:
That's nice... even though the original op request was due to the lack of hardware keyboards, which a G1 has. You go ahead and put all your faith in one guy who is busy as is, and ill release the integrated switchrom version I made to everyone else k?
Speaking of which
Zero Enhanced Recovery Images:
G1: http://twistedumbrella.slackdev.com/Zero_DRC-1.0.img
MT3G: http://twistedumbrella.slackdev.com/Zero_HRC-1.0.img
To use switchrom on these, run "sh sbin/switchrom.sh"
This will list the available commands for future use
This is only until I integrate the menu option directly
Original Thread: http://forum.xda-developers.com/showthread.php?p=4365404#post4365404
Click to expand...
Click to collapse
is this the same as cyanogens and JF recovery with added switchrom or is it a completely new recovery image?
Why not just use Amon Ra's recovery image? Has alot more features than cyanogens one plus the switchrom you want. I used to hate mounting /system/sd before i backed up
Hey everyone,
With the intro of BFS302 and Cyan's almost stable rom, I figured it is time to do some testing w/ user.conf files on CM 4.1.99. I feel this is necessary because I notice that after ~12 hours or so, the phone really starts to lag and I have a suspicion it has something to do w/ compcache.
I WAS using the stock CM 4.1.99 setting (24mb compcache), and now I am trying a user.conf that uses 64mb compcache w/o backing swap.
Anyone have any good settings\configs that have worked well for them AFTER SEVERAL HOURS OF USE?
The phone always seems to be quick after bootup and a taskkill, but after a few hours (possibly when compcache gets full) it starts to act sluggish
EDIT: Now that 4.1.999 is out, what is everyone using for user.conf settings?
EDIT2: Now that 4.1.9999 (and possibly more to come) is out, what is everyone using? I have added the corrected userinit.sh and my current conf file for reference if anyone wants.
zimphishmonger said:
Hey everyone,
With the intro of BFS302 and Cyan's almost stable rom, I figured it is time to do some testing w/ user.conf files on CM 4.1.99. I feel this is necessary because I notice that after ~12 hours or so, the phone really starts to lag and I have a suspicious it has something to do w/ compcache.
Click to expand...
Click to collapse
You are starting this testing thread on a ROM that has broken BFS and Compcache. This has been reportedly fixed by Cyanogen for the next update. Maybe it would be best to wait to try this when compcache is working efficiently again.
Oh, well thats good to hear. Hadnt heard anything about BFS or compcache issues yet. Anyway, guess we can continue testing once the new update comes out today.
Well to answer your question though, miketaylor00's user.def script has been working really well for me since I started using it...
http://forum.xda-developers.com/showthread.php?p=4334135#post4334135
Here's mine (Unix formatted, open in Notepad++). Running great on CM 4.1.99 for almost 2 days now w/o rebooting. Everything's still smooth and responsive.
Here are the highlights:
...
# 32MB cc with 24MB backing swap on Linux-swap partition
compcache_en=1
cc_disksize=32
cc_memlimit=24
cc_backingswap_en=1
cc_backingswap=/dev/block/mmcblk0p3
cc_swappiness=60
...
# swapfile off
swap_file_en=0
...
# swap partition off
linux_swap_en=0
...
# Defaults here
proc_cpu_en=1
scaling_min_freq=245760
scaling_max_freq=528000
sampling_rate=2000000
powersave_bias=200
up_threshold=40
...
I've also had good results with up_threshold set at 32. I'm also running the "extra memory" kernel hack, so that might be a contributing factor.
After messing with user.conf last night and all day yesterday, it seems the best solution is to just disable CC and enable linux swap or nothing at all until the update is released.
Thanks for your opinions and experiences. I have had 2 kernel panics\reboots today using stock settings, switched to a user.conf file I was using before to see if there is any difference. Lookin forward to the new release tonite though
bump because of new update
zimphishmonger said:
bump because of new update
Click to expand...
Click to collapse
Send me the default file and I'll send you my recommendation. I don't have time to load Cyanogen but I've been testing similar ROMs and I am testing the same BFS patch right now. I've found that BFS performs about the same with the same settings whether it is on Hero or Donut or Cupcake. I may not get you the optimal settings but it will be close and you can build from there.
The stock doesnt have a user.conf file, it just enables compcache 24mb by default (I believe). I usually use a slightly modified version of your user.conf file. I changed the cpu to 254760, and the swappiness to 60 (Just changed for testing).
I have a 64mb swap parition on a class 4 SD that is being used as a backing swap. I cant figure out if a backing swap is helping or not, as the lag happens after being booted for 8+ hours (usually overnight)
zimphishmonger said:
The stock doesnt have a user.conf file, it just enables compcache 24mb by default (I believe). I usually use a slightly modified version of your user.conf file. I changed the cpu to 254760, and the swappiness to 60 (Just changed for testing).
I have a 64mb swap parition on a class 4 SD that is being used as a backing swap. I cant figure out if a backing swap is helping or not, as the lag happens after being booted for 8+ hours (usually overnight)
Click to expand...
Click to collapse
Keep the 64MB swap and try the settings from JacHeroSki. See how that runs for a while. What are you using for your CC memlimit? Are you still having problems on the 999 build?
miketaylor00 said:
Keep the 64MB swap and try the settings from JacHeroSki. See how that runs for a while. What are you using for your CC memlimit? Are you still having problems on the 999 build?
Click to expand...
Click to collapse
Havent seen any issues on 999 build yet, but as I said, it happens after a while (when the compcache gets full and uses the backing swap, I assume). Anyway you can post the user.conf for jacherski? Is it different then xROM1.5r4 or r3?
Regarding CC_memlimit, I am currently using 24. Recommended?
zimphishmonger said:
Havent seen any issues on 999 build yet, but as I said, it happens after a while (when the compcache gets full and uses the backing swap, I assume). Anyway you can post the user.conf for jacherski? Is it different then xROM1.5r4 or r3?
Regarding CC_memlimit, I am currently using 24. Recommended?
Click to expand...
Click to collapse
Yes, BFS completely changes the game with the user.conf. Try this one out. The format might not be right so you will probably need to just copy the settings over. That's why I was going to have you send the original. I'm too lazy/busy to download and extract the CM file. But here is my BFS user.conf. I'm betting the upped CC Memlimit will probably help you out quite a bit.
Much appreciated, will 'convert' it and let ya know how it works out over the next day or so. Lookin forward to playing w/ the new xROM whenever that comes out
Zim, did you see my post in the Compcache vs. Linux vs. Stock thread? If not, check it out. It explains it a little better. I should start another thread on tuning BFS ROMs and post what I know. JacHeroSki is so fast that I'm using it as my daily ROM now. We just need to make it more stable and it will be perfect.
miketaylor00 said:
Zim, did you see my post in the Compcache vs. Linux vs. Stock thread? If not, check it out. It explains it a little better. I should start another thread on tuning BFS ROMs and post what I know. JacHeroSki is so fast that I'm using it as my daily ROM now. We just need to make it more stable and it will be perfect.
Click to expand...
Click to collapse
I agree, BFS really has given Android a whole new lease on life. So snappy. I would love to use JacHeroSki full-time, but I rely on a Bluetooth headset occasionally, so thats a deal killer....but I do have a switchrom image that I continually update to see whats new
Will check out that post, but you should start another thread about tweaking specifically w/ BFS. Seems to be gaining universal acceptance in the community, and it def changes the game around.
zimphishmonger said:
I agree, BFS really has given Android a whole new lease on life. So snappy. I would love to use JacHeroSki full-time, but I rely on a Bluetooth headset occasionally, so thats a deal killer....but I do have a switchrom image that I continually update to see what you new
Will check out that post, but you should start another thread about tweaking specifically w/ BFS. Seems to be gaining universal acceptance in the community, and it def changes the game around.
Click to expand...
Click to collapse
I'm really interested to see how those settings run on the latest Cyan. I have been wanting to tune it but I haven't had the time. That ROM is a lower priority for me because only a handful of people seem to want me to offer my suggestions on it. Cyanogen seems to want to stick to compcache only so I've left it alone for the most part.
copied and updated my user.conf file. Seems a lil more snappy right off the bat now. Will report back w/ long term results.
I currently use Cyanogen full-time, but I do occasionally have a habit of switching back and forth to xROM.
zimphishmonger said:
copied and updated my user.conf file. Seems a lil more snappy right off the bat now. Will report back w/ long term results.
I currently use Cyanogen full-time, but I do occasionally have a habit of switching back and forth to xROM.
Click to expand...
Click to collapse
Could you upload your updated user.conf file?
sacredsoul said:
Could you upload your updated user.conf file?
Click to expand...
Click to collapse
I am messing around w/ some Hero stuff at the moment, so I cant access my user.conf. Its pretty easy to modify miketaylor's previously released .conf, however. Ill attach my previous user.conf and you can just take the setting from miketaylor's attached one (above)
My bad in advance if this question is off topic.
Lets you say you flashed the stock rom [why i don't know] or one of the roms hanging around here. The RUU goes to 100%, you set the screen, the time, you get a peek at the home screen (lookin pretty plain there) only to be told to wait 3 seconds. A couple things run get a little progress indicator and the thing reboots.
Now your home screen is looking different. Couple plugins enabled, others disabled. Been scouring XDA regarding this and only found scant references here or there about setting your thing up to install cabs off an SD card. I'm looking for something more in the neighborhood of having different plugins enabled, possibly settings too.
Anywho if you know of where I can get some reading in about this type of stuff, lemme know.
It's the built-in autorun. There are also many different third party alternatives. A few are in SuperJustKitchen v0.7.
Besides that, I'm trying to decide if this is offtopic or not... Technically it has to do with cooking....
ivanmmj said:
It's the built-in autorun. There are also many different third party alternatives. A few are in SuperJustKitchen v0.7.
Besides that, I'm trying to decide if this is offtopic or not... Technically it has to do with cooking....
Click to expand...
Click to collapse
hehe i'm walking a fine there...
I was wondering who were those guys and what are they doing in my kitchen? Autorun, check autorun, and run cc From what I gathered about those programs is that runcc is like autorun but newer. My guess in using them is setting up some sort of txt file and pointing runcc or autorun to it.
If so what can I put in that txt file, coz I know i can't write something like "uh... dood, I don't want titanium enabled, I want this one enabled with this setting and that setting ticked... and while you're at it can you fiddle with that one over there, and lets throw some cabs on there shall we? they're over here..... you're not done yet, now I want you to monkey with the settings like so... alright now get the hell out of my office!"
If I could I would...
Whatever information you can point me over to would be cool.
Thanks
Dr.Gonz0 said:
hehe i'm walking a fine there...
I was wondering who were those guys and what are they doing in my kitchen? Autorun, check autorun, and run cc From what I gathered about those programs is that runcc is like autorun but newer. My guess in using them is setting up some sort of txt file and pointing runcc or autorun to it.
If so what can I put in that txt file, coz I know i can't write something like "uh... dood, I don't want titanium enabled, I want this one enabled with this setting and that setting ticked... and while you're at it can you fiddle with that one over there, and lets throw some cabs on there shall we? they're over here..... you're not done yet, now I want you to monkey with the settings like so... alright now get the hell out of my office!"
If I could I would...
Whatever information you can point me over to would be cool.
Thanks
Click to expand...
Click to collapse
RunCC is meant as a replacement for Autorun. Autorun just requires a text file while RunCC requires a Lua that points to a text file.
There are a few walkthroughs but nothing concrete on how to create a good autorun file.
Some of the commands are:
The lock screen command (I forget what it is)
EXEC: (Execute the following)
CAB: (Install the following cab)
CPY1: (Copy from this)
CPY2: (Paste to this)
RST: (reset the phone)
In the older Autoruns, to set a theme you'd use:
EXE: along with a program that set the theme
In the newer Autoruns, you can just set it with:
TSK: \Windows\theme.tsk
Unfortunately, neither works with WM6.5.1 so you have to set the theme with an EXT with many files and registry keys.
There are a few other autorun apps that people in xda have made that can do more, like be able to run your own custom config from your SD card if you want every ROM to have certain things automatically configured (as long as all the ROMs support the particular auto-configuration utility you have configured for.)
To tell you the truth, I never bothered much with Autorun unless I had to replace a file that needed to be one version for the rom to load the first time and another after the first time set up was done. Realistically, you can do almost everything with a simple EXT package.
ivanmmj said:
Unfortunately, neither works with WM6.5.1 so you have to set the theme with an EXT with many files and registry keys.
Click to expand...
Click to collapse
Now ain't that a kick in the pants
ivanmmj said:
To tell you the truth, I never bothered much with Autorun unless I had to replace a file that needed to be one version for the rom to load the first time and another after the first time set up was done. Realistically, you can do almost everything with a simple EXT package
Click to expand...
Click to collapse
I was thinking the very same thing. Something's telling me that I need to try out that "Create Ext" button. Maybe throw whatever reg keys I want played with in that file? That would be more simpler than creating an auto run thingie. Hmmm... if that is the case I guess I would to just need to know how to tinker with my home screen and settings from the registry.
Dr.Gonz0 said:
Now ain't that a kick in the pants
I was thinking the very same thing. Something's telling me that I need to try out that "Create Ext" button. Maybe throw whatever reg keys I want played with in that file? That would be more simpler than creating an auto run thingie. Hmmm... if that is the case I guess I would to just need to know how to tinker with my home screen and settings from the registry.
Click to expand...
Click to collapse
The easiest way to learn is to take a CAB that does something you like and converting into a EXT and looking at the registry settings it creates.
ivanmmj said:
The easiest way to learn is to take a CAB that does something you like and converting into a EXT and looking at the registry settings it creates.
Click to expand...
Click to collapse
That definitely helps, as well as using a reg editor to find out what has been done after installing a program then exporting the key to throw in the app.reg file. The real fun part was tracking down basic settings for things like button settings, today items (and their settings), and default theme (boy was that a blast!) Thanks again for clearing up the confusion