yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] BoneMo:
WOW

v2.1 final

updated CWM recovery to 5.0.2.7 and added back soft-key support (thanks to mustaka@xda for the back-key modification. sagol hocam…)

reverted 500MHz deep-sleep enter change for stability purposes

bus frequency modification

Coming soon…
[Galaxy S II Original Android Development] JPxM0Dz:
Great job on RC3, not a big fan of Quadrant, but do use it to test from one kernal to the next. Big improvement over RC1 and RC2
[Galaxy S II Original Android Development] minidou-77:
Can't wait the bus frequency modification ^^
[Galaxy S II Original Android Development] _cummoo:
2.1 FINAL

Can't believe it - the Final is up !!! :D :D
[Galaxy S II Original Android Development] gokhanmoral:
some people think that modifying the sharpness and color tuning makes the images artificial.

I will make it optional in the next release and you will be able to use either speedmod values or change them to your taste.

also, I removed 500MHz deep-sleep entering frequency in the final.

I tested both setting it to 500MHz directly or lowering the 800MHz (to have the same s value as the recommended freq) to 500MHz dynamically before entering to deep-sleep.

first one gives SOD and the second one (strangely) sometimes stuck on 500MHz for the forth level which was supposed to be 800MHz.

anyway.. I will leave it to the next version.

as for MIUI tetherin problem: can anybody tell me a version which didn't have that problem?

that will help me a lot to identify the problem.
[Galaxy S II Original Android Development] YaocH:
I'm not striving to achieve the best benchmark 24/7. Just a gauge of the powress of the latest development of siyahkernel. Everyone wants to have their cake and eat it, but battery life and pure power don't go hand in hand. Battery life is the ultimate holy grail for all mobile devices and its why CPU governors can be changed on the fly together with max cpu frequencies, so that ultimate performance can be called upon as and when needed. If it bothers you so much, I can always add that I'm undervolting for 24/7 use. 25MHz @ 800mV and cap the max frequency to 1200Mhz. Do you then need me to post a picture of my battery usage graph so as to show that I'm not detracting from the original purpose of the development of this kernel??? I just want to have my cake and eat it, whenever I feel like it.
[Galaxy S II Original Android Development] zorkis:
I wonder how you are able to update from Cyanogenmod old nightly to the latest nightly with siyahkernel. for me it's just getting me to first boot loop. I couldn't get in recovery or download mode. Don't wanna do it again
[Galaxy S II Original Android Development] pappschlumpf:
As with the other 500 MHz versions no return from sleep with rc3 using ondemandx.
[Galaxy S II Original Android Development] silverio28:
Gokhanmoral

what is the best governor to save battery?

In version 2.2 you will try to improve battery life or will you try again record-breaking performance?
[Galaxy S II Original Android Development] YaocH:
Make sure that you flash the update twice before flashing the siyahkernel and then whatever else you need before rebooting. This has worked consistently for me for the past 10+ nightlies. Hope this helps.
[Galaxy S II Original Android Development] tvhak:
tested 2,1rc3. but i am sorry to say that. i had with 2.1rc 1 and 2 less battery drain.

hoping final will be better for my phone. otherway i just stick with 2.1rc2 because that one is great
[Galaxy S II Original Android Development] :
I've never had a single problem with 500mhz and deepsleep, is this because of differences between processors or what? Strange, oO

Too bad that it doesn´t seem to work for everybody and that you had to disable it. This way i wont be able to flash any newer versions of the kernel without it, because i think it´s a great feature.
[Galaxy S II Original Android Development] YaocH:
Same here (10 char)
[Galaxy S II Original Android Development] DobermanS:
@ Gokhanmoral

"as for MIUI tetherin problem: can anybody tell me a version which didn't have that problem?that will help me a lot to identify the problem."

sadly but no,i personally jumped over betas,and haven't always checked :(

i have made logcat on rc2 when i was able to ping out by ip,hope it give some help.

any way,you can be sure,with your kernel miui works best all the way from 2.0 :thumbs up:
[Galaxy S II Original Android Development] squall_kay:
video playback

using siyah rc3 with galnet miui 1.10.28. noticed unsmooth HD video playback?

anyone encountered same prob?

kernel or ROM?

