yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] andip71:
Ah, ok. This is good to know. Yeah, there are some apps that require the android logging. Just did not know this is one of them.

Indeed, took be around a month on and off. But I was not happy with the Voodoo sound implementation anymore after I took a quick look at the code. And I decided not to wait until SC will release a new version for the S3 one day, or never, who knows.

Sure we can still continue working on it, not at all the question. Let me know what else you have in mind, as so far my personal wishes are all contained already. But happy to put additional stuff in when possible.

Andi
[Galaxy S III Android Development] AndreiLux:
Yes, the state of the current implementation is a big mess and mountain of dead code, but it works.

And for what's missing, not much really, just needs to be feature equivalent, so that means the speaker tuning, and oversampling controls from what I can see. I'll have reread your code, but you made it very easy to add functionality so I don't think we'll have any problems.

You should get applauded for the work as is very well done.
[Galaxy S III Android Development] abhibnl:
no probs bro, but there's no 3g network available where i live, only 2g. and what about fast dormancy? should i enable it or disable it?
[Galaxy S III Android Development] andip71:
I cannot tell, this depends on your mobile provider. Best is to ask them or to know someone in the same network...

Andi
[Galaxy S III Android Development] sherlock5545:
Or try to look it up on the Web. Search something like [Your Carrier Name] + [Fast Dormancy] on google. You might find someone who already posted something about it.

Sent from I9300 - UltimaROM
[Galaxy S III Android Development] Pard0ned:
AFAIK, 3UK support fast dormancy. Just in case anyone is wondering. :)
[Galaxy S III Android Development] MIKEMON:
I'm using, fast dormancy, and it comes from dev.Goghan me on this super kernel
[Galaxy S III Android Development] gsw5700:
3UK do support fast dormancy I asked them

Sent via TCP/IP
[Galaxy S III Android Development] MIKEMON:
Module, CIFS, apparently functional
[Galaxy S III Android Development] maatsby:
I don't think the launcher redraw issue is relevant to the kernel. There are many reasons why you would get a redraw and many ways to help prevent it, mostly involving keeping it in memory. e.g. the V6 supercharger script.

And I'm pretty sure most custom launchers have an option in their settings to keep the launcher in memory.

Personally I'm using the Jkay framework and I've "whitelisted" the launcher which keeps it in memory. No redraws since doing that.
[Galaxy S III Android Development] bihslk:
First i will thanks developer for a good kernel. No issues yet. I will ask wich governor and IO i should use? Thanks
[Galaxy S III Android Development] xw0lf:
three questions:

1) if i use governor (pegasus - default) with your tweaks from config panel... it's ok or not?.. i not sure if your tweaks work together with governors or override 'em?

2) are your kernel build optimised by linaro libs (to gain speed) or not?

3) are you interested to look/hack hdmi/mhl support in samsung kernel... looks like default action is auto/handshake and this is not good when you have big 1080i/p TV with hdmi-in.. picture is rescaled to 1920x1080@30/24fps and this is async with original 1280x720@60fps samsung galaxy s3 resolution mode... it's not big problem for photos/videos presentation, but to play games is bad deal :( :( .. so, can u force in kernel to use 1280x720@60fps as hdmi out through mhl, on all hdmi devices conected?

some other kernel developers for htc devices find way to do this, but samsung galaxy s3 is not htc one (s/x) :) here is more info, please read whole topic: http://xdaforums.com/showthread.php?t=1799157
[Galaxy S III Android Development] GoGoris:
Plans for 4.2/4.3?

Hi, do you guys have plans to make a kernel version for android 4.2 or 4.3?

---------- Post added at 06:11 PM ---------- Previous post was at 06:04 PM ----------

I use ZZMoove Optimized (I don't notice slowdowns and battery life is great), but a lot of guys here prefer use pegasusq like samsung, which is good to.

As IO sheduler I use deadline, but this seems to be very rare. Most people on this forum seem to use RoW, SIO is good too. I think everything except CFQ/BFQ is considered good on this phone.
[Galaxy S III Android Development] bihslk:
thanks mate
[Galaxy S III Android Development] MIKEMON:
Yes, now being tested zzmoove optimize the scheduler,, SIO, and it seems also very stable.

Find out problems and give a message to Andi
[Galaxy S III Android Development] gkhushal:
most stable version after v2.11..???

Any suggestions guys
[Galaxy S III Android Development] MIKEMON:
Yes, version 2.12 beta2 is absolutely super and without problems.
[Galaxy S III Android Development] gkhushal:
Beta2 or beta2a..??
[Galaxy S III Android Development] MIKEMON:
It does not matter if you are using,, CIFS, beta2 otherwise the same.
[Galaxy S III Android Development] gsw5700:
2.12b2 and phone is flying again, (faster than the eye can see) I like it :)

