yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] xavihernandez:
Hmmm I still have wifi issues. It does not connect my network. It says "connection..." and nothing happens. I still have to connect public hotspots before. Then connection again my network and it obtains IP address. Weird issue. Dunno if someone got same kind of problem.

Merry Xmas people. And thank again gokhan!!!
[Galaxy S II Original Android Development] tolis626:
Check your init.d scripts.Many of those(like Thunderbolt) modify things that are network-related(TCP etc).If you see any of these,delete the lines that have any relation to network and see if it works.

I don't bash Thunderbolt or something(I modify and use it myself),but it's for the Galaxy S originally and there may be incompatibilities.
[Galaxy S II Original Android Development] pikachu01:
Try "Forgetting" the Wifi AP. Might be corrupted?

I'm using ThunderBolt! on SGSII and I'm not facing any problems :/
[Galaxy S II Original Android Development] droidphile:
You have to! You're the author !! :D

Nice tweaks btw, especially the i/o scheduler ones.
[Galaxy S II Original Android Development] shanume:
Intellidemand?

Hi gokhanmoral

I will ask why is this Intellidemand governors removes and change back to ondemandx? is there any chance to get Intellidemand Governors back in the future release??

I ask this becuz, when I use siyah 2.4.2 with Intellidemand I have more then 4 days battery life.. thats why I flash back to 2.4.2...

/Tommy
[Galaxy S II Original Android Development] radicalgel:
Ok so this is a quick couple of questions:

1) Can UV through Voltage Control possibly cause data loss or is risk of data loss on restricted to messing with internal voltages? If UV through Voltage Ctrl can potentially result in data then could some pls explain how such an event occurs and what data am I at risk of losing?

2) What exactly is the difference between the voltage accessible through Voltage ctrl and internal voltages?
[Galaxy S II Original Android Development] xavihernandez:
I have nothing related to network but a module ipv6 in 01modules file.

I have already tried that and it does not fix. It happens for any private network.

Thank to both of you anyways.

Another thing : every body got volune on headset issue? (From 50% of volume progressbar volume.does not increase, even progressbar goes to 100%)
[Galaxy S II Original Android Development] droidphile:
The intellidemand we had in a previous version was only a slight variation or tweaked ondemand/ondemandx. Gokhan might bring it back in future releases with features of original intellidemand - browsing mode detection, temperature sensing, etc.

As of now, try ondemandx/conservative with 2.6.1, it's smooth and battery friendly. There are so much more tunables compared to 2.4.2

1) No data loss will happen while UVing through voltage control. There is no support for changing internal voltage as of now. Gokhan said he might bring it in the next releases, that's all.

2) Voltage accessible through voltage control is core/arm voltage. Internal voltage is a different story. Simply put, we don't need to worry about internal voltage for OC/UC. Only tuning core voltages will do.
[Galaxy S II Original Android Development] tolis626:
Well,I too am using Thunderbolt! without any problems,but I've modified many things to suit me.I also deleted all network related commands because of your warning that it may not work as expected on the SGS2. :)
[Galaxy S II Original Android Development] Rampler:
@gokhanmoral

First of all thank you, for your great job you have done.

My Proposal to make it more user friendly:

Leave all additional ZIP's (Battery, Performance) and so one. Most things are already implemented in Voltage Control. User who want to have UC/UV and choosing differnet gouverners should buy VC. Also it would be nice if you and the dev from VC would cooperate and implement a buttom for the logger function for example, same for brightness values.

Its only my personal opinion, and i have high respect what you have already done.
[Galaxy S II Original Android Development] gabx:
Linaro Kernel

Hello,

did you already tried to build this kernel from source? :

http://www.linaro.org/downloads/

Have you ever tried to use their cross compiler ?

EDIT: it seems kernel source won't work for SGS
[Galaxy S II Original Android Development] xavihernandez:
My mobile phone is not recognized when I plug it to PC. It is charging but nothing happens. No USB debugging notification neither. Anyone has had this issue??
[Galaxy S II Original Android Development] AndreiLux:
Is dual-booting still something on the to-do list?
[Galaxy S II Original Android Development] alcurtis93:
Its been done. Google lolboot sgs2
[Galaxy S II Original Android Development] AndreiLux:
My question is not if it's been done or not, but if it will be coming to Siyah. AFAIK Gökhan had a better implementation in the works. Hellcat's is build upon a simple kernel.
[Galaxy S II Original Android Development] gokhanmoral:
there are already several dual-booting implementations. I saw another one in android development section yesterday.

