yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] dddtc2005:
Yes, the output below

rootfs / rootfs ro,noatime,nodiratime 0 0
tmpfs /dev tmpfs rw,nosuid,noatime,nodiratime,mode=755 0 0
devpts /dev/pts devpts rw,noatime,nodiratime,mode=600 0 0
proc /proc proc rw,noatime,nodiratime 0 0
sysfs /sys sysfs rw,noatime,nodiratime 0 0
none /acct cgroup rw,noatime,nodiratime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,noatime,nodiratime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,noatime,nodiratime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,noatime,nodiratime,cpu 0 0
/dev/block/mtdblock2 /system yaffs2 ro,noatime,nodiratime 0 0
/dev/block/mtdblock3 /cache yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mtdblock5 /radio yaffs2 rw,noatime,nodiratime 0 0
/dev/block/mmcblk0p2 /data ext4 rw,nosuid,nodev,noatime,nodiratime,errors=panic,
barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/mtdblock6 /datadata yaffs2 rw,noatime,nodiratime 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,noatime,nodiratime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,noatime,nodiratime 0 0
/dev/block/vold/179:9 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,noati
me,nodiratime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,noati
me,nodiratime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[Vibrant Android Development] DerTeufel1980:
Ok, we are getting closer ;-) this are the jellybean mountpoints, so I guess, it booted by fault with jb initramfs.

Could you now please attach your build.prop and also boot.txt.

I need to find the reason, why this happened. Thanks

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Vibrant Android Development] dddtc2005:
That's great. Here is the files. I pack the build.prop into a rar file cause the prop is not allowed to upload.

Thanks
[Vibrant Android Development] DerTeufel1980:
it is, as supposed.

in your build.prop, there is build id: IML74K

please change it to IMM76L

i am going to add the number to the next release....was thinking, that every ics rom is based on the latest IMM76L
[Vibrant Android Development] dddtc2005:
Great. It works well now. Thanks a lot!

Another question is what "devil idle" is?
[Vibrant Android Development] DerTeufel1980:
It changes internal dividers, to limit the main bus freq to 100 instead of 200, while screen off. This automatically does the same to ram and gpu, sets liveoc value to 100 and reduces int voltages by 50 mV

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Vibrant Android Development] hurtz777:
I was running the devil app but Bluetooth Kill was disabled. Anyone else have to reboot because Bluetooth freezes when turning on?
[Vibrant Android Development] dddtc2005:
In config app there is a option that says "Bluetooth Kill", it may keep on in default setting, you can just uncheck the box.
[Vibrant Android Development] dddtc2005:
I found "mediaserver" drain the battery a lot, but I'm sure any media player is closed. Not sure it is a ROM related problem or a kernel related problem? Is there anyone else have the same problem?
[Vibrant Android Development] Thismines:
Sorry if this is a noob question, i couldnt find any post about it thus far.. what is the difference between the CMC version and the VC version?
[Vibrant Android Development] Smartassassin:
One is cyanogen color one is voodoo color.
[Vibrant Android Development] Waldos:
This kernels are for what?

http://devil.haxer.org/Rc5_kernel/
[Vibrant Android Development] hurtz777:
Devil 1.0.0 RC5 works on both ICS and JB. Der 1.0.0RC5 is running amazing on the latest CM9 0719 Vibrant nightly. I also figured out that the Devil Kernel Config App v0.7 causes the bluetooth to not turn on without rebooting. The Devil Kernel Manager v1.5 works flawless and doesn't cause the bluetooth to hang up when turning on. The delayed Froyo RIL on CM9 nightly still gets unknown baseband for me with RC5 and CM9 0719 so I have to still revert back to the original Galaxy S RIL that works perfect. Thanks a million for working on this badass kernel!
[Vibrant Android Development] colorprint:
GPS not works with RC5 kernel and JB (CM10) :(
[Vibrant Android Development] nick1217:
Rc5 is great thanks!
[Vibrant Android Development] fraserwAstro:
Sorry for the noob question but can someone explain or link a post that explains the relation between the live oc high target and the live oc percentage? Percentage of what, the stock freq? Then wouldn't that conflict with the target high?

Also any way to play with voltages while using live oc?

Thanks
[Vibrant Android Development] DerTeufel1980:
i have updated the op/changelog with a link to cm10 kernels, to be used with teamhacksung's builds of jellybean. maybe i am opening a new thread for it this evening.
[Vibrant Android Development] maoten:
Tried the v1.0.2 on CM9 nightly 16/7/2012

the phone wont boot even into CWM.

went back to 1.0.0.RC5 through odin,

will try to flash the latest nightly then flash kernel back.
[Vibrant Android Development] lorendroll:
can't flash it on the latest remICS, stuck on a devil boot screen... 0.79 and subzero kernels works fine
[Vibrant Android Development] maoten:
yep, even with latese nightly CM9 23/7/12 i went back to Devil1.0.0RC5
[Vibrant Android Development] lbw321:
Will there be devil3 1.0.2 datadata for vibrant that can be used on your devil v5 port?

BTW,1.0.1 running super smooth now.
[Vibrant Android Development] DerTeufel1980:
Afaik there aren't big differences between vibrant and I9000 (maybe someone knows more about it) but I think flashing the i9000 kernel should work / at least boot.

I can't look at the issue till evening/night, but if your phone boots, or boots not with I9000 kernel, it would help to find the issue.

edit: just to make sure, i got you right: you were trying to boot with this kernel: Devil3_1.0.2-ICS_vibrant....

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Vibrant Android Development] nbhnohome:
There seems to be a glitch somewhere in 1.0.2 .

