yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] IDisposable:
Thanks and report

Thanks tons for this kernel. I've been running 0.1 since it was posted and I have no issue with battery. I do NOT use bluetooth, so that might be a factor, but it runs awesomely well.

For my stats, I'm running Airflip's ASOP, KJ6 modem, 0.1 kernel, and a bunch of unbloat using the script-building tool. It's essentially perfect.
[Samsung Galaxy S (4G Model)] jb0ne:
I'm really looking forward to voodoo sound being built in to this kernel...and any other optimizations bhundven puts in. Despite it being beta, this kernel is the best so far for me.

Ok dumb question -- this is *just* the kernel, right? Doesn't touch the modem?
[Samsung Galaxy S (4G Model)] bhundven:
Just the kernel. Doesnt touch anything else. No need to wipe anything. Does automatically install su, superuser.apk, and bootanimation binary.

How it all works will change in the future.
[Samsung Galaxy S (4G Model)] 7TimesCursed:
Sometimes my phones screen can't turn on. For example, it rings but the screen stays off. And the power button doesn't turn it on. Only way to get my screen back is doing a battery pull.. BTW no real battery life issues here either.

I keep GPS on but not BT.

Juice defender manages my wifi.
[Samsung Galaxy S (4G Model)] bhundven:
Go back to v0.0.2d. Don't use v0.1.0.
[Samsung Galaxy S (4G Model)] lumin30:
Is this recommendation specific to his/her situation?

Sent from my SGH-T959V
[Samsung Galaxy S (4G Model)] bhundven:
v0.0.2d is the last "Known-Good" version. There is a problem with v0.1.0.

This is my recommendation for

everyone

until I release a new version.
[Samsung Galaxy S (4G Model)] jb0ne:
If I'm already on 0.1.0 will I encounter issues going back to 0.0.2d? Like with cwm for example?
[Samsung Galaxy S (4G Model)] hechoen:
BH what is the issue with v0.1.0? I've been on it since you released it a few days ago and it seems to be working really well. I hadn't tried any of the other releases so maybe I just don't see the problem. Anyway thanks again for all the work your putting into this kernel.
[Samsung Galaxy S (4G Model)] bhundven:
I guess if you dont notice any problems, then do what you want. :)
[Samsung Galaxy S (4G Model)] bhundven:
Ive documented the problems in the issue tracker and the commits ive made on github (see my signature.).
[Samsung Galaxy S (4G Model)] hechoen:
Yeah thanks for that. It's the same issue I thought. Just wanted to make sure it wasn't something I didn't know about. Again there is zero battery issues for me. I just got 2 days off one charge on valhalla. If you want the logs let me know.
[Samsung Galaxy S (4G Model)] itzik2sh:
Hi

