yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] :
Only if they mess up with anything: init.d undervolt freezing, etc...

---------- Post added at 07:21 PM ---------- Previous post was at 07:19 PM ----------

check out: /sdcard/clockworkmod/blobs, something like this. I don't remember the path very well, but now backups are stored this way, in a very disorganized way. Much better making backups with tar.
[Galaxy S II Original Android Development] jgcaap:
Found the explanation. For Me is working great but itll Trust the dev hehe thanks
[Galaxy S II Original Android Development] MySeLfPT:
Hello everyone,

Sorry if this has been already answered countless times but there are way too many pages to read.

Does anyone have a DSPmanager working in CM9 or any other equivalent app that equalizes system wide in CM9?

Thanks in advance,

MySeLf
[Galaxy S II Original Android Development] Mohamedselim:
Dspmanager is buit in all cm roms as i know i use it in cm10 now search market by term equalizer and you will find lots of apps try some until you settle with one
[Galaxy S II Original Android Development] ksilver89:
Hello guys, is anyone know how to execute this command in gesture script? I found this line in GlobalActions.java. I'm trying to toggle expanded desktop in ParanoidAndroid rom with gesture, it'll save a lot of time switching out between fullscreen apps.

Settings.System.putInt(mContext.getContentResolver(), Settings.System.STATUSBAR_STATE, Settings.System.getInt(mContext.getContentResolver(), Settings.System.STATUSBAR_STATE, 1) == 1 ? 0 : 1);
[Galaxy S II Original Android Development] ba32471:
Problems

I have Siyah 4.0 on StockRom XXLPT GALAXY S2

I have following problems, don't know if problems are in charge of kernel or rom.. :eek:

- As soon as i connect my galaxy S2 to my car in Bluetooh, the bluetooth sharing program crashes than everinthing works

- No more Usb host Feature

- No more hdmi out feature..

Thanks a lot..

Graziano
[Galaxy S II Original Android Development] shawnaye:
i think we should set this question out there.

What schedulers are you guys all pairing with pegasusq?

default is cfq but i always switch over to sio. got freezes on 3.5.2 and 4.0.1 wondering if linked with scheduler.

shall try default i guess.
[Galaxy S II Original Android Development] MySeLfPT:
Dsp manager does not work with syiah kernel in Cm9 AFAIK. I have it installed, it does not work.

Thanks for feedback.
[Galaxy S II Original Android Development] arunreturns:
Hi

Am on 4.1 rc1.. My phone reboots suddenly and battery drops from 70 to 17 after that reboot... Any ideas???

I tried this both AOKP as well as Samsung.. The ROMS i use are in my sig

Any help would be appreciated
[Galaxy S II Original Android Development] timberwolf60:
Tried run extweats > misc > removed root with auto install root ticked on both rom, then go for further testing.

I had no problem on this kernel as my tapatalk signature.

Send via my GT I9100 using Tapatalk2,

1st ROM , RR JB 3.0.4,

2nd ROM, RR 2.6.1,

Siyah 4.1 rc1, SuperSU Pro
[Galaxy S II Original Android Development] nitinvaid:
Its working I use it:)
[Galaxy S II Original Android Development] BlackRainX:
Will be ever there a both GPU versions?..?
[Galaxy S II Original Android Development] pangiotis24:
when gokhan solve the problem which was causing reboots and kernel panics he will release a stable version with 4 gpu steps
[Galaxy S II Original Android Development] Tungstwenty:
I just answered in the gestures thread, please check the response there.

---------- Post added at 11:24 AM ---------- Previous post was at 11:06 AM ----------

Gokhan,

Two DEV-related questions :)

1. I noticed that on 4.1rc1 adb is once again secure and requires "adb root", unplug/plug. Is this by design, or slipped back in after an update?

2. Even without the 4th step for GPU and the additional frequencies, there's still plenty of freqs to choose from in ExTweaks (8). However, and unlike what happens for the CPU, there's no way to change the frequency and not worry about the voltage, using the stock value appropriate for the new frequency. The only thing that exists is the description of the GPU pane that mentions the stock voltages for the default frequencies: 160, 267, 267.

