yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Tye:P:
@ pikachu01

Hi. You seem like you might be the guy to ask.

Do you know how to mount an external HDD as writable?

Can I do this through the terminal and if so what commands do I have to enter?

I keep getting device or resource busy when I try to:

mount -o rw,remount dev/block/sda1 mnt/ntfs/sda1

Is this even close to being right?
[Galaxy S II Original Android Development] ndnesh:
HI, with 3.2.1 and with 3.2 and with 3.2rc2, i am getting lines on the right hand side of the display. I have tweaked a everything that was on offer in Extweaks, however i still have those lines in the medium to low brightness settings. This was not there in 3.2RC1.

Reverting for now :(

Played around the settings in Extweaks more, and reverted all GPU voltages to 3.2RC1 settings, however i can still see the white lines . Reverted to 3.2RC1.

I dunno what else has changed in the screen or GPU Settings which can cause this.

If someone can look into this, ill be very grateful. I always use the default profile, and dont do any tweaks.
[Galaxy S II Original Android Development] LogeshMenon:
3.2.1 has significantly lower cf bench score compared to 3.2

Any ideas. Any input on battery life of 3.2.1, is it better?
[Galaxy S II Original Android Development] Tye:P:
Benchmark scores (especially synthetic ones) are only of limited value and should be used as just a guide. I wouldn't put too much faith in it.

It's too early to be sure about the battery; most recommend at least one full discharge cycle and even then unless your testing methodology is by the book it's subjective at best.

I'd say it would be as good as always (nearly) if I had to put money on it.
[Galaxy S II Original Android Development] gcrutchr:
@gokhanmoral

Here is slogan for your kernel:

"Tuned to perfection"
[Galaxy S II Original Android Development] bala_gamer:
the solution was there in previous pages, seems you guys havent read it.

anyway, beta 5 dont have recovery.

1.download the tar version of beta4.

2.flash it via mobile odin or pc odin

3.read the pros and cons before flashing betas :)
[Galaxy S II Original Android Development] ROHIT345:
Beta 5 was reuploaded and there is no missing recovery now in the reuploaded version.

edit: redownload beta 5
[Galaxy S II Original Android Development] drigz08:
Is proximity sensor broken in b5? Is it just me? please test it, when I received a call, answered it, placed near my ear (2 mins call), when the call was done screen does not turn back on, but I can see proximity sensor still lit up and I can still hear charging tone when I plug the charger.

Edit: Using stock DXLP7 rom
[Galaxy S II Original Android Development] crazykamui:
drigz08 /////

I am same

Cyanogen9 last nightly 3/22
[Galaxy S II Original Android Development] brenogbi:
Why my cel dont go to deep sleep? The bat r drain to fast !!

Sorry for my bad english
[Galaxy S II Original Android Development] zekurosu:
Take the battery out for a minute or so... that should make yer phone able to sleep again

Sent from SGSII powered by CM9
[Galaxy S II Original Android Development] bala_gamer:
is anybody having problem mounting internel sd in usb mass storage mode? only the externel sd gets mounted in mass storage mode.
[Galaxy S II Original Android Development] gokhanmoral:
there will never be a paid version of my work. if it was my work only then maybe I would make something paid. but this kernel is more linus's than it is mine :) I am not going to make tiny changes here and there (that's what I do) and use them to promote anything paid. everything you need about this kernel is free and will stay so.

not yet. I haven't started to modify the existing code much. I have only added the old-known functionality until now. I am planning to add ondemandx behavior to ondemand in beta7.

exactly. I have disabled CFS tweaks and that helped. also, I reverted some config changes which were effecting performance.

I think I know the reason. I will try to add it back in beta6.

it's also in my todo list. I will add another mount menu. you'll have both mount internal usb storage and external usb storage.
[Galaxy S II Original Android Development] drigz08:
That's a quick response. How about the proximity sensor for long calls (more than 2 minutes)? Screen does not go back on.
[Galaxy S II Original Android Development] gokhanmoral:
in my list but I haven't tested it yet.

good news: I fixed the MTP problem.

now I will send a test version to a friend who uses Samsung rom to test it...

The solution is easy and effective: I made that part a kernel module. and just used the same code to make two different modules, load them in pre-init depending on the ROM type.