Sent via TCP/IP
[Galaxy S III Android Development] MIKEMON:
Yes, absolutely super and stable for all if it will complete its use.

---------- Post added at 09:04 PM ---------- Previous post was at 08:47 PM ----------

Otherwise, really, if you set a custom profile by using the phone's super
[Galaxy S III Android Development] GoGoris:
I am also using v12b2a since 2 days. It is very fast and relatively stable. The only problem I had are accidental freezes when changing the cpu governor within the boeffla tweaks app.
[Galaxy S III Android Development] bl4ckdr4gon:
I have experienced this too, although I couldn't raeally tell if it's something to do with the kernel since I have Facebook, tTorrent Pro and a game open that time.
[Galaxy S III Android Development] lkirra:
With all the positive feedback, 2.12beta2a should consider as stable.

Next step i think will come my favorite part since the 2.11betas series. :)
[Galaxy S III Android Development] lou2s:
I just experienced the freeze from changing the governor mentioned above too!

No other apps were opened at the time, I launched boeffla tweak app, change the governor from two cores to boeffla moderate successfully, then I scroll down further to check other settings. The phone suddenly froze completely as I was scrolling down to equalizer. I needed to long press power button to power down ans restart the phone. Cheers!

Sent from my Boeffla I9300
[Galaxy S III Android Development] lkirra:
Might that freeze be a hardware problem?

No problem with my i9300 with 2.12beta2a..

Are you guys experiencing freeze using a custom rom?

Or using recovery twrp?

My guest don't flash the zip with twrp, use the md5 instead and flash it by odin or mobile odin.

I have errors in the past flashing and re-odexing though twrp so i switch to cwm.

Love the nandroid backup of twrp though..
[Galaxy S III Android Development] migz012788:
Me too also experienced freezing of phone when changing cpu governor. And when opening chrome. Experienced 3 times.

Im not using twrp. Im using philz touch recovery. I am a flash addict. And this only happens when ive change kernel to 2.12 b2. But other than that this kernel really works fine :)
[Galaxy S III Android Development] lou2s:
Re: [KERNEL] [Samsung JB] Boeffla-Kernel 2.11 (21-05-2013)

I only use the boeffla app to flash lately.

Ans before that I only use m.d.5 and flashed with mobile odin.

Sent from my Boeffla I9300
[Galaxy S III Android Development] lkirra:
Well, maybe there are still bugs in some devices for 2.12beta2a, mine is working fine though..
[Galaxy S III Android Development] migz012788:
Well it does not happen anytime. When you only change governor once and you were lucky it will not freeze. However what happend on me is I am testing governors. I change it time to time and yeah. It freezes. Right now ive flashed a new rom and flashed this kernel. Changed governor once and yeah everything works well. Ot does happen when you change cpu governor several times :)
[Galaxy S III Android Development] andip71:
Just quickly: yes changing the governor away from zzmoove to something else can lead to freezes in sporadic cases.

Known for quite a long time and I think ZaneZam worked to improve this in zzmoove 0.5 version.

But apart from that... Governor is also not meant to be changed all the time. So it had never the highest priority to improve here.

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] andip71:
Which is? :D

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

TP.
[Galaxy S III Android Development] andip71:
Hehe, I knew that.

Soon....!

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] Pretzel Kleo:
I need Boeffla...! Why Samsung doesn't drop the Kernel Sources yet :rolleyes:
[Galaxy S III Android Development] STAticKY:
Because they haven't officially released 4.2.2 yet. That comes before the sources

TP.
[Galaxy S III Android Development] DonHuan:
Can't wait for Zram to be back! :fingers-crossed:
[Galaxy S III Android Development] SignetSphere:
Cause the ROM you're using is a leaked ROM. No sources will be released on a leaked ROM and June is just around the corner so the official one will be released, same goes for it's kernel sources.
[Galaxy S III Android Development] MIKEMON:
I use only official fw.

I do not ever leaked 4.2.2 version, then the kernel can not work well
[Galaxy S III Android Development] MIKEMON:
I do not know why, but I Zzmoove consumes more battery than the pegasusq, profile / battery-friendly / but I really do not know
[Galaxy S III Android Development] Madlisboa:
Inst Zzmoove = Performance?