Would it make sense to put in ExTweaks not the absolute voltage (since I recon the xml schema does not support conditional values for the V params based on the selected F's) but rather a delta - like the one in CPU altough perhaps for each of the 3 or 4 steps individually? Example: 0, 0, 0 - no undervolt / detault voltages for whatever freqs have been chosen; -25, -25, -50 - undervolt values for each of the steps, etc ...

I'm not sure whether this makes sense, because there might not be any "stock" or "default" values for the GPU, and in that case it's really only a matter of experimenting. If so, my question is whether permanent damage can happen if "bad" values are used for the voltages.

I noticed this when thinking about reducing the 1st level to 40MHz and then remembering that I should somehow probably adjust the voltage to something different than 950mV, but didn't know what to.
[Galaxy S II Original Android Development] dannykul:
Check out this post: https://plus.google.com/103583939320326217147/posts/L5aVZe7C9vg, provides explanation on CWM 6 Backup methods (and more importantly how incremental backups work with Blobs).
[Galaxy S II Original Android Development] robertobsc:
Hi Thungstwenty!

I may be wrong, but I think gpu steps have a different concept then cpu steps.

Stock samsung steps are 160/267 with the default voltages that appear in extweaks. There isn't a table of voltage values for each possible step like cpu. In Siyah, It has a table of voltages but for 3 default steps.

Of course, a table of voltages to each step could be implemented, but we get another problem. The minimum voltage is 800 mV, and that's really the minimum stable voltage. I changed the code to undervolt to 750 to associate with 40 Mhz, but the system became unstable. I know fluxi was able to put the minimum voltage to 700, so I don't know if something else should be changed to get more stability in such low value or if 700 works in aosp and not in Stock samsung...

It is strange, because steps from 40-100 works just fine on 800, but 40 doesn't work with 750.

To resume I think that gpu voltages hasn't a good range to play like cpu. The undervolt is more limited. I don't think it's worth to mess with it.

Enviado de meu GT-I9100 usando o Tapatalk 2
[Galaxy S II Original Android Development] Tungstwenty:
If that's the case, then 800 would be the right voltage for 40MHz :)

Anyway, according to your information there's no such thing as stock voltages for each frequency, only the minimum and maximum values which are global. Each of us must therefore experiment for every single step and find the voltage that keeps it working under stress, and ExTweaks cannot provide a "0" delta because there are no reference values for all steps.
[Galaxy S II Original Android Development] MySeLfPT:
What versions of those are you using? Which player do you use. Is the sound equalization having effects system wide?

Thanks in advance
[Galaxy S II Original Android Development] nitinvaid:
after 3.5.x all versions works for me

I use jetaudio first then pause music

then use any player u want dspmanager bassboost equalizer all works....
[Galaxy S II Original Android Development] panosfx:
I have omega v15,1 anad siyah kernel 4.1 rc1.

I paid for extweaks plus but my English it's not so good can anybody help me to set a good battery profile and one profile for perfomance?

If you don't want to post it here maybe you can p.m. me.

Thank you very much!
[Galaxy S II Original Android Development] karlesg:
Just like previous beta's pegasusq doesn't hotplug properly.

With the siyah default hotplug thresholds (hotplug freq up/down 500000/400000 - hotplug rq up/down 400/400)

the second core is pretty difficult to turn on so the first core spends much more time at max freq. If I remember correctly from various measurements that have been made, battery-wise it's better to have 2 cores working at 500 MHz than have 1 core working at 1 GHz.

But although the second core is turned on with difficulty, once turned on it almost never turns off while screen is on! For testing purposes I raised my screen off time out period to 1 minute to check the behavior of hotplugging... If the second core is turned on and you leave your phone for 1 minute without touching it, the phone remains still at lowest frequency, but with both cores on! If you turn off the screen and turn it on again, only then the second core is turned off. So this isn't normal and this isn't a proper behavior of hotplugging. In 3.x versions pegasusq hotplugged properly and didn't have this odd behavior. I don't know what is changed in latest versions.

Also imho the hotplug rq up/down thresholds must be lowered a little to 350/350 or 300/300 or 350/300, so that the second core turns on more easily.

Anyway if you want to see and have a proper hotplugging behavior, switch to ondemand.
[Galaxy S II Original Android Development] yahyoh:
dsp manager work here on ( apollo -jetaudio-play music ) without any problem
[Galaxy S II Original Android Development] :
I could use MONO sound, sometimes I share my headphone, so... you know :)

offtopic: know any equalizer to get mono sound?
[Galaxy S II Original Android Development] nitinvaid:
use poweramp it has a option i think or jetaudio
[Galaxy S II Original Android Development] jomaga:
Yes, poweramp has a mono option in tune/equalizer settings
[Galaxy S II Original Android Development] apk_xiz:
Hi OP your kernel 4.1rc1 have a huge problem with 3D games lke samrai vs zombies defence .while playing svz it lags like hell but on stock kernel or siyah 3xxx it runs butter smooth. And also it takes 5 secionds to show recent apps (by long pressig home buttion) but on siyah 3xxx it take only 2 secionds . Lls fix it :/
[Galaxy S II Original Android Development] Many40:
I'm answering to potentially DEV question :)