nothing fancy, but effective. I'll try to solve the problem with my linux vm (push over https) and then push the changes. sorry for the delay but I don't want to use bitbucket this time. and I can do it on windows, so the problem is not with github or pushing over https... anyway.. test-time.
[Galaxy S II Original Android Development] Marchief:
Nut sure if you can do anything but bln doesn't activate for SMS or the stock email program, have an exchange account setup. Omega ics 5.2 stock.

Swyped from my Samsung Galaxy SII using tapatalk
[Galaxy S II Original Android Development] gokhanmoral:
you should ask it in omega ics thread.
[Galaxy S II Original Android Development] coloxim:
you can make two different kernel ...one for cm9 and one for samsung rom..is not better?

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] AvRS:
It's not better, it's more work. If it was me I would only develop for what I use but lucky for most this is Gok and he likes to support both and is doing so freely.
[Galaxy S II Original Android Development] gokhanmoral:
no, it is not better for me.

but it is easier, for sure.

I want to have dual booting. it's been my dream for a long time. there are already some implementations but I want to implement it myself and I want to have both CM9 and Samsung ROMs on my phone.

there is also an easier solution for that: make an app which flashes two different kernels depending on the user's choice. it is an easier solution but not better.

simple is good, but not always better.
[Galaxy S II Original Android Development] rlorange:
Gokhan: would it be possible to add Szupty's USB host driver?
[Galaxy S II Original Android Development] gabx:
LCD density

I like using 200 dpi as LCD density.

I don't want to use any external app, so I use this following tweak in CM9:

in /data/local, I created a file local.prop with my custom settings:

qemu.sf.lcd_density=200
ro.sf.lcd_density=200

So these settings are permanent, even when I flash a new update. I place too in this folder any customization like another bootanimation.zip, ringtones folder.

Using your kernel prevent this file to rule, and I am back to 240.

I tried to weak your /default.prop file with adding my two lines, but it doesn't work as when I reboot the device, iniramfs create a new clean one whitout my customization.

I can write these dpi settings in your default. prop inside the unpacked initramsf folder, then repack zImage, but each time I will update your kernel, this trick will be lost.

I know I can edit manually the /system/build.prop file, but here again, each CM9 update will break the trick.

Do you have any idea about a workaround? Why Android can't rule anymore my /data/local/local.prop file with your Kernel?

TY for any help. I am sure it can help other users.
[Galaxy S II Original Android Development] arkadius41:
Hi Guys. Is this kernel rooted ? Does it fit to XWLP2 ? Sorry for maybe stupid questions ;)
[Galaxy S II Original Android Development] amozonesk:
oh god.
[Galaxy S II Original Android Development] Crescendo Xenomorph:
Hmmm, my min off freq is at 500Mhz by default. And all lulzactive parameter (using lulzactive program) is default now. ;)

What's the recommended parameter for lulzactive? the best for performance but not too battery eating when gaming?

I got the best battery since v3.2. Only 2% drop overnight. Also no more freeze and SOD since v3.2.

Now using and testing v3.2.1....
[Galaxy S II Original Android Development] shawnaye:
And at the same time could someone share a parameter for battery as well as reasonable performance?

Because my cpu is still sticking at 1000mhz too much for my liking and I've checked bbs according to pikachu and found nothing that could cause the issue.
[Galaxy S II Original Android Development] Crescendo Xenomorph:
What version are you using?

I never check about the CPU time, but its very battery friendly since v3.2. Now I no need to take my charger/spare batt with me. This is real and true! :cool:
[Galaxy S II Original Android Development] hellsgod:
atm i play with the lulzactive settings, so here my temp. settings:

inc_cpu_load: 75%

pump_up_step: 1

pump_down_step: 1

screen_off_min_step: 11, @500

up_sample_time: played with 10000, but atm its on 15000

down_sample_time: 40000

No lags, no freeze, gaming no problem. With this settings every step in the table will be used.

hells
[Galaxy S II Original Android Development] Crescendo Xenomorph:
Sorry, you are limited to 8 thanks per day.

Thanks, I'll try this and will get back to forum with result... :)
[Galaxy S II Original Android Development] shawnaye:
using 3.2 haha, i keep checking because 1000mhz is just occupying like 80% when im just texting.

shall try this as well and revert!
[Galaxy S II Original Android Development] akira888:
A mate recommended:

up_sample_time: played with 20000

down_sample_time: 60000

Don't know the difference though....

---------- Post added at 02:20 PM ---------- Previous post was at 02:18 PM ----------

AOKP's quick torch feature caused torch wakelock in the previous Siyah's releases.

