yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] rodries:
I've tryed to compile to apply your fix, but I've got a hang when I install the compiled kernel. To compile it I only call ./build_sh with a little change in it,

I've added mkdir -p $INITRAMFS_TMP/lib/modules/ after rm -rf $INITRAMFS_TMP/.hg

I've tryed with & without this change and with & without your patches. Have you tryed to install siyah compiled by yourself?

I get a hang when loading the kernel, I'm using international config, in build_sh you can see that the default config is international.
[Galaxy S II Original Android Development] jaikat:
i know this has been mentioned many times before, but there's something i can't understand here..

i'm trying to get the logger always running, i just don't want it to be disabled.. i put the "enable-logger" script where its supposed to be, renamed the "disable-logger" script under /data/.siyah, rebooted and at first logging works, but after sometime it stops, i go into /data/.siyah and find that the "disable-logger" script reappears. this also happens even if i delete the file completely..

please help.
[Galaxy S II Original Android Development] gokhanmoral:
I'm back

hi again.

sorry for being silent for such a long time. I was very busy and got married. after deploying my projects and a little honeyishmoon break (only 3 days because of the workload) I am back.

fortunately, I will have some time this week.

I am planning to compile another kernel tomorrow which will include Entropy512's patches to solve video decoding issues with the latest kernel and some rollbacks to 2.6.9 which seems to be the best version according to the feedbacks.

I am also planning to complete the new config scripts tomorrow. xan sent me the new voltagecontrol app with universal config interface support and it works great. if I can finish the scripts tomorrow v2.6.13 will have those scripts and almost everything will be controllable through that new interface.
[Galaxy S II Original Android Development] www1:
Can add display screen voltage control?

I want to try small undervolt

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] MistahBungle:
Good to have you back Gokhan & congrats on your marriage :)

Don't apologise, we're lucky as users to have a dev like you who listens to our feedback & implements the things we like/ask for in your builds.

Looking forward to the new build & especially the new interface, but take your time man, we can wait a few days/week/whatever ;)
[Galaxy S II Original Android Development] :
Congrats in order as well mate...I agree with MistahBungle. Take your time mate and we can wait. At this moment of time give more attention to the Mrs and we can wait.:)
[Galaxy S II Original Android Development] Vaedryn:
Welcome back Gokhan and all good , gratulation to you and your woman:)

SGS II Cyanogen Mod 9 Tapatalk
[Galaxy S II Original Android Development] desean:
logger is enabled by default (see FAQ) since many versions ago. I guess you are either using an old version that has it disabled or you have an init.d script that is creating that disable-logger file

Congrats on your marriage
[Galaxy S II Original Android Development] b2rdetor:
HI, Gokhan I wish happiness to you and your family!!!
[Galaxy S II Original Android Development] incubus_fr:
Congratulations!
[Galaxy S II Original Android Development] teiglin:
Something is wrong with this quote...

+

Right, there it is. Oh look, I see some winged pigs in the sky! :rolleyes:

Welcome back GM. Sorry you only got 3 days of honeymoon! :(
[Galaxy S II Original Android Development] droidphile:
Are you in some sorta pain?
[Galaxy S II Original Android Development] Entropy512:
Undervolting the screen will not help power consumption, and in fact is likely to hurt it.

I am 90% certain that the screen dims using PWM - it rapidly turns power on/off to a pixel to achieve a given brightness. PWM is an efficient way of altering brightness as it wastes very little power.

Undervolting the screen's main supply, however, will have counterintuitive effects - to achieve a given brightness, the PWM value will be higher. So the screen will consume more current (higher PWM duty cycles) when provided with lower voltages. This combined with the fact that the screen power supply is an LDO and not a buck converter (LDOs get less and less efficient as their output voltage drops) like the CPU core power supply means that undervolting the screen supply LDO will result in MORE power consumption for a given brightness.

Same goes for the touchkey backlights - I'm fairly certain there's a boost converter between the touchkey LDO output and the LED itself, that aims to achieve a constant current to the LED (It's almost impossible for a typical white LED to run on only 2.8 volts directly). If the input of this converter is undervolted - it will use more current from the LDO, which will increase power consumption. I hope to run some tests this weekend.
[Galaxy S II Original Android Development] DirkTeur Velserbroncx:
Gokhan welcome back and congratulations on your wedding, hope you did enjoy your tiny honeymoon mine lasted for a day, and they asked me to start to work at the same day i got married, so i know some about a heavy workload.

never the less wish you and your new wife al the best for the future and maybe soon we can expect a little tike to follow up when your done with developing?

Aldo i think you're never done.
[Galaxy S II Original Android Development] chowlala:
Congrats on getting married bro! =D *bro fist*

Life is more important anytime!! :D
[Galaxy S II Original Android Development] stylez:
Mini Gok :D

Could spout end of development due to time constraints :(

WB gok and congratulations :) keep buckled up ;)

Sent from the valley of the shadows....
[Galaxy S II Original Android Development] rainin:
Congrats on the marriage bro. Wishing u a blissful marital life.

Take your time. Life first, kernel later ;)
[Galaxy S II Original Android Development] olifee:
Congratulations gokhanmoral!