I'm also on 4.1rc1 and:

1. Haven't played these games but especially for your gonna download them and spend a while to check if it's really kernel related;

2. Time for recent apps to pop up - 1 s.

Regards
[Galaxy S II Original Android Development] vitoski:
I can confirm that. Even though I tweaked pegasusq so that hotplug_freq_1_1 is 400 000 and hotplug_freq_2_0 is 300 000 and hotplug_rq_1_1 350 and hotplug_rq_2_0 is 200, the second core goes offline only after I turn off the screen.

What's more even if I set up the Smooth scalling to 1000 Mhz with 1200 Mhz max frequency, then mostly my phone works on 1200 while simply swithing between screens or opening small apps like MyCars.
[Galaxy S II Original Android Development] apk_xiz:
for 1 ) i played that game like 4 months (from ics 4.0.3 to 4.0.4 [always stock roms]) and not had a single lag till siyah 4.1rc1

for 2 ) 1 sec i this it is 1 s(but when playing big games it drops to 2 s ) but 5 s is tooo much

---------- Post added at 10:50 PM ---------- Previous post was at 10:44 PM ----------

i will wait Till OP's latest build ,untill i will stay away from 4.1rc1 (due to too much lags [might be rom incompatibility {just like camera bug with siyah 3xx}])
[Galaxy S II Original Android Development] nitinvaid:
Is there any way that I can switch to default Samsung light sensors values
[Galaxy S II Original Android Development] aljo00:
Hmm, siyah has removed rc1....

So rc2 on the way :)
[Galaxy S II Original Android Development] Manitax:
Is still up

http://d-h.st/E5G

11 hours without a freeze or random reboot. Rc1 seems to have fixed that.

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II Original Android Development] gaz617:
Lux Auto Brightness from the Play Store is a great app you can use to adjust light sensor values. Samsung defaults are 0, 10, 100, 1000, 10000, 16000

---------- Post added at 07:39 PM ---------- Previous post was at 07:16 PM ----------

In my opinion (and on my device) Ondemand governor, cfq scheduler and Linux Kernel defaults hit the sweet spot. I know peasusq is kinda gokan's pet project but it's never worked that well for me.
[Galaxy S II Original Android Development] yahyoh:
yeah ondemand better imo + cfq or deadline or sio
[Galaxy S II Original Android Development] panosfx:
Anyone?
[Galaxy S II Original Android Development] tendan:
:banghead:

Go to http://xdaforums.com/showthread.php?t=1658647
[Galaxy S II Original Android Development] It_ler:
This is the wrong thread - non-dev stuff should be posted here => http://xdaforums.com/showthread.php?t=1658647

Have a look here for a good and battery friendly profile => http://xdaforums.com/showpost.php?p=26755476&postcount=850

(MagicConfig from geko95gek !)
[Galaxy S II Original Android Development] cybernetus:
Freeze with the rc1 charging the phone.

Min scale 100mhz

Max 1200mhz

Smooth 1000 / zram 150 / default profile

I believe the problem is the min scale.

last_kmsg: http://pastebin.com/ABVbd0gT
[Galaxy S II Original Android Development] sgs2.5:
I switched fom 4.1beta6 to 4.1rc1.

My S2 became blazing fast again. Mobile data seems much more stable and 1000% faster. Much less forced closes too.

My rom is Resurrection Remix 3.0.4.

Hats off to GM ! :cowboy: :good:
[Galaxy S II Original Android Development] CamoGeko:
^Mobile data has no relation to the Kernel mate. Must be placebo.

Sent from my HTC One X
[Galaxy S II Original Android Development] mrbluesman:
Ok so as I didn't trust these 16mb backups I thought I'd test it,

1. Backup with cwm 5

2. Upgrade kernel to rc1

3. Backup with cwm 6

4. Wipe data factory reset

5. Wipe cache

6. Wipe dalvik

7. Restore cwm 6 backup

8. Errors restoring data

9. Restore cwm 5 backup

10. Restore completed successfully

Staying on SiyahKernel 4.0.1 for the time being
[Galaxy S II Original Android Development] sgs2.5:
Either that or mobile coverage @ work reaaaaaally sucks (trying this at home now).

