yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Galaxy_Fan:
Wrote that 2 days before too. Same problem
[Galaxy S II Original Android Development] Galaxy_Fan:
CM7 builds comes with CM7 kernel.Use that first and after complete installation you can change
[Galaxy S II Original Android Development] koolshubh:
Ok so that means frist i will flash codeworks kernal and then flash CM7 rom and after that I can change to any CM7 compatiable kernal... I am correct!!!!
[Galaxy S II Original Android Development] silver2706:
Agreed...B13 is much more stable than b14, 15, 15-2...
[Galaxy S II Original Android Development] DirkTeur Velserbroncx:
No problems so far with 2.1b15 on Axlor HDblog V2, battery life seems less then on v2.0

v2.0 gave me about 3 days with lite use
[Galaxy S II Original Android Development] pachinkosan:
bug here (miui 1.10.21) with 2.1 b14 & b15

when phone in deepsleep, i can't answer phone calls (i hear that phone is ringing, but display is black and don't want to wake up till the call will be denied)

no uv, no oc (just some uc from 1200 to 1000)

screen on profile: ondemand 500-1000

screen off profile: smartassV2 100-500

tried to switch smartassV2 to ondemand - nothing changes

with xcell#14 this is fine, but i prefer u'r kernel, so mb some help or fix <3
[Galaxy S II Original Android Development] spaxx24:
What ROM do you guys recomend for ultimate batterylife? I'm on stock KI8 atm.
[Galaxy S II Original Android Development] vastac13:
Try using without on/off profiles, just smartassv2 on governor
[Galaxy S II Original Android Development] xeq544:
CM7 (10 characters)
[Galaxy S II Original Android Development] :
Why not go all the way and use insanity? ;)
[Galaxy S II Original Android Development] lsj_87:
But i don think CM7 are stable yet rite ? does it still have problems with hardware such as bluetooth, camera and etc ?
[Galaxy S II Original Android Development] xeq544:
Dunno, Ive been on insanity CM on my SGS1 and I liked it. But I kinda fell in love with stock cyanogenmod, its just nice and clean :) And I dont need multidpi so I am satisfied.

CM feels very polished now. The camera is ok, stills are 8mpix, video works at 1080p no problems. Only the camera app is not as good as stock samsung one, but thats just how google made that app. Other than that... CM is now my daily rom... its stable, smoothness is awesome compared to samsung roms. You can lock cpu frequency to max 500 mhz and its still as smooth as with 1200mhz max freq :)
[Galaxy S II Original Android Development] incubus_fr:
1475 mV. I cannot stay a long time at this voltage however, it's just for fun ;-)
[Galaxy S II Original Android Development] armanderli:
How come I can't instal the last two beta 2.1beta 14 and 15 just give me bootloop at bootscreen...I tried everything I know...

Wipe dalvick cache,

wipe partition,

wipe data

Format everything...except internal and external SDcard because there are bunch of files I need in there

Tried different rom...Stock leak samsung Rom...XXKI3,XXKI4,8 KJ2 still no luck

2.1 beta 13 works well and can't go beyond...

I'm usin' KJ2 stock with 2.1 beta 13 right now, in order to root I used CF-root KI3 by chainfire

set cpu to overclock,and titanium back up to restore my files everytimes and My backup pro for sms,mms and call logs....

What Can possibly be the problem...I've been doni' this for some times now so please don't start with noob solution...
[Galaxy S II Original Android Development] pappschlumpf:
Same problem here, govenor ondemandx, no profiles. And the screen stays black. No return from deep sleep! Upped all voltages already. My settings were stable with all versions before. So I think it's not an uv problem!!!
[Galaxy S II Original Android Development] Antonyart:
go to Settings--programs--call settings--answer settings--enforce proximity sensor (DISABLE IT), thats it work done!

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

go to Settings--programs--call settings--answer settings--enforce proximity sensor (DISABLE IT), thats it work done!
[Galaxy S II Original Android Development] Kwakkel:
With beta 15, I am unable to wake my phone from deep sleep.It must be noted that my phone is undervolted:

100 Mhz 790 mV, 200 840 mV, 500Mhz 875 mV, 800 Mhz 950 mV, 1000 Mhz 1075 mV, 1200 Mhz 1150 mV.

These voltages are stable in beta 14 and I'm still trying to lower them. The beta 14 kernel seems to me solid as a rock.

By the way, I would like have the option to run my phone on 25 Mhz. I know that some people here have achieved that. I can't find a proper guide to do this. Has anybody a link or some advice?
[Galaxy S II Original Android Development] bLack_Q:
Hey,