(finally a good reason to post something non-dev related. Wait... it actually is dev-related ;) )

Always remember, life comes first, so if you have some free time this week to compile, also spend some time with your wife :).
[Galaxy S II Original Android Development] stevehkim:
welcome back GK! congrats to you brotha and best wishes. been married 11 years now with 2 beautiful kids and wouldnt have it any other way. cherish what you've got and take your time!

MIUI/SIYAH Pimp Juice

Fast and Furious @ 1.5ghz
[Galaxy S II Original Android Development] Hannibal226:
Congrats!

Waiting for next release ;-)

CHEERS ;-)

Sent from my Galaxy S2 - I9100 with SensatioN Rom!
[Galaxy S II Original Android Development] jaikat:
congrats gokhanmoral and best wishes :)

i'm running 2.6.12, and the only way i could run logcat was by either renaming or deleting the "disable-logger" file under /data/.siyah

is this file created by siyah?!
[Galaxy S II Original Android Development] eric-filth:
I like so much. I wanna to say for you. Very very good work congratulations for your time to make this.

Your tests confirmed my opnion about undervolt.

And have people here say uv dont make difference.

I dont know why developers still keep possibiliy to use min freq 100mhz
[Galaxy S II Original Android Development] Thialala:
Congratulations Gokhan. Best wishes.
[Galaxy S II Original Android Development] AlexMagik:
Hi Gokhan,

as a married man myself, i think i should say that i'm sorry for you :)

kidding (no, not really) :p:p:p
[Galaxy S II Original Android Development] Shinfei:
Congrats mate best wishes ;-)
[Galaxy S II Original Android Development] Holgott:
Congratz Gokhan! Hope u found ur spiritual middle! :-)
[Galaxy S II Original Android Development] InnAl:
All the best to you and your wife Gokhan!

My wedding will be in December :-)

Envoyé depuis mon GT-I9100 avec Tapatalk
[Galaxy S II Original Android Development] tenchi0205:
Congrats on getting married bro!
[Galaxy S II Original Android Development] Crescendo Xenomorph:
Congratulation Gokhan... ^^
[Galaxy S II Original Android Development] don1bong:
Congratulations gokhan :D

F5 spam for update ;)
[Galaxy S II Original Android Development] legionxx:
Congrats Gokhan and best wishes! :D
[Galaxy S II Original Android Development] privat75:
Hayırlı olsun

Mutluluklar dilerim

:thumbup:

Gesendet von meinem GT-I9100 mit Tapatalk
[Galaxy S II Original Android Development] pollo17385:
Congrats Gokhan and best wishes! ;)
[Galaxy S II Original Android Development] aljee77:
Congratulations for the wedding and everything good for you and your wife!!!
[Galaxy S II Original Android Development] xXCorleoneXx:
Congrats mate best wishes .
[Galaxy S II Original Android Development] manyakurt:
Mutluluklar dilerim abi, dikkat ettim o kadar geliştirici var içlerinde en çok sevilen sensin. Ve takipçilerinde çok seviyeli, millet dev topiklerini kitlemek zorunda kalıyor...

Güç seninle olsun ! :)
[Galaxy S II Original Android Development] poochewer:
Thats exactly what I wanted to say!! LOL:rolleyes:
[Galaxy S II Original Android Development] cwc3:
SGH-I777 community gives you the best of wishes to both you and your wife. You found true love my friend. Congratulations :)
[Galaxy S II Original Android Development] Ok_Kaleidoscope5109:
i get a lot of wifi dropouts... yes you guys probably will blame my router or whatever, but as a tech geek ive been rocking my Nexus S for a year, and my iPod Touch 4G, HP TouchPad, and iPad 2. All never drop Wifi.

