yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] SkOrPn:
@ JAC,

After following this code I get "32112640"

cat /sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/size

Listen I want someone to explain why several of us get a result of "32112640" * "512" = "16441671680" yet Voodoo works perfectly... Can someone please explain this, if it hasn't already? Voodoo works great on my 416MB NAND. My phone was purchased in the TMO store in Albuquerque, NM at 9am July 15th, the day it was released in the US and has a Box Date of 06/29/2010. Thanks for any insight you may have. Im just getting tired of seeing peeps say it dont work on the larger NAND, when in fact it does.

Just more info below to help figure this out...

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>adb shell
$ cat /sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/si
ze
cat /sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/size

[B][COLOR="Red"]32112640[/COLOR][/B]
$ mount
mount
rootfs / rootfs rw 0 0
proc /proc proc rw 0 0
sys /sys sysfs rw 0 0
[B][COLOR="Red"]/dev/block/mmcblk0p4 /data ext4[/COLOR][/B] rw,noatime,nodiratime,barrier=1,data=ordered 0 0

tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocha
rset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset
=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
/dev/block//vold/179:9 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,g
id=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-
1,shortname=mixed,utf8,errors=remount-ro 0 0
$

I bolded and made red my outputs. Is there an explanation for this? Lisa (or is it Linda?) says voodoo was enabled successfully every time I flash it... :confused:

Thanks
[Vibrant Android Development] SkOrPn:
MORE INFO

See post above ^

EDIT: Master has stated in a PM that he also has the 416MB NAND and is running voodoo just fine.... What gives?
[Vibrant Android Development] tissimo:
Does this kernel work with the ota JI6?

Sent from my SGS Vibrant.
[Vibrant Android Development] slighpcs:
Yes, I can attest to JI5 and JI6 personally. I have not however verified installing via Samsung's recovery method... renaming to update.zip, all has been through clockwork.

If your referring to the backport created, that is.
[Vibrant Android Development] demo23019:
It works but you need additional files before flashing, you cant just flash kernel on at the moment...it will brick

Go back to page 37-38 for info
[Vibrant Android Development] CappyQ:
Just tried this on JI6 using ClockworkMod Recovery 2.5.1.2, and the Old Kernel ZIP is hanging on "Installing update..." every time. I tried redownloading the file in case it was corrupt; no dice. Any tips?

EDIT: Nevermind! Got it working. Used this newer, signed ZIP instead: http://slighpcs.com/downloads/android/signed/OldKernelSupport_r1-signed.zip

Thanks for the help!
[Vibrant Android Development] bchalk:
I don't know but, no matter what I seem to do it doesn't seem to do anything... with the kernel installed.

>adb shell

$ su

# cd /sdcard

# rm -R Voodoo

# reboot

>adb shell

$ su

# mount

rootfs / rootfs rw 0 0

proc /proc proc rw 0 0

sys /sys sysfs rw 0 0

/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0

tmpfs /dev tmpfs rw,mode=755 0 0

devpts /dev/pts devpts rw,mode=600 0 0

/dev/block/stl6 /mnt/.lfs j4fs rw 0 0

tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0

none /dev/cpuctl cgroup rw,cpu 0 0

/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0

/dev/block/mmcblk0p3 /data_tmo rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0

/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0

/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0

/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0

/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/block//vold/179:9 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

#
[Vibrant Android Development] SkOrPn:
Yeah I got the same exact results like 100 times straight over a period of about a week. Then one day sombionix told me to have faith and try flashing froyo that does not brick via Odin, then flashing a true stock rom and setting Odin to repartition. After getting my phone back to stock, although I thought I already was, I then rooted, and installed Rom manager and clockwork recovery, downloaded a Bionix rom with JAC's OC/UV/Voodoo kernel and upon booting up heard Linda transform my NAND into EXT4, lol...

I dont know what else to tell people other than I have the 416MB NAND and Voodoo is working perfectly after following the fix posted in the OP here..

This fixed my voodoo woes and I have flashed several voodoo enabled roms and kernels since and each and every time voodoo gets enabled with no problems...
[Vibrant Android Development] bchalk:
Must have something to do with the repartition.

voodoo.txt

