yashsingh1/xdaforums huggingface dataset:
[Galaxy 3 Android Development] hillbeast:
App2SD works in 2.1, and should work in my test kernel I uploaded.

You can't use Multi OS Data without an SDEXT partition. This is why you have problems. There is no simpler method for you other than manually backing up data for each firmware individually every time you switch.
[Galaxy 3 Android Development] TheF3nix:
Hillbeast(: ever considered reverting the kernel back to using app2sd instead of using hybrid?
[Galaxy 3 Android Development] m1trand1r:
hybrid is just fine;)

Sent from my hybrid sg3

multibooted

Kyrillos' v8.1 powered by

g3mod 2.0 OC
[Galaxy 3 Android Development] kyrillos13:
Me too.... I got stuck on the G3MOD screen..

PS: Hillbeast, if you symlink /system/sd to /sdext, will TB display the sdext space?
[Galaxy 3 Android Development] TheF3nix:
Haha yeah works fine for me too(: but heard complains from others too. Maybe its causing all the battery draining too?
[Galaxy 3 Android Development] hillbeast:
No because Hybrid is currently the best method for the fact it is fully customisable. You don't need to fiddle around with permissions or scripts to adjust what you move, just change one file on the SD card and reboot.

Okay something is weird in this kernel too. Grr.

And I don't think that would work because it's not a mount point.

Maybe it is, but I can't see why it is.
[Galaxy 3 Android Development] TheF3nix:
Haha maybe 1 version with app2sd and another with hybrid as test version? Then compare the differences?
[Galaxy 3 Android Development] KSLevel11:
So, I have enabled MiltiOsData and SDEXT partition.

So, if I want switch rom from Xxjps to CM7 I have to:

1. Go into CWM.

2. Backup data of current rom.

3. Switch Rom to CM7.

Is this everything? Or I have to do some more?
[Galaxy 3 Android Development] silentneuville:
The G3 mod V2.0 drains the battery very quickly I replaced it with V1.9 and battery drain was dramatically improved
[Galaxy 3 Android Development] fuxmen:
That was mentioned here 1000 times before, just back to 2.0 Beta2 or try the test kernel 2-3 pages before
[Galaxy 3 Android Development] mohsin2cool:
i get stuck at boot,,,flashed 5 to 6 times......

:(:(
[Galaxy 3 Android Development] DaBigFreak:
Reflash with odin, only that helped me out!
[Galaxy 3 Android Development] Vic 17:
I think that the oc version are not mature.. after some time it froze and lag more and more.. back to non oc version and waiting for something better
[Galaxy 3 Android Development] umangsagar:
Hasnt given any trouble to me so far, not everything behaves the same way on every hardware so you may find Non OC being stable for you or may want to try some other Kernel.

---------- Post added at 12:50 AM ---------- Previous post was at 12:45 AM ----------

It did hang for me too initially, but I used the buttons to enter into recovery mode, did the wipe again (did dalvik cache wipe too as I had flashed a new ROM altogether), and restarted, it took a while during the first boot but is working after that.
[Galaxy 3 Android Development] manish19:
@Hillbeast

Any update on 2.1?
[Galaxy 3 Android Development] hillbeast:
Nah because in 2.1 this problem is fixed. There's no need.

To switch ROM, just backup the current ROM in the multi boot menu, switch to your other ROM and boot. Easy.

This is a bug I am working on fixing. It's a very difficult problem to diagnose so please be patient. I think I am getting somewhere but I can't be sure...

Same as above.
[Galaxy 3 Android Development] TheF3nix:
Okay thanks hillbeast!
[Galaxy 3 Android Development] satishynd:
hey can anyone plz tell what is the problem with g3mod-2.0b2-nonoc ???

i read that it's battery drain is low then 2.0 .. can plz tell whats the difference?
[Galaxy 3 Android Development] hillbeast:
Only feature missing in 2.0b2 is the fs.options is not supported.
[Galaxy 3 Android Development] satishynd:
thanks hillibeast

but does anyone have g3mod-2.0b2-nonoc tar??

i've downloaded g3mod-2.0b2-nonoc zip.. do i just tar it and put it in odin? did that it gives some error...
[Galaxy 3 Android Development] vleutmans:
Could battery drain be explained due to the "nervous" on-demand behaviour ?

I mean if you put on-demand 83-1200, then you will see the freq. jumping up a lot, even when idle. Even when you tweak scaling settings with setcpu, then it's almost impossible to let the CPU "rest" at 200 Mhz idle when scaling was 200-1200. Let the cpu rest at 83 mhz seems impossible. Check with cpuspy and you will see what I mean.
[Galaxy 3 Android Development] mankokoma:
the zip-file is to be flashed via CWM, chose zip from sd card.

sent from the desert

with XDA app
[Galaxy 3 Android Development] cool.darshak:
May be lag is coz of rom...you can try extreme version n keep cpu at little lower freq
[Galaxy 3 Android Development] bizjoya:
m already using 1.8 performance 200-1000 MHz .. do I need to uninstall setcpu and install it again to set the frequency 100-1000Mhz, ondemand after flashing 1.9 perf onedemand?? or shud i go flashing without changing anything??? :)
[Galaxy 3 Android Development] fuxmen:
U don't need to do nothing just unchceck set on boot
[Galaxy 3 Android Development] cool.darshak:
Set on boot works buddy
[Galaxy 3 Android Development] cdesai:
Nice logo! :)
[Galaxy 3 Android Development] schwarzerkreuz:
Hi Dharam, many many thanks for cpu minimum frequency 100mhz on performance, ultimate and extreme kernels. :)
[Galaxy 3 Android Development] cool.darshak:
Oh someone notices it...thanks
[Galaxy 3 Android Development] fuxmen:
I have one oppinion and just opinion. For me now having 4 version of this kernel is pointless. That amount of compiling and Uploading and for only change the max freq and kernel Hz??

