yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] predatorftp:
Ok,

Try to go into the dual boot menu and flash from internal SD, Syiah Kernel on the second ROM, This might "remind" the dual boot engine that a second rom exists.

I had the same problem once, after flashing a ROM without CWM...

Try this and let us know.
[Galaxy S II Q&A, Help & Troubleshooting] Many40:
Bad news for you mate. I had the same issue when I flashed new 1st rom, then I lost option at boot to choose 2nd rom even it was still present in /.secondrom folder on sdcard (it shouldn't have happened to be honest, normally it should work properly so it's kind of bug of dual booting I assume). This doesn't happen after flashing only a new kernel. So, only solution I found that time was reflashing 2nd rom from nandroid backup (always is worth to have one:)). After that the option to choose between two roms was restored. Regards.
[Galaxy S II Q&A, Help & Troubleshooting] CamoGeko:
Haha, I will get to configuring Fluxi soon. :)
[Galaxy S II Q&A, Help & Troubleshooting] danielsf:
gokhanmoral, may I ask if you have seen anything in the s3's kernel that could be ported to the s2 please? Like the s3 I believe has different logic governing what gpu frequencies are valid to the s2, which allows the s3 to have frequency steps between 267 and 400mhz such as 350mhz, which would be invalid on the s2. Do you think that could ever be ported to the s2. Like the s3 has 350mhz step, I tried setting the s2 to that, like you suggested it before, by echoing it to the gpu frequency table. Of course it showed no difference, as even though it gpu scaling table shows 350mhz, it really is still only 267mhz due to it being an invalid frequency. So do you think somehow porting the new logic for valid frequencies from the s3 to the s2 is feasible at all, as the s2 is starting to get...dare I say it...dated :(

Also, do you think it would be possible to have 4 gpu scaling frequencies please, as using the malistatus app some one made here to show what gpu frequency you were using, I found that a lot of games would use 200mhz as opposed to jumping straight and staying on 267mhz and be just as fluid. But a lot of games would also use 160mhz over 100mhz but a lot of 2d games use 100mhz. So to have four steps like 100,166,200 and 267mhz could save power, hopefully :)
[Galaxy S II Q&A, Help & Troubleshooting] predatorftp:
I just had the weirdest bug ever !!!

My phone crashed !

I tried to do a system backup from "ROM Manager" the phone rebooted and turned black and stayed this way for a while. pressing the power and home button didn't change anything. pressing 4 times the home button still worked and turned the screen into night mode.

took out the battery and tried to get in CWM, no luck it's like it doesn't exists anymore. i finally got into Download mode and flashed Syiah 3.3.2, thinking i could at least get into CWM mode. no luck.

I just flashed using ODIN and Original ROM (TAR) and the phone just hangs on the Samsung Logo for the last 20 min.

HELP !!!

Edit (1)

Just had an idea - Flashed using Odin Siyah 3.3.2 again and now i have access to CWM. I accessed the dual boot option menu and now cloning 2nd rom to 1st. crossing my fingers.
[Galaxy S II Q&A, Help & Troubleshooting] CamoGeko:
1. Do not use ROM Manager for flashing or backups. It doesn't play well with SGS2.

2. Tried flashing CF-Root via ODIN then turn off your phone and try to boot into recovery via the 3 button combo.
[Galaxy S II Q&A, Help & Troubleshooting] predatorftp:
that's what i did, but the 2nd rom was no good :( it's like it doesn't exist any more.

I solved to problem by flashing from scratch Nightly + Gapps + Siyah

my phone works now :)
[Galaxy S II Q&A, Help & Troubleshooting] toxicbubbles:
Great work again gokhan, wifi back working for me, sweet, was sitting on 3.2.7.1 as no wifi when the SGS3 drivers were added, this one seems to have fixed that thanks and the usb option is great using linux mtp just never seems to do what I want so great to have this option to make access that much quicker. Good to see you've no forgotten us totally.
[Galaxy S II Q&A, Help & Troubleshooting] CamoGeko:
Yes, second rom is inaccessible when you're using any other kernel.

Glad you got it sorted. :)
[Galaxy S II Q&A, Help & Troubleshooting] ballmead:
It didn't work :-(
[Galaxy S II Q&A, Help & Troubleshooting] sam142000:
Can these results be considered good enough for an average user like me?
[Galaxy S II Q&A, Help & Troubleshooting] durangatang:
Looks good to me. Are you happy with it?
[Galaxy S II Q&A, Help & Troubleshooting] sam142000:
I've never crossed the 4Hr Screen On time.

