yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] antt00:
My device have hang twice with beta 7

Touch room ki3

OndemandX 200 - 1200mhz

No uv

I/o vr

Once during editing some pic and once after I unlock my device.

Changing to sio to test further. And I have cleared all my cache.
[Galaxy S II Original Android Development] prinzhernan:
I know it says in the 1st post that it alerts supports 2.3.4 and .5 but can't I use this with 2.3.3?
[Galaxy S II Original Android Development] chadouming:
This has been said a lot of times, but if i remember well, it's no. Why are you not evolving to 2.3.4 or 2.3.5 ?
[Galaxy S II Original Android Development] lpsi2000:
Dude, get a new joke or keep your day job. This one is pretty lame right now.
[Galaxy S II Original Android Development] kalpik:
You sir, have outdone yourself! This is your new masterpiece! Smoothest kernel EVER! The appdrawer scrolling is super smooth, even with a live wallpaper!

Now, for the love of god, PLEASE backup your source :p

We don't want another masterpiece getting lost :D
[Galaxy S II Original Android Development] Denwa:
Gok, do I still need to delay init.d scripts with b7? I guess ill find out shortly. :)

--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] ebliss:
I actually flashed my wife's gs2 (on stock 2.3.3 still) with 1.8 and it is fine. Have not flash any betas on hers because she will kill me if I crash her phone and she doesn't want me to update hers to 2.3.4/2.3.5.
[Galaxy S II Original Android Development] aceofclubs:
You could set email notifications on xda web site for this thread only.
[Galaxy S II Original Android Development] PsychicSaint:
that will do.. thanks
[Galaxy S II Original Android Development] samjunctio:
Is auto calibration working in 2.0 ?
[Galaxy S II Original Android Development] adyscorpius:
Beta7 is so good, it actually masks the lags of MIUI with it...

Gok, you've done an awesome job.

And please, remove from OP that this isn't original work, cuz since v1.8, I havent even checked out the "Original Android Dev" section... Its that good... And I'm sure even if started out as not being original, the fact that Hacre is seeing this thread, only proves its worth every bit being called original...

Keep up the good work, but from the speed of your updates, don't burnout yourself... Take your breaks... :-)

Thanks...
[Galaxy S II Original Android Development] theory_87:
2.0b7 is good. B6 lag.on my device till I was force to use speedmod.. but b7 is back on track again...

Send from my Samsung Galaxy S II
[Galaxy S II Original Android Development] Henrywcy81:
increase charging speed is a great thing to me as i dun wanna wait for nearly 2.5hrs to fully charged the battery.

However,does this kernel drain the battery?i just want to find a kernel that can really save the juice
[Galaxy S II Original Android Development] frankcilo:
For me Ragemod has better battery consumption!:confused:
[Galaxy S II Original Android Development] adyscorpius:
Increased charging speed helps if you use a charger that has more than stock output...

Also, draining battery is tough on this kernel since long... Definitely a recommended kernel, though final consumption is on your usage style...
[Galaxy S II Original Android Development] dica:
Strange behavior, ghost charging

I have a strange behavior on 1.8 as you can see on the screenshot at the end of the graphic it seems like my battery livell is raising up without charging my phone, is it possible??
[Galaxy S II Original Android Development] lupos89:
Probably this appen because you have not calibrated the battery yet!
[Galaxy S II Original Android Development] dica:
I think siyah 1.8 does an automatic calibration when the battery livell reach 100%.
[Galaxy S II Original Android Development] gokhanmoral:
true. but the calibration is not completed as soon as the battery reaches 100% but it is completed once it is fully depleted. even then calibration is not 100% completed. you are advised to complete another full-to-empty cycle.
[Galaxy S II Original Android Development] ziTney:
You could use RSS feed right? And then put it on your homescreen :)

Sent from Samsung Galaxy S2 ->XDA Premium App
[Galaxy S II Original Android Development] :
It's broken in beta7 btw :)
[Galaxy S II Original Android Development] xtremeRadicalz:
what io scheduler is 1.8 using and what is sio
[Galaxy S II Original Android Development] fuzi1986:
Only as hint: CWM Recovery is still 5.0.2.3
[Galaxy S II Original Android Development] geoalexus:
I flashed 1.8 via CWM and everything it's ok except the fact that it wont accept any sim. It said: please insert sim card.

I flashed b7 and all things work so for the moment i'm gona stick to this one.

