yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] enigma1981:
I'm inclined to agree with that... I swapped to LulzactiveQ this morning and I've had no problems at all today so far

Swyped from my GT-I9300 using Tapatalk 4 beta
[Galaxy S III Android Development] Ha_Ha Shoes:
I changed a few settings and Beta 2 is awesome.
[Galaxy S III Android Development] lkirra:
Stock XEMC3

Boeffla Kernel 2.11beta4

> Lulzactiveq

> Row

> Freq 1000MHz

> Heavy Undervolt

> GPU 160/266

> Heavy Undervolt

> SD card Tweak 1024kb

> zRam Swap 600MB

Smoothness playing games and @ Wifi Browsing most of the day!
[Galaxy S III Android Development] fatiherkoc:
Beta 4 my settings.

Zzmove battery

Row

Cpu -100

Gpu-100

Zram swap 400mb

Cpu max freq 1200

No black screen, no fc, no problem running one day...

Thanks.....

---------- Post added at 04:08 PM ---------- Previous post was at 04:05 PM ----------

Beta 4 battery performance...

Original samsung 3000mah battery...
[Galaxy S III Android Development] Agaranda:
Just now I've got a black screen.

Changed to Boeffla-moderate and CFQ.

I'll report results.

I9300XXEMC3, Boeffla 2.11b4, Earsonics SM3v2
[Galaxy S III Android Development] Pusheka:
All "-FS" problem.
[Galaxy S III Android Development] andip71:
2.11-beta5 / 2 flavours

Hi guys,

ok, it seems beta4 is already much more stable than 2 and 3. This indicates a toolchain problem.

However, I still have too many reports about weird behaviour, so I decided to further nail that down with you in the next beta.

Situation is:

Kernel with zzmoove 0.4 and without zRam worked fine (beta1)

Kernel with zzmoove 0.4 and zRam seems to give various issues

So the question is - is one of the two functionalities itself the issue, or the combination of it?

And the best is: I could also see some laggy behaviour first time on my phone with zzmoove opt-fs and 400 MB zRam.

In order to help me finding that out now, I decided to release two flavours of beta5:

boeffla-kernel-2.11-beta5-zz3_zram

This is the same as beta4, just zzmoove is downgraded from version 0.4 to 0.3 (this means, fast scaling is not available anymore), zRam is included

boeffla-kernel-2.11-beta5-zz4_nozram

This is the same as beta4, just zRam has been removed, zzmoove 0.4 is still in

I would really appreciate if you would choose the version you are more interested in (either if you like zzmoove0.4 more or zRam), flash it and report back how it goes.

Of course you can also test both of them.

By this we should be able to find out what finally the issue is (fingers crossed!).

Please note, these versions are only available on the kernel homepage this time, not via load&flash in Boeffla Tweaks app!!!

Thanks

Andi
[Galaxy S III Android Development] Pretzel Kleo:
Gonna test zram version! Reporting later!

Enviado desde Samsung Galaxy S3 con Omega Rom v43.3 & Boeffla Kernel v2.11b4 usando Tapatalk II Premium.
[Galaxy S III Android Development] enigma1981:
That's some serious user support right there!! that's six test versions for us to try and iron out all our issues... That's awesome Andi, just awesome!!

Swyped from my GT-I9300 using Tapatalk 4 beta
[Galaxy S III Android Development] andip71:
Thanks enigma. This is the only thing I can do.

Most of the time I cannot replicate the issues (apart from today), so I see it as my obligation to give you as much good test versions to verify and hopefully detect a pattern soon.

I really get headaches with that meanwhile, so I want to finally sort it out.

All your help and patience is highly appreciated!!! :)

Thanks for all.

Andi
[Galaxy S III Android Development] Pretzel Kleo:
So far... the first boot was faster! a lot actually, my launcher (Next Launcher) loaded in 2 seconds and with other beta versions it was like 5 or 6, applications opened very fast and no lagg yet.

I changed my settings... was using undervolting CPU and overvolting GPU (complete setup a few pages back), as I already said beta2 was perfect with that but beta3 and beta4 while playing games made my cellphone reboot, happened to me like 5 times.