Just wish my phone would give >4hr screen on time. :o
[Galaxy S II Q&A, Help & Troubleshooting] Syrus01:
After flashing v3.3.2 I noticed some "lag" each time I unlocked my phone (using Widgetlocker + Apex Launcher). It seems as if Apex Launcher had to redraw the whole UI everytime. I first only saw the background, had to wait a second and then the ui (widgets and dock) popped up.

Now i activated GENTLE_FAIR_SLEEPERS (which was disabled by default) for testing and the issue seems to be gone.

Is there some kind of in depth explanation how the functions behaves (I'm a n00b though). At the moment the info in extweaks (disable for better ui responsiveness) highly contrasts to my actual experience. I'm just curious...
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
droidphile has some interesting threads with lots of explanations ; here's a citation from one of them :

GENTLE_FAIR_SLEEPERS

"Sleeper Fairness is a concept used by CFS which treat sleeping/waiting tasks as if they were in a run queue. This implies tasks which spend most of the time waiting for an user input and such will get a fair share of CPU when they need it. Disabling Gentle Fair Sleepers could improve UI responsiveness."

source:

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

In laymen's term :

just like user-space has it's governors (pegasusq,ondemand,lulzactive, etc.) to let the processor speed up depending on user's demand, the operating system (android,or linux actually) has it's own system of scheduling, in this case CFS, to distribute it's power to the demanding processes, and this system can be fine-tuned with different parameters, one of them being GENTLE_FAIR_SLEEPERS, which, practically speaking ensures, that all processes get a fair share, so things go along more evenly, and every proces gets finished in a reasonably fair way.

It can help with energy efficiency, indirectly, making sure a proces gets done and is not put on hold for to long ; on the other hand if there are a lot of processes going, it's going to spread it's power to all of them, so maybe you will experience some 'laggy'ness ; that's why in this case it can be turned off for more responsiveness.

My experience is it tends to smooth out all activities in such a way, that it's more battery friendly, causing more deep sleep (which is good energy-wise). This in combination with some other tweaks, gives just that little more extra battery-life.....:)
[Galaxy S II Q&A, Help & Troubleshooting] sora9961:
Siyah 3.3.2 better or 3.2.7.2 better
[Galaxy S II Q&A, Help & Troubleshooting] durangatang:
Looks like you still had 20% left?

I don't think I ever got over 4 hours screen on time with the stock battery. Have to tweak your phone a lot to really maximize battery, or get a bigger battery.
[Galaxy S II Q&A, Help & Troubleshooting] Tungstwenty:
What and did you flash as the primary ROM, and How did you do it? (Odin, maybe?)

I'm asking this because if you flashed a stock ROM through Odin, for instance, a part of the CSC (which is only needed on the 1st boot for finishing the setup) is written to the /hidden partition, which is where the system of the 2nd ROM is stored.

If you did that, the /system of the 2nd rom is gone, even though /data, etc. might be there (on the sdcard).

It might be possible, depending on the 2nd rom you're using, to flash just the /system part of it onto the /hidden phone partition, or using the swapping method, and if you don't touch the data, cache, etc. of the 2nd rom it should work exactly as before with no data loss.
[Galaxy S II Q&A, Help & Troubleshooting] CamoGeko:
3.2.7.1 is better.
[Galaxy S II Q&A, Help & Troubleshooting] tlf55:
I changed some frequency and underclock with ExTweaks, now if i want them back as stock how do i do ?

If I Flash back to a stock with odin it will get these back as stock ?

Thanks
[Galaxy S II Q&A, Help & Troubleshooting] Flint2:
Android logs

Anyone sees improvements disabling Android logs from exTweaks ?
[Galaxy S II Q&A, Help & Troubleshooting] tlf55:
Thanks ! but i mean if i change to the stock kernel it would be reseted by himself or i have to reset first then flash back to a stock with odin ?
[Galaxy S II Q&A, Help & Troubleshooting] Flint2:
To reset exTweaks

To reset ExTweaks settings,

- Reboot to Recovery (using CWM or VolumeUp+Home+Power on boot) and

- select 'kernel specific options' --> 'Reset ExTweaks profiles' (there is no confirmation screen)

- Reboot
[Galaxy S II Q&A, Help & Troubleshooting] tlf55:
And for my other post ? :

Thanks ! but i mean if i change to the stock kernel it would be reseted by himself or i have to reset first then flash back to a stock with odin ?
[Galaxy S II Q&A, Help & Troubleshooting] Many40:
+1 Fully agree. The same for me. Regards
[Galaxy S II Q&A, Help & Troubleshooting] rygel16th:
i went from 3.2.7.2 to 3.3.2.

both are very smooth and have good battery life.

i prefer the new one because of the new settings in ex-tweaks
[Galaxy S II Q&A, Help & Troubleshooting] Boat Traveller:
What are the Extweaks' new settings ?
[Galaxy S II Q&A, Help & Troubleshooting] CamoGeko:
ARCH_POWER and GENTLE_FAIR_SLEEPERS.
[Galaxy S II Q&A, Help & Troubleshooting] Many40:
With all respect (just to understand the problem), how do you know and how do you assess that if you flash the 1st rom (with system stored in the hidden partition /dev/block/mmcblk0p12) the another (different) hidden partition asigned only for the 2nd rom system(/dev/block/mmcblk0p9) is involved. While dual-booting only boot partition (kernel) is shared between two roms. Other parts of the firmware (ROM) are supposed to be independent.
[Galaxy S II Q&A, Help & Troubleshooting] Boat Traveller:
Thx. What are the purpose of those settings ?
[Galaxy S II Q&A, Help & Troubleshooting] Many40:
Source - Droidphile's thread:

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

......................

a) GENTLE FAIR SLEEPERS

