yashsingh1/xdaforums huggingface dataset:
[Galaxy 3 Android Development] hillbeast:
ANY folder in the data partition can be moved. There are no limitations. You could even move the gps folder if you wished. Why you'd want to is another thing. Just specify it in the data2sd.dirs.
[Galaxy 3 Android Development] kyrillos13:
Okay thanks. I created a data2sd.dirs in /system/etc/ but i think it doesnt work. Does it need any permitions/owner settings?
[Galaxy 3 Android Development] bautrupp:
I had the problem with not mounted data-partition too. Now with v2 of the test-version everything is ok again. Your test-kernel from a few days ago was also fine and didn't make any problems.
[Galaxy 3 Android Development] hillbeast:
I don't think it needs any special permissions. Lemme see what it's doing on my end.
[Galaxy 3 Android Development] kyrillos13:
It seems that there are some errors in sdext and data partition (g3mod.log).
[Galaxy 3 Android Development] FadeFx:
Ok, so if i want to install latest test version over 1.6 with data2sd enabled, what would be the procedure to go? I guess its best to place the data2sd.dirs file and then flash the kernel, right?

----------------------------------------

tapatalked
[Galaxy 3 Android Development] Pinak.ahuja:
is interactivx governor supposed to be working properly in the latest test version ?
[Galaxy 3 Android Development] debaj:
I did this, but the directories are duplicated in /data and in /sdext, and the phone says that my internal memory almost full. What did I do wrong, or what else must I do?
[Galaxy 3 Android Development] hillbeast:
Yes there is supposed to be them in both sdext and data. There is something peculiar with the way it's doing something as I was also getting weird things to do with space. Which test kernel are you on?

I believe so. I haven't changed anything on it so I don't know.

If you already have DATA2SD, you should just be able to flash it with no issues.

Send me a copy of the logs.
[Galaxy 3 Android Development] moikop:
It seems to have a problem with not going further the max freq set with setCPU. Nothing serious though :P

I'm looking into it
[Galaxy 3 Android Development] debaj:
Hill Beast Test Kernel 25-09-2011v2
[Galaxy 3 Android Development] radek.god:
first crash "25.9 v2 kernel" - Terminal emulator

after restored by Titanium backup, ran "su" command" and allow superuser, phone freezed (SETCPU set to 83-1200 ondemand, but real speed should be 1000-1100 because of battery profile activated and set to 1000/1100 as max only )

Phone needed to be powered off by button as I get no response for Home button :-( ...
[Galaxy 3 Android Development] hillbeast:
Okay, I'm noticing some really odd stuff too with Data2SD Hybrid. I suggest everyone moves back to the kernel from 22/9/2011. It's not working right. I'm gonna take a look at it tomorrow.
[Galaxy 3 Android Development] radek.god:
I cant passed over 800 MHz, but after SETCPU data deleted and app removed and reinstalled, then after new frequency detect it works, I saw usage ALL frequencies steps from 83 to 1200 MHz ;)
[Galaxy 3 Android Development] kyrillos13:
Okay, but i think the wifi bug exists from 17/9/2011.. So take a look too :) And yes, Hybrid Data2sd isnt working (for me), in /system/etc/...
[Galaxy 3 Android Development] Pinak.ahuja:
Also it gets stuck on lowest frequency sometimes.
[Galaxy 3 Android Development] radek.god:
I tried 25.9 v1 and v2 only, at v2 I see no wifi problem yet. I am testing CPU+GPU by stability test with battery only and with battery % profiles, so as my battery level is lower and lower I am moving from 900 to 700 MHz and lower and lower too ... , for now 1h12m mins stable:cool: ...

Unfortunatelly I was not at 100%, so I did not tested stability over 1000 MHz yet, I will try it over night with USB/AC charge

I hope mentioned problems is with hybrid DATA2SD only (?). So If I will probably never use this, I should stay on "25.9v2" kernel until newer released.

I hope future kernel will NOT have data reset bug :D

