yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Honusnap:
Did you tried a game at 67Mhz, a demanding one .. to see if the problem is not on the Antutu side ?

If i remember correctly 1300 is the cumulative performance you can achieve (2D+3D) at 267Mhz => Perhaps Antutu apply its own max settings before running its test.

I've just tested "Reckless Racing 2" at 67Mhz, it's playable but it's definitly smoother at 160Mhz.
[Galaxy S II Original Android Development] :
You should talk to Gokhan, maybe he knows how to fix this. I think he fixed it on his kernel, so he could give you the answer.

Post here the last beta with the old mmc driver, so everyone could try it. It was after this beta that slow motions started to happen.
[Galaxy S II Original Android Development] djdeeles:
First I tried game its same. Quadrant same fps values.

Setting in voltage control is ok no problem I said.
[Galaxy S II Original Android Development] Lownita:
I find this kernel a bit more choppy than siyah. For example when opening a folder in apex launcher or opening/closing the app drawer, I see some small lag here and there. And also the overall scrolling feeling is smoother on siyah.

What settings could I change to make it feel like siyah, any suggestions?

Thanks!
[Galaxy S II Original Android Development] :
Yeah, I'm also feeling this. Older versions were never like this :(
[Galaxy S II Original Android Development] yahyoh:
dont use 67 gpu step ;)

---------- Post added at 03:48 PM ---------- Previous post was at 03:48 PM ----------

dont use 67 gpu step ;)
[Galaxy S II Original Android Development] :
I'm not using 67, in fact, I will never use it and never used it. 160/267/267. I'm using the same settings I used on older versions, and they were always perfectly, I had the most amazing performance. Now it's a bit laggy, as the guy said.
[Galaxy S II Original Android Development] yahyoh:
what cpu governor ? :rolleyes:
[Galaxy S II Original Android Development] :
ondemand, not tweaked.

Here's my settings

SIO

AFTR or LPA

xxKernel Gingerbread

160/267/267 GPU

900mV/950mV/950mV GPU

GPU thresholds: 85/75/100/80

I always used those settings, and it was always perfect
[Galaxy S II Original Android Development] myfluxi:
Our problems are completely different - not even remotely connected. Please try to understand even the basics, or please, please use Siyah :)
[Galaxy S II Original Android Development] :
I know that what happens on this slomo bug here is the same that happened on siyah. The cause could be the same. But you don't really need to throw in my face that you know more than me. thanks for letting me try to help.
[Galaxy S II Original Android Development] superleeds27:
Mustbe like the 4th time now ive seen someone say 'Ask Siyah'

Just let him solve it himself, Chances are the two things wont evn be related
[Galaxy S II Original Android Development] myfluxi:
Look, the mmc driver was introduced with beta5, slomo started with beta2. Notice something? I'm not in your face, you are in mine because if you looked at those changelogs you would have noticed :)

I don't generally follow Gökhans threads or repos, sometimes something catches my eye, e.g. if a user points on something. Like the invert function which I trigger completely different by sliding instead if pushing a button.

If I understand it right and please correct me if I'm wrong, the slowdowns in Siyah happened due to missing mutexes in his BLN implementation: https://github.com/gokhanmoral/siyahkernel3/commit/7c5958075dbef14441380b477fb82e97f92d5e01. As a matter of fact I did not touch BLN weeks before it happened here - no way bits and bytes magically transform to create a problem which didn't exist before.

Over here we have a problem with cpufreq and I may have solved it by reverting a commit which can be found here: https://github.com/myfluxi/xxICSKernel/commit/b1fdf66b9a33d0c35ef544603530afc2f9b878d8. And I mean it serious if I say: Maybe I'm too stupid to see the cause directly because I don't. I know what's happening but I have to see a few more logs with my debug kernel to really understand.

And by the way, by tracing though thousands of lines of code I found another bug so whatever happens with slomo, it made me a better person in regards of dealing with problems. I will do some things different from now on because monitoring two big communities, xda and android-hilfe.de requires huge amounts of ressources and has to be managed a bit differently than just our German forum before.

Question: This light-buttons-on-touching-the-touchscreen. Please tell me what exactly happens because I never ever used a Sammy ROM for more than 5 minutes. So I'm again too stupid to know. :)
[Galaxy S II Original Android Development] :
I've never asked this "light-buttons-on-touching-the-touchscreen". Please, just chill dude, I'm just trying to understand how things work. If you are going to get stressed on replying to me, just don't reply. Remember, you were also a student :)

