yashsingh1/xdaforums huggingface dataset:
[Samsung Infuse 4G] Dani897:
use sgs kernel flasher, or heimdall(extract the .zip for this). this thread is intended for people that can solve some of their own problems. if you can't make your own cwm package or use other utilities then you need to learn more. it's kinda the spirit of the forums, being a "developers" forum there is some expectation that at minimum you don't have a give-me attitude. not saying that you do have that kind of attitude. it's just there is sometimes a large number of beligerant newbs that want bug free software delivered on a silver plater and refuse to learn about fairly basic things like zip packages, flashing meathods, and such expecting someone to take time out of their day to do it for them. so please look for sgs kernel flasher in the market or search for a premade .zip package for kernel flashing that will allow you to drop in zImage into a folder using any archive manager program like win rar.

if you need some assistance on making your own cwm package you can pm me but ill tell you right now that sgs kernel flasher is very easy and offers a way to backup the old kernel.
[Samsung Infuse 4G] qkster:
Hi, Entropy.

I know you're busy and have a lot on your plate. If you get a chance, can you take a look at this post?

http://xdaforums.com/showthread.php?t=1408433&page=7

This ties back to the issue you dealt with back in Oct/Nov 2011 on the SGS2.

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

http://xdaforums.com/showthread.php?t=1290020&page=19

I've been trying to chase down some battery drain issues. I suspect it may have something to do with rogues apps as you have suggested. It it may also be wifi driver related.

I would have wifi on at home. No unusual drain.

I would leave home with wifi to scan. No issue.

Arrived a different location. Connect to new location wifi. Drain starts.

This take place with background data off, gps off, sync off.

The drain continues even after I get back to home and log back to home wifi. Even after an hour of re-establishing with a "home" wifi, it continues.

I gathered the /proc/wakelocks and dsmeg and some screen shots. I'm not sure what to make of the data as it relates to kernel or firmware.

I also download Shark for Root and will try to run this during the drain.

I'm running your GB DD 4.4.2012 kernel with uclb3 deodex base. (CPU Master to limit CPU to 800) I recalled you mentioning about i9100 wifi blobs and BT-AMP bug. I don't know if this drain and the BT-AMP is the same? Has the i9100 wifi blobs been known to fix the drain cause?

I'm not familiar with specific hardware, linux or kernel technicals but I can follow directions at obtaining specific info or dumps that may make sense to you.

Any help is appreciated. Thanks.
[Samsung Infuse 4G] mataflakitas:
How can I fit the Cwm red with SGS Kernel Flasher, if I am in froyo aid..?

---------- Post added at 06:59 PM ---------- Previous post was at 06:49 PM ----------

help please im new in phone samsung galaxy infuse..
[Samsung Infuse 4G] Zen Arcade:
Search, read (repeat)... the answers are out there
[Samsung Infuse 4G] SIGMAxB:
I just used infuse toolkit with the trusty old stock gb included worked like a charm flashed from green GB slimmed down I love

Sent from my SAMSUNG-SGH-I997 using Xparent SkyBlue Tapatalk 2
[Samsung Infuse 4G] JordanElliott:
No. U can only use a certain kernel for cm7 or miui
[Samsung Infuse 4G] gabby131:
just flashed this kernel and i notice quite a difference.....in voltages though.

I can manually type the mV value instead of the undervolt (decrease) which is cool.

the conservative governor is tweaked.....default sample rate is 40000!!! Happy!

tested using SetCPU......
[Samsung Infuse 4G] Entropy512:
It is NOT compatible with CM7 or anything based off of CM7. CM7 requires a slightly different kernel architecture.
[Samsung Infuse 4G] Dani897:
would it be possible to add support for alternative file systems and remotely reformat the sd card to an alternate fs? im not sure if formatting the internal sd to something else is safe but we do have an external sd. one of the things that bugs me is the fat32 file size limit. i mean we have hdmi (atleast in froyo) and a gpu that can decode .h264 at decent quality and firmware that supports the .mkv wrapper. why must we be limited to a 4gb file? i want to watch movies without breaking them into small files and im sure i can use ext2 or ext4 but i like to get experimental sometimes.
[Samsung Infuse 4G] Entropy512:
I've had very bad experiences with filesystem backports in the past, so other than possibly enabling something else in defconfig, it's something I am not likely to do.

Mounting external SD as something other than fat32 might be doable for someone with some init script tweaks.
[Samsung Infuse 4G] Entropy512:
Posting new update in the original post in 1-2 minutes, fairly minor one:

1) Integrated codeworkx's cpuidle patch. Thanks to LinuxBozo for initially integrating this to our CM7 kernels. Should improve battery life a little in some situations, and seems to have improved it significantly in certain high-drain corner cases (Specifically, gmail tends to rape my battery when in very weak-signal conditions where data keeps dropping - it's much more gentle now)

https://github.com/Entropy512/linux_kernel_sgh-i997r/commit/e963add3293068ece8555bdd358415172d26adb8

2) Integrated the TCP buffer size changes from UCKI3/I4. I did some calculations and with a latency of 150 ms, I think the stock Rogers buffer sizes were good for 6-8 megabits/sec at best. However I could be off by a factor of two either way here, I'm really rusty on bandwidth-delay product calculations. However it could improve data speeds a bit for some people, at the expense of the TCP stack eating more memory. No one seems to have issues with running out of RAM so I figure this one's safe.

https://github.com/Entropy512/initramfs_sgh-i997r/commit/2a5fd7e86868f6b1da11f49471dc86d1ae5c0124
[Samsung Infuse 4G] steezinstangl:
i've been using the new updated kernel all day, and its working great! thank you!
[Samsung Infuse 4G] araemo:
Those numbers seem right to me. In any of the gb releases, I max out right around 6Mbps, no matter where I am.

Thanks for the links to github, I want to start trying to follow the changes to see if I can start learning something.
[Samsung Infuse 4G] JordanElliott:
entropy. just wanted to say. great job with the new kernel. data is sooo much faster now. ty so much. hope u feel better soon.
[Samsung Infuse 4G] Ryanscool:
Good job on the kernel! It seems as fast as it was overclocked. Anyway, when i open setcpu it says i am running at 1ghz. It does not go any higher. Is this ok if this happens? Oh yes! My 4g speeds are as good as they were in the beginning! Yes thank you!
[Samsung Infuse 4G] JordanElliott:
Theres no overclock. Only uc and uv
[Samsung Infuse 4G] Ryanscool:
Yea I know I was just saying it is as fast as it was when I had it overclocked with Infusion.
[Samsung Infuse 4G] JordanElliott:
Oooo!! sorry bro. Misunderstood u lol
[Samsung Infuse 4G] Entropy512:
Congratulations - you just found the first confirmed bug that I know of. I tried firing up StabilityTest and it's stuck at 1 GHz, and in fact it stays stuck there even if I enable Performance governor. This has probably been broken for a long time. I'll look into it this week.

See my question below.

So wait - if you do an A/B comparison of this release and the previous one, do you see a clear difference in data speeds as you switch back and forth?

I figured almost surely there's more than just the buffer sizes at play, since diddling with RILs did seem to change things - but maybe those changed latency enough to make a difference.
[Samsung Infuse 4G] JordanElliott:
Yea. Huge difference. Wifi is faster too
[Samsung Infuse 4G] JordanElliott:
And bug? What do mean. Like its stuck at 1000frequency?
[Samsung Infuse 4G] Ryanscool:
Yea go into setcpu and mess around with it. I have never seen it go to 1.2 ghz, and when it first loads up it sticks at 1ghz for a while. It still seems smoother then Infusion though. Even on conservative, just saying it changes frequencies like crazy in the app. I love the kernel though because data is quite a bit faster for me it went up from an average of 4.5 mb to 6.7 mb (in the middle of the day) just using this. I am also starting to see the battery drain just a tad bit faster then other kernels, probably from the constant changing of frequencies.
[Samsung Infuse 4G] JordanElliott:
No. The changing of frequenices is the tweaked conservative governor. Same as hellraiser. Look back on page 5
[Samsung Infuse 4G] JordanElliott:
1.2? there is no 1.2?
[Samsung Infuse 4G] Kadin:
Entropy, or anyone else that can clarify what I might be doing wrong, need some advice please.

I'm currently running Infused 2.2.3 with Infusion 1.1. I attempted earlier to change my kernel over to your current daily driver but hit a snag. First thing I did was set my voltage back to stock on all various speeds and set it just like it was originally and then I saved those settings and rebooted.

Upon flashing the kernel, when booting into the OS, it froze and locked during the 'X' animation. I tried a few reboots with no luck. Not sure what I did wrong but I flashed the kernel the same way I did with Infusion - via the red CWM boot menu.

I'm back to 2.2.3 with Infusion 1.1 and not sure how to attempt this again.