1-Flashing 1.0.2 right on top of 1.0.1 make the phone Stuck at "VIBRANT" screen and wont even boot back into Recovery no matter what I tried

Noob question: I found there is folder inside folder (one into another) (like a million of it :mad:) under Android folder on the Internal SD Card.

2- ODIN and Format the internal SD Card (there is no way I can delete that Folder without having to format the whole SD Card)

3- Reflashing the ROM with 1.0.2. The phone got stuck at the "Animation" screen

4- WIPE everything. Reflashing the same ROM with 1.0.1 then I'm back to business ;)

Thanks for your hard work
[Vibrant Android Development] nedlog:
Latest version working well on Zen 1.8.5. Real snappy.
[Vibrant Android Development] maoten:
Yes Flashed from "Devil3_1.0.0-Rc5_datadata_vibrant_CFS_BLN_CMC_20120719.zip" TO "Devil3_1.0.2_jb_vibrant_CFS_BLN_CMC_20120722.zip"

after that, phone get stuck at Devil logo.
[Vibrant Android Development] DerTeufel1980:
But this is a jellybean kernel. Are you using it with a jellybean rom?

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Vibrant Android Development] maoten:
Opps... Thought. It will work as i checked 1st post in thread saying its. For ics rom only. And supports JB.

That's. What i understood.

So i have to get the one without jb in the name which. Is located in another folder

http://rootaxbox.no-ip.org/divers/Devil3_1.0.2-ICS/
[Vibrant Android Development] DerTeufel1980:
This would be the right one.

There have been too many changes lately, to use one kernel for both

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Vibrant Android Development] testomat:
I flashed Devil3_1.0.2-ICS. Get now unknown baseband. Coming from AOKP Milestone 6 and subZero v1.5 Build #159 (Sunshine_And_Bacon).

Is there a fix ?
[Vibrant Android Development] mryounghc:
i installed rc5 yesterday and GPS is sick. initial lock can take a while (1min in my case) but afterwards i had no more than 25 seconds so far after ds. best i have ever had so far including froyo. i am going to try the newest now

forgot to mention im on remics 1.2
[Vibrant Android Development] nirogu325:
That's awkward. I too moved from that specific build of SubZero kernel to this one hours ago and still have my baseband, all good. The only difference being I'm using the latest SlimICS ROM (4.2). I even went ahead and activated zRAM successfully.
[Vibrant Android Development] DerTeufel1980:
Please try using an other ril. The Froyo RIL sometimes is making issues with my kernel. There is a flashable zip by mr_psycho somewhere.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Vibrant Android Development] testomat:
Found Mr. Psycho froyo ril at root Wiki in his kernel thread and flashed it, but same problem :(
[Vibrant Android Development] DerTeufel1980:
Not the Froyo RIL, this is default and making the issue :mad:

You need to use the other ril package.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Vibrant Android Development] testomat:
Thanks. It worked with the other ril. Super Arbeit Teufel!
[Vibrant Android Development] Moronig:
Stuck at devil logo

Same here, both Devil3_1.0.1_datadata_vibrant_CFS_BLN_VC_20120722 and Devil3_1.0.2-ICS_vibrant_CFS_BLN_VC_20120722 leave me stuck at the devil boot screen.

Had to do an advanced restore of the boot partition from a previous devil kernel for it to boot.
[Vibrant Android Development] Shiv4m:
Do kernels control the GPS? If it does, how is it on this kernel?
[Vibrant Android Development] hurtz777:
Original Samsung Galaxy S RIL Revert