2010-10-11 06:57:38 Voodoo: model detected:

2010-10-11 06:57:38 Voodoo: this model is not supported

2010-10-11 06:57:38 Voodoo: running init !

I'll just wait for beta5, hopefully it should work with how it is now...
[Vibrant Android Development] SkOrPn:
Yup thats the EXACT same error I got to "this model is not supported". Pissed me off something fierce, but I did not give up and trusted his guidance. Now Im loving voodoo... YMMV tho, lol
[Vibrant Android Development] bchalk:
Worked, I decided to do it. Flashing the original 2.1 true stock firmware with repartition checked did the trick. Make a complete backup on your hard drive of your internal sd card first as it definitely will get wiped.

http://xdaforums.com/showthread.php?t=739091
[Vibrant Android Development] SkOrPn:
So voodoo is working now on your phone? And you definitely have the 416MB NAND?
[Vibrant Android Development] bchalk:
Yes. The repartition with that JFD stock rom I'm sure did it. Guide here: http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=8562641#post8562641
[Vibrant Android Development] SkOrPn:
lol, I dont need a guide, I fixed mine weeks ago... lol ;) VERY glad to hear about your success. Now we can spread the word.
[Vibrant Android Development] Master™:
I am pretty sure he copied my guide... And just added a bunch of stuff that was unnecessary
[Vibrant Android Development] bchalk:
So that guide doesn't list ticking repartition, does it work without ticking repartition? As I was thinking that was what was doing it... If not I guess it's just something else in the flash lol :shrug: I dunno, it's late.
[Vibrant Android Development] Master™:
Nope.. Thats what I did for mine to work. I have never repartitioned
[Vibrant Android Development] SkOrPn:
Well its actually sombionix's guide, he just updated it with steps to get you voodoo without actually running bionix. As he states in the guide, flash your nandroid backup after installing bionix w/voodoo. I dont think he needed to add any of that considering the fix might actually be just the repartitioning done by Odin 1.3.

Maybe we can investigate further by asking the next sucker to just try voodoo'ing their stock rom... lol
[Vibrant Android Development] Master™:
lol I meant the guide to enable voodoo not to do the other lol.. I did the exact same but like 5 hours before him :D

And the fix isnt repartitioning... I have never done that
[Vibrant Android Development] SkOrPn:
REALLY???? Well all I did was followed som's guide, and ticked repartition and that was the only thing that seemed to fix mine. Hmm, are we getting lost again. WTF fixed it then? LOL

EDIT: crap sorry but I have to go to bed. I wont be around for another 8 hours or so. Good luck figuring it out. lol
[Vibrant Android Development] Master™:
No idea, But I deff have the Larger NAND chip && voodoo enabled :rolleyes:

I have never repartitioned :confused:

Maybe it was the Froyo.. because Froyo wipes everything and might have done something else..
[Vibrant Android Development] BruceElliott:
ETA for JACs Kernel w/ Voodoo Beta 5?

Hi JAC,

Could you give us an update on when your kernel incorporating the newly-available Voodoo Beta 5 may be ready?

Thank you!
[Vibrant Android Development] geoffcorey:
Beta 5 has to be released for him to be able to incorporate it into his kernel.
[Vibrant Android Development] BruceElliott:
I saw on a different thread that JAC has received Beta 5 from Supercurio.
[Vibrant Android Development] miclflores:
So does that mean you have to actually set SetCPU to get the better battery life? If I don't set it up, does the Kernel still support the UnderVolting? I use the kernel but not sure if the UV is working since I never use SETCPU. Thanks for the help.
[Vibrant Android Development] evo9mrjr:
I'm using stock j16 rooted and wanted to flash this kernel over it of the uv oc color fix so I tried with odin and never booted... Will I get a diff result with clockwork recovery because this ain't working need help
[Vibrant Android Development] tenjhotenge:
Does Jacs kernel OC/UV WITH voodoo lag fix work on the J16? Because so far noone has tried it with voodoo yet. Only the OC/UV kernel.
[Vibrant Android Development] joshthewaster:
You need to get the back support files to be able to use these kernels. You can find those a few pages back and there is actually a seperate thread about it in the dev section with a zip file.