Thanks!
[Samsung Infuse 4G] Ryanscool:
Get Infusion 1.0 and install it. Then try going to this kernel. I was on 1.0 and I came to this no sweat, even though this may not be your problem. Oh and I did not do cwm, I did sgs kernel flasher. And yes Jordanelliot, It is set on the scale thing all the way up there, but I have never seen it go that high, even though when I go to the pie graph thing it has gotten up there quite a bit. It seems just a little bit odd. Anyway, I do not think the phone is really even getting to 1.2 ghz Entropy. When at performance, I still do see some homescreen lag.
[Samsung Infuse 4G] Entropy512:
Jordan - correct, it never hits 1.2 GHz. Doesn't even seem to want to hit it on performance governor, so it seems to be more than just an issue with conservative.

Even with the lower peak frequency, the conservative governor tweaks should improve performance by making it ramp up to 1 GHz faster (depending on your settings). In the Advanced tab you can tweak the up/down thresholds to make it more aggressive.
[Samsung Infuse 4G] Ryanscool:
Entropy, do you know what is making these bugs? Ha probably not or else you would fix them. I think the kernel is on the right track, which could maybe become the best non-overclocking kernel. The idea to increase data speed is so great!
[Samsung Infuse 4G] Entropy512:
Right now - no. Especially considering that since this isn't an OC kernel, I didn't really touch clock code that much.

If it weren't for the fact that performance governor has an issue too, I'd blame it on a side effect of netarchy's conservative governor tweaks.

The only other times I've committed anything that messed with clocks are the voltage control patches and netarchy's SoD fix patch.

I'm going to attempt to revert to the previous release tomorrow evening to test - does the 8/29 release do this too? (will test it myself Monday evening - but helpful to know beforehand.)

I will try the 8/13 release tomorrow night too. While I pull versions that are really old from the first post, I do keep them around on my hard drive.

As you can probably tell, this is clear evidence that I'm a battery whore not a clockspeed whore. :P
[Samsung Infuse 4G] bedwa:
Couldn't have guessed that by now Entropy. :P

That's interesting, I'll see if my conservative does that as well, even though I am a speed whore.... (and packing 3 batteries on me 90% of the time... :P )
[Samsung Infuse 4G] Ryanscool:
Ha I have not tried any previous releases, I just wanted to try something new lol. I am not going to stop using this kernel though, i need the data speeds.
[Samsung Infuse 4G] seano666:
You've mad my day with this, Entropy! It could make my phone run at 500mhz, with data speeds like this who cares!
[Samsung Infuse 4G] Kadin:
Well I'm still having no luck. I flashed over to Infusion 1.0 and then installed sgs kernel flasher then attempted to flash to the daily driver. Still getting the frozen X animation before full boot. Not sure what else to check other than waiting for another version to come around...

Appreciate your help though.

[EDIT] And as soon as I typed this up I had another idea. I was using Voltage Control (which I reverted back to the default settings) but I didn't delete the boot settings or profile even though I updated and saved both after reverting the settings. Upon deleting both of these, it now works.

I also noticed though that when I open up Voltage Control, there are some UV's such as 400Mhz 1050mV (-50), 200Mhz 950mV (-25) and 100Mhz 950mV (-50). Is this default settings with this kernel? 1200Mhz is the highest showing which I assume is normal even though other posts in here suggest otherwise.
[Samsung Infuse 4G] Ryanscool:
If i were you, i would go back to infusion for right now. There are some bugs with this kernel, which does not run the phone to its full potentiol, except data. I am even on infusion right now waiting for a fix.
[Samsung Infuse 4G] JordanElliott:
Ooo. I found the bug now!! Lol. 12000 doesn't appear lolololol. It does sometimes. Not always tho.
[Samsung Infuse 4G] P1 Wookie:
Is this something that only happens when using a voltage control app? I've had cpu spy running and mine is using 1200 but not 1000. And the frequencies it is using are pretty even.
[Samsung Infuse 4G] snoopdaclown:
I was looking through the whole thread and I saw UV settings and the higher freqs had higher UV values when I though the lower freqs had higher UV values. I have -100 for 1.2 and -175 for 100. I just want to check. And I have to delete the saved boot settings and profile in order to install this coming from infusion 1.1?

Sent from my Haxsung Infused 4G powered by Infusion
[Samsung Infuse 4G] Entropy512:
The issue might somehow be related to how some of your kernels don't use certain speeds at all - not sure yet.

That's odd that 950 mV at 200/100 is showing up as -25 - 950 is the stock voltage at 200/100. Maybe Infusion bumps default up a bit and this is somehow an artifact of coming from Infusion?