Pegasusq= Battery?

Btw i will test boeffla since some friends told me very well about the kernel :p
[Galaxy S III Android Development] MIKEMON:
Yes, it is absolutely the best kernel, but really for me the best profile / pegasusq-battery.friendly / is stable and super battery life, performance slightly less, but enough for normal operation
[Galaxy S III Android Development] Pard0ned:
I've been trying out the other schedulers, and pretty much all have showed stuttering and lag when playing music through power amp with the screen off. Pity since this is one of the main things I use my phone for.

Pegasusq works fine though.
[Galaxy S III Android Development] MIKEMON:
Yes, use profile / battery-friendly / and super at my best for stability and battery life.
[Galaxy S III Android Development] DocMarc73:
I listen to music a lot as well, using Google music player. Not a single issue with it, of course with screen off. No stuttering or else. Zzmove opt governor
[Galaxy S III Android Development] Hbohd:
Just a little idea from me: would it be hard to implement settings in boeffla app to change max screen-off freq for zzmoove? Like any other settings? In my opinion it may help some people with their problems. Furthermore, it may save some battery for people that don't need higher screen-off freq that for example 300-400mhz.
[Galaxy S III Android Development] Pard0ned:
Is power amp too memory hungry then? I've whitelisted it with jkay's framework, still happens.

Will give zzmove optimised a second go, I think.
[Galaxy S III Android Development] andip71:
This is a planned feature of zzmoove 0.5.

Andi
[Galaxy S III Android Development] ginzo:
Everything smooth with power and battery friendly profiles :thumbup::thumbup:

I've modified some config now but I see that is really stable :)

!Live! from my Galaxy S3

Rom: Maya v4 XXEMD2 ♥

Kernel: Boeffla 2.12 beta2

Modem: Buelk1

Operator: Vodafone

Recovery: Philz Touch
[Galaxy S III Android Development] andip71:
2.12-beta3

Good evening,

after a great football celebration last night (where my club won the European Champions league :good:), I am back now with a new maintenance update:

2.12-beta3

Change Log (vs last stable 2.11)

All functionalities of last stable kernel 2.11

Linux kernel "upstreamed" from Samsung original version 3.0.31 to latest release 3.0.80 from 25.05.2013 (www.kernel.org)

Additional charging rates for USB and AC charger

Preparation work to include zRam in next beta4 again

As always - download from homepage or via Load&Flash.

Cheers

Andi
[Galaxy S III Android Development] DonHuan:
Cool! I'm on it. :good:

And congatulations with the victory! :highfive:
[Galaxy S III Android Development] MIKEMON:
I also thank my friend and congratulations on your victory, but this kernel in particular.
[Galaxy S III Android Development] Pretzel Kleo:
I know all of that... You didn't understand what I mean lol.
[Galaxy S III Android Development] ZaneZam:
exactly andi and that's the main reason why the new 0.5 version is not ready yet! ;) main coding is done, features are working so far but i promised "somewhere" (and to myself *g*) that i will look into this annoying freezing problem *g* which by the way has unfortunately increased in this new version because of some perfomance related changes i made! sooo i even didn't consider to release such a unstable thing

as i always want it as stable as possible! fixing these freezes isn't that easy, i found the problem soon but i had to do little bit of research, debugging and much testing. and for now i can say: u can definitely not harm your device by doing a forced reboot by pressing the power button for 15 seconds *g* that is for sure as i had to do this a million of times during fail-testing and my device is still running fine! :)

oh ah aaand i forgot to mention, i think i fixed that freaking freezes! :) (say that faster - tongue twister *g*)

this all applies of course only to zzmoove governor when u switch from it to some other governor.

if there are freezes when u for example switch pegasusq profiles then we have again talk about

what we already taked about andi. :)

so long

ZZ
[Galaxy S III Android Development] donleong:
This kernel is really really awesome

thanks AndiP for the hardworks

this kernel works great in custom rom and cant wait for the new stable version

will introduce to my friends...

