yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] olifee:
Sounds like a problem of the ROM. Works fine here on CheckROM RevoHD 3.1.1.

The notification / unmount message is shown by the ROM, the kernel just notifies it of having mounted the pendrive (if I understood correctly).

Which ROM do you use?

---------- Post added at 12:12 AM ---------- Previous post was at 12:00 AM ----------

I totally agree with you :). Data should be safe in all normal use cases, the abnormal use cases (like the oscilloscope) can find their own solution (like logging to a network file system or ramdisk ;) ).

A suggestion when you switch to 3.1 sources: I am not sure whether this will really help, but using the new zram as swap greatly improved performance on my desktop. After I also added zcache, I save many read accesses.

I am not sure how much of an impact it is on a non-harddisk system with virtually no seek times, but it might be worth to test it. After all, it is a tradeoff: Slightly more CPU-time against some / a lot more RAM. Especially, the additional zcache might make sense.

A nice init-script I use is provided here:

http://www.mathematik.uni-wuerzburg.de/~vaeth/download/zram-init-2.tar.gz

It's pretty long, but very failsafe, but I guess for a tryout on the phone you might just insmod the modules with some settings and swapon them ;).
[Galaxy S II Original Android Development] gokhanmoral:
is it formatted as ntfs?

if so, don't worry and just unplug because no rom supports it yet. automounting of ntfs it is supported by the kernel.
[Galaxy S II Original Android Development] Knight77:
CheckROM RevoHD 3.1.1... :(

---------- Post added at 12:41 AM ---------- Previous post was at 12:40 AM ----------

No is fat and honestly I tried for hours to run a script that allowed me to read the ntfs but nothing... can you please post the correct procedure? Thank you
[Galaxy S II Original Android Development] gokhanmoral:
actually we already have zcache and zram support in v2.2 but they are not enabled.

I will introduce them in the next version.

use v2.2 and plug the usb with ntfs

it will be mounted to a directory in /mnt/usb automatically.
[Galaxy S II Original Android Development] olifee:
You're awesome :).

I think before 2.6.38 (or something like) they changed the syntax pretty often, e.g. at some time, there was an app to set the size of the zrams iirc (and the name once was compcache). That might be the reason why I forgot it was already working with older kernels ;). And of course the module code from the new kernels should also work now that it is there, I guess you used that :).

Did I mention you are awesome? :)
[Galaxy S II Original Android Development] xan:
Static bus frequency support added to VC. (finally)

Its integrated into profiles system, should work in init.d script too.

I'm planning to add governor-specific settings and promised tweaks.sh tuning, this will take some time though, as I'm switching to another project. (nitrality)
[Galaxy S II Original Android Development] Gowind:
Guys don't know whether this is kernel related. I've always been on siyah. But ever since I'm on 2.1.1, I lose my imei after a reboot. Sometimes it comes back after a couple of reboots but many a times I had to restore my efs backup. This started to appear after I have changed modems too.
[Galaxy S II Original Android Development] Rockin_Zombie:
+1 happened to me twice, a reboot fixed it. Happened in both sammy (gingermod) and MIUI rom.
[Galaxy S II Original Android Development] lordsyre27:
WTH

i flashed this kernel to my SGS II Stock Rom 2.3.3.. It booted first and goes so well until I reset my phone.. It got stock in In Welcome Logo and cant even go to recovery.. What happened? What am I supposed to do?
[Galaxy S II Original Android Development] bala_gamer:
Still using 2.3.3? The 1st post of this thread states, this kernel is only for 2.3.4 + roms. You are supposed to read it before flashing.
[Galaxy S II Original Android Development] navdra:
Just noticed that backlight buttons don't work in daylight

Sent from my Galaxy S II
[Galaxy S II Original Android Development] crypticc:
Why on earth would we need compressed backing store?

there is oodles of memory on our devices for multi-tasking. Better to let dalvik swap the app out IMO.
[Galaxy S II Original Android Development] scorpion667:
For some reason in CM7 111 with Siyah 2.2 B15 automatic brightness does not work.. most of the time. I can see it adjusting on rare occasions. Any way to fix via script? It was working fine for Samsung ROM and same kernel.

After setting Bus to 400mhz for all steps aside from 200mhz and touchscreen sensitivity to 0, this is the smoothest android experience I've ever seen!
[Galaxy S II Original Android Development] :
doesn't work in init.d script on stock xwki8 rom, with rc2 and media scanner disabled (all other values applied successfully).
[Galaxy S II Original Android Development] antt00:
On checkrom 2.0 (XXKI4) and i confirmed vel1m1r findings. Bus freq was not set at boot even though it was in the init.d script. Other stuff like governors in the script is executed normally. Using 2.2 RC1.
[Galaxy S II Original Android Development] sadonlyone:
hmmm...