I want to express my deep and sincere gratitude to Bhundven for all the great effort put in developing, listening, providing and helping the people of this community, no matter how noob they sometime seem to be. I think some of us (maybe youngsters, i don't want to generalize) got spoiled and forgot people here have real physical lives with spouses and children and real life chords and not our (probably underpaid ;) ) employees.

So after that said, i want to say i somehow feel KJ1 kernel booting longer time and having to be superuser updated, but actually working much faster. Is there any tool or anyway i can quantify these differences to help the development? I'm running Valhalla Final with Adrenaline shot 12.

Thanks!

Sent from me
[Samsung Galaxy S (4G Model)] bhundven:
And just to be clear, it's not just me. Take RaverX3X for example. Dude is doing all his rom dev without a dev box. He is on a laptop he paid $50 for, until he gets back home. That's pretty friggin impressive.

Not right now. The next version will have a different recovery and a different boot-time profile.

I'm not expecting anyone to provide any feedback on the kernel at this point. As things are in flux right now.

RaverX3X's Valhalla BlackEdition comes with a 'pre-release' of v0.1.1 (v0.1.1-rc1). This version disabled deep idle and dma acceleration. Should be much smoother then v0.1.0. I didn't fully release this version because the next version will change soo much and this change was soo small, that I didn't want to bother.

I should have something ready for testing after the new-year.
[Samsung Galaxy S (4G Model)] nemoboy07:
Just to clarify... This kernel doesnt support oc right? just tested it and it really doesnt work..
[Samsung Galaxy S (4G Model)] crackpot:
I assume you mean OC as in overclock, in which case it handles it fine for me. I'm running at 1.3ghz (1.0ghz is stock), using Tegrak Paid.
[Samsung Galaxy S (4G Model)] Juls317:
fine here too using an OC/UV set up
[Samsung Galaxy S (4G Model)] bhundven:
Right, this kernel doesn't by default have any oc/uv built in. But tegrak should work.

(btw, your signature says 'kg6' where it should say 'kj6')
[Samsung Galaxy S (4G Model)] Juls317:
i'll fix that when i can get to my laptop haha thanks though
[Samsung Galaxy S (4G Model)] itzik2sh:
Bhundven, you're welcome to join my QA team (only problem you need to relocate to India).

As far as what you said about Raver, the guy's a living SGS 4G legend...

Sent from me
[Samsung Galaxy S (4G Model)] ericmpanda:
Bump for a Happy New Years Best Wishes !!!
[Samsung Galaxy S (4G Model)] bhundven:
Haha! You too!
[Samsung Galaxy S (4G Model)] hampsterblade:
Happy new year. My phone made a new years resolution to be running cyanogen mod. Hehe.

Keep up the good work. Cant wait to see the next version.
[Samsung Galaxy S (4G Model)] Fluidification:
my phone's resolution is to be running CM9 by the summer.?!?>?> Don't know if it is possible.
[Samsung Galaxy S (4G Model)] Exodian:
Its possible. Just need the right knowledge and skill to be able to build it. I wish I was code savvy but im not. However, I will donate something very nice to the person or team that makes it happen.
[Samsung Galaxy S (4G Model)] Fluidification:
Bh, how is kernel coming along?
[Samsung Galaxy S (4G Model)] Caligula36:
+1, not asking for eta, just whats in progress
[Samsung Galaxy S (4G Model)] htaak:
http://xdaforums.com/showpost.php?p=21040800&postcount=7
[Samsung Galaxy S (4G Model)] Fluidification:
dude, I know the plans, I just want to know where he's at.
[Samsung Galaxy S (4G Model)] FBis251:
I think you didn't read this part:
[Samsung Galaxy S (4G Model)] cannondale0815:
Man, FB, was that really necessary? It hurt my eyes...
[Samsung Galaxy S (4G Model)] FBis251:
It's just that he keeps making posts without reading. :/. I'll change the color back to black.
[Samsung Galaxy S (4G Model)] bhundven:
If I were in school, and had nothing to do from the time I got homework/exams done and the next class, I'd a had cm7 done 3-4 days after the source drop came out.

Unfortunately, that is not the case. And I've stated over and over again about how I am busy, and can only dedicate less-then 20% of my time on the kernel and cm7.

I just got a shipment yesterday from Sparkfun with a breadboard, resistor pack, micro-usb breakout board, and jumper wires so I can get 'factory mode' usb uart on my phone. After I can break into the sbl prompt and enable the usb uart after the bootloader, I should be able to see where the cm7 bootloop is coming from... as well as start work on u-boot.

Last night I was able to connect the bus pirate (v3.5) to the phone in 'factory mode on' (619k ohm), but I was unable to break into the sbl prompt. I spoke with AdamOutler and he said that he was able to break into the sbl prompt with this mode.

I think it has something to do with the uart mode settings on the bus pirate.

I'm hoping to get this working today. :D

Baby steps to debugging...

Baby steps to figure out cm7 bootloop...

Baby steps to update new recovery (fsr/ext4) and hopefully push changes upstream to get working... updated rom manager images...

Baby steps to mtd/yaffs2 and moving away from proprietary Samsung kernel drivers...

Baby steps to pushing changes for cm7 and kernel upstream so we can get official cm7 builds....

Baby steps to porting to ICS... the plan basically stops here wrt CM and Kernel work, as I have no clue what problems we will face porting from cm7 to cm9.

Lots of steps, little time for me to dedicate to tasks... lots of writing 'updates' for you guys to read so you don't throw a riot in our forums because you have problems being content with "I'm still working on it... don't freak out".

--

P.S. I've updated the op's "Plans" link to point to this post. As I promised.
[Samsung Galaxy S (4G Model)] leo321:
Thanks bhundven for keeping us updated, and sticking with the device when others just gave up. You're brilliant!
[Samsung Galaxy S (4G Model)] bhundven:
Well, even if I get a new phone (hopefully the US version of the Galaxy Note comes soon...), I won't get rid of or stop using my sgs4g! Promise!

To prove it, I still have my G1 and still use it! (and I will have to use it here soon when I get the usb uart stuff working on sgs4g... as I need a working phone!)
[Samsung Galaxy S (4G Model)] leo321:
Funny you should say that... I still had my htc hd2 until recently (notorious screen digitizer connector issue killed her) i used about twice a week... Even though a winmo phone it ran android like a boss! cm7 is what i miss about it, they even have an ics port!
[Samsung Galaxy S (4G Model)] bhundven:
If we had more sgs4g developers with deeper experience with kernel and android development, we'd have cm7 and cm9 too.

Unfortunately, everyone that PM's me wanting to help do not have enough experience or haven't answered my questions. It really would be nice to get some help from someone more experienced.

But, back to on-topic... here we are. This is where I'm at.

I don't see any status updates until I fix the cm7 bootloop. After that, it's on!
[Samsung Galaxy S (4G Model)] Caligula36:
Are we no longer required to have a seperate sd card partition made for the voodoo ext4 conversion? In CWM, it says voodoo lagfix is disabled, though when i check the voodoo control app or check it in the terminal, it does say im in ext4. Also linda never makes a speech.
[Samsung Galaxy S (4G Model)] bhundven:
I believe you still need that. I suggest backup your sdcard, repartition in cwm. Make sure the ext2 partition is >=2048M

After repartitioning your sdcard, it should be blank, which means voodoo lagfix will ultimately be disabled. Let linda convert to rfs...

Reboot to recovery after loading android all the way in rfs (lagfix disabled) and re-enable voodoo lagfix and /system lagfix.

Should now be golden.
[Samsung Galaxy S (4G Model)] Fluidification:
never repartitioned, ext4 works great via voodoo.
[Samsung Galaxy S (4G Model)] Caligula36:
See i keep getting instructions that contradict each other. im working with a freshly formatted sd card, everything seems to be working except for the lack of linda talking and CWM saying its disabled, even while the terminal command says it is in ext4. If theres no need for the partition, then why waste the 1 gb of space.
[Samsung Galaxy S (4G Model)] FBis251:
I think I know where the repartition thing is coming from.

I never really messed with Android before Froyo but until Froyo, apps2sd was not enabled or officially supported by android, you had to use a 3rd party app and create a separate partition on your sd card. People still receommend you do this even though there's no need for a separate partition as any version Froyo and later will do this automatically even if the whole SD card is in 1 partition and it's formatted as FAT32.

You're already on fat32 and the command told you you're already on ext4, so you're good. Delete the extra (useless) partition and get your space back.

You're not gonna hear Linda give her speech unless you turn lagfix on and off. You can even try this, try opening the Voodoo control app from the market and turn lagfix off on all partitions, reboot. You'll hear Linda saying she's disabling lagfix, it might take 5 or more mins depending on your sd card's speed. After this you can run the command again in the terminal and verify that lagfix is off in the app, and you can turn it back on, reboot, hear Linda, check terminal/voodoo and it'll say ext4 is enabled.

You don't need to disable/reenable but if you want to go ahead but I think it'll just be a waste of time and read/write cycles for you sd card. You're definitely already on ext4.
[Samsung Galaxy S (4G Model)] Fluidification:
Apps were never able to go to SD before froyo. Android currently reads SD as having capabilities to create a .android_secure folder and share data with it. Before. It was just as an external media unless the system would read it as part of the system. For that, there would need to be an ext partition. The partition for voodoo thing is only to make the recovery verify that there is an sd card though. It has nothing to do with APPS2SD. Once the recovery would verify that the card is there, it wouldn't give the "NOT ENOUGH SPACE ON SD CARD" error.
[Samsung Galaxy S (4G Model)] bhundven:
Ok, finally after getting some more help from AdamOutler, I was able to get in the SBL prompt and set SWITCH_SEL so I can see all of the bootlogs... PROGRESS!

http://pastebin.com/14cBZxP1 -- breaking into sbl prompt

http://pastebin.com/r0s9PPi6 -- boot with SWITCH_SEL set to 6543
[Samsung Galaxy S (4G Model)] FBis251:
Awesome. Too bad it took so much work to just get a verbose bootup. I love verbose. :)
[Samsung Galaxy S (4G Model)] bhundven:
Meh. I'm gonna look to see if the sbl environment is the same format as the u-boot environment. If so, we can use fw_env tools from u-boot to update the sbl environment, since the sbl is basically a hacked version of u-boot.

