yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] STAticKY:
Cm10.2-alpha16-v2 working beautifully . all zram devices balancing nicely.

Great work man. Keep it up.

On small request, could you make the number of zram devices configurable as well as a configurable swappiness. I'm thinking that 2 devices may be the sweet spot for CPU cycles/performance if it infact uses one thread (core) per block device. Leaving the other 2 core asleep but still having multi threaded zram. Hope its not to much of an ask. Thanks

TP.
[Galaxy S III Android Development] Kyle07:
It's awesome having the screen controls again! Thanks for the addition, Andi.

It appears that the Mode is not correctly applied until one toggles the the sharpness tweak. Not an issue as such if you are aware of it.
[Galaxy S III Android Development] STAticKY:
Hi Andi,

Would you consider adding a toggle to change how zram size is applied. Toggle on would be spread the size over the amount of configured devices and toggle off would be apply chosen size to each device. Do you follow?

You could call it zram spread toggle or something along those lines...

Or you could simply increase the max allowed size for zram...

Saves me messing with scrips all the time

Thanks

TP.
[Galaxy S III Android Development] andip71:
Well, some use negative mode to save battery when they are using apps with white background. So they can put negative mode on and have white font on black background.

That is why I will keep both toggles in for now. Once you know the outdoor mode toggle behaves weird, it is manageable I guess :)

This is interesting. I just tested on CM10.2 nightly and can confirm, the mode is not getting active. But for me it also does not help to toggle the sharpness tweak.

The only way for me to make it work is to set the szene from Standard to e.g. UI. Then everything works fine. I guess I will add a toast message for that, to let users know.

But to go sure: Which firmware/rom are you exactly on? So I can try your way of toggling the sharpness fix?

It seems the whole MDNIE implementation in CM is not 100% perfect. On Samsung Roms, the mode does apply without any issues or workarounds.

Honestly - no. The zRam implementation is already complex enough in the app.

And it is, in the end, only some simple math, right?

If you want 150 MB per device on 4 devices, you just set the slider for total size to 4*150 = 600 MB. Done.

I trust you are without issues able to do that?

Sorry :)

Andi
[Galaxy S III Android Development] agam1308:
Andi, is there any way to set touch to wake delay on one second?

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Android Development] andip71:
only if you use a init.d script for it. not officially, it is only going in 5 second steps.

I could easily change that, but not sure whether this makes so much sense, having 1 instead of 5 secs.

Andi
[Galaxy S III Android Development] Kyle07:
I can't seem to reproduce the issue consistently. Now, if I toggle the mode it works perfectly. It has something to do with messing with the outdoor mode I think. But as you say, the CM implementation is a bit wonky. My setup is as per my sig.
[Galaxy S III Android Development] GTMoraes:
Hey boeffla, good to see that you're now working to make CM kernels. Loved your samsung ones.

Can I suggest some improvements? I've heard that this kernel in particular is pretty fast and efficient, and you could implement some of the features (heard some good things about the touchboost mod) on your kernel. There's the kernel source on the bottom of the first post.

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

Unfortunately, it's made for the US S3 (dual core, different audio chip, etc etc), so idk if it will be this straightforward.

Great job, and keep it up! =)
[Galaxy S III Android Development] mrbojangle69:
I do not know if it has been questioned before but I would like to know if the UMS Mode shown in the Overview tab on the Boeffla Config forces the device to be connected as an USB Mass Storage unit. I am using the latest CM 10.1.3 Stable rom on a Samsung Galaxy S3.

Please answer Lord Boeffla, I'd like to go back to the days of Mass Storage connection, I hate MTP (so slow and dissapointing). Thank you in advance Master!
[Galaxy S III Android Development] andip71:
Yes it does. But only for external SD storage (internal is not possible).

All in the updated documentation as well.

Andi
[Galaxy S III Android Development] mrbojangle69:
I assume that If I want to access the internal storage I have to untick that UMS Mode box.

Thank you again Lord and keep up the great work you do, it's an amazing kernel!!!
[Galaxy S III Android Development] andip71:
yes!
[Galaxy S III Android Development] MBurns2:
Finally i tested your kernel on cm too.. No words.. Perfect!! Thanks master Andi!!

Inviato dal mio GT-I9300 con Tapatalk 4
[Galaxy S III Android Development] andip71:
Definitely not yet perfect, MBurns2.

But we are getting there, together, step by step... :)
[Galaxy S III Android Development] MBurns2:
mate i'm really impressed about yours "pegasusq battery saving"..why lot of developers don't use pegasusq governor ? i find lot of zzmove custom profile (which is good) but nothing about pegasusq..thanks
[Galaxy S III Android Development] andip71:
1.0-beta5

