yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] RarrKnuq:
I’m using cyanogenmod “stable” 7.1 build on Samsung galaxy S2, and found some strange problems which I figured was somehow caused by kernels with BLN functionality. I found that after flashing SiyahKernel v2.0 Beta 8 (or another BLN-enabled kernel, like this one: forum.cyanogenmod.com/topic/31387-bln-support-for-galaxy-s2), dithering, or antialiasing or whatever makes fonts look nice is somehow disabled. Gtalk, Gmail, Google reader font becomes very ugly, others apps are not affected that much, but still affected. Everything looks like non-antialiased downsized image. The only place where I could find any additional info about this issue is here: forum.oxygen.im/viewtopic.php?pid=7360. It’s strange, but _at boot_, before first lock, fonts looks normal. I have to cycle lock-unlock once, and here it is – my eyes bleeding again… What’s interesting, that this stuff can’t be shown on screenshots – screens look the same. So it looks like some drivers issue… I’ll try to make a photo when I get home.

So, again, steps to reproduce:

1.	Flash Cyanogenmod 7.1 to SGS2

2.	Boot your device, launch Gtalk or Gmail app (not Email). Look at nice fonts in messages.

3.	Lock phone, immediately unlock. Look at nice fonts in messages.

4.	Flash kernel with BLN support, for example SiyahKernel (clear caches etc).

5.	Boot your device, launch Gtalk or Gmail app (not Email). Look at nice fonts in messages.

6.	Lock phone, immediately unlock. Look at those fonts in messages. Be careful, your eyes may bleed.

I hope I’m not only one with this issue

P.S. Sorry about ugly links. I can't post normal ones - antispam forbids that.
[Galaxy S II Original Android Development] Entropy512:
No, since there's increasing evidence that 1.8 actually made the AOS bug worse:

As in, it's still happening, but you don't see any signs of it any more other than your battery draining. It's still something that needs more investigation/testing. I'm going to start slowly rolling back Linux base kernel revisions in a test tree to see which base upgrade (.8, .9, .10, .11, .12, .13, .14?) made the change and what was done in that revision. Gonna take a few days though!

Define "safe" - higher charge currents WILL reduce the total number of charge/discharge cycles your battery can take. How much? Unknown. It's why my Infuse kernels had a variable charge current, higher at low battery and slowing down as the battery charged higher. Was inspired by this - http://www.engadget.com/2011/02/20/apple-patent-application-points-to-denser-batteries-improved-ch/

Also don't set it higher than your charger can handle - weird things will happen if the charger "browns out". Don't always believe the charger specs too - once I got a "1A" charger that was only good for 300-400 mA.

Not unless you want to lose your capacitive buttons.

Right now there are two I777 kernels, codeworkx's and mine (unless you count the CM7 kernels)

Charging might be hosed if you flash this on an I777 too - I777 has a different charger chip than the I9100. (Sort of - I777 has the MAX8997, however charging is offloaded to a MAX8922 for some reason. Freaking annoying because the 8922 only has two useful current settings - 400 and 650 mA.)
[Galaxy S II Original Android Development] R_M_R:
Hello..... can u pls fix this or is it fixed in V2.0 ?

:mad::mad:
[Galaxy S II Original Android Development] spaxx24:
This is awesome. I slept about 8 hours, and battery went from 100% to 98%!!!?? And after that, I listened to music on bus/subway to work (about 1hour 10 min) and it went from 97% to 93%.. awesome or what?

Im was on beta8, Touch X-power ki8, smartassv2 (100mhz-800mhz wake, 100-200 sleep) with:

*100 MHz - 800mV

*200 MHz - 800mV

*500 MHz - 850mV

*800 MHz - 900mV

Flashed rc1 now, gonna see if it is as good.
[Galaxy S II Original Android Development] gokhanmoral:
I will upload rc2 in 5 mins.

and I won't upload CWM flashable version this time.

because you guys should learn how to flash tar files if you already have root.

download the attached apk and figure out how to flash it. (tip: flash kernel)
[Galaxy S II Original Android Development] verrox:
Yey, waiting eagerly.

On galnet miui, the contrast goes realy high after a screen off, did you fix this? :)
[Galaxy S II Original Android Development] kenkiller:
Man you're hardworking..... :D
[Galaxy S II Original Android Development] RarrKnuq:
Hm, maybe you are suffering from same thing I do? look at my post above
[Galaxy S II Original Android Development] verrox:
Sounds like the same thing.