Significance: Android UI Interactivity.

Sleeper Fairness is a concept used by CFS which treat sleeping/waiting tasks as if they were in a run queue. This implies tasks which spend most of the time waiting for an user input and such will get a fair share of CPU when they need it. Disabling Gentle Fair Sleepers could improve UI responsiveness.

Tweaking Via Script:

#disable

echo "NO_GENTLE_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features

#enable

echo "GENTLE_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features

b) ARCH POWER

Significance: ARM Topology Awareness.

Arch Power patch causes arch dependent power functions to be used instead of generic high resolution timer ticks and double ticks.

Tweaking Via Script:

#disable

echo "NO_ARCH_POWER" > /sys/kernel/debug/sched_features

#enable

echo "ARCH_POWER" > /sys/kernel/debug/sched_features

........................
[Galaxy S II Q&A, Help & Troubleshooting] Pigmachine:
too late
[Galaxy S II Q&A, Help & Troubleshooting] cyberlion17:
Same issue as me, though I have never tried the gentle option before. I'll test it later :)
[Galaxy S II Q&A, Help & Troubleshooting] Tungstwenty:
Flashing the primary rom places its system files in the regular /system partition, on mmcblk0p9. However, the stock ROMs have in addition to the system files some additional apk's to be installed on the 1st run into /data as regular user apps (Swype, some live wallpapers, etc.). And while flashing these stock roms, the hidden.img file is written onto mmcblk0p12, overriting the system files of then 2nd rom.

If that's the problem that occured (stock rom flashed as primary), after the 1st boot and apps installation, you can then rewrite the system data from the 2nd rom back to mmcblk0p12 and 2nd rom now has all the data it needs (but it's still necessary to check whether Siyah will detect it and show the dualboot menu).
[Galaxy S II Q&A, Help & Troubleshooting] robertobsc:
Hi GM. Some people were complaining about battery drain in 3.3.2. I think I just found the problem.

I have two roms installed. Xwlpd and wannamlite xwlpg, v12. The battery drain only occurred in wannamlite and a huge amount of kernel wakelocks occurred with the vbus_present event. The funny thing, my phone wasn't connect at any charger!

My guess is that there's some kernel bug that tells that the USB is being used.

That would explain why weren't all that complained about battery drain (since this happened only in wannamlite) and why flashing 3.3.1 back solves the problem.

Well, please take a look!

Oooh, another bug that I ask you to correct is the GPU initial frequency bug. I think it is simple. Example, my settings are 100,160 and 267. I boot my phone, we have the boot animation, etc. Then the first thing that i do is to open mali stats. It shows that the GPU is in 160 and don't go back to 100, even with 0% load. It happens only in the boot moment. In this case the workaround is go to 267 to come back to 100.

Please take a look also in this!

Thanks so much!
[Galaxy S II Q&A, Help & Troubleshooting] Lady_Chloe:
When I'm lucky, I sometimes get slightly over 5 hours on the stock battery. I have wifi on all the time, usually browsing the web (with inverted rendering), using some apps, watching videos... But if the mail app goes crazy and uses thousands of alarms, it drains faster and I get barely 3 hours. A reboot fixes this but sometimes when I find out that the mail app went crazy, it is already too late.
[Galaxy S II Q&A, Help & Troubleshooting] Syrus01:
That is one very nice explanation. Thank you very much for putting this all together.

So I just had some twist in my logic...