Hi all,

before weekend starts, one more beta for you (both CM variants), just minor changes though :)

1.0-beta5

Change log

Added Zen scheduler

Upstream to 3.0.97 Linux kernel from 27.09.13

Major cleanup

Available as always: Load&Flash or grab it from the homepage.

Cheers

Andi
[Galaxy S III Android Development] enigma1981:
When I flash this kernel over Temasek cm10.2 I get random issues like keyboard crashing, occasionally difficult to wake etc... is this a conflict with the Temasek kernel I was using previously? Should I run a clean up script or similar before flashing youth kernel? Or is it just coincidence?

I have no oc/uv by the way

Swyped from my Galaxy S3 using Tapatalk 4
[Galaxy S III Android Development] zenosteam:
Hi andi perhaps it asked before but I want to know you point of you about UV effect in battery life

Envoyé depuis mon GT-I9300 en utilisant Tapatalk 4
[Galaxy S III Android Development] andip71:
I really do not know what Temasek did special, if at all. But I think something else is wrong. I know many users using boeffla kernel on CM10.2 of Temasek without issues.

At least version 1.0-beta3 and beta4... so you could try these ones as a test.

But I doubt, I am on nightly CM10.2 of today and all seems to be fine.

Also make sure, there are no strange script in init.d folder, just to go sure.

It is minimal, almost not noticable. The only positive effect of undervolting can be lower temperature of your device.

But generally I am not a friend of undervolting anymore, too much risk of instability, no less positive gains.
[Galaxy S III Android Development] andip71:
To save your current bootanimation, just copy the file bootanimation.zip from either your /data/local or /system/media directory.

Then you can always put it back again.

However, only real good and safe solution: Do a Nandroid backup before you try it.

Andi
[Galaxy S III Android Development] dhirend_6d:
Tested it by changin a few settings too. And all seems to be working absolutely fine now. Well for me the only problem was the Governor I/O tab. All other tabs worked perfectly with the app. I changed the Governors and checked too. And it seems that the settings stick now and do not reset.

Thank you again. :) :)
[Galaxy S III Android Development] Kord:
[MENTION=947981]Lord Boeffla[/MENTION]

Thanks! I'm on CM11 (Official) now and seems that sound is fine :)

Also, I'm checked previous bug with SharpnessTweak and problem still exists, even on KitKat.

Regards :good:
[Galaxy S III Android Development] andip71:
Hope you will go to a rom with Omnirom basis soon, because there I implemented a completely different and new version of the sharpness tweak.

Cm11 implementation I will check in the next days anyways...

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] SharpBang:
[MENTION=947981]Lord Boeffla[/MENTION],

I would like to know if your drivers uses the latest mali r3p2 drivers and if there's some way to see if they're really being in use... That's because I don't see that difference at all.

Thank you
[Galaxy S III Android Development] exscape:
Hi!