So... Gonna test for a period of time this settings:

Governor: Lulzactiveq

Scheduler: Row

CPU Max Frequency: 1600MHz

CPU Undervolting: Off

GPU Frequencies: Stock

GPU Undervolting: Off

LED Fading: Fade (Bright)

LED Speed: x2

Touch Boost: Off

Sharpness Fix: On

AC Charge Rate: Stock

USB Charge Rate: Stock

System Tweaks: Off

Ext4 Tweaks: On

Sd-Card Tweaks: On - 512 kb

All the Supports: Off

Android Logger: Off

Kernel Logger: Off

zRam Swap: 400MB

If everything goes well I will use Undervolting and Overvolting... maybe that's the problem.

Enviado desde Samsung Galaxy S3 con Omega Rom v43.3 & Boeffla Kernel v2.11b4 usando Tapatalk II Premium.
[Galaxy S III Android Development] Tuckycv:
I'll give it a go at boeffla-kernel-2.11-beta5-zz3_zram, since I'm seeing problems with lagging on incoming calls (that's have been my problems too) where the phone is ringing and the screen remains blank for 3-4 rings. I've been readind same issues with perseus and using FS seems to be a common thing.
[Galaxy S III Android Development] enigma1981:
installing b5zz4_nozram as the "max running apps 50" doesn't play nicely with zram so I leave it disabled anyway... Will report back soon. :)

Swyped from my GT-I9300 using Tapatalk 4 beta
[Galaxy S III Android Development] ducky1979:
I had the freeze on beta 4 so just testing beta 5, I've downloaded the test no zram version just incase.

But apart from that I'm loving this kernel and your dedication to it Andi! Thank you

Sent from my Motorola brick (with aerial)
[Galaxy S III Android Development] SignetSphere:
Just flashed beta5zz4-nozram here andi all works well on mine. Just some minor lags since i underclocked/undervolted both the GPU and CPU. But apart from that no major problems so far on mine. :good:

my settings are still the same

Governor: ZZmoove - battery

Scheduler: row

CPU Max Freq: 1200 MHz

CPU Undervolting: -100 mV

GPU Freq: 160/266

GPU Undervolting: -100 mV

LED fading: stock

LED speed: stock

Touch boost: on

Sharpness fix: on

AC Charge rate: 1200 mA

USB Charge Rate: 475 mA

System Tweaks: On - Boeffla tweaks

Ext4 tweaks: On

SD card tweaks: On - 512 kb

CIFS Support: off

NFS Support: off

Xbox Support: off

exFat Support: on

Android Logger: off

Kernel Logger: off
[Galaxy S III Android Development] lkirra:
i think FS with Undervolting cause problem..i had problems when using both the same time, and no problem without the zzmove with FS..
[Galaxy S III Android Development] Pusheka:
Flashed beta5zz4-nozram

Governor: ZZmoove - battery-FS

Scheduler: row

CPU Max Freq: 1400 MHz

CPU Undervolting: -50 mV

GPU Freq: stock

GPU Undervolting: -50 mV

LED Fading: Fade (Bright)

LED Speed: x2

Touch boost: on

Sharpness fix: on

AC Charge rate: 1200 mA

USB Charge Rate: 900 mA

System Tweaks: off

Ext4 tweaks: On

SD card tweaks: On - 512 kb

CIFS Support: off

NFS Support: off

Xbox Support: off

exFat Support: on

Android Logger: off

Kernel Logger: off

All ok :)
[Galaxy S III Android Development] SignetSphere:
Hmm. USB charge rate at 900 mA? Just a friendly reminder my friend... setting it that high when usb charging may fry up your usb cable. I recommend setting it to its default value ;)
[Galaxy S III Android Development] ginzo:
I am testing beta5 with zzram now, the config is the following:

LulzactiveQ

Row

Cpu uv -25

Gpu uv -25

Zzram 400

All the rest default

All is ok and very smooth :):thumbup:

Tapatalked from my Galaxy S3

Rom: Maya v3 XXEMC2 ♥

Kernel: Boeffla 2.11 beta5