implementing a tool for configuring kernel is in my todo list and I will add restoration of cwm backups as secondary rom, but it won't be ready soon because I am involved in a huge project which has a very tight deadline.

by the way, there is a new base from samsung, for galaxy tab plus, which is using v2.6 kernel. I had 20 mins spare time at work today and merged it with my sources. it did compile but did not boot. changes are simple and if I can get it booting without too much effort, I will release 2.6*2 (not 2.6.2) :)
[Galaxy S II Original Android Development] xavihernandez:
Hmmm it seems that my problem is hardware related. At least even I change ROM or/and kernel my mobile is still not recognized by USB bus. It only charges. Too bad :(
[Galaxy S II Original Android Development] ziroxs:
Hi,

can someone please provide me a script for init.d folder to adjust the screen off frequency?

I just installed 2.6_S99+battery script for a test and didnt want to have voltage control or setupcpu.

thx
[Galaxy S II Original Android Development] kobi63:
The performance.zip scales up to 1200mhz or 1400mhz?
[Galaxy S II Original Android Development] olifee:
You might also try using another USB cable, if one pin has no connection, it might only charge but not be detected as USB device.

I am using a USB-A => mini-USB cable + mini-USB => micro USB adapter mostly for charging my device which came with a non-Samsung charger, and it only connects "sometimes" to the PC as device because the adapter is slightly loose.

Original Samsung-cable should work best.

If you want to debug the problem, have a look at the output of "dmesg" (run on a root shell) on your device right after you plugged in the cable. The dmesg-output of a linux-system connected to it might also help (if there is none, it is totally not recognized :( ).

Did you also try to disable and reenable USB-debugging in settings?
[Galaxy S II Original Android Development] xavihernandez:
First thank for your answer.

I have already tried official and unofficial wire.

Ill try dmesg when I get back home as I have no Linux desktop here.

I wish it helps!

Thanks again ill message here when I have more infos.

EDIT : i have run demsg on my device shell. What should I copy to give you more infos??
[Galaxy S II Original Android Development] Dark_Lord0122:
phone reboots on 2.6.1 with and without battery.zip/UV OC

any ideas?

Edit :

and some weird battery drain from 95 to 83 and 81 to 64
[Galaxy S II Original Android Development] RotesMeerJogger:
if i use the option "flash a kernel" in CWM i get error "no zimage found". what is my mistake? is it required to reboot in recovery mode, select kernel zip and flash it and not in cwm app? at the moment i have ninphetamine 2.1.3+ kernel running. thanks for feedback.
[Galaxy S II Original Android Development] Dark_Lord0122:
Redownload it. i prefer TAR over CWM . i flash them using the CWM app
[Galaxy S II Original Android Development] brack11:
1600 I wouldn't post those screens with enlarged battery, it's not fair.

Sent from my GT-I9100
[Galaxy S II Original Android Development] brack11:
No, I used WiFi 80% of that time.

Sent from my GT-I9100
[Galaxy S II Original Android Development] Rampler:
You have to do an Update (ZIP Update)

Flash a Kernel is used for a TAR file.

You can make a Kernel update in CWM, choose only flash update. i have done it already, it works.

I assume you have a ZIP file
[Galaxy S II Original Android Development] kobi63:
hmm anybody? CPU Spy says i'm only getting 1200MHZ as the highest lvl, should it reach higher?
[Galaxy S II Original Android Development] Rampler:
@All users who have doubts to flash the new Sihya kernerl 2.6.1

I came from Sihya 1.7.8, flashed via CWM (Update ZIP function ==> No Problem)

after then flashend to 2.1.x and so one

Today a flashed from 2.5.2b without any problem

A always flashed without any wipes, no dalvik, no cache wipe.

I got never a problem.

Therefore i suggest, dont read, just do it, enjoy it.
[Galaxy S II Original Android Development] SirCanealot:
Sorry to mention bad news, but I've been having major draining issues in 2.6.1. Was anyone else having issues?

My phone didn't seem to be in wakelock according to battery stats, but cpu spy says my phone didn't sleep all night! Poor thing... :p

Just installed better battery stats but don't notice anything out of the ordinary. Gone back to 2.6 for now anyway...
[Galaxy S II Original Android Development] RotesMeerJogger:
you are right. thanks! now i also on siyah kernel :cool: i have flashed a kernel view month ago and thought have flashed it with "flash a kernel" :)

have made a little benchmark test with quadrant and and my best result with 1,2 ghz was 2200 points. now with siyah kernel i have between 2500 and 2800 with 1,2 ghz and smartassV2. what the hell going on?? ;) :D

