yashsingh1/xdaforums huggingface dataset:
[Samsung Infuse 4G] bedwa:
State of the Kernel

First off, I do want everyone to know that I have in NO way stopped plans for development. But I do need to let everyone know this.

For some odd reason, anytime I compile my kernel post compilation of my Infusion 1.5 Kernel, I am not able to compile a working kernel. It builds, it flashes, it just doesn't boot. It's too small or WAY TOO LARGE.

Ex: My zImages of my 1.0 and 1.5 are approx 7.x MB. The kernels I've built so far have been 11.x, 5.9 and 6.8. and no closer to the 7.x that I was building....

With that being said, tweaking is on a halt till I can successfully build again, but I AM working diligently on building.....

Thank you to everyone for your continued support and encouragement.

-B
[Samsung Infuse 4G] Ltilt2:


Are you pulling our legs and you have a kernel ready to upload?
[Samsung Infuse 4G] bignate78:
I don't think he's kidding. Don't bug

Big dog Infuse I997 running Infused 1.5, Defused 1.4
[Samsung Infuse 4G] clown_luv:
Download dolphin browser in market and use that dl will solve your problem
[Samsung Infuse 4G] MikeyMike01:
Or get Download All Files.

Sent from my Infuse 4G
[Samsung Infuse 4G] Entropy512:
Thank you for the update - If you haven't fixed it by the end of the holiday weekend, I'll give building your tree a try. It is about time I tried to get a kernel build environment up and running. (Who knows, the toolchain I compiled for Cortex-M3 development earlier this year might work fine on an A8.)

Now, pardon my git-newbness:

I see that tree 5ab1cfb852ed7a3882fb /commit fb422b0d794f9d09ce16 (your latest) is Infusion 1.5 - Which one is 1.0 out of curiosity? Also, where's the line of code that broke UV? (I may have an hour or two here and there to familiarize myself with the tree that I can't actually work on building.)

Oh, I think I figured out what might be needed to port the battery charge rate tweaks from http://xdaforums.com/showthread.php?t=996631 to our kernel. Gonna be at least a week before I can poke at that though, and if I'm doing that work I will NOT be putting the topoff tweaks in - I want my battery to charge fast but I don't want to be replacing batteries extra often because they get overcharged.
[Samsung Infuse 4G] crazynfo:
O/C Daemon Automagical Overclocking

O/C Daemon

Just wanted to point out this new O/C Daemon I found earlier this week when I was flashing a new ROM to my girlfriends HTC Inspire. I was wondering if we will be able to see something like this on the Infuse one day, or if the O/C Daemon is incompatible with the Samsung framework.

For those of you who don't click the link above, it is basically like you have SetCPU or Voltage Control baked right into the kernel, so there is no extra process. It controls the governor & CPU speed dynamically at the kernel level. It looked like it could provide some additional battery life, and perhaps improve lock screen performance for those of us with low minimum clock speeds on sleep.

Not making a request, just wanted to bring it up in case bedwa wasn't familiar with it yet, I don't know if it is a common thing to see in kernels, or if it is a new thing and somewhat rare.
[Samsung Infuse 4G] bedwa:
Updated State of the Kernel Address. v.6/30

After repulling the initramfs from gtg465x and kanging and modding the build and clean scripts from Razor950 (and LinuxBozo), I now am able to rebuild my 1.5 Kernel. SO, with that said, I'm back to tinkering.

And FYI, I am going to look into how the Daemon Controls are implemented to see if it is possible to port. ;)
[Samsung Infuse 4G] Entropy512:
That isn't baked into the kernel. It's a C app that runs from the commandline shell, and uses the same exact sysfs kernel interface that SetCPU and Voltage Control use.

e.g. all that is is an alternative to SetCPU and Voltage Control (or, at least from the description, possibly only voltage control at the moment) that runs natively outside of the Dalvik JVM.

So it should work on our devices, but from reading the description, I see:

1) No voltage control support, but this may be doable with some basic shell scripting since voltage should be "set once and forget" once the correct values are determined with the sysfs interfaces