BTW... For those of you bummed out because I don't accept donations and really want to help out the cause.... Donate to either RaverX3X or AdamOutler!

If it weren't for these two guys, I wouldn't be where I'm at this very second, and cm7 and other cool future stuff would not be possible!
[Samsung Galaxy S (4G Model)] Caligula36:
Excellent, thank you FB and Airfluip for the detailed explination. That really helps to clear up the setup process for ext4. Also to bhundven for your acomplisments with the CM7 port. A lot of times when people are asking whats going on, we arent looking for eta's, just for a 'whats up'.
[Samsung Galaxy S (4G Model)] tehgyb:
You guys are pure beast mode
[Samsung Galaxy S (4G Model)] FBis251:
Seriously.
[Samsung Galaxy S (4G Model)] Fluidification:
Wait, BH you booted into CM7?
[Samsung Galaxy S (4G Model)] bhundven:
No, those logs are from valhalla-black with v0.1.1-rc1+.

My phone ran out of batteries last night while I was playing around with the sbl, so I will start on cm7 stuff after work today.
[Samsung Galaxy S (4G Model)] bigtom624:
Cool. Thanks man
[Samsung Galaxy S (4G Model)] bhundven:
Status for today... sick. Taking some time off and in bed to sleep this off. Also... you'll notice I'm back on my G1 ;)