I think that You can, to save some time make lite 83-667mhz and OC version 100-1400, because if someone want 1000mhz it set it with set cpu or other app. If someone have more then set more... Just a sugestion, don't know what U guys think about that...

Like now i have Ultimate but set 100-900, if i want more i set mor for example for Video playing or games
[Galaxy 3 Android Development] cool.darshak:
Kernel Hz are different :)...people can enjoy what they like...lower the kernel hz better the battery
[Galaxy 3 Android Development] harkan89:
Guys.. I have absolutely no idea what you've done with v1.9, but I'm getting a serious boost in performance now.. Boot up time under 20 secs.. Fastest I've experienced on my phone :D I dunno if its just me getting lukcy :P .. But I have to say.. AWESOME job with the new kernel..
[Galaxy 3 Android Development] zimbara:
great job with 1.9, serious speed and performance :) Just one setcpu question. I've put it on 100 to 800 MHz ondemand with set on boot always on and no profiles. Is that ok or should i change something? Thanks again :)
[Galaxy 3 Android Development] Dharam_Maniar:
it is good...
[Galaxy 3 Android Development] moole:
I humbly join in with a request for a version without compcache. 1.3.4 is still by far the fastest kernel for me, compcache is just causing lag...

No need for coding an on/off switching method for it - just one extra version of the kernel (perhaps extreme) without it would be excellent and much appreciated. :)

Thank you for your efforts!
[Galaxy 3 Android Development] Dharam_Maniar:
//ROM Dir

__system("mkdir /sdcard/Android/data/g3mod/roms/CyanogenMod6_ROM");

__system("mkdir /sdcard/Android/data/g3mod/roms/CyanogenMod7_ROM"); //Add CM7 Support

__system("mkdir /sdcard/Android/data/g3mod/roms/G3MOD_ROM");

__system("mkdir /sdcard/Android/data/g3mod/roms/Kyrillos_ROM");

__system("mkdir /sdcard/Android/data/g3mod/roms/Grigora_ROM");

__system("mkdir /sdcard/Android/data/g3mod/roms/AOSP_ROM");

__system("mkdir /sdcard/Android/data/g3mod/roms/DutchMods_ROM");

__system("mkdir /sdcard/Android/data/g3mod/roms/Kyorarom_ROM");

__system("mkdir /sdcard/Android/data/g3mod/roms/Indroid_ROM");