Is there anything I need to know about how to compile? I'm having the same issue with temasek's kernel as I do with yours (those are the two I've tested so far).

I'm on temasek's CM11 compile from 20140113, and it works as it should with the stock kernel. However, I want to patch one tiny thing and so I need to compile it myself.

I'm on the currently latest commit of the boeffla11.0 branch, 4171bd5f4040edfd2cfc5b201078764a53d9b9b5 (commit message: "release tag 2.1-beta10"). On top of that, I've changed CROSS_COMPILE to arm-eabi-linaro-4.7.3, added -Wno-error to CFLAGS_MODULE and CFLAGS_KERNEL (some VMware hypervisor module or such failed to build) and patched out a double-defined variable that halted the compile.

The problem is that I don't get Wi-Fi when using this custom kernel. It works fine with temasek's kernel build, but not when I build from his sources. It's disabled when I boot, and if I flick it to "On", it just stays there but nothing happens. The text that it's not enabled stays on screen, and the on/off switch is stuck at On until the next reboot.

Apart from the patches above, what I then do is

make clean

make ARCH=arm m0_00_defconfig

make ARCH=arm

abootimg -u /tmp/boot.img -k arch/arm/boot/zImage

where /tmp/boot.img is temasek's stock image. So I simply replace the zImage and nothing else; is this a problem?
[Galaxy S III Android Development] Moster2:
Every kitkat rom has those and also all kernels for 4.4 roms have them.
[Galaxy S III Android Development] Kord:
Hmmm, maybe Temasek or ArchiDroid? I don't know, because Omni is still missing some features that I like and on Temasek I have a bug with Read only file system.

Anyway, thanks a lot!

Regards :good:
[Galaxy S III Android Development] dhirend_6d:
You can try SlimKat too its pretty neat.
[Galaxy S III Android Development] sqlpro:
Hi [MENTION=220904]andi[/MENTION],quick question

Am currently running neat ROM with omni beta9a and got a notification this morning about beta 10 update which I clicked yes to install but it downloaded cm version and installed it! Is that normal?

---------- Post added at 03:58 PM ---------- Previous post was at 03:44 PM ----------

Interesting I use exact same app and never noticed the issue. May be I should pay close attention. This app quite useful especially if you have small children.

---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------

I just tried again and yes can replicate issue. This makes sense why some times I get random issues.
[Galaxy S III Android Development] Moster2:
Yes, he already said that. The app only knows stock and cyanogenmod(aosp). So it will download the cm version.
[Galaxy S III Android Development] andip71:
No need to look somewhere. If your kitkat rom boots up, it uses the r3p2 drivers.

Otherwise it would get stuck with a blank screen.

I do not provide any kernels anymore (apart from Samsung 4.1.x kernels) with older drivers.

I think you miss a fundamental piece:

WIFI is compiled as a module in the kernel, it is the dhd.ko module which needs to exist in /system/lib/modules.

If you do not copy this module over during the packaging process of the kernel, it will not work (same goes for other modules btw).

Did you do that?

I also can recommend Slimkat. It is really veeeeeeeery lean and therefore fast.

However if you are looking more for a fully featured rom, you can use Archi or Fusion.

No, this is not normal and I just tried it and it installed the Omni kernel fine for me.

I think, you might be confused by some information of the config app.

If you see something like [i9300/cm/cm11], this does NOT show you it is a CM or Omnirom kernel.

This shows you just that the kernel is based on the basis of CM code.

The only way to see it is the Omnirom or CM11 kernel is by looking at the kernel information!

Look at the screenshot, this is an Omnirom kernel. Do not look at the info in the circle, but the one in the rectangle.

However, I appreciate while the info in the circle was for kernel internal purposes only, it might be confusing. So I will change it very soon to become more clear.

Hope that helps

Andi
[Galaxy S III Android Development] andip71:
Please see my last post. It DOES download the correct kernel, it is just a cosmetical issue which apparently confuses users.

Andi
[Galaxy S III Android Development] andip71:
And me again: I changed the handling already.

If you do a load&flash in the app now, to reinstall beta10 - or you download beta10 again manually and flash, you will see already

[i9300/cm/omni11]

in the config app.

So, the device is i9300, the platform is cm based, and the "flavour" is omnirom11 kernel.

Hope it is more clear now.

Andi
[Galaxy S III Android Development] andip71:
... and on top I just pushed app version 2.1.8 to play store.

It will fix the incompatibility with "smart app protector" app.

Andi
[Galaxy S III Android Development] sqlpro:
Thanks for the info . BTW the file i downloaded from website has omnirom in the file name but the file downloaded by app has only cm word. That's what confused me and thus the question.
[Galaxy S III Android Development] exscape:
Indeed, that was the problem. I figured it could be a module earlier, but then thought that the old module should work since I compiled from the same sources. I guess not! I copied them over and got it to work... a little.

I still can't connect to my main network, which is secured with WPA2. I did manage go get online on an unsecured one, however.

On my WPA2 network, I get

I/wpa_supplicant( 2834): wlan0: CTRL-EVENT-SSID-REENABLED id=2 ssid="xxxx"

I/wpa_supplicant( 2834): wlan0: Trying to associate with 00:17:f2:xx:xx:xx (SSID='xxxx' freq=2472 MHz)

I/wpa_supplicant( 2834): wlan0: CTRL-EVENT-ASSOC-REJECT bssid=00:17:f2:xx:xx:xx status_code=1

I/wpa_supplicant( 2834): wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=2 ssid="xxxx" auth_failures=2 duration=20

I most certainly have the correct password, which hasn't changed since I changed kernels. Re-entering the password also doesn't help.

Any idea what this might be? The modules built were btlock, commkm, dhd, frandom, mvpkm, pvpcpkm and scsi_wait_scan; I copied those over.

EDIT: Never mind, this seems to be fixed now. Not sure if it had something to do with the AP or if trying again later helped, but I didn't change anything anywhere to get it to work. Thanks for the help re: the modules. :)
[Galaxy S III Android Development] andip71:
Well, now everything seems to be allright. I also do only copy all modules to /system/lib/modules during the kernel flash (in the installer zip).

Well, no... no clue why you cannot connect now.

Andi
[Galaxy S III Android Development] lchiocca:
Hi Andi,

I looked at the source code for my "touchkey led issue". Looking at the "cypress-touchkey.c" it looks at though it's not been kept in sync with omnirom/cm. I looked at yank555's original version, but it is based off something really different. Since omnirom allows you to override all the values, why even bother with the softkey leds at all?

Loris
[Galaxy S III Android Development] andip71:
Basically, I implemented this already many months before Omnirom did it.

So I kept it in and did not bother with the Omnirom commit at all.

I can only switch over to the Omnirom commit if it does not break my config app.

Maybe I will look into that one day (after my next holidays).

What was your issue exactly? Sorry, cannot remember anymore.

Andi
[Galaxy S III Android Development] lchiocca:
I wanted to disable the softkey led backlight altogether. But no combination of rom/kernel + omnirom/cm settings allowed me to disable them.

Cheers

Loris
[Galaxy S III Android Development] andip71:
Aha, and which Rom are you using?

I am on Omnirom latest nightly + latest version of my kernel.

When I switch touch led control in boeffla config to "rom controlled", then the LED stays off for me.

Note, you have to lock your screen with the HW button once before everything takes proper effect !!!

Andi
[Galaxy S III Android Development] lchiocca:
I'm also on the latest omnirom nightly + latest boeffla kernel. Here my setup:

* "Touch LED controlled by kernel" to off

* "Touch LED when touch screen" to off

* omni advanced settings -> screen -> touchkeys -> backlight -> off

* use power button to turn off screen (screen goes blank ;))