I did not expect it and my call log and newer SMS are gone :mad::(
[Galaxy 3 Android Development] moikop:
mmm, I have set freqs with setCPU 400-800, and it goes from 400 (not less) to 800 and sometimes to 1200. It avoids freqs from 900-1100...

I'll look into it :P
[Galaxy 3 Android Development] dhirend_6d:
In multiboot, while switching ROMs, even if we get error(example: cound not find file etc) the dalvik cache still gets wiped irrespectively. It shpuld get wiped only after the ROM is istalled or if the ROM is detected correctly.
[Galaxy 3 Android Development] radek.god:
Ok All I wrote before was dedicated to ONDEMAND scalling.I think It works, but I see 1000/1100 those frequencies are nearly not used.I found this with G3MOD 1.9 too. Probably 1.6 too. I think phone does not used them.It was used obly when I set it by profile ...

Should not be this SETCPU apk limitation ? I am sure this apk was not designed for so many frequencies like G3MOD use.For example some of those frequencies are not vidsible at "circle percentage graph" :-o

Phone use mostly 1200,83, then 800,900 and 200 MHz

I will probably have to delete SETCPU data and turn off profile to have correct measures what phone use when 83-1200 ondemand scalling set :cool:

Now I am testing INTERACTVIVE scaling :

- It really ignore MAX freq.It use sometimes 1200 MHz even lower frequency set.But it is not so bad as it looks like, because it use 1200 MHz only for less than a second and then it follows cpu freq user limit ...

I get no restart, phone looks stable one or none force closure :cool:, but I will test 1200 MHz by stability test with AC power over night.We will see :cool:
[Galaxy 3 Android Development] moikop:
Oh, I though you were talking about interactiveX...

Well, ondemand hasn't been changed at all (except for one performance tweak I did some days ago, but nothing that would change it's behavior dramatically ;)). Ondemand has always been the same, and it works good the way it does now :p

Ondemand won't use all the freqs available always..

Yeah, if you use Ultimate or Extreme version, it will sometimes jump to 1200. But if you have, for example, Performance version, instead of 1200, sometimes it'll jump to 1000 :P
[Galaxy 3 Android Development] radek.god:
I hope there will be some profile what will use frequency really interactively.Or maybe interactively is not right word.What I mean is some scalling what will use ALL frequencies, so if CPU is more used at 900 , it will not jump directoly to 1200, but will move to 1000 , then to 1100 etc ...

We will see Extreme version stability :confused:

to this day I checked on my phone that Fugumod 1366 is 99.9 % stable vs ANY G3 MOD Extreme unusable at 1300/1400 and even Ultimate 1200 are not stable.

If it is not high kernel Hz problem, then it should be probably because of sync vs async freq ...

Kernel 25.9.v2 passed just only 45 mins at 1200 MHz and still is continuing, I will post result after 8-10 hours :cool:
[Galaxy 3 Android Development] mankokoma:
1. sometimes its really hard to follow your accomplishments... the test kernel is "only" ultimate.

2. why don't you use fugu, always praising them & dissing G3 kernels? there are still no problems 4 me with none of them...

3. for g3 i'm sure you just have to use correct advanced settings:

10000

90

0

200

then all freqs should be used.

sent from the desert
[Galaxy 3 Android Development] radek.god:
1) - I am noob and my english is very ****ty - sorry ;)

I think Ultimate is acceptable as max for me, but I want to have stable 1300/1400 when phone is connected to charger and I play some games ...

2) - G3 MOD has so many advantages, for me is most important specially implemented CWM with rfs support and fact that final version has not wi-fi bug as fugumod 1366 has.Unfortunatelly ALL G3MOD Ultimate or Extreme kernels was not 100% stable for me till now.I tested "25.9.v2 " kernel over night and

I can confirm I passed 9+ hours at stability test(CPU+GPU) :cool:

Great work

3) I am using posted advanced settings , I tried :

10000/15000/20000

85/90/95

always 0

0/200/250

And even with those settings 1000/1100 was not used (only when I set permanently 1000 or 1100 by SETCPU profiles... )
[Galaxy 3 Android Development] hillbeast:
Most of the time, if your phone needs more than 800MHz, it will just go right to 1200MHz, but the fact it doesn't touch 1000/1100 isn't much of a worry as you are using it at the time anyways and wouldn't you rather it just get the job done quickly then to mess around at 1100?