Anyway boot into clockwork recovery, flash the back support then BEFORE rebooting flash the kernel you want. Enjoy.
[Vibrant Android Development] evo9mrjr:
Will try thanx alot
[Vibrant Android Development] evo9mrjr:
Last question before I flash ... If I flash the kernel that has oc uv color fix and voodoo lag fix .... Will that automaticly enable the voodoo lag fix or is there another step after to get the lag fix ... I've only used the ext2 lag fix .... New to voodoo
[Vibrant Android Development] joshthewaster:
I don't use voodoo so I don't know. From what I've read it does. Flash and run quadrant, you'll know.
[Vibrant Android Development] Master™:
A lot of people have tried it, Bionix 1.7 is based on JI6 (Official Releases) and it works flawlessly!
[Vibrant Android Development] evo9mrjr:
yeah im about to try right now
[Vibrant Android Development] Segnaro:
You have to flash eugene's files for support of old kernels first, but yeah voodoo works. I got it on JI6 too. :D
[Vibrant Android Development] gravis86:
No need for SetCPU to take advantage of undervolting, just for overclocking.
[Vibrant Android Development] evo9mrjr:
ok i flashed Vibrant OC/UV V1.1 CWM Recovery on my j16 and im getting quadrant score is 2382 with the ext2 lag fix should i try voodoo or leave it alone.... if i should try voodoo i need to know which link and download do i use because m confused about the threads ive found kinda like im guessing which one to use,,, just give me the exact one to use or ill just stay with this thanx you guys have been a great help...
[Vibrant Android Development] Segnaro:
Use Voodoo OC/UV Beta4 CWM Recovery V1.1 from the front page of this thread.
[Vibrant Android Development] evo9mrjr:
i was going to use that one but upon reading it states if i have the big NAND that i have to wait for the beta5 and to come out because i have the big NAND but thanx i guess im on the right track
[Vibrant Android Development] joshthewaster:
There is a fix for that floating around. Think I saw it in the general section. If I see it I'll post a link.
[Vibrant Android Development] evo9mrjr:
Yeah I found the fix you were talking about but it will wipe everything I think imma wait to try that one later....thanx
[Vibrant Android Development] joshthewaster:
Oh didn't know that. I wouldn't either then.
[Vibrant Android Development] henreeg:
Anyone know this kernel goes hand-in-hand with the new update coming out?
[Vibrant Android Development] evo9mrjr:
New update? What new update it works on j16 yes if thats what your talking about
[Vibrant Android Development] joshthewaster:
But not without the back support files!
[Vibrant Android Development] j0hnZ:
I flashed this between the two posts above only to have my **** soft brick again...thanks for spreading around false information....another lesson learned.
[Vibrant Android Development] kaizasoshi:
And what might those files be? Thanks in advance!!
[Vibrant Android Development] slighpcs:
You have some options here:

1.) Flash the kernel after installing from Old Kernel Support packaged for the good people or here, [MOD] T959UVJFD Kernel support in newer builds (Flashable .zip).

2.) Install the kernel with Back support rolled into one also here, Old Kernel Support packaged for the good people
[Vibrant Android Development] joshthewaster:
As posted before

