yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] :
Well, i'm getting fcs while opening the system on the xxtweaker. Since logs may help you, let me fc it again and get the log. Going also to clear data.
[Galaxy S II Original Android Development] :
Here's buddy.
[Galaxy S II Original Android Development] :
Would it be possible to have a reset option directly in xxtweaker instead of having to go to recovery? provided that is doable and savvy of course :)

Sent from my SGS2 - SlimICS Rom & Fluxi Kernel
[Galaxy S II Original Android Development] myfluxi:
It's already in beta5 and much more: A full fledged settings administration with settings restore at runtime. To be released very soon, just ironed out some tiny, tiny bugs.

Thanks! Did you mess with LCD Density using a windows editor? I'll add more null or empty checks for people who do.
[Galaxy S II Original Android Development] gaz617:
Looking forward to it!
[Galaxy S II Original Android Development] :
No. I've reinstalled CM9 without modifying the build.prop. And even if had to change lcd density, i would change on notepad++, as i do to edit everything related to android.

I've learned this by hurting myself, trying to edit update-scripts on wordpad. Some time after that, i realise they needed to be coded in unix, otherwise it woudn't work.

I think I have an idea to BLN, to be more precise and functional. Whenever the screen turns on without we doing it, BLN would be activated. I think it could work better just with the screen receiver on xxtweaker, so maybe no wakelocks. Just a idea, don't know if i'm totally right, but if you got it, can you think about it?
[Galaxy S II Original Android Development] nehalem176:
Why setting value for threshold up in bus frequency will revert to default value 23 after reboot?? :confused::confused:
[Galaxy S II Original Android Development] myfluxi:
Because I messed up while copying & pasting. On reboot the value of down threshold is loaded for both, up and down threshs. Will be corrected in beta5, thanks for the report.