today I've made an upgrade to rom XWKJ3, with CF-Root-SGS2_XW_XEN_KJ3-v5.0-CWM5. then I've switched to v2.2 rc2, v2.2 rc1, v2.2 beta16 and back again to CF-Root. between kernel's flash I've noticed something not so good: on 3 above kernels from Siyah home button wake up performed delay when it was pressed, after a few minutes of using phone.

I've not tested older kernels just 3 above. On CF-root this never happens, home pressed button always react almost instantly and wake up lockscreen.
[Galaxy S II Original Android Development] andyhung:
I have put those script in /system/etc/init.d and changed permission to 777 :

/system/etc/init.d # ls -la

ls -la

drwxr-xr-x 2 root root 4096 Nov 24 09:53 .

drwxr-xr-x 14 root root 4096 Nov 23 17:08 ..

-rwxr-x--- 1 root shell 365 Aug 1 2008 00banner

-rwxr-x--- 1 root shell 27 Aug 1 2008 01sysctl

-rwxr-x--- 1 root shell 229 Aug 1 2008 03firstboot

-rwxr-x--- 1 root shell 201 Aug 1 2008 04modules

-rwxr-x--- 1 root shell 1452 Aug 1 2008 05mountsd

-rwxr-x--- 1 root shell 443 Aug 1 2008 06mountdl

-rwxr-x--- 1 root shell 925 Aug 1 2008 20userinit

-rwxrwxrwx 1 root shell 2584 Nov 24 09:53 S95CpuManage

-rwxrwxrwx 1 root shell 1353 Nov 24 09:53 S96CPUV

-rwxrwxrwx 1 root shell 1601 Nov 24 09:53 S97GPUV

However, after the system reboot, it just stopped in Samsung logo.

I am using CM7.1 stable with siyah 2.1.1

Any hints ??
[Galaxy S II Original Android Development] gokhanmoral:
I suggest you to use "#!/sbin/busybox sh" as the first line in the scripts because some roms do not have /system/bin/sh linked to busybox

EDIT: stopping at samsung logo is not related with this though..

you may be using wrong values or your phone may not handle something in the scripts.

use stock values
[Galaxy S II Original Android Development] Molitro:
That's very much not good, you know... It means the phone is always awake, and the battery will last for few hours.

The delay on the phone wakening is, you can say, "built into the phone", and basically inevitable if you want the phone to go to deep sleep (which you DO want).

On a kernel's note, I don't know what is happening lately, but I can't reach the 1% every around 2:30 hours idling with wifi I got with old versions. I barely get 1 hour out of every %. Same everything, don't know what the hell is wrong.

Tonight I tried with void.charlie, and the drain went down to something similar as what is was before (not quite there yet, though). 9% on 17 hours. I'll keep trying with newer versions of Siyah, cause it's always the one that gave me the best battery life, but I don't know what's happening lately.
[Galaxy S II Original Android Development] sadonlyone:
@Molitro

standard battery sucks anyway. I would rather prefer speed and stability to gaining 1 or maybe 2 hours of battery. for me, with wifi, data and gps on, battery lasts not even a day long. until v2.2rc3 release I'll keep cf-root.
[Galaxy S II Original Android Development] Molitro:
Edit: I was talking about the wrong topic xD
[Galaxy S II Original Android Development] hallydamaster:
That's not quite true! I am running cm7 and Siyah 2.1.1 and my phone is waking up instantly after I press the home button! And my phone is definitely going into deep sleep!

The problem its must likely the governor or UC related!
[Galaxy S II Original Android Development] d8389:
Can you change auto brightness delay ?

It takes about 30 seconds before brightness level become acceptable after passing tunnel during navigation. 30 seconds without GPS navigator because stupid auto brightness delay.

This is problem of all SGS2 kernels including stock.
[Galaxy S II Original Android Development] Molitro:
Maybe in CM is different. But in samsung roms is I as said. Around 6-700 ms to wake up, and nothing to do to avoid it.
[Galaxy S II Original Android Development] bala_gamer:
@ gokhanmoral,

there are some new gpu drivers released(dated 21,november 2011), will this be of any use to improve the performance of our graphics or fixing any existing bugs?

Here is the link.

http://www.malideveloper.com/developer-resources/drivers/open-source-mali-gpus-linux-kernel-device-drivers.php