Just make sure if you flash you DO NOT reboot between the back support files and the kernal you want.
[Vibrant Android Development] kaizasoshi:
Thanks guys!!! worked like a champ
[Vibrant Android Development] j0hnZ:
Worked for me too!
[Vibrant Android Development] }{Alienz}{:
Any hope of making a 1.3Ghz Kernel, similar to KingClick's #4 version? I keep hearing about 12s on Linpack and that's quite high for an Eclair 2.1 Vibrant.
[Vibrant Android Development] Fedburin:
Is there any way to easily disable undervolting on this kernel maybe via a script in the init.d folder? I searched everywhere. The one option for another kernel wsa to remove the undervolting script from the init.d folder obviously UV is cooked into this kernel.
[Vibrant Android Development] BlackVision:
So no Beta 5 version for large NAND chip users for the Vibrant huh? I don't trust Masters post to trick the large NAND chip phone to working with the existing Voodoo lagfix. Plus you have to erase everything and use ODIN... too much work.
[Vibrant Android Development] draychi:
I've tried reading around for this, but can't seem to find the answer.

Is this fix able to run with JI6 stock?

It was great on 2.1, but even after a fresh re-install of JI6 and root, it won't pass the vibrant screen. King's kernel is doing the same thing, except with his, it just goes black.

Back to JI6 stock with Ryan's until I can figure something out.
[Vibrant Android Development] slighpcs:
This kernel works fine so long as you use the back-ported files. Have a look at this thread, or this post specifically.
[Vibrant Android Development] Master™:
Did you flash before disabling voodoo?
[Vibrant Android Development] Master™:
Heyy! Why don't you trust me? :D

But yeah, I thought that Beta5 was supposed to be released like 2-3 days ago :eek:
[Vibrant Android Development] draychi:
I'm not running Voodoo.
[Vibrant Android Development] draychi:
Thanks, looks like someone tested it and got it flashable, i'll give this a shot.
[Vibrant Android Development] slighpcs:
You are correct, all (recent) kernels have been thrown together as flashable Clockwork zips. As well, you can rest assured that I have personally tested everything I post unless explicitly stated (such as the Back-ported Voodoo Kernel). ;)
[Vibrant Android Development] BlackVision:
LOL...well somehow you tricked the existing voodoo lagfix to think the Vibrant is a I9000. I guess I would rather have voodoo lagfix know my phone is a vibrant. lol. But then I am sure JAC will probably undertake a similar trick in the beta 5 kernal? I read on his twitter page that he didn't have enough time to work on it because he was celebrating his birthday. So maybe it is coming soon?
[Vibrant Android Development] draychi:
It seems to want to install in CWM, reboots, then goes back into CWM...I try to reapply and it goes very quickly, and jumps back to the CWM menu.

This suppose to install automatically right?
[Vibrant Android Development] slighpcs:
I believe that's right, it will return to Clockwork after the flash, and you will need to tell it to reboot. I'm waiting on a call or I would verify for you. :D

If you are using the Voodoo kernel, I would assume it would be the same, but I have not tested it.
[Vibrant Android Development] draychi:
I'm on stock kernel... i just want the JAC 1.1 installed, no colorfix or voodoo.

It isn't installing though, opens package, then restarts clockwork into the menu, i'm on a completely stock rom flash with root....odd.

I have Ryans OCLF installed, mainly for the easy root, but I've tried flashing JAC kernel with ryan's stuff enabled and disabled.
[Vibrant Android Development] slighpcs:
I'm not sure I understand... here's how I go about installing:

1.) Download the zip to your sdcard, /sdcard/download for example

2.) Open Rom Manager from the menu and click "Reboot into Recovery"

Your phone will reboot into Clockwork Recovery mode (unless it hasn't been installed, in which case you'll want to reboot from the Samsung Recovery menu and repeat the steps)

3.) Choose install zip from sdcard

4.) I believe the next option is to Choose a zip file from sdcard (not positive... still waiting for the day to end or I would verify)

5.) Scroll down to and click on the directory "download", within you should find your file "Vibrant_OCUV_CWM_v1.1_JI6_r1-signed.zip", for example; Scroll down to and click on that file

7.) You will be prompted with a screen with multiple blank options and one of them will list the file name "Vibrant_OCUV_CWM_v1.1_JI6_r1-signed.zip"; Scroll down and click on that file

8.) The flash will take place and I believe drop you back into Clockwork Recovery mode; From here reboot and all should be well running on the new kernel
[Vibrant Android Development] djf8:
Any chance you are working on integrating some of ttabbal's work to enable back light notifications. I think it would be a pretty nice addition to your already amazing kernels.
[Vibrant Android Development] draychi:
Up and running now.. so strange, I've been doing all that step by step, except I was renaming the file to update.zip so I wouldn't have to browse for it. Leaving the original file name there works lol.

Btw, runing this JAC at 1.2ghz and using Ryans OCLF 2.2 is ****ing sick... so snappy and tossed me a 2750 quad, 9.9 mflop. So smooth.
[Vibrant Android Development] joshthewaster:
Since this is now possible is it possible to have the back light stay on as long as the screen? Or what I would prefer, Just turn them off completely?