got a bug with Batista Rom 2.4 and b15. The phone wont wake up from deepsleep like my preposter. I use UV with the same settings like in b14. Ondemand governor, no set-cpu screen off profiles. What to do? b14 working with no problems so far.

regards
[Galaxy S II Original Android Development] xeq544:
Jezus, why dont you read previous posts, with beta15 you have to rise uc values by at least 25-50mv. I did for 100mhz - 800mhz steps and now my phone is rock stable.
[Galaxy S II Original Android Development] hausmanis:
Ive also noted that b15 cant handle low uv voltages as low as previous versiond

---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------

Hmm ok so more battery drain in b15 :(
[Galaxy S II Original Android Development] xeq544:
Lol yeah... +25mv will drain a whopping 0.00065 percent more battery.
[Galaxy S II Original Android Development] Kwakkel:
@xeq544 I've read those reports. So I was not surprised that b15 was unstable. But that does not mean that I should not report it here. Why should I raise my voltages if there is a kernel that can handle the low voltages? I'd better return to the kernel with less drain and wait for an update of b15.

And please react a little more civilized instead of scolding at others
[Galaxy S II Original Android Development] xeq544:
I was being ironic... because higher voltages really don't account for more drain, and if they do its neglectable. B15 for example, saves a lot of battery because it enters and leaves deep sleep at 500mhz instead of 800mhz. That saves more battery than all your undervolting alltogether :P And is also the reason why lower uv values dont work and thats a good tradeoff. Thats why I was sarcastic... its all in this thread.
[Galaxy S II Original Android Development] m2smoe:
Hrm. Actually, it doesn't. With b15, I had 12% loss overnight. With b14, only 9%. Of course, this is still in test phases...
[Galaxy S II Original Android Development] xeq544:
That really isnt reliable test, just subjective test. I had 0 percent loss overnight... doesnt prove anything. Doing any kind of conclusions with one night of standby is really not useful. You really think those extra 3 percent are because of higher voltages ?
[Galaxy S II Original Android Development] sergiu84:
Guys, b15 was pulled by the dev anyway... Wouldn't it be a good idea to just sit and wait for the next published update?
[Galaxy S II Original Android Development] jim-bo:
He's since republished two subtly different versions of it, it is these versions people are discussing
[Galaxy S II Original Android Development] droidphile:
Using Root Explorer, navigate to /sys/devices/system/cpu/cpu0/cpufreq/

Click on the top-right button if it says "mount r/w". Open freq_table and edit to replace the last value (100) and change to 25. Your file should look like this

1600 1400 1200 1000 800 500 200 25. Save the file.

Now use SetCpu or Voltage Control to set minimum frequency to 25 mhz. Note that this settings will be lost on reboot unless you use a script. Until then, on every reboot, you have to edit freq_table to use 25 mhz
[Galaxy S II Original Android Development] m2smoe:
Yes, I do, considering pretty much nothing else has changed on my phone. Sure, it's not necessarily reliable, but that's what all clues point to.

In any case, obviously, more voltage used = more battery used. That's just the laws of physics.
[Galaxy S II Original Android Development] xeq544:
True, but its still neglectable difference compared to other battery draining things in the phone. Definately not in the realm of whole percents, more like hundreths of a percent.
[Galaxy S II Original Android Development] shrooms90:
i would reflash, my phone didnt wanna go to sleep when i first flashed b15 but nothing showed up in wakelocks, but now i reflashed and its solved
[Galaxy S II Original Android Development] Molitro:
Guys, you can't say that some voltage difference is the reason of some different % when you have changed your kernel, even if there is little change between versions.

My phone, for one, with b13 had 1%/2h on wifi... b15 yesterday lost it and drained 25% over night, because it had hours of wake state, obviously because the changes made to b15 aren't stable

If you want to judge voltage, do the same test, and I mean exactly the same, changing just the voltage.

I can say, though, that small changes like 25 or 50 mv aren't going to make a noticeable difference compared to everything else, that's for sure.
[Galaxy S II Original Android Development] leod_UK:
Debugging Notification

Their appears to be an issue when using this Kernel on MIUI that the Debugging notification icon is not cleared when removing the USB cable.
[Galaxy S II Original Android Development] Zanr Zij:
To solve, off debugging mode, auto mount storage in USB Setting and re-plug to comp :).

---------- Post added at 05:50 PM ---------- Previous post was at 05:47 PM ----------

2.1b14 I loss only 2% in 7h 30' overnight with airplane mode :). 98% -> 96%!
[Galaxy S II Original Android Development] leod_UK:
cheers for the response but seems more of a workaround as I don't always want it to mount, I sometime just plug into laptop to charge.

