yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
OK... Don't know, sounds like the J2 leak breaks wifi in ways that J2 on the Infuse didn't then...

Either that or the linking workaround depends on initramfs mods that I already had in my Infuse kernels.

Unfortunately I already have way too much on my plate to mess with the J2 leak for the time being... Maybe in a week or two.
[AT&T Samsung Galaxy S II SGH-I777] mjgspr95:
No prob... I only use tether at work and wifi at home. I can switch when needed. btw modem and GPS are better with j2 for me.

i777 stock 2.3.5

14 tog mod

Entropy512 Doom

Onepointsixingit
[AT&T Samsung Galaxy S II SGH-I777] mjgspr95:
:-) +1

i777 stock 2.3.5

14 tog mod

Entropy512 Doom

Onepointsixingit
[AT&T Samsung Galaxy S II SGH-I777] saltytostitos:
Phenomenal

Just wanted to post this quickly to say my battery life is great with this kernel. I usually load my phone up with a ton of apps and I use a lot of widgets and auto-syncing.

I run 200 to 1.2 on conservative. After a 12 hour workday i'm right around 50%. Most of my use is data, with plenty of phone usage.

Keep up the great work!
[AT&T Samsung Galaxy S II SGH-I777] Simba501:
Great work. I had one weird hiccup, but it seemed to be a one-time freak incident, as I've not seen it again or been able to reproduce it. Battery life is great with ondemand, but considering others are complimenting conservative, I may give that a shot.
[AT&T Samsung Galaxy S II SGH-I777] mjgspr95:
Using coservative as well. I usually switch to ondemand, but no lag yet.

Sweet!

Edit: I spoke too soon... Conservative just not good with OC and I'm a OC junky. Conservative great w/o OC

i777 stock

Entropy512 Doom

Onepointsixingit
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Added some small documentation on using the NFS modules to the first post.
[AT&T Samsung Galaxy S II SGH-I777] sweetboy02125:
First thanks for the kernel that helps me change the boot animation.

However, I noticed a slightly drain the battery a bit more than the regular CWM 5.0.23 or I'm imaging. I flashed DD_10202011_exp
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
My battery life is awsome. unplugged at 6:30 this morning, still at 61%, light to medium use. And i'm in a marginal low signal area at home, where I've been a good part of the day.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Well, if it's "slightly", then there are way too many variables (signal strength, how many emails you get, etc.) that affect drain... At least in theory, this kernel should beat the CWM kernel in nearly all situations, as I do include a few power management fixes (some of which come from codeworkx himself!)

Now, codeworkx's Cyanogenmod kernels - that's a different story. Honestly you won't see too much difference between his CM7 kernel and this one - much of the capabilities of this kernel come from there. :)

There's a reason why, even though I do often run CM7 (not yet on this device - probably not until I wind up in a "no more ideas" phase with this kernel), I usually wind up just running the stock kernels. On the Infuse, it was difficult for me to do a better job than LinuxBozo, and here, there's no way my skills compare to those of atinm and codeworkx.
[AT&T Samsung Galaxy S II SGH-I777] Simba501:
Has anyone noticed unusually long media scanning times?
[AT&T Samsung Galaxy S II SGH-I777] Misterjunky:
re: Media scanning times

The only time I noticed very long media scanning times is when

the usb from the computer is plugged into the phone.

It looks to me as if the phone is trying to SYNC all my MP3 music

which is on my computer with the MP3's that there is on the phone.

I wish there was some kind of toggle so we can enable or disable this.
[AT&T Samsung Galaxy S II SGH-I777] sweetboy02125:
Uh im talking about the CWM from codeworkx use for stock on another thread. Any way i still use your kernel cause i hate at&t bootscreen. ;)
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
That's what I meant - his CWM kernel is very basic (That's what its intent is as far as I can tell - a basic, stable, as-close-to-stock-as-possible way to get CWM...), I'd be surprised if it did better on battery because it's missing power management features present in my kernel and his Cyanogenmod kernels.

I believe mediascanner can be told not to scan certain directories by putting .nomedia into them.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Just as an update - There probably isn't going to be an update of this series for a few days at a minimum. I'm in the process of running some experiments that will never be released.