2) It only supports two "profiles" - screen on and screen off. It doesn't support entering other profiles like SetCPU does depending on other environmental factors (charging vs. not, battery charge level, temperature, etc.)
[Samsung Infuse 4G] crazynfo:
The one thing I never liked about SetCPU was that the profiles cause the process to run 24/7 in order to support the requisite polling. I do understand that there is only a sleep and a wake profile with the Daemon. I was not personally using the temperature or charging profiles, let alone battery level, so I suppose that is a good point.

I commented on smartass governor earlier, because my main concern is as little CPU use as possible while sleeping. You brought up some good points. I was mainly trying to prevent the constant polling from checking sensors/battery level/etc with SetCPU, and I was reading about this while flashing my GF's ROM and just thought it was good for conversation, and perhaps to add a new ideal to the mix. I had completely missed the support for UV/OV in the daemon, that is also a glaring omission.
[Samsung Infuse 4G] tight686:
I can't wait to donate towards this kernel. Absolutely loving it more and more.

(Fourth check on this thread today)
[Samsung Infuse 4G] bedwa:
When you do, let me know so that I can add your name to the Insanity Crew. I like giving credit and thanks where it is due.
[Samsung Infuse 4G] tight686:
Nice mantra. Perhaps the Insanity crew could one day become the beta testing crew?
[Samsung Infuse 4G] Entropy512:
I made an attempt to compile your sources. So far:

"make clean" fails with some errors relating to a missing fsr directory.

An attempt to build bombs at drivers/media/video/samsung/tv20/s5p_stda_grp.c

Error logs for both attached

Edit: I attempted to use a newer version of the CodeSourcery toolchain, could this be the cause of the problem? I'm going to attempt to downgrade, although I think my build directory may be crudded up now since 'make clean' doesn't work.

Edit 2: Never mind! Do NOT use the "latest and greatest" CodeSourcery release, it won't work! The 2009q3-68 release recommended in your README did build a zImage, although the one I have is 12M... So I'm guessing I probably shouldn't even attempt to use that.
[Samsung Infuse 4G] bedwa:
have to use Q3, 2009 version to build, new git will have a build and clean script.

and till I do that and get the updates in, lookie here... ;)
[Samsung Infuse 4G] ookba:
SWEET!!!! Upload pls!! :)
[Samsung Infuse 4G] Entropy512:
I'll settle for a git push. :P

Edit: bedwa, is there an IRC channel the Infuse devs hang out on?

Edit 2: I missed gtg465x's initramfs instructions (nuke all the git stuff) - after nuking all git-related items, I built a 7.4M kernel. :)

Edit 3: Anyone know why dmesg returns NOTHING on the Infuse?
[Samsung Infuse 4G] bedwa:
Yep, the initramfs is where I think I was making my goof. With that I am removing my initramfs from my git and using gtg's and will change readme accordingly to add the one line to the init.rc for init.d support. (Thank xcaliburinhand for that one. ;) )

Edit: Dmesg is probably due to debugging flags turned off in default.prop (initramfs) and the IRC is #Infuse4g at freenode. Still coding and going to git either tonight or tomorrow.. May have another surprise in store. ;)
[Samsung Infuse 4G] Entropy512:
Thanks for the info, I'll see if I can reenable dmesg before the weekend's festivities start.

I'm in #infuse4g now but AFK - about to head to bed.

Oh yeah, I figured out how to boost charge current a little bit. (Ported one of the charging tweaks from an experimental Epic 4G kernel)

It's at https://github.com/Entropy512/Infusion-Kernel/commit/b5bab7b70a8c6ca0c7eee2aff46139480db0b213 but I would keep it out of your kernel until I've got some time to do some ammeter/voltmeter testing.
[Samsung Infuse 4G] bedwa:
noted and bookmarking....

Just give a pull when it's where you feel it needs to be. ;)
[Samsung Infuse 4G] 2sl0w:
Keep up the good work bedwa!!
[Samsung Infuse 4G] bedwa:
Heads up, UV is working, but there is now a sleeplock on all governors other than conservative. Looking into a way to fix, then I will release.
[Samsung Infuse 4G] Ltilt2:
Thank you Mr. Bedwa. we appreciate your hard work.
[Samsung Infuse 4G] MikeyMike01:
That's fine I use conservative anyway. :D