I've only see slomo reports after the new mmc implementation, in fact, it was when I got it for the first time. Okay, just they are different problems is okay. Thanks, i'll never bother you again.
[Galaxy S II Original Android Development] superleeds27:
Like i said previously. If you used the search function on this thread you would release that the Slow Mo's started around beta 2 for some people.

3 Beta's before the new MMC driver was introduced, like MyFluxi said.
[Galaxy S II Original Android Development] myfluxi:
Oh, I was asking everybody about this touchscreen/led function. The forum software just does not allow two consecutive postings so I put it in one. Forgive me if it wasn't clear enough.
[Galaxy S II Original Android Development] Testraindrop:
As far as I know, the Samsung implementation is as follows:

You touch screen -> Led lights go on,

if you touch screen again in an intervall (say 5seconds), the lights stay on for again 5 secs and so on.

Basically the same as you now touch the buttons and they light up, only with Screen as trigger.
[Galaxy S II Original Android Development] myfluxi:
Sounds stupid but I'll look into it, thank you und dankeschön! Prima Wetter, gelle?
[Galaxy S II Original Android Development] Testraindrop:
If you implement it, then only as an option please :)

Jup, ausnahmsweise mal super Wetter :)
[Galaxy S II Original Android Development] myfluxi:
OK, it's already there. I just have to decide where to add the sysfs (keyboard or touchscreen module) and which options to include, e.g separate timout options for buttons/screen.

Any ideas?
[Galaxy S II Original Android Development] AvRS:
I don't like it but can see why some do so would say keep to one timeout setting to be less confusing but just have the ability to choose which you use, screen or touch keys.

Sent from my GT-I9100
[Galaxy S II Original Android Development] iamnotkurtcobain:
Can you post a screenshot of your gpu settings too? Thanks.

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II Original Android Development] rzat:
Whatever u decide please keep current setup available. Sammy screen trigger is like u said stupid. So yeah i vote for separate time out/off
[Galaxy S II Original Android Development] BigShix:
It's very annoy about "Slide-to-Invert" because I always active it while typing on screen keyboard. Each time two finger press on the left and right side of screen, it turn to Invert mode which not need to "Slide across the screen by two finger" ???

The developer should have an option to disable it on xxTweaker.
[Galaxy S II Original Android Development] coloxim:
i don't like this function...

fluxi can you add breath bln when i plug the phone..because i don't use bln only when the phone is chargin and when is autoctive the bln are only "static"..if i change when unplug the phone i've bln active...
[Galaxy S II Original Android Development] CRXed:
Today I got the lockscreen bug again with beta 9, so back to beta 5 again.

Am I the only one having this problem?

And if yes, what can I do?
[Galaxy S II Original Android Development] sasho36:
Tried it this afternoon and had the slow-down bug. Here is the logs just after reboot. Hope it helps you find the source of the bug.
[Galaxy S II Original Android Development] CRXed:
So in 14 hours, you played with your phone for 9 hours??

I find it hard to believe.....:confused:

@Myfluxi:

Can you make a change to the buttons in your screens? They do not fit on a standard 240dpi, see screenshot. Maybe you can move them lower, below the actual number you can change.
[Galaxy S II Original Android Development] Honusnap:
Well in general student do not try to teach the teacher.... the problem was certainly here.

It remember my grandmother that was always behind me when i was fixing something in her house... she was unable to do things but always able to teach others how to do ... :D

Myfluxi is using a lot of is time, there is a problem in the news releases.. he certainly now how to get informations to solve this... be confident in his capacities.... i'm.. ;)

---------- Post added at 08:06 PM ---------- Previous post was at 08:03 PM ----------

It's for people that do not know where their buttons are ... :laugh:

=> Attached : I got a slowmotion experience on beta9, just after unlocking the screen, the phone works normally for some seconds than becomes very slow, got a black screen for 7 seconds than some message "Go launcher is irresponsive, wait, close"... choose wait then it was like i was gave some processor time for 1 second.. than again irresponsive... i played this game for a minute or something like that, then everything back to normal.

It is not really slow... using only 100Mhz as CPU frequency is faster than that, it's irresponsive, like you would be given 1 second of processor every 15 seconds... don't know if this can help.
[Galaxy S II Original Android Development] yahyoh:
please please please don't add this sick thing like sammy rom (wtf every time i touch screen the buttons will light :mad: ) i really hate it :crying::crying:

and really thank for ur hard work ^^
[Galaxy S II Original Android Development] anshmiester78900:
guys how to install the tweakr ? its in zip
[Galaxy S II Original Android Development] pelpa87:
I prefere them off till i touch one of them....why must them be on if im not using them? I also know where they r...so why i need them on while i m not using them.....

If u implement it...would be nice if it is as an option
[Galaxy S II Original Android Development] msquared:
Remove the previous version ,if you have it, and flash it throught recovery
[Galaxy S II Original Android Development] anshmiester78900:
thnx :)
[Galaxy S II Original Android Development] rage77:
I have the exact same problem. Logs of interest or use?
[Galaxy S II Original Android Development] AvRS:
Logs are the only thing of interest or use when reporting bugs as saying you have an issue isn't an easy thing to debug so please add logs for myfluxi to check out :)
[Galaxy S II Original Android Development] superleeds27:
Slow mo bug. Beta 9. First time i've had it!
[Galaxy S II Original Android Development] anshmiester78900:
Guys im on beta9 and in screen settings i have increades the gama 10 more it will not effect the screen in negative way right ?
[Galaxy S II Original Android Development] kilometers4:
Any plans to have dual boot on your kernel?
[Galaxy S II Original Android Development] malikalhaji:
Nope
[Galaxy S II Original Android Development] yahyoh:
for god sake do really want to use two roms in ur mobile !!!!!!! if yes go for syiah :rolleyes:
[Galaxy S II Original Android Development] Ok_Kaleidoscope5109:
if you use the open source display driver, is navigation completely impossible?

I understand the compass screws up, but how does Google Maps Navigation run? Acceptable?
[Galaxy S II Original Android Development] kilometers4:
Woah, it's just a question. Just curious if Fluxi has plans for it..

Edit : and to answer your question, I want as many roms as I can get on my phone ;)
[Galaxy S II Original Android Development] tariq2kn:
Will this kernel be available for stock roms???

Phone: XWLPD

Modem: DDLP8

Kernel: Phenomenal 5.5 Medium

Theme: ICS Domination + 15 Toggles

Launcher: Apex Launcher
[Galaxy S II Original Android Development] Testraindrop:
Nope

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II Original Android Development] mundixx:
anyone else having the dreaded suspend_backoff wakelock with beta9? this is seriously killing the battery :-(
[Galaxy S II Original Android Development] OutCold44:
I'm afraid suspend_backoff is not kernel related.
[Galaxy S II Original Android Development] mundixx:
How to solve this? I was assuming it's the kernel since it was listed under Kernel wakelocks
[Galaxy S II Original Android Development] :
Reproduce the slomo bug: EVERYTIME when scrolling tabs on Chrome, it freezes and start the slomo. It's impossible to use chrome.

Here's some logs
[Galaxy S II Original Android Development] pelpa87:
@myfluxi

Xxtweaker-->cpu-->horplug settings--> FC

Does anyone else having this issue in beta 9 and latest xxtweaker??

Myfluxi...do u need a log?? I ll make it...
[Galaxy S II Original Android Development] antt00:
No FC here also with beta 9 and latest xxtweaker and CM9
[Galaxy S II Original Android Development] AvRS:
It's not worth posting bugs without logs as mentioned by myfluxi countless times as it's not affecting everyone.
[Galaxy S II Original Android Development] Honusnap:
1 - create a log

2 - go in cwm and clear xxtweaker settings
[Galaxy S II Original Android Development] coloxim:
With this kernel in las cm9 long Press for kill app.. doesnt work...

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] Jagdish84:
Try increasing the led timeout to 3 seconds, had the same issue with dorimanx kernel and worked for me...

Sent from my GT-I9100
[Galaxy S II Original Android Development] Hawkeye1103:
It's from the language... for some reason if you are on spanish language it FC's
[Galaxy S II Original Android Development] coloxim:
Noooooo.ufffff.....i 1 sec..ill try...

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] Siemser:
U need to go in settings - developer settings - tick the option to kill app through long press

Gesendet von meinem GT-I9100
[Galaxy S II Original Android Development] coloxim:
I know..but doesnt work...if I set more than 1 second...works...thanks for the help..
[Galaxy S II Original Android Development] myfluxi:
Please do yourself, myself and the other users a favor and at least flip though the last pages before posting redundant info.