Specifically, I'm trying to identify exactly where in the patching process from 2.6.35.7 to .14 the infamous "AOS Bug" changes in nature. As a result, I need to patch halfway, test, patch back or forward halfway again (depending on test results), etc. to narrow down exactly which patch it was. Since the patch/test/patch cycle takes quite a while in the "test" phase, this is slow going.

After that, depending on investigation results, I'm thinking of adding support for 100 MHz operation in order to reduce drain during svnet-dormancy wakelocks.
[AT&T Samsung Galaxy S II SGH-I777] tboooe:
RAM optimization script?

Entropy, just curious if you have any experience with juwe11's RAM optimization script (http://xdaforums.com/showthread.php?t=1111145). Will this play nice with your kernel?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
It'll work, but it is kinda pointless.

Hint: If you see someone claim that they have a "universally best" lowmemkiller tweak, they're lying or talking out of their ass.

OOM killer settings are going to have VERY different optimal settings depending on how much RAM a device has - and ours has 1GB.

Some of the filesystem I/O stuff in there might be beneficial - but again, what is best on a system with 256M or 512M RAM is not going to be best on a system with 1GB RAM.
[AT&T Samsung Galaxy S II SGH-I777] Simba501:
I'd welcome this gladly. I'm still experiencing that weird wakelock with the Calendar (not kernel related), so this would help me as well since it doesn't ramp up the CPU.
[AT&T Samsung Galaxy S II SGH-I777] spyz88:
Kernel Module

Entropy,

Would it be possible to add the iptables “OWNER” Module? The reason I ask is because that's what Orbot (TOR for Android) needs so that transparent proxying will work. Otherwise it fails ;/

If possible thanks alot, if not I understand and thanks for all your work.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
I'll check tonight, but this one should be easy, just a defconfig change.
[AT&T Samsung Galaxy S II SGH-I777] mbze430:
revisit of BLN

Entropy,

I know that BLN isn't high on your list and I know you said you will be doing other test work in the next week or so. But I want to revisit this.

I was reading over in the Intl SGS2 Dev on Jame Bond Care Bear Kernel + BLN

You have mentioned that the BLN will not release wake_lock in your own testing(kernel). However, it seems there is a "work around" with the BLN pro App; also stated in that thread. So I was wondering if you can implement it in an experimental BLN release and have a few of us go at it along with the BLN pro app.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
I may consider that, especially after I finish the current power management research effort. It might be a good combo with 100 MHz support.

Plus, unlike the Infuse community, people here seem to be mature enough to handle experimental features in a responsible manner.
[AT&T Samsung Galaxy S II SGH-I777] jjesusfreak01:
You are making a dangerous assumption...

PS: Great job, your kernel has the honor of being the first custom kernel on my phone.
[AT&T Samsung Galaxy S II SGH-I777] MikeyMike01:
Spend 10 minutes in the Infuse forum. You'll want to stab your eyes out.
[AT&T Samsung Galaxy S II SGH-I777] eep2378:
+1 Along with wanting to stab a few other things too :eek:
[AT&T Samsung Galaxy S II SGH-I777] slifer315:
Is it really worse than the Captivate forum?

Sent from my SGS II.
[AT&T Samsung Galaxy S II SGH-I777] mbze430:
Man, I can't WAIT for the 100mhz option. I was looking at my avg CPU usage it's been 80% @ 200mhz / 825mA and 8% @ 800mhz and the rest been scatter across up to 1.4ghz. If I can use 100mhz this would save some more juice.
[AT&T Samsung Galaxy S II SGH-I777] rbtconsultants:
So, I have two (likely) unrelated minor issues.

Today I noticed my better draining faster than usual. CPU Spy showed it wasn't going into deep sleep. Most of the time was at 200. No real indication as to why, although email showed a lot of awake time. I do use exchange email. A reboot seemed to fix it.

The other is that cell standby in battery use always shows 100% no signal, which is weird and wrong but doesn't seem to affect battery life. Anybody else notice this?

Thanks for everything.

Bob
[AT&T Samsung Galaxy S II SGH-I777] jsmith8858:
No, BLN plus 100mhz would be a GREAT combo! Looking forward to this, good luck and thanks again for your hard work!
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
1) Check out my known battery drainers thread in General, includes some methods for hunting wakelocks. Don't have a link atm, my brain is fried after this... PAIN AND SUFFERING: https://github.com/Entropy512/linux_kernel_sgh-i777/commits/samsung_update3

