Background..
With any linux system i build first thing i do is remove the journal from all my EXT4 partitions, to make a long story short ( i wont bore you with details of just how journal writes totally slow disk i/o , google it ) this gave me on average a 25% increase in system speed ( obviously due to the increased i/o rate )
I usually did it with
Code:
mke2fs.ext4 -O ^has_journal ...device...
before installing the distro, now i thought hey maybe this would work on android?
Now mke2fs is not well supported on arm but tune2fs is! in fact its included in TWRP 2.5 so
Code:
tune2fs -O ^has_journal /dev/block/platform/sdhci-tegra.3/by-name/APP
( for the system partition) should work right , and in fact yes it does !!!, tried it from TWRP command line and hey presto %^$%^$^%$ FAST system
This is the code for a recovery script version
Code:
ui_print("test script");
ui_print("");
ui_print("");
ifelse(is_mounted("/system") == "/system", unmount("/system"));
ifelse(is_mounted("/cache") == "/cache", unmount("/cache"));
ifelse(is_mounted("/data") == "/data", unmount("/data"));
ui_print("converting partitions to ext4 minus journal");
ui_print(" ");
set_progress(1.000000);
ui_print("e2fsck system partition");
ui_print(" ");
run_program("/sbin/e2fsck", "-p", "/dev/block/platform/sdhci-tegra.3/by-name/APP");
ui_print("e2fsck data partition");
ui_print(" ");
run_program("/sbin/e2fsck", "-p", "/dev/block/platform/sdhci-tegra.3/by-name/UDA");
ui_print("e2fsck cache partition");
ui_print(" ");
run_program("/sbin/e2fsck", "-p", "/dev/block/platform/sdhci-tegra.3/by-name/CAC");
ui_print("now lets rub out those nasty journals");
ui_print(" ");
run_program("/sbin/tune2fs", "-O", "^has_journal", "/dev/block/platform/sdhci-tegra.3/by-name/APP");
run_program("/sbin/tune2fs", "-O", "^has_journal", "/dev/block/platform/sdhci-tegra.3/by-name/UDA");
run_program("/sbin/tune2fs", "-O", "^has_journal", "/dev/block/platform/sdhci-tegra.3/by-name/CAC");
ui_print("and re-fsck to clean any set bits");
ui_print(" ");
ui_print("e2fsck system partition");
ui_print(" ");
run_program("/sbin/e2fsck", "-p", "/dev/block/platform/sdhci-tegra.3/by-name/APP");
ui_print("e2fsck data partition");
ui_print(" ");
run_program("/sbin/e2fsck", "-p", "/dev/block/platform/sdhci-tegra.3/by-name/UDA");
ui_print("e2fsck cache partition");
ui_print(" ");
run_program("/sbin/e2fsck", "-p", "/dev/block/platform/sdhci-tegra.3/by-name/CAC");
And i include a zip for those who like to test
Ps have not checked the function of this line
Code:
run_program("/sbin/tune2fs", "-O", "^has_journal", "/dev/block/platform/sdhci-tegra.3/by-name/APP");
the bash equivalent is
Code:
tune2fs -O ^has_journal /dev/block/platform/sdhci-tegra.3/by-name/APP
where ^has_journal is a parameter of -O not sure the recovery script is wrapping that correctly, if anyone flashes this script could you please check by typing
Code:
tune2fs -l /dev/block/platform/sdhci-tegra.3/by-name/APP
in the TWRP terminal, scroll upward with an up finger swipe and check has_journal is not in the filesystem properties ( going to do it myself on next system wipe, but just enjoying the speed at the mo !! , am testing it on PRIME 04-20 mildly tweaked by me )
Thanks
Edit ... Since there has been more than passing interest in this obscure piece of code i have decided to tidy this post up
Hence now there are 2 scripts, one to remove the journal from your ext4 partitions, and one to re-instate the journal, this should allow people to test their setup with each without any wiping or reformatting
Instructions.......
( tested with TWRP 2.5+ only )
Flash the bugger
DO NOT WIPE ANYTHING, after flashing, doing so will only reformat the wiped partition with a journal
For us who have no background in Linux. What is this for? Does it just increase system speed? I'm running prime 4/20 as well and would definitely like to test it once I know exactly what it's supposed to do.
JetOhmNet said:
For us who have no background in Linux. What is this for? Does it just increase system speed? I'm running prime 4/20 as well and would definitely like to test it once I know exactly what it's supposed to do.
Click to expand...
Click to collapse
No linux was just for explanation.
But it also work for Android.
So that's a good thing
The script he has posted is for twrp.
JetOhmNet said:
For us who have no background in Linux. What is this for? Does it just increase system speed? I'm running prime 4/20 as well and would definitely like to test it once I know exactly what it's supposed to do.
Click to expand...
Click to collapse
It forgoes recording disk writing (?) operations to a journal and instead writes things directly to disk (or a buffer, if you want to be pedantic).
Instead of going:
Write to journal (I'm doing this write) -> Write to journal (I'm currently doing this write) -> execute operation -> erase entry from journal
It goes:
Execute operation
The end result is greater write speeds, but greater risk of data loss if there is power loss.
If you were in the middle of a write operation when the power goes dead, the journal entry saying that you were doing something will still be there, so the OS can either resume/restart the operation (since it knows it was incomplete) or do some sort of error handling since it knows something went wrong.
For more/related info, see this thread.
[email protected]_OC said:
No linux was just for explanation.
But it also work for Android.
So that's a good thing
The script he has posted is for twrp.
Click to expand...
Click to collapse
I got that much, just wasn't convinced on what exactly this script does.
psyren said:
It forgoes recording disk writing (?) operations to a journal and instead writes things directly to disk (or a buffer, if you want to be pedantic).
Instead of going:
Write to journal (I'm doing this write) -> Write to journal (I'm currently doing this write) -> execute operation -> erase entry from journal
It goes:
Execute operation
The end result is greater write speeds, but greater risk of data loss if there is power loss.
If you were in the middle of a write operation when the power goes dead, the journal entry saying that you were doing something will still be there, so the OS can either resume/restart the operation (since it knows it was incomplete) or do some sort of error handling since it knows something went wrong.
For more/related info, see this thread.
Click to expand...
Click to collapse
And thank you on the specifics and pros and cons. I'll definitely give it a try now and let you know what I think/if i notice any bugs!
Sorry, wrong post!
I was tring to send a message to a Razr owner but i bungled with the XDA app.
Thanks anyway for your reply.
yes will work on any android/linux system using ext4 partitions, in the case of n7 thats only system,data and cache.
But the actual TWRP script needs checking for syntax for every device. ( obviously checked it on the n7 )
I can confirm a MASSIVE speed increase, everything in noticeably smoother and faster, which is to be expected since you have increased disk i/o by at least 25%, especially important in the data and cache partitions.
To really understand whats going on you really must google EXT4 and the journal folk's, a journaling filesystem is a legacy of the linux server heritage, its very useful in a server context, if you have a crash and are running 100+ TB of data, the journal allows you to reboot and instantly be back online ( which is massively important is the server world where seconds offline means millions of dollars ) rather than wait many hours for a fsck to complete. For android it is completely inappropriate! it should be obvious why
Psyren's post is a good simple explanation of the write structure and how removing the journal speeds things up.
If this code goes into anyone's rom please give me some love in the credits
Ps as mentioned in the post there is a line to double check, if your doing it by hand from the TWRP terminal then i can confirm it def works, i have not double checked the script ( except to prove it flashes etc ) and wont for about a week, i am getting ready my own rom that concentrates on improving the linux sub-structure, and that's taking my time
Sorry if this is a stupid question, but does this wipe any partitions or will there be any data loss flashing the zip?
Or does it need to be flashed before flashing Rom?
Sent from my MB865 using xda app-developers app
elfrosto said:
Sorry if this is a stupid question, but does this wipe any partitions or will there be any data loss flashing the zip?
Or does it need to be flashed before flashing Rom?
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Flashing does not wipe anything, but I also haven't noticed any i/o improvements.
Looks like a very interesting script.. Could we do that from CWM or even from a terminal? If yes what would be the procedure? Thanks for sharing!
JetOhmNet said:
Flashing does not wipe anything, but I also haven't noticed any i/o improvements.
Click to expand...
Click to collapse
Could you please check the journal has been removed with a
Code:
tune2fs -l /dev/block/platform/sdhci-tegra.3/by-name/APP
at the TWRP terminal, thank you ( remember to scroll upwards and look for the line with fs properties )
The script stuffed up my nexus. I had a backup but just letting you know. It booted to the animation but went no further. Any benchmarks?
Sent from my Nexus 7 using xda premium
bcvictory said:
The script stuffed up my nexus. I had a backup but just letting you know. It booted to the animation but went no further. Any benchmarks?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hmm thats interesting, which rom you running ? You using TWRP ( im on 2.5 ) I tried it on my nexus and no problems, even with multi-rom in.
Can anyone suggest an appropriate benchmark prog to use please, ( something that tests io as-well as ui responsiveness ) and i will post results on the next wipe. Like i said i am def claiming a noticeable improvement on Prime 02-04 as far as ui is concerned, eg when i go to playstore and scroll my apps there is no longer any pause in the scroll, lots of other things like that, and all the "pages" of various apps come up faster. But really need a quantitative test.
Thanks
jubei_mitsuyoshi said:
Hmm thats interesting, which rom you running ? You using TWRP ( im on 2.5 ) I tried it on my nexus and no problems, even with multi-rom in.
Can anyone suggest an appropriate benchmark prog to use please, ( something that tests io as-well as ui responsiveness ) and i will post results on the next wipe. Like i said i am def claiming a noticeable improvement on Prime 02-04 as far as ui is concerned, eg when i go to playstore and scroll my apps there is no longer any pause in the scroll, lots of other things like that, and all the "pages" of various apps come up faster. But really need a quantitative test.
Thanks
Click to expand...
Click to collapse
Well can you write a how-to install this? I flashed the zip using Twrp 2.5 over the top of my PA install. Is that what we are meant to do?
If you are claiming io speed then maybe and io tester? (Can't think of one off the top of my head)
And an antutu just for kicks
Maybe a before and after?
Sent from my Nexus 7 using xda premium
So i forgot to run a benchmark prior to flashing this. Silly me. But here are my speeds after flashing. I'm running Prime (4–20) with faux ultimate kernel clocked at 1.7Ghz.
Also here are my Antutu and Quadrant marks:
JetOhmNet said:
So i forgot to run a benchmark prior to flashing this. Silly me. But here are my speeds after flashing. I'm running Prime (4–20) with faux ultimate kernel clocked at 1.7Ghz.
Click to expand...
Click to collapse
cool thanks for that Androbench def best in this category but readings can vary 50% or more per run, eg did 2 runs separated by seconds
run1 sqlite benchmark
insert 1052.63 TPS
Update 789.47 TPS
Delete 348.02 TPS
run2 sqlite benchmark
insert 617.28 TPS
Update 274.97 TPS
Delete 910.87 TPS
Maybe we should ignore " small differences " LOL
On the up side the RD/WRT stats only vary buy about 30% so should be a better guide.
Will have some before/after comparisons for you tomorrow,
On the subject tho should not a benchmark program have exclusive access to the system? ( which is impossible in android ) otherwise isnt it just reading and writing along side all the other system RW calls
PS.. how do you get the screenshots, would be useful for posting benchmarks
bcvictory said:
Well can you write a how-to install this? I flashed the zip using Twrp 2.5 over the top of my PA install. Is that what we are meant to do?
If you are claiming io speed then maybe and io tester? (Can't think of one off the top of my head)
And an antutu just for kicks
Maybe a before and after?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Well seems good to me, yes just flash it, do not wipe anything after since TWRP will reformat with a journal. To be honest i have no idea why it failed in your case, thought maybe it is a CM vs AOKP thing but just had a pm from a bloke on a CM clone that flashed great and having good results, so hey cant be that
THe only thing i can think of is the kernel, could be something tweaked in that causing a confusion between ext4-minus-juornal and ext2, that happened on very old linux kernels, but not seen that for years, so doubt that to.
If you can be bothered try again, post if you get the same result and i will give it a go with a PA when finish my little rom
jubei_mitsuyoshi said:
Well seems good to me, yes just flash it, do not wipe anything after since TWRP will reformat with a journal. To be honest i have no idea why it failed in your case, thought maybe it is a CM vs AOKP thing but just had a pm from a bloke on a CM clone that flashed great and having good results, so hey cant be that
THe only thing i can think of is the kernel, could be something tweaked in that causing a confusion between ext4-minus-juornal and ext2, that happened on very old linux kernels, but not seen that for years, so doubt that to.
If you can be bothered try again, post if you get the same result and i will give it a go with a PA when finish my little rom
Click to expand...
Click to collapse
I use M-Kernel. Don't wipe cache and dalvik?
Sent from my Nexus 7 using xda premium
jubei_mitsuyoshi said:
PS.. how do you get the screenshots, would be useful for posting benchmarks
Click to expand...
Click to collapse
Hold the power button and volume down simultaneously.
Related
A Very quick port of the Mytouch Slide Leak.
Credits : Vega, his files made it boot
Upload date 2010-04-22
Download at the bottom of this post
Very Quick 'status' list
Hangover edition v003c
WiFi - Fixed - honestly its fixed now
Market - Fixed - I know , I know , you have no reason to believe me
Theme Switching ( MyMode ) - Fixed
YouTube, sound no video
Gmail seems working, until you try to read one
Browser not working, stock or third party- looks like an issue with binder, this is what I want to fix next
the MyTouch Music player works
FullScreen weather - better , but sun 'shines' blue, idkw
Silly Bootanimation, - Replace by pushing to /data/local/bootanimation.zip
lots of other things untested/ not working
I'm sure that will be amended/appended
Main Features
MT3G friendly a2sd
CacheHack - 3 in 1 Flashable Zip
Auto swap ( you have a swap partition , it will find it and set it up )
AnySPL
[*]Eng/Hard/Stock aka NoneDanger
[*]Death/Haykuro aka Danger
[*]Any MT3G SPL
One zip does it all?
yeap,
I get the recovery program to run a shell script, this script looks at the size of mtdblock4 ( the 'cache' partition ) and then creates symbolic links based on what 'SPL' it has determined, then the rest of the ROM is flashed, the files follow the links and .. well its like someone sat down and thought about the best way to use the space
At some point I would like to look at getting that shell script generated so that it can very easy to apply to any rom.
Danger I do have to admit that the Danger version is a bit of a 'quick fix', around 20mb is idle on /system, I'll look at improving on that.
At the moment all the system apps are on data, but as app_IS, with a little bit of 'moving and re-linking' we can trigger a2sd to do its thing
Edit 2010-04-24: system apps are going to sd by default now
NoneDanger is as good as it can get on the G1, got a couple of mb free space on system, and that will likely improve as the 'bad apps' are weeded out
I currently have 37mb free on data, yeah I know for some reason people want this empty, why? its faster than sd
MT3G ok, so you don't have a keyboard , but space you have lots of space
The script will chop this 164mb rom in two and share it across /system and /cache leaving the 295mb /data partition free for dalvik-cache, user apps and setting/files
Download
######## MD5SUM ##########
#########################
72b53b0f3b16ea9e161e605b8dfe47d0
#########################
Uploading a new version
fingers crossed, working for everyone.....
FR-MTSlideTo32B-v003c-AnySPL_S.zip
NB, WiFi, themes (MyMode) and market
no browser yet...
#########################
Current Patches
###########
FR-FavesFix4-003c_S.zip
Should be able to flash straight after the main 'ROM', if it does fail, just reboot straight back to recovery and flash the fix again
#########################
Instructions !!
OK, this is a very early release, consider it Alpha, the ROM is Huge and as such it takes a good while for it to settle.
If you 'went in' a little early you will see FC's , and it will look real bad...
But trust me , its fine
Reboot by pressing call + end and then menu, and let it settle
One it gets settled in it actually does quite well, much better than I had hoped
and I have not done any tweaking yet, just got it to boot
Edit : 2010-04-24 - Its actually quite stable on a first boot now
But still give it a couple of minutes, and do the full sign in
( i.e. don't charge in to do a market sign in, never understood why that was needed )
Missing widgets?
probably 'logged in' a little too quick
if widgets seem to be missing, then
settings --> applications --> manage applications --> menu(key) --> filter --> all --> HTC sense --> clear data
should make them all available
Make Backups?
you need
[UTIL] BART-1.2.0 Backup and Restore Tool
Now supports backup and restore of CacheHack ROMs
Anyway, I hope you enjoy
feel free to use as a base,
32a Port - not confirmed working yet
Daneshm90 said:
Hey, any chance of a 32a port? thnx
Click to expand...
Click to collapse
Firerat said:
errm yeah
I'll have ago but I can't test
Click to expand...
Click to collapse
Firerat said:
FR-MTSlide-32a_S.zip
no idea if it works
Click to expand...
Click to collapse
Just a Kernel , so flash it last
A quick note on patching CacheHack ( or any ROM )
Just wanted to make a quick post on Patching this ROM, and any ROM for that matter
as stuff is on cache, and is in different places dependent on the SPL symlinks are are 'broken'
So, we fix them in the update script
mountall.sh
Code:
#!/sbin/sh
mount -a
if [ -d /system/csys ];
then
mount -o bind /cache /system/csys
fi
now, in your update-script the top line should read
Code:
run_program PACKAGE:mountall.sh
assuming that mountall.sh is in the root of the zip
now, when the update-script runs the mountall.sh
all partitions get mounted, and if /system/csys directory exists it bind mounts /cache to it
All of the symlinks will now work
so , if your replacing a file in /system/lib the link will be followed
Danger its actually /system/lib/
NoneDanger and MT3G its /cache/system/lib ( or /system/csys/system/lib )
this also means you can easily do
Code:
copy_dir PACKAGE:system
where in the zip
system/
system/lib/libWatstis.so
system/app/SomeSystem.apk
libWatstis.so ends up in the right place
as does SomeSystem.apk, even if its on the sd ,
( /system/app >> /data/app_s >> /system/sd/app_s )
in the past, to 'upgrade' a system app on sd, people would delete /data/app_s ( as it was a symlink ) which would break things for anyone not using a2sd
nb, the mountall script should be in unix format, else it will fail !!!
a third post
Silly edit is silly, will test out later.
So much win coming soon. Thanks for the post. Is the AnySPL a no-wipe from your first one?
I noticed I can't change scenes. Just does nothing-- is that me or a bug to be worked on? And the bloatware makes me think I bought an ATT phone all over again, lol. There's a lot of room for improvement. Just when I was getting bored with Legend, got a new toy to play with.
just checking before i get too far in this is the cfs-3d kernel on this rom already or do we flash that one over this rom also?
Let see
Giving this a try right now on my Mt3g... Will let you know how I go.
enatefox said:
So much win coming soon. Thanks for the post. Is the AnySPL a no-wipe from your first one?
Click to expand...
Click to collapse
Hmm, hadn't thought of that
/system and /cache get wiped by the script, but I leave /data alone
it might get touchy about it with no wipe
One of the things I want to do is the deal with the whole wipe thing, I personally don't wipe, if it works , if not then I wipe
do i still have to flash the kernel from the other post on top of it?
vortec87 said:
just checking before i get too far in this is the cfs-3d kernel on this rom already or do we flash that one over this rom also?
Click to expand...
Click to collapse
Oh, yeah, sorry its already got the CFS 3D
SmartBrother90 said:
do i still have to flash the kernel from the other post on top of it?
Click to expand...
Click to collapse
nvm i see the answer
Firerat said:
Oh, yeah, sorry its already got the CFS 3D
Click to expand...
Click to collapse
Thanks Firerat You are the MAN!
No incall volume...Looks really SICK!! Good job!!
this is for g1?
This will change your life. Run as root, thank me later
Code:
pm disable com.htc.htclocationservice/com.htc.htclocationservice.AutoSettingReceiver
pm disable com.htc.socialnetwork.provider/com.htc.socialnetwork.provider.SocialUpdateReceiver
pm disable com.tmobile.nabservice/com.tmobile.nabservice.NabSyncReceiver
pm disable com.tmobile.selfhelp/com.tmobile.selfhelp.BootCompletedReceiver
pm disable com.android.voicedialer/com.android.voicedialer.VoiceDialerReceiver
pm disable com.google.android.apps.maps/com.google.googlenav.friend.android.ServiceReceiver
pm disable com.htc.htclocationservice/com.htc.htclocationservice.AutoSettingReceiver
pm disable com.android.bluetooth/com.android.bluetooth.opp.BluetoothOppReceiver
pm disable com.htc.providers.uploads/com.htc.providers.uploads.UploadReceiver
pm disable com.google.android.apps.uploader/com.google.android.apps.uploader.common.ConnectivityBroadcastReceiver
pm disable com.android.voicedialer/com.android.voicedialer.VoiceDialerReceiver
pm disable com.tmobile.thememanager/com.tmobile.thememanager.receiver.ThemePackageReceiver
pm disable com.svox.pico/com.svox.pico.VoiceDataInstallerReceiver
pm disable com.android.voicedialer/com.android.voicedialer.VoiceDialerReceiver
pm disable com.htc.htclocationservice/com.htc.htclocationservice.AutoSettingReceiver
pm disable com.oz.mobile.android.voicemail.application/com.oz.mobile.android.voicemail.application.VoicemailBroadcastListener
pm disable com.htc.android.omadm.service/com.htc.android.omadm.service.StateReceiver
pm disable com.nuance.vsuite/com.nuance.vsuite.drivermode.MessageReceiver
pm disable com.tmobile.nabservice/com.tmobile.nabservice.SMSSyncService
u da man firerat! it works.
Thanks for this
Umm since there is no BootScreen how long does it usually take to boot ? because i am kinda iffy on weather i should wipe again and flash
(been booting for about 5 mins)
whats the diff between this one and the other slide rom?
This fast already...
Wow, I have no idea wether it's your Cache hack working well or that this ROM just works better with the mt3g but I can't believe this is the first release. Looking forward to everything working... Will use this as my everyday ROM for sure!.
XxKOLOHExX said:
Thanks for this
Umm since there is no BootScreen how long does it usually take to boot ? because i am kinda iffy on weather i should wipe again and flash
(been booting for about 5 mins)
Click to expand...
Click to collapse
logcat dude... ur a dev.
and it should be more than 5. it odexes on boot.
I don't even have this phone, but I'm tired of hearing you guys complain about your wifi dropping . HTC programmed the Desire S to drop wifi connections if the signal falls below -88db. I'm not sure why they did that because -88db is a perfectly usable signal. With this fix, your wifi connection won't drop until the signal falls below -108db.
You need to be running a custom deodexed ROM to apply this fix.
Flash through Clockwork Recovery.
Let me know if it works for you!
If you appreciate my work, donations of any amount are very much appreciated.
Small update... noticed that I didn't set the permissions right on one of the files. May want to grab v2.
On another note, where is everyone? Dev community for this phone needs to wake up!
gtg465x said:
Small update... noticed that I didn't set the permissions right on one of the files. May want to grab v2.
On another note, where is everyone? Dev community for this phone needs to wake up!
Click to expand...
Click to collapse
i´m here ;-)
just downloading v2 and give it a go and a test...
i will report back as soon as i feel there is something happening after flashing ;-)
thanks for this.... if this works, i can enjoy my wifi in the kitchen while drinking coffee ;-)
regards and thanks
We still can't use it, for the majority of Desire S user got an S-ON units.
For those who can't apply the above fix due to "S on" (pretty much everyone?) you can try the easier way which I've posted in another thread. Some people said it doesn't help but there's no harm in trying
there's a stock setting that can enable Desire S to hold Wi Fi connection a lot better. Go to Settings -> Wireless & networks -> Wi-Fi settings. Click menu button and choose Advanced. Second section from the top is "Best Wi-Fi performance" - tick it. That's it. It really made the difference for me. Dropped Wi Fi signal was a frequent thing with my Desire S but ever since I've ticked this option (~1 week ago) I haven't had such problem at all.
rubbish said:
For those who can't apply the above fix due to "S on" (pretty much everyone?) you can try the easier way which I've posted in another thread. Some people said it doesn't help but there's no harm in trying
there's a stock setting that can enable Desire S to hold Wi Fi connection a lot better. Go to Settings -> Wireless & networks -> Wi-Fi settings. Click menu button and choose Advanced. Second section from the top is "Best Wi-Fi performance" - tick it. That's it. It really made the difference for me. Dropped Wi Fi signal was a frequent thing with my Desire S but ever since I've ticked this option (~1 week ago) I haven't had such problem at all.
Click to expand...
Click to collapse
Just so people know, doing this does NOT have the same effect as applying my fix. That might help you a little in the mean time until you get S-OFF, but my fix should completely fix the issue.
Also, why does loveboatcaptain appear to have S-OFF and the rest of you can't?
^^^^^^^^^
He might used xtc clip to turn it from s-on to s-off
this is the only way to do this until a dev figur some
software way to do this
abo.saud said:
^^^^^^^^^
He might used xtc clip to turn it from s-on to s-off
this is the only way to do this until a dev figur some
software way to do this
Click to expand...
Click to collapse
Yes, true, and the xtc-clip is pretty expensive too, so most of us have to wait for a software method to get s-off, and then we can root and install clockworkmod i believe.
Unless you knew someone or somewhere who can make it to S-OFF, cause the xtc clip is expensive.
Why there are two files to dowload? What's the difference?
Anyway: thanks for the fix
Now there would be a reason to flash the deodexed ROM from loveboat
As there are few devices sold and there is only one cook but no "hardcore-devs" (no offense to loveboatc.) for kerneltweaks or S-off there is not much life here..
Mine is S-off since SIMunlock - but done by a company for money (EUR 20,-)
But the stock-htc-2.3.3 is really great (very good battery, very stable,...) - so better than CM7 on my NexuS :/ I only needed root for deleting the htc-ads.app (navigation, amazon,...) and for adblocker,..
dont know said:
Why there are two files to dowload? What's the difference?
Anyway: thanks for the fix
Now there would be a reason to flash the deodexed ROM from loveboat
As there are few devices sold and there is only one cook but no "hardcore-devs" (no offense to loveboatc.) for kerneltweaks or S-off there is not much life here..
Mine is S-off since SIMunlock - but done by a company for money (EUR 20,-)
But the stock-htc-2.3.3 is really great (very good battery, very stable,...) - so better than CM7 on my NexuS :/ I only needed root for deleting the htc-ads.app (navigation, amazon,...) and for adblocker,..
Click to expand...
Click to collapse
The two different versions are for two different ROM bases. Look in your software information to see which firmware you're running.
gtg465x said:
Also, why does loveboatcaptain appear to have S-OFF and the rest of you can't?
Click to expand...
Click to collapse
yes i used the xtc clip to get s-off, but didn´t buy one. i found someone who has this clip in a german android forum. meet him, give him some bugs (15€) and a coffee and while drinking that coffee he unlocked my wildfire and my desire s.
so you needn´t to buy it, cause you only will use it once. the s-off with the xtc clip is irreversible. nothing what you can flash can change that at the moment.
there is a second possibility with the clip as i read. there is a new version for sale which works "prepaid" and costs something like 25€/20£ which is a quite cheep way to get s-off i think.
phone repair shops in berlin for example have that clip too. will take some time to find one, but it´s really simple when you live in a bigger city.
dont know said:
Now there would be a reason to flash the deodexed ROM from loveboat
As there are few devices sold and there is only one cook but no "hardcore-devs" (no offense to loveboatc.) for kerneltweaks or S-off there is not much life here..
Mine is S-off since SIMunlock - but done by a company for money (EUR 20,-)
But the stock-htc-2.3.3 is really great (very good battery, very stable,...) - so better than CM7 on my NexuS :/ I only needed root for deleting the htc-ads.app (navigation, amazon,...) and for adblocker,..
Click to expand...
Click to collapse
grrrrr ;-) i know that i´m not a hardcore dev :-( sadfully for myself too.
i would like to have someone who can do the job better than me. i made that only for myself, but wanted to share that with the community, cause there was nothing really usefull to find. and without HCDR.Jacob we would still have nothing, cause i would have failed on that what we now have.
give me some more time. i´m a hardcore family father, with a 10 month old little boy and a wunderfull wife, who like what i´m doing in my freetime, cause she´s addicted to android too *chear* and of course i have a fulltime job too.
but i´m working hard in my freetime to build something that will be a good basement for evrything that comes further.
on my next 2 or 3 free days i will be have a look at the kernel. perhaps HCDR.Jacob will give me a hand on that again, so we could do a little OC and UV for better battery life and some smartass-gov tweaks.
i also set up my mac (yes shame on me i use an apple macbook to build android ;-) ) to build from source for android.
you know what that mean right? AOSP ROM ;-) or to be clear CM7 !!!
but this will take a lot of time i think. for me ;-) but let´s see what i can do for all of use until there are hardcore devs around. which would be super cool to have someone to work with...
regards
im a new android user, i booted into the clockwork thing and selected your update file from sd card to update with. It appears to install correctly.
Is there a way i can check if this patch has been installed properly or not?
Thanks
bongo1 said:
im a new android user, i booted into the clockwork thing and selected your update file from sd card to update with. It appears to install correctly.
Is there a way i can check if this patch has been installed properly or not?
Thanks
Click to expand...
Click to collapse
Open /system/etc/calibration as text and see if rssi_offset at the bottom of the file is equal to -20.
Sent from my Inspire 4G using XDA App
Thanks for that, my offset is 0 so didn't work, does the patch work on the stock eu firmware with root, or do I need to use loveboats custom firmware?
Thx
Sent from my HTC Desire S using XDA App
Installed loveboats custom firmware,
maybe i missed something but i did following.
- install LBC MOD SAGA alpha v0.01
- boot into clockwork recovery
- select install zip from sd card and select saga_wifi_fix_1.28.401.1_v2.zip
- install sucessfull
- reboot phone
- rssi_offset=0 so did not work
did i make any mistake?
thanks
bongo1 said:
Installed loveboats custom firmware,
maybe i missed something but i did following.
- install LBC MOD SAGA alpha v0.01
- boot into clockwork recovery
- select install zip from sd card and select saga_wifi_fix_1.28.401.1_v2.zip
- install sucessfull
- reboot phone
- rssi_offset=0 so did not work
did i make any mistake?
thanks
Click to expand...
Click to collapse
so i found time to test your fix a little bit...
sadfully i have to say that your update.zip didn´t work with my ROM (see below).
the files are working, really gread... now i can drink coffee in my kitchen without loosing my wifi connection. thank you very much for fixing that.
to fix your update.zip i compared your updater-script with mine.
you used the following mount command:
Code:
mount("ext3", "EMMC", "/dev/block/mmcblk0p26", "/data");
mount("ext3", "EMMC", "/dev/block/mmcblk0p25", "/system");
i used this:
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p26", "/data");
the desire s and the incredible s are using ext4 which you can find out by typing following in your terminal:
Code:
adb shell
mount
this is the output from my terminal:
Code:
...
/dev/block/mmcblk0p25 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p27 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p28 /devlog ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
...
i´ve had the same problem with my ROM and while compiling and building the clockworkmod recovery... after changing everything to ext4 clockworkmod and the script installed my ROM successfully.
i tried the lines and modified your script and after that the files where changed correctly.
hope that will help the other ones having problems to flash it.
regards
p.s. can i use your fix in the next update for my ROM (credits included ;-) !! ) and is it possible to increase the values a little more (just for personal interest)
i can confirm changing the file system as you suggested worked
Thankyou to both.
Thanks loveboatcaptain. I just assumed the mounts would be the same as the Desire HD. Updated the fixes in the first post to mount ext4.
Here is the next version of my HTC Evo Shift Sense kernel. It was built from the 2.3 gingerbread source. It should be stable and smooth as that was my main goal with this. I usually dont come here to XDA as often, so you may receive better support for questions/concerns here at SDX
Kernel Features:
Undervolted
Overclocked to 1.92Ghz
Interactive governor added
Smartass governor added
Enabled powersave governor
Faster charging over USB (Still slower than AC Wall charger)
BFQ (Budget Fair Queuing) i/o scheduler
Full bash mod (Gives you working directory, command history, tab completion and a shameless plug of my kernel in the shell )
Enabled ext4 filesystem support
Included HAVS/SVS support for Vipermod or incredicontrol (thanks to cayniarb and his tiamat kernel for guidance)
Init.d scripts supported (needs testing)
Default Settings:
Max Frequency = 1.209GHz
Min Frequency = 245MHz
Governor = Interactive
I/O Scheduler = BFQ
Download a cpu control application like No-Frills/SetCPU from the market for editing these settings.
Information:
The bash mod is something that cloverdale proved was what people liked so I went ahead and edited the ramdisk and zip to set that up so thanks to him for that.
After playing with the frequency table a bit, I changed methods this time and used the CM method for overclock on this phone. Its a method I saw several developers use while on 2.2 and seemed a bit cleaner than the method that I had originally set up. Thanks to toast, for the implementation of that.
This is still something I want to improve so I really need some feedback as to what you guys want to see. I will try my best to fulfill all logical suggestions.
With the bash mod, if you flash a kernel over this, it may (depending on the script method) remove the nice pretty text for the shell. It will still be functional as that part is installed to the phone itself. I will post up a 'bash removal' zip to restore back to default eventually
Ext4 FS has been added. It requires you to convert your filesystem from ext3 to ext4. Ive made it pretty simple for you to do with a script inside of a flashable zip. If something goes wrong, please let me know.
HAVS/SVS passes the VDD (Voltage draw for each frequency) values to userspace, meaning that they can be set by the user. While nothing NEEDS to be done for it to work, users now of the option of tweaking the voltages just a bit in order to increase their battery life. This was tested with the free application 'incredicontrol' from the market. ANY and ALL bug reported due to the fact that you dropped the voltages a bit to much will be ignored. This is DUE AT OWN RISK. I can tell you that from my experience, dropping down 50mv is about as far as you can go on my kernel. Good luck.
To anyone wanting to learn how to start getting into development, Please email, PM, or find me on irc #gen-dev, #sdx-developers, #htc-evo-3d on irc.freenode.net. I will teach you whatever I can as best I can. It is the only way to progress the development community. Ive spent hours teaching several over the past week and countless hours in the past. Please do not hesitate to ask.
Kingdom ROM Users:
Thanks to nfinitefx45 for letting me know what had to be changed in the ramdisk, I now have a new zip for this ROM that includes the full bash mod.
Downloads:
all downloads can be found here
Installation:
EXT3:
1. Download and place on SD card
2. Boot into recovery and make a back up if required
3. Flash zip
4. Reboot
EXT4:
1. Download both the ext4 kernel and ext4 conversion zip and place both on SD card
2. Boot into recovery and make a nandroid backup (very important)
3. Flash EXT4_fs_conversion.zip (do not reboot)
4. Restore the nandroid you just made (do not reboot)
5. Flash ext4 kernel.
6. Reboot
Returning to EXT3:
1. Download ext3 conversion zip and have an ext3 kernel. Ensure both are on the SD card
2. Reboot into recovery and make a nandroid backup (very important)
3. Flash EXT3_fs_conversion.zip (do not reboot)
4. Restore the nandroid you just made (do not reboot)
5. Flash ext3 kernel
6. Reboot
FAQ:
Q: What is EXT4?
A: Ext 4 is the newest version of the extended filesystem. It is mainly used as the default linux filesystem in most distros. It has improved read and write speeds over the previous versions (ext3 and ext2) It should provide slight speed improvements over the default filesystem on the shift, ext3.
Q: Why do I have to 'convert' my filesystem and is it necessary?
A: My ext4 kernel will only mount system, data, cache, and devlog partitions as ext4. It is not 100% necessary to convert the existing filesystem to ext4 as ext4 is backwards compatible, meaning it can mount ext3 partitions as ext4. By converting it to true ext4, you will be able to take full advantage of ext4 speed.
Q: Will this affect the way I flash ROMs and modifications?
A: In theory, no. The ROM should flash like normal but if they do have a custom kernel included, it will be necessary to flash an ext4 kernel after the ROM.
Q: Is this safe?
A: While working with partitions and their filesystem is considered risky on any account, I have made the conversion zips as simple and as safe as I possibly can. If any corruption does occur, it is usually fixable but should not happen in the short life of these devices.
Q: Does this change the way the backup and restore functions work in CWM or TWRP?
A: No, it should not effect the way the recoveries backup and restore data. There have been some notification of the 'wipe' functions in 'mounts and storage' reformatting back to ext3 but, you should be able to just flash the conversion zip again to return to ext4.
Q: I want to use a different kernel that is not ext4.
A: You will need to flash the EXT3 conversion zip to return your partitions to ext3. Then flash like normal.
Q: AOSP ROMs are on ext4, why do they not require the conversion?
A: While this was an option, I felt it best to do ext4 100%. An ext3 partition can be mounted as ext4 and it will provide some speed enhancements but, it is not full ext4. AOSP roms are simply mounting the ext3 partitions as ext4 which is fine, just not my preferred method.
Q: Will this effect my sdcard in anyway
A: No it will not.
Q: What do I do if something goes horribly wrong and my phone is stuck in a bootloop and I cant pull it out?
A: This is a help forum, post your issues and I or another helpful person will help you. If you are not receiving help, PM me or email me at [email protected] and I will get back to you.
Click to expand...
Click to collapse
Changelog:
11/11: Added support for HAVS/SVS. Re-worked clock table and added 1.9ghz. Enabled init.d scripts. Finished tweaking smartass governor.
11/03: Added EXT4 version of both kernels. Added bash mod to Kingdom ROM version.
11/02: Initial Release v1.5
Source available at https://github.com/dodgejcr/speedy-2.6.35
Thanks to all the people in the huddle that tested this before release to ensure it was up to standards (especially strapped and crump). Big thanks to joeykrim for his FlashimageGUI app that made testing 20 or so kernels over the past day or two less of a headache
Thanks for this. Just installed and seems to be great
Sent from my PG06100 using xda premium
For the Kingdom you will need to change the dhcpcd line in speedy.rc to
service dhcpcd_eth0 /system/bin/dhcpcd -ABKL eth0
disabled
oneshot
this will allow for the wifi to enable.
hope that helps
nfinitefx45 said:
For the Kingdom you will need to change the dhcpcd line in speedy.rc to
service dhcpcd_eth0 /system/bin/dhcpcd -ABKL eth0
disabled
oneshot
this will allow for the wifi to enable.
hope that helps
Click to expand...
Click to collapse
Sweet thanks. I had planed on either asking you today or tearing down your ramdisk to find it. Saved me time. If I add any more tweaks to the ramdisk ill be sure to add this. Much apreciated
Thank you Dodge! XDA is honored by your visit! So... when we getting an AOSP flavor?
jesusice said:
Thank you Dodge! XDA is honored by your visit! So... when we getting an AOSP flavor?
Click to expand...
Click to collapse
Been working on one for a while now. Cant seem to make myself happy with it but I have yet to stop. With this one done and out of the way, maybe I switch over to AOSP and whip something up for that. LOL Who knows
You the man Dodge. Thanks for all the work, been running smooth so far.
Sent from my PG06100 using Tapatalk
been running for two days, smooth as buttermilk.
Thanks for the fix dodge! Runnin great nice and smooth, hope you tweak it up and add nfinite's fix in. As soon as I come up with some ideas will drop'em on ya. Enjoy the movie! Lol
Sent from my AT100 using Tapatalk
-somebody- said:
been running for two days, smooth as buttermilk.
Click to expand...
Click to collapse
+1... Never disappointed with your kernels...
Sent from my PG06100 using Tapatalk
Ext4 support for filesystem
Sent from my PH44100 using XDA App
nfinitefx45 said:
Ext4 support for filesystem
Sent from my PH44100 using XDA App
Click to expand...
Click to collapse
+ 1 on the ext4 support dodge!
Sent from my AT100 using Tapatalk
nfinitefx45 said:
Ext4 support for filesystem
Sent from my PH44100 using XDA App
Click to expand...
Click to collapse
Sounds like a glorious idea. Ill probably add that for the next release. Keep the suggestions coming
modmouse78 said:
Thanks for this. Just installed and seems to be great
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
touche, seems to run quicker than x99 at 1.2 ondemand governor
dodgejcr said:
Sounds like a glorious idea. Ill probably add that for the next release. Keep the suggestions coming
Click to expand...
Click to collapse
Enable call recording.
jesusice said:
Enable call recording.
Click to expand...
Click to collapse
Ooh a challenge. Haven't done that before, should be interesting. Ill give it a shot
Sent from my HP Touchpad
You do know J this is a sese kernel! You lost or forget what thread you're in ? Lol jk
Sent from my PH44100 using Tapatalk
dodgejcr said:
Ooh a challenge. Haven't done that before, should be interesting. Ill give it a shot
Sent from my HP Touchpad
Click to expand...
Click to collapse
Video calling support is in the newer aosp kernels. If you need a start on where to look. I don't think the .13 one does tho I could be wrong. Not sure how easy it would be to impliment. Best of luck tho.
Sent from my PG06100 using xda premium
sparksco said:
Video calling support is in the newer aosp kernels. If you need a start on where to look. I don't think the .13 one does tho I could be wrong. Not sure how easy it would be to impliment. Best of luck tho.
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
being that the shift doesnt have a front facing camera video calling is kinda pointless (just my opinion)
Check in the dhd and dz threads as there source is very similar to ours
Sent from my PH44100 using XDA App
This is an idea spawned by nubecoder.
The Goal: To collapse full and lite rom versions into a single version, and utilize a configuration file on the sd card to tell the rom how to install itself, creating a standard and simplicity for end-users.
RDU
ROM DEVELOPERS UNITED
AS ONE
CWM ROM Lite/Full Toggle UtilitySupported ROMs:
- RandomROM ThunderHawk 3.3
- Legendary ROM RC 2.2
To Developers: Join me as the RDU, and together we can make rom flashing a more enjoyable experience.
To Users: If you support this idea, contact your favorite devs on their rom threads and let them know! This utility functions around a file created on your SD Card under the clockworkmod folder called 'options.cfg'. This same file is also now utilized in ThunderHawk 3.3 and II to choose whether to install standard or scroll-able toggles, as well as an advanced or a simple power menu.
So here's how it works:
I personally split my rom into a regular version and a slimmed down lite version. Unfortunately, I then have to make sure I regularly update both versions, and then test them both while keeping both on my phone. Since I'm currently maintaining 3 different roms, and 2 different versions of each, this gets to be a handful. So I've coded a mock version of the setup. I've now designed it, with thanks to hoffman, so that the rom or switcher will default to a Full configuration if no config file exists. The config file is safely tucked away under /sdcard/clockworkmod.
Using a single separate flash-able, I can toggle the config file between lite and full simply by flashing it whenever I want to change it. I can set it to lite, and install as many of my roms in a row in lite version without having to do a thing extra.
The Latest Version Here.
The Previous Version Here.
After setting the config file, simply run the rom, and after copying the config_check file into your tools folder and utilizing coding such as the following, it can determine how to install itself:
Code:
#MOVING TOOLS TO PHONE
package_extract_file("tools/config_check", "/tmp/config_check");
set_perm(0, 0, 0755, "/tmp/config_check");
#DETERMINE FULL OR LITE VERSION
run_program("/tmp/config_check","check");
ifelse(
# read the "lite.version" value from the file
file_getprop("/sdcard/clockworkmod/options.cfg", "lite.version") == "yes",
(
# if the value reads yes, enable lite version
ui_print("Lite Version Enabled...");
),
(
# if the value reads no, enable full version
ui_print("Full Version Enabled...");
package_extract_dir("fullpack/system", "/system");
package_extract_dir("fullpack/data", "/data");
package_extract_dir("fullpack/sdcard", "/sdcard");
)
);
UPDATE: (1/06) I have yet further redeveloped the scripting to enhance the capabilities. Previously, this script would read the options file and, assuming that the first line is the "lite.version" property, backup the rest of the file. After which, it would rewrite the file accordingly, and then restore the backed up file info. Should the lite property not be in the first line, the scripting will likely fail. As such, I have rewritten the code in a more elegant way to now properly adjust the options.cfg file without the need to rewrite it. Thus, enabling the file to more safely contain any number of more installation settings, such as Clean Install/Full Wipe.
UPDATE: (12/21) I just rewrote the script further so that it can preserve any additional settings one might want to add (i.e. scrollable/nonscrollable toggles, advanced power menu/simple power menu, etc.) as long as the full/lite setting remains listed first.
UPDATE: (12/15) Okay, so I've tucked the file under Clockworkmod where it should be safe, yet easily accessible. I've also recoded the .zip to us shell scripting to write the file rather than blunt force copying file back and forth over top of each other.
So the idea is that we might be able to standardize something like this across various roms.
I'm currently in talks with earthbound[iap] over a possible app kitchen configuration of sorts to bring this together. Using another cwm script, or android app, or windows app, or manual editing, etc. any number of customizations could be applied this way through this single file.
Further ideas or customizations from fellow rom developers welcome.
Post reserved for more... I don't know.
Awesome!
Sent from my epic that didn't have CIQ before it was cool
Thanks for all your work!
I use an automating script i threw together to merge my package versions allowing me to keep a base package, then separate incremental (the actual updates done to files), extras for the full version, and slim version (which is base+incremental), then zipalign apks/jars, zip, and sign the rom packages, as well as generate the link/filesize/md5 output that i can enter into my rom OP.
This is how i can put out my ROM so quickly day by day, i don't know how everyone else does the grunt work of package release, i noticed most roms are unsigned (or invalidly signed based on other roms), but CWM doesn't check by default anyway.
My original idea was exactly this - one monolithic file that automatically chooses which to install - especially when dealing with Rom Manager for choices, but then decided the file size hit wasn't worth it to some since the slim package is 50MB smaller a lot of people download it - especially direct to phone.
My thinking on the versioning for included extras has instead switched focus to WIPE/NO-WIPE configurations in order to avoid having to backup/restore the data as opposed to leaving the data in place if the FS is already where desired (i.e. on an ext4 ROM, check if rfs, if so, backup and format.) it's a smarter and faster way than just ALWAYS backing up/formatting/restoring. The trick was to make this work in updater-script, testing the fs, though still it would be great to have some sort of interactivity - what is shown here is about as close as we can get to an interactive install.
If anyone is interested i'll clean up the script and post it. It's basically a custom made simplistic ROM Kitchen. in fact, it's written in PHP (with shell_execs for necessary shell commands), which i run in php cli, but can obviously run on a server as a multi choice ROM Kitchen (i'm working on this one now for SleeperROM).
PHP is a fluency so it was quick to put together.
EDIT: i didn't mean to steal any thunder, but since you said you're developing a ROM Kitchen sort of thing with earthbound i felt it necessary to advise on my secret sauce
I have to say that it is always great seeing you guys work together. Good luck. It sounds like a great idea that is way over my head.
Sent from my Epicly Legendary Galaxy S Device or my Galaxy Tab rooted (feels naked without a ROM)
SenseiSimple said:
Thanks for all your work!
Click to expand...
Click to collapse
Any knowledge shared is worthwhile! While 50mb or so is a hit, its relatively inconsequential on 16gb of storage when the advantages are looked at. Faster testing for me and less uploads to manage! But more importantly, I've arranged my rom so that the full version add-ins can be quickly removed via 7zip by a picky user.
The fact of the matter is that I have less than 80 lite downloads as compared to more than 800 full version downloads just on last weeks edition. It seems nearly 90% of downloaders aren't concerned with SD storage usage. Its the phone storage they ought to keep their eyes on ;-).
Id certainly be interested in your kitchen of sorts.
-Sent from my Random Epic.
ERA would be down for sure. know we kind of gave up on making two versions because it takes a lot of testing and what not. I'll see if I can get a hold of Hoff or ksmullins. And we can work together.
Sent from my SPH-D700 using xda premium
stormglove said:
ERA would be down for sure. know we kind of gave up on making two versions because it takes a lot of testing and what not. I'll see if I can get a hold of Hoff or ksmullins. And we can work together.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
No need... I'm a lurker. >.>
Seems like a great idea... I'll keep checking back on for progress updates. And if anyone needs a hand with anything, just shoot me a PM. I'm more than happy to help out.
I'm a web dev too.. Prefer front end, so if there's some things you need mashed out, gaive me a shout about tht as well. =)
hoffman1984 said:
Seems like a great idea... I'll keep checking back on for progress updates. And if anyone needs a hand with anything, just shoot me a PM. I'm more than happy to help out.
I'm a web dev too.. Prefer front end, so if there's some things you need mashed out, gaive me a shout about tht as well. =)
Click to expand...
Click to collapse
Right now it's a simple flash-able. Flash it once, it writes the config file for Lite version mode. Flash it again, and it writes the config file for Full version mode. And you can do it over and over again until you flash a rom, which then identifies the coding in the config file and acts accordingly.
So, one could feasibly break that rom .zip down into further "variations," although I personally will not be taking this route at the moment. earthbound[iap] is looking into creating a Windows or Android app that would enable you to choose any number of options and write them to that same config file. Then your rom of choice could read all of those options.
But for now, it's just Lite or Full. Speak up if you have any contributions, it would be nice to have this in common amongst multiple roms!
Maybe just change the name of the .zip? And check if its the lite or full, even though you'll still have the same .zip, it changes depending on filename
sent from my always aosp epic
ugothakd said:
Maybe just change the name of the .zip? And check if its the lite or full, even though you'll still have the same .zip, it changes depending on filename
sent from my always aosp epic
Click to expand...
Click to collapse
That could probably work, but would require a person to change the file name manually, on every rom and update they download. Or the dev can do it beforehand, upload identical, differently named roms. But then you still have to upload 2 versions.
My proposal is essentially an on/off switch accessible from CWM. And for a person who only installs lite versions, or only installs full versions, they would only have to do it once. Ever. No matter how many compatible roms they download.
And Earthbound proposes a whole range of customizations.
A standard for Development on the Epic... Indeed a good idea.
This is also how bigger projects (CyanogenMod\MIUI) start. =)
hoffman1984 said:
A standard for Development on the Epic... Indeed a good idea.
This is also how bigger projects (CyanogenMod\MIUI) start. =)
Click to expand...
Click to collapse
Alright, here is where I need help. The switcher feature works perfectly and it's beauty is in its simplicity. However, it's simplicity is the number one problem I can identify.
The switcher and the rom check the config file for a yes or a no. While that works, it fails if the file doesn't exist. Sure, a user can download the file and place it once manually, but that just doesn't sit well with me.
What I would like now, is for the rom and switcher to first look for the file, and if they can't find it, then they should create it with Full install as the default setting. After which, the switcher can once again perform it's duty.
Anyone know a good way to do this?
RandomKing said:
Alright, here is where I need help. The switcher feature works perfectly and it's beauty is in its simplicity. However, it's simplicity is the number one problem I can identify.
The switcher and the rom check the config file for a yes or a no. While that works, it fails if the file doesn't exist. Sure, a user can download the file and place it once manually, but that just doesn't sit well with me.
What I would like now, is for the rom and switcher to first look for the file, and if they can't find it, then they should create it with Full install as the default setting. After which, the switcher can once again perform it's duty.
Anyone know a good way to do this?
Click to expand...
Click to collapse
The only way i can think is maybe include the options.cfg and a script that does the checks for you. If the file doesn't exist, move it from /tmp/ to /sdcard/... Then onto your original script, which SHOULD find the now present options.cfg on the SD. Let me know if i mucked this up. =P
This has not been tested...
Code:
run_program("/sbin/mount","/sdcard");
package_extract_file("scripts/options.cfg", "/tmp/options.cfg");
package_extract_file("scripts/config_check", "/tmp/config_check");
run_program("/tmp/config_check");
config_check
Code:
#!/xbin/sh
#
cfg="options.cfg"
if [ ! -f /sdcard/$cfg ]
then
mv -f /tmp/$cfg /sdcard/$cfg
fi
Then on with your script...
SenseiSimple said:
Thanks for all your work!
I use an automating script i threw together to merge my package versions allowing me to keep a base package, then separate incremental (the actual updates done to files), extras for the full version, and slim version (which is base+incremental), then zipalign apks/jars, zip, and sign the rom packages, as well as generate the link/filesize/md5 output that i can enter into my rom OP.
This is how i can put out my ROM so quickly day by day, i don't know how everyone else does the grunt work of package release, i noticed most roms are unsigned (or invalidly signed based on other roms), but CWM doesn't check by default anyway.
My original idea was exactly this - one monolithic file that automatically chooses which to install - especially when dealing with Rom Manager for choices, but then decided the file size hit wasn't worth it to some since the slim package is 50MB smaller a lot of people download it - especially direct to phone.
My thinking on the versioning for included extras has instead switched focus to WIPE/NO-WIPE configurations in order to avoid having to backup/restore the data as opposed to leaving the data in place if the FS is already where desired (i.e. on an ext4 ROM, check if rfs, if so, backup and format.) it's a smarter and faster way than just ALWAYS backing up/formatting/restoring. The trick was to make this work in updater-script, testing the fs, though still it would be great to have some sort of interactivity - what is shown here is about as close as we can get to an interactive install.
If anyone is interested i'll clean up the script and post it. It's basically a custom made simplistic ROM Kitchen. in fact, it's written in PHP (with shell_execs for necessary shell commands), which i run in php cli, but can obviously run on a server as a multi choice ROM Kitchen (i'm working on this one now for SleeperROM).
PHP is a fluency so it was quick to put together.
EDIT: i didn't mean to steal any thunder, but since you said you're developing a ROM Kitchen sort of thing with earthbound i felt it necessary to advise on my secret sauce
Click to expand...
Click to collapse
This wipe no wipe is a GREAT idea... I'm going to see what i can cook up for Legendary. >.>
Now if only we could build a menu of selections for this into CWM...
-Sent from my Random Epic.
Also... Quick question for Sensei... Did your wipe or not wipe look something like this?
Code:
ui_print("Attempting to mount the Filesystem as EXT4...");
ifelse(
mount("ext4", "EMMC", "system", "/system") == "system",
(
ui_print("Filesystem mounted as EXT4...");
ui_print("Mounting the rest...");
mount("ext4", "EMMC", "data", "/data");
mount("ext4", "EMMC", "cache", "/cache");
),
(
ui_print("File System Not EXT4! Will now convert...");
ui_print("Backing up Data..");
run_program("/sbin/mount","/sdcard");
run_program("/sbin/mount", "/dev/block/stl10", "/data");
run_program("rm", "-r", "/data/dalvik-cache");
run_program("/tmp/data-backup");
ui_print("Formatting file system...");
run_program("/tmp/fsck.ext4", "-fy", "/dev/block/stl9");
run_program("/tmp/mkfs.ext4", "-O", "^ext_attr,^has_journal,^huge_file", "-L", "SYSTEM", "-b", "4096", "-m", "0", "-F", "/dev/block/stl9");
run_program("/tmp/fsck.ext4", "-fy", "/dev/block/stl10");
run_program("/tmp/mkfs.ext4", "-O", "^ext_attr,^has_journal,^huge_file", "-L", "DATA", "-b", "4096", "-m", "0", "-F", "/dev/block/stl10");
run_program("/tmp/fsck.ext4", "-fy", "/dev/block/stl11");
run_program("/tmp/mkfs.ext4", "-O", "^ext_attr,^has_journal,^huge_file", "-L", "CACHE", "-b", "4096", "-m", "0", "-F", "/dev/block/stl11");
)
);
There's obviously some room for error here, but I was going for the basic idea...
hoffman1984 said:
Also... Quick question for Sensei... Did your wipe or not wipe look something like this?
Code:
ui_print("Attempting to mount the Filesystem as EXT4...");
ifelse(
mount("ext4", "EMMC", "system", "/system") == "system",
(
ui_print("Filesystem mounted as EXT4...");
ui_print("Mounting the rest...");
mount("ext4", "EMMC", "data", "/data");
mount("ext4", "EMMC", "cache", "/cache");
),
(
ui_print("File System Not EXT4! Will now convert...");
ui_print("Backing up Data..");
run_program("/sbin/mount","/sdcard");
run_program("/sbin/mount", "/dev/block/stl10", "/data");
run_program("rm", "-r", "/data/dalvik-cache");
run_program("/tmp/data-backup");
ui_print("Formatting file system...");
run_program("/tmp/fsck.ext4", "-fy", "/dev/block/stl9");
run_program("/tmp/mkfs.ext4", "-O", "^ext_attr,^has_journal,^huge_file", "-L", "SYSTEM", "-b", "4096", "-m", "0", "-F", "/dev/block/stl9");
run_program("/tmp/fsck.ext4", "-fy", "/dev/block/stl10");
run_program("/tmp/mkfs.ext4", "-O", "^ext_attr,^has_journal,^huge_file", "-L", "DATA", "-b", "4096", "-m", "0", "-F", "/dev/block/stl10");
run_program("/tmp/fsck.ext4", "-fy", "/dev/block/stl11");
run_program("/tmp/mkfs.ext4", "-O", "^ext_attr,^has_journal,^huge_file", "-L", "CACHE", "-b", "4096", "-m", "0", "-F", "/dev/block/stl11");
)
);
There's obviously some room for error here, but I was going for the basic idea...
Click to expand...
Click to collapse
mine is much simpler but essentially, yes.
Code:
unmount("/data");
run_program("/tmp/busybox", "mount", "-t", "noext4", "/dev/block/stl10", "/data");
ifelse(is_mounted("/data"),(
ui_print("Backing up data, formatting.")
run_program("/tmp/tar-backup","backup");
unmount("/data");
run_program("/tmp/fsck.ext4", "-fy", "/dev/block/stl10");
run_program("/tmp/mkfs.ext4", "-O", "^ext_attr,^has_journal,^huge_file", "-L", "DATA", "-b", "4096", "-m", "0", "-F", "/dev/block/stl10");
),ui_print("Leaving data intact."));
basically unmount > mount anything BUT ext4 > check if mounted (if it did mount, it's rfs or whatever) then backup/format
that only selects how to NOT wipe/ preserve data... leaving the ext4 data intact like that has a weird effect on the first boot of showing the AOSP android logo animation contained in framework-res, but it shows the regular /system/media/bootanimation thereafter... i haven't noticed any ill side effects that weren't a result of my own error while replacing existing data files with new ones in the rom package. so i'd like to provide the option of WIPE BEFORE INSTALL for those who want clean install (right now i just provide a flashable that does the formatting for a clean slate (no 3x wipe/factory reset necessary)
Is_mounted. Interesting... Didn't know that syntax exsisted... I apparently have more homework to do, and maybe ill just stick the to the code I have (as its just a bit different) than the competition.
Anywho, thanks for the point in another direction... I'll definitely be implementing VERY soon...
Sent from my PG86100 using XDA App
More tweaks being added see below!!!!!!!!!
Here's a little tip/tweak!!!!!!
All credit goes to my friend Nibras Reeza this is hes work all credit to him im just the messenger. I tested this tweak for him awhile back in the GT540 thread tried it on the TF101 and had great results so thought I should share
This wasnt supposed to be a tweak for devices with 1Gb of RAM etc. However I think if I had to choose odexed or deodexed I would choose deodexed plus this tweak no matter what device no matter how much RAM.
AS WITH ANY MODDING PROCEDURE FOR YOUR PHONE, THIS GUIDE ALSO COMES WITH NO WARRANTY. AUTHOR HOLDS NO RESPONSIBILITY FOR ANY DIRECT AND INDIRECT CONSEQUENCES OF FOLLOWING THIS GUIDE. MAKE SURE YOU HAVE MADE A NAND BACKUP BEFORE PROCEEDING.
This will give a performance boost in deodexed ROMs as much as odexing system & data apps. This is an alternative for odexing. It's not that you can't apply this tweak on an odexed ROM but rather, it's useless to do so.
1) Open Terminal Emulator on phone or adb shell from PC and type the following.
su
setprop dalvik.vm.verify-bytecode false
setprop dalvik.vm.dexopt-flags v=n,o=v
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
2) Add these to the /data/local.prop or build.prop.
dalvik.vm.verify-bytecode = false
dalvik.vm.dexopt-flags=v=n,o=v
(Copy local.prop or build.prop to SD and edit them. Copy back afterwards. If lines starting with dalvik.vm.verify-bytecode or dalvik.vm.dexopt-flags exist already, please modify them as above. Also type following in adb shell or terminal emulator.
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
Advantages:
More free RAM.
Faster launch for system & user apps during the second launch.
Gives as much as of a performance boost as ODEX without odexing. Themer friendly.
Smoother app switching.
Disadvantages:
Might break some apps. ( I have not had any break you probably wont either but you have been warned!!!! )
Reversing the change/undo tweak.
Type the following in shell.
su
setprop dalvik.vm.verify-bytecode true
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
WARNING!!! (Have had a few people have this problem) If you have V6Supercharger installed and you are trying to edit the build.prop through root explorer or similar and its just not working its not the tweaks fault nor my fault you must Un-Supercharge edit the build.prop then Re-Supercharge afterwards!
MORE TWEAKS!!!!!!!!!!!!!!!!
I will add to this section when I can mostly just build.prop tweaks or change's to settings that might help some people get there device a little smoother
##########################
**Improve Touch Performance**
1. Open up your favorite Root explorer
2. Open build.prop in a text editor
3. Add this line of code ( windowsmgr.max_events_per_sec=500 )
4. Save and exit and delete build.prop.bak if you trust the tweak
5. Reboot Enjoy
Quick note if your build.prop has an additional build properties section the line of code needs to go in there !!!!!
###########################
**Dalvik Tweak**
1. Open up your favorite Root explorer
2. Open build.prop in a text editor
3. The line of code stating the vm growth will usually be set around 32-48 on some TF101 roms they now use 54-64 Thanks for the support devs
4. Save and exit and delete build.prop.bak if you trust the tweak
5. Reboot to Recovery
6. Wipe Cache and Dalvik-Cache
7. Reboot Enjoy
############################
To be continued......
ADDING MORE SOON BUT WANT THEM TO BE 4.0.3 SPECIFIC SO LOTS OF TRIAL AND ERROR HAPPENING
The problem with this is that it just turns off the dalvik controlls, so it may break some apks. Nice tweak, however
Will give this a go later.
Is there any reason why it wouldn't work in ics?
Sent from my HTC Desire Z using xda premium
Tried it on my phone with CM7.1 and everything is fine... I'm not sure if it improoved but I'm not getting any errors from apps...
i remember trying this on my gt540 (why is it now legacy device section?) and it worked great but we would have 100mb free ram at a time whereas ow i got a gig in this badboy. confirmed works.
Sent from my Transformer TF101 using xda premium
gnufabio said:
The problem with this is that it just turns off the dalvik controlls, so it may break some apks. Nice tweak, however
Click to expand...
Click to collapse
Cheers im looking into a few other tweaks and tricks at the moment will post if theres any good ones
Sent from my tf Enigmatic V1 Alpha 1.59Ghz Panda.test ( still a little crashy at this speed )
pashinator said:
i remember trying this on my gt540 (why is it now legacy device section?) and it worked great but we would have 100mb free ram at a time whereas ow i got a gig in this badboy. confirmed works.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Haha goog to see another gt owner and yes im pretty sure it is now
Ive had people at univerrsity and a couple of mates ask if it was one of the first androids ever lol
Sent from my tf Enigmatic V1 Alpha 1.59Ghz Panda.test ( still a little crashy at this speed )
pashinator said:
i remember trying this on my gt540 (why is it now legacy device section?) and it worked great but we would have 100mb free ram at a time whereas ow i got a gig in this badboy. confirmed works.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
UNIX-like systems cache eveything and as memory is needed, lesser used cached items are purged. If you have a UNIX-like system that has a lot of free RAM, your system is not running at optimal performance. Empty RAM is wasted RAM.
Cheers!
-M
Xda member since 2007
every time i run rm /cache/dalvik-cache/* it fails but wiping the dalvik cache in CWM will do the same thing correct?
mrevankyle said:
every time i run rm /cache/dalvik-cache/* it fails but wiping the dalvik cache in CWM will do the same thing correct?
Click to expand...
Click to collapse
Correct
With mine i cleaned cache also aswell as cleared out staging but thats just me
Sent from my tf Enigmatic V1 Alpha 1.59Ghz Panda.test ( still a little crashy at this speed )
dragon_76 said:
UNIX-like systems cache eveything and as memory is needed, lesser used cached items are purged. If you have a UNIX-like system that has a lot of free RAM, your system is not running at optimal performance. Empty RAM is wasted RAM.
Cheers!
-M
Xda member since 2007
Click to expand...
Click to collapse
This is true but theres alot to be said for the way the system uses that ram its not about using all of it its about using it wisely a nicely tweaked efficient unix system can run on 100mb of ram even less hell i had ubuntu running alright on my gt540 before i got the transformer.
My point free ram is not always wasted ram
Sent from my tf Enigmatic V1 Alpha 1.59Ghz Panda.test ( still a little crashy at this speed )
This is interesting. I might try to implement this on G1. But not a TF rom, doesn't make sense to me atm.
Btw, free ram in android means faster app launch times, especially on devices low on ram.
jcarrz1 said:
This is interesting. I might try to implement this on G1. But not a TF rom, doesn't make sense to me atm.
Btw, free ram in android means faster app launch times, especially on devices low on ram.
Click to expand...
Click to collapse
+1 thankyou sir!!
By all means have a jam im probably going to post more tweaks soon just testing them and screwing round with bits
Sent from my tf Enigmatic V2 beta 1.65Ghz Panda.test cust kernel settings
Thanks. Confirmed working.
you're welcome should have more soon
Sent from my tf running krakd warped an twisted 1544mhz Blades kernel
On my TF I have no /data/local.prop or build.prop... suggestions? I have a build.prop under the system folder.
nappent said:
On my TF I have no /data/local.prop or build.prop... suggestions? I have a build.prop under the system folder.
Click to expand...
Click to collapse
default.prop should be in root folder
build.prop is in /system
mrevankyle said:
default.prop should be in root folder
build.prop is in /system
Click to expand...
Click to collapse
What? This mod has nothing to do with the default.prop. I don't understand how that can help me as it was not mentioned in the OP.
Hello, just dropping by to let you know that your thread has been featured on the XDA Portal
http://www.xda-developers.com/andro...-best-of-both-worlds-for-eee-pad-transformer/
Hi!
Just tried this on a sk17i with 2.3.4 (Xperia Mini Pro) Feeling good so far!