Not sure if it still presents?:confused:
[Galaxy S II Original Android Development] hellsgod:
The difference is that the cpu is not scanned so much with 20000 than with 15000, and the cpu will not scale down so fast with 60000 than with 40000.

so... its up to you whats better ;)

you can set inc_cpu_load: to 90% and set up_sample_time to 10000, so the cpu will be scanned very fast and can scale up without lags at 90% load.

hells
[Galaxy S II Original Android Development] II_DiE_4:
Actually i have this lines also on different kernel if the brightness is low and white background.

I just thought its a problem with the screen on these brightness lvls.. Dunno if some1 has an idea.
[Galaxy S II Original Android Development] akira888:
have you guys ever come across such situation where your phone suddenly becomes extremely slow to an extent that you need to force reboot?

I don’t think the phone freezes, it is just very very slow. So no operation is possible.

using sitah v3.2 lulzactive, noop, 100-1200

some tweaks in extweaks and lulzactive, UV in CPU & GPU

any clue, folks?
[Galaxy S II Original Android Development] Geekeek:
Hello,

Pardon the extremely noob question but I just got I9100G replaced with I9100. Running GB XWKL1. (India)

Can I straight away flash this kernel or do I need to root with CF-Root first and then install with CWM? Asking because I read there are compatibility issues. Basic idea is to use ICS. Thanks for the help!
[Galaxy S II Original Android Development] kwerdenker:
If your target is battery, you also might consider using a pump down of 2. That way it scales back faster to the lower frequencies on a reduced load.

Sent from my secret moonbase via space carrier pigeons
[Galaxy S II Original Android Development] omniwolf:
you guys should take the OT to the IRC channel (deets in the first post) :P

siyah is auto rooting, you shouldn't have to use CF root first.

having said that, i think pretty much all SGS2s are on ICS now officially? we even have it here on all networks in australia!
[Galaxy S II Original Android Development] akira888:
But my CPU frequency range is 100-1200, how come it would go down to 25?

Also I am using the below:

inc_cpu_load: 75%

pump_up_step: 1

pump_down_step: 1

screen_off_min_step: 11, @500

up_sample_time: 20000

down_sample_time: 60000

Would the above setting in lulzactive cause problem?

thanks
[Galaxy S II Original Android Development] kwerdenker:
Sorry, double post because XDA app acted up

Sent from my secret moonbase via space carrier pigeons
[Galaxy S II Original Android Development] eric-filth:
+1

Enviado do meu GalaxyS2 usando Tapatalk 2.1
[Galaxy S II Original Android Development] gokhanmoral:
there is absolutely no change in scrolling or any related part.

i only modified battery profile a bit and increased 267MHz voltage to 1000mA.

if you are using the battery profile, you should fix it yourself: either don't use it or adjust GPU frequencies. otherwise, 3.2 is the same as 3.2.1 in every way related to scrolling.
[Galaxy S II Original Android Development] cedric123:
i flashed miui to secondary rom but now i cant boot to secondary????? im on kernel 3.2.1 pl help send via pm thraeath cant follow
[Galaxy S II Original Android Development] liamR:
Did someone get Wi-Fi Direct working properly with this kernel ?

I can find my other devices but can't send files etc...

I have to have Wi-Fi Direct but hate to move to another kernel.

Thanks
[Galaxy S II Original Android Development] altinxh:
Please can U share your extweaks and Nstools in details?
[Galaxy S II Original Android Development] EARNEST_EU:
Yep, played around with values, 0..20 range. The result is the same. It is not as smooth as before.

Also, something weird had happened. My battery stopped charging at 83%. Reflashed kernel to CM9 and the charging continued.
[Galaxy S II Original Android Development] coloxim:
Who have a good battery life use 3g?

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] rlorange:
Actually yes I did get this. It seemed to happen when my wifi went just out of range
[Galaxy S II Original Android Development] OGroteKoning:
I don't know if this is kernel related, but last night I loaded 3.2.1. I had a 7hr 50mins Powersave wakelock. The phone never went into deep sleep. Over and above normal reboot, I rebooted just before going to sleep. This morning my alarm did not go off although it was set to go off. I suspect that it could be because of the minimum 100 MHz freq, but I could be way off base. After rebooting this morning after this incident, I rebooted again and left the phone for a while. (i had to go ****-shave-shower-and-shampoo for work ;) ) When I got back, CPU Spy indicated that the phone went into deep sleep.
[Galaxy S II Original Android Development] Jigen90:
Great Gokhanmoral, awesome work!