in previous ROM version, didnt encountered this prob.
[Galaxy S II Original Android Development] tvhak:
i have seen this problem more. and i have it to. think its kernel. because i have it since i use siyah kernel.

but i like siyah so i leave it like this....
[Galaxy S II Original Android Development] aegeuss:
Gökhan,

Please do it optional, if you will because these settings break the Voodoo Screen Tuning App, found in the market, written and developed by Supercurio, which gives better results for out displays. It's one of the reasons I don't use Speedmod kernel although it's a perfect one.

By the way, SOD problem in RC2 can be overcome via a small increase in the voltage for 500, 200 and 100 mhz's undervolting settings.

Eline sağlık again ;)
[Galaxy S II Original Android Development] YaocH:
Yeap me too. I used to be able to do 1080p hd playback on youtube smoothly but now only 720p. I dont know if it's something to do with android 2.3.7 on cm7.1 or what coz after i updated to 2.3.4 and 2.3.5 on stock samsung roms i couldnt choose other options besides 480p but on 2.3.3 stock samsung rom, i could playback smoothly
[Galaxy S II Original Android Development] :
You people and your damned undervolting! Just leave the values on stock and Gokahn wouldn't have that many problems with the Kernel.

If you undervolt, don't report any ****ing "bugs" in this thread. Be happy that Gokhan develops this awesome kernel and stop destroying everything with your ****ing uv!
[Galaxy S II Original Android Development] drziddo:
Please gokhanmoral, enable back the batt accurate mode. I was loving the numbers inside the batt icon. Thanks in advance.

---------- Post added at 05:44 PM ---------- Previous post was at 05:43 PM ----------

+1!

Agreed 101%.
[Galaxy S II Original Android Development] Molitro:
I also never had any problems coming from deep sleep neither in the beta that used 500 MHz nor in rc3.
[Galaxy S II Original Android Development] pac213:
Happens to me too. WIll revert to RC2.
[Galaxy S II Original Android Development] CA3iR0:
You have to flash it twice. ALWAYS!
[Galaxy S II Original Android Development] :
I don't...
[Galaxy S II Original Android Development] CA3iR0:
And here! :confused:
[Galaxy S II Original Android Development] olifee:
Thanks gokhanmoral for another awesome release :).

I am really looking forward to final ;-).

My dual-headed ftdi-adapter (integrated hub, two ftdi-usb-to-serial converters inside) is still not working with the same device-descriptor-errors I already mentioned before (for reference: http://pastebin.com/jVb3Bmbi on mobile and http://pastebin.com/ZqM1jrBt on desktop, a single 4-port-hub in between for more power).

However, it did not even work in 1.8, and I do not need it right now, so only look into this in case you are bored ;-).