thanks a lot :)
[Galaxy S III Android Development] maatsby:
Strange issue (that's not very important) with the latest beta 2.12b3 - when you press the power button to turn off the screen it does this fade to black thing instead of flicking straight off. Definitely wasn't there with beta 2. And I think the last time I noticed it was 2.11b7 if I am remembering correctly.

Not a huge issue, just something interesting that I've noticed
[Galaxy S III Android Development] andip71:
maatsby... this is really strange because how the screen goes off is purely a rom function, the kernel can only support by disabling the earlysuspend (which boeffla does for a very long time already).

So in short, absolutely zero has changed between beta2 and beta3. Also I did not see anything in the kernel upstream from 3.0.79 to 3.0.80 on that.

But still, very interesting somehow.

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

sorry for late answer, but was really busy during last weekend (mainly due to football, hehe).

1) It is ok. Tweaks and settings for governors are cleanly separated in my kernel. To make people not need to worry about it :)

2) No, I dropped Linaro for the time being as Google 4.7 stock toolchain (which I use now instead) has been reported to give smoother experience. But Linaro is 4.7, Google as well, so there should not be rocket science differences between them.

3) Funny, somehow this request comes to me from many sides nowadays. And I can confirm I am currently looking into it and managed to hack the frequency already to stick to 60Hz. However, the picture is completely useless after that, so I need to find more areas that require changes. This is time consuming and I do not have that much time these days. So all I can say is: Yes, I am currently looking into it, but not with highest priority.

Thanks

Andi
[Galaxy S III Android Development] xw0lf:
tnx for answer.. questions/answers 1) & 2) is ok, i no have additional questions...

about 3) i have some ideas/suggestions... for me, MHL is cool, because can put sgs3 video out to much biger screen (good for presentations/games/surfing/youtube....) but, default implementation is bad, because ppl with 720p TV are favored, while we with 1080p are deprived.. auto/handshake choose output resolution for hdmi-in device and for 720p TV it's 1280x720@60fps (default for sgs3 too, maybe 50fps instead 60fps for europe, but not sure) while 1080p TV's get 1920x1080p@24/25/30fps (rescaled sgs3 resolution.. not good for games)

if you have no idea how to fix that (problem is burried in kernel, looks like), you can look at this custom kernel for "htc one" (my link from previous reply).. developer with nickname zeromhl (or mhlzero???) claims to fix that in his kernel build for "htc one" (force hdmi output to 1280x720@60fps)... if this is not hardware specific but rather android specific, you can look in his kernel source how he fix that and duplicate solution for our lovely samsung galaxy s3 :) :) if you find solution to manipulate with hdmi output through mhl, you can add some more option in your confing panel too (auto/manual, resolution 50 or 60fps, whatever....) ?

4) sorry for this, but i not sure and must to ask.. do your kernel is bullet-proof to "sudden death"?
[Galaxy S III Android Development] andip71:
Hi there,

to the HDMI/MHL thing: I had a look at the HTC implementation already a few days ago, but it does not at all apply to Samsung kernel. The files this guy modified are even not existing in our source tree. So we have to continue searching the Samsung drivers :)

Regarding sudden death:

My kernel is as bullet-proof to sudden death as Samsung put all mitigation into the last source code update 10.

Samsung started to fix the sudden death issue with source update7 and refined the implementation with update8 again. Since then it is the same in the code till now.

Nobody can and will guarantee for it, but this is the most we can ever do - using latest sources with the latest fix.

Andi
[Galaxy S III Android Development] maatsby:
Thanks for the reply.

It is very strange, I flashed beta 2 again and its definitely gone. Might be something interacting with the rom? I don't know. Its not a big deal, just interesting.

And good work Bayern! It was a very close game, it could have gone either way
[Galaxy S III Android Development] Madlisboa:
Hi AndiP,do i need to wipe something before to flash anny new version of your kernel?ty.
[Galaxy S III Android Development] SignetSphere:
You don't need to wipe anything just go ahead and flash the kernel ;) Just keep notice when Andi says that you need to reset your settings before flashing a newer version. On the case of 2.12 beta 3 you don't need to reset anything though :D
[Galaxy S III Android Development] Madlisboa:
Thank you :)
[Galaxy S III Android Development] andip71:
Weird, really weird. Can you really replicate this issue by flashing beta2 and beta3 up and down? I really wonder.

But I have to say, I have a bit given up to try and explain everything. There are so many things influencing this stuff, roms, firmwares, apps etc.... so I have to accept sometimes some things are not explainable via distance.

And yes, you are very right. Dortmund was very close to Bayern and it was also a but lucky to punch it in 1 minute before end of the game. But... I am a happy man now :)
[Galaxy S III Android Development] ginzo:
I'm very happy with Boeffla kernel Andi, but I think that I'll have to buy a new battery as the best results that I have with battery friendly settings , screen on for 3h and some minutes more.. I'll never had 4/5 as I see with other happy users. . :(