Bricked the sgs4g after flashing cm7 self-kang. Yeay for UBM and resurector! :D One-Clicked back to sms-kj6. With the G1, I don't have to worry about missing txt or phone calls while this cm7 stuff is going on.

Hopefully when I wake up tonight I'll have some energy to hack some more.

Have a relaxing weekend!
[Samsung Galaxy S (4G Model)] bigtom624:
Thanks for the update. Hope you feel better. Get some rest.
[Samsung Galaxy S (4G Model)] Juls317:
God, i don't care if your sick, I WANT CM7! in fact, go ahead and fix MIUI too!

just kidding. glad to hear that you are making progress and i look forward to the next release of the kernel. get better!
[Samsung Galaxy S (4G Model)] Somairotevoli:
Be careful with the kissing, might be contagious;)
[Samsung Galaxy S (4G Model)] Juls317:
haha good catch. fixed. still getting used to mmy kindle's keyboard
[Samsung Galaxy S (4G Model)] cmhjr:
Hope you feel better and get your rest.

I still use my G1 with the extended battery when I mess up my SGS4G. It's like the little engine that could.
[Samsung Galaxy S (4G Model)] ericmpanda:
Sleep man relax feel better
[Samsung Galaxy S (4G Model)] bhundven:
Yea, mine has the extended battery too, as well as a sticky 'a' key...
[Samsung Galaxy S (4G Model)] AxleFolie:
Im always having error flashing this im on valhala final + cwm voodooLagfix v3.0.2.8x.. Do i need to uninstall first my old version of voodoo?
[Samsung Galaxy S (4G Model)] finch8423:
That would require a different, non-voodoo kernel.