Any answer for the sim card problem on 1.8? I did all the othe things : clear cache, davilk, reboot twice...
[Galaxy S II Original Android Development] hrzeyni:
No problems at all with your kernels, currently @ b7. Keep up your great work :-)
[Galaxy S II Original Android Development] usul1685:
Annoying *click* sounds after going to 2.0b6/7

Hello all,

I was using v1.8 of this kernel for some time and and just loved it. Yesterday I decided to flash v2.0b6 (today I've switched to 2.0b7). I love this version too, and going to stick with it. One problem though, there are annoying *click* sounds (:confused:) when making a single tap on the screen. It just drives me crazy! Any ideas on how to make it stop?

Thanks.

I should have searched for the option prior to submitting a question here (I thought that the sounds are kernel related). I found the option for turning these sounds off in the display section in settings..

It seems an odd coincidence, that the *click* sounds appeared just after flashing the new kernel version..
[Galaxy S II Original Android Development] nofam:
Beta 7 won't wake from deep sleep for me - have tried a few different governors, but nothing helps . . Any ideas?
[Galaxy S II Original Android Development] antt00:
Just to feedback, since switching to sio, my device had not hang with the same settings.
[Galaxy S II Original Android Development] vnvman:
Are you uving? 800-825 mv is way too low for some devices, mine won't wake up unless i set it @850 mv, so i just keep 200mhz @850 mv as minimum frequence. I guess i just have some unlucky piece of hardware here :rolleyes:
[Galaxy S II Original Android Development] :
Also if I may suggest to open new thread when 2.0 is released as this one is too crowded :)
[Galaxy S II Original Android Development] tonysac:
If I understood correct one core is closing when phone is sleeping? If yes with this way we save some battery, so isn't necessary to set a sleep profile?

Right now I'm using nofrills with 100-1400, ondemand/sio with no problem..but still I'm searching for the ultimate smoothness combination..even if with above combination, phone is smooth enough lol

Save water..drink beer...
[Galaxy S II Original Android Development] BoneMo:
Go to Settings>Sound and there should be something like Audible Selection+checkbox

i hope that that´s the right one
[Galaxy S II Original Android Development] cattleprod:
A cow sat on it, now it can't get up anymore :)
[Galaxy S II Original Android Development] skimminstones:
trying to search through this thread but all thats coming up in the results is petty arguments making the search function useless so im going to have to ask instead.

Ive read some people having issues with the clock losing time but my clock widget every now and then is just freezing dead, have tried a few different widgets and happens on all of them now. Thinking it may just be this kernel ive tried a different one, (abyss), but its freezing on that too. Im wondering if its something to do with the .14 builds as it doesnt happen if i change back to a .7 build kernel. Trouble is my battery life is so much better on the .14 builds so id rather not change.

Can anyone suggest something?
[Galaxy S II Original Android Development] richyy74:
I was testing siyah vs. stock ki3 and ki8 in the past days. B7 stays for me for the time being. Much quicker than previous versions or stock. Newer toolchain,as I have seen, really brought something.
[Galaxy S II Original Android Development] kisstom:
Problem with wifi. It's freezes when on , of and on again (beta7)
[Galaxy S II Original Android Development] yoplaboum:
Big problem with wifi..
[Galaxy S II Original Android Development] dtekkt:
I have no Problem with Wifi, using Leomar 2.7.1, OndemandX, sio, 100-1200 and -100mV uV

BUT: battery calibration isn't working (and didn't in b6) :D
[Galaxy S II Original Android Development] Denwa:
No wifi issues here.

Did have daemon controller crash on me. Had to reinstall oc daemon. Never had that occur before. Not sure if that if that kernel is related it not.

Is there any way to lower minimum brightness? Have it as low as possible and it is still blinding at night.

--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] Skyline92:
Seems to be related to your Rom. Look @ the post above yours :cool:

Hint: Same Rom :eek:
[Galaxy S II Original Android Development] Nuja:
Can we use juwe's ram optimisation script or you already added ram tweaks ?

thx
[Galaxy S II Original Android Development] JJEgan:
NO CSC wrong CSC ???

jje
[Galaxy S II Original Android Development] nishadh:
2.0 b7 was giving me problems. It stayed awake @ 200 MHZ more than the deep sleep and the battery started draining like crazy. And the battery status showed a solid blue in the awake row throughout.

Also wifi was having issues in remaining connected. I do not play with overclocking and undervolting and all that. My settings were simple with no frills 1200 to 200 mhz, smartassv2 and deadline.