But I'm very happy of the responsiveness of the phone now and I will replace the battery :thumbup:

!Live! from my Galaxy S3

Rom: Maya v4 XXEMD2 ♥

Kernel: Boeffla 2.12 beta3

Modem: Buelk1

Operator: Vodafone

Recovery: Philz Touch
[Galaxy S III Android Development] maatsby:
Yeah I've definitely reproduced it by flashing back and forth a couple of times. But I think you're right, there are too many variables! I'm happy to wait until its accidentally fixed again in an upcoming version ;)
[Galaxy S III Android Development] donleong:
in my opinion, the screen on time does not represent the battery life of the phone

btw, it depends on the usage of ur phone

if im wrong pls correct me... thanks
[Galaxy S III Android Development] bl4ckdr4gon:
Might not be required from version to version, but I make it a habit to wipe settings via Boeffla app before flashing the newer kernel. Just to avoid possible crap that might happen.

Hope this helps, even if I'm not AndiP. :)
[Galaxy S III Android Development] migz012788:
Dont know what happened. But after i flash beta 3 from beta 2, my phone is much more smoother :D i love this rom!!
[Galaxy S III Android Development] andip71:
Hm... well, it is not a rom, but however...

I mean, I am happy for you to have an even smoother phone now. But the changes between beta2 and beta3 do not really justify this.

Maybe your phone like beta3 somehow more, dont know :)

Anway - enjoy it!

Cheers

Andi
[Galaxy S III Android Development] MIKEMON:
For me everything is really stable and cool.

Do not regard the difference between beta2 and 3

But to really get into the best version for S3

cheers Andip
[Galaxy S III Android Development] MIKEMON:
Yes, everything can affect the performance and stability

Applications, synchronization, and other widgets

I have my rom without any problems
[Galaxy S III Android Development] ginzo:
Yes of course, but when I see a screen on time of 5 or more hours I would like to have the same :D

I am really happy with Boeffla kernel, but I would like to see if with a new battery there is a difference :)

!Live! from my Galaxy S3

Rom: Maya v4 XXEMD2 ♥

Kernel: Boeffla 2.12 beta3

Modem: Buelk1

Operator: Vodafone

Recovery: Philz Touch
[Galaxy S III Android Development] donleong:
haha... i see

same here, really satisfied with this kernel

worth to flash it :D
[Galaxy S III Android Development] alberber:
How can I change screen off max freq with zzmove governor? I don't see any option in the app.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Android Development] andip71:
Not at all currently. This feature will come with zzmoove 0.5 again.

Currently it is not in. Has it been stated somewhere? If so, please let me know, and I need to delete it.

Andi
[Galaxy S III Android Development] alberber:
Oh I didn't know that. Don't worry, I just heard it somewhere so I thought it had that feature.

Thanks.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Android Development] andip71:
No problem at all. It will come with newer zzmoove governor implemenations.

So just stay tuned :)

Andi
[Galaxy S III Android Development] Gorgtech:
I really miss the Boeffla Sound :crying: Hopefully Samsung will release the kernel sources for JB 4.2.2 soon enough :confused:
[Galaxy S III Android Development] enigma1981:
Same here... all my music sounds so bloody lifeless now!!

Swyped from my Galaxy SIII using Tapatalk 4 beta.
[Galaxy S III Android Development] Hbohd:
Forgive my curiousity, but wouldn't adding few scripts to /res work? I have manually added option for choosing screen-off max freq and I think it should work normally...
[Galaxy S III Android Development] andip71:
How exactly have you done it?

Of course there are apps that recoginze when the screen is off (SetCPU e.g.) and then modify the max cpu frequency setting.

But this is not what I meant, zzmoove 0.5 will have it built in as a parameter.

Or how did you exactly do it?

Andi
[Galaxy S III Android Development] DocMarc73:
Just a quick positive feedback on 12beta3:

No issues: daily usage, navigation, calls, music, antutu benchmark, all fine.

Stock rom xxemc3 + jkay mod
[Galaxy S III Android Development] Hbohd:
Okay, sorry. I got confused by version numbers of zzmoove. Your kernel has 0.3 now and it hasn't got screen-off limitations for cpu freq... So it means I added some option to boeffla configuration app that didn't work at all :p