Unfortunately I use SetCPU instead of VC so I can't be sure.

That's another confirmed report that when coming from Infusion you have to be VERY careful due to the different VC settings. I think SetCPU may be somewhat safer in this regard as it usually nukes settings back to defaults when it sees changes in the kernel, and also Xan's VC puts some voltage stuff in init.d while SetCPU does nothing until the app has a chance to run - means you don't get the benefits until later but in some ways it's safer.

Mine reported 1200 as being active 0.66% of the time last night - everything else was in the 10% or more range (higher percentages as clock rate dropped)

Thanks, that's useful to know. It could be some sort of bug in netarchy's VC code. Will look into it more tonight.

Edit: It's hitting 1.2 GHz, but misreporting 1.2 GHz as 1.0 GHz. 1.0 GHz isn't a valid frequency in this kernel. Should have noticed that early, but I'm decobwebbing after not doing much for weeks. Sorry.

I just looked, it's a bug in how I ported netarchy's voltage control mechanisms to a non-overclock kernel. Netarchy's undervolt patches were designed for a different set of frequencies. See:

https://github.com/Entropy512/linux...363273#arch/arm/mach-s5pv210/cpu-freq_c110b.c

Look at line 656 post-patch:

return sprintf(buf, "1200mhz: %d mV\n1000mhz: %d mV\n800mhz: %d mV\n500mhz: %d mV\n200mhz: %d mV\n", exp_UV_mV[0]/1000, exp_UV_mV[1]/1000, exp_UV_mV[2]/1000, exp_UV_mV[3]/1000, exp_UV_mV[4]/1000);

You'll see that it has 5 frequency steps listed:

1200, 1000, 800, 500, 200

But the kernel actually has the following frequencies

1200,800,400,200,100

This disparity seems to result in things getting a little... wonky. However what I have seen is that if you disable voltage control in SetCPU, 1.2 GHz does appear as a used frequency in the statistics table. If you enable it, the table seems a bit... wacky.

This might be related to how CPU frequency statistics were broken in Bedwa's Froyo bus overclocking kernels - disparities between the voltage control interface and other parts of the kernel leading to confusion at varying layers in software.

So:

If you disable all forms of voltage control, you'll hit 1.2 GHz, however some reporting interfaces will still falsely indicate that you're running at 1.0 GHz. If you enable VC, you may still be hitting 1.2 GHz, but it's kind of unknown because the reporting gets even more hosed then.

I'll try to fix this tonight. Once I post it, until it gets more testing under the belt I'm going to have three releases up in the first post.
[Samsung Infuse 4G] ryanbmw51:
Please forgive me if I'm having a moron moment, but which of the 2 files should I dl?

I've tried both and when I open sgs kernel installer to load the kernel I can't seem to find the files in my phone. Not sure which folder they're in.

I'm on infused 2.2.3

Thanks
[Samsung Infuse 4G] Entropy512:
I don't support direct downloads of any flashable item to a phone - I've seen it cause too many problems.

As to which file - I always keep one old version around in case I accidentally introduce a regression (translation: in case I break something in a release). So use the one with the newest date.

A small update will be coming tonight FYI, at that point there will be three versions posted.
[Samsung Infuse 4G] ryanbmw51:
I see. So you think its a bad idea to DL direct to the phone? Oops. Been doing that almost exclusively. As a matter of fact, whenever possible. Seems to have worked out great until now. But I'll try again later when I get home from work.

BTW. Thanks for all you do. I'm looking forward to the better battery life out of this. Maybe I can get away without having to use my 3500 battery to get through a whole day but I'm prob being a little optimistic there. I use my infused infuse A LOT!

Thanks again.
[Samsung Infuse 4G] JordanElliott:
no. its fine if u download it right to your phone. if u download download all files from the market and download the zip from your browser it will work perfectly. u download. then open sgs kernel flasher and open it from your sdcard it is in download folder
[Samsung Infuse 4G] ryanbmw51:
I've done this many times in the recent past and what you're saying is right. Usually works just like that but for some reason the kernel does not show up in that download folder. Unless I'm not seeing it but I've looked over and over again. Any chance it saved to a different folder?
[Samsung Infuse 4G] ryanbmw51:
Got it. Thanks for your help. As it turns out I did not have download all files reinstalled after flashing to my current rom. Just installed that and now the file showing up in download folder.

You're the man thank you...
[Samsung Infuse 4G] JordanElliott:
hmmm... thats weird. do u use stock brower? or..

---------- Post added at 03:58 PM ---------- Previous post was at 03:58 PM ----------