So i flashed back to 1.8 and everything was back to way it should be.
[Galaxy S II Original Android Development] mikebike20:
Hey gokhan...i use your 2.07b on galnet 1.10.14v2, sheduler on sio 100-1000 and it had never been so smoothly than now. All seems to be fine and rocking. A little annoying thing is the android usb connected draw still in status bar even when sgs2 is diconnected. Concerning battery drain it's too early but keep your efforts mate. It sounds really good...
[Galaxy S II Original Android Development] spline1:
The SmartassV2 is very choppy. In adw Launcher ex is it stuttering with slowly scrolling.

With ondemand it is better
[Galaxy S II Original Android Development] d3l1:
Just had the weirdest reboot ever:

When exiting K9 Mail, the phone shut itself off, rebooted and hung at the first bootlogo (yellow triangle screen) for about a minute until the animation kicked in. It then started the phone and at the bottom of the screen I could read "Safe Mode", TW was the launcher again with an empty homescreen. I pressed "settings" to look around when I suddenly saw the boot animation again (no logo, just instantly the animation) and I was back in the phone the way it's supposed to be.

Kernel (see sig), o/c daemon settings: screen off 100-200 conservative, screen on 200-1200 ondemand, virtous_oc.

any ideas what happened here? nothing seems to be damaged or broken, still this behaviour is weird and I've never seen it before.
[Galaxy S II Original Android Development] lowrider_05:
I used the kernel thru all 2.0 betas and musst say with the 2.0b7 my battery is draining a little less than before and i use 100 - 1.6 with ondemand and V/R on galnet MIUI

this is just for information and a big THX for your work
[Galaxy S II Original Android Development] vnvman:
To my knowledge a sleep profile isn't necessary on any kernel, regardless what some people say: the cpu will be completely power collapsed when screen is off (deep sleep) and there aren't tasks running. Basic processes and sync daemons won't make the kernel ramp up higher than 100/200 mhz, depending on how you set the minimum frequence. All i do is triggering the powersave governor when listening some music for a long while (keeping the screen off), so that even if i turn on the screen for a second to skip a song or a playlist i won't waste some juice making the cpu ramp up for such a little task. That's the way i've been running all of the kernels i used since i got my first android phone, about a year and a half ago, and i'm actually pretty satisfied about this method since it has proven to be the best one for battery saving purposes (in my own experience at least) and it's also very simple to use. Just my 2 cents ;)
[Galaxy S II Original Android Development] rodries:
Hi gokhan

I've noticed that siyah kernel hasn't /proc/last_kmsg, so if we have a freeze o reboot which info is useful to you?

I think with this file you can find the bugs easily
[Galaxy S II Original Android Development] jmblazquezh:
One question about this. It is assumed that the maximum mV calibrates available. Let me explain. My battery used to calibrate the batterycalibration app. This applicaction does not always show the same mV. Sometimes it is 4196 mV, 4198 mV sometimes, sometimes they are 4200 mV. How many mV autocalibrates the battery?

Regards.
[Galaxy S II Original Android Development] rauschkugl:
Finally my battery is really great on ki3 rom with beta 7. Please keep it like that. No issues so far.

Sent from my GT-I9100
[Galaxy S II Original Android Development] boshot:
donation done.

3WW46389BF898414W
[Galaxy S II Original Android Development] pockobg:
Battery is great ot b7, but is there a way to set the autobrightness levels like on MIUI
[Galaxy S II Original Android Development] d3l1:
I just tried to install daemon controller on our second phone, downloaded leomars kitchen app, installed it and marked the oc daemon for installation. now when I press "apply" it tells me that my ROM isn't leomar's. It worked on the first device, or am I doing something wrong? How do I get oc daemon installed correctly? thanks in advance!

(feeling really stupid atm :) )

EDIT: It worked using the "old" kitchen app I had on my sdcard. seems like the new one (10/12/2011) checks the ROM.
[Galaxy S II Original Android Development] joeyfong:
I am running CM7, how do I flash this kernel? Can be flashed via ROM manager?
[Galaxy S II Original Android Development] the^one123:
my facts

hi guys.

For me beta7 is running better than all the versions before.

Here are the facts.

Rom: LeoMar 2.7.1

O/C: O/C Daemon Controller

UV: init.d script

UV Parameters:

100MHZ @ 825mv

200MHZ @ 850mv

500MHZ @ 875mv

800MHZ @ 975mv

1000MHZ @ 1075mv

1200MHZ @ 1175mv

1400MHZ @ 1275mv