When Flashing MIUI Xcell kernel, debug message disappears after you disconnect USB but Kernel doesn't have all the Siyah tweaks and optimisations

:UPDATE disabling debugging prevents mount of storage on miui
[Galaxy S II Original Android Development] hornedfiend:
I agree with the UPDATE comment. With siyah I can only mount the storage with debugging mode on. If not, my windows says it's an "unrecognized device".
[Galaxy S II Original Android Development] madman_cro:
how can i get my frequency over 1600? set cpu doesn t show nothing over 1600. im on b15
[Galaxy S II Original Android Development] lueis:
search before you ask
[Galaxy S II Original Android Development] xuxuzao:
how can i script this?
[Galaxy S II Original Android Development] bgx:
Hey gokhan! I can't lower or rise the 1600mhz step in b15! You changed something?

In b14 I had echo 1401 and its result to 1400 but in b15 everytime I get 1600!
[Galaxy S II Original Android Development] gokhanmoral:
it will be fixed in b16.

b15 was a real mass :)
[Galaxy S II Original Android Development] nightranger73:
+1

I have 1536 as highest value in freq table but I get 1600 at boot although it seems more stable with this clock speed

Edit: tnx just seen post above
[Galaxy S II Original Android Development] Entropy512:
Um, considering our fuel gauge probably has 2-3% of error variance, that means nothing. Especially combined with the fact that any overnight run is going to be different unless you force a fixed high drain (such as permanently wakelocking the device, or the "AOS pingdrain" test)

Edit: Not sure if 100 MHz really buys anything if at all. I need to run some more tests, but in a test where the phone was permanently wakelocked (for a better idea of "steady awake drain" state):

It drained 36% in 8 hours when 100 MHz was enabled. About 66% of the time was at 100 MHz, 33% at 200. Given how often it was "ramping up", it's clear the phone often needed to be at 200 MHz to get housekeeping tasks done. This comes out to 4.5%/hour

It drained 39% in 9 hours when a minimum frequency of 200 MHz was set. Drain was 4.33% - In reality there's likely enough fuel gauge error that it wasn't really higher than drain 200 MHz, but it was so close as to wind up being within measurement error limits.

There's a possibility, however, this may be due to cpuidle - A CPU cranking along fulltilt at 100 may use less power than a CPU hitting idle at 200.

In real-world situations where the phone is entering deep-sleep/suspend:

Most of the time, it will never hit 100 MHz, it spends most of its time in the "accelerate to wait" state

If you force it to 100 MHz by setting a limit of 100 MHz, it'll spend a LOT more time longer awake - better to hit 200, get stuff done, then return to deepsleep.
[Galaxy S II Original Android Development] Galaxy_Fan:
:)

:eek:
[Galaxy S II Original Android Development] dark79:
Debugging has to run for USB mount to work. Try adding the code below to build.prop and see if the icon disappears after removing the cable.

persist.adb.notify=0
[Galaxy S II Original Android Development] Galaxy_Fan:
Worked. It's gone
[Galaxy S II Original Android Development] mavixda:
Can I use this kernel with CriskeloRom?
[Galaxy S II Original Android Development] Galaxy_Fan:
YES, Sure.
[Galaxy S II Original Android Development] incubus_fr:
From what I could notice since I own my SGS2, the gauge is not linear at all and the readings when close to 100% are more than optimistic.

Roughly, 100% to 99% overnight drain is like 50% to 45% (or less) the next night with the same conditions.
[Galaxy S II Original Android Development] RippeR37:
Is there a way to increase usb port voltage when device via usb port is connected? I found working my Patriot 8GB pendrive (both in Fat32 with auto-mount and in NTFS with manual work), but my Samsung S2 5400rpm requires 1.4V when idle/low bandwitch i think, and 2.2V when reading (max?). Unfortunatly it doesn't work default on this kernel. Is there a way to increase voltage on that port so it gets that 2.2-2.5Volts? Or at least some more so i could try and maybe it would work some way :)
[Galaxy S II Original Android Development] :
I stopped using 100MHz a while ago, couldn't notice a difference.. Yes, sometimes I test it, but most of the time I am at stock values 200-1200 or even underclocked to 200-800.. still have to find a reason and noticable difference between 800 and 1200 in daily use.
[Galaxy S II Original Android Development] gokhanmoral:
I was reading speedmod thread and people were talking about kernels being snappier by changing compiler optimization parameters. there is no other reason that my kernel would perform worse other than user dummyness (such as comparing my kernel with smartass@100-1200 to speedmod kernel which would make you a total idiot) because I know hardcore doesn't change anything that would effect performance other than the compiler parameters. oh sorry, he changes jhash implementation but I also use the same implementation.