Nice to see some progress though.

Sent from my Infuse 4G
[Samsung Infuse 4G] JordanED69:
Great job. Keep up good work
[Samsung Infuse 4G] Kif420:
Can I just flash cwm zip? Coming from bone stock infuse. Just rooted with cwm.

Or do I need to odin the tar too
[Samsung Infuse 4G] bradbusa:
me too :) cant wait
[Samsung Infuse 4G] Entropy512:
Either one works, you can odin or cwm, no need for both.

Odin is probably what i'll need if I ever break it now that I'm starting to do my own dev. ;)
[Samsung Infuse 4G] Kif420:
Awesome. Thanks!
[Samsung Infuse 4G] tight686:
+1
[Samsung Infuse 4G] bedwa:
Testing now, will upload tomorrow if nothing goes awry.....
[Samsung Infuse 4G] bradbusa:
Woohoo!
[Samsung Infuse 4G] Entropy512:
bedwa has source for 1.5.1 up now. He's testing it, as am I (I compiled from his sources).

One thing I will tell you, once you get 1.5.1, BE CAREFUL with UV settings.

My first attempt at UV settings (-50 near the top end, -100 near the bottom end) resulted in sleeps of death. (Unable to bring phone back from wake.)

I'm now at -75 at 1200 and 1000, with -25 from 800 on down, and I am not getting SoDs. Trying -50 at the bottom now...

Edit: The following is working for me so far:

1200: -100

1000: -75

800,400,200,100: -50
[Samsung Infuse 4G] Ltilt2:
What is GHZ? With this new update? Or was uv the only update in this new update...thank you bedwa for all the work you do
[Samsung Infuse 4G] Entropy512:
So far from looking at his commits - fixing UV and lots of architectural/coding cleanups.
[Samsung Infuse 4G] 2sl0w:
Woot.!. Cant wait to try this in the morning.
[Samsung Infuse 4G] Ltilt2:


Nice!
[Samsung Infuse 4G] Entropy512:
So far so good, won't know for sure until the end of this camping trip I'm about to leave on.

Started with battery at 95 around 1-2 AM last night, was at 85 at 9 AM. Of course, that was "screen off sitting on the counter" the whole night.
[Samsung Infuse 4G] Ltilt2:
So, you guys are going to test the kernel before releasing it to the public?

and, again thank you.

kept waking up through the night to see if there was a release.:D
[Samsung Infuse 4G] bedwa:
This time yes. If you can build it, feel free to test it. Otherwise I'll release later today.
[Samsung Infuse 4G] JordanED69:
Thankyou :)
[Samsung Infuse 4G] Ltilt2:
thank you so much sir, I will await for your release.
[Samsung Infuse 4G] indymx:
I was going to give it a whirl, however....

CC mm/truncate.o

mm/truncate.c: In function 'truncate_inode_pages_range':

mm/truncate.c:290:1: internal compiler error: Segmentation fault

Please submit a full bug report,

with preprocessed source if appropriate.

See <https://support.codesourcery.com/GNUToolchain/> for instructions.

make[1]: *** [mm/truncate.o] Error 1

make: *** [mm] Error 2
[Samsung Infuse 4G] bedwa:
1.5.1 up!

Fixed UV is on! Now with added Speedmod as a bonus. ;)

Next is trying to get a working 1.7 GHz, it's been kernel panicking anytime I try it currently. Will keep working on it.

And can someone try Tun again to see if it works, that's not a feature that I frequently use.....
[Samsung Infuse 4G] ookba:
Just installed 1.5.1! Testing! So far so good! Thanks!

EDIT1: no voltage tab in setcpu!? Wonder why...

EDIT2: Running Quadrant, on CPU, gets to Video decoding - H.264 and freezes.

Is tun compiled in or is the tun.ko module needed?
[Samsung Infuse 4G] tight686:
So far so good!