1600MHZ @ 1400mv

OC Parameters:

Wake Profile: 200 - 1200 MHZ @ ondemand

Sleep Profile: 100 - 200 MHZ @ ondemand

Scheduler: vr

Until beta6 switching beetween screens was lagging on GoLauncher.

With these settings it runs very smooth. No Wakeup Problem or other mistakes.

On GoLauncher with Live Background it runs smoother than without? Why????

Can i change the scheduler with init.d script? I dont want to run both O/C Daemon and no-frills or Voltage Control.

theone
[Galaxy S II Original Android Development] tolis626:
For your issue with GoLauncher,go to menu->preferences->advanced and disable high quality scrolling.Solved it for me as I was facing the same issue.I knew my phone wasn't THAT much abnormal. :p
[Galaxy S II Original Android Development] rauschkugl:
Yes. You can download the zip and flash with rommanager. Don’t forget to wipe dalvik afterwards.

Sent from my GT-I9100
[Galaxy S II Original Android Development] Zanr Zij:
I think this is voltage bug: I can decrease voltage 100MHz - 800MHz @ 600mv and run stable. Battery life no change, maybe drain faster. When I increase to 750mv, phone freeze!

Normal my S2 stable volt setting:

Clock 100 200 500 800 1000 1200

Volt 775 800 825 950 1050 1150

Sent from my GT-I9100
[Galaxy S II Original Android Development] tolis626:
Already covered many many many MAAANY times in this thread.Search ain't one of your talents,eh? :rolleyes:

There is no bug.The regulator(The part of the phone that feeds the circuits with power) can't give 600μV,it's too low.There is a hardware limit.Even if you set 600μV succesfully,it's not really 600μV.It automatically sets a higher value,accepted by the regulator,which may be stock voltage.750μV is the real deal,that's why it freezes your phone. :)

Gohkan,for me beta7 is even worse than beta6.At least beta6 had normal battery drain.Now,with beta7,my charger got full of dust and my spare battery is useless.I demand that you pay me for rendering my spare battery useless! :p

Seriously,with beta7 phone runs like a dream.Smooth,fast,battery lasts forever(Please leave calibration broken :p ) and,most importantly,for the first time in my GS2's life,it's 100% stable.

I only have one question.Besides the screen off profile in ondemandx(and the "x" obviously :p ),what are the differences between ondemand and ondemandx?Because with ondemand it's relatively smooth all the time,but with ondemandx it lags for some seconds and then it becomes uber-smooth.I demand an explanation! :p
[Galaxy S II Original Android Development] Zanr Zij:
If I can set 600mv sucessfully, but the hardware not compatible, it mean that is voltage setting bug of kerrnel. And "automatically sets a higher value" mean exactly which value? 775mv? 1250mv? Do you know? Who know?

Sent from my GT-I9100
[Galaxy S II Original Android Development] landerson07:
I'm on checkrom 5.5 and cannot install anything from kitchenpro? Either with darkyrom, kitchen or cwm? It says it installs but then it's not there? No oc daemon, camera mods etc

Any ideas?

Ps I'm on beta 7
[Galaxy S II Original Android Development] roymustafa:
Hi everyone...Leomar + Beta 7...I am very sad...it is so smooth and fast that i missed the word "slow"...:p You are great Gokhan...
[Galaxy S II Original Android Development] Bene2k11:
It's not a bug, it's a feature. It makes sure that you don't set your voltage too low. And it sets voltage to the stock one then. That's why you should lower voltages in short steps, until your phone gets unstable. Then raise it once to get a stable feel. And so you've got the lowest voltage your phone is capable of.

With best regards from my ExynosROM-powered SGS2 always running the newest version of Siyah-Kernel.
[Galaxy S II Original Android Development] Elistheman:
@gokhanmoral

is it possible to increase the voltage to the usb port when using OTG?

for like small ssd drives? they require 5 volts and i know android can only spare 4 using the otg feature.
[Galaxy S II Original Android Development] Orka82:
The battery puts out 3.7V.
[Galaxy S II Original Android Development] Elistheman:
yeah but i heard the software limit is 4..... i can put some diy work to operate the phone using 5 volts so i can use my ssd drive not a big problem but the software prevents me from doing so
[Galaxy S II Original Android Development] Zanr Zij:
Tks but I need Gokhan confirm :)
[Galaxy S II Original Android Development] gokhanmoral:
the voltage level is already 5V on the usb port but the current output is limited to 500mA.