one little questen: i don't see voltage control on "running apps" in go launcher ex but the settings from VC works in the background all time. is it right? i make this question because setcpu was listet under "running apps".
[Galaxy S II Original Android Development] KcDaRookie:
@RotesMeerJogger: yepp, the values are saved in the system-files, neither vc nor setcpu has to be running in background after setting the values and applying them

hättest setcpu getrost jedesmal killen können ^^
[Galaxy S II Original Android Development] RotesMeerJogger:
thanks for your feedback. i have killed setcpu but it come back a view time later :)

wow! with vr i/o sheduler i get over 3400 points in quadrant (with 1,2 ghz max). what is your sheduler for best performance in "real smartphone handle" not only for benchmarks? how can i set profiles for "screen off" or "calling" in VC? and is it possible to disable brightness reduction on 10 % battery with siyah kernel?
[Galaxy S II Original Android Development] KcDaRookie:
vr is best for benchmarking only, but dont forget that high scores in benchmarking does not mean good overall performance, bfq/cfq and sio are good alrounders, i would stick to that, if you want to have high scores in marks you took the wrong kernel, siyah kernel does not aim for scores, but for smoothness and perfomance.

You can change the brightness recalibration in powersafe menu (Einstellungen > Energiesparmodus > Benutzerdef. Einstell. zum Energie sparen > Helligkeit) uncheck the boxes and you should stay on higher brightness levels...

Screen off profiles aren't recommended for a lot of governors, ie ondemandx or smartass etc. because they already have an in-built screenoff mode, for example ondemandx has a default screen off max freq of 500, so if you lock the screen the phone won't go higher than 500 MHz...

In Voltage Control if you press on the profilename (on the upper left part of the screen) you can create further profiles, but I dont know if you can choose that a certain profile is loaded in a certain state, can't test it either because this only works in paid extreme edition.

But as I said, screen off profiles aren't really necessary, the governors can handle different stated very well on their own.
[Galaxy S II Original Android Development] olifee:
DISCLAIMER: I know this post is not closely on-kernel topic, but even if it is not related, it might help somebody with usb-problems to diagnose.

Sorry for the late answer, thanks for your reply!

If all is fine, on the device, you should see lines like:

<7>[16669.567974] usb usb cable = 1
<7>[16669.569091] usb udc->enabled=0,=1
<7>[16669.569793] usb Enable usb LDO.
<7>[16669.571426] usb check ldo vcc_d(192)
<7>[16669.572478] usb check ldo vcc_a(192)
<7>[16669.574377] usb change mode ret=0
(some other stuff)
<6>[16669.896706] android_usb gadget: high speed config #1: UMS + ACM + ADB (Debugging mode)

In case only some "max8997" lines are shown, it only charges and has not realized a PC is attached to the cable.

To reduce the amount of stuff it shows you, you can do:

cat /proc/kmsg | grep usb

This will do the same as dmesg, but live, and filter for lines containing 'usb'.

If you get a similar output, the device works fine and has detected the attached computer.

Maybe, you will also see some usb-related errors in those lines. Hopefully these will point to anything...

On the desktop, you would expect something like (my desktop has high debug settings in kernel, so you might see less output):

[31396.454091] usb 2-3: new high speed USB device number 21 using ehci_hcd
[31396.569028] usb 2-3: New USB device found, idVendor=04e8, idProduct=685e
[31396.569035] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[31396.569040] usb 2-3: Product: SAMSUNG_Android
[31396.569045] usb 2-3: Manufacturer: SAMSUNG
[31396.569049] usb 2-3: SerialNumber: XXXXXXXXXXXXX
[31396.570703] scsi16 : usb-storage 2-3:1.0
[31396.571057] cdc_acm 2-3:1.1: This device cannot do calls on its own. It is not a modem.
[31396.571175] cdc_acm 2-3:1.1: ttyACM0: USB ACM device
[31397.570686] scsi 16:0:0:0: Direct-Access Android UMS Composite 00 PQ: 0 ANSI: 2
[31397.570898] sd 16:0:0:0: Attached scsi generic sg7 type 0
[31397.573320] scsi 16:0:0:1: Direct-Access Android UMS Composite 00 PQ: 0 ANSI: 2
[31397.573497] sd 16:0:0:1: Attached scsi generic sg8 type 0
[31397.580204] sd 16:0:0:0: [sdg] Attached SCSI removable disk
[31397.580534] sd 16:0:0:1: [sdh] Attached SCSI removable disk