(Note: For those astute in git, those are not against my main tree, but against the kernel tree from before I started touching it. Later I'll start working on merging, probably this weekend, and likely one little piece at a time, which is why I split it all.)

2) 100% no signal is a known framework bug, no kernel involvement I'm 95% certain.
[AT&T Samsung Galaxy S II SGH-I777] claimui:
Entropy, have you looked into the "Deep Idle" state discussed in this Nexus S thread and whether there is something comparable for the SGS2?

EDIT: Nevermind, just found this post by gokhanmoral in the SiyahKernel thread.
[AT&T Samsung Galaxy S II SGH-I777] Adelaide.:
If you go into Settings > About phone > Status and keep that screen open for a few seconds it fixes it so it shows the phone having a signal. You have to repeat this every time you rest the phone though.
[AT&T Samsung Galaxy S II SGH-I777] Adelaide.:
I installed this yesterday, and I am running into a couple of problems. I'm not sure if they are related or not, but I figured I would ask.

I'm rooted and running stock. After installing the kernel I also installed SetCPU and CPU spy. I did not change any CPU settings. Several apps also updated from the market, but I don't remember what any of them were.

The battery counter is acting strange. I've got a minimalist text widget on my home screen and the battery displaying on my extended control bar on the lock screen. The battery appears to be updating irregularly. It will go down several % at a time, and then not change for an hour on both battery read outs.

The phone isn't remembering that I have launcher pro set as default. I've been running it since a day or two after I got my phone without any issues. Now when I hit the home button it randomly asks me what app I want to perform the action with. I've tested a bunch of apps, and figured out that it only happens after waking the phone up. It remembers the setting until the next time the phone goes to sleep.

The battery usage chart isn't displaying things correctly. I had been on that screen when I got the first pop up about the home screen. I reset the phone, and when I looked at the battery usage chart roughly 3 hours of "on battery" time had disappeared. It went from nearly 13 hours down to just over 10 hours of on time. Another reset did nothing. The 13 hour number was correct.

Thanks a bunch guys. Let me know if there is any more information that would be helpful.

Edit 1: I decided to flash stock and see if I still had any of these problems. Odin can see my phone, but fails at set up connection every time I try and run it. I've never had any issues with Odin before. I tried it with both USB debugging on and off. Scratch that. Hardware issue, farking cats chewed on the USB cable. It must not have been getting a solid connection.

Edit 2: Flashing stock did not fix anything. I reflashed so I had CWM and restored my phone back to where it was before I installed this kernel. Everything appears to be working fine now. The battery usage chart even jumped back up 3 hours. If anyone has any ideas what may have happened, please let me know.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Those are WEIRD... The closest behaviors to that I've seen anyone report were from someone who diddled with batterystats.bin

I only trust the time listed in Settings->About Phone->Battery Usage in the following situation:

Charge to 100% (wait for the notification)

Remove from charger

As to not remembering launcher settings - I have NEVER seen anything like that happen before. My guess is some setting in /data was hosing stuff up.

Edit: That loose USB connection could have made the fuel gauge wig out temporarily... battery pull might have fixed that.
[AT&T Samsung Galaxy S II SGH-I777] Adelaide.:
I am so glad to see you online. I think it has to be one of the apps that updated. I reloaded my CWM back up and it was working perfect. I went to the market and updated the apps that I knew were waiting and it started again. I'm going to uninstall them one by one and see what happens.

The battery wig out started a couple of hours before I ever plugged it into the gnawed on USB cord.

Edit: Bloody hell, it was widget locker! I froze it with TiB and the stupid launcher pro default issue stopped.
[AT&T Samsung Galaxy S II SGH-I777] agh1701:
Had simalar problems using 10/20 EXP + JK2. What I did:

Factory reset.

CWM clear battery stats.

ran down phone and charged to full.

Right now the battery full chime occurs at 97%. Do not know if what did fixed it or it just went away.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Clearing battery stats only deletes the statistics displayed by About Battery - battery stats are not used in any way for state of charge calculations by our fuel gauge. This is a Samsung, not an HTC.