Atleast im not the only one affected :D
[Galaxy S II Original Android Development] iamsmallpang:
v2.0rc1 CWM can;t work..

please fix it
[Galaxy S II Original Android Development] joeyfong:
RC2 is out, pls check
[Galaxy S II Original Android Development] YaocH:
With all due respect, the CWM flashable version is really useful to those who are not constantly tethered to their PCs or are using other OSes other than windows. It's also great to be able to update on the go since the rate at which you are releasing revisions of your kernel is nothing sort of amazing. Do hope that you will seriously reconsider your decision as I'm quite excited to try rc2. Else i guess i can only update after I get home at the end of the day):

Much appreaciated!

Edit: I should add that i do know how to flash tar files by first extracting the zImage file and then flash it using CWM. But i don't know why i lost CWM after i changed to CM7.1.
[Galaxy S II Original Android Development] and1_vj17:
just use darkyrom to flash the tar much more easier than going to recovery first
[Galaxy S II Original Android Development] spaxx24:
Why dont you just download the .tar in your phone and then flash kernel from the app?
[Galaxy S II Original Android Development] gokhanmoral:
Do you have root? If so just read the post you have quoted and use the app. It is easier than flashing in recovery.
[Galaxy S II Original Android Development] stifmaister:
Hi ,

i have root and currently running the rc1 version of the kernel.i tried to flash Rc2 from the CWM app, using the flash kernel feature, and after the phone reboots in recovery, the installation fails with some errors about the filesystem.

I know how to flash through odin, but i m not currently tethered and i would appreciate if you could release a CWM zip flashable version.

Thanks for this wonderful kernel

Sergio
[Galaxy S II Original Android Development] terenceleechan:
no need to extract zimage from the tar right? just flash the tar through the app? sorry, im used to flashing through cwm recovery, so im trying to learn. also, if i use this method, will cache and dalvik cache be wiped automatically? thanks!
[Galaxy S II Original Android Development] YaocH:
Noted, thanks!!:D

---------- Post added at 02:39 PM ---------- Previous post was at 02:38 PM ----------

Yeap i meant the CWM app.
[Galaxy S II Original Android Development] kenkiller:
Guys, if u really want the CWM zip so much just open the tar and a previous zip with 7-zip, drag and drop the zimage file from the tar into the zip and it'll be ready to flash immediately. :D
[Galaxy S II Original Android Development] joeyfong:
I did that via cwmmanger, and then nothing happen, any further steps???
[Galaxy S II Original Android Development] netchip:
Freakin symlink in recovery.rc /misc to /etc

Sent from my GT-I9100
[Galaxy S II Original Android Development] dtekkt:
Guys, in cwm app you must select flash kernel", is it really that hard?
[Galaxy S II Original Android Development] terenceleechan:
do i need to extract zimage or just directly flash kernel (tar)?
[Galaxy S II Original Android Development] tomj777:
Edit: this should have quoted Netchip's symlink explanatory post

That explains that then (i was very tired then).

Hey G. I reckon you should continue to attach the CWM zip, just for convenience and consider it an act of kindness where you force a learning curve climb on those new or missing curiosity.
[Galaxy S II Original Android Development] bandit79:
u can flash directly the .tar file via CWM-flash kernel
[Galaxy S II Original Android Development] dtekkt:
Directly flash the tar
[Galaxy S II Original Android Development] spaxx24:
Look.

1. Download the .tar to your phone, just as it is on this site.

2. Start Darky ROM app, or CWM app.

**IF YOU STARTED**

(a) DARKY, go to 3a

(b) CWM app, go to 3b.

3a. Select "Flash/Install file from SD Card" in Darkrom.

3b. Select "Flash kernel" in CWM app.

4. Select the .tar file, click it.

5. ???

6. Profit.
[Galaxy S II Original Android Development] YaocH:
You will have to extract the zImage file from the tar and then flash it using the CWM app. Don't get it why people choose to give a whole lot of drama when they can just use the time to provide such a succinct answer and solve the poor guy's misery.

