yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] sherlock5545:
Boeffla doesn't come with a recovery. You can flash the kernel on stock, no problem.

Sent from I9300 - UltimaROM - Boeffla Kernel
[Galaxy S III Android Development] burner07:
but the only disadvantage is that i don`t have custom recovery and root ?
[Galaxy S III Android Development] andip71:
In S3, almost no kernel comes with an own recovery (only Siyah did that for a while when I am not wrong).

Reason is: Different to Galaxy S1 and S2, in S3 the kernel and recovery partitions are separated (which is good).

So just flash the kernel you like, and flash the recovery you like (Philz is my recommendation).

Andi
[Galaxy S III Android Development] MIKEMON:
beta7

Beautiful and clean work guys / Andi § Zanezam / will be again tested for this amazing kernel.Opět precise and perfect, thank you very much:):)
[Galaxy S III Android Development] Erahgon:
Here's a small write-up I did on another thread about zRam:

- zRam is a kernel created swap device. It creates a disk of sorts in the RAM itself, rather than on the media drives (i.e. unlike traditional swap), and uses compression (most of the time).

- zRAM is like a balloon: It fills up as data is swapped out, and is compressed.

- The size denotes the maximum amount of total memory pages' size, before compression. This means, if you choose 512MB, for example: It will compress up to 512MB of data from the RAM before it begins caching out the data. The actual amount of RAM used will be equal to, or lesser than the value, depending on the compression ratio.

- Swapiness is the tendency of the memory management interface to use the swap space, rather than to cache out a memory page from RAM. 60% is considered normal for a Linux desktop. 90% seems like a good value for mobile. If anyone is getting lags, adjust this value before giving up altogether.

- The trade-off with zRam is the need for processor power, in order to compress data. The lag is noticeable during heavy multitasking or when swapiness is unnecessarily high. However, considering that cache is much slower, the trade-off becomes relatively minor!

- zRam is faster (and safer) than cache swap/eMMC and disk based swap, as zRam uses RAM, which is faster, and theoretically doesn't have a sector write wearing limit (unlike disk, or even worse: eMMC devices).

Sent from my GT-I9300
[Galaxy S III Android Development] yosef019:
where?

men this beta 5 was killer freezer

need reset settings from beta 6 to 7?
[Galaxy S III Android Development] andip71:
No need to reset.

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] khalid0099:
Installed feel its stable:thumbup:
[Galaxy S III Android Development] MIKEMON:
Yes, I accepted very stable, fast, and everything is fully functional, thanks

Just a question? Can not disturb / wake touch the On / function Jkay mode?

Otherwise, great work
[Galaxy S III Android Development] gsw5700:
Dude, I'm confused about your response, so others maybe also.

I said,

400mb ram means 400mb will be used for compressed ram. This will actually provide approx 800mb+ available ram depending on your own usage. I'm using 100mb ram and am getting about 220mb of actual ram from this. Cool eh.

You said

No no, it's not the size of the RAM drive, it's the size of the data it will take into the RAM drive before compression.

So I'm saying 400mb is the size of the ram drive and it could typically hold 800mb+ of compressed memory. Isn't this what you have said?

Sent via TCP/IP
[Galaxy S III Android Development] Erahgon:
I may have misunderstood. Apologies in any case! I'll edit my previous post.

Just to clarify: Say you have 300 MB of zRam enabled. To begin with (just after boot), zRam will be barely used. Meaning that the amount of RAM it will take as zRam will be very less (say 0 MB).

Now, the system needs RAM, so it swaps out pages of an app worth 30 MB. This 30 MB will be compressed, to - for instance - 20 MB, and take up 20 MB of RAM now.

This goes on, for a maximum of 300 MB of pages swapped out. However, the RAM used may be just 200 MB, depending on the compression ratio.

What I interpreted from your post was that you thought that the the size of the RAM drive will be 400 MB, and that it would compress the data and hold more than that.

Sent from my GT-I9300
[Galaxy S III Android Development] DocMarc73:
Sorry for continuing this:

How does all this translate into simple words? Does this mean the following: When i set a higher value, like 600 mb, the system starts to compress data earlier than at a lower (300 mb) setting?

Or what side effects do different settings have?
[Galaxy S III Android Development] andip71:
No. In easy words: the setting defines the maximum zram can consume from normal ram. When this is exhausted, android will again start to kill unnecessary apps.

So, you could even always go for 600 to get the maximum out of zram.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] Kyle07:
My S3 is blisteringly fast. It has never been this responsive before. Nice to see some good ol' optimisation making such a vast improvement.
[Galaxy S III Android Development] alberber:
Don't understand the differences between all zzmove profiles... Well, I know the differences in battery, opti and performance. But what does a FS profile do? And 1 core, 2 cores, 3 cores...?

Sorry, I'm a noob for this and don't get the logic.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Android Development] pricey2009:
B rilliant

O utstanding

E xtravagant

F antastic

F ull Featured

L ag Free

A wesomeness

You know the score.
[Galaxy S III Android Development] Pard0ned:
I was just getting really bad lag (of around 5/6 seconds) while trying to download a torrent, using ttorrent pro. Never happened before. Changed to Pegasusq and tried it again and was no issue. Was strange, and damned annoying. Lol.

Was using zzmove performance gov.
[Galaxy S III Android Development] SavanTorian:
hello xda-boardies and boeffla-kernel-fans. :)

this are the results of my "toogling test" between all the govenors, available in 2.12-b7...

in some cases, toggling may cause freezes and you'll have to hard reboot your phone by pushing the button

tests may vary from phone to phone and configurations of your rom...

these results are only reference points

the toggling test has been made on a gt-i9300 | 16GB peppleblue-version | firmware stockhybrid ap: md3 / cp: mc2 / csc: oxaemc2

ZaneZam works hard on the fix, the next test'll be within one or two day/s :laugh::good:

---

ok= toggling works bi-directional

fail= toggling fails in one or both directions.

toggling between govenors:

pegasusq

- default

<<>> 1. zz moove - ok

<<>> 2. zz battery - ok

<<>> 3. zz optimized - ok

<<>> 4. zz performance - ok

- boeffla (battery saving)

<<>> 1. zz moove - ok

<<>> 2. zz battery - fail

<<>> 3. zz optimized - ok

<<>> 4. zz performance - fail

- boeffla (moderate)

<<>> 1. zz moove - ok

<<>> 2. zz battery - ok

<<>> 3. zz optimized - ok

<<>> 4. zz performance - fail

- 1core

<<>> 1. zz moove - ok

<<>> 2. zz battery - ok

<<>> 3. zz optimized - ok

<<>> 4. zz performance - ok

- 2core

<<>> 1. zz moove - fail

<<>> 2. zz battery - ok

<<>> 3. zz optimized - ok

<<>> 4. zz performance - fail

- speedmod

<<>> 1. zz moove - ok

<<>> 2. zz battery - ok

<<>> 3. zz optimized - ok

<<>> 4. zz performance - ok

lulzactiveq

<<>> 1. zz moove - ok

<<>> 2. zz battery - ok

<<>> 3. zz optimized - ok

<<>> 4. zz performance - ok

toggling between user profiles at themselves:

power extreme <> OK <> power <> OK <> standard (stock) <> OK <> batt friendly <> OK <> batt saving

power extreme <> OK <> power

power extreme <> OK <> standard (stock)

power extreme <> OK <> batt friendly

power extreme <> OK <> batt saving

power <> OK <> standard (stock)

power <> OK <> batt friendly

power <> OK <> batt saving

standard (stock) <> OK <> batt friendly

standard (stock) <> OK <> batt saving
[Galaxy S III Android Development] rulala:
hi , All

in the theory , ZZmoove-Battery is Battery-saving in all ZZmoove governors.

But with my test , ZZmoove(Standard) governor save more than ZZmoove-Battery.

WoW. it Surprised me. I don't know it is right or wrong...

I will continue to use optimized and then performance...focus on their Battery.
[Galaxy S III Android Development] talhafarooq87:
AnDip could you elaborate how much we get undervolt in cpu and gpu when we select high undervolting? Thank you :)
[Galaxy S III Android Development] Pretzel Kleo:
CPU:

25: All stock voltages for all frequencies will be reduced by 25 mV

50: All stock voltages for all frequencies will be reduced by 50 mV

75: All stock voltages for all frequencies will be reduced by 75 mV

100: All stock voltages for all frequencies will be reduced by 100 mV

light: The following voltages will be applied (from 1600 to 200 mHz): 1400 1363 1300 1238 1200 1150 1075 1025 975 950 938 900 900 875 850

medium: The following voltages will be applied (from 1600 to 200 mHz): 1375 1338 1275 1213 1175 1125 1050 1000 950 925 913 875 875 850 825

heavy: The following voltages will be applied (from 1600 to 200 mHz): 1350 1313 1250 1188 1150 1100 1025 975 925 900 888 850 850 825 800

GPU:

Undervolting patterns

25: All stock voltages for all frequencies will be reduced by 25 mV

50: All stock voltages for all frequencies will be reduced by 50 mV

75: All stock voltages for all frequencies will be reduced by 75 mV

100: All stock voltages for all frequencies will be reduced by 100 mV

light: The following voltages will be applied (from low to high frequencies): 875 900 950 1000

medium: The following voltages will be applied (from low to high frequencies): 850 875 925 975

heavy: The following voltages will be applied (from low to high frequencies): 825 850 900 950

Overvolting patterns

o25: All stock voltages for all frequencies will be increased by 25 mV

o50: All stock voltages for all frequencies will be increased by 50 mV

o75: All stock voltages for all frequencies will be increased by 75 mV

o100: All stock voltages for all frequencies will be increased by 100 mV

Take a look in the official page of the Kernel.
[Galaxy S III Android Development] noobSU:
FS is something related to fast scaling. You can understand it by just hearing that. Though fast scaling sucks lil bit of juice. Not that much. But its more responsive than without FS. I always prefer w/FS. ( with Fast scaling )

1 core = only single core will be used for most of the tasks. Actually for every tasks i think. :rolleyes:

Same as above for 2 cores 3 cores etc. For me its useless. You have 4 cores. That is the thing makes your S3 a quadrant :D
[Galaxy S III Android Development] andip71:
As far as I have seen in some threads, it works on XXELKC. But have not yet tried myself so far.

The minimal version only exchanges one file, the camera HAL. It is worth giving it a try, very unlikely it breaks something.

Andi
[Galaxy S III Android Development] rab1412000:
Okay I'll try it soon. It's the only thing missing in this excellent kernel.

Sent from a Galaxy far, far away
[Galaxy S III Android Development] andip71:
I could build this fix into the kernel as well, but I expect Sammy to come up with new kernel sources soon. So rather prefer to wait and have the workaround by applying this fix for the time being.

Andi
[Galaxy S III Android Development] gsw5700:
I'm using the video fix on elkc and video works fine

Sent via TCP/IP
[Galaxy S III Android Development] andip71:
Thanks, GSW5700.

So, that is the confirmation finally - you can go for this fix :)
[Galaxy S III Android Development] maddes1402:
Good evening Andi,

some weeks ago you were so kind to gimme your permission to use your amazing kernel in my ROM. All I can say is that everybody is totally exited about it.

But today I recognised something weird. With your kernel the permissions of init.d scripts are always set to 777 instead of 755. First of all I was confused and thought I was drunken during the latest build and changed the permissions in my updater-script. But there everything is ok. Even after manually changing the permissions they were set back to 777 after reboot. With another kernel this doesn´t take place. So I guess it´s kernel related :D

Are you aware of this behaviour or is this your will? Dunno...scripts are executed at boot, of course. But to my knowledge 755 is usual.

Thanks, Matt
[Galaxy S III Android Development] andip71:
Hi Matt,

yes, I am fully aware. I set the permissions before execution to 777 to ensure people that do not give proper permissions do not run into problems.

I could set them to 755 as well, but did not encounter any issues due to the "more privileges" the scripts have with 777.

But if you tell me any downside of it, I am happy to change for the next version of course.

Thanks

Andi
[Galaxy S III Android Development] maddes1402:
Thanks for the fast reply. Well, no :D. I was just wondering.

Thank you ;)
[Galaxy S III Android Development] rab1412000:
Just flashed the video recording fix from the Boeffla site and all is working well.

Sent from a Galaxy far, far away
[Galaxy S III Android Development] PetritH:
I just like how fast this kernel is developing, people started realising that this is the best kernel out there.

Thank you Andi.
[Galaxy S III Android Development] andip71:
Great. As expected. Thanks for sharing the result.

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] rab1412000:
andiP

when i connect the sgs3 to my laptop via usb3 my phone gets charged but i dont get the mtp notification and thus cannot transfer files and whatnot.

however when i switch to normal usb, i get mtp and the phone is recognized as mass storage.

is this a known issue or is it an intentional 'feature'?
[Galaxy S III Android Development] andip71:
Neither nor. Have not changed anything regarding mtp or usb at all.

Cannot verify as I do not have a device with usb3 port.

Can you verify for us using stock kernel quickly?

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] mar72:
I use Win 8 and usb3 connection to PC, charging the and MTP connection works without problems.
[Galaxy S III Android Development] rab1412000:
Okay mar72 basically confirms that it works could be an omega v34 or some weird driver glitch either way it's no biggie as it works in normal usb.

I personally don't wanna fiddle too much with switching kernels in and out, as it can slightly risk something going wrong ;and I do use my phone for my business.

Sent from a Galaxy far, far away
[Galaxy S III Android Development] andip71:
Okay, thanks to all of you for reporting and confirming. I was sure it is not kernel related, but... you never know.

Thanks to all

Andi
[Galaxy S III Android Development] Jekle_Ace:
Any chance of the ramfs being updated to ELKC version? Thanks
[Galaxy S III Android Development] jbejaranogarcia:
Have you thought out, in the near future, a kernel boeffla configuration apk? As siyah, for example....thanks AndiP :)

Regards from Spain.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Android Development] andip71:
Yes, with next beta version this will be updated. However, ususally this does not really have any positive or negative impact when there are no major firmware versions changing.

Hm, no, not really. But I know some people started working on one, so we might have the choice one day.

And I already had some first thoughts as well, but not with real high priority.

Andi
[Galaxy S III Android Development] brunodu91:
How you to change equalizer and headphone ?

I can just modify sheduler and undevorvolt with set cpu

Envoyé depuis mon galaxy s3, rom El liberator Lkc v5. / 4.1.2 jb , Kernel boeffla 2.2 , apex launcher, thème syps. Purple .... via tapatalk 2
[Galaxy S III Android Development] andip71:
2.12-beta7a

Good morning,

apparently there was an issue with touch-to-wake getting phone calls dropped when the dark screen was touched during a call (although I could not replicate that on my side for whatever reason).

Anyway, a fix has been applied for this, so there is a new beta7 update called

2.12-beta7a

available already now.

Homepage or Load&Flash->Test.

Cheers

Andi
[Galaxy S III Android Development] Pretzel Kleo:
Thank you! Problem solved.

Enviado desde Samsung Galaxy S3 con Omega v43.5 & Boeffla v2.12b6 usando Tapatalk 4.
[Galaxy S III Android Development] andip71:
Superb, PretzelKleo. Thanks for the quick confirmation.

And thanks also for your help with the voltages, I was just about to write the same:

Everything (!!), really everything is described on the kernel homepage.

Just to point this out once again :)

Andi
[Galaxy S III Android Development] rowlers:
I've had 2 instances of phone freezing this morning, both required powering phone off. This is beta7. Will the updated b7 cure this?

Anyone else had issues with b7?

Thanks for the great support andip!

Tapatalk'd from my SGS3
[Galaxy S III Android Development] Pard0ned:
What is your settings? Have you undervolted anything?
[Galaxy S III Android Development] andip71:
So far no other reports about freezing.

Also stable for around 20 hours for me.

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] seth73:
i had just a freeze, but i had uv -75mv so maybe that was part of the problem (running fm radio, bt for a keyboard, jota+ texteditor, umts internet with firefox in the background and hitting 25% battery...) so i'm not sure who's to blame ;)

greetings

seth
[Galaxy S III Android Development] Ninolina:
Hi, AndiP, did you see my question from a few pages back? http://xdaforums.com/showpost.php?p=42499252&postcount=4558

Sorry for bothering. :)

Thanks in advance. :) ;)
[Galaxy S III Android Development] nelsonw:
Freezing? I think the FBI should stop this development. Bc for sure our S3s will start the SKYnet and end the world if you keep improving... Lol i never had a Android phone fast like this. Thanks!
[Galaxy S III Android Development] maatsby:
I've had freezing. I thought it was undervolting so I removed it. It happened again, so I removed zram. Happened again. I'm using Paranoid Android now to give that a try.

This happened on beta 5 and beta 7. I skipped beta 6

EDIT:

I should add that everything was stock except for the governor being zzmoove. I didn't test pegasusq, i had to have a useable phone for work so i tried paranoid
[Galaxy S III Android Development] bazz7777777:
Am I right in thinking if I don't use touch to wake I don't need 7a, cheers andip

sent from the moon
[Galaxy S III Android Development] andip71:
Hm, despite the fact I think this is a complete overkill battery-wise, i will check over the next days in the code and let you know. Ok?

Thanks

Andi
[Galaxy S III Android Development] andip71:
Yes, this is right.

However, the final version will have it included, so you could get used to it already :)

Andi
[Galaxy S III Android Development] sherlock5545:
Beta 7 is great, no issues so far at all. Thanks Andi.

Sent from I9300 - UltimaROM - Boeffla Kernel
[Galaxy S III Android Development] Ninolina:
Thank you for answering! :) I will wait for your replay on this. :) I know it may be a battery killer but I would like to have that as option. :)

Thanks. :) Your work is GREAT! :)
[Galaxy S III Android Development] alberber:
Isn't there a zzmove profile for quad core mode? All of them are for 1,2 or 3 cores? I would like to try performance profile with all cores working.

Maybe I'm missing something?

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Android Development] bixano:
Hey on every zzmove governor all the cores are on ! The thing is that only 1 core are on must all the time and really when you need all the 4 cores get on ! Try cpu stats and run some benchmark and you will see all cores working !

By the way I think to get very smooth UI we need 2 cores on, and I cant make this on zzmove , maybe someone could help me what settings in governor I need to change to put on the 2 core more fast ( maybe when I touch the screen ), I can do this very good with lulzactiveq, but I wanna this with zzmove =/
[Galaxy S III Android Development] lkirra:
Nice build on this sir AndiP

2.12beta7a is great!

The touch on wake don't work on my s3

And is the feature eat up battery on sleep if it work?
[Galaxy S III Android Development] sherlock5545:
Touch2Wake isn't supposed to work all the time. You decide within how much time you can touch the screen to wake the device again if it were to time out. I set it to 20 seconds, which means after those seconds, touching the screen won't do anything.

Sent from I9300 - UltimaROM - Boeffla Kernel
[Galaxy S III Android Development] bixano:
I had my first freeze since the version 10, it was with last beta 7, I opened need for speed most wanted, and the phone freeze and reboot it self, I think it was because of UV, but I aways use -100 for cpu and -75 for gpu, all the things stock and zram 400mb, I put gpu and cpu a little bit less undervolt -75 and -50, I will try and post here if it happens again ! Sorry my bad english ! I try to write this very quikly im late to work ! =P
[Galaxy S III Android Development] lkirra:
touch2wake

is it supposed to wake the device at touching the screen for the given time?

it does not work for me, though 2.12beta7a build is really good.

touch2wake is the only thing that does work for me..
[Galaxy S III Android Development] Hbohd:
Nope, it is working in completely other way. Let's go to the "display" settings in normal android settings, than change 'screen timeout' to 15sec (the shortest one, just for testing purpose).

Than choose in boeffla tweaks app some time for touchwake feature (lets say 20 sec).

Next step: you let the screen to turn off without touching it, so after 15 sec it goes off. And then you have 20 sec to bring it back by simply touching it (for the first time you should feel like a magician :D )

And it's all ! It works only after screen timeouts, not when you turn it off by power button :)

Many ppl may find it useful, you have to check if you really need it.

Cheers !
[Galaxy S III Android Development] bounti:
Just wanted to say thank you for this amazing kernel. EVERY issue I've had since getting my phone 6 months ago is now gone. Issues included...

- Extremely slow charging (biggest gripe).

- Voice recognition not working if the phone is on more than a few hours.

- Random freezes and stutters (most noticeable when playing music).

- Complete unresponsiveness when launching a large game (eg MC4 or Shadowgun) if the phone's been on for more than a couple hours, forcing me to do a hard reset.

- Horrible battery life (8-10 hours with as little as 30mins screen-time)

From day one I've been using Siyah Kernel coupled with the OmegROM but recently decided to give the UltimaROM a try before switching to Boeffla after noticing it had init.d support (I use mattiadj's memory swap mod, so it's a necessity for me). I feel like it's the first time I'm really seeing what my S3 can do. So again, thank you. :)
[Galaxy S III Android Development] alberber:
ZaneZam

Will you be providing a new scriptpack together with the new version? I've been having a look at SetCPU and I see some things have changed or new things have been included.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Android Development] MIKEMON:
So after using everything seems fine.

battery, Touch2 wake all fantastically functional

still be tested Zzmoove, but I think it will be a sensational start to the stable beta7

Thanks to all
[Galaxy S III Android Development] eyalpaz:
hi,

first of all, i've gotta praise this kernel and beta 7a in particular, cause it is just perfect. butter smooth, responsive, perfect audio and about 1.4%/per h battery with 600 zram.

one question though, does anyone know how to config jkay lockscreen to 1 minute timeout (rather than the 17.5 seconds it is now)?
[Galaxy S III Android Development] sherlock5545:
You should ask that question to the Jkay thread? You'd get better response, I assume.

Sent from I9300 - UltimaROM - Boeffla Kernel
[Galaxy S III Android Development] gkhushal:
1.4% per hour I think it's more battery drain

I get .5-.75 % per hour easily