yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] andip71:
No, the app is already further than the kernel.

You can only switch that on with the next beta5 of the kernel. But this is not yet out in the wild (only in the hands of the pre-testing team).

So, patience :)

Good good, was expecting that.

Andi
[Galaxy S III Android Development] NikitoGR:
I know I'm dumb that I didn't read your guide on the website. Please dont hate me, my pc doesnt work, and I use my phone instead. Btw I use the stock charger hahahahahaha :cyclops:

I will give a try to the beta one. Your work is really great. :cool:

(Can I use your sig?)
[Galaxy S III Android Development] szunyi77:
Sorry, my question was solved!
[Galaxy S III Android Development] shorza:
Try this?

- clean your plugs

- replace usb cable at charger

if all does not help: enable the two switches in Boeffla Config to ignore unstable power and safety margins.

Credit to Lord Boeffla
[Galaxy S III Android Development] mad_ady:
I'll try anything once, but it doesn't look like a hardware issue.
[Galaxy S III Android Development] andip71:
Why should I hate you? :) All good.

And the beta will come out today or during the weekend. Let's see.

Yes, you can use my sig.

Andi
[Galaxy S III Android Development] shorza:
My app is saying it expired ever since it ticked over to the 1st of March.

Anyone else?
[Galaxy S III Android Development] andip71:
Everyone probably... new app will be in play store in 2 hours.

Andi
[Galaxy S III Android Development] andip71:
2.2-beta5

Hi all,

I am currently uploading the new beta version for you.

Version 2.2-beta5

28.02.2014

Updated zzmoove governor to version 0.8 RC1

Implemented new governor "intelliactive" (credits to Faux123)

Updated BFQ scheduler to version v7r2

Touch-to-wake charger mode added: If switched on in Boeffla-Config app, touch-to-wake will stay active as long as the phone is connected to a charger or usb port

Initramfs updated to version of 28.02.14

Enjoy

Andi
[Galaxy S III Android Development] XDAMaxe:
Hi Andi,can you say something about changes/modifications of zzmoove 0.8RC1 ?
[Galaxy S III Android Development] szunyi77:
hello

I turned on the status and Touch Touch wake wake mode charger 40 seconds.

If the device or usb charger, it works to the touch.

If not connected, and after I touch upon closing, will not wake up the device.

What could be the problem?

I use AOSB rom 4.4.2 and 2.2 beta 5 boeffla omnirom kernel.
[Galaxy S III Android Development] andip71:
Touch wake (when not on charger) only works if the display goes off by itself.

If you use the power button to switch it off, touchwake is disabled (this is like it was all the time).

Reason is: Sometimes you want to put your device in the pocket etc, so you need to switch the display off and disable touchwake - by using the power button.

Andi
[Galaxy S III Android Development] andip71:
Hi, yes, I could... but as it is still not a final release, I leave it up to [MENTION=3279788]ZaneZam[/MENTION] what he wants to tell and what not.

I mentioned him, so he can kick in and tell you.

Andi
[Galaxy S III Android Development] szunyi77:
I see, thank you very much for your quick response.

A very useful feature is the Touch wake charger charging mode, I really like!

Note:. Former HTC device for me, and there was a possibility that when a key is touched to the lower three, woke up the device.

Here it is not possible to hold down any button to wake the device?
[Galaxy S III Android Development] Tubamannen:
Thanx for adding intelliactive, been using it on my d802 the last week, and now on my i9300... :)

Skickat från min GT-I9300 via Tapatalk
[Galaxy S III Android Development] andip71:
I never looked into that. But it would also require the same battery (wakelocks) and therefore also only be available for some configurable time.

So, touch to wake should be sufficient.

Andi
[Galaxy S III Android Development] ZaneZam:
pfffh it's really a lot of stuff from 0.7 to 0.8 but RC1 it was "just" that:

- code- and comment-style changes part II: massive re-arrange, cleaning and correction

- priorize scaling block over early demand functionality in scaling logic

- usage of 'scaling_block_threshold' value inverted - now it's a real maximum value for load gradient

- added tuneable 'scaling_block_force_down' to be able to adjust and disable forced down scaling

this tuneable is holding a multiplier (example 1: 2 = force down scaling exactly the amount of

scaling block cycles long, example 2: 3 = force down scaling the amount of scaling block cycles * 2)

0 = disable forced down scaling and use only scaling up blocks

- minor optimizations at multiple points in the code

profile header file (Version 0.1):

- cleaned and added comments