__system("mkdir /sdcard/Android/data/g3mod/roms/rom1_ROM");

__system("mkdir /sdcard/Android/data/g3mod/roms/rom2_ROM");

__system("mkdir /sdcard/Android/data/g3mod/roms/rom3_ROM");

__system("mkdir /sdcard/Android/data/g3mod/roms/rom4_ROM");

//Data + sd-ext Backup Dir

__system("mkdir /sdcard/Android/data/g3mod/data/Froyo_DATA");

__system("mkdir /sdcard/Android/data/g3mod/data/CM6_DATA");

__system("mkdir /sdcard/Android/data/g3mod/data/CM7_DATA");

//Kernel dir

__system("mkdir /sdcard/Android/data/g3mod/kernel/Froyo");

__system("mkdir /sdcard/Android/data/g3mod/kernel/CM6");

__system("mkdir /sdcard/Android/data/g3mod/kernel/CM7");

These are the new positions for ROMs, Data and Kernels...

The ROM's should be in system.img formats and kernels in .zip types...
[Galaxy 3 Android Development] m1trand1r:
flashed 5 min ago....excellent work....thank you...

Sent from my Gti5800

Kyrillos rom V7.1

powered by

G3mod ultimate kernel V1.9
[Galaxy 3 Android Development] dayusg:
froyo 1.9 lite kernel have two extended power menu:)
[Galaxy 3 Android Development] vleutmans:
I agree with your statement. I now use g3mod 1.4 also without compcache

until a new kernel is available.

Btw app2sd also is a source of lag, so i use link2sd

instead.Our phones are just too lite to enable

features that lean on our tiny processor :-)
[Galaxy 3 Android Development] zimbara:
I am having serious mp3 playback issues. Stock music player and winamp both lag, vibrate, black screen and exit almost every time when i try to play a song. Other than that no problems, and 3g speed has improved :)

What should i do about the mp3 problem?
[Galaxy 3 Android Development] pentagramII:
Ive got no any problem with music playback on the newest kernel. Maybe thats fault of ur ROM.
[Galaxy 3 Android Development] fuxmen:
Test kernel have great battery life and indicates it with good precision, testing from yesterday relase :) But i thought that it will have 83 stepings and lower voltage. But i understand that final 2.1 will have it
[Galaxy 3 Android Development] DaBigFreak:
Where to get the new 2.1 testkernel?

I treid something now. Wanted to add /data/data to sd-ext, using hybrid data2sd.

So I added in data2sd.dirs data. Worked, just reboot, /data/data was now on sd-ext. No real more laggin, 160MB free internal memory.

Because phone is laggin too much, now I wanted to go back. Only having /app and /dalvik on sd-ext.

So I went in data2sd.dirs, deleted till the two entries. Reboot, no user apps any more. So went in Rootexplorer (copied first to internal) and kopied the 3 folders back to internal...but from now on, realy strange folders were linked in g3mod.log, like /ap /lo /dalv looked like the folder-names were not read right.

Now I am trying to copy and paste stuff back, finding a way to get the /app /log /dalvik-cache back to work...

So, adding new folders is no problem, but going back is just pain. What about adding this in kernel/script, that if an old link is found on sd-ext, but not in data2sd.dirs, it will be moved back to place before. Should be automatic.

EDIT: So what realy finaly give me my system back, is the before done system-backup with CWM. AWESOME!!! I realy messed up my system, but this backup just made all as it was before. AWESOME job, happy I made all this, so now I know how to save my system, in minutes I got ALL my working system back, I am realy amazed!
[Galaxy 3 Android Development] neo1691:
I am on g3mod v b2, ROM: Kyrillos v8.1

can i use kyrillos, cm7 and cm6.2 roms via multiboot and hybrid data2sd??
[Galaxy 3 Android Development] KSLevel11:
Okey Hillbeast, thanks for help. Multiboot works properly! :)

I have one more question: If I use multiboot, DATA is backed up from current "status" of current ROM and then DATA is copied to EXT partition, or DATA is "downloaded" from "sdcard/Android/data/g3mod/data"?
[Galaxy 3 Android Development] manish19:
@Hillbeast