The kernel wakelock will stay and cannot be avoided unless we get wakelock-free BLN to work (which we can't at the moment). Thanks for the suggestion, though.
[Galaxy S II Original Android Development] :
Why should I change those bus theresold values? What are the benefits? TIA

Sent from my SGS2 - SlimICS Rom & Fluxi Kernel
[Galaxy S II Original Android Development] shadowblade330:
yea the sampling_rate_min does not save either.
[Galaxy S II Original Android Development] thez3ro:
will NTFS support be added in the near future maybe?
[Galaxy S II Original Android Development] gdskp:
Same here with beta3 on cm9 latest nightly. How to fix it:(
[Galaxy S II Original Android Development] shadowblade330:
havent had a problem with this bug yet how does it get activated.
[Galaxy S II Original Android Development] gdskp:
It is random...It could be hitting a search result from play store, closing an app back to launcher...

I could only reboot my phone to solve the problem. Nothing else I could do when it gets activated...
[Galaxy S II Original Android Development] shadowblade330:
hmm ok ill see if that occurs but so far nothing unless it happened when i was using beta 1 cuz i do remember having random reboots. but in beta 3 so far everything is ok.
[Galaxy S II Original Android Development] myfluxi:
It's a read-only value and shouldn't be there in the first place. I just rewrote that part, it will be clearer in beta5 now. Thanks again.

There is no slow motion bug in this kernel, it's a specific thing in Siyah that cannot happen here. Especially not since I did not touch anything remotely related to BLN for more than two weeks.

Whatever happens, it's just your device and maybe think about your ROM instead of the kernel.

Again it's a pity that kernel cooks are taken in resposibility for things happening in user space (read: your Android ROM). Wakelocks, battery issues, inconsistent behaviour and all that.
[Galaxy S II Original Android Development] shadowblade330:
Was not blaming you I just wanted to know about the bug to try to replicate it I know those random reboot were probably due to my settings being off
[Galaxy S II Original Android Development] myfluxi:
If there is an error, I take full resposibility of course. Then again it's not fair to relate this directly to kernel versions. Please think about it before posting, thanks.
[Galaxy S II Original Android Development] override182:
I experienced the slow-mo bug last night and honestly in a good way IT IS COOL! LOL. Yeah, a reboot saved me and thats the only once i experienced it. Ur lucky if ur getting it freq. Logcat?
[Galaxy S II Original Android Development] Prashanthme:
I m planning to reinstall ROM again... Can i wipe the factory reset/data?? I m afraid of BRICKBUG!!! :confused::confused: Can anyone reply me in this issue??
[Galaxy S II Original Android Development] Rawi666:
Fluxi is a safe kernel. Don't worry and wipe ;)
[Galaxy S II Original Android Development] alcurtis93:
Course you can!
[Galaxy S II Original Android Development] override182:
Hit the slo-mo bug just now. Here is the cookie https://www.box.com/shared/4c8817e704a2a686f0c8

RRemix 2.2, .02beta3. Didnt open playstore at that time. Was doing a titanium restore on an app. Slide down notification, pressed back. Not sure where or what caused it. Hope the logcat gives a clue to anyone understands it
[Galaxy S II Original Android Development] wonsky21:
What is this slow motion bug?
[Galaxy S II Original Android Development] override182:
Its like Skrillex bass drop at 30% speed. Everything moves slowly. Touch button didnt respond so when u pressed the power button. The CRT effect goes below 50% of its normal speed. Thats the Slo-mo effect yaww
[Galaxy S II Original Android Development] myfluxi:
Thanks. Your system is running less than a minute and you already have a zillion errors of various kinds in your logcat (crashes, missing ressources, apps not being granted permissions etc.). What you call slo-mo bug may be a cacophony of applications doing weird things, interfering, blocking system ressources. If this happened on my device all the time, I'd **** my pants ;)

You may want to backup, reinstall your ROM and see if it happens again. And then only install apps you really need to survive as too many running processes wreak havoc on performance and cause unpredictable behaviour.
[Galaxy S II Original Android Development] kalpik:
But the slow mo bug is very real.. And it's only happening with Beta 2 onwards. I'm not sure what gokhanmoral did to fix it, but it's definitely present in Beta2+
[Galaxy S II Original Android Development] Honusnap:
Think it that way : You throw a party and invite 1-8 friends.. everything run smooth. Now let everyone in the street comes to your home... :D, in less than half an hour your bedroom is occupied, some freaks are throwing up in the toilet... well... your phone is in this second state.. :p
[Galaxy S II Original Android Development] gaz617:
[Deleted] Too slow!
[Galaxy S II Original Android Development] antt00:
Quite frankly i had never experience any "slowmo bug" either on siyah or fluxi with CM9.
[Galaxy S II Original Android Development] kalpik:
That's the thing, that son of a b**ch bug is very random. Can't reproduce it if I want to :(
[Galaxy S II Original Android Development] override182:
Thanks! Haha that was funny to know indeed. Didnt expect that outcome cuz i didnt notice issues on the front end. I guess i need to try to learn whats happening on the backend then :)
[Galaxy S II Original Android Development] JAG131990:
Troll.
[Galaxy S II Original Android Development] override182:
Had a great party last nite? Cuz i betcha didnt scroll n read till the end.

Btw, everyone having the slomo bug. What rom are you on? Im having it on Res Remix 2.2 now. On beta3 fluxi .02
[Galaxy S II Original Android Development] grzesdroid:
@Myfluxi

Can you add to xxtweaks "reset fuel gauge" ??

tapatalk@ SGS ||
[Galaxy S II Original Android Development] Gorjess:
Hmm, every time i reboot the xxtweaks app vanished.. I have to reinstall it again and all my setting are lost :(
[Galaxy S II Original Android Development] gdskp:
CM9 latest nightly.

Actually it is a clean install with restoring my apps before. The number of apps I install now is even smaller than before.

Do you enable the "force gpu rendering" in setting,developer options? I searched about the slomo bug and a post states about that.
[Galaxy S II Original Android Development] iekansh:
Which is the latest xxtweaker to use with this?
[Galaxy S II Original Android Development] shadowblade330:
can i get help with my log. I get this crash where my battery is around 50%, then when it boots backup my battery drains to around 20%. I am not quite sure why this happens. It has happened more than once so I am trying to figure out what causes this.

Thanks
[Galaxy S II Original Android Development] baza14:
I can't find any settings to turn off keys backlight. Is there any option?
[Galaxy S II Original Android Development] gaz617:
v0.3.9_beta4, comes with the latest kernel and has OTA updates.

Yes, in xxtweaker go to BLN and LED, scroll to the bottom, LED Buttons>lighting interval>Always off.

Also, if using cm9, may have to go to system settings>advanced>sensors>Enable keys backlight unchecked.
[Galaxy S II Original Android Development] iekansh:
And the latest Kernel is the one posted here in OP? Also, the one that comes with kernel is not in English or is it?
[Galaxy S II Original Android Development] Testraindrop:
Hi Fluxi, don't know if it's only me, but custom touch settings for charger is not saved after reboot.

If I change them, profile is set to undefined, after reboot profile is set to Gingerbread again, and the settings are shown right, but feel like the original ones.

If I change them eg. From 30 to 29 and back to 30 it feels like it should be again, until the next reboot...

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II Original Android Development] gaz617:
Always go here for the latest kernel http://www.android-hilfe.de/kernel-fuer-samsung-galaxy-s2/236546-aosp-aokp-kernel-04-05-12-fluxi-xx-kernel-ics-xxtweaker-app-xxtouch-recovery.html. fluxi isn't actually the op of this thread he just drops in to lend his expertise to this xda branch of the android-hilfe post.

As of 13 June latest is 3.0.34-FLUXI-XX.02-BETA3

The latest xxtweaker app reads your default locale so if your phone is in english it will be in english.
[Galaxy S II Original Android Development] :
fluxi. Checking my logcats, I've noticed this: "I/run-parts( 1704): /system/etc/init.d/S98system_tweak[492]: cannot create /sys/kernel/debug/sched_features: No such file or directory" It's from the ThunderBolt! scripts. I talked to pikachu and he said to ask if SCHED_DEBUG is enabled. Is it?
[Galaxy S II Original Android Development] djenis:
Dose it work this kernel on stock ics room ? I'm using NEAT ROM so let me know. thanks in advance
[Galaxy S II Original Android Development] misterspex:
carefully read the threadtitel and you'll know
[Galaxy S II Original Android Development] luigi_sa:
Hey all, can't find anything in the change log about voodoo louder support... I know the rc5 kernel didn't allow voodoo to access the sound chip. Is there possibility of building the support into the kernel? I'm using slim rom and would prefer to stick with their recommended kernel.

Thanks
[Galaxy S II Original Android Development] MDE_86:
+1

Tapatalk / SGS2 / Cyanogenmod 9 Nightly / Fluxi Kernel.
[Galaxy S II Original Android Development] Honusnap:
Already in Cwm, not the kind of action you do everyday ...
[Galaxy S II Original Android Development] :
Here it is. Took from Siyah initramfs, hope it works on fluxi's kernel, also.

Just execute the script on rootexplorer or scriptmanager.
[Galaxy S II Original Android Development] spaxx24:
I have alot of wakelocks... This is from one hour of me doing nothing. Someone got any tips? Om fluxi.
[Galaxy S II Original Android Development] nitinvaid:
Its best kernel for me

Dsp manager is working

Sound is also great,
[Galaxy S II Original Android Development] grzesdroid:
@up

Reboot :)

tapatalk@ SGS ||
[Galaxy S II Original Android Development] mchu6am4:
+1
[Galaxy S II Original Android Development] al_madd:
For wlan_rx_wake wakelock the answer is in the OP..
[Galaxy S II Original Android Development] spaxx24:
Do i need to disable it on the router? I dont quite understand..
[Galaxy S II Original Android Development] Testraindrop:
That only works if a windows PC is in the same network. But what to do if they are off? What settings can I change in the router?

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II Original Android Development] myfluxi:
Gökhan's solution of bln/breathing is completely different, Siyah and XX do not even share one single line of code in this part. There haven't been changes in since at least two weeks. Period and end of topic, thank you.