Could someone post a simple guide to activate BLN in CM9?

In extweaks settings "BLN test" works, btw as soon I receive a sms, call..it doesn't

Have I to install BLN Control, NSTools or Light Flow?

I read this topic, searched BLN and CM9..but I didn't find a working solution.

If someone knows how to get it work correctly in CM9, it will be appreciated!

Thank you!

(I'm using latest cm9 0509 and latest siyah 3.2.1)
[Galaxy S II Original Android Development] pikachu01:
Dump the whole log. A PowerManager lock means an app is causing the partial wakelock.
[Galaxy S II Original Android Development] OGroteKoning:
TB was scheduled to run early this morning - it was probably that.

Okay ... I messed up - I disabled the logger for some silly reason so I don't have a log to produce. Sorry! :o

But I will monitor the situation and enable the log so if does happen again, I will post the log.

EDIT - Is there a list of wakelocks somewhere I can download to study? (I will do a search too, but assistance here will help)
[Galaxy S II Original Android Development] eric-filth:
Sorry gokhan im not specified from what version i came. Was RC2.

RC2 is a lot more fluid and smooth scrolling than 3.2.1

Enviado do meu GalaxyS2 usando Tapatalk 2.1
[Galaxy S II Original Android Development] akira888:
Looks like it is caused by lulzactive governor?
[Galaxy S II Original Android Development] pikachu01:
From BetterBatteryStats :)

Dump the log from there. You can download it here:

xdaforums.com/showthread.php?t=1179809
[Galaxy S II Original Android Development] EARNEST_EU:
I don't know. But that is the fact. Maybe voltage change is the reason? Also, why do you mess around with voltage and clock speed? What's the reason for changing it? Personally, I would prefer if everything set "by default"
[Galaxy S II Original Android Development] SergeF1:
im on ParanoidAndroid which es CM9 with some addons...for BLN to work just need ExTweaks and Nstools nothing more...

What i did:

Settings, ADvanced, Sensors, tick "Enable Keys Backlight" then untick (lights will be always off with this)

Go to Extweaks, BLN, Activate BLN, notification timeout whatever you want (mine is 10 minutes), Blinking effect (breathing is also possible :P), led timeout 1.5 sec (now keys will be active while screen on just 1.5sec, you can select other of course) test, apply changes.

Go to Nstools, settings, select set on boot and NSTools service (both have to be active).

That's it. eveything is running perfect for me, sms, calls, everything.

PS: I noticed that SMS notification is on by default, i didn't cahnge that. Don't know if that make some difference.
[Galaxy S II Original Android Development] leongwenjun:
sometimes it like to lock to 800mhz , damn it , all governor & rom also like this.
[Galaxy S II Original Android Development] shawnaye:
My CPU just doesnt listen, maybe it's taking time to get accustomed to 18 steps.

but it's just always sticking to 200 500 800 1000 like it's always used to.

https://www.dropbox.com/s/g31yl2dqkwfm9hu/Screenshot_2012-05-11-17-54-10.png
[Galaxy S II Original Android Development] SergeF1:
All the steps have some time according to your screenshot...don't you have a governor which scale 2 steps after threshold or something lke that selected? maybe lulzactive with 2 step pump up?

Have you tryed with ondemand or conservative for example?
[Galaxy S II Original Android Development] kwerdenker:
I think ondemand will reinforce the problem even further because of the smooth scaling, which tends to scale as fast as possible to it's target frequency. luzactive with 1 step up should be more than sufficient to use all available steps.

Concerning the 500MHz and 800MHz: if you touch the screen, the CPU automatically scales to 500MHz, so a high statecount is normal. Same thing for 800MHz, since it's the frequency that gets selected for going into and waking up from sleep. For me, 800 also seems to be the most sufficient step, since my phone rarely goes to 1000MHz in normal scaling operations.
[Galaxy S II Original Android Development] shawnaye:
hmm, i am using lulzactive, but my pump up is 1 and pump down is 2, when i look at cpuspy it just feels like the other frequencies are being avoided somehow.

not like other people whom have evenly balanced frequency states.

yeah, ondemand is even worst! haha. i really like lulz because i can use the lulz settings, i was previously on noop+ Conservative a long time back but decided to make the leap. basically, the phone usage you saw there, was typing messages, using chrome, XDA~ing with you chaps.

So i really dont know what can explain the high frequency. oh btw, all background apps/games are practically killed except for those mentioned.