- added new settings 'zzmod', and 'zzbatp' (WIP)

- lowered early demand sleep threshold value to 30 in all settings

this is a little bit out of context but for a bit more info: the changes were mainly for the new scaling block feature ;)

RC2 is also ready (with a nice speed feature *g*)

but currently i'm hunting the nasty "hotplug bug" that sometimes appears will see if i can fix it

for the final version, if not then we have to live with it for now :(
[Galaxy S III Android Development] striked0wn:
U can set usb charge up to 600mah safe.. (In boeffla-config).. If it's not working.. It seems your mainboard powers only 475mah at usb-ports..

Sry for the bad english.. :P
[Galaxy S III Android Development] zeli9:
Actually the numbers you quoted are correct and this is normal behavior. But you can install this app:

https://play.google.com/store/apps/details?id=com.abmantis.galaxychargingcurrent.free

and see what's your charging current readings are, if you're on USB 2.0 I don't recommend going over the stock values, you might fry your cable/USB port... if you're getting low or inconsistent numbers (below 1000 mah) from mains power you might want to try another cable/charger - the samsung stock cable is crap as has been noted by many users, I have done a bit of testing as well and can confirm this too.

---------- Post added at 10:25 PM ---------- Previous post was at 10:17 PM ----------

Andi, I'm new to this kernel, just trying it out, have been on temasek's, yank's and googy as well, all nice kernels in their own way of course :)

I have a question: which governor/profile do you currently use/recommend? I'm not sure about pegasusq profiles and zzmoove ones. I'm familiar with zzmoove yank's profile, I assume it's the same config as with temasek kernel?

Thanks for your great work! Already purchased the donation key to support development :)
[Galaxy S III Android Development] ZaneZam:
Oh no not again archi :)
[Galaxy S III Android Development] JustArchi:
Don't get me wrong ZZ, it happened also with normal pegasusq using, so definitely it's not you :laugh:
[Galaxy S III Android Development] nicesoni_ash:
I tried this kernel as suggested by temasek, I am looking for wifi direct possibilities. Is this kernel has working wifi direct? I tried with samsung tab 2 stock rom with superbeam app but it keeps hanging at enabling wifi direct. That's why I wanted to confirm. Thanks.

Btw just to add, I like stweaks integration in this kernel very much. Thanks. I am testing yank555, temasek and yours and all three are amazing. :)

Also if I want to try any other kernel do I need any cleanup script for this kernel or anything else?

_____________

Sent from my GT-I9300 powered by Temasek Rom & Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] andip71:
Hi,

one important correction: There is no stweaks in this kernel. Boeffla-Config looks quite similar maybe, but it is not based on stweaks but written from scratch (I do not like to rely on other code for apps).

No cleanup script needed, just make sure there are no nonsense script in your init.d folder.

But in Boeffla-Config you can even clear init.d with one klick.

Cheers

Andi
[Galaxy S III Android Development] andip71:
By the way...

By the way... forgot to mention before:

I MIGHT have found the CPU not clocking down issue. I investigated and found I forgot an important commit to be included.

Too early to say victory, as I could not replicate the issue so far. But... we will see.

Maybe beta6 will therefore come out today.

Cheers

Andi
[Galaxy S III Android Development] faddys123:
Sometimes my settings in the app keep resetting and I have to keep changing e everything back.
[Galaxy S III Android Development] nicesoni_ash:
Sorry for that, yeah I meant to say Boeffla config app. Used to stweaks too much so. Btw any suggestions about my wifi direct related question?

_____________

Sent from my GT-I9300 powered by Temasek Rom & Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] andip71:
1.0-beta6

Hi guys,

many thanks for your comprehensive feedback in the past days.

This helped me to create a new beta for you (for both CM10.x)

1.0-beta6

Change log

* Fixed CPU frequency stuck issue (hopefully)

* Updated Yank zzmoove profiles

* Android logger on by default (switch off again if you like)

* Insecure kernel (adb has root authoritiy)

Thanks

Andi
[Galaxy S III Android Development] andip71:
Fusion? What is fusion, a rom?

Have no clue, as I cannot test on every rom.

I test usually on CM latest nightly, slim, miui, archi and AOKP.

Hm, what is very long? And what exactly takes long? Time until you see the lock screen? Something else?

Guys, I am really sorry, but if you are not a little bit more precise nobody can help you.

Thanks zeli.

I personally use zzmoove with zzmoove yank battery profile. Currently also testing the new Zen scheduler.

And yes, the two Yank zzmoove profiles are the same ones Yank has in his latest Samsung/CM kernels.