It's not and it will not be enabled. :)

I will add it as option in xxTweaker, not in beta5 but the following release. In the meantime use the linked script, of course it can be applied to this kernel as well.

I didn't test it but just by looking at my code I rewrote parts of it. Now it is like it should be - so thanks for the input!
[Galaxy S II Original Android Development] Honusnap:
Nope, in windows. If you've got a Windows seven computer connected to this same router... Windows is sending queries to the network, this queries wake your phone up. Not saying this is the problem in your case, but you can try disabling these "settings" and see how it goes.
[Galaxy S II Original Android Development] :
i see... and xxtweaker still FCing when tapping system.
[Galaxy S II Original Android Development] nehalem176:
Guess its thunderbolt clash with xxtweaker. I just mount s98 tweak manually via script manager work fine here, no fc in system. Just scheduler keep stay at sio instead noop, my prefered scheduler. No biggie for me.
[Galaxy S II Original Android Development] mgmate:
Fluxi,

Xxtweaker on SII is FCing when starting on phone reboot in my settings, but only if CPU is set to conservative.

With on demand is fine.

Enviado desde mi GT-I9100 usando Tapatalk 2
[Galaxy S II Original Android Development] AvRS:
Get a logcat otherwise it's no use posting "bugs". You need to help the devs help you.
[Galaxy S II Original Android Development] disellusional:
got the slow mo bug.

recently upgraded to beta 4 too, nothing else has changed on the phone.