o. nvm. responded to early. lol
[Samsung Infuse 4G] ryanbmw51:
OK so I flashed it but now under "about phone" it says kernel version is 2.6.35.7-I997RUXKG3-CL366622. Is this right? Because it looks a lot like the previous kernel i had flashed.
[Samsung Infuse 4G] Entropy512:
One thing I know is that downloading to device directly will often mangle file names, causing files with different names to get named the same. A bunch of people were complaining in pershoot's thread for his Tab 10.1 kernel about that, saying to label his files more clearly - but it was their browser mangling the file name (because his file names were VERY verbose!)

I think I've got a fix for the misreported speeds for the most part, except for one issue - for some reason SetCPU reports the current frequency in the main screen as 1000 MHz when the speed is 1200. The time in state stats in the Info tab are correct though. I'll try to fix this, but if I can't I'll post soon. It's an oddball one here...

OK, did a bit of testing, cpuinfo_cur_freq reporting is busted and reports 1000 MHz for 1200, so it's def. a kernel thing. Investigating now.
[Samsung Infuse 4G] JordanElliott:
yea. it is. thats the name of the kernel thingy lol

---------- Post added at 04:12 PM ---------- Previous post was at 04:11 PM ----------

sweet. hopefully it will work :)
[Samsung Infuse 4G] ryanbmw51:
OK. In the download folder it is named kernel-2011-08-29-4etc. But after flashing under about phone it has a different name for the kernel. As I spelled out before. Just want to confirm that the kernel was flashed and in place.

Thank ya!
[Samsung Infuse 4G] JordanElliott:
yea thats just the folder name that it names it when entropy backed up the kernel with sgs kernel flasher.
[Samsung Infuse 4G] Entropy512:
The kernel version string (2.6.35.7-blahblah) will almost never change. It can't change without breaking one of Samsung's proprietary modules, and if you break that module, the system won't boot at all.

The only reasonable way to identify a kernel is some of the more detailed info reported by SetCPU or Voltage Control. In SetCPU, if you go to the Info tab and choose Device, you can see the user/host that built the kernel, and when it was built.

For a kernel that comes from me, currently you'll either see adodd@quadmonkey or (rarely, if I was building on my laptop) adodd@andysg51

Build date will usually be at least a few days before the package date. (Package date being when I backed it up using SGS Kernel Flasher to post it) Tonight's update will be an exception - I'm about to back up this kernel and post it.
[Samsung Infuse 4G] JordanElliott:
sweeet!! changelog plzzz :D
[Samsung Infuse 4G] Entropy512:
OK, new kernel posted in first post.

This fixes the voltage control table so that 1.2 GHz will be hit when undervolting. (It may have even been hit when not undervolting.)

There is a small issue remaining - 1.2 GHz gets reported in /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq as 1.0 GHz - scaling_cur_freq reports correctly. cpuinfo_cur_freq is what SetCPU uses to report current frequency in big letters in the user interface

I'm 95% certain this is a display-only issue - the PLL settings all look correct for 1.2 GHz on first review, and it's not possible to run at 1.0 with my current code. Plus I'm 90% certain this is also broken on Rogers stock in the same way - but I could be wrong. I'll try hellraiser or gtg's kernel since neither do anything with clocks.

Also, for those who reported improvements in data speed with the 9/24 release - please do an A/B comparison between the 8/31 release and either 9/24 or 9/26 (doesn't matter, data speeds weren't touched between 9/24 and 9/26) and let me know the results. (e.g. flash back to 8/31 and test a few times, then flash up to 9/24 or 9/26 and test)

Edit: forgot to link the relevant git commit - https://github.com/Entropy512/linux_kernel_sgh-i997r/commit/34e16dd50da22fb735e975768fab1a4b2b01d5c1
[Samsung Infuse 4G] JordanElliott:
entropy i dont wanna be a bother. but did u fix the usb storage error in logcat?

did u pull this change from linux?

https://github.com/LinuxBozo/initramfs_sgh-i997r/commit/268a9920d0e5046f6a766473e8c651204c50c5be
[Samsung Infuse 4G] Entropy512:
Didn't see that.

That multi-commit has some stuff I'll put in, some stuff I've already put in, and some stuff I'm really not sure about until it has more testing under the belt. Some of those changes may be what fixes wifi for UCKI3/I4 system image users BUT the same changes might break wifi on non-I3/I4 based ROMs.

Gonna play with it...
[Samsung Infuse 4G] JordanElliott:
ok cool :) btw. u should accept my friend request on here. lol