Edit: at least that was what i did and it worked. Looks like i have much to learn though=X Sorry for giving the wrong info
[Galaxy S II Original Android Development] :
You have to extract zImage only when you flash from stock back to cfroot or similar to get rid of yellow triangle, after that just flash .tar. no need to extract anything.
[Galaxy S II Original Android Development] terenceleechan:
thanks! its clear to me. its just because i read about extracing zimage
[Galaxy S II Original Android Development] YaocH:
Noted. Thanks!:D
[Galaxy S II Original Android Development] :
Also, if you rooted (properly ;)) with cfroot kernel, you already have cwm app installed.
[Galaxy S II Original Android Development] joeyfong:
I am running cm7 with 2.0 beta 8, cannot flash the tar file via cwmmanager......any help???
[Galaxy S II Original Android Development] gokhanmoral:
I will provide CWM flashable zip file for the release. however, if you have CWM recovery problem you cannot use zip file to fix that problem and I really don't want people continue bashing the thread with "oh noo, now I cannot flash zip file..." messages...

CWM recovery is broken in rc1. it was my mistake and I am really sorry for that.

but it is not a catastrophic problem which should cause 10 pages of posts.

I also want to note that I am living in GMT+2 and I sleep at nights normally :)

installing an additional application and helping yourself in these kind of situations is not a bad thing after all.
[Galaxy S II Original Android Development] :
Reboot phone, start cwm manager, go to flash kernel, choose ...rc2.tar, wait, do a second reboot.
[Galaxy S II Original Android Development] YaocH:
So i just flashed rc2 and i noticed that the vibration issue is back again, I'm using cm7 nightly 84 and the heptic feedback is occasionally soft and normal. Fluctuating frequently between the two. It was fine when i was using b8 previously. Flashed using darkyrom tool2.
[Galaxy S II Original Android Development] kva:
Hi, why do you set constraint for the 100Mhz to 800mv min ? I was using 775 on my phone and it was working very well...
[Galaxy S II Original Android Development] YaocH:
Also noted that the auto brightness made the screen significantly dimmer than usual as compared to b8. Is it a feature you implemented to try to save some battery life?
[Galaxy S II Original Android Development] joeyfong:
@YaocH, how did you do that under cm7?
[Galaxy S II Original Android Development] xeq544:
Cant flash rc2 from rc1 using cwm manager, i click on flash kernel, choose the tar file, and bam nothing happens :) (Im on cyanogenmod nightly85)
[Galaxy S II Original Android Development] YaocH:
Appreciate if you could quote the msg in future, but anyway i went to look.

I downloaded Darkyrom Tool 2 from the market. (just search for darkyrom) go to the DarkyROM tab and then only tick the option for install kernel. Then go back to General tab and then under the flash choose the kernel from the folder you saved the tar file at. This method worked for me. Hope it's of help to you.
[Galaxy S II Original Android Development] joeyfong:
Same here 10 chars

---------- Post added at 08:35 AM ---------- Previous post was at 08:32 AM ----------

Rebooting, thx.
[Galaxy S II Original Android Development] YaocH:
If i flash from DarkyROM tool 2, i dont get to wipe cache partition and Dalvik Cache. Will this cause any problems? Coz i'm experiencing instability with rc2. How do I go about to wipe the cache partition and Dalvik Cache before flashing rc2?
[Galaxy S II Original Android Development] mikebike20:
Thanks Gokhan for this new release, i was surprised of rc1 pb but solved it easily flashing root by odin in few seconds. Don't worry of scared people and keep your very nice efforts. I do a full charge with this rc2 and give report tonight maybe. Running it on miui galnet 1.10.12 (the more stable for me now). See you mate.
[Galaxy S II Original Android Development] joeyfong:
Thx @YaocH so much, looks like using daryrom tool 2 is better than cwmmanager.
[Galaxy S II Original Android Development] YaocH:
That's great, you're most welcome.

However, I experienced severe instability with rc2. Froze twice while using in a short span of 5mins when i updated from b8. Heptic feedback became on and off, sometimes strong and sometimes very weak. The brightness is also significantly lower. I'm using nightly 84. Do you have such issues also? And which version of CM7 are you using?

I should add that i do overclock to 1.6 and undervolt 100MHz at 800mV. Settings were stable on b8. I changed back to b8 based on the above reasons.
[Galaxy S II Original Android Development] ebliss:
I would suggest that you remove the overclocking and undervolting first and see if it still freezes.
[Galaxy S II Original Android Development] gokhanmoral:
check your undervolting script.

I think you did not experience any instability with rc1, right?

I only changed the lowest cpu voltage limit (from 800 to 650) and if you are using anything below 800 that is now effective.
[Galaxy S II Original Android Development] YaocH:
I did not change to rc1 because of the mentioned issues with the CWM recovery. It seems that it froze because I change the CPU governer to Ondemandx. I realised that it was causing the crash as it also froze on me when i changed back to b8. Have since changed back to ondemand and no issues.
[Galaxy S II Original Android Development] kwerdenker:
It's not like my settings weren't tested and stable with other kernels out there ;) But I can very well live with a slightly higher value on 200 if the 100 stepping gets used most if the time ^^