Andi
[Galaxy S III Android Development] rowlers:
b6 cured (so far!) CPU stuck at 1400. Thanks Andi...
[Galaxy S III Android Development] sandeman11:
probably a stupid question. How do i know if i got a samsung based rom or CW-rom? :eek:

Thanks!

Currently on a omega 4.1 rom

just wanted to step out to revolution with dualboot and Siyah Kernel. After a bootloop restored backup but got no connection with phone-provider :crying:
[Galaxy S III Android Development] enigma1981:
Omega is Samsung based :)

Simples

Swyped from my Galaxy S3 using Tapatalk 4
[Galaxy S III Android Development] amppen:
Any particular reason for asking about it in this thread? Omega is a Samsung ROM, unless it's the AOKP Omega.

The telephony fail sounds like corrupted EFS. Hope you've got a backup. EFS backup, that is.
[Galaxy S III Android Development] zeli9:
Great! Many thanks!

Really love this config app that allows to change settings easily and is much more responsive than stweaks, which takes a while to start up...
[Galaxy S III Android Development] Techniques:
Fusion is this ROM.

http://xdaforums.com/showthread.php?t=1855963
[Galaxy S III Android Development] andip71:
I hoped that. I realized quite quickly today, I totally forgot to include a commit that is required when you upstream the kernel to latest Linux version.

Stupid me...

Andi
[Galaxy S III Android Development] sandeman11:
reason? that i read a lot of Omega-users using the Boeffla kernel. I thought the telephonyfail / Mobile Network, has something to do with a wrong kernel?

basically i did whats below, after reversing (after bootloop) the connection is gone...first and last time i am trying a dualboot....:confused:

Procedure to Dual Boot

Step 1

Download Siyah Kernel (make sure you download the S3 version) and any ROM of your choice.

Step 2

Boot to Recovery by pressing and holding Volume Up+Home+Power

Step 3

Select

->install zip from sdcard

->choose zip from sdcard/choose zip from internal sdcard

->siyahkernel.zip (The file we downloaded at step 1) and select yes install.

Now go back and select Reboot Now.

Step 4

galaxy s3 dual boot stweaks

Once you are up, open up the App Drawer and select STweaks and navigate to the DUALBOOT tab and select Reboot into 2ndROM Utils.

Step 5

galaxy s3 dual boot recovery

Now Navigate to dual-boot options and do the following

Format 2ndROM system

Wipe 2ndROM data/cache

Wipe 2ndROM dalvik-cache

Step 6

Now select install zip to 2ndROM from internal/external SD and install the rom as per the normal installation procedure.

Step 7

Once installed, go back and select install zip from sdcard->choose zip from sdcard/external sdcard and select siyah kernel and flash it again.

Once done, select Reboot Now.

Step 8

galaxy s3 dual boot stweaks options

Now you can go into STweaks, select the DUAL BOOT tab and select either Reboot into 1srROM/2ndROM as per your need.

You can also use Reboot into 2ndROM Utils and update/replace the ROMs as per the same procedure.
[Galaxy S III Android Development] amppen:
hmmm...

So if you use Siyah you need to flash Siyah for the 2nd ROM also. And this is the AOSP Boeffla kernel thread, there is also Sammy Boeffla that works with Omega.
[Galaxy S III Android Development] cheese458:
using latest beta 5 :) what kind of governor is intelliactive? Battery? Performance? combination?
[Galaxy S III Android Development] mufaa:
After applying the Boeffla 2.1 on the Mokee 4.4.2 ROM, I have noticed my camera has gone really dark. The viewfinder and the pictures under moderate lighting conditions are extremely dark (before it was quite normal and certainly not as dark). Even pic quality has suffered.

What gives? I hope there is a solution!
[Galaxy S III Android Development] ZaneZam:
what i know: goes in performance direction, scales fast and stays more often on higher frequencies hence might be smoother than other governors

it has hotplug capability but doesn't use it often ;) at least with standard settings so in summary it's less battery friendly than other governors but how much and if that is really true should be checked individually because as allways it depends on phone usage and personal taste ;)
[Galaxy S III Android Development] cheese458:
thanks!
[Galaxy S III Android Development] andip71:
Unlikely this has to do with kernel.

Maybe settings.

But I do not know that rom at all...

Sorry

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] JustArchi:
Fast overview of new governor:

Basically it has two steps - MIN (200 MHz) and MAX (1400/1600, depending on what you configured) :D.