Don't know why my SGS2 sometimes drops or fails to connect at times to the same router that all these other devices have no problem connecting to...

Second question: If I wanted to use CWM Touch recovery with this kernel, what should I do?
[Galaxy S II Original Android Development] droidphile:
1) Issue is likely to get solved in next release since there's a revert of wifi drivers. As a simple step, try forgetting the network and configure again.

2) You can integrate touch cwm and build a release from Gokhan's sources or wait till Gokhan releases a build with touch cwm. :)
[Galaxy S II Original Android Development] AlexMagik:
Or you can try with the version 2.6.9 as it works a lot better than the 2.6.12; at least for me. Also which modem are you using?
[Galaxy S II Original Android Development] droidphile:
Wifi issues are almost completely kernel related and rom related, unless it's router/traffic related. Kernel has the wifi drivers. Not the modem. 2.6.13 will have same wifi drivers as 2.6.9.
[Galaxy S II Original Android Development] don1bong:
You tried changing the wifi channel?.. Get wifi manager from Android market, that will scan the best channel for you..

Swyped from white Siberiantiger coated checkROM enabled brick
[Galaxy S II Original Android Development] Entropy512:
It could be the attempt to bring in different wifi drivers in the kernel, it could be just that the BCM4330 doesn't like your router - it doesn't seem to like a lot of hardware, ESPECIALLY firmwares around XWKK5 or so. Wifi is partly handled by the kernel but also heavily by a binary "blob" of firmware that's stored in /system. Some Samsung firmwares either broke this firmware or some other configuration stuff in /system. AT&T UCKK6 sucked wifi-wise, and XWKK5 is likely bad too.

Yup. Modem will ONLY affect wifi hotspot (since that uses cell data).

Early Qualcomm MSM chips had the baseband radio do all sorts of housekeeping (including bootloading the application processor I believe), and the AMSS did all sorts of stuff (GPS, and wifi too I think, but I'm not sure).

All Samsungs are the opposite - the application processor bootloads the radio processor, and the radio processor ONLY handles cell data.
[Galaxy S II Original Android Development] shoman94:
Where do you get his info? Wifi hotspots use wifi not cell data. I've used many. Always wifi.
[Galaxy S II Original Android Development] AndreiLux:
Using the phone as a wifi hotspot tethering cell data.
[Galaxy S II Original Android Development] shoman94:
Yea no kidding but that is a portable hotspot not a wifi hotspots as what was being talked about. The modem still has nothing to do with wifi period.
[Galaxy S II Original Android Development] Entropy512:
Um, you can't provide a wifi hotspot without the data coming from SOMEWHERE. Where do you think the data comes from when you turn on wifi hotspot mode?
[Galaxy S II Original Android Development] shoman94:
Yes but what you quoted was talking about router wifi dropout issues not mobile hotspot issues.(why I was confused of what you were talking about) And even if it would be mobile hotspots issues, the issue would be on the wifi side which would be related to the modem. Its all I was getting at.
[Galaxy S II Original Android Development] ernest101:
hey guys i got a problem, when i mount internal storage and connect it to my pc, nothing happens, no idea why, it only happened when i am using this kernel (i am quite new to Siyah). No i am not pointing fingers that Siyah is faulty or whatever, it is likely some dumb thing i did with my phone/computer. I am using CM7 116 btw.
[Galaxy S II Original Android Development] don1bong:
Are you referring to, previously MTP used to connect automatically?

And now you have to open notifications and click to enable USB connection

Swyped from white Siberiantiger coated checkROM enabled brick
[Galaxy S II Original Android Development] Entropy512:
No, that's not what I quoted. What I quoted was:

And I confirmed that statement. "router/traffic related" was a bit vague so I clarified that as being wifi hotspot functionality.
[Galaxy S II Original Android Development] ernest101:
erm no, it is when i am in recovery and wanting to mount usb storage. i have updated my driver and my computer isn't detecting my phone, i tried with my friend's htc, it worked for the htc.
[Galaxy S II Original Android Development] don1bong:
HTC uses completely different drivers.. Have you tried installing kies ? That will ensure you have the correct drivers..

Swyped from white Siberiantiger coated checkROM enabled brick
[Galaxy S II Original Android Development] shoman94:
OK :rolleyes:
[Galaxy S II Original Android Development] Honusnap:
Totally agree ... 2.6.9 or 2.6.7 better than 2.6.12 also for me.

About touch cwm .. i really don't see the advantage of having it .. !! A mistake by touching the wrong place .. Pfiiiiiouuuuu .. format done .. :rolleyes:

Cwm is very good as it is
[Galaxy S II Original Android Development] Destke:
I find the kernell good, but i have only one problem. It's small but pretty important.

The volume of my media and ringtones is low. So somethimes i don't even see i have a message cause i can't even here it. Is there a fix for this.

Cause via my headphones i got a pretty decent sound.
[Galaxy S II Original Android Development] tolis626:
Did it cross your mind that these popups which ask whether you are sure you want to continue exist for a reason? ;)