I'm not ditching this kernel (it's too sweet) but it would be great to have this incorporated.
[Vibrant Android Development] IuNlockeM:
I don't see the folder of /system/etc/init.d

trying to OC like says on the bottom. am i missing anything?

NOTE:For compatibility with all phones this does not automatically OC to 1.2Ghz per Unhelpfuls idea as not everyone can handle 1.2Ghz. Use a user script in the init.d folder with

Code:

#!/system/bin/sh

echo 1200000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freqor setCPU to OC the Kernel to 1.2Ghz. 9.8MFLOPS is about what these CPU's average in Linpack at this speed. I've had it in the 10's and that may be coming back as another option.
[Vibrant Android Development] AnonymeLex:
I am little bit noob with this forum, is this kernel compatible for I900 (from samsung) ?
[Vibrant Android Development] }{Alienz}{:
It is not compatible with i9000 lex.

Jac, can you include BLN (back light notification)support in the next version of the kernel? They have it working and ready to integrate into other phones in the i9000 dev forum. It would be awesome if a port to the vibrant was done.
[Vibrant Android Development] morfic:
JAC, a search of the thread for .config comes up empty, think it's possible i could look at the .config for this kernel? Kernel came with Bionix 1.9.1, best Vibrant experience yet.

I asked Curio for his .config, his reply is defconfig+ext4+tun, which doesn't seem right.

So my curiosity is still going, much appreciated if you would share it.

Thanks,

Daniel
[Vibrant Android Development] jaliscojorge:
Hi, I ran into a problem when I installed the ocuv kernel with colorfix it said install completed and returned back to clockworkmod screen i rebooted and now phone is stuck on black vibrant screen. What can I do to fix this. I also tired reinstalling stock kernel and did a nandroid backup and no go. I also have the j16 update.

Never mind I used odin 1.3 to get back to stock then odin again to j16, and restored rom backup from last night and I'm back to where I left off. Only question is why did I get stuck at vibrant screen?
[Vibrant Android Development] c-pimp:
Jac curious if your next kernel will support the z4mod and since others are asking and id like to see back light notification as well ;)p

thanx again jac, your work is always the best!
[Vibrant Android Development] C-4Nati:
My question was just answered, thanks Alien.
[Vibrant Android Development] reuthermonkey:
I've been having this problem too. Slacker. Pandora. Music Player. I've tried all of them and thought it was the ROM. Glad to see it's the Kernel, and that it may be due to the undervolting. I'll go back to the stock kernel for the time being, but I look forward to the next JAC kernel update.
[Vibrant Android Development] rbirg:
I've tried searching but I haven't found any results.

I just installed Sombionix's Fusion, and I tried flashing over this kernel(1.1) with voodoo. Linda started talking, but then informed me I don't have enough space. What could be causing this? My phone booted up fine.

Does this just mean voodoo wasn't enabled, but the kernel flashed correctly?

Edit: never mind, restart fixed it
[Vibrant Android Development] SeanFloyd:
I installed the Bionix Fusion ROM today and since Voodoo was not included, I flashed it for the first time today over the ROM. Everything went great.
[Vibrant Android Development] Kubernetes:
Maybe JAC can make a version with less aggressive undervolting? It seems like a decent number of people can't use JAC's or KK's UV kernels, so this might be a really helpful mod.
[Vibrant Android Development] austindkelly:
Help Needed: I flashed the kernel after doing the JI6 update. I used the stock recovery version on my Vibrant. When I rebooted, all I get is the black Samsung Vibrant screen, I can hear the T-Mobile jingle but I never make it to the home screen.

I have tried to load the original kernel on to my external SDcard, but clockworkmod recovery will not let me mount the ext-sd. I have also hooked it up to my pc via USB cable and mounted the USB via clockwork and when i click the "E" or "F" drive it just says please insert disk.

Whats the best way to fix this, or how can I get the original kernel on to /sdcard so I can load it with clockworkmod recovery.

PS - I have also tried restoring with nandroid but it does not seem to have fixed it, so i suppose that does not change the kernel.
[Vibrant Android Development] joshthewaster:
Did you flash the back support files with the kernel? No idea how to get the files on so you can use clockwork but you could restore with odin, flash your backup and then try again.