If your phone is needing 1200 while it's off then that's another story but 99% of the time 1200 will be fore when the screen is on, and you are stressing the heck out of the phone. so we won't put 1000/1100 as a top priority for getting fixed.
[Galaxy 3 Android Development] Benjamin_L:
Can you please stop using gay as an insult? Thanks!
[Galaxy 3 Android Development] aeriko:
I am using battery left widget and i get the values below: (i have hillbeast kernel v2)

System% : 62%

Estimated% :49%

I think the true value is present by app.. because my phone closes from battery when values are:

System% : 18%

Estimated% : 5% (this value is from app)

I had the same problem with 1.8 & 1.9 kernels..
[Galaxy 3 Android Development] hillbeast:
Yeah the current method for calculating the battery is a little off. We're gonna take another look at it.
[Galaxy 3 Android Development] aeriko:
No offense, my remarks are intended to improve the kernel and not to "attack" to developers.

You have done a great job so far ..
[Galaxy 3 Android Development] hillbeast:
Oh yes I know. I took no offense. We know the battery driver is screwy. It's just a really horrible thing to code because every change we make seems to make it worse.
[Galaxy 3 Android Development] radek.god:
I get restart when I confirmed superuser rights, so till now 1 reset and 1 total freeze when superuser used

25.9.v2 kernel - I went from 100% to 76% within 5 hours only :(

1.6 Ultimate kernel - It take so longer to get 80% from 100%

I will revert to 1.6 for daily use ...

can You use battery driver from kernel 1.6 ? :cool:
[Galaxy 3 Android Development] GryTEcHoG:
When we can expect 2.0 kernel? Just approximate time no offence
[Galaxy 3 Android Development] hillbeast:
Well G3MOD 2 is nearly ready. Apart from CM7 support and a few more tweaks here and there, we have it working. We still want to get the battery going nicely though.

And to the people who are impatient about CM7 support and blaming it on hybrid, it's not hybrids fault: it's preinit. There is NO preinit working on CM7 whatsoever and without that we dont' get fs.convert, hybrid Data2SD and anything else we need before the system inits.
[Galaxy 3 Android Development] FadeFx:
Right that moment when its done... nobody can know the exact time, not even the devs. But i guess it will be this year

----------------------------------------

tapatalked
[Galaxy 3 Android Development] mankokoma:
data2sd.dirs

I don't get it... made the data2sd.dirs (origin from kyrillos' app2sd-v2) file:

app

log

dalvik-cache

[BLANKLINE]

put it in /mnt/sdcard/Android/data/g3mod/

and after reboot I got

# busybox df -h

Filesystem Size Used Available Use% Mounted on

/dev/block/stl7 192.4M 115.2M 67.4M 63% /intdata

/dev/block/mmcblk0p2 982.3M 278.9M 653.5M 30% /sdext

/dev/block/stl7 192.4M 115.2M 67.4M 63% /data

/dev/block/stl7 192.4M 115.2M 67.4M 63% /data

...

/dev/block/stl6 209.1M 157.8M 40.7M 79% /system

/dev/block/stl8 33.5M 12.0K 31.7M 0% /cache

# mount

....

/dev/block/stl7 /intdata ext4...

/dev/block/mmcblk0p2 /sdext ext4 ...

/dev/block/stl7 /data ext4...

/dev/block/stl7 /data ext4....

...

/dev/block/stl6 /system ext2 ....

/dev/block/stl8 /cache ext2....

/dev/block/stl4 /efs rfs....

/dev/block/vold/179:1 /mnt/sdcard vfat....

/dev/block/vold/179:1 /mnt/secure/asec....

Only system-apps are on the screen...

What's wrong with me? :o
[Galaxy 3 Android Development] hillbeast:
Yes the sdext and intdata mount are a new method of mounting the /data from G3MOD v2 onwards. It makes Data2SD easier to mount.