It is a confirmed bug in the spanish translations and a reason why I don't like anything else than my stuff inside the code. If something is messed up at least I know who is responsible...

Please read the CM9 thread, many users were complaining about this ROM related problem. CM hard coded the trigger value to 2 seconds which is was too long. Newer nightlys make the value adjustable. No matter how long you set LED timeout, it will always work. Even 3 seconds kill timeout work with 2 seconds LED timeout.
[Galaxy S II Original Android Development] myfluxi:
Kernel Update Fluxi ICS XX.02-beta10

Slomo may be actually two bugs, which explains why it happened much less with beta9. So those observations regarding the mmc driver were not totally unfounded while the conclusion may have been a bit off. Let's see what happens.

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

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

Changelog:

Kernel: Fix typo in ext4 driver that may have caused those slowdowns on wakeup and unlock

Kernel: touchscreen: Optionally flash LED buttons on touch, not in the tweaker app yet, if you need it *now*, echo/write time in ms into /sys/class/sec/sec_touchscreen/tsp_flash_timeout, e.g. for one second

echo 1000 > /sys/class/sec/sec_touchscreen/tsp_flash_timeout

Fileserver: On download instead of "download.php" correct filenames are saved
[Galaxy S II Original Android Development] francesco.cordella:
Thanks!
[Galaxy S II Original Android Development] myfluxi:
Again, thank me when everybody is happy again. Thanks to you, though :)
[Galaxy S II Original Android Development] superleeds27:
Glad to see we're making progress
[Galaxy S II Original Android Development] gdskp:
Kernel: Fix typo in ext4 driver that may have caused those slowdowns on wakeup and unlock

Does it mean we have less wake up lag?
[Galaxy S II Original Android Development] mbutandola:
I must admit that I'm feeling the same. Phone is definitely more jittery than when I first used this kernel. And I don't tweak anything. Always use default settings but scrolling is not as smooth as it used to :(.

Envoyé depuis mon GT-I9100 avec Tapatalk
[Galaxy S II Original Android Development] myfluxi:
Actually no, this just corrects an error introduced with the update to Linux 3.0.33.

The wakeup process is determined by wakeup time of all those devices which is significantly longer in ICS than in GB. There is no cure at this time but it's also not as bad as some experience it. Looking at the kernel log, wakeup times are around 0.5-0.65 sec which is acceptable. I myself do not feel bugged about ICS's behaviour, I don't have an excessive number of apps installed though.

Regarding smoothness: Checkout beta10 with the fix mentioned above.
[Galaxy S II Original Android Development] victorator:
beta10 is out
[Galaxy S II Original Android Development] AvRS:
Indeed it's 7 posts before yours ;)

Fluxi always posts updates to this thread as well as the German forum.
[Galaxy S II Original Android Development] ivangs1:
Any feedback about beta 10?

I have used beta 9 with CM9 but i had big battery drain from wifi wakelock.
[Galaxy S II Original Android Development] sakindia123:
i feel it's a bit jittery than before,and lots of battery drain on idle :(

or mayb that's just me i guess
[Galaxy S II Original Android Development] iamnotkurtcobain:
Don't know why but beta 8 had better battery life than beta 9. Have to try beta 10 but I guess battery life would be the same as beta 9...

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II Original Android Development] BigShix:
Hi myfluxi

Could you make an option to disable "swipe to invert" because this annoy to me. I using much on typing and it something go to invert when I press left and right side screen same time. And something it change to invert and normal and invert contiously while I typing on screen.

Thank you.
[Galaxy S II Original Android Development] diddly3000:
Using this beta 9 on cm9 rc1 having massive cpu usage from kernel according to badass battery monitor. Anyone else got this.??

Should I just use cm9 default kernel that comes with rom or maby Version 1 final fluxi do you guys think.

Any other kernels for cm9 with good results?
[Galaxy S II Original Android Development] Testraindrop:
Use CM9, Siyah, whatever Kernel and be happy or provide logs. easy as that.
[Galaxy S II Original Android Development] elite_gamer04:
Bajee and I have been battling it out to try and figure out why the translated xxTweaker doesn't save settings after a reboot - seems like a few of us are having issues.