Sent from my secret moonbase via space carrier pidgeons
[Galaxy S II Original Android Development] poch_1421:
i'm on v1.6

what if i don't want to change my charging speed in v1.7? is there a setting menu for me to check it out?
[Galaxy S II Original Android Development] gokhanmoral:
if you don't change it it will not change by itself.

in fact, if you don't change anything everything will be stock.

of course there are won't-harm-anything type of changes such as i/o schedulers etc..
[Galaxy S II Original Android Development] chiggah:
What is a stable version for VillainROM 2.5 ?
[Galaxy S II Original Android Development] kairton:
What values ​​do you suggest for the voltages?

I am looking to voltages that help reduce battery consumption.
[Galaxy S II Original Android Development] gokhanmoral:
latest beta is stable enough

I'm going to upload beta3 and continue tomorrow..

I have changed the maximum frequency from 1600 to 1504 because some users reported that 1600MHz is not stable enough. I didn't want to add another step since that would require lots of other changes such as UV scripts.

BFQ-v2 is working and default now.

we are using SLQB just like in 1.6
[Galaxy S II Original Android Development] gokhanmoral:
I suggest stock voltages :)

if I suggest UV values, lots of people will try those settings and they will only complain, they will think that it is the kernel's fault, report bugs and make me sad.

If you suggest UV values, some people will try them and they will thank you if those values work for them, others will think they don't have decent sgs2s and they will be sad. :)

so...

use stock voltages :)

you'll get more by using 100MHz.
[Galaxy S II Original Android Development] Dark_Lord0122:
i got wake lock on LagFree using beta2 hope beta 3 fixes that ( i return it back to stock speeds)
[Galaxy S II Original Android Development] chiggah:
What sort of Android OS usage % are you getting with VR 2.5 ?

I'm getting about 40% with ninpo 2.0.5 with no applications open at all
[Galaxy S II Original Android Development] Остап:
I'm 11 hours since charged. Used 9% of battery. 0.81% per Hour. 925mv@100MHZ. ~ 95% of deep sleep.

Now i'm changing it to 850@100 and go to sleep. Tomorrow we will see if u was right ;)
[Galaxy S II Original Android Development] xinfinityoO:
can someone give a recommended u/v settings for smartassv2

i knw the voltage settngs dont work the same on all devices but would help as a guideline.

thanks
[Galaxy S II Original Android Development] dandroid13:
Here I use -100mV for each frequency. Very stable. ;)
[Galaxy S II Original Android Development] mocas:
Hello gokhanmoral, simply love your kernel, i have tried all your versions since the first one, for me in terms off battery vs performance its the best, but i´m having one problem with your kernel, since a few versions ago, my data conection is malfunction and wireless to, i think its kernel related because if i try ninphetamine kernel the problem its fixed. wen i switch betwin wireless and data conection the wireless only turns on again if i reboot the phone, dont know if you have any solution for this problem i would appreciate that a lot.

P.s I have been using oxed roms kh3 and now ki1 (original rom, ripped some samsung software and instaled jkay deluxe theme)

One again keep up the good work.

And thnks again.

Sorry for my bad english. ;)
[Galaxy S II Original Android Development] Silverbolt:
I have noticed the same thing with the wifi connection, but it doesn't happen all the time for me.

Every now and then my phone won't wake up. I have to pull the battery to restart.

Has anyone else had this happen?

I am using Criskelo v20.
[Galaxy S II Original Android Development] mocas:
Did you undervolt your processor? what kind of governor are you using?

you dont need to pull out the battery, just keep pressing start button and the phone will reboot.
[Galaxy S II Original Android Development] zikarus:
As for the malfunction of data connections try switching the airplane mode on and off once.

Helps on my device to reanimate data connections without the need to reboot...
[Galaxy S II Original Android Development] :
Flashed b3 in the middle of the night, tried to use brazilianwax, but it wouldn't wake from sleep, so switched to smartass and all back to normal with voltages posted before.

Bfq io seems pretty good and I am glad it is default now :D.

Let's see how my baby acts during the day after full charge (and battery calibration which works correct now :))

Maybe a suggestion, for release, remove new governors until we have proper time to test them and you have time to tune them, smartassv2 is damn good :).
[Galaxy S II Original Android Development] :
I am using these, my phone can handle lower, but I don't think it gives more power save, but opposite. So:

1504mhz: 1400 mV

1400mhz: 1300 mV

1200mhz: 1250 mV

1000mhz: 1150 mV

800mhz: 1050 mV

500mhz: 925 mV

200mhz: 900 mV

100mhz: 875 mV
[Galaxy S II Original Android Development] fostirop:
Hi all, using this Kernel first time. How do I understand if battery calibration has worked? I left it on charge all night, last night.

Thanks!!
[Galaxy S II Original Android Development] :
Check in /data/ if .battery-calibrated file is created using root explorer or similar
[Galaxy S II Original Android Development] Denwa:
I don't know what it is but something keeps breaking the abilty to install .tars via cwm or darky app. Maybe the newer recovery?

Reinstalling cwm app worked before but not this time. (I'm on 2.0b8).

:(

--sent from a faster than light sub-atomic particle via subspace communications tapped in binary by a finicky evil dragon with a broken wing hurtling through space while playing chess and sipping tea all while sitting in a rattan chair wondering why those dreams about being a bipedal huminoid seem so real...
[Galaxy S II Original Android Development] - Fabio -:
Thanks for your answer, I'll try to get that amazing battery life you got !!

I can hardly go over 3h screen on time...
[Galaxy S II Original Android Development] tomj777:
Interesting. I experienced similar (although it was easy to fix CWM). I am using Leormar75's ROM.. You?

BTW, Loved the sig.
[Galaxy S II Original Android Development] gokhanmoral:
800mV is too low anyway.

I know there are people who claim their device to be stable at even 775mV but it is just luck.

I changed a lot of code between beta8 and rc1 and if you are using your device at the edge of stability & instability now it may not be stable anymore @800mV.

I recommend you to use 1 step above the stable voltage level always.

I don't think it will effect the battery life more than 5 minutes.

and if anybody has enough time please test battery life with 100MHz@800mV powersave vs 100MHz@925mV powersave, lowest brightness and screen on always.

we will have an idea about the effect of undervolting.
[Galaxy S II Original Android Development] Denwa:
Thanks.

Leo 2.7.1 here as well. How did you fix the issue. I've reinstalled cwm app several times.

--sent from a faster than light sub-atomic particle via subspace communications tapped in binary by a finicky evil dragon with a broken wing hurtling through space while playing chess and sipping tea all while sitting in a rattan chair wondering why those dreams about being a bipedal huminoid seem so real...
[Galaxy S II Original Android Development] :
I just tested on LeoMar 2.7.1 and it works fine (tested all installations from b8, rc1, rc2). Stupd questions: are you rooted? Did you allow CWM superuser right? I know you probably did, just want to try to help as I really have no problems.
[Galaxy S II Original Android Development] tomj777:
As Netchip's observed, there was a symlink. I put the file into /etc (without testing that CWM was borked, so maybe I didn't have anything to fix after RC1).

To fix kernel flash with CWM Manager, no idea. Same with both versions 2.0 and 1.8
[Galaxy S II Original Android Development] gokhanmoral:
I was about to ask the same.. you should allow superuser access for cwmmanager. if you are not asked for it then you have a problem with root.

I removed root just because of that problem.

some kernels reinstalls root over and over and at some point your device lose root.

su binary and Superuser.apk is in the system but they do not work.

try to clear application data of Superuser and if it doesn't work use odin to flash cf-root.
[Galaxy S II Original Android Development] Galaxy_Fan:
CWM app doesn't work.

Just use darkyrom2 and everything is fine and nobody needs a cwm zip anymore
[Galaxy S II Original Android Development] coolfire:
I'd like to know that too. ;)
[Galaxy S II Original Android Development] Lennyuk:
Can someone (Or the OP) please upload a CWM flashable version of RC2 I don't have access to ODIN while at work.
[Galaxy S II Original Android Development] vnvman:
You don't need that: just download the darky rom tool from the market, then tap flash from sdcard and choose the .tar file. This worked for me and many others here :)
[Galaxy S II Original Android Development] tomj777:
Alas SU was showing within it's app log that root was being granted. Nonetheless, i instructed it to forget settings, reacquired root access for CWM, observed request for root and repeated symptoms. Something else is happening here. Any other tests I can run (from work, no ADB / Odin)?
[Galaxy S II Original Android Development] mikebike20:
Don't worry...i use darkyrom2 too and you don't need to wipe anything else. Deep sleep mode is ok too with this method so you can flash securely by this app.