* use power button to turn on screen (screen comes back - yeah :))

* swipe pattern unlock

* now I'm back in the advanced settings. If I press the menu key, it lights up :(
[Galaxy S III Android Development] andip71:
Deleted
[Galaxy S III Android Development] andip71:
I don't know.

I do exactly the same, and for me the LED stays off.

Also, the LED stays off for me when I set:

- boeffla-config v2 to kernel controlled = on

- in advanced settings, disable touch led

Also it is staying off then. For me.

Maybe you have a 3rd party app installed that can cause the effect.

Andi
[Galaxy S III Android Development] lchiocca:
Hi Andi,

Ahh... I switch to omni a couple of days ago _after_ I originally reported the issue on cyanogen! That exact config works on omni but not on cm. But, honestly, now that I've got a setup that works, I'm happy! :)

Thanks again! You're really a great guy!

Loris
[Galaxy S III Android Development] andip71:
Thanks Loris!

I even consider longer-term to completely dump the CM11 kernel.

Today I installed the Omnirom kernel as a test on CM11 and it seems to work fine too. But for the time being, I continue to maintain the two kernel types still.

Cheers

Andi
[Galaxy S III Android Development] Moster2:
Are you sure that the vibration settings work? Im not 100% sure, but I remember that those advanced settings were changed in cm and omni kept the old cm style. That's also the reason temasek recommends an omni kernel.
[Galaxy S III Android Development] andip71:
I am 100% sure, as I built a patch into the kernel to also support the older CM style of configuring it :D

https://github.com/andip71/boeffla-kernel-omnirom-s3/commit/69327432d7f1fa77693af40c3b2fc42dcdffbe3f

Andi
[Galaxy S III Android Development] shoalinagent:
Not sure if this is common knowledge and I apologise if it is but I have noticed substantial interface lag on b10 when using smartassv2 and min CPU state any less than 400mhz. I keep everything default as always aside from oc to 1600.

Other than that, everything seems sweet on this build, battery life is great and things are notably smoother. I might download b10 and flash again just to be sure I don't have a corrupted file.

i9300 | temasek 4.4.2 | boeffla kernel
[Galaxy S III Android Development] andip71:
shoalinagent, well... SmartassV2 was included on request of a few users only.

It is definitely NOT my recommended governor as it was never extended to support multiple cores properly.

Maybe I should take it out again, hm. But some people like it still...

Andi
[Galaxy S III Android Development] shoalinagent:
Thanks for your input on this, I had a feeling something wasn't right with it. I will revert to zzmove battery yank :)

i9300 | temasek 4.4.2 | boeffla kernel
[Galaxy S III Android Development] JustArchi:
Hey Andi.

What exactly did you change in terms of larger entropy levels?

I'm wondering if there is a point, because there's no issue with standard 4096 entropy pool, the issue is with regenerating it.

I merged CrossBreeder into my ROM, including haveged support:

https://github.com/JustArchi/ArchiD...auto/system/etc/init.d/99ArchiDroid_Init#L164

I balanced regenerating entropy with being gentle on battery, so it will always stay at 3072+ with maximum of 4096.

Also are you using frandom for /dev/urandom and /dev/random? In my implementation I got better results with using non-blocking erandom, which you can also read from my Init.