Modem: BUDLI2

Operator: Vodafone

Recovery: Philz Touch
[Galaxy S III Android Development] fuxmen:
Testing beta 5

Max 1000mhz

Uv both - 75

Zzmove battery

600 MB zram

Beta 4 gave me a lot of lags with 1400 and persaqus... Even one screen feeze after wake up for about 5s
[Galaxy S III Android Development] ZaneZam:
i doubt that this will fry anything as this is exactly the current specification of usb 3.0 ;) if at all it could maybe harm a motherboard of very bad quality when using this setting in combination with usb 2.0 which has a current specification of 475mA ;)

[MENTION=220904]andi[/MENTION]

thx for that multiple versions approach! :highfive:

[MENTION=535343]all[/MENTION]

thanks for all the reports about zzmoove/zram issues! its really a bummer hope we will find the culprit soon! anyhow in the meantime i've reworked the fast scaling part of zzmoove governor which will be then available in the upcoming 0.5 version (i'm right now testing beta). can not say much about it or if it fixes anything as it just got ready about an hour or so. looks good so far but i have to be patient, hope u can be that too. thx! ;)
[Galaxy S III Android Development] gsw5700:
Beta5 nozram, zperf a fine no issues (but I had no issues before! )

Seems to have more memory available too which is a bonus

Sent via TCP/IP
[Galaxy S III Android Development] andip71:
I just wanted to confirm what ZaneZam already wrote:

If your charger device (or USB port) cannot deliver 900 mA, the charger chip in the S3 will notice that automatically within milliseconds and automatically reduce the charging current until the current gets stable.

So there is not a real chance for any harm.

Andi
[Galaxy S III Android Development] arbi97:
What's it the ZZ4 and ZZ3 ? And which set me ?
[Galaxy S III Android Development] andip71:
zz03 is including version 0.3 of the zzmoove governor (by ZaneZam).

zzmoove 0.4 of that governor, however, supports additional functionalities like fast-scaling.

If you search the thread backwards a bit, ZaneZam gave a lot of information on it in a post.

Andi
[Galaxy S III Android Development] MIKEMON:
Great kernel

Hello everyone, I personally think that the biggest problem freeze and laggy on this great kernel undervolting using ZZmoove governor.

Always set to pegasusq or Lulzactiveq all right: Prsty kříženy:
[Galaxy S III Android Development] gsw5700:
Strange I've always used the zperf governor and haven't had a single problem. Users with problems might need to enable debugging/logging to determine the cause of the problem to see if there is a common pattern. I've tried everything to stress the phone but it just keeps running extremely well.

If anyone can repeatable get a lag or crash, please let me know and I'll try my best to reproduce it

Sent via TCP/IP
[Galaxy S III Android Development] MIKEMON:
Yes, but if I change the Pegasusq or Lulzctiveq everything is absolutely perfect
[Galaxy S III Android Development] fifi62820:
Hello I'm on beta 4 I configure my way and after a reboot my phone configuration is no longer taken into account although the hook boeffla tweaks are in the right place in my setup. I put 1.2ghz and after restarting it returns a 1.4ghz party customization for each entry. an idea please?

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Android Development] andip71:
I need a debug info file created by boeffla tweaks in order to investigate this...

Thanks for sending

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] gsw5700:
Cool, any chance you can pm me your Boeffla Config file? I'll try your settings and see if I get any issues . If I don't it must be something else...

Sent via TCP/IP
[Galaxy S III Android Development] Pretzel Kleo:
First "Freeze" + "Reboot" in my cellphone! I was playing Shadowgun and I had opened GameKiller... Memory Issue maybe? But I think it is caused by GameKiller and not a Kernel problem though.

Enviado desde Samsung Galaxy S3 con Omega Rom v43.3 & Boeffla Kernel v2.11b5-zz3_zram usando Tapatalk II Premium.
[Galaxy S III Android Development] fifi62820:
Ok thank you very much for this information. Good luck andi.

Good job i like this kernel

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Android Development] enigma1981:
Pretzel, stop cheating and your phone won't punish you ;)