that may not be enough for ssd drives. you need to supply extra power to operate.
[Galaxy S II Original Android Development] gokhanmoral:
I confirm :P

there are some limitations on power regulator.

and before AndreiLux has found out the exact limitation values somebody claimed that he could run his phone @600mV stable. therefore I lowered the min voltage value from 800 to 600.

but I see no point of using anything lower than 800mV.

instead of playing with regulator defaults I will revert that change and make the min 800mV again.
[Galaxy S II Original Android Development] Elistheman:
@gokhanmoral

im asking this the third time.....

if you can please include NTFS external hardrive mount support..... i mean i cant mount NTFS external hardrive via OTG even with the scripts someone here on xda made

i can only do this with stock kernel

if you can please port this feature....
[Galaxy S II Original Android Development] milan188:
I have had lots of freezes since i flashed the beta 7 kernal.

First I flashed the kernal wiped the dalvich flashed superuser then rebooted and i get lots of freezes when i try to access root apps like Titanium Backup.
[Galaxy S II Original Android Development] paira:
@gokhanmoral

could put this governor ........

InteractiveX

? is better than saving battery Smartassv2?? or SavagedZen??
[Galaxy S II Original Android Development] richyy74:
I have a strange thing which appeared with b7 can anyone please check and confirm or explain?

If fast dormancy is disabled after wake up there is no data connection until I somehow /changing apn or flight mode/ disable and re enable mobile data.

With fast dormancy enabled all is as it should be.

XWKI8+XXKI3 MODEM

Any thoughts?
[Galaxy S II Original Android Development] jeffojeff:
I'm using KI4 as modem and I didn't encounter that.
[Galaxy S II Original Android Development] gokhanmoral:
there are people who can mount ntfs drives with fuse + ntfs-3g by using this kernel.

you may need to modify the script.

basically, you need to insmod fuse and use ntfs-3g

and fuse.ko is already in /lib/modules

I do not use OTG and I do not have a usb cable to try it.

even if you ask it fourth time I cannot help you about this.
[Galaxy S II Original Android Development] Elistheman:
i guess i will try again.... it didnt work on 1.8....
[Galaxy S II Original Android Development] AndreiLux:
Yep. There are 3 limitations:

1) the regulator driver limitation which is set to 650mV on the voltage converter rail the CPU cores are desigated to (and that is probably a physical limitation and nobody should touch those values).

2) the kernel minimum voltage initialization value of that converter which is also set to 650mV.

3) the system interface for undervolting which had a soft-lower limit of 600mV.

The thing is, 1) and 2) overwrite any value <650mV set by the system interface and set it to the default value. That's why it's stable. If you set it to 650 it will crash up until 775 for some lucky people, and 800/825mV for most people.

Also the phone hasn't got enough power to feed into an SSD for example. SSDs still draw 2.5-3W under load, and even if the phone can deliver the voltage of 5V with step-up converters, it can't deliver the amperage or power for both the HD and the phone itself... I can drain the battery in 2 hours under full power, that's about 3W consumption considering the 6.1Wh battery, and about 1A of current. So you'd have possible peak draws of 2A, sorry, but not happening on a phone.

Doesn't matter.
[Galaxy S II Original Android Development] Zanr Zij:
That is! Set 600mv sucessfully but not effect + you see no point of using lower than 800mv :). You should remove lower than 750mv :) and it will have none this type of bug/feature :D
[Galaxy S II Original Android Development] CA3iR0:
CM Nightly #84 + Siyah v2.0b7 + XXKG5 = maximum perfection!
[Galaxy S II Original Android Development] cobhc:
Sorry to go OT here, but why specifically the XXKG5 modem? Unless I missed something and it's a lot better than any other.
[Galaxy S II Original Android Development] gokhanmoral:
I cannot agree more.

XXKG5 is still my all-time favorite.

I don't like the new overscroll effect on latest roms and I feel that XXKG5 is much more battery efficient.
[Galaxy S II Original Android Development] theory_87:
Possible at 750mv? My phone is running at 100MHz @ 775mv rock stable.

Send from my Samsung Galaxy S II
[Galaxy S II Original Android Development] gokhanmoral:
by the way, I am not talking about the modem but the ROM.

I think modem preference depends on the region.

I like KG2 most for Vodafone Turkey + my wifi routers.
[Galaxy S II Original Android Development] the^one123:
Hey tolis you are right with this. thx guy now it's smooth like hell :-)

what settings are you using for oc your cpu ?

Thx for that

theone