Edit: Yeah quadrant hangs for me as well. Not a deal breaker by any means.
[Samsung Infuse 4G] bedwa:
on Edit #2: Try Xan's Voltage App. ;) (Oh and give it a few min after boot, may take a moment.)
[Samsung Infuse 4G] ookba:
Thanks. Seems like H.264 is not working on 1.5.1. I cannot play any .MP4 videos. Works fine on Community Voodoo and Infusion 1.5. Can you check yours?
[Samsung Infuse 4G] JordanED69:
Ur gettin frozen at h264 too? I get that on g2g's kernel too.. Wtf
[Samsung Infuse 4G] bradbusa:
awesome! so excited :) 2 questions..

1. what is speedmod?

2. what is TUN?

and where can i find out more info about these?
[Samsung Infuse 4G] JordanED69:
I can play mp4's fine. But benchmark wont get past that part loll
[Samsung Infuse 4G] ookba:
TUN is for establishing VPN tunnels to remote servers and hosts.
[Samsung Infuse 4G] JordanED69:
Should.i.flash.kernel or wait for fixes?
[Samsung Infuse 4G] ookba:
Flash it and test! How else can the dev know what to fix. :)

You can always flash back to any kernel you want later.
[Samsung Infuse 4G] bryanb86:
Same here.
[Samsung Infuse 4G] JordanED69:
how do u flash the odin one? i flashed the cwm version b4. now i cant get either :mad::mad::mad:

Edit: i got it to work.
[Samsung Infuse 4G] bedwa:
I'm going to meet in the middle on the speedmod edits and post a 1.5.2.
[Samsung Infuse 4G] JordanED69:
how long should this take with odin? lol its been 5 mins

Edit: damn it. i have to reflash my whole phone. idk what happened
[Samsung Infuse 4G] bedwa:
should be about 10 seconds....

If need be remove the tar, download heimdall and and do it again....
[Samsung Infuse 4G] JordanED69:
whole crap. 10 seconds. damn. something messed up
[Samsung Infuse 4G] bradbusa:
what is speedmod?!

and why are you removing it?
[Samsung Infuse 4G] bedwa:
Not completely removing. It's lowering some of the reserved system mem to let userspace and applications use it. I have to give alittle back to the video buffers to make sure that proper video processing is afoot (or at least can be tested... :P )

Compiling now BTW.
[Samsung Infuse 4G] ookba:
I see. Kinda like pagepool in WM ROMS. I did notice MUCH more RAM available on boot. Yea, but then the H.264 issue came up I take it? Also, any idea why the voltage tab isn't showing in setcpu? It did on 1.5. Also, I got the same issue flashing in ODIN, just freezes up and then won't boot. The fix was to flash another kernel you know works with ODIN. Looking forward to testing 1.5.2. :)
[Samsung Infuse 4G] JordanED69:
same here. the odin kernel messed up
[Samsung Infuse 4G] bedwa:
Hmm... must have been cause I made the Tar on my phone. Uploading the new ones now....
[Samsung Infuse 4G] samsungcaptivates:
just flashed 1.5.2 with sgs kernal utility bumped up to 1.6 from 1.4 was running infusion 1.0 loved it i am using set cpu my voltage tab is there and all is well so far i will be playing with setting soon also 2135 benchmark with quadrant standard for those interested in that sort of stuff\
[Samsung Infuse 4G] samsungcaptivates:
oh fyi thats over stock deodexed rom
[Samsung Infuse 4G] samsungcaptivates:
here is kernal flasher that i used
[Samsung Infuse 4G] JordanED69:
what voltage settings are you using?
[Samsung Infuse 4G] ookba:
1.5.2 is better! I get SOD (Sleep of death) using OnDemand governer. More testing. MP4's play! Will advise.
[Samsung Infuse 4G] JordanED69:
wait. isnt sleep of death bad? lol
[Samsung Infuse 4G] bedwa:
Thanks! Upon looking forward, testing 1.7 now, and looks like I had to take out the 900 MHz to get it in, for 1.8, I'm looking to eliminate 1100 MHz. I'm pushing here guys. ;)