And one more can the banding problem be solved? any idea about the problem?
[Galaxy S II Original Android Development] yoplaboum:
2.2rc2 works fine with criskelorom v31

good job
[Galaxy S II Original Android Development] gokhanmoral:
I will test them in rc3 but there is another big problem I am trying to solve before I release the kernel sources. once I solve them, I will release the sources first, and then integrate the drivers then release rc3
[Galaxy S II Original Android Development] yoplaboum:
Mirror updated : http://aideadsl.com/sgs2/kernel
[Galaxy S II Original Android Development] b2rdetor:
try dat

http://4pda.ru/forum/dl/post/1261358/update_Services_v2_XWKJ3_deodex.zip
[Galaxy S II Original Android Development] bgx:
Can't open that link :(

EDIT: OK, have it, after registration! ... Forget it! It works!
[Galaxy S II Original Android Development] droidphile:
Works fine here :) Gingermod 0.7 (ki3)

Have you tried voodoo screen tuning app? For users with SM2-A1 line screen hardware revision (most of us have that), the problem seems to be solved using M2 gamma preset in the app.
[Galaxy S II Original Android Development] bala_gamer:
Im having SM2-A2 as default, as of now it seems voodoo screen tuning app is only working with auto brightness it seems, but soon he will work it out.

Edit: Just tried the M2 preset, things look too much white washed and sadly banding is there, ran nenamark to confirm it.
[Galaxy S II Original Android Development] KennyLegend:
I've just had data loss using rc2. Started suffering bad lag and apps not opening. Reflashed the Rom and all is well again.
[Galaxy S II Original Android Development] NiceCarpet:
Hi there,

Could anyone please tell me how to disable the softkey lights under non-automatic brightness settings? I had them disabled before by running an old script by gangsterjoop that did the following:

echo 0 > /sys/devices/virtual/misc/melfas_touchkey/brightness
chmod 454 /sys/devices/virtual/misc/melfas_touchkey/brightness

The only problem is that now it no longer works with RC1/2 etc. My backlights stay on no matter what I do. I've tried pushing both '0' and '2' manually to no avail. I've also tried turning them off with 'screen filter app', but that, too, no longer works.

Does anyone know what files to edit to disable the softkey backlights under these new kernel versions?

Thanks for any help!

EDIT: Uh-oh, wrong thread! I was aiming for the Q&A thread here. If a mod could please delete this post, that'd be great. Sorry.
[Galaxy S II Original Android Development] droidphile:
SM2-A2 Line preset should give you a warmer temperature display if your hw rev is A2. A2 preset might be more green for you, but it should be comparatively the better preset.

Anyways supercuiro is reverse engineering to make our phones' display better. Let's be patient now and overwhelmed later :)
[Galaxy S II Original Android Development] wyco:
Hi,

I might be completely barking up the wrong tree in which case apologies.

Is there any way to include some sort of compatibility for iPhone-HEADSETS? (the ones with microphone and volume/answer button etc). I'm not experienced with coding of any sort but I'd assume that there should be a way to 'teach' the SGS2 to accept the commands coming from them.

[before someone pokes me about it, I don't want to buy a headset from Apple per se, but there are many good ones out there made by AKG or Sennheiser that only work with the i-products that I'd love to use!)

Thnx
[Galaxy S II Original Android Development] droidphile:
Yes you're actually barking up the wrong tree :p

This ain't a keylayout mod or app mod thread!

Afaik, volume button can not be made compatible to increase music player volume or whatever since it is a limitation in the framework. Answer button obviously can be used for pausing/resume, skipping the track, etc.

Semi-off topic, there are mods to prevent screen wake from headset button and phone's volume button.

(You actually thought "wow, a thread with 1.5 million views, someone will help me out", right? :D)
[Galaxy S II Original Android Development] wyco:
re 1.5m views: haha, no, not quite, I just assumed that if there is a way to solve the issue that must be via either programming it into a kernel or a ROM. So I posted it here because this is the kernel I'm using now :) [i appreciate i'm quite new here but not quite that new to online forums, which again i appreciate you don't know, and/but i try not to troll around with obviously stupid requests in the wrong place usually ;)]

As far as I've read about the issue, there seem to be random headsets which generate poor voice/music quality or issue with microphones because some of the internal cables are wired differently, so I guessed that could perhaps be solved in a software-mod :)

Thnx anyway.
[Galaxy S II Original Android Development] scorpion667:
Solved, seems CM7 has it's own brightness curve that I modified to my needs, seems to ignore the kernel values.