Similarly, running down the phone and charging to full does nothing to recalibrate the battery. The only time this ever might have benefit is after installing a battery that has been sitting unused for many months (a few charge/discharge cycles will dissolve the passivation layer). In fact, your state of charge estimates will be more likely to be inaccurate for a little bit of time after doing this due to the rapidly changing battery voltage.

I've generally seen that the deeper the state of discharge the phone is charging from, the farther it'll "bounce back" after charger removal on the GS2. Probably the same on the stock Infuse - but I explicitly had code in that kernel to drop charging current as the charging process went onwards. (So far, it looks like putting that code into this kernel will not be possible - the charger chip has three current settings, one of which is useless. It's one of the few differences from the I9100.)
[AT&T Samsung Galaxy S II SGH-I777] Simba501:
You must have updated widgetlocker. I was experiencing the same thing. It came down to its homehelper feature. Nothing would stop it from clearing the default; except if you enabled it. This fixes the issue. Enable homehelper and select the launcher of your choice. In the past, it didn't matter. But apparently, there's a bug in the most recent update that causes it to behave weirdly. I hadn't experienced the problem since opting to use it.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
I've seen you say this several times, and I've been meaning to ask...

On the captivate forums, it was generally accepted knowledge, or perhaps dogma, that flashing roms and especially kernels with a partially discharged battery would screw up the battery guage, and that clearing battery stats and running deep discharge/recharge cycle was the way to fix it. Never saw anyone over there say otherwise.

Was that just unenlightened hoodo, or was that phone different?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Unenlightened voodoo - I'm even more positive of this than with the GS2. All first-gen GalaxyS phones had a MAX8998, which had fuel gauge functions identical to the MAX17040, which has a datasheet publically available at http://www.maxim-ic.com/datasheet/index.mvp/id/6621

Even without that datasheet, if you read the kernel sources, you'll see that there is no way to load battery stats into the gauge chip.

It was just a case of people blindly applying HTCisms from the Winmo days to Samsung Android devices.

Now, at some point, the 17042 in our device MIGHT have advanced features in it enabled that require calibration (there are some extra functions in there), but right now they're not enabled and the only input to the gauge is "reset".
[AT&T Samsung Galaxy S II SGH-I777] bigblue95z:
Running the 10/20exp. Just downloaded Voltage Control and it is set to 'ondemand'. I have not changed a thing. Has this changed since OP then? Or is VC full o shat?

EDIT: OK, I lied. I'm running the 10/20 from S8
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Update: I have the following items in testing:

1) 100 MHz support

2) A revised more generic SoD patch that doesn't need to be redone every time the clock level table changes

Unfortunately, one of these caused an SoD this evening, so more testing/investigation is needed prior to release. Right now it's looking like something in 100M support, so I need to take a closer look at that.

Longterm plan is now to try and reduce the impact of "accelerate to wait" on suspend/resume. (A negative side effect of the SoD patch.)
[AT&T Samsung Galaxy S II SGH-I777] Simba501:
Awesome. I really appreciate these "updates." Love to hear em.
[AT&T Samsung Galaxy S II SGH-I777] Adelaide.:
I am back running this kernel with zero issues so far. Sorry for blaming your kernel Entropy!
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Something is causing SoDs, not sure if it's 100 MHz or my attempt to rework the SoD patch.

Gonna take a day or two to find out. Also, 100 MHz may simply not be worth it in terms of power consumption reduction - need more testing.
[AT&T Samsung Galaxy S II SGH-I777] mbze430:
at what mA is 100mhz running on your testing?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
I haven't wired an ammeter to this thing, the only thing I've done is a controlled drain test (leaving the phone sitting but with a wakelock to keep it running)

I realize, however, that I should have done it in airplane mode.

There's a possibility that cpuidle may make 100 MHz irrelevant unless it can reliably run at a significant voltage reduction from 200. Cpuidle completely turns off the CPU clock when there is nothing to do, so spending 100% of your time running at 100 MHz may not be that much more efficient than running 200 MHz at 50% load at the same voltage. In fact it might be less efficient because, at least from looking at the cpuidle code, it seems like deep idle (this is different from deep sleep/suspend) does turn off a few things other than the CPU core.
[AT&T Samsung Galaxy S II SGH-I777] mbze430:
I completely agree.