I am not sure we can really find the problem in there, but if it is a hardware-problem, we might see some errors...
[Galaxy S II Original Android Development] xavihernandez:
Well I tried that and I saw those line sometimes and sometimes not. I tried to touch the cable to see if there is no bad contact. And it seems to be the problem. At the moment I can recognize my device. But if I move the cable it randomly disconnects.

Well thanks for your advice and your time.
[Galaxy S II Original Android Development] mazroui:
Anybody else using latest version getting similar results ? Kernal wakelocks hmmm...
[Galaxy S II Original Android Development] mundixx:
sorry for this rather ignorant question.. but in this version, 2.6.1, can we still apply the ZIP files (performance.zip) ?
[Galaxy S II Original Android Development] droidphile:
You can use performance/battery/defaults or one that you create tweaking values in any of these.
[Galaxy S II Original Android Development] mundixx:
Thank you! Well 2.6.1 looks promising.

Sent from my GT-I9100
[Galaxy S II Original Android Development] droidphile:
vbus-present: Your charger was plugged in

svnet-dormancy: Driven by data use

main: Wakelock held when screen is on

svnet: Driven by data use

powermanagerservice: Wakelock held to have the screen-on, as a partial userspace wakelock

bln_wake_lock: wakelocks held for active bln notifications

radio-interface: Wakelock for RIL. Related to dialing/receiving call

AudioOutLock: Held while playing music?
[Galaxy S II Original Android Development] mazroui:
Thanx for the clarification, after a while the batt picture got clearer ^_^
[Galaxy S II Original Android Development] b2rdetor:
test ondemand&conservative 100-1400

tweaked conservative are real **** (sorry gokhan but IMHO) )))

first - its instable with minimal usage (always try to scales up to 200\500), but ondemand sets 100 and sometimes (muuuuuch more less scales up to 500)

second - during game (GTA3) it set 1200 and never up and down freq, but ondemand uses 800,1000,1200,1400 during game when its need without any performance loss. may be ondemand even smoother because it use 1400 (cant understand why conservative isnt set 1400 during game, but it set 1400 when

scroll inda launcherex - very strange behavior)

third - during 10min GTA3 at the same level same brightness conservative drain 6+%, but ondemand only -4 - 4+% (really shocked), because ondemand try to stay 800-1000 and set 1200-1400 only when it need, but conservative set 1200 always!!! tested with mugenpower 3200mA (2.5-3h vs 4-4.5h playing!!!)

my settings its a batery.zip (without governor\freq tweaks), autobrightness (without energysaveautobrightness), initd brightness 15, 0, 22 (you can set it like you want)

voltage control script (100-1400 ondemand bfq, 1400\1250, 1200\1150, 1000\1075, 800\950, 500\850, 200\850, 100\850, GPU 100\800, 266\950)

all extreamly stable and fast as ligthning with extreme battery life during sleep and usage\power usage!

recomend it for all!!!
[Galaxy S II Original Android Development] Miguel-:
I've had a few times phone not going to deep sleep after kernel flash but its usually fixed by just rebooting the phone and leaving it to bootup properly before starting anything..
[Galaxy S II Original Android Development] cwc3:
Still have a bit to learn about your kernel. Playing around with those init.d scripts you gave us, awesome place for a beginner to tweak. Enjoying the battery now.

Once again, much love from the AT&T people.
[Galaxy S II Original Android Development] milan188:
I flashed 2.6.1 with battery script and my charging from the charger is quite slow... I changed it to 900 on voltage control... I don't know if this was mentioned before

Sent from Galaxy SII XDA Premium
[Galaxy S II Original Android Development] Delacor:
Sometimes I get a bSoD when I recieve a message in Whatsapp etc.

Means System don't do anything when I Press Homebutton...

Cleared all caches, going back to 2.5.2 for now....

send from my GT-I9100
[Galaxy S II Original Android Development] gabx:
ICS and Kernel 3

Hello,

do you intend to build a Kernel for ICS, as we have now a not so bad alpha cm9 ROM ?
[Galaxy S II Original Android Development] hIdd3N-:
Better read changelogs. Charging amp control is disabled cuz it won't work on sgs 2. Never has and never will.

You problem with slow charging lies somewhere else.

Check background apps or maybe it's just placebo.
[Galaxy S II Original Android Development] hIdd3N-:
I'm sure he will as soon as sammy sources are available.
[Galaxy S II Original Android Development] Molitro:
Yeah, he said some time back that he was going to.
[Galaxy S II Original Android Development] Rampler:
my expierience with 2.6.1