I'm on CM9 myself and have tried the usual suspects; Permissions to 777, reinstall of the Kernel (after Cleaning Script), moving of .apk etc to no avail :(.
[Galaxy S II Original Android Development] :
Thanks mate, I'll try that now.
[Galaxy S II Original Android Development] msquared:
How does it work on CM9??
[Galaxy S II Original Android Development] mbutandola:
I think you just need to hit on any CPUIdle mode even if it's already ticked. Guess it's then triggers the settings being saved on xml file. Well, worked for me. :)
[Galaxy S II Original Android Development] eric-filth:
Bajee

I unzip the xxTweaker to translate for Brazilian. But i need one xml editor you know one to use with android?

What file is need to translate?

Enviado do GalaxyS2 usando Tapatalk 2.1
[Galaxy S II Original Android Development] sohebq:
how to turn off menu key lights?

edit: found it
[Galaxy S II Original Android Development] fronti90:
there are problems with the original version too so i am not sure if this is due to the translation
[Galaxy S II Original Android Development] DSC05:
@elite_gamer04

Have you updated the su binary too?
[Galaxy S II Original Android Development] XDA mark:
See the picture for my current status. I installed Fluxi this morning, so this is still the first cycle.

SIO + Ondemand, 200-1200MHz, mild undervolting, 2000mAh hours battery.

Main activities, whatsapp, 20-30 minutes call with viber, some youtube and internet browsing. Will post more screenshots when my battery reaches 1% :)
[Galaxy S II Original Android Development] spelaben:
Update your Superuser binary if the settings are not saved, even if it is telling you it is already up to date. If you are using SuperSU, get rid of it and get Superuser. Worked for me.
[Galaxy S II Original Android Development] edangel:
Wow..thanks..that worked for me..did already 3 reboots and settings are still saved..even xxtweak app remain in english language!thanks mate... :D
[Galaxy S II Original Android Development] bajee11:
Here you go..

1) Decompile xxtweaker apk

2) Go to /res/values/

3) Translate strings.xml and arrays.xml

4) Recompile apk

5) Take the apk generated in /dist

6) Sign the apk

And your done!

You could modify xml files in several ways, Notepad ++ is one way to edit it. Since I don't know German, I translated everything with Google Translate Toolkit. If you got more questions, let me know. :)
[Galaxy S II Original Android Development] TaoNinja:
Just tried this with Ressrection Remix 1.9

And this Kernel is having problems with the WiFi on that ROM,

Anyone else having the same problems?

Really love this Kernel so much ^_^

Hope there will be a fix for this soon...

Keep up the GREAT job guys!

Fluxi all the waaaaay :)
[Galaxy S II Original Android Development] wonsky21:
Every attempt to decrease Voltage table even 1 step down (1075, 975, 975) ends with freeze form me... I guess I have to live without it :/
[Galaxy S II Original Android Development] Boonyard:
anyone got a mirror? Keeps trying to download a PHP file and not a zip from current links.
[Galaxy S II Original Android Development] eric-filth:
Thank you very much.

But i descompile and cant see /res/values

Here one picture with folders i have.

Enviado do GalaxyS2 usando Tapatalk 2.1
[Galaxy S II Original Android Development] bubba949:
Rename the php to zip and it will work.
[Galaxy S II Original Android Development] bubba949:
rename the .php file to.zip and it will work.
[Galaxy S II Original Android Development] gsmdb:
Using the EN xxtweaker bln breathing is grey out? Does the breathing work at all in xxtweaker? If it works how to set up the breathing steps?

EDIT: Got it.

New question. How to make a double breathing sequences; breath one, pause, breath twice, pause, and so on?
[Galaxy S II Original Android Development] XDA mark:
+1, just to confirm this will work. I changed the name from download.php (if I remember correctly) tot Fluxi.zip, everything ok no problems.
[Galaxy S II Original Android Development] shadowblade330:
If u don't want the bugs just use xx.01 I felt that one was least buggy and least kernel wake locks. The .02 betas are still that betas but it will be different for everyone cuz of different usage.
[Galaxy S II Original Android Development] myfluxi:
I think you already mentioned this some time ago and I tried hard to reproduce it but failed. However I don't want to clutter sysfs with even more options and decided to improve movement detection instead. Try it out, just for you, my friend from Hanoi ;)

Slide2Invert test: fluxi-kernel-sgs2-XX.02-b10-s2i.zip

Regarding battery life in beta8, 9 and 10. Any assumption is completly pointless as there are no relevant changes whatsoever. The same applies to smoothness, cpu usage and all that stuff. Sometimes it's scary to read those comments, not just in this thread, I mean it in general.