I have "Unknown Baseband" errors with the latest Devil ICS/JB kernels with CM9 Nightly builds and CM10. This is definitely caused by a combination of the Devil kernel and the stock Vibrant Froyo RIL that is standard now in CM9 Nightly builds and CM10. Some Vibrants will work perfect with the Froyo RIL in ICS/JB. Some Vibrants will work with the Froyo RIL with a delayed start in kernel on ICS/JB like my Vibrant. Some Vibrants will only work with the original Galaxy S RIL in ICS/JB. It looks like the majority of Vibrants always work with the original Galaxy S RIL, second best is Froyo RIL with a delayed start in kernel, and only the minority of Vibrants work with just Froyo RIL in ICS/JB. I have attached the original Galaxy S RIL revert that MP made called cwm-revert-ril.zip as well as the stock Froyo RIL called cwm-froyo-ril.zip that is flashable in CWM and it will work for most Vibrant owners with ICS/JB and Devil/SubZero kernel. Just flash your RIL zip of choice in CWM and reboot.
[Vibrant Android Development] fraserwAstro:
Yes kernels can affect gps performance. With rc5 the gps is as good as it ever was imho
[Vibrant Android Development] hurtz777:
Der is there any way you can make the next Devil ICS kernel delay starting the Froyo RIL just like the stock CM9 0724 does so some of us don't have to use Galaxy S RIL to avoid the unknown baseband error? Devil3 1.0.2 ICS version won't even initialize GPS or turn on the GPS icon because of the GPS lib changes in CM9 0724 nightly. SubZero #159 also has no GPS with 0724.
[Vibrant Android Development] FaultException:
The GPS part is our problem not Devil's.
[Vibrant Android Development] DerTeufel1980:
i am using the same init.aries.rc as the stock kernel now (release 1.0.3). hope it works. please report back

Edit: i didn't see changes to kernel related to gps libs, but I am taking a look at it again
[Vibrant Android Development] davidgs:
Release 1.0.3 is working good for me with the latest CM9 nightly (0725), no baseband issues...

For me, GPS stopped working with this CM9 nightly (stock or devil kernel)
[Vibrant Android Development] hurtz777:
Der I still get unknown baseband with CM9 0725 and Devil 1.0.3 and CM10 V8 and Devil 1.03b JB. Are you sure Devil kernel is delaying the start of Froyo RIL just like stock CM9 kernel? Flashing the Galaxy S RIL revert gives me working baseband just like past Devil kernels. It has been confirmed that GPS is broken in CM9 0725. I also can't get GPS to initialize and show icon on CM10 V8 and Devil 1.03b.
[Vibrant Android Development] tichs:
Hi Guys I try to port this to the t959v but it bootloops. It loads and everything but it just gets to the splashscreen and reboots. Looks like I think some files need some tweaking to match the phone's properties
[Vibrant Android Development] DerTeufel1980:
I just have copied the init.aries.rc from fe. I did not make any changes to it, to be sure it works now. Weird.

Maybe I can start the rild even later.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Vibrant Android Development] DerTeufel1980:
At least you have to modify initramfs, to match yours needed.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Vibrant Android Development] FaultException:
Yeah try hooking the rild start trigger to the boot animation end. Also, which init.rc are you using and did you modify it?
[Vibrant Android Development] DerTeufel1980:
I copied the one from your commit, using froyo ril. I did not change anything.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Vibrant Android Development] DerTeufel1980:
please try, if this kernel fixes the ril issue with froyo ril.

i am starting the rild now, when bootanimation has stopped. i don't think, i could start it later ;)

Don't use this on cm10. Ics only kernel!
[Vibrant Android Development] tsiah:
Flashed this on my vibrant with cm10 v5 and the phone wouldn't even boot...
[Vibrant Android Development] DerTeufel1980:
Because cm10 is not ics. Sorry, I should had post a warning. I thought the ICS in filename would be enough.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Vibrant Android Development] tichs:
I'll try that, If this works and boots most certainly would be the best thing. the things that I have to change though is that kernel shows itself for t959v galaxy s 4g and not vibrant.

Well I found that the vibrant "vibrantmtd" is also causing issues and it has to be changed to galaxys4gmtd and it has to be added to the build.sh. I don't know if you can try it also using the working source https://github.com/teamacid/android_kernel_galaxys4gmtd
[Vibrant Android Development] FaultException:
No, I mean the init.rc not the init.aries.rc.
[Vibrant Android Development] DerTeufel1980:
oh, didn't get this...init.rc...could not find the file for vibrant at github.

here is mine:

https://github.com/DerTeufel/samsung-kernel-aries/blob/ICS/usr/vibrantmtd_initramfs/ics_init/init.rc
[Vibrant Android Development] hurtz777:
Der I just tested 1.0.4 and it is still unable to get baseband with Froyo RIL on my phone. Are you sure you have implemented the same init.rc as FE?
[Vibrant Android Development] FaultException:
Init.rc is in android_system_core/rootdir

Try using that one maybe.
[Vibrant Android Development] Moronig:
If I'm coming from another kernel, what version of Devil do I need to flash before the latest update? If I flash just the latest file, it hangs on the kernel logo.

Thanks!
[Vibrant Android Development] DerTeufel1980:
the files are almost the same: here are the differences:

1. i don't execute this: exec /system/bin/sysinit

2. i am starting this service (which also executes init.d):

3. socket zygote stream 660 root system (this is yours)

this is mine: socket zygote stream 666

everything else is the same

i am going to change 3. now. the other don't seem to be important ;)
[Vibrant Android Development] hurtz777:
Der if you could also please make the GPS changes that FE made to his CM10 V8 kernel so that GPS will work again on Devil JB kernel that would be awesome. Thanks for all you do!
[Vibrant Android Development] tsiah:
Oh, I assumed ICS kernels were the same. There's a devil 1.0.1 kernel on my phone now and I thought this was a new version of the same kernel.

My bad :)
[Vibrant Android Development] DerTeufel1980:
Sorry. I try to make a new topic for jellybean as soon as possible.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Vibrant Android Development] DerTeufel1980:
attention: jellybean only (official one, not a port of my rom (this kernel has no datadata partiton))!

please test gps and froyo ril :)
[Vibrant Android Development] hurtz777:
Der 1.04 Test 3 kernel is finally working properly by delaying the start of Froyo RIL in CM10 V8! I would also like to note that Galaxy S Settings actually works with official CM10 V8 where it would freeze with a blank screen with the stock kernel. As far as GPS I get the GPS icon but no satellites in view. I did flash yagf2 fix earlier and that might have broke it. I will fresh flash later and let you know if anything changed.
[Vibrant Android Development] mryounghc:
i dont think it is the fix. i have the same problem without the fix. i tried to check settings with fasterfix and fasterfix cant change servers.

well after sitting for a few minutes i now have 2 in view but no locks yet. i dont know if it is because i am on pool ntp but i dont know how to change it without fasterfix. ill let it sit for a while longer to see what happens
[Vibrant Android Development] FaultException:
Wow, so it is the zygote change?
[Vibrant Android Development] mryounghc:
weird, now iam able to change my server. idid nothing different but kept trying....

i'll check how gps works now
[Vibrant Android Development] hurtz777:
Der I just tested your CM10 V9 port and 1.0.4 datadata kernel and I get unknown baseband with the included Galaxy S RIL and the Froyo RIL. Many other have confirmed this bug. I would just use the delayed Froyo RIL fix that works in 1.0.4 test 3 in the next datadata kernel and we should be all set! Is there any way you can archive the older kernels in a folder on the ftp server? I was wanting to to try our 1.0.3 datadata kernel to make sure the issue is the kernel and not the V9 rom.
[Vibrant Android Development] DerTeufel1980:
No, I must have overlooked something else. I can't remember the change exactly right now, I'll post it later.

Now to the next issue :P

I took your latest init.aries.gps.rc, which other changes did you make to get GPS working?

I'll try to make some kind of archive. I have deleted some kernel yesterday, while trying to get a better order.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Vibrant Android Development] Dougfresh:
Wow! There's a bunch of crying babies in this *****....DerTer'ers kernel are excellent!! It's a bit confusing due to the version ##'s, but a bit of searching will bring ya great results
[Vibrant Android Development] FaultException:
In CM10 or CM9?

I committed a GPS wrapper to both to get the old GPS going, but that's ROM side. Note that CM9's GPS (on the latest nightlies) is not working period right now, so it's not your kernel's fault.

In CM10, I changed "GpsWrapper" to "noaslr" and now does not replace the gps daemon, but rather is a binary used to execute the daemon in init.aries.gps.rc like so:

/system/bin/noaslr /system/vendor/bin/gpsd
[Vibrant Android Development] Dougfresh:
Dan B !! You're the shizz. I hope we'll see ya in the SGS3 forums.
[Vibrant Android Development] kobesabi:
Thanks, I tested this on FE's CM10 preview v8 ROM, it seems to work great.

Advanced Menu / Galaxy S - shows up correctly now

GPS - sees 12 birds at about 1 min...locked 5-6 bird in at about 5 min