can i use hybrid app2sd on G3M 1.9?like if i copy the hybrid script to init.d folder and the hybrid data2sd files to g3mod folder under Android?
[Galaxy 3 Android Development] fuxmen:
OMG

Guys look at this battery graph:

36h of using, countless number of sms (~150) couple minutes of call, loot of active using of phone, wifi, data always on,

I'm soo happy with this test kernel! Hillbeast this is awesome, waiting for 2.1 with diffrent steppings :) and lover voltages :)
[Galaxy 3 Android Development] i_rnb:
Battery drain is gone after flashing g3modv2final twice & calibrating.. :)
[Galaxy 3 Android Development] hillbeast:
When you multiboot with Multi OS Data, it makes a tarball of your intdata and places it in /sdext/multios. It doesn't use the SD card partition because I wasn't sure if it would comprimise the integrity of anything, and I was worried it might get tampered with.

Yes and you will need Multi OS Data enabled.

If you use the script that I gave Kyrillos or Kyorarom, then yes, but the config must be in /system/etc/ I believe.

Okay. This test kernel has clearly fixed the battery drain. Mine lasted 24 hours and dropped 40%. I can now start adding features to it.
[Galaxy 3 Android Development] mankokoma:
FAT-partition... permissons permissions... but in a tarball - maybe okay :)

Mine is up now for 12:30 hours and still at 4010 mV.

Did not do too much, just one call and surfing a little wireless (no 3G). Deep sleep for 10:30 hours, means two hours of usage... I think that's fine!

Would it be easy to switch features with easy configs (like the compcache on/off way)?

I'm afraid that too much could be too much...
[Galaxy 3 Android Development] TheF3nix:
I am still facing the problem of being stuck at the g3mod bootscreen after i flash hillbeast test 067.
[Galaxy 3 Android Development] mankokoma:
delete fs.options, compcache and put the rest in the sdcard/Android/data/g3mod/ to standard helped for me.

sent from the desert

with XDA app
[Galaxy 3 Android Development] Digibonez:
With the the latest Moikop test kernel, I can't install anything from market. I believe it has something to do with the missing a2sd partitition (see my previous post in this thread).

Send from my Samsung GT-5800.
[Galaxy 3 Android Development] hillbeast:
Something is peculiar with the fs.options on /system. Will look into it.

Try:

chmod 777 /data/app
chmod 777 /data/app/*
chmod 777 /sdext/app
chmod 777 /sdext/app/*

And try again.
[Galaxy 3 Android Development] kyrillos13:
I have a bootloop too :/
[Galaxy 3 Android Development] hillbeast:
Something is weird with how it mounts /system... Try mounting it manually from adb shell and see if it continues to boot.
[Galaxy 3 Android Development] kyrillos13:
I will try it later.

Also:

# removes journal

tune2fs -o journal_data_writeback /dev/block/stl6

tune2fs -O ^has_journal /dev/block/stl6

# mount options

mount -o remount,noatime,nodiratime,delalloc,noauto_da_alloc,data=writeback,commit=600,barrier=0,nobh /system /system

I have those enabled.
[Galaxy 3 Android Development] TheF3nix:
Thanks hillbeast for looking it to it(:
[Galaxy 3 Android Development] hillbeast:
Hill Beast Test Kernel 068

http://www.mediafire.com/?0434j34y7bol7l9

I think I fixed the not mounting /system bug. This was caused by a change moikop did which moved some important mounting commands around, but they also made it so some of the commands weren't executed under certain configurations.
[Galaxy 3 Android Development] kyrillos13:
I am going to test it :p
[Galaxy 3 Android Development] hillbeast:
I am currently testing a different mounting option for the SDEXT in order to boost performance. Seems to be a bit quicker but I'm not sure if it's a placebo or not.
[Galaxy 3 Android Development] kyrillos13:
okay test kernel 068 boots fine :) What mounting option are you trying?
[Galaxy 3 Android Development] hillbeast:
Ah good that fixed it then. Basically I am referring to your App2SD script and I am using NO options apart from those defined in the fs.options and whatever Linux uses by default.

/dev/block/mmcblk0p2 /sdext ext2 rw,noatime,nodiratime,errors=continue 0 0
[Galaxy 3 Android Development] Pinak.ahuja:
fs.options for system is still not being read in hillbeast 068 kernel here is my fs.options

stl6 barrier=0,nobh,noauto_da_alloc
stl7 barrier=0,commit=7200,noauto_da_alloc,nobh
mmcblk0p2 barrier=0,nobh,noauto_da_alloc

and here is the output of #mount | grep ext

# mount | grep ext
mount | grep ext
/dev/block/stl7 /data ext4 rw,nosuid,nodev,nodiratime,relatime,commit=7200,barri
er=0,data=ordered,noauto_da_alloc 0 0
/dev/block/stl6 /system ext4 ro,nodev,noatime,nodiratime,barrier=1,data=writebac
k,noauto_da_alloc 0 0
/dev/block/stl8 /cache ext2 rw,nosuid,nodev,noatime,nodiratime,errors=continue 0
0
[Galaxy 3 Android Development] fuxmen:
For me everything is ok, just commit in fs.options should be 600 not 7200.. and some other options should be diffrend, maybe fs.options file is not right..

wait for hillbeast for reply
[Galaxy 3 Android Development] hillbeast:
Let me have a look into it.

EDIT: Can you do 'cat /init.rc | grep /dev/block/stl6' and post the results?
[Galaxy 3 Android Development] Digibonez:
Did so, but still the same problem. When trying to install anything from market, phone gives me "not sufficient memory to install this app error". Outside market, I can install everything without any problem. Tried already to install a different version of the market.apk. Now running version 3.2.0.

I'll try your latest test kernel now first and see if that would solve my problem.
[Galaxy 3 Android Development] TheF3nix:
Hillbeast, your test kernel is working great on my phone:D I think the battery problem has been reduced and doesn't pose much of a problem to me(:
[Galaxy 3 Android Development] Pinak.ahuja:
Here you go

export PATH=/data/local/bin:$PATH

$ cat init.rc | grep /dev/block/stl6
#mount ext2 /dev/block/stl6 /system ro check=no
mount ext4 /dev/block/stl6 /system nodev noatime nodiratime ro barrier=0 nobh noauto_da_alloc
$
[Galaxy 3 Android Development] mankokoma:
mine still stucks... (test068)

Mine still stucks. ADB SHELL (with stucking bootlogo):

- exec '/system/bin/sh' failed: No such file or directory (2) -

So CWM does work! But even there, /system is NOT mounted.

Put my fs.options (working with v2.0) back before flashing via update.zip (no PC available, but now I'm at home):

stl6 nodiratime,noatime,nobh,errors=continue 0 0
stl7 noauto_da_alloc,nodiratime,noatime,nobh 0 0
mmcblk0p2 noauto_da_alloc,nodiratime,noatime,nobh 0 0

ADB SHELL in CWM: (the funny is: stl6 IS NOT MOUNTED!)

Now deleted fs.options again. Unfortunately after reboot recovery "Device Not Found" from ADB (****)SHELL, but that's another story...

fs.options are deleted, so normal reboot.... okay - now starts...

BTW, do you use ext2 for the external?

Now ADB SHELL:

Where are all these strange options from? I disabled journal on ext4.

Why is it complaining about missing mtab (first time ever)? Why isn't /system not mounted in CWM?

Once booting again WITH fs.options... same result: exec '/system/bin/sh' failed: No such file... & in CWM /system (ext2) also NOT mounted.

Sorry for maybe useless looong post. Just wanted to document that

nothing changed for me with 068. Still no mount options possible.

---------- Post added at 03:17 PM ---------- Previous post was at 03:14 PM ----------

# cat /init.rc | grep /dev/block/stl6

#mount ext2 /dev/block/stl6 /system ro check=no

mount ext2 /dev/block/stl6 /system nodev noatime nodiratime ro

JUST WANTED TO ADD: THE TEST KERNEL WORKS GREAT! NO BATTERY DRAIN ANYMORE! The fs.options issue is kindergarden stuff, which I don't mind too much!
[Galaxy 3 Android Development] radek.god:
is it same or better like 2.0 OC beta v2 ?
[Galaxy 3 Android Development] realismo:
Unfortunately the drain problem still exist wit 68 too. I used to my phone update 3 or 4 apps with wifi on. The battery almost dropped 15 percent in 5 minutes. My battery was great wit 1.9 and also i had problems with b2 too. Same issue. Keep up good work Hillbeast!
[Galaxy 3 Android Development] EdisDee:
Hello,

I was messing around with the recovery and thought maybe you can adjust it a little bit. It would be fantastic if when you select the switch rom option, the recovery would backup my current rom, format the system and then switch to the selected rom.img. Is it possible?

Thanks in Advance.
[Galaxy 3 Android Development] hillbeast:
Odd. There are two spaces between barrier and ro. Check your fs.options and make sure there aren't two spaces there between stl6 and barrier. If it isn't then I will look at the code later today.

It seems the code for fs.options on /system are broken. I've always thought that there would be no need for fs.options on system though because you don't write to it, therefore all the tweaks for disabling the journal are unnecessary. I'm probably wrong on that though.

Will look into it when I get time.

I can do that, however personally I don't want to backup /system EVERY time, so it will take a while to switch, longer than it currently does.

Also I am going to make it so if /system wasn't mounted, that the kernel won't self-destruct the busybox.
[Galaxy 3 Android Development] EdisDee:
What about if the recovery would ask if you want to backup your rom? Is that possible?
[Galaxy 3 Android Development] hillbeast:
Ah yes I could do that.
[Galaxy 3 Android Development] EdisDee:
Please, mister hilbeast :) at least make the recovery to format system before switching roms. Because formating system is an extra thing you have to remember to do or else you will end up with a lot of apps from both roms :) Just like I did. And I'm not saying it's a good thing because i didn't want the mess I got after swithing :D So please, if it's not hard for you, please, do it... :cool:

---------- Post added at 12:46 AM ---------- Previous post was at 12:43 AM ----------

Or maybe even two options? backup, format and switch and a simple format and switch?

P.S. Not a bad suggestion for v2.1, eh? ;)
[Galaxy 3 Android Development] mankokoma:
You mean, it would have been fixed with deleting the line which affects /system?

That's logical - didn't try that.

And of course you are right - as ro mounted it makes not that much sense to put any options about writing anyhow.

But as I deleted the journaling and default mount options on ext4 partition (mmcblk0p2 / stl7) with tune2fs,

I still wonder where the options data=writeback & commit=20 belong from.

Are they taken from some compiled code? There was no way with 'find' & 'grep' to get the files where these options could come from...

So in order to check the battery life I won't change anything for now. btw, charged full and did calibration - now 6 h uptime 1h usage with wireless, still amazing 4128 mV left.

Thanks for your work and explanations!
[Galaxy 3 Android Development] hillbeast:
I am assuming these options might come from something automated then. I wouldn't know where to look to fix this. I will take a look if it becomes an issue.
[Galaxy 3 Android Development] m1trand1r:
i've been playin' around with my phone sth....messed all up...:)

had to do all over again...don't know if this is any good.. here is my battery stats screenshot....View attachment 756319

Sent from my hybrid sg3

multibooted

Kyrillos' 8.1 powered by

g3mod 2.0 OC
[Galaxy 3 Android Development] vivekchamoli:
Its ok ..you need to check the profiles and voltage calibration ..
[Galaxy 3 Android Development] kyrillos13:
@Hillbeast, can you add Smartassv2 governor? (I am not sure if this helps) I will test it in the next g3mod nightly :P
[Galaxy 3 Android Development] prem0621:
I tried many roms with G3mod 2.0.

My phone is not working up to the mark with G3mod 2.0.

Getting constant lags. No good wile i scroll or open any apps.

I feel its coz of hybrid data2sd.

I just downgraded to 1.9 and its working like charm.
[Galaxy 3 Android Development] TearsDontFalls:
Did you try several governors and different cpu settings, i have no lags with the non of with the governor performance.
[Galaxy 3 Android Development] hillbeast:
I will look into it.

I will upload my latest test kernel later today.