Anyways, VodafoneNL was down this afternoon too. Perhaps they got a new data plan ;) My mobile performs at Wifi speeds now (with WiFi turned off, or is it?)
[Galaxy S II Original Android Development] CamoGeko:
Lol

Maybe you meant to say that wifi is working better for you now...

Sent from my HTC One X
[Galaxy S II Original Android Development] rauschkugl:
The recovery on rc1 doesn't work really well. would be great if you could switch back to the recovery version of 4.0.1 until they fixed it. I wasn't able to get a working backup with it.
[Galaxy S II Original Android Development] Gillion:
I can confirm. Backup fails. RC1
[Galaxy S II Original Android Development] :
I'm pretty sure my signal never failed in my pocket, until now. It's been sometime since my signal goes from 4 bars to nothing in my pocket. Don't know if it's the freaking RIL from CM10, screwed SIM card, srewed carrier, kernel, modem, don't know.
[Galaxy S II Original Android Development] jgcaap:
Did you make a new backup with cmw 6?
[Galaxy S II Original Android Development] #illidan:
Got a kernel panic on RC1 while it was in deep sleep. There are no issues when using the phone but since the beta I keep getting these panics only when the phone is in deep sleep. Last_kmsg is useless as the info in the file starts from bootloader initialisation & there is no info before that which seems to also be happening from the beta versions.

CM9, GPU & CPU UV, pegasusq, sio

Due to the instability caused by UV to the GPU (mali crashes) fluxi set the min voltage for the GPU at 800mV

Point 2 does seem valid. After using the phone continuously for a day the delay is almost 2 - 3 secs & its especially noticeable when multitasking or playing graphic intensive games.

Have you checked your UV?

RC1 does have an option to set the backup style to either the old tar method or the new blobs method. It's under the backup & restore options in recovery.
[Galaxy S II Original Android Development] jlevy73:
Most likely the RIL issue with CM10. Kernel only affects wifi as you know but I remember back on my Nexus One, kernel guru Kmobs, received a lot of complaints on one of his kernels relating to radio. The issue was people who UV the CPU had issues with their radio/signal crashing. So Kmobs did a blind experiment where he released several kernels with different pre-defined UV to see if he could locate the problem. Unfortunately the test was inconclusive. The bottom line was that people who didn't UV a lot didn't have their radio crash on them. Anyway, that was a different phone with a different OS so their are a lot of different variables.
[Galaxy S II Original Android Development] rajarshi10:
Screen flickering issue with RC1. Back to 4.0.1
[Galaxy S II Original Android Development] gokhanmoral:
if "properly" refers to something like "it should hotplug the second core out when I am watching without having any activity" then you should use ondemand or hotplug governor because it is not how pegasusq works.

the app that you use to "watch" it creates a load and it increases average rq which makes the governor not hotplug the second core out.

in past I modified that logic and introduced an additional averaging to hotplug the second core in/out more easily but then I thought it was not a good idea.

if I put that logic back the hotplug logic in pegasusq will behave very much like the one in hotplug (some of you know it as abyssplug or assplug) or old legacy gb hotplug logic. I don't want to smooth that part.

yeah.. if you want the second core to be turned on while watching ondemand is a good choice.
[Galaxy S II Original Android Development] gokhanmoral:
1- yes, it should be my mistake. I will check it tonight. I made some refactorings in initramfs to make it more clean and I must have used ro.secure=1 in the new one.

2- I also want to make that voltage part simpler but I could not find an easy way of doing it. the best way is to requery the asv value and reset the voltages when the user changes a frequency of a step, and then reapply the relative value, but that will take all the flexibility away. some users cannot even get a stable 400MHz with 1200mV and they just want to increase the voltage of a single step. it is really hard to make everyone happy... :) the way I would suggest (if I were only a user of this kernel) would be to remove all the settings from gpu tab and force everyone use init scripts.
[Galaxy S II Original Android Development] pikachu01:
Actually, just by having the screen on on a blank desktop with no apps on, using ADB to "cat" the 2nd core status, I see that pegasusq indeed is harder to have it's 2nd core turn off. It only turned off after a few minutes.
[Galaxy S II Original Android Development] karlesg:
thanks for your answer.

Just like pikachu01 did, I also tried with adb cat sys/devices/system/cpu/cpu1/online

You were right the app was affecting it. I'm using your default hotplug rq up/down 400/400

Now It's even harder to turn the second core on. I really think that the rq thresholds need to be lowered.