Val final comes with an older beta version of this kernel. That being said, you shouldn't encounter any problems installing. I had the same setup, and upgraded to CWM 5. What does the error say?
[Samsung Galaxy S (4G Model)] AxleFolie:
When flashing it after installing my screen flicker with big letters then it will reboot and will not load.. stop on bootloading..
[Samsung Galaxy S (4G Model)] Fluidification:
use heimdall or ODIN
[Samsung Galaxy S (4G Model)] leo321:
Did that once thought i broke it... Soft bricks are annoying.
[Samsung Galaxy S (4G Model)] bhundven:
The voodoo lagfix is in the kernel. So uninstalling an old version just means flashing a new version.

I have CWM flashable versions of my kernel in the OP. Download it, put it on your sdcard, reboot to recovery. Flash the new kernel. maybe fix permissions and reboot to android. Done. No need for odin or heimdall unless you've already screwed up.
[Samsung Galaxy S (4G Model)] cannondale0815:
bhundven, I have been using your Beta 3 kernel on top of Valhalla Final and Racing's ICS theme for a while. Racing now released an update to his theme, and flashing this update with CWM 5.x, while seemingly successful, actually didn't work. I had to downgrade to your Beta 2d kernel with CWM 3.x. Just wanted to point this out to you. Here is the other thread:

http://xdaforums.com/showthread.php?p=21343547&posted=1#post21343547

Thanks!

-J
[Samsung Galaxy S (4G Model)] bhundven:
You guys can call me bryan. ;)

Yup, Something changed in CWM5. I'm not sure if it is a problem with CWM5 or just something changed that requires a change to the updater-script in the cwm zip package. Som mentioned this too and posted a zip for me to test.

I still haven't gotten around to it, but it will either be fixed in the next version or I will post something about the updater-script.

You can access adb in recovery, it would be nice to get a logcat of installing the package. If you enable voodoo -> voodoo debug, that will give you adb.
[Samsung Galaxy S (4G Model)] hechoen:
This whole time I've been calling you BH.

Thanks Bryan for the work your doing
[Samsung Galaxy S (4G Model)] Caligula36:
I had an interesting issue a few days ago on my phone, was going to add an event to my calender, when the entire phone froze up. I was waiting for a FC window to pop up but it never came, and all the buttons, including the power button were disabled.

Im not sure if its a kernel, a ROM, or a launcher issue, but i have the logcat if you want to see it. Otherwise for the occasional annoying hang up, its been pretty reliable. On Valhalla final with your newest kernel, with the blue theme, and lightning zap (sorry, i know you dont like that added for debug purposes)
[Samsung Galaxy S (4G Model)] mysticfrog:
installed this beta and i believe it actually sped my phone up a bit kinda strange though.. but i do love this... thankx b
[Samsung Galaxy S (4G Model)] bhundven:
It's more likely to be your ROM. The kernel wont make any app fc, unless they are doing something evil (like an ioctl or some kind of direct native driver call... And that would just make your phone reboot.)

Either way, with an issue like this, I would highly suggest starting logcat, reproduce the issue, send the logcat to the ROM dev. If he finds a problem with the kernel, he will contact me... As each ROM runs a different version of the kernel... And I dont test my kernel with every ROM.
[Samsung Galaxy S (4G Model)] bhundven:
Op updated. I decided to release Beta 3.1 v0.1.1-rc1+ so that I don't loose this file.

Another version will be released soon with more fixes. Read post #2 for changes.

Not a lot was fixed in this version. I know su and superuser are out of date.

Again, another kernel version will release soon.
[Samsung Galaxy S (4G Model)] bigtom624:
Hey Bryan, first of all thanks for the update. When I hit the link it looks like it is going to the KJ6 one click file, and it says the Kernel file could not be found.
[Samsung Galaxy S (4G Model)] zargeus:
The file is pointing to the correct location, just github must be messed up. There are 8 files totaling 52.4 mb, but only 7 files there totaling 45.6 mb.