Live and learn!
[Galaxy S II Original Android Development] shr33kant:
Been getting random reboots while sending sms on rc2 today :O I think I'll be going back to RC1 till RC3 is released.
[Galaxy S II Original Android Development] buxz777:
sent you a nice long pm with loads of tips to turn your sgs2 into one hel lof a superb mp3 player with the single button functions you require from the headsets :-) ive also linked some wicked headphones , a wicked headphone adapter with mic and single button controller so you should be sorted :-)

peace :-)
[Galaxy S II Original Android Development] wyco:
Thanks! :)
[Galaxy S II Original Android Development] funkyirishman:
Hopefully right forum

Have the below Kernel installed

2.6.35.14-Siyah-v2.2beta3gm@ubuntu #24

When I launch CWM I get the below message

This version of CWM Manager should be used with CF-Root v5.0 or newer. It appears you are running a different kernel. Various Features have been disabled

I am on running the Ultra Toxic Rom

Is there anything that I need to to to this kernel to ensure all features of CWM will run as I am looking at flashing a Theme?

Thanks
[Galaxy S II Original Android Development] KennyLegend:
Flash the latest version of Siyah ;)
[Galaxy S II Original Android Development] planetf1:
were you OC/UV -d at all?
[Galaxy S II Original Android Development] timberwolf60:
Your phone was rooted with CF Root before because CF Root not happy you to change to other kernel. I had this problem as you.

Solution: Easy root/unroot :

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

1) unroot your phone by using Easy rooting/unrooting by DOOMLORD.

2) root your phone again fellow the instruction on the above link.

Finally used DARKYROM2 to flash siyak.tar.

Upon successful, you will have CWM V5 without warning triangle and binary counter not increasing.
[Galaxy S II Original Android Development] KennyLegend:
I was uv by 25mV om each step which is nothing really.

I'm back on rc2 now again and somehow it feels snappier than before. Might have been a bad flash too of course. I'm not moaning btw ... Just sharing my experience ;)
[Galaxy S II Original Android Development] bala_gamer:
Guys , i need some clarifications regarding overclocking and power consumption.

1.If our device can perfectly run @ 1.2 ghz with 1150mv, then why does the stock rom from samsung using more 'mv' to run at the same speed.

2.im running stable with 1.4 ghz @ 1250 mv (which is the stock voltage used for 1.2 ghz), Does that mean without an increase in power consumption we can run @ 1.4 ghz?

3. Does overclocking alone consumes more power or overclocking along with over volting increases power consumption?

As this thread deals more about ov/uv than any other, i thought it would be appropriate to post it here.
[Galaxy S II Original Android Development] droidphile:
1. Because different cpus are of different grade and stock voltages are safe and stable voltages for all. One device might work smooth on heavy uv, but another one might crash even at -25 mv.

2. Well power consumption directly proportional to frequency and directly proportional to square of voltage. So a lower clock saves more power than a higher clock running at lower voltage.

3. Over clocking consumes more power, so over volting with oc will increase consumption further.

Undervolting can not save considerable amount of power. But underclocking can, comparatively. (like setting lowest freq to 25 mhz and highest to 800 or 1000!)

Cpu isn't the biggest power drainer in our phones. It is our amoled display.
[Galaxy S II Original Android Development] scorpion667:
Clock increase consumes more power even if voltage is identical. I forgot the ratio but to be honest for me 1400Mhz @ 1275mv battery lasts the roughly the same as 1300Mhz @ 1225mv. The power usage is negligible. As the guy above me said, the screen is what rapes most of the battery.
[Galaxy S II Original Android Development] yoqxi:
Many devices do, but every phone is a little different, so Samsung chose a value that is guaranteed to work on every device.

No, voltage and frequency are both factors to the power consumption. The voltage is to the power of two in the calculation though.
[Galaxy S II Original Android Development] funkyirishman:
Can only see version Siyah-v2.1.1.tar so better to flash this rather than the beta version or am I blind or not looking in the right place to find the latest version

Possibly :o
[Galaxy S II Original Android Development] bala_gamer:
Well Thanks! This is what i thought it would be .. gr8 explanation..
[Galaxy S II Original Android Development] Raptor svs:
The part I put in bold type is wrong.

You said the reason yourself: The voltage V goes into the power consumption P as V², whereas the clock frequency f only linearly. So P ~ fV².