BTW: ids_arm: 13 hpm_class: 15. Work's rocking stable on stock frequencies, and battery runtime is ok for me, so I stay with that for now ^^.
[Galaxy S II Original Android Development] psychoid:
am i missing something here?what kernel got to do with batt icon ?
[Galaxy S II Original Android Development] CA3iR0:
On CM Nightly? Impossible. It will only flash correctly on the second attempt.
[Galaxy S II Original Android Development] YaocH:
Don't wanna risk it
[Galaxy S II Original Android Development] cedric123:
[Can you add the mDNIe features (stock included in samsung sources then we will be able to use supercurios voodoo app:)
[Galaxy S II Original Android Development] CA3iR0:
That's why the first flash is so fast. The second takes a lot more time to finish!
[Galaxy S II Original Android Development] kokoskokis544:
cwm

i hope the new recovery also has the function to select using the power button. i think is much better and reliable using the power button as i believe most of u noticed that if u dont press the home button quickly it selects twice..also the soft menu button in a cf-root kernel was modified to go downwards instead of the other way round..just suggesting if u can include those.. thanks
[Galaxy S II Original Android Development] fenomeno83:
Who said that wake from sleep doesn't work, it's better that post voltages..maybe 500mhz related voltage is too much low
[Galaxy S II Original Android Development] Henrywcy81:
Can't wait for the final version!!

hope that i can update my phone when i wake up.

gd nite guys
[Galaxy S II Original Android Development] tomdot:
Sorry for the cross post with Villain thread.

I really need some help. It appears that no matter what I do, this is about the max battery I can realistically achieve on a regular basis. It's mind numbing that many gents are getting 5+hours screen on time.

Country: Hong Kong (HSPA H+/3G always active)

Dormance: Enable/Disable (no difference)

Display: auto with near black wallpaper

ROM: Villain 3.0 (KI3)

Modem: KI1/KH3/KI4 (current)

Kernel:ninpo 2.0.5/siyah 2.1rc3 with safe UV using ondemand/lulzactive (current) governor

I have never been able to pass 2h display time which I understand to be the biggest battery drain. Neither do I have any wake lock problems.

Any help appreciated! Thanks all!
[Galaxy S II Original Android Development] jdmcivic:
the secret to having better display on times is to use wifi instead of 3g data. 3g data sucks battery like mad.
[Galaxy S II Original Android Development] YaocH:
I would try to do a nandroid backup before completely wiping the device. factory reset, wipe cache partition and delvik cache before restoring the backup. If this still does not solve the issue, then i suggest doing a titanium backup and then clean wipe and reinstall and restore your apps without system data. I had battery issues too when i first switched over to cm7.1 and the second method managed to solve it. It will also be good to know if you just switched over to villianrom? and if you came from another custom or stock samsung rom?
[Galaxy S II Original Android Development] Entropy512:
The basic rule is - if the device cannot run at 800 MHz with the voltage settings for 500, it'll crash.

This isn't exclusively an undervolting problem - it'll happen at stock voltages if the device isn't able to undervolt 800 to the stock voltage of 500.

The ideal thing would be to figure out a way to do the clock-locking right before the regulators go away and unlock the clocks once the regulators are back - PM_SUSPEND_PREPARE is too soon, PM_POST_SUSPEND is too late.

The other option would be to lock the voltages to that for 800 MHz and continue to allow clock transitions. It might give some additional hints as to what's going on in the suspend period - like whether the CPU is spinning like crazy in a loop during that period or not.
[Galaxy S II Original Android Development] chadouming:
This is not kernel related, but rom related. If you go in setting, about phone, status, you will have a precise battery pct.
[Galaxy S II Original Android Development] dragon546:
Hey Guys in the hope of cleaning the thread so that those who are helping Gokhan improve his kernel can post here. Please can you post issues and question in the Q&A thread I have created with gokhan permission. it is still quite rough, I hope the community would assist me in resolving new adopters and experience users who may questions about the kernel. Currently is just has slightly edited version on whats on the first 2nd post.

I prefer not see people lose their rag because a new adopter has a question about the kernel.

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

Many Thanks
[Galaxy S II Original Android Development] Devhux:
I am not sure if this is kernel related but vibration isn't working for me anymore (using KI4 rom with this kernel).

Vibrate icon is showing, i've enabled haptic feedback, and ice even tried test mode and nothing works. Any ideas?
[Galaxy S II Original Android Development] tomdot:
@YaocH

I tend to believe it could be my apps. I have already wiped/factory reset, wipe dalvik, cache, data and system before reinstalling Villain 3.0

Each and every time I use titanium backup and restore WITH data. This could very well be the problem but how do i prevent that from happening again!?

Titanium has been a trusted partner and an enabler of intra-day ROM changes... is there a better way of doing this?
[Galaxy S II Original Android Development] DobermanS:
Great idea ! IMHO you should add in title of this thread so ppl know right away,

otherwise any one who didn't read your post will continue to post here...
[Galaxy S II Original Android Development] incubus_fr:
So, if questions and issues go to the new thread, what will be on topic here?
[Galaxy S II Original Android Development] nikzDHD:
Development issues I guess :)
[Galaxy S II Original Android Development] gokhanmoral:
I think questions about beta versions should go to the new thread which will decrease the traffic on this thread drastically.

we always have beta versions anyway :)
[Galaxy S II Original Android Development] pixiebob:
edit: error
[Galaxy S II Original Android Development] dragon546:
Dev issues and analysis from those like Andreilux and Entropy, Olifee and others should stay in this thread as to Benchmarking results I will leave that to you guys. I just feel sometimes vital information gets lost in here. Especially like the AOS discussions were intertwined with user issues. In other words if you have a problem after you flashed the kernel post in Q&A if you could reproduce the problem and there are loads of people getting the same thing then maybe and only after permission from gokhan the issue can be promoted here.
[Galaxy S II Original Android Development] incubus_fr:
Il fully agree on questions, just wanted to know which issue should be posted here. I mean it's not always easy for everyone to know if the issue is in front or behind the screen ;-)