I don't know if you have the ability to check this from the programming code or you might actually have to get physical on the unit to find voltage usage(voltage meter)... but I think without knowing the amount of voltage used in deep idle vs. usage voltage on a stable 100mhz.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
I just need to run some more overnight wakelock tests. So far, running one with 100 MHz support and one with the CPU locked to a min of 200 MHz made no difference in overnight drain.
[AT&T Samsung Galaxy S II SGH-I777] Dungeon47:
To fix: in WidgetLocker Settings>Advanced>Root Helper>

Uncheck HomeHelper ondemand via root,

Disable Home Helper.
[AT&T Samsung Galaxy S II SGH-I777] jgrimberg1979:
I got a stupid question but i got to ask.. I just bought this phone and i came from an htc more or less backround. I am very familar with fastboot, adb, and pretty much every modding tool out there for htc phones but I new to samsung and odin and heimdall...

1. Is it not possible to flash a kernal via flashable zip in cmr?

2. is Odin and Heimdall essential the same thing? If so which one is better?

I want to try out this kernal but i was hoping to get some feedback before i got kernal crazy like i do with my old htc phones.

An another note. I have owned a lot of phones, iphone4 thunderbolt, bionic. and a bunch of htc phones and i swear this phone is by far the best in every aspect. I love it. Sorry if went off on a tangent in this thread.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
1) You can flash in clockworkmod, that's why I have two sets of instructions, one for tar releases one for zip. I actually should redo my instructions since I haven't done a tar release in a while.

2) Odin/heimdall is kinda similar to fastboot on other devices - it's a downloader mode that can flash anything. Heimdall is an open source reimplementation of Odin, Heimdall works on MacOS, Linux, and Windows, Odin is Windows-only.
[AT&T Samsung Galaxy S II SGH-I777] jgrimberg1979:
Thanks for you quick response

So since i am a windows user, i can stick with odin and it can do everything heindal can do correct?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Everything? Not so sure. Heimdall has a few extra features - but for most users these aren't needed.

I really don't have that much experience with Odin, being a Linux user. However I know of at least two ROM devs that choose Heimdall over Odin even on Windows machines.

On an unrelated note:

After further testing, I'm not going to release 100 MHz support, the results I have had were as follows:

In normal operation, drain was either equal or higher when I had 100 MHz support enabled

In artificial tests run as follows:

Set the phone to airplane mode, eliminating CPU usage for radio housekeeping and background data

Force a permanent wakelock as follows to get suspend/resume power usage out of the picture:

echo "spork" >/sys/power/wake_lock

Set the Conservative governor to ignore nice load so the next command doesn't cause the CPU to scale

Run the following command to eat up all spare CPU cycles, at a low priority:

nice -n 10 cpuhog

End results:

6.5%/hour drain in one overnight test at 200 MHz

5%/hour drain in one overnight test at 100 MHz

Not much difference, obviously at 200 you're close to an area where static power consumption dominates. In addition, this was in a highly synthetic non-real-world test. In reality, a CPU at 200 can enter "deep idle" for longer periods of time than a CPU at 100. If you read through arch/arm/mach-s5pv310/cpuidle.c in the kernel sources, it looks like deep idle does a bit more than clock-gate the CPU and shuts off a few other peripherals or at least puts them in a powersave mode. This likely explains why in a more "real world" drain test, 100 MHz actually did worse than 200 MHz. Spending 50% of your time in deepidle and 50% active at 200 is better than spending 100% of your time at 100.

Some other time I might be able to tune 100 MHz to be advantageous, but right now - making it actually matter would be a major project, and there are far more important things to do right now like start integrating the I9100 update3 improvements and try to reduce the impact of "accelerate to wait" on the battery.

cpuhog was a program I wrote myself - I'll post sources for it later, and will also post the 100 MHz patch I was testing with - but it won't be included in a kernel release
[AT&T Samsung Galaxy S II SGH-I777] mbze430:
I still say this is beneficial, maybe not right now.. but I see potentially using 100mhz.

Thanks for the update
[AT&T Samsung Galaxy S II SGH-I777] vladm7:
with those results, the marginal benefit of having 100Mhz can be for constantly running, low-consuming tasks (music player?). But I presume that other battery consumers on the phone would make the saving negligible and not worth risking stability.

-- vlad