If GENTLE_FAIR_SLEEPERS is disabled like in my first case, android give less attention to sleeping tasks, which helps my battery but also makes my background/waiting processes less responsive. In my case after unlocking my device Apex Launcher (which I assume is waiting/sleeping at that moment) is a litte bit laggy. But widegtlocker which is an active foreground app gets much attention (this is ment with better ui responsiveness [for foreground tasks]).

Now that I enabled GENTLE_FAIR_SLEEPERS the waiting Apex launcher gets a better fair chance and thus more attention and processing power by the system. But in an overall view the WHOLE system gets less responsive because more attention/procesessing power is "wasted" to background tasks instead of foreground tasks. So processing power is shared more equally to the overall system which leaves less processing power for the active event and thus reduces ui responsiveness.

I think I got it with my own amateurish words.

So my "problem" is simply the fact that I am using a standalone lockscreen app. If I used a launcher integrated lockscreen, the system wouldn't have to switch between two task (of whom one is sleeping) and thus I wouldn't experience this kind of lag.

That also means, if the apex developers implement a "keep in foreground" feature I could disable GENTLE_FAIR_SLEEPERS again without getting lags?
[Galaxy S II Q&A, Help & Troubleshooting] carlos67:
I'm using Widgetlocker and Apex like you are and I too get exactly the same situation when unlocking (not waking) to the homescreen after a period of deep sleep. Like you, the wallpaper draws and after a lag of maybe 3-4 seconds, the apps, dock,widgets etc then appear. I'm running Siyah 3.2.7.2 though unlike you.

Have tried lots of governor/scheduler combo's but no joy. Apart from this one issue (annoying as it is) the phone is silky smooth.

What governor and scheduler are you using? And are you undervolted/clocked?

I am running SmartassV2 with SIO scheduler and thunderbolt's main script which disables the 3 "sleepers"

Anyone else using widgetlocker/apex experiencing this too?

---------- Post added at 02:25 AM ---------- Previous post was at 02:21 AM ----------

That's the question I'm asking myself. On 3.2.7.2 and weighing up trying out 3.3.2.

Anyone who has used both got an opinion, especially with regard to battery life/wakelocks?
[Galaxy S II Q&A, Help & Troubleshooting] #illidan:
If you could provide me with a link to this K's kernel thread I would be able to help you but without that what I can tell you is that this thread is the official siyah thread & siyah kernel is made by GM for the GT-9100. There are dev that use his repos to make kernels for other galaxy s2 versions like the i777 which I'm guessing is where the mic swap & no swap versions come if I remember correctly so since you have the GT-9100 you can use the kernel provided by siyah.

Lower value is more responsive. But setting it too low will cause swipes to be registered as clicks.

If you flash a stock kernel all the pram values will be replaced by the values present in the stock kernel. You don't need to resest ex tweaks & flash the stock kernel.
[Galaxy S II Q&A, Help & Troubleshooting] BananaMilkShake:
Hi all. Would like to know whether flashing this kernel through odin will root my phone, or I have to root my phone first then flash this kernel???

*I have an unrooted phone btw*
[Galaxy S II Q&A, Help & Troubleshooting] CamoGeko:
I would advise you to flash cf root kernel in ODIN first, then reboot to CWM recovery and flash SiyahKernel.
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
one small adjustment you should make in your thoughts:

it doesn't specifically apply to background/foreground processes, but to processes in general

the way it works, simply put:

processes needing attention place a request in a run-queue

the actual processor will proces this run-queue, and this can be done in numerous strategies (so to simplify, just a couple of examples)

the most straightforward way would be to handle each request and go on to the next, but this would mean a request taking up very long (hogging the processor) would hold up all others ; not very efficient

another approach would be to set a time limit, and handle the request, until the limit is reached, and putting the reqeust back to the end of the queue ; that way is more fair to the other waiting requests, and minimize long waits.

inactive/sleeping processes (whether foreground or background) don't have requests in the run-queue, so if and when they do have requests, they have to take turn at the back of the line in the run-queue and wait until they are served

..and what GENTLE_FAIR_SLEEPERS does is putting these inactive/sleeping processes in the run-queue, as if they had requests, but the only request they have is 'do nothing' most of the time and are handled in almost no time (far within the time-slice limit) and so a minimum is wasted. But when they do have a request, chances are they will get served a lot faster, than starting way back at the end of the line.

It would be logical to think that enabling GENTLE_FAIR_SLEEPERS would consume more energy, but contemplating the real fact of the matter, I think by handling things this way, somehow eliminates some overhead which results in a positive saving. I've noticed in that in the android battery statistics, the android OS part and the android sytem part has been realtively reduced compared to when the it is not enabled, and of course the fact that consumed battery percentage per hour has gone down...