Swyped from my GT-I9300 using Tapatalk 4 beta
[Galaxy S III Android Development] gsw5700:
Well tried running antutu stability tests etc which really stresses the cpu on zzmoove-fs and performance-fs on nozram Kernel, not one single issue, I'm giving up I can't get zmove to fail!

Sent via TCP/IP
[Galaxy S III Android Development] egopatagonico:
I'm testing the version without zram ... fantastic! recover my true s3. very smooth with no lag. Real Racing played very well! impossible to know battery performance yet.

Usted zzmove batery fc, row, and Heavy uv,

Swypeado w my fat finger
[Galaxy S III Android Development] Pretzel Kleo:
Sorry but I will have to decline... I have to, actually, since every time that a new version of Omega is out I full wipe the device, all my progress in the games obviously is erased and I'm not able to finish them.

Backup is not an option since my Internal Memory is Full of Games and Apps that I use almost everyday and my 32GB external sd is full of music.

Cheers.

Enviado desde Samsung Galaxy S3 con Omega Rom v43.3 & Boeffla Kernel v2.11b5-zz3_zram usando Tapatalk II Premium.
[Galaxy S III Android Development] MBurns2:
changing too often the governor (5/6 times every day) can cause hardware problems? ty
[Galaxy S III Android Development] rulala:
I test zz3_zram and zz4_nozram .

I found Lulzactiveq governor is not the best for Game .

zzmoove is the most smooth one. I Use with zzmoove performance-fs.

It is smooth even without zram 400mb when I play Dungeon Hunter4

zzmoove performance is also good . But -fs is better a little.

I think "zzmoove governor + zram " is not very well for me.

PegasusQ + zram is better .

Play Dungeon Hunter4 will "Lags" If You use PegasusQ + No zram.

So it is important to use zram when only use PegasusQ.

If zram and zzmoove 0.4 only can choice one. I choice zzmoove 0.4.

But zram indeed help a lot for 3d Big Game!! I test many times.

It just a pity that zzmoove & zram can't work very well.
[Galaxy S III Android Development] MBurns2:
two question:

-governor like zzmove battery allow me to increase my battery life even during 3g navigation ?

Yesterday i did some test and with pegasusq (touch boost activate) my phone goes fast (really fast) but my battery during 3g navigation goes down 2% every 4/5 minutes..then i tried zzmove battery and all seems to go better (2%on 10 min navigation)..i know that consumption are influenced from many factor..but it's only for asking if i must choose the right governor even for 3g navigation

-changing govern too often,can cause hardware problems ?

thanks..and thanks Andi for this awesome kernel :good:
[Galaxy S III Android Development] GzC:
I think I've encountered hardware problem? I always get high ram usage(600+ MB) no matter which rom or kernel I've flashed. Can barely do multitasking between two apps. Even it's a clean one without any settings and apps installed? :(
[Galaxy S III Android Development] sherlock5545:
600+ is normal on an s3, have you tried using zram? It's makes a huge difference for multitasking.
[Galaxy S III Android Development] andip71:
First of all: Yes, zzmoove is aimed to save battery, so it is very likely it consumes much less than pegasusq also during 3g navigation.

And NO: You cannot create any hardware problems by switching the governor. You can safely switch as often as you want :)

As sherlock said... this is normal. Android is designed to use your memory as good as possible. This means, everything stays in memory as long as it can. Android has a very sophisticated memory management for that. And you should leave it almost as it is.

But multitasking between apps should be fine, I do it all the time. However I have to admit, I debloat my firmwares always down to a minimum.

Andi
[Galaxy S III Android Development] GzC:
600+ never happened before on my own experience. It start to act like this since this week. zram seems interesting, what is your settings for the zram? I saw it does not work very well with zzmoove governor? Thanks anyway. :thumbup:

---------- Post added at 03:19 PM ---------- Previous post was at 03:10 PM ----------

I've done the same things too, was using light force rom(greatly debloated rom), plus I've remove some preloaded apps that I didn't use at all. Maybe I'm too care about the ram usage, because I like everything to be minimal. Do you recommend to use any ram management apps or mods(ram manager, v6 supercharger, etc)? :rolleyes:
[Galaxy S III Android Development] gsw5700:
If you want more memory, you should try the Gorgoid rom, it's only 329MB, very lightweight,stable and fast, works great!