did not have any experiences on beta 2 and lower
[Galaxy S II Original Android Development] kalpik:
I was the first one to report the slow mo bug, but just wanted to let everyone know that I haven't had that since! All I did was raised lowest GPU level to 100MHz and voltage to 900mV.

Maybe others can try this and see if it fixes the issue for them too!
[Galaxy S II Original Android Development] mgmate:
Here there are. There are two reboots. First one ok with on demand and second one with a fc with conservative. This is the only change.
[Galaxy S II Original Android Development] myfluxi:
Looking at it now. Edit: There is only one log and it shows a clean startup, please add the crash log.

How would this behaviour change if there hasn't been a new release of the Tweaker? I simplified this part, it should work now even with unusual or unexpected user settings. Update with beta5.

OK, now this may be interesting. From beta2 I allowed 700mV as minimum GPU voltage, this may be too low for some devices. Please test if 800mV and 67MHz and maybe other settings change the observed behaviour.
[Galaxy S II Original Android Development] mgmate:
AS i Said only happens with Conservative.

If I change the governor to On Demand, starts fine.

Regards,
[Galaxy S II Original Android Development] Ausboy 2011:
I find that the CPU likes to use 500 rather than 200 even on tasks like SMS or general phone browsing. Anyone else have this problem. Chews through my battery like no tomorrow :/
[Galaxy S II Original Android Development] Testraindrop:
Had same problem using Ondemand on last few Fluxi versions, changed to conservative, better now for me...
[Galaxy S II Original Android Development] spaxx24:
With beta3 the touchkeys dont turn off even when i have "always off" in xxTweaker
[Galaxy S II Original Android Development] Ausboy 2011:
Thanks it favours 200 a lot more now :)
[Galaxy S II Original Android Development] Honusnap:
500Mhz do not seems abnormal to me, 200Mhz is really low even for simple task.

Try setting your minimun to 100Mhz and your maximum to 200 Mhz than try using your applications..... how is it ..? Slow ? => Reason you need higher frequency.
[Galaxy S II Original Android Development] Ausboy 2011:
Nope set conservative and wala fixed must be a problem with ondemand. 500 shouldn't be used higher than 200 when only smsing half the day. Anyway problem solved all is good :)
[Galaxy S II Original Android Development] halkoliiteri:
every time you touch the screen frequency bumps up to 500mhz. sending sms is touching screen so that is the reason.
[Galaxy S II Original Android Development] Honusnap:
Using Go sms with more than 4000 messages, i've just tried : CpuSpy => Clear => Go sms => Slide down => open a conversation => slide to an old message => go back to Conversation list => slide => CpuSpy

=> got 100, 400, 500, 600 and 800 Mhz used

This not a problem with ondemand, ondemand jump to higher clock than Conservative.

Try what i say and you'll see that you need more than 200Mhz to operate your sms application.
[Galaxy S II Original Android Development] Ausboy 2011:
Didn't have a problem with ondemand with Samsung rom. Just seemed it favoured 500 more. Ohwell who cares I'm happy now might as well get over it
[Galaxy S II Original Android Development] myfluxi:
This is not a problem, it's a desired behaviour. The feature is called Frequency for Resposiveness, I ported it from pegasusq governor over two months back because I love the concept. Freq will jump to 500MHz almost instantly which leads to an incredible snappy and responsive (gee!) behavior. If you dont't like it, set freq_for_responsiveness to your minimum frequency (e.g. 100 or 200) using the xxTweaker app. Don't expect to save energy by switching it off, we're talking about milli- or even microseconds here... Saving battery is 90% up to your imagination - dim the display, or use another kernel that promises to magically transform your device into a perpetuum mobile ;)

Additionally read up about the concept of ondemand, jumping to target frequency immediately, and why it is a favourable concept. You can play with freq_step as well. Read and understand :)

This is true as well, freq will be locked for a short amount of time on a touch event. I made this frequency adjustable but didn't find time to implement in the tweaker app. You can use an init.d script in the meantime, e.g. for 200MHz:

echo "200000" > /sys/devices/virtual/sec/sec_touchscreen/tsp_touch_freq
[Galaxy S II Original Android Development] mgmate:
Fluxi,

Did you have the opportunity to look at the logs. I see the lines where the process died, but I do not see any other clue about why this is happening with conservative only.

06-14 11:32:07.870 I/Process ( 2880): Sending signal. PID: 2880 SIG: 9

06-14 11:32:07.880 I/ActivityManager( 1877): Process net.fluxi.xxTweaker (pid 2880) has died.

06-14 11:32:07.880 W/ActivityManager( 1877): Scheduling restart of crashed service net.fluxi.xxTweaker/.Service.BootCompletedService in 33688ms