But it not mounting the folders is a bit bizarre. Lemme think about this.
[Galaxy 3 Android Development] kyrillos13:
@Hillbeast, Feedback!! Data2sd isnt working :/ Check some errors in g3mod.log too.
[Galaxy 3 Android Development] hillbeast:
The log is telling me that Data2SD is disabled. You sure you have a fs.data2sd file which has hybrid written in it?
[Galaxy 3 Android Development] kyrillos13:
I tried the data2sd.dirs in /system/etc/ but it isnt working. Do i have to do anything else except the data2sd.dirs file?
[Galaxy 3 Android Development] hillbeast:
Yes in the /sdcard/Android/data/g3mod/ folder you need a fs.data2sd file which contains 'hybrid'.
[Galaxy 3 Android Development] kyrillos13:
Okay ty, i will try it.
[Galaxy 3 Android Development] debaj:
Wait, maybe this caused the problem I sent you yesterday, lemme check...
[Galaxy 3 Android Development] Mohanshbhr:
I have some problem with gmod 1.9 lite, in this kernel 'reboot' command is not working in terminal emulator and adb also, I tried 'busybox reboot' but it is also not working. It gives ' reboot returned' display. ' reboot recovery' is working. I did not checked in performance, ultimate, extreme.
[Galaxy 3 Android Development] ale_bot:
in some roms you need to type "reboot now" (without quotes) for reboot. dont know why :)
[Galaxy 3 Android Development] deadwood01:
Type reboot reboot n it works.... Its typed twice not a typo...
[Galaxy 3 Android Development] Orilin:
Aaah...now is clear! I neither created the file. I have created only data2sd.dirs in /system/etc folder.

When I turn back to home this evening I will try!
[Galaxy 3 Android Development] debaj:
Well, it caused a bootloop for me... trying factory reset now.

EDIT: Even worse: the bootup process crashes at the startup sound, plays about 3/4 part of it all over again... I suggest not to experiment with it if you don't have a backup and time to reflash.
[Galaxy 3 Android Development] hillbeast:
Yes in JPS they changed the reboot command for some stupid reason. You have to do reboot and a reboot option, however if you just put in an invalid option it'll reboot anyways. You can type 'reboot Uranus' and it'll work. Just won't reboot the planet or the bottom thing.

What ROM? If you're on my Kyorarom v0.3.0, have you put CMbins 0.3.0 on there?
[Galaxy 3 Android Development] debaj:
Yes, the only thing is that I use Kyrillos' apps2sd v2, maybe this caused the problem. Reflashing v0.2.0 ODIN version now, then try again after updating, if that works fine, I'll let you know.
[Galaxy 3 Android Development] cdesai:
This......
[Galaxy 3 Android Development] debaj:
Reflashed Kyorarom v0.2.0, factory reset, installed v0.3.0 beta, applied CMbins v0.3.0 patch with remove zip, then another factory reset just to be sure. Bootloop again when SD card is in the device (so it can read the fs.data2sd file). Without the SD card boots fine.
[Galaxy 3 Android Development] radek.god:
a) 0.2.0 is bad , I get same problems like You and many FCs and restarts

b) a2sd script, specially v2 is piece of .... after huge testing I can reccomend only LINK2SD as stable and usable if 512 MB ext part is used as MAX ...

I did not tried rather 0.3.0, but I tried as firts 0.1.x (? - mean previous before 0.2.0) it works +/- good with G3MOD kernel.With Fugumod 1366 kernel it works badly ...

---------- Post added at 03:56 PM ---------- Previous post was at 03:43 PM ----------

I have a question.

If kernel G3MOD 2.0 will be "hybrid" , I mean usable for CM7 too, then I should flash over this kernel any Gingerbread part from other phone and it should work ... ?

I mean I will flash only Gingerbread , not boot file and other incompatible files of course.

I am thinking about use Gingerbread from I5500 and/or S5830 ROM and flash it with correct name and with Apollo OPS of course

I know I5800 has stored Froyo at factoryfs.rfs and S5830/I5500 has stored Gingerbread at system.rfs file.