GPS toggle - no longer cause reboot

Gallery - still shows blank screen. I'm not sure if this is ROM or kernel related. I have cleared out data and tried several program to scan but shows up nothing. However, Root Explorer can see all the files fine. Camera 360 can see all its pics taken fine. Just Gallery not populating all the pics.

Edit: On GPS toggle, if you toggle off...wait a little bit/lock screen...unlock back in..then turn on...then it does not reboot crash. if you do it on/off fast enough consecutively, it will crash reboot
[Vibrant Android Development] FaultException:
Wut? Stock still does this. What did you do Der!?
[Vibrant Android Development] kobesabi:
I just discover new problem I think and it's repeatable.

If I put it on airplane mode, then later airplane mode off, then turn on gps then off gps, it later reboots within 10 sec later.
[Vibrant Android Development] FaultException:
Try just toggling GPS without airplane 3 times.
[Vibrant Android Development] kobesabi:
Without airplane mode, I still works after 3. It reboots on the 5th time.

Edit: if i do on and off fast enough, it will reboot on the second On...so I guess the result is no fix yet?
[Vibrant Android Development] DerTeufel1980:
if anyone wants to try:

i have compiled my i9000 rom for the vibrant today as well:

http://download.rinik.de/rootaxbox.no-ip.org/devil_jellybean/rom/20120729/

it's a jellybean rom, compiled from the latest sources of teamhacksung/faultexeption

if you are coming from a different rom, you have to wipe/factory reset.

more infos here:

http://xdaforums.com/showthread.php?t=1775169

and here:

http://hellybean.site11.com/

till now, no one has tested the rom. it could be possible, that it does not boot

please everyone who wants to try, make a nandroid before.
[Vibrant Android Development] hurtz777:
Der I get the following error after wiping and installing Helly_Bean_vibrant_20120729:

set_perm: some changes failed

Status 7
[Vibrant Android Development] Drjjones426:
I can confirm. I get the same error when attempting to flash
[Vibrant Android Development] hurtz777:
Der I just ported your Hellybean 072912 I9000 release to the Vibrant and it flashes perfectly so there is definitely something wrong with Helly_Bean_vibrant_20120729. Unfortunately Devil 1.0.5 gives unknown baseband on both Galaxy S RIL and Froyo RIL so it looks like we have gone backwards from both RIL and GPS working on 1.0.4 Test3. I also tested the slightly older kernel you included in your Helly_Bean_vibrant_20120729 and it is also unable to get baseband. Devil 1.03datadata gets proper baseband but doesn't work with delayed Froyo RIL and of course no GPS. I would use 1.0.4 Test3 as a functional base to add on to when making your HellyBean(datadata) and your CM10 Stock Devil kernels. Please bring back some more Voodoo Color love man!
[Vibrant Android Development] DerTeufel1980:
There have been changes to the rom, this is why my jellybean kernel is working with FaultException's rom, but not with the port of mine.

Can you do:

adb shell

cat tmp/recovery.log

Right after install failed. Then you could add the missing file, or remove the line from updater-script and install it.

Sorry for the issue :(

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Vibrant Android Development] lbw321:
Missing some files in system/vendor or that's part of changes from source?

So that would cause the error:confused:
[Vibrant Android Development] DerTeufel1980:
I have to flash the rom myself later to find the issue.

Changes are related to gps and data. This is why the I9000 port does not work correctly.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Vibrant Android Development] hurtz777:
Der don't forget to use Vibrant KA7 or preferably KB5 modem in the next HB Vibrant build. I can't believe how much work you do for us!
[Vibrant Android Development] lbw321:
+1

Really appreciate ur work for us.
[Vibrant Android Development] nick1217:
What is the difference if I select smooth governor profile vs normal on smartassV2 and can. I use devil idle and deep idle together?
[Vibrant Android Development] DerTeufel1980:
Could you link me the modem please.

I also found the issue. Trying to build new rom today.

Smooth is tuning each governor to be faster.

You can use it together

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Vibrant Android Development] testomat:
Look here Teufel for modems

http://xdaforums.com/showthread.php?t=868774
[Vibrant Android Development] Waldos:
That modems are for 2.1 and 2.2

If you want ICS modems > http://xdaforums.com/showthread.php?t=1399722
[Vibrant Android Development] wizel420:
appropriate kernel

does any one know if this kernel is good for:

JELLYBRO CM10 KANG build: VIBRANT

??

thanks in advance
[Vibrant Android Development] Waldos:
Try 104 Test3 DerTeufel Kernel. The best combo