Cheers.
[Galaxy S III Android Development] dhirend_6d:
Great scott man. :eek: :eek: . Not like that. Kernel wakelocks are the stuff Boeffla would require. App wakelocks you can reduce by using Greenify/freezing apps you don t require in Titanium.

As an example consider this. Using BBS, download here. Logs of the various wakelocks and screenshots of the kernel wakelocks screen. Attached below.

Boeffla can only look into the kernel wakelocks (Also, one cannot completely remove those, nothing is perfect. No matter what anyone does, there are bound to be wakelocks). The app wakelocks well mostly you need to live with those.

Also keep in mind, always wait for 2 3 charge/discharge cycles before you report for battery drain subsequent to either flashing ROM/kernel.

Hope this helps. Cheers.
[Galaxy S III Android Development] alexferdean:
I noticed this too, but it's not related to cm or custom kernels cause it's the same on stock. I checked this in a pitch black room vs a Galaxy s1 phone, and the s1 it's completely black. Then I checked with an s2 and it's in the middle between s1 and s3. I don't get it, shouldn't it be black as in turned off leds?

Sent from my S3
[Galaxy S III Android Development] lchiocca:
Exactly my point. That's why I was asking. I also own a S1 and there it is really black. So I thought that it might be kernel related. It could be an mDNIe thing or something similar.
[Galaxy S III Android Development] Choristav:
Newest beta fixed any UMS issues I had as described.

Thank you [MENTION=947981]Lord Boeffla[/MENTION]
[Galaxy S III Android Development] angelshie:
...guys which kernel i have to download for slimbean 4.3 rom :what:
[Galaxy S III Android Development] andip71:
CM10.2 Boeffla-Kernel in version 2.1

http://boeffla.df-kunde.de/sgs3/boeffla-kernel-cm/cm10.2_download/Series 2.x/2.1/

Andi
[Galaxy S III Android Development] lchiocca:
Have fun Andi!

Looking forward to see JustArchi's changes to omnirom: Boeffla sound control (https://gerrit.omnirom.org/#/c/3428/) :)
[Galaxy S III Android Development] nguoikhongten03:
Hi all. Can you please share with us your profile in Boeffla config?

i'm use temasek cm11.

Thank
[Galaxy S III Android Development] exscape:
Hmm, I got a random reboot yesterday, on ArchiDroid 2.3.3 STABLE.

Kernel is shown as

3.0.101-CM Boeffla-Kernel-Omnirom-2.1-beta8-20131229@andip71 #1 Sun Dec 29 11:51:20 CET 2013

I'll probably try my 2.1-beta10 compile starting later today.

/proc/last_kmsg: http://pastebin.com/MGTdahQx

The interesting stuff starts at line 603.

<1>[ 3663.704144] c0 Unable to handle kernel NULL pointer dereference at virtual address 00000000

<1>[ 3663.711055] c0 pgd = c0004000

<1>[ 3663.714005] c0 [00000000] *pgd=00000000

<0>[ 3663.717827] c0 Internal error: Oops: 17 [#1] PREEMPT SMP

<4>[ 3663.723120] c0 Modules linked in: dhd frandom exfat_fs exfat_core [last unloaded: dhd](bf1003ec)

<4>[ 3663.731888] c0 CPU: 0 Not tainted (3.0.101-CM #1)

<4>[ 3663.736930] c0 PC is at __wake_up_common+0x28/0x98

<4>[ 3663.741696] c0 LR is at __wake_up+0x40/0x54

After that, there's a *ton* of

<3>[ 3664.430250] c0 BUG: scheduling while atomic: s3c-fb/721/0x00000003

repeating over and over. I'm guessing interrupts were enabled but shouldn't have been, at that point?
[Galaxy S III Android Development] andip71:
Hi,

hmmmm, cannot interpret anything useful out of that snippet.

However, beta8 is quite old, it is from end of last year. And taking into consideration how swift the development is going on, I would strongly recommend you step up to latest beta10 where I used (of course) an up-to-date initramfs for todays roms.

Just as a hint...

Andi
[Galaxy S III Android Development] andip71:
Hi Archi,

sorry for late answer. I cherry-picked this, honestly.

This is the commit, it is very straight forward :)

https://github.com/andip71/boeffla-kernel-cm-s3/commit/1739aa3942eb56cfb7d219af4e92404fbe9361f5

Andi
[Galaxy S III Android Development] sherlock5545:
Hi Andi, I tried crating a tasker profile using the guide on your website, however each time a try to trigger the profile, Boeffla Config crashes.

Sent from my GT-I9300