Regards,
[Galaxy S II Original Android Development] Prashanthme:
Hi guys.. I m on Paranoidandroid with fluxi kernel.. But the automatic brightness is not working properly with this kernel.. Rest other kernel its works.. It takes more than 15 seconds.. and when it reaches brightness if i come to dark side it doesn decrease to low.. It stays thr only.. any solution?
[Galaxy S II Original Android Development] myfluxi:
Kernel Update Fluxi XX.02-beta4

This update is only needed for the new led backlight level (= "0") to avoid users reporting their bln was broken.

CWM ZIP: fluxi-kernel-sgs2-XX.02-beta4.zip

Odin TAR: fluxi-kernel-sgs2-XX.02-beta4.tar

Update xxTweaker v0.3.9_beta5

This is a monster update (at least for me), now we're having a feature freeze.

OTA or direct download: fluxi-xxTweaker-0.3.9_beta5.zip

Changelog:

kernel: keyboard: cypress: Use standard voltage for constant/blinking bln, with very low voltages, the user might wonder why "bln does not work"

kernel: Upstream patches from CM9 repo and more smaller patches

ramdisk: Update CWM recovery, add "Power off" option in Advanced menu (user request)

xxTweaker: System: Rewrite LCD-Density part to catch unxpected user settings

xxTweaker: System: Reset fuel gauge option (user request)

xxTweaker: Display: Rewrite touch config logic

xxTweaker: BLN & LED: New "Level 0" for the LED button backlight, helps as workaround to keep LED buttons effectively off

xxTweaker: BLN & LED: New 1 minute timeout for notifications (user request)

xxTweaker: CPU: On governor change, reload saved user settings for the selected governor. So now it's possible to have individual settings for each governor - nice!

xxTweaker: CPU: Remove read only value sampling_rate_min from settings in ondemand and conservative

xxTweaker: CPU: Fix Bus Frequency up threshold value on reload after reboot

xxTweaker: CPU: Fix on changing governors, governor list reports the actually selected governor

xxTweaker: New settings administration. Save, restore, manage and reset your settings. As it is a new function that required much more than 1000 lines of code and a lot of detail work (and as a sidenote is the killer feature in ExTweaks Pro that costs you $$$), there may be small errors. If errors occure, please supply logs and report what exactly happened before failure.
[Galaxy S II Original Android Development] Crazy-Silver:
Can you add abyssplug governor from abyss kernel? And can you add 25mhz and 50mhz?

Samsung Galaxy S II Powered by CyanogenMod 9 + Fluxxi Kernel
[Galaxy S II Original Android Development] grzesdroid:
Myfluxi you are amazing: D thanx !!!

tapatalk@ SGS ||
[Galaxy S II Original Android Development] xator91:
Updated first and second post with new update (12/06/2012)

Sorry for the mistake..
[Galaxy S II Original Android Development] AvRS:
Was proven by Gok to be nothing more than a renamed hotplug governor so would be worthless in this kernel and we already have a tweaked Ondemand which works perfectly. My advice would be to stick with that kernel if you like it that much or search the forum for abyssplug or assplug (I'm not being rude that's what it was referred to as so may help you find posts about it).

---------- Post added at 01:47 PM ---------- Previous post was at 01:47 PM ----------

It's just been updated today a couple of posts earlier than yours ;)
[Galaxy S II Original Android Development] xator91:
Updated now the thread with XX02-beta4 (14/06/2012) changelog post too ;)
[Galaxy S II Original Android Development] sakindia123:
thanks for the new app,although i get a "Kernel not supported" in beta5(no such thing in beta3-I think u implemented some sort of version checker) ,the app still works flawlessly :)
[Galaxy S II Original Android Development] myfluxi:
Please search this thread about my opinion about pegasusq on the sgs2. It's one of Gökhan's dreams, and I wholeheartedly respect his excellent work on getting it running on our device. But again, imho it offers no advantage at all.

If I work on a kernel for the sgs3 I will surely use some of his knowledge about the nessecary steps to patch cpufreq and hotplugging logics. But even on a quad core - I do not see the advantage as there are no applications (except for demos and benchmarks) that effectively make use of multicore.

If you need pegasusq, allright but please search elsewhere :)

Regarding the other topic, :D:D:D @ AvRS

@xator11: thanks!

@sakindia123: It checks for FLUXI in the kernel name - not to protect it but to avoid whining users, "IT DOES NOT WORKZ!!!"
[Galaxy S II Original Android Development] xator91:
Thanks too for your best kernel :)