It literally uses minimum in idle and maximum in case of any load. For me it looks the same as performance governor, just with a small addition of idle load.

If you ask me - this is the fastest governor and definitely causes biggest battery drain. No go for me, I'm back to [MENTION=3279788]ZaneZam[/MENTION] :D.
[Galaxy S III Android Development] pricey2009:
To be fair the results I've had with zzmove I am NEVER going to try anything else.. Big up Andi and Zanezam you two are the only reason I still have this phone.. I cannot thank you enough. Legends.
[Galaxy S III Android Development] Choristav:
[MENTION=947981]Lord Boeffla[/MENTION] I still have huge stutter issues and freezes with the latest beta on Temasek's rom with the new beta. I noticed the phone getting hot as well.

Anything after .1 beta kills it.

Anything I can do?
[Galaxy S III Android Development] FlemishDroid:
Beta 5 works great on CM11. :thumbup:

By the way the Dutch translation of the config v2 app contains some big mistakes. For example controlleer -> controleer.

Verstuurd vanaf mijn GT-I9300 met Tapatalk
[Galaxy S III Android Development] mufaa:
Hi!

Generally what settings would that be? I am confused by the result as well.

Edit: Also, I want to try the new 2.2Beta5. Can I simply install it on top of 2.1 or will it require a complete ROM wipe?
[Galaxy S III Android Development] Svartsyn333:
I have a very big problem with your kernel, wether it's the one for Stock Roms or AOSP. If my battery runs completely low and phone turns off, it appeares that every now and then the phone gets stuck in a bootloop. I first did not consider it's related to your kernel as I only used stock based Roms. I tried to reflash Rom, mods, kernel but still bootloop. So I did what I thought it had to be done: format system and flashed new Rom. But now I switched to 4.4 Asylum Rom and the same thing happened to me again. I then only reflashed Rom without wipe, mods, kernel and the phone booted again. I'm really sad this happens because I love your kernel but I can't as long as this problem persists. :(

Sent from my ? using my ?.
[Galaxy S III Android Development] Nic2215:
Just so u know, I too often use until phone power off and I even set ignore battery warning in Temasek, never had bootloop ever in Stock, slimkat or Temasek.
[Galaxy S III Android Development] Svartsyn333:
Weird. Happend to me several times as long as I was on Boeffla Kernel. It's gone since I use kernel that came with the Rom.

Sent from my ? using my ?.
[Galaxy S III Android Development] mad_ady:
I tried your suggestion, and I have new information which might help. If I enable ignore unstable power and safety margins and I reboot, I am able to use the dock once. After I unplug, if I don't reboot, the phone will freeze when I plug it again.

The tests were done on beta5, with ac power set to 1A.

At one point I did manage to plug it in 3 times without a freeze, but I think I turned off the unstable power/safety margins in between. I haven't been able to reproduce it.

When are the settings regarding power applied? On reboot or at runtime? I haven't seen anything related to it in SuperSu's log.
[Galaxy S III Android Development] Yeti47:
Anyone had any issues with the last releases (beta 5 and the config v2 app) where boeffla sound is always turned off? Starts on, then goes off when the config v2 app starts during boot?

I've formated /system, run all the kernel clean zips and reinstalled everything again to no avail. Tried Beta 4 with no impact. Can only assume it is new dated version of config v2 (which I have also reinstalled)? Would have to change the date to use the old version and do not want to screw my syncs...
[Galaxy S III Android Development] andip71:
Yeti... Do you have boeffla sound app installed as well?

Nobody else should be able to switch it off again.

When the kernel loads, boeffla-sound is off by default. Then the kernel switches it to on.

The boeffla config app v2 during startup does not apply any settings at all. It cannot even do that, there is no code in for that.

So can only be another app conflicting...

Run the conflict scanner in Boeffla config settings...

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] Yeti47:
Nope, only boeffla-config v2 installed. Did a conflict search when I reinstalled it.

It's odd as all my other settings are left as defined like voltage and governor, just sound all turned off. Did and update to the today's omni nightly as well, so it could be doing something, though would not expect it. May test a roll back of that anyway, to exclude it.

Thanks for ruling out the config app! Not too important as it only takes seconds to reset again, but the unexpected makes me wonder what is going on.!

Cheers...
[Galaxy S III Android Development] andip71:
I wonder if boeffla sound can be controlled from within Omnirom meanwhile... Need to test that soon..

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] Yeti47:
Forgot to thank you for the quick reply, appreciated! If the rollback works l post.