Thanks for your help guys, really appreciate it.
[Galaxy S II Original Android Development] rlorange:
Possibly I do use lulz
[Galaxy S II Original Android Development] rlorange:
Shwane. That pump down 2 is the problem. Use a faster down sample if you want both even frequency use and quick ramp down.
[Galaxy S II Original Android Development] KennyLegend:
Wow ****... proof just how much battery FB app uses
[Galaxy S II Original Android Development] kwerdenker:
My lulzactive config is as follows:

Inc CPU load 70%

Pump up 1

Pump down 2

Screen off min 800MHz

Up sample time 20000µs

Down sample time 40000µs

As you can see from this screenshot, I get fairly the same results as you do with a similar work load. I guess this is the normal modus operandi for lulz :)
[Galaxy S II Original Android Development] shawnaye:
i'm using SIO+Lulz, you?
[Galaxy S II Original Android Development] kwerdenker:
That's why I have replaced it with FriendCaster a long time ago. Better design, faster load, better PUSH notifications and a whole lot less battery drain :)

But this is again a good example why most of the battery drain issues are due to apps and not the kernel.

noop, but the I/O scheduler makes no difference to the frequency scaling. that just orders the requests made to storage elements.
[Galaxy S II Original Android Development] toinktoink:
quick question, why didn't i get the 3 seconds timeout after installing the 2nd rom.
[Galaxy S II Original Android Development] shawnaye:
le sigh.. then what can allow the frequencies to scale more smoothly..
[Galaxy S II Original Android Development] MyLifeRocks10:
did u format secondrom data and secondrom cache before installing 2nd rom?
[Galaxy S II Original Android Development] kwerdenker:
Your frequencies do scale smoothly. It's just that the in-between steps don't satisfy the needed processing power for the current load and so the scheduler jumps to the next step. You could try to force longer stays on a step by increasing up sample time and set inc cpu load to 90% or something. Just don't expect a smooth and lagfree operation with this type of setup :)

Also, concerning your 100MHz step is never used: did you setup 100MHz as a min-freq in voltage control, nstools or whatever config tool you use?
[Galaxy S II Original Android Development] pangiotis24:
With latest version I have big boot_hsic wake lock.what is this?
[Galaxy S II Original Android Development] hughfollett:
Hi guys! Maybe this is a silly question, but I want to learn something, so here it is: I'm using some custom voltages with voltage control app, is it safe to flash a newer version of siyah without resetting them before? And will those values be resetted after the flash??

Thanks in advance!!

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] KennyLegend:
Yeah thats why I posted it. Just to give people an idea. I could have just as easy said "this kernel is ****...drains my battery like f**k".

O/t... while friendscaster isn't bad I find that I miss posts with it and it just doesn't give the same experience .

FB app still is the most complete package but drains bad. Check the CPU usage in task manager !!!
[Galaxy S II Original Android Development] Ankit Tulsian:
Yes its safe to flash and it will get reset to default siyah values or stock values.
[Galaxy S II Original Android Development] shawnaye:
hmm, my frequencies are 200-1000 haha, therefore i dont have 100 shown.

hmm, i might just try that!
[Galaxy S II Original Android Development] toinktoink:
thanx man, at first i didn't, but eventually tried it before reading your reply, thanx though :)
[Galaxy S II Original Android Development] Hagis:
Same here but on service center they say it is normal amoled symptoms. It is only visible on lowest brightness setting

Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
[Galaxy S II Original Android Development] rauschkugl:
it won't get reset. the undervolting in vc app will stay as it was set up before.
[Galaxy S II Original Android Development] sefrcoko:
try it with 3.2.1...rc1 is 3 versions old.
[Galaxy S II Original Android Development] sefrcoko:
enable or disable wallpaper scrolling then change it back again. This solved it for me in Apex launcher.
[Galaxy S II Original Android Development] ToucherCD:
waiting wipe/factory reset for second ROM :)
[Galaxy S II Original Android Development] naveediftikhar:
Woooh..i jus got a wlan wakelock of about 30 mins jus like that..iam having a brilliant battery life with my own settings of about 2hrs 30mins with 58percent still left but with this walelock my battery jumped down to 35% in about 30mins..the prob last time i remeber this wakelock was solved..ao can anybody help me to get rid of it..ive gone through droidphiles xplanation of this but that didnt help me...iam using latest siyah with wanamlite 11.5 ondemand-sio 100-1000freq with gpu n volt uc's,uv's..!

P.s my wifi is on all the time!