Sent via TCP/IP
[Galaxy S III Android Development] GzC:
Thank you for your great kindness, I will definitely try it! :thumbup:
[Galaxy S III Android Development] pistoke:
Yesterday I had a black screen for few seconds. I opened Chrome and I got black screen immediately. After few seconds home screen came back. Now I was able to open Chrome. All the tabs were closed. I don't know if this was kernel related or not. Next time, how can I try to find out, what caused it?

Anyway, I'm on beta4.

Lulzactiveq

Row

CPU UV -75

GPU 266...533

GPU UV -25

Led fade bright

Other settings are default. So zram is off.
[Galaxy S III Android Development] andip71:
Hm, this sounds more like a glitch on the rom level. Especially as everything came back again.

Anyways, if we are really really lucky we could see something weird in the kernel log maybe. For that you have to enable kernel logger in boeffla tweaks.

When it appears again, you can create a debug info file in boeffla-tweaks and mail it to me. Not sure if I will see anything, but at least it is worth a try.

Andi
[Galaxy S III Android Development] rulala:
beta5 two version i am ok . so i back to beta4 to test.

Governor: ZZmoove - performance-fs

Schedule row

AC Charge rate: 1200 ma

System Tweaks: On - Boeffla tweaks

zram: 400

I had a soft reboot .

I think it is zzmoove 0.4 governor + zram problem.

when they work together , it will have issue.

and If this is true , beta5 should no one had any problem.

I don't think it is UV . OC problem.

maybe boeffla tweaks is another possible.

now I cancel it and back to off (Stock)

If soft reboot happen again , it is really zzmoove 0.4 governor + zram problem.
[Galaxy S III Android Development] Mickyman:
I'm currently using zzmoove battery. How will FS benefit me if I choose that one?
[Galaxy S III Android Development] andip71:
Hi, ZaneZam explained all very much in detail here:

http://xdaforums.com/showthread.php?p=40938139&highlight=zanezam#post40938139

Andi
[Galaxy S III Android Development] DonHuan:
I have serious lags when listen to music on 2.11-beta3, 2.11-beta4 with ZZmoove Opt and ZZmoove Opt-FS. Music interrupted for several seconds, then for some minutes OK, and then again. Though there were no lags on 2.10-beta2-linaro. The same configs except for ZRAM 600 on 2.11.

I'll test both 2.11-beta5 today and give my feedback later.

Thanks.
[Galaxy S III Android Development] Agaranda:
Everything OK now

Cheers

I9300XXEMC3, Boeffla 2.11b4, Earsonics SM3v2
[Galaxy S III Android Development] elbildozer:
Downloading....testing v 2.9
[Galaxy S III Android Development] Hbohd:
Are you talking about listening to music with screen turned off? It may be due to zzmoove screen-off frequency limit, which can be changed by sysfs (originally it is set to 500Mhz when screen is turned off)... You should try changing it on your own, here is what zanezam said:
[Galaxy S III Android Development] andip71:
Just to complete... in next beta 6, this frequency will be changed to 800 MHz already. Empiric tests in the German forum showed this is a good frequency where MP3 playback works fine, as well navigation is working ok.

Andi
[Galaxy S III Android Development] elbildozer:
it seems like it is nice kernel with so many options
[Galaxy S III Android Development] gsw5700:
I use a screen off frequency of 600mhz, playing music with the screen off uses 200mhz for most of the time and occasionally I see a peak of 600mhz. Playing music never stuttered. If you are running a lot more stuff, you may need to increase screen off max frequently to 800mhz

Sent via TCP/IP
[Galaxy S III Android Development] DonHuan:
Yes, screen off. What about 2.10-beta2? What was the frequency limit there?
[Galaxy S III Android Development] Pusheka:
Flashed beta5zz4-nozram

Governor: ZZmoove - battery-FS

Scheduler: row

CPU Max Freq: 1400 MHz