Expect it will be tomorrow though, as it's my wife's birthday party tonight, and I can only sneak away be debugging for so long without losing bits of body...
[Galaxy S III Android Development] andip71:
Happy birthday to your wife. Enjoy the party.

And... No rush. I am also booked the whole weekend for other stuff.

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] drgreenth:
I would really love f2fs support..

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Android Development] andip71:
Not in my plans for many reasons I stated many times.

I personally feel this is more a hype than real big improvement after reading some statements.

And... No ecosystem around it still, and too far away from stock.

Sorry for now

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] simonwil:
I had the same problem and fixed it by freezing DSP Manager with TB.
[Galaxy S III Android Development] drgreenth:
Well. Ive been using it for about month now and its indeed not just hype. But I understand that you want to keep boeffla kernel as stock as possible. But in this custom rom world we are already quite far from stock so thats why I asked. Everyrhing else is better w/ boeffla kernel.

Lähetetty minun GT-I9300 laitteesta Tapatalkilla
[Galaxy S III Android Development] Yeti47:
Thanks, that worked! Odd how it only started today, will have a look at the changelogs tomorrow.
[Galaxy S III Android Development] karanfire123:
Is it me or does the md5 checksum doesn't match with the kernel?
[Galaxy S III Android Development] Yeti47:
DSP Manager now has boeffla sound control built in, that was overriding the settings. Looks to be a recent addition, so disable is best...
[Galaxy S III Android Development] 2rgman:
Just checked 2.2-beta5 and 2.1-stable, it's match
[Galaxy S III Android Development] Nic2215:
Is there a way to remove kernel logger? Just to save some juice lol. I can disable it via stock rom, currently using teamasek. Is it temasek features?
[Galaxy S III Android Development] metalgearhathaway:
Just moved from my S2 to my S3 today, expect my contributions to decent testings once I familiarize myself with all things i9300 :)
[Galaxy S III Android Development] mad_ady:
I think there is a setting for it in the Boeffla app, Misc tabm at the very end.
[Galaxy S III Android Development] Nic2215:
Ya its Gray out can't unpick. :-\
[Galaxy S III Android Development] Moopow:
Welcome...
[Galaxy S III Android Development] andip71:
There is only in Samsung roms.

If you switch off the kernel logger on CM or Omnirom based kernels, it breaks sound for some weird reason.

That is why I do not allow it on CM and Omnirom kernels.

Andi
[Galaxy S III Android Development] karanfire123:
How are you checking the md5sum? I'm using an app from the play store called md5checker and it doesn't match. Now I'm confused as to flash the kernel or not. ?
[Galaxy S III Android Development] mad_ady:
<offtopic>

This won't bring your car back, but you can probably buy yourself a coffee!

Confirmation number: 4FJ09005XT952741E

Thanks for the support!

Hopefully this will bring you closure: http://www.huffingtonpost.com/2010/07/26/the-funniest-notes-left-f_n_659338.html#slide=118930

</offtopic>
[Galaxy S III Android Development] andip71:
Many thanks, Mad_ady... much appreciated.

Slowly it is turning to the better again. It seems, I can at least get an adequate new car in 3 weeks again. So, time to close this topic very soon I guess.

BTW - did not forget about your inquiry about kernel compilation. I am still a bit busy now, but will come back to you soon on it via PM.

Cheers

Andi
[Galaxy S III Android Development] mad_ady:
Don't worry about it. I'm in no rush. I'm just trying to learn :)
[Galaxy S III Android Development] Kyle07:
So, today at work I listened to music almost the entire day. With the "Intelliactive" governor set. I can report that I did not have a single audio stutter in that time! Even with the minimum CPU frequency set to 200MHz. This is awesome for me because I have always had some stuttering (Even at 300/400MHz minimum CPU frequency on ZZmove, PegasusQ or lulsactiveq).
[Galaxy S III Android Development] andip71:
Great, thanks for sharing this feedback.

But now I am curious about battery consumption compared to the other governors in your case?

Andi
[Galaxy S III Android Development] Kyle07:
Battery is not as good as ZZmove but I don't really mind in this instance. I am now sitting with 27% battery left, 1 hour 30 minutes screen-on time and On-battery time of 10 hours 15 minutes. I will just configure an "Audio Profile" in BC which switches to Intelliactive from ZZmove Optimal.
[Galaxy S III Android Development] ayoubij:
[MENTION=947981]Lord Boeffla[/MENTION]

Do you know which kernel I should install with PAC rom, the Omni or cm kernel ?

thanks.