I thought that compiler optimizations should not make a noticeable difference because -O2 is already used as default and the only thing that can make a difference would be to use -mtune parameter or a different compiler.

I am not against compiler optimizations and I also use them. they increase the performance for sure, but that performance increase can never be expressed as "oh my, this version is A LOT FASTER"...

just to prove that I am not wrong and they are having a placebo effect, I am releasing beta16 WITHOUT ANY COMPILER OPTIMIZATIONS.

I just got 6163 in antutu with 200-1200 ondemand in the second run and I feel no difference. it may be a little lucky because I normally get 5700-5800...

I wonder about your experience...
[Galaxy S II Original Android Development] chadouming:
Gokhanmoral already maxed the out voltage from the usb port if i remember well.
[Galaxy S II Original Android Development] Auridran:
I've always disregarded those comments. It's quite clear that it's placebo and nothing more.

To make the phone "feel snappier", you're going to need way more speed boost than a few optimizations can provide. I'm guessing in the realm of 25%+ extra performance. The version increment game and innate bias give way more speed than anything else!
[Galaxy S II Original Android Development] :
Well I got 6200+ yesterday on stock KJ8 and 'old' b15, so lets see what today brings.
[Galaxy S II Original Android Development] paranoidisc:
I Have a problem..

thnx for the great kernel..

im using miui rom 1.9.16.

recently im flashing ur kernel.

now my bluetooth doesnt work..

any idea why it doesnt work ?
[Galaxy S II Original Android Development] mikebike20:
I am very interested by your solution but i don't know where i have to insert this code. Can you help me please ?

Edit : sorry, i found the file with Root explorer and copied your line, thank you mate
[Galaxy S II Original Android Development] gokhanmoral:
I am not adding it to beta16 now. if it doesn't exist I will add that line.
[Galaxy S II Original Android Development] mikebike20:
Thanks bro, cause lots of miui users like me choosed your excellent kernel and the line doesn't exists
[Galaxy S II Original Android Development] iamsmallpang:
gokhammorel.????? why v2.1 beta 16 CWM download link is beta15
[Galaxy S II Original Android Development] mikebike20:
I put the line given by Dark79 just down this line : persist.service.usb.setting=0 is that good ??
[Galaxy S II Original Android Development] gokhanmoral:
try beta16...

it is without any extra optimizations other than only "-march=armv7-a -mtune=cortex-a9" which doesn't count :)

default is -O2 anyways...
[Galaxy S II Original Android Development] gokhanmoral:
oops :) thanks for the warning.

It was a copy&paste mistake..
[Galaxy S II Original Android Development] iamsmallpang:
THANKS! Your revise....

downloading instantly
[Galaxy S II Original Android Development] gurgenta:
can we download now.

it seems that name of the file you uploaded is wrong.
[Galaxy S II Original Android Development] Bene2k11:
Yep that's okay.
[Galaxy S II Original Android Development] mikebike20:
Beta 16 dowloaded, thxs a lot
[Galaxy S II Original Android Development] :
b16, ondemand 200-1200 - Antutu 6080 first run, 6150 second.

No noticable difference in smoothness :)
[Galaxy S II Original Android Development] Bene2k11:
I'm using this script in init.d on beta 16 to change the freq_table:

21freqtable

#!/system/bin/sh

echo "1600 1400 1200 1000 800 500 200 25" > /sys/devices/system/cpu/cpu0/cpufreq/freq_table
echo "25000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "1200000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

Well and actually it doesn't work. ;D

Did I make any mistakes?! :D

Didn't work for some of the previous betas before too though.
[Galaxy S II Original Android Development] gcrutchr:
B16, JPKJ2 ROM, stock, default settings - no difference - benchmarks about the same as B14,B15
[Galaxy S II Original Android Development] kalpik:
B16 running fine! No perceivable difference in smoothness.
[Galaxy S II Original Android Development] Promsd:
Beta15 - freeze on sleep. Beta 14 - normal sleep.
[Galaxy S II Original Android Development] gokhanmoral:
forget about b15 :) I was sleeping yesterday while modifying the code :)
[Galaxy S II Original Android Development] minidou-77:
no problem with b16 and the last Hyperdroid

@1400Mhz, sio and stock voltages :

6719 with Antutu
[Galaxy S II Original Android Development] nerotix:
@gokhan

I'm using 2.1b14 on Galnet MIUI 1.10.25 and its working flawless. However, on the kernel that comes with Galnet MIUI 1.10.25, the headset volume is working properly, when I install this kernel, it doesn't work anymore.