CPU Undervolting: -50 mV

GPU Freq: stock

GPU Undervolting: -50 mV

LED Fading: Fade (Bright)

LED Speed: x2

Touch boost: on

Sharpness fix: on

AC Charge rate: 1200 mA

USB Charge Rate: 900 mA

System Tweaks: off

Ext4 tweaks: On

SD card tweaks: On - 512 kb

CIFS Support: off

NFS Support: off

Xbox Support: off

exFat Support: on

Android Logger: off

Kernel Logger: off

1 day use and everything is super.
[Galaxy S III Android Development] SignetSphere:
Deleted. Found the answers above xD
[Galaxy S III Android Development] rensen:
The last betas for me not abe a lot of difference, really its my impression.

Yes i notify some microcuts in audio with latest betas since zram i think.

Talking about audio......for anyone work the volume buttons of the original white headphones and original music player?, for me not work now, its only me?

Also confirm again that USB mode with boeffla-tweaks some times broken and dissapear.

Back to beta 4 because i like zz 4.0 and zram for now.

Abe a nice week-end all here.!!!

THANKS
[Galaxy S III Android Development] andip71:
2.10 had still zzmoove 0.3 implemented, there was no frequency limit during screen-off. This has been introduced with 0.4.

Cheers

Andi
[Galaxy S III Android Development] GzC:
Seems problem had been pointed out now, looking forward for new feature soon. :thumbup:
[Galaxy S III Android Development] fuxmen:
Got just one hot reboot with beta 5 zram :) it was fun haha

Remind me times of lg o2x and even better of Samsung Galaxy i5800 had couple per day with it sometimes haha

But kernel works like hell besides that
[Galaxy S III Android Development] DonHuan:
You think it's normal to have such problem?

It's not good, IMHO.
[Galaxy S III Android Development] fuxmen:
I don't think it's normal but in betas yes :)
[Galaxy S III Android Development] lou2s:
Using beta5 zz0.4 without zram

Overall very good, no soft reboot for a day.

There was one bug noticed though (dunno if it is bug), sometimes when I unlock the screen, the foreground apps will be halted. E.g. I was using whatsapp, then I lock the screen with power button. Sometimes later I unlock the screen then whatsapp will be unresponsive. After several touches, android gave a msg that whatsapp had no respond and asked if wanna close it. I pressed close and whatsapp still stuck. I then need to go into application manager in order to force close whatsapp.

This had happened 3 times today. Whatsapp, line, and tw launcher independently.

Settings:

Zz battery fs

Row

1200, -50mV

Gpu default, medium uv

System tweak off

Other then this minor issue everything was smooth and the battery was good!

Thanks!

Sent from my Boeffla I9300
[Galaxy S III Android Development] cesarbuzatto:
Not wake-up

My phone sometimes, wont wake-up from sleep with this new beta, it happens 2 times with beta 5 and only pull the battery resolve this issue.

Any advice for solve this?

Iam using zzmove opt, default clocks, -100mv cpu, gpu default clocks, -75mv gpu, rom is Omega 43.3
[Galaxy S III Android Development] artyfarty:
decrease UV and try
[Galaxy S III Android Development] G1032:
I actually came on new to report the exact same issue. Music skips on all beta versions since with or without zram enabled. I've tried Poweramp, GMMP and the stock music player.Pegasusq governor.I've moved back to 2.10 beta2-linaro. Thanks.
[Galaxy S III Android Development] andip71:
2.2-beta1 available

Hi all,

version 2.2-beta1 is now available for download on www.boeffla-kernel.de

I thought, before I disappear this evening to do a business trip to UK until Friday, I release this beta.

Only change compared to alpha5 is a fix for the mic_mode settings.

Still would encourage everyone to update to beta1 now.

Thanks and have a great day

Andi
[Galaxy S III Android Development] ginzo:
Have a good trip Andi ;)

I download it now :) and I keep you informed for sure :thumbup:

Tappato dal mio misterioso Galaxy S3

Rom: Frankestein v2.1

Kernel: Boeffla 2.2 alpha 5

operatore: Vodafone