Been using 4EXT Touch recovery on my Desire HD for a good while now and it's quite easier than CWM.Not to mention that it has some more options.
[Galaxy S II Original Android Development] CamoGeko:
Not really a kernel issue, I had no issues with volume here.

What ROM are you using? Its most likely that.

Logged using an SGS2 type droid while floating in CheckROM quadrant...
[Galaxy S II Original Android Development] Destke:
Using Checkrom V6 :-) Hadn't had an issue before I installed the kernell.
[Galaxy S II Original Android Development] Delacor:
Use my SII in mass storage mode on my Mac.. My Mac says sometimes that my Filesystem is corrupted. Tried it then with windows - same thing... Pls. Help my Filesystem isn't corrupted and I already tried formatting it...

Also don't work in CWM...

Send from my SII ;)
[Galaxy S II Original Android Development] Destke:
Nevermind :-) My problem seems to have solved itself.
[Galaxy S II Original Android Development] gokhanmoral:
v2.6.13 is ready (and the source is already pushed to bitbucket).

I have not uploaded it to my blog yet because it needs some more testing (mainly the new config interface)

I hope to release it tomorrow (another delay). I hope xan can finish the voltage control app and publish it in the market by then (or maybe publish as another app).

the new config interface is able to config pretty much everything (cpu hotplug settings, AFTR & secondcore functionality, gpu thresholds & voltages, resetting fuel-gauge chip, and some others that I forgot)

xan has done a great job and the interface looks great.

the interface will be open & usable by others. the scripts are pretty easy. I will simplify them even more when I have some more time.

thanks to xan that I didn't have to spend any time on implementing an app. his voltage control app was the reason that I did not learn java and I am thankful to him because of that :)

anyway.. I hope you will like the interface when it is released.
[Galaxy S II Original Android Development] sgunf:
Wonderful!

Waiting for hands on!!

Thank you again & again for the time you spend for this kernel. Maybe your wife will thank you a bit less, but i hope she will understand ;-)
[Galaxy S II Original Android Development] AlexMagik:
wooooo....

.13 is getting here :)

will waiting impatiently for it :)
[Galaxy S II Original Android Development] shoman94:
Will he be adding the screen state function? (Screen off governor change)

I would be anxious to see how

.13 will match up to the 2 kernels I tested the last couple days for my rom.
[Galaxy S II Original Android Development] ole12:
Just writing something on the somehow quiet thread.
[Galaxy S II Original Android Development] gokhanmoral:
I have restarted to work on the kernel on the beginning of this week.

the thread is silent because there is not much changes lately.

some people are using v2.6.7 or v2.6.9, some are using 2.6.11 and some of them are using 2.6.12 (those who do not watch videos I guess)...

I am sure there are lots of people who have migrated to other kernels because of the low activity on this thread.

from the source code perspective, there is not much difference between the available kernels actually.

everybody is waiting for ICS sources.

I see that entropy512 has a new kernel for i9100 which is very good.

we already have several other active kernels. I read that simone201 has released a new config app and working on some other paid version..

so, there are other threads which are already active :)

I am working on a config interface which I believe is very good (thanks to xan and AndreiLux) and I don't want to rush because I want it to be bugfree this time.

There will be not much tweaks in the kernel because +- 50 points in antutu benchmark is not worth spending lots of time. people already reported that v2.6.9 is good enough and I want v2.6.13 to be at least as good with a decent config app.

then I will start working on ICS, even without having the source code.