---------- Post added at 08:29 AM ---------- Previous post was at 08:26 AM ----------

..testing now , and over the weekend, and comparing to 3.2.7.1 which I've been using for a while now, and will use as reference....

but also curious if others have any good comparison...
[Galaxy S II Q&A, Help & Troubleshooting] owen1978:
Was on v3.2.7.2 then flashed the latest Kernel

Wiped Cache/Dalvik

Now stuck on Samsung Logo screen

Cannot access recovery

But can access download

Any one else had problems?

Do I simply flash my previous kernel tar file in odin?
[Galaxy S II Q&A, Help & Troubleshooting] Mutalisk:
Had that as well (with the newest), I flashed resurrection CM9 to be sure, but no problem, either way Odin helps ;)

Try it with an older kernel, if it won't work flash a firmware.

Either way, be sure your battery still has energy - mine hadn't, I had to use another one, because it couldn't charge as well.

But don't worry, can be fixed easily, with a new kernel you won't even lose your data ;)
[Galaxy S II Q&A, Help & Troubleshooting] johnbeetee:
Actually it has been there all the time, but has been disabled, and later removed from extweaks, but if you knew how, you could enable it with scripts or other ways, under the "surface" so to speak.

Same goes for ARCH_POWER which has been enabled in most versions, and is better that way. I think it was disabled because some may have complained it due to its laggy side effects (prior to pegasusq) specially in combination with some governors. But now with pegasusq and GENTLE_FAIR_SLEEPERS, I think it should be default enabled, and tweakable so people can always turn it off for gaming or other such activities....
[Galaxy S II Q&A, Help & Troubleshooting] CRudner:
3.3.1/2 Issues

Hi There,

I was using 3.3.1 & 3.3.2 the last few days and i was having a few problems with stability.

I am running the latest CM9 nightly and I was getting freezes that would drain my battery almost completely.

I have had to revert to 3.2.7.2 as I had no problems with it.

I did a GSWiper(Kernel wipe) and a GS2ROMNuke(full wipe script) about a week ago, as I had been have issues with various Rom and kernel versions. Since doing it my phone was doing great until 3.3.1/2

Has anyone else been experiencing problems with the last two versions?
[Galaxy S II Q&A, Help & Troubleshooting] CamoGeko:
Nothing like that has been happening here. Perhaps its a good idea to wipe your extweaks settings. Do a reflash of your current ROM and install 3.3.2 straight after. Then see how it goes.
[Galaxy S II Q&A, Help & Troubleshooting] Flint2:
The ExTweaks Settings are part of the Siyah Kernel, with stock kernel you can't tweak this settings, and the ExTweaks app will not work anymore.

So, no, you don't need to reset settings because there will be reset when you flash a stock kernel or a siyah kernel after 3.2.
[Galaxy S II Q&A, Help & Troubleshooting] Tye:P:
Does anyone know what the plus symbol in ExTweaks Pro does?

I was thinking reset or check for update but it appears not to do either of those.

Perhaps unimplemented?
[Galaxy S II Q&A, Help & Troubleshooting] CamoGeko:
You have to have ExTweaks installed first, then buy the + (donate) versions and it will allow you to use multiple profiles. On it's own ExTweaks+ does nothing, except give Gokhan your money for all the amazing work that hes done and doing for us.
[Galaxy S II Q&A, Help & Troubleshooting] robertobsc:
Hi gokhan and folks,

Just to tell that the battery drain just stops if I switch the USB to "force mtp" option.
[Galaxy S II Q&A, Help & Troubleshooting] Tye:P:
I have ExTweaks Plus.

In the top left corner there is a ExTweaks symbol (green square with white cross). You can press it, in the free version I'm pretty sure it says that you need the Plus version to use it. When I press it the CPU shoots up to 1200MHz at about 50% load and sits there for a second or two but appears not to do anything.

I'm asking whether anyone knows what it does or if it's an unimplemented button?

If it's unimplemented you might be able to add a function to it eg. trigger another profile or start another app, perhaps NSTools.
[Galaxy S II Q&A, Help & Troubleshooting] sharp87:
after flashing siyah 3.3.2 my battery status in settings app shows only screen and cell standby and i use tapatalk for more than 2hrs but it is not listed there...is this an bug in kernel....and stock kernel doesnt hav this problem
[Galaxy S II Q&A, Help & Troubleshooting] pikachu01:
Cannot reproduce this. Only if an app consumes more than 2% of battery, it'll show there. Tapatalk is visible for me when I used it over some time.