Also looking at pushing in BFQ scheduler on the next iteration and possibly a special surprise of a boot logo (if my drawing resource comes in for me, he's the one who swapped the blue out in the red Nexus S LWP in my sig).
[Samsung Infuse 4G] JordanED69:
keep up the great work. u deserve a million dollars :P
[Samsung Infuse 4G] hydrogenman:
nice work Bedwa, I think I'll wait around for your newest update before flashing
[Samsung Infuse 4G] bedwa:
Go ahead and flash, this update's not close to completion, I just want to keep you guys updated... ;)
[Samsung Infuse 4G] hydrogenman:
with the problem's you were discussing, they just show up when benchmarking? or will it impact video playback?

didn't quite follow
[Samsung Infuse 4G] 13_:
You can try bumping the UV back up on the lowest clocks (example 100Mhz was -100 up to -75) while still using OnDemand... may solve SleepDeath. I have had a problem with 200Mhz doing that to me on another phone bumped it 25 and it never returned.
[Samsung Infuse 4G] samsungcaptivates:
I habeen using performance gpu sense 1.0 with set cpu profile when screen off set to lowest cpu freq have been getting good batt life and great performance with no undervolt but oc to max
[Samsung Infuse 4G] samsungcaptivates:
Ok so far with ondemand any uv with freq 100 or 200 causes sleep death i have no uv on these freq then stepping up -25 all the way up to 800 mhz then -50 through 1000 then -100 through 1.6 been stable with no issues running ondemand gpu
[Samsung Infuse 4G] byuboy87:
im running latest refuse. do i just flash this kernel over existing? no i need to wipe/back up anything? flash to stock?
[Samsung Infuse 4G] bignate78:
Hows the battery life with this kernal??

Also no over heating?
[Samsung Infuse 4G] 13_:
Yes. No. No.

I'd recommend using the Odin and flashing the .tar. Odin>PDA>select the .tar>DL mode>flash. Takes maybe 15 sec. Be sure RePartition is UNCHECKED.

or

You can also flash from CWM. Zip on root of SD card>reboot recovery>Install from zip>choose.zip> flash>reboot.

For control once you have it Installed, get Voltage Control from market.

To start, select the states you will use and set the UV's at -50 from there you can fine tune. See this Mini Guide for a quick tut here.

Have fun. ;)
[Samsung Infuse 4G] 13_:
If you are using it right, @ a stock clock of 1.2Ghz and UV properly it will be better than anything else you have tried.

If you UC to 1 Ghz and UV, I'm gonna imagine it will be ridiculous good.

If you OC to 1.4(or1.3) and UV properly, I'm gonna say it will be at least AS good as stock if not still better.

Of course heavy use is heavy use, nothing can defeat the addicted :D
[Samsung Infuse 4G] bignate78:
From the sounds of it this kernal needs an app to get anything out of it. I'd rather not mess with what's good on what others have made their kernals into instated of having to keep switching it up
[Samsung Infuse 4G] indymx:
My Quadrant scores are significantly better with the infused kernel.
[Samsung Infuse 4G] bradbusa:
Better than this kernel, with overclocking?

That's preposterous
[Samsung Infuse 4G] indymx:
1800's now 1600's withis kernel OC'd to 1300
[Samsung Infuse 4G] bradbusa:
WOW. can anyone else confirm similar results?

are you sure your voltage settings are correct?
[Samsung Infuse 4G] Artimus009:
Where is the ect folder? I am using root explorer and I don't see it...
[Samsung Infuse 4G] indymx:
Its /etc
[Samsung Infuse 4G] Artimus009:
In the op...it said ect. Cool thanks.
[Samsung Infuse 4G] Artimus009:
I've been getting mid 1900's consistently...I set it up exactly like in the op....great job bud, now lets see after a full days use on battery life.
[Samsung Infuse 4G] bryanb86:
im breaking the 2000's on this kern
[Samsung Infuse 4G] bedwa:
oops!

Fixed. My bad, sorry.
[Samsung Infuse 4G] bedwa:
Are you running the conservative governor? It wasn't going over 1 ghz for me when I had it on there. When I went to performance or ondemand, it jumped.
[Samsung Infuse 4G] nervad:
Sweet