Gokhan, maybe you want to tell us which kind of post is helpful for you here?
[Galaxy S II Original Android Development] dragon546:
Well I have seen post about people battery life depleting I mean have they done any troubleshooting themselves? is it the rom or an app stuff like this should go Q&A thread.

Or I have been guilty of this one when a new kernel beta is released not going to right place to read the changelogs.

Just a couple of examples.

On the flip side more complex stuff like the usb OTG stuff and AOS stuff should go here where there has been analysis.
[Galaxy S II Original Android Development] gokhanmoral:
development related posts are welcomed here always.

this thread is in "android development". although we are not in the "original" part ;)

by the way, is there any other device section with original and non-original android development difference?

let's make the same difference... if you have something original to say, say it here :)

I will follow both threads, of course.

but I think the other thread will help me a lot to save time.
[Galaxy S II Original Android Development] dragon546:
I know the transition will be difficult at first and my knowledge is limited to my day today rom galnetMIUI and some of the Samsung Stock Rom. I hope that more experience users will help me to help on that thread gokhan can focus on his stuff.

CM has done this with some success, I hope the same can be done with the new thread.
[Galaxy S II Original Android Development] incubus_fr:
To be honest I like your action and understand the need for it.

I just wanted to make sure it's clear for everyone ;-)
[Galaxy S II Original Android Development] AndreiLux:
The other thread should be more specified as to what belongs there and what not; I would just suggest kicking all bug-reports, testing-reports, and questions about functionality in there, and to be very clear about that. The remaining rest should remain here.

And the whole FAQ should be rewritten then if one wants to do it properly. And I mean really thoroughly because there's always the same questions coming again and again. I had the same idea a while ago but didn't want to impose myself, but I'm willing to help. Call it something like a book of knowledge. But dragon546 already started it so I don't know of his opinion or Gökhan's.
[Galaxy S II Original Android Development] kapa75:
Hi gokhan :)

With your kernel, my battery lasts 2 days, it's awesome!

will dual boot be included in the next version?

Thank u :)
[Galaxy S II Original Android Development] dragon546:
It's still rough stage and people are already posting on this, I will try and tidy up the FAQ I have changed a few things. I am still learning intricacies of the kernel as well as how roms interact with it. I have only had my SGS 2 since Sept 1. I really appreciate everyone input on there.

How did this came about actually was seeing frustration more established users of this kernel getting mad on new and existing user queries. I PM'ed Gokhan and got his approval.

---------- Post added at 07:26 PM ---------- Previous post was at 07:25 PM ----------

Please post this in the Q & A Thread here:

http://xdaforums.com/showthread.php?t=1325831
[Galaxy S II Original Android Development] AndreiLux:
My point was if we're doing it then we should do it correctly, and if you want I can write a thorough guide on it and ask it to be shoved underneath your first post, I say this because I think it's already started off to a bad start quality wise. Most of the feature-list, the FAQ are all outdated an unspecific.
[Galaxy S II Original Android Development] chadouming:
We should make the faq guide at the beggining of the new thread. But doing a faq with frequently asked question on a 800 pages thread will be a pain in the ass. I suggest that we should, a few person , take some time together ( maybe on an irc or w/e ) to get the most asked question out of this and make a good faq. This could help a lot of user. And report person asking the question who are in the frequently asked ^^

Operation iron fist :D
[Galaxy S II Original Android Development] dragon546:
Understood Andrei I would be delighted if you can do this so I can provide a much more updated support FAQ for Siyah. I also do really appreciate your efforts in your work.

EDIT: I have put a note in the other thread about FAQ being outaded and a new revision to follow.
[Galaxy S II Original Android Development] eiraku:
Or we can start a new thread for v2.1 and start the saparate Dev/Q&A thread thing from that point on. That way, the FAQ can be re-written cleanly and we can start from scratch.

Which makes sense seeing that 2.1 final is around the corner. In the meantime, this thread can be closed up.

And the new thread needs to CLEARLY be labelled as a Dev thread.