Now if you increase (just for the easy calculation) the clock by a factor of two, but lower the voltage by a factor of two, you end up consuming only 2*0.5²=0.5 times the power of the original setup. In short: if you can lower the core voltage by the same relative amount as you increase the clock speed, you will in the end save that percentage in CPU power consumption.
[Galaxy S II Original Android Development] droidphile:
Agree with you. But is it practical to have that 'factor' linear to frequency and voltage?

Consider 25 mhz at 850 mv

P=c*25*0.85*0.85 = c*18.06 [c=constant]

Can you match this power consumption on 100 mhz?

1) P= c*100*0.85*0.85 = c*72.25 [100 mhz at 850mv]

2) P=c*100*0.5*0.5 = c*25 [100 mhz at 500mv]

Even at 500 mv for 100 mhz, which is impossible, 25 mhz at 850mv saves more power than 100 mhz.
[Galaxy S II Original Android Development] NicoBD:
This is right, but if you just take a look at CPU Spy you will see, the phone is more often at lower frequencies. So the over all effekt of your bold text is right...
[Galaxy S II Original Android Development] bala_gamer:
How about monitoring the cpu temperature in our s2? AFAIK there is no kernel that supports this feature. Its been months no one talked about this feature. Does the s2 lacks the needed sensors in the diode to read temperatures or can it be still enabled via kernel?
[Galaxy S II Original Android Development] droidphile:
Our phone does not have a heat sensor on cpu. We only have the battery temperature sensor.
[Galaxy S II Original Android Development] olifee:
Because we can :P.

Seriously, I totally see your point. However, I do not know enough about dalvik's behaviour. If it does not even 'see' swap as free memory but only looks at the physical memory, zram will be just perfect, because it only reserves space if it is really used. For that reason, if dalvik really behaves like that, it should never become active in normal use, but only if you totally need it because you just loaded some super-cool memory-eating app (or started several servers on a chrooted debian and still want to run firefox and opera at the same time).

For such reasons, I would like to test it, and as an optional module, it will not hurt anybody ;).

As for zcache, that should be totally helpful. All free RAM is used for file cache in linux-based OS's by default, which is very nice, because memory-hotplugging is still extremely experimental with most setups and might save only a negligible amount of power (if it works at all on our phones). Using it as filecache is the best way to put it to some use.

So zcache should give us about the double size of the normal file cache for very small CPU overhead (as it also reduces the I/O by providing more cache, it might also save power and increase loading speed for bigger apps).

So I see most gains with zcache, but there are many unknown parameters, so it might be nice to just give it a try :).
[Galaxy S II Original Android Development] jgrimberg1979:
is there any way we can get this kernal for the sgs2 for art, i777? It would be so great to use this kernal.on our phones. I know alot of people.in the i777 forums would be very happy too!
[Galaxy S II Original Android Development] eastonfr:
When is rc3 out i thought it was meant to b out yesterday?
[Galaxy S II Original Android Development] Vaedryn:
It is out when Gokhan is ready :)

SGS II Cyanogen Tapatalk
[Galaxy S II Original Android Development] cmd512:
Exactly, if you took the time to read back just 1 page, you'd see gokhan is trying to implement a whole ton of stuff in RC3, including but not limited to brand new Mali drivers released on 11/21.

So like Kjetal said, wait.
[Galaxy S II Original Android Development] tolis626:
Well,not only that,but without proper utilization it will be totally useless. :)

Anyway,it will also be a nice way to put that pesky mmcblk0p12(or whatever the hell its name is) hidden partition.I imagine a speedy flash memory will do,eh? ;)
[Galaxy S II Original Android Development] olifee:
Didn't even think about that, but might be a nice idea in case we need even more RAM than zram in physical memory can offer ;). But that will then be an option for the 'special' users doing non-phone-stuff with their phones, I guess.

I am not sure about the block-device backend-support in current zram (it is mostly used for in-RAM-swapping). It seems there are plans to supersede zram as backend for swapping with frontswap+zcache (frontswap will also use zcache as backend for swapping to compressed RAM and work without limiting it's size by automatically growing / shrinking).

My desktop-setup currently uses one zram for each cpu-core available (of course, I do not use cpu-hotplugging there) and only swaps to disk if all are completely filled (which might happen once a year or so :P ).

EDIT: By the way, the zram-developers recommend zram for embedded devices to reduce I/O-load and wearing (in case you really need to swap on flash).
[Galaxy S II Original Android Development] tolis626:
Well,my rig got nothing but RAM,so I didn't exactly ever need it... :p

But anyway,we will surely not need in the forseeable future,but sometime there will probably be need for it.Be it heavier games,launchers,newer os,whatever. ;)