until I release v2.6.13 (it is ready except for the config scripts) there will not be much traffic on this thread...
[Galaxy S II Original Android Development] :
take your time mate. no rush here...quick question. sorry if this has been asked. your configurator app will that be open to use with other kernels as well? thanks again for your time
[Galaxy S II Original Android Development] Vaedryn:
Start work for ics when source is puplic sounds nice :) hope we will see in the future a Kernel from you for aosp and stock likes the GB Kernel:)

SGS II Cyanogen Mod
[Galaxy S II Original Android Development] gokhanmoral:
most of the settings are common.

the answer is both yes and no.

the kernel developers will be able to implement that interface very easily.

however, my implementation will be in the initramfs, therefore will not be usable on other kernels.

xan is thinking about releasing the implementation as a separate application.

if he does so, I am thinking about adding that functionality.

for now, the interface is reading the config file, setting the values...etc using a script in /res folder named uci.sh

it is possible to make the app to read additional config from /system/uci.sh and this way rom developers will be able to implement some custom pages.

and we can even add /data/uci.sh to let users create their own custom screens.

the interface specs will be open but the implementation of it in voltagecontrolapp will be closed (of course).

I have already installed mono for android to my computer and I am thinking about making an open implementation using it.

the good in the interface is that you won't have to reinstall the app to change the interface. once you have an app that supports it (such as voltage control) new kernel releases will introduce new tabs and UI elements to customize.

and there will not be any incompatibilities.

if you revert back to an old kernel, the interface will be modified accordingly to support the installed kernel.

the scripts are very easy to modify and other kernel developers will have a document (I will write it after releasing it) which explains the details.

it will take about an hour for them to use the interface in their kernels.

normally, we echo a value (or values) to a device file.

if it is a single value, the interface is very easy to modify.

if there are more than one value (such as gpu thresholds) you have to create a new script (or modify an existing script)

there is an xml file which defines the interface and it is also very easy to customize.

there is no documentation now but you can check the details in my bitbucket repository (http://bitbucket.org/gokhanmoral/siyahkernel in res/uci.sh and res/customconfig directory)
[Galaxy S II Original Android Development] :
Thanks GM..:) Looking forward to the release and as i said take your time i think i can speak for most people here that we appreciate what you do for us.:) I shall have a look at the bitbucket to get more info..:)

Just a little last simple question..What kinda scripts are you thinking of adding? will you add scripts like to activate the dual core incase that means no need for the Tegrak app then?
[Galaxy S II Original Android Development] gokhanmoral:
I have added tegrak's secondcore app functionality to the scripts. so, right, you won't need tegrak's second core app.

for now, in the first tab, we have hotplug settings (secondcore on/off, loadl, loadh, loadl_scroff, loadh_scroff, rate, rade_cpuon, rate_scroff, freq_cpu1on), CPU Idle and Power Settings (AFTR/IDLE+LPA modes, sched_mc) and smooth scaling settings (smooth_target, smooth_offset, smooth_step)

in the second tab, we have... well... let me upload a video, that will be simpler :)

brb
[Galaxy S II Original Android Development] gokhanmoral:
ok here it is : http://youtu.be/gZlodCWLWHc
[Galaxy S II Original Android Development] :
cheers mate...i will say this next release will be a massive one...as much as i love NEAK and i am using that, siyah for me has always been the daddy:D

Looks great and the new implementations look great in the Voltage Control app you guys have done a great job with it. Looking forward to testing it.:)
[Galaxy S II Original Android Development] zikarus:
That looks awesome!
[Galaxy S II Original Android Development] gokhanmoral:
if you inspect the source code, neak and siyah kernels are not that much different.

simone201 has only some different approaches, that's all.

I am thinking about the contribution part more and try to contribute&share as much as I can. I hope NEAK can do the same as he grows older :) you are right, considering my age, siyahkernel is like a daddy :)
[Galaxy S II Original Android Development] :
from speaking with Simone yes that is what he is intending to do. But in his way he is creating a whole new app by having everything in one plus all the stuff you can do from recovery the way he has implemented his tweaks and options from it. So yeah you are right not that different but different approaches and i yeah you are right both will grow in time. :) Nothing but good stuff from the both of you.
[Galaxy S II Original Android Development] CamoGeko:
+1

Siyah and NEAK are in a class of their own. :)

Logged using an SGS2 type droid while floating in CheckROM quadrant on a research mission.......