If I will flash over CM7 kernel system.rfs renamed to factoryfs.rfs as a tar file at ODIN I am sure it will work, but I did not tested this yet ...

But As bluetooth, FM radio and other HW parts does not work at CM7 for now, I expect it will not work at G3MOD 2.0 kernel too.Or Am I wrong ?
[Galaxy 3 Android Development] debaj:
I use v0.3.0beta, not v0.2.0. a2sd v2 did not make any problems for me yet, and as it seems, there is nothing to do with it.
[Galaxy 3 Android Development] hillbeast:
Okay, can you get to ADB when it's crashed?

The reason it works well on G3MOD kernel and not on Fugumod is because it's built around the G3MOD kernel. I never tested it for Fugumod, and the reasons for the force closes was because of CMbins which has been fixed up a lot in v0.3.0.

And no don't even attempt to flash the ROM form another phone. You will KILL your phone. I am not meaning a softbrick, you will KILL it because it will flash something in the wrong place and your phone will be dead. There is nothing to gain from using another phones firmware on ours.

This is what annoyed me about the post a person made saying they had done it because it's a total lie. DO NOT BE FOOLED PEOPLE IT IS NOT POSSIBLE TO RUN FIRMWARE FROM THE WRONG PHONE ON ANOTHER PHONE AND EXPECT IT TO WORK.

Also hybrid kernel doesn't mean 'it will run anything', it means 'it will run any G3 firmware'.

App2SDv2 works perfectly for everyone who uses it. I've been using it since Kyrillos made it. Not issues to report whatsoever.
[Galaxy 3 Android Development] debaj:
I forgot to save a dump (silly me, I was watching the logcat output in DDMS), but tomorrow I'll do it again after a full CWM backup. What I remember, there were a bunch of "file not found" errors with strange file paths like /data/data/appname.apk (as the /data folder were duplicated in itself) then the system core crashed with a null pointer exception. This was the first bootloop without the factory reset.
[Galaxy 3 Android Development] hillbeast:
Okay it might not have mounted something correctly. Every adjustment I make to it seems to backfire...
[Galaxy 3 Android Development] radek.god:
I understood If You will use incompatible OPS from another phone or You will try flash incorrect file name or file with bad content at tar.Then flash will not work or you will kill your phone.It is understandable.I do NOT want flash ROM from I5500/S5830 as it is.

I want flash only +/- 200 MB file from those ROM only. To be Froyo replaced by Gingerbread.All other files will stay like they are.Except kernel file.This have to be replaced to be able boot Gingerbread.I am sure if I will extract CM 7 files, content of 200 MB files will be +/- SAME ...

BUT if you will use Apollo OPS + correct file name "factoryfs.rfs" with correct size limit (~ under 200 MB ?) then WHY You should brick your phone ? There is NO reason to destroy it.Because You will flash similar files with same structure.You will only replace Froyo OS with Gingerbread OS.You will not flash boot or sbl files, so You should always be able go to download mode and flash Froyo back.

If I am wrong, then try explain me WHY I am wrong.I repeat, I will use Apollo OPS file and I will flash only one file - factoryfs.rfs at tar + CM7 /G3MOD 2.0 kernel at tar.

except me :D
[Galaxy 3 Android Development] marcellusbe:
Well ...

if you use another phone's firmware (exemple G5) on G3 ... it's a mistake. Why ?

Because of some android's libs like gps, lights, gralloc, copybits, wifi, bluetooth, radio etc... are specific to the hardware of the phone.
[Galaxy 3 Android Development] hillbeast:
Whoops. Clicked thanks by accident and it refuses to remove it.

Anyways... *facepalm*. Because our phone has a totally different chipset in it. There is nothing even REMOTELY similar about our phones. Even if by a fluke it booted, NOTHING will work. Graphics, touchscreen, sound, sensors, WiFi, vibrate, the lot will all be broken, and because the hardware is being accessed in the wrong way, for all we know it could catch fire. I am not kidding as bad drivers could do that. It could instruct the CPU power circuitry to send 3V directly into the CPU and fry the CPU. We don't know.