May you wonder what I'm talking about:

In AOSP roms as CM and MIUI there used to be a bug then if u set ur headset volume to 100% it wont go as loud as it should be, the loudness is still 50% even tho its set to 100%. If you want to fix this problem, you perhaps could check in the kernel that comes with Galnet MIUI 1.10.25.

Hope this helps you to resolve this issue.

Thanks for reading

P.S I wrote this before but didnt have any respond and the thread gets spammed alot so thats why I wrote it again. Please not that I'm not trying to push you to do anything but this is just a friendly notification, if this is fixable, i think your kernel will attract more people since this is the only thing thats been buggy on CM7/MIUI for a while and almost noone was able to fix it. And since you're the kernel master ;) maybe you could check it out.
[Galaxy S II Original Android Development] :
FFS, I did search, with specific criteria of many different varieties (each specific in nature), but **** me if I can find out whether or not beta kernels still come with CWM 5.X.X

I guess I forgot how to use the intarweb.
[Galaxy S II Original Android Development] lpsi2000:
Yes, CMW 5 is the only way we go here. Let it be known we love CMW5 and that is that.:D
[Galaxy S II Original Android Development] chadouming:
yes it still come with CWM 5
[Galaxy S II Original Android Development] :
Thanks gentlemen. Let it be known that I prefer... CWM X.X.X
[Galaxy S II Original Android Development] gokhanmoral:
I noted that problem and will look into it.
[Galaxy S II Original Android Development] Bene2k11:
Push... :/
[Galaxy S II Original Android Development] nerotix:
Cool thanks, if you need anymore information feel free to PM me, or if u want something tested :)
[Galaxy S II Original Android Development] gokhanmoral:
in rc1, CWM recovery will be optional.

I will prepare a CWM flashable zip for v4.0.0.2 and v5.0.2.6

v5.0.2.6 will be default and you will be able to flash CWM recovery using CWM recovery :)
[Galaxy S II Original Android Development] gokhanmoral:
check permissions.

and use terminal to see if it works.

I tested if I can change 100 to 25 and I could.
[Galaxy S II Original Android Development] dica:
Thanks for this option, this will avoid the compatibility issues with other roms like check revolution rom.
[Galaxy S II Original Android Development] gokhanmoral:
there is absolutely no compatibility issue with check revolution rom and beta16. I am using it to test and v5.0.2.6 is working without any problems.

maybe in 2.0 or earlier versions there were... but not in any of the recent versions...

I will put that option to let users upgrade CWM recovery later.. and also for those who "afraid" to try v5.0.2.6 and the only downgrade option will be v4.0.0.2
[Galaxy S II Original Android Development] Bene2k11:
Is there anything wrong with it?
[Galaxy S II Original Android Development] YaocH:
Are you using voltage control? I had similar problems previously whereby voltage control was screwing with my settings and i could not save my settings to freq_table. If you are, you can try to uninstall it and see if your settings stick. Re-installing after that seems to cause no further issues for me, but I'm no longer using voltage control.
[Galaxy S II Original Android Development] gokhanmoral:
those screenshots are not enough to tell you if it is ok. you also need to check /system/bin/sh and it's permissions.

if you don't have it, try to replace the first line with

#!/sbin/busybox sh
[Galaxy S II Original Android Development] Promsd:
beta 16 - freeze on sleep :( wtf? maybe bad UV setting?
[Galaxy S II Original Android Development] Bene2k11:
Uninstalling Voltage Control didn't resolve the issue.

Editing freq_table manually works.
[Galaxy S II Original Android Development] chadouming:
B16 is working flawless for me ^^, no SOD even with lower UV than usual. On MIUI 1.10.25
[Galaxy S II Original Android Development] nikzDHD:
B16 sod as well on same uv settings as 14, will tweak them again.
[Galaxy S II Original Android Development] AndroidGX:
beta16 :

Still need to stay MIN at 875mV, otherwise device freeze :(

*edit*: SOD with same UV settings as beta14.
[Galaxy S II Original Android Development] Galaxy_Fan:
Outstanding COOL!

I just need CWM 5.x.x but the possibility to choose...COOL
[Galaxy S II Original Android Development] the^one123:
Same Here. Witch frequenz you have min?

Till beta 14 these are my settings.

OC Daemon.

100 @ 825

200 @ 875

500 @ 875

800 @ 975

1000 @ 1075

1200 @ 1175

At the moment the device is freezing several times.

Should i upper the voltage for 100mhz up to 875mv or is there another frequenz which is using more power now.

theone