- cpu utilization is more distributed over the frequencies. With 2.5.2b i had 90 % of 100 Mhz and 8 % of 800 Mhz, rest 200 and 500 Mhz. For my use the 2.6.1 its better, the usage is more fluently.

- Akku drain, no differnce (without Battery.zip)
[Galaxy S II Original Android Development] grey77:
I beg to differ. UVing can lead to any data loss due to possible hardware instability. And the changes will permanently remain after some process writes these corrupted data to disk. If someone is unlucky he might even damage file system and completely ruin the functionality of his software and he`ll have to wipe and reflash the whole thing.

It doesnt matter whether we use VoltageControl or SetCPU or other utilities.

---------- Post added at 02:35 PM ---------- Previous post was at 02:24 PM ----------

Uve been doing that already by undervolting ur CPU (according to ur signature). =)

Actually, the point is to have more adjustable features in the kernel. We try UV for that new internal voltage regulator. We thoroughly test it. If that gives us more battery life and doesnt compromise stability and we can afford spending some time for bored to death testing routines, why not? Cant wait to test out the internal voltage regulation feature! =)
[Galaxy S II Original Android Development] KennyLegend:
It is still adjustable via voltage control mate. That means anything up to 500mA Will result in a 400mA charge current and above 550 i think results in 650mA charge current. I don't think Gokhanmoral actually removed this feature yet.

Correct me if im wrong here guys .
[Galaxy S II Original Android Development] droidphile:
I mean if you undervolt step by step, like normal people. Calm down.

His UV is for core voltages. He was talking about internal voltage. Two different things.
[Galaxy S II Original Android Development] grey77:
Well, even if we do it by slowly reducing voltage step by step, EVERY glitch can lead to corrupted data. See my expanded post above.

Nah, Ive read it thoroughly. It correlates with each other when it comes to run the same risks of UV.
[Galaxy S II Original Android Development] pikachu01:
UVing the arm voltages would only bring about corruption if your file systems are not journaled and you were writing something in the middle of tweaking your voltages.

UVing the internal voltages would bring about corruption as the voltages are too weak to support writes, thus causing some writes to be only completed halfway.

Also, gokhan,

Have you taken a look at the patch here:

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

This is to make ondemand sleep really really well, reducing battery usage when screen is off.

Also, can you enable CONFIG_SCHED_DEBUG on your config? This enables tweaking the CFS (which would lead to better performance, with little expense on battery life)
[Galaxy S II Original Android Development] grey77:
Corrupted data will be flushed out to file system later, simple as that. ;) It doesnt matter when. The point is that after instability due to any UV we run risks of getting corrupted data (user and system ones).
[Galaxy S II Original Android Development] pikachu01:
Your definition is too broad. The chance of having data corruption when UVing arm voltages vs internal voltage is far too small to tie them up together. By that definition, you could even say flashing a CWM file could cause corruption (yes it happens, but it's rare), or even an Odin flash (yes, it's rare too)
[Galaxy S II Original Android Development] ziroxs:
I am now a little bit confused. Is for example the battery.zip/performance.zip able to be applied only for 2.6_S99 Kernel or for 2.6.1 as well?
[Galaxy S II Original Android Development] duff91:
Anybody have this problem with ntfs pen drive?
[Galaxy S II Original Android Development] EdgaBimbam:
you can apply for both versions ;)
[Galaxy S II Original Android Development] tolis626:
For Christ's sake,these zips are plain init.d scripts that modify certain kernel parameters to favor battery or performance or to maintain a balance between the two(defaults.zip).They don't have anything this special in them,they're just reference scripts and are subject to change by anyone.You can even apply them on 2.4 and 2.5 and maybe even older versions.Only things that have been implemented in 2.6 won't change.Alright?
[Galaxy S II Original Android Development] grey77:
Very true. These battery/performance scripts and other settings from the late releases do work with older kernels like 2.2beta6, unknown settings will be just ignored, not allowed/out of range parameters will be substituted with default ones.

2ALL: could u pls test on ur configurations the performance while playing HD (720P) video with software/hardware codecs over CIFS? It degraded in recent kernel versions (probably since 2.2i/2.2p), not flawless any longer.
[Galaxy S II Original Android Development] bala_gamer:
I have seen this in other kernel thread

SAMOLED+ screen UNDERVOLT (3V ---> 2.5V)

is it possible to UV the screen?? as it is the most power hungry part, Uv ing it might save some juice. What are the other configurable voltages in S2?