Nice work on the kernel, running it @ 1.4ghz performance to see how it goes and then cycle through the rest
[Samsung Infuse 4G] clown_luv:
Do these settings atick on reboot made that folder but after reboot go in to voltage control and there back to stock settings
[Samsung Infuse 4G] ajs145:
I have the same problem. Settings don't hold in Voltage Control. I created the /etc/init.d folder, per the OP but still no luck. Have to reconfig each reboot.
[Samsung Infuse 4G] bedwa:
Must have etc/init.d folder and save settings in voltage app.
[Samsung Infuse 4G] JordanED69:
Post a screenshot of ur settings plz?
[Samsung Infuse 4G] mrzzheng:
thanks for the update. will we have bln in this kernel soon? really like it though there are some tiny bugs in defuse kernel 1.4.
[Samsung Infuse 4G] crazynfo:
Flashed 2 hours ago, no issues yet. -25 on the 100, -50 on 200-800, -75 on 800-1300, -100 on 1600. Running conservative governor. Will update with any issues tomorrow after work.

Thanks bedwa!
[Samsung Infuse 4G] nervad:
Keep up the good work bedwa your efforts are much appreciated. A few bench tests

Voltage Settings

Sent from my Infusion 4G
[Samsung Infuse 4G] ookba:
Seems like the issue I'm seeing is switching governers. I have my primary profile in setcpu set to 100-1600 with ondemand. I also have a profile set up for screen off using conservative. After about 3-5 screen offs, I get the SOD.
[Samsung Infuse 4G] bradbusa:
why dont you use all of the cpu frequencies available?
[Samsung Infuse 4G] nervad:
Its a personal thing, I don't think its a requirement to use all it just depends in what balance you are looking for. I like these to balance speed and battery

Plus less frequencies 4 cpu 2 cycle, btw just my opinion:-)

Sent from my Infusion 4G
[Samsung Infuse 4G] nervad:
Best one yet

Sent from my Infusion 4G
[Samsung Infuse 4G] bradbusa:
holy ****, are you still using the same settings that you posted before?!

also, i keep getting a frozen screen. it's happened to me twice now.. i have to pull the battery when this happens. does this mean too much voltage, or too little?
[Samsung Infuse 4G] nervad:
No just one setting, 1600 on performance to see what this baby can do, obviously not recommended for everyday use

Sent from my Infusion 4G
[Samsung Infuse 4G] bradbusa:
maybe i dont fully understand cpu clock speeds yet.. if the processor can pull that score with only one speed, why cant it perform just as well with other speeds enabled as well?

it only uses the lower speeds when there isnt as much of a demand, right? why would this hinder it's top end performance?
[Samsung Infuse 4G] 13_:
That depends on the governor sort of. OnDemand you can technically set just low and high as it will scale on demand from low to high with virtually no delay. If you were to enable all frequencies with on demand and use phone for some time then check frequency usage with cpu spy you will see that very few of the frequencies were used for any period of time.

With other governors the scaling is different. Conservative will slowly scale through all of the selected states. Others do similar but at different speeds. Sometimes a bad UV or unstable speed will give trouble either because it is not a stable clock or scales to fast from previous state or the UV is to big a step from state to state and you will get a crash or lockup. Each governor acts differently and can also have scaling speed changed either in kernel or with scripts.

OnDemand is preferable because it gives you excellent screen off/sleep conditions and the big bang of full cpu clock when commanded by your input almost immediately, actually flying past any suspect UV's or unstable lower clocks.

SO short answer, you can probably use all states below your highest and see no ill effects and also still see minimal time in states other than min or max clock.

For Conservative or others you may want to limit active states to 5-7 depending on Max clock. Example: 1.5Ghz I would set with these states, 100,200,400,800,1000,1200,1500. The idea is like making a stair case with equal "steps".... like 200Mhz jumps, UV's in similar steps. What you want to avoid is big jumps or bunched together states because, like pokemon its gotta touch'em all, and that takes time, slowing (lag) phone down. In cpu spy you will see most of the states used for a good amount of time.

Also Just because a specific clock speed crashes does not mean IT'S UV is bad ... it could be the state below or above which needs adjustment. ;)