But the second core turns off more easily than I described in my previous post. Now it needs about 5 ~ 20 seconds from the time that I exit to the homescreen and do nothing to close the 2nd core. But if I lower the rq thresholds so that the 2nd core turns on more easily, then probably this time will increase.
[Galaxy S II Original Android Development] robertobsc:
Hi GM, i should agree with pikatchu. The hotplug behavior of pegasus really changed, and it started when the update 7 sources were applied.

I didn't see what changed, but I was guessing that number of process in queue increased, but also could be the the number of process that the function that pegasus call returns more now? May be something changed in that part by Samsung?

Probably I'm saying crap in that time, sry about that, but it's a fact about pegasus new behavior, plus I don't think you did that change...

Enviado de meu GT-I9100 usando o Tapatalk 2
[Galaxy S II Original Android Development] gokhanmoral:
ok I will monitor the behavior once again tonight.
[Galaxy S II Original Android Development] Tungstwenty:
I don't have such problems, but read somewhere that some apps check for ro.secure and refuse to run if it's 0.

Detecting the su binary, SuperSU or Superuser apk's are other factors to be solved, of course, but if ro.secure is indeed a problem for some folks (and this is the only part that can be blamed on the kernel) perhaps another option would be to have an adbd that ignores the flag and is always insecure. Is it feasible and desirable to include such a modified daemon?

Again, no issue at all for me but thinking ahead of the complains :laugh:
[Galaxy S II Original Android Development] gokhanmoral:
I was using a modified adbd binary (just as you said, it was ignoring ro.secure flag and was always running as root) but I reverted back to the stock one when I had a problem that I can't remember now. I will modify and compile the one in cm repo again and put it to 4.1.
[Galaxy S II Original Android Development] mrbluesman:
Yes see point 3
[Galaxy S II Original Android Development] nihilista:
I don't know it should be so like it is, but i've seen same behaviour with pegasusq. It turns off second core only if screen is off, the app for monitoring it can't use so much cpu that it prevents shutting down second core. With other governor like hotplug second core goes down after some (short) time at minimum freq. Turning sched_mc in extweaks to 1 fixes this, but its noticeable more laggy, benchmark says the same and i remember someone said to better set it to 0, in cause of overlapping with pegasusq scaling.

However, for me pegasusq in 3.xx kernel versions was great and scales cpu like wanted, no lag and no second core staying on while doing nothing.

Btw, 4.1 rc1 kernel working great here, but i never tested the cwm restore, seen someone having problems with it, but dont want to test it and loose my data ;)
[Galaxy S II Original Android Development] zonehack:
I would like to ask if it's necessary to use a kernel cleaning script when upgrading to newer versions or is clearing cache and Dalvik enough?

thanks in advance
[Galaxy S II Original Android Development] minidou-77:
No need to wipe anything

At least for me

I never did and never had any single issue

IMHO kernel cleaning scripts are useless

If you want to clean things do a total wipe (format /system + wipe data +cache + dalvik) and then reinstall your ROM and kernel
[Galaxy S II Original Android Development] gokhanmoral:
do whichever please you most :)

"clean", "snappy", "fast", "best", "awesome" words cause addictive effects which are really hard to change and the effects are massive...

it's been told hundreds of times that those scripts are just removing some files from the init folder and even make some funny modifications which are lost after a restart... but just because of that "cleaning" word, those scripts are used by thousands and those people just ignore the other comments.

I don't know any script that can clean a kernel enough if the kernel itself is dirty.
[Galaxy S II Original Android Development] nedooo:
Latest 4.1 RC1 gama shift doesn't work. Stock XWLPT
[Galaxy S II Original Android Development] Tungstwenty:
http://bit.ly/O24Rdm
[Galaxy S II Original Android Development] nedooo:
I was searching this thread, didn't ever checked that other non dev, although that's dev stuff LOL
[Galaxy S II Original Android Development] fs1023:
Hi All

Does anyone know if it will be ok to flash OTA Paranoid Android 1.991. rom whilst PA 1.990 version is my second dual boot ROM with Siyah's latest SGS2 kernel.

Regards

fs1023
[Galaxy S II Original Android Development] cybernetus:
Yeah there is no problem with this configuration ...
[Galaxy S II Original Android Development] Mad_Rick:
Hello gokhanmoral,

I also want to upgrade from 3.3.2 to 4.1rc1. In your opinion what is the best practice when upgrading so that there are no conflicts between kernel´s?

Thanks in advance,
[Galaxy S II Original Android Development] SGT John Doe:
Can someone please explain some of the settings under CPU at ExTweaks :eek:

Yes, i have done some reading both at the forum and at google. All i want is good battery life, but still performance.

Max cpu lock, what should i choose there? I want to use one core until more is needed.