Let's compare the specs shall we:

Our Phone

CPU: S5P6422 @ 667MHz

GPU: FIMG 3DSE

RAM: 256MB

NAND: 512MB OneNAND with 9 partitions: (boot, Sbl, logo, efs, zImage, factoryfs, datafs, cache, modem, and one other partition I lack the effort to identify

WiFi: Wi-Fi 802.11 b/g/n

3G: 3.6Mb/s

Bluetooth: v3.0

Screen: 400x240

Galaxy 5

CPU: Qualcomm MSM7227-1

GPU: Adreno 200

RAM: 256MB

NAND: 512MB NAND (maybe OneNAND, I don't know) with COMPLETELY DIFFERENT PARTIONS

WiFi: Wi-Fi 802.11 b/g/n with DLNA

3G: 7.2Mb/s

Bluetooth: v2.1

Screen: 320x240

THE PHONES AREN'T REMOTELY THE SAME.

This isn't like running Windows 95 on a Core i7 where it'll just be missing stuff but you can use it alright. No this is a matter of it will not work no matter what.

If you really wish to attempt this then by all means go ahead, but I have warned you that this could KILL the phone. Again, it could be PERMANENT damage. Do you really want to risk it for something that won't gain anything? Don't be fooled people.
[Galaxy 3 Android Development] radek.god:
OK, but Marcell , how You did CM 7 workable ?

I am sure You just copied Gingerbread from another Samsung ROM or he copied part of CM7 dedicated to another Samsung model.

I understood You had to build CM7 kernel from the beginning or You used source files from another CM7 phone and make some changes before compile.

And HW specific ? I expect it is similar to PC linux, so one driver/lib is SAME for many chipsets.Marvell gigabit Yukon use ONE driver only for 10+ models of Marvell gigabit Yukon variation.I am sure at phone HW it will be same.And if BT/radio does not work, then HW is so different we need another driver like at CM7 ...
[Galaxy 3 Android Development] hillbeast:
marcell got it working through a lot of hard work by rewriting the drivers and such from scratch to make them compatible. ROM porting is really not that simple.

And no he used the standard CM7 source code, not code from another phone and is then developing it to work for specific hardware.

No, don't compare a phone to a desktop computer. Desktop computers have thousands of drivers installed with the system to be compatible, that is why Windows takes up 5GB of hard disk space while our phone uses just 220MB, and besides those drivers are for the same brand of chip anyways. Yes Marvell drivers will usually work with other Marvell chips, but it doesn't mean it'll work on an Intel chipset. It's the same thing here: the Galaxy 5 doesn't even have the components made by the same company. Our phone is mostly made by Samsung, the Galaxy 5 is mostly Qualcomm.

But anyways if you're so convinced it'll work then go ahead and do it, but every developer on this website will agree with me in that it won't work whatsoever, and any developer who is convinced otherwise really need to go back to university and learn about how drivers work.
[Galaxy 3 Android Development] bizjoya:
m on 3888 mV on 63% .. anything to worry about?
[Galaxy 3 Android Development] Dharam_Maniar:
not at all...
[Galaxy 3 Android Development] bizjoya:
My highest regards and faith on you.. :D thanx a lot .completely relieved. just for a query .. how about flashing g3mod 1.8 on stock JP6??
[Galaxy 3 Android Development] Dharam_Maniar:
yes, you can...
[Galaxy 3 Android Development] hillbeast:
I will look into having a more adaptive battery drop for the people who have fast 4.2-4V and people who have slow 4.2-4V. I am one of the slow droppers.
[Galaxy 3 Android Development] FadeFx:
Can u first test if it makes a difference if the phone is charged trough usb or wall adapter?

----------------------------------------

tapatalked
[Galaxy 3 Android Development] hillbeast:
Someone else will have to test this as my computer has a Gigabyte motherboard which supplies 3x the normal current through the USB ports, so essentially my computer provides more power to my phone than the wall charger.
[Galaxy 3 Android Development] satyamsit:
me generally charge it thru usb charger instead of wall charger.. almost 90% of times...