So we will have to probably wait for Bryan to try and reupload?
[Samsung Galaxy S (4G Model)] Shermer321:
Appreciate the work, nice to see a 2012 update.

Any possibility of adding bln to the next release?
[Samsung Galaxy S (4G Model)] bhundven:
Nope.

10char
[Samsung Galaxy S (4G Model)] bhundven:
Yea, sourceforge is retarded. I don't know why the newest file link never updates. If anyone knows how to fix this on sourceforge, I'd be very happy!

Yea, I had to re-upload. If you don't click the "done" button after uploading the file, it doesn't finish uploading. How dumb.

Link fixed. Enjoy.
[Samsung Galaxy S (4G Model)] Juls317:
Just wondering, why no bln in the next release? Just focusing on bugs and CM7 for now?
[Samsung Galaxy S (4G Model)] bhundven:
More or less.

Right now I'm in 'bonsai mode' as I write this, I'm trimming down the drivers/ directory in the kernel to remove any code that is not specific to the SGS4G. This helps to make the difference between upstream aosp and our kernel less. Hence, easier to port.

Also, while I was 'repo sync'ing cm7 onto my new laptop, I noticed they finally posted the samsung aosp tree :)

http://android.googlesource.com/kernel/samsung

So, Now I am targeting that tree for the port. This tree contains both 2.6.35 and ics 3.0.1.

When I 'trim the bonsai' down, I'm going to apply my difference to 2.6.35 and then merge those changes to 3.0.1.

THEN, voodoo sound, bln, cm7, cm9, blah blah blah, the same thing I've been saying sence I started this thread :-P :D

At the same time, I'm looking into mtd/yaffs2 to replace the fsr/rfs and fsr/ext4 filesystem combinations. This will help us to 'trim the bonsai' further by removing more samsung specific stuff that we don't need and have a kernel with good performance and UV/OC (yes, we could have that now, but I'm shooting for stability for now).

Also, my cm7 tree seems to be coming along, but still needs much work.

As I said before, my current github tree for cm7 parts is in a non-working state. If it even builds, it won't work. I have a local mirror and staging branches for both fsr/ext4 and mtd/yaffs2.

Things are progressing, but not as fast as you would like ;) I know.
[Samsung Galaxy S (4G Model)] adobrakic:
I love you. Just throwing that out there.

Sent from my SGS 4G.
[Samsung Galaxy S (4G Model)] digitallure:
Had a small issue after flashing but fixed permissions and all seems to be fine. Wifi was a bit whacky and system was sluggish.
[Samsung Galaxy S (4G Model)] Core618:
DL the 1.1, may apply it this morning... if you're already working on a larger release I may just wait...

Gods, I'm too lazy to even flash a kernel this morning... must need more caffeine...

Thanks for the update B, glad to see things moving along..
[Samsung Galaxy S (4G Model)] bhundven:
...I love you too, man. lol
[Samsung Galaxy S (4G Model)] itzik2sh:
Hi Bhundven/Brian

I'm working on a translated Valhalla Final ROM.

I used APKTOOL to decompile all system apps and framework, add language values strings and recompiled using APKTOOL.

Strange thing, on kernel version 2d none of the apps was recognized by the system, it was like they're not there.

I flashed KJ1 kernel and they all appeared & work flawlessly.

Do you have any suggestions?

Sent from me
[Samsung Galaxy S (4G Model)] bhundven:
No clue. I got the recovery from drhonk's kj1. Maybe something in your updater-script is not installing apps right. Checkout one of raver's updater-scripts, they seem to always work.
[Samsung Galaxy S (4G Model)] bhundven:
picture of progress

https://sourceforge.net/projects/teamnerd/files/2012-01-15 21.38.05.jpg

Building stuff, bricking, debugging, hacking - start over from the beginning of the sentence.
[Samsung Galaxy S (4G Model)] QUIETLYloud:
Is this the same version that is included in Valhalla black edition?