Plus I think that SERIOUS, TECHNICAL questions/comments that CAN contribute to the actual development of the kernel (i.e. "proper" bug reports with logcat logs or someting VS mindless derivatives of "oh hlap mai phone rebooted" questions and feature requests) SHOULD be kept here for Gok's perusal.

Although I'll leave it to the thread watchers (the more senior guys hovering in here) discretion weather a question is something that deserves a Gok's attention or should be replied with a terse "QA thread please".

Or something, IMHO anyway.

I'll support anything to make sure the plebs don't drive another dev away. For the love of God, please.
[Galaxy S II Original Android Development] AndreiLux:
Basically if I'm going to do it, I'll rewrite the whole sha-bam including all the parts in your post, but at the same time I don't want to overshadow you as the OP, since you took the initiative and are also actually answering most of the questions there as it seems, I don't have the patience to deal with all the plebes myself :p . But in my AOS thread I just bombarded them with enough information clear enough that they would just shut up or not know what to ask, and it's been clear of stupid questions until now. So if you still want to give the green-light under that case, that then I'll start it.

Edit: eiraku's idea is also good.
[Galaxy S II Original Android Development] dragon546:
Andrei my pleasure go for it. Once its done and you are happy with it I will amend the posts. Thanks I cannot thank anymore limited to 5 a day. I have to deal with Plebes everyday that's what you get for doing Desktop Support, hence my bad documentation techniques lol
[Galaxy S II Original Android Development] jdmcivic:
alright. i am able to reproduce this auto revert to stock UV values effect.

i even had my init.d scripts on time delay after boot.

to reproduce this auto reverting to stock UV values. all the phone needs is to go into deep sleep and voila.

tested this many times. did a manual UV via gscript, all okay when echoed out the values. values stayed put while having screen on all the time. the moment i switch off my screen and let the phone go into deep sleep. stock values come back!

is this a feature gokhan implemented so as not to have any SOD?
[Galaxy S II Original Android Development] mdaaddic:
Can you tell us your settings please? Do you uc/oc?
[Galaxy S II Original Android Development] gokhanmoral:
I cannot reproduce it.

of course it is not something I did on purpose and I cannot think of a reason which can revert your UV values back to stock.

are you on rc3 or rc2?
[Galaxy S II Original Android Development] dragon546:
He is using RC3 he replied to the Q&A thread
[Galaxy S II Original Android Development] snakefreak:
Can user request features? ;-) like to have dvbt support in kernel+ a few modules.
[Galaxy S II Original Android Development] AndreiLux:
About the FAQ/etc: screw it, I'll do it on a later date, got some other stuff to do now. Asked a mod if it's possible to shove a post underneath the OP so I don't have to bother you with it and I'll get to edit it myself if needed.
[Galaxy S II Original Android Development] jdmcivic:
alright good news. i can confirm it is not kernel related. 100% its rom related. am on gingermod 0.7

i flashed back 2.0 and did the test. same results. damn im gonna change rom tomorrow.
[Galaxy S II Original Android Development] olifee:
I guess this counts as dev-releated and thus belongs in this thread ;-).

Well, I actually tried compiling DVB-T modules back with 1.8 sources.

The modules were actually fine. A major problem, however, was loading the correct firmware (most DVB-T-devices need to be loaded with a firmware to get them working).

Android is missing the firmware-helper tools which are included in desktop-linux-distributions (I think udev handles the job there with some helper-stuff).

I loaded the firmware manually using kernel sysfs (found instructions on stackoverflow somewhere) but it did not help:

After the firmware was loaded, the USB-hub should do something like unplugging and replugging the DVB-T-stick. As it seems, this did not work / might not be supported with our USB-host-controller (or it's driver).

Loading a firmware on a desktop-machine and hotplugging to the phone (stick powered by hub the whole time) also failed (but I actually never tried this with two desktops, so I do not know whether it is supposed to work).

In case anybody comes up with another idea, I might try my luck again ;-).

I also tried wifi, but as it seems the implementation uses something different from "normal" wifi-stacks on desktops (all molten down into one big wifi-driver?), so I could not build the normal wifi-stacks at the same time. As such, I did not even try, because only external wifi without the internal one appeared not to be so useful to me ;-).

If you need other special modules, I guess you can just ask for them or try compiling them yourself with released sources.