yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] raphman:
While trying to install Facebook app I have had 1 soft reboot, then I tried again, and 1 hard reboot. Phone became very hot and unresponsive, while CPU was about 10℅. I'm on zzmove battery yank. Same happened with messenger.

Nothing interesting in logcat but the fb package compilation events.

So I disabled zRam and reboot, and then everything installed flawlessly.

I think there's something related with zRam about the bugs related by some users.

Note : cm 13 have been installed after a total wipe (formatted all partitions)
[Galaxy S III Android Development] andip71:
Then the two or three people which reported the reboots can try it.

In general it confirms my statement which I do since cm12... The s3 is memory-wise extremely outdated for modern roms.

Andi
[Galaxy S III Android Development] andrey210973:
No rebooting, no overheating of the CPU.
[Galaxy S III Android Development] andip71:
CM13 kernel update

Good morning,

new week, new start, with an update to the CM13 kernel.

Version 5.0-beta6

04.01.2016

Important: You need at least Boeffla-Config V2 in version 2.2.16 or higher on this kernel !!!

Update: Ramdisk of official CM13.0 build of 04.01.16

Enjoy

Andi
[Galaxy S III Android Development] tokict:
Installed !!!

Thanks Andi, for the first kernel update "this year". :thumbup::D
[Galaxy S III Android Development] Logan:
Works perfectly andi you are the boss :D

(I only update the cm13 when you update the ramdisk)
[Galaxy S III Android Development] alex16021973:
The New boeffla 5 beta 6 its a best.

Top score from 41000 to 42800 ??

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] DodgerTheRunner:
What Kernel settings do you have to get such a score?
[Galaxy S III Android Development] alex16021973:
Last nightle

BF kernel 5 beta 6

BF config v2

kernel adiutor from APP store

Tis is my config of kernel.

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] Romflasher69:
No wonder why people complain about battery draining :laugh:
[Galaxy S III Android Development] alex16021973:
no Problem white my battery.

My battery its 100% OK for my.

White full Akku 10-12 hours , facebook, tapatalk, whatsapp no Problem.

Tis is my best system.

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] craP_cillA:
?? why do you use boeffla-kernel?! AND kernel adiutor?!^^ thats crap dude.. ;) cause you got the boeffla-kernel app to configure boeffla-kernel...no need for kernel adiutor! and by the way: if you configure kernel adiutor you have to enable it (bei systemstart anwenden) to work :'D
[Galaxy S III Android Development] Logan:
Normal usage with stock boeffla config settings battery ends in 7-8h.

3.5h ost, i think my battery is broken because in different roms with different kernels when i have battery less than 10% and turn phone off then plug the chrager.

immediately the battery turns to 50% charge(like from3% to50% in 1 second) after that i turn the phone on, the battery starts draining from 50% in fast way until 20% then screen freezes and phone dies 0% battery then charges normally!

This sign for dead battery or charger?
[Galaxy S III Android Development] lazylord2016:
+1
[Galaxy S III Android Development] sunny1234590:
Same here! Maybe [MENTION=947981]Lord Boeffla[/MENTION] can tell us about this.
[Galaxy S III Android Development] viktor92:
Your battery is dead. The same happened with the Galaxy Pocket of my daughter (original battery with little use...), changed for a new one (alternative brand but with warranty) and all the weird behaviors were gone :good:
[Galaxy S III Android Development] ansh1996:
Flashing different ROMS with different sources can sometimes mess up the battery stats. What you can try is using battery calibrator from play store. Try calibrating your battery with that app. If that does not solve your problem then your batteries have run their lifetime and you need to change them.
[Galaxy S III Android Development] andip71:
Well, there is not so much to add... Batteries are getting old and defective over the time.

When I was still running my S3, I replaced my battery every 12 months to always have good battery duration.

Usually the symptoms explained here point to a "weak" battery. So after charging starts, the voltage rises up very quickly (which you see in the percentage value too) as it does not properly store the power anymore.

Andi
[Galaxy S III Android Development] PRO>KOMP.<:
What OC settings is safe for S3?

I want little more performance but don't want to kill S3. :)
[Galaxy S III Android Development] Kenfary72:
but for cyanogenmod 13 the kernel is good or much bug?

one question

what is the difference :

idle+lpa

lpa after

idle only

who is good for battery and little performance?
[Galaxy S III Android Development] tokict:
Hi, [MENTION=947981]Lord Boeffla[/MENTION]

After using your cm 13 beta 6 kernel with 04/01/2016 nightly build for some days.

Unfortunatelly thoose "Freeze and Hard Reboot" issue happen to me. [emoji24] [emoji24]

It's happening mostly while i'm using s3 for playing game wich is consume much memory/RAM. Eg : Fifa 16 UT (FYI : this is never happen before)

Would you please take a look at this?

For now, i try to turn off zRam. And let's see what is the result.
[Galaxy S III Android Development] andip71:
Sorry, cannot look into something I do not have here. I never had a single freeze.

And there is no reason why something should be different all of a sudden, kernel code is the same as on CM12.x etc.

I think we have to accept, CM13 is at the very beginning and nothing stable should be expected before end of January (as also said by CM team in December).

Sorry for being hard here, but S3 development for me is over. So I am not gonna spend time on fixing general issues not related to my code.

Thanks for understanding

Andi
[Galaxy S III Android Development] andip71:
Tell us the result. Maybe zRam (which I was never a big fan of) does not play nicely with CM13. And this is something I could easily do - not enabling it by default.

Waiting for your report :)

Andi
[Galaxy S III Android Development] tokict:
Thanks for your response.

Ok. I understand what you mean.

Let's hope that this is really cm 13 issue itself (not a kernel issue), and will be fixed by CM ASAP, like you said.

Even if it's never been fixed. So, we should accept that maybe it's our device hardware problem. As we know s3 i9300 very old phones. Wich is not enough again to handle too many newest things.

Thanks Andi

You already do the best for s3 i9300
[Galaxy S III Android Development] andip71:
Exactly.

The thing is - and that was the main reason for me to move on to newer phonse: Memory.

1 GB is just not enough anymore for todays apps and Android versions.

zRam helps a bit, but it is not curing the original issue of having not enough ram, it is a dirty workaround in my eyes. Hence does not surprise me if it comes with stability issues.

Since I have my OnePlus One with 3 GB and my OnePlus 2 with 4 GB memory, all this tweaks and workarounds are not needed anymore. And I really enjoy that stability a lot :)

Thanks

Andi
[Galaxy S III Android Development] tokict:
Ok. Will give you report after some hours/days using it without zRam.
[Galaxy S III Android Development] andip71:
I will provide a maintenance update today anyways, so will remove the default zRam already.

Cheers

Andi
[Galaxy S III Android Development] baltics:
The i9300 is like the Mercedes W123.

With lots of care and attention and a new battery every year or two, it just keeps performing.

For heavy games there are much better devices than mobile phones with 1GB of memory.

Though my first desk top computer only had 256MB until I doubled it to 512MB. But that was 20 years ago, running Windows 95.
[Galaxy S III Android Development] tokict:
Thanks Andi

Will immediatelly flashed it as soon as i get notification about maintenance update.

Also, i think today is the day for update.

Because today CM move to "6.0.1 r10". I don't know, even its related to kernel/not.

But, i think its needed. :D
[Galaxy S III Android Development] andip71:
Very soon... my phone is currently booting up with the new kernel. When it runs, I will push it out to you guys.

Andi
[Galaxy S III Android Development] andip71:
CM13 kernel maintenance update

Hi all,

here we go for the promised CM13 kernel maintenance update:

Version 5.0-beta7

04.01.2016

Change: zRam is now disabled by default after a fresh install - recommendation: if you do not need zRam urgently, switch it off

Update: Ramdisk of official CM13.0 build of 07.01.16

Enjoy

Andi
[Galaxy S III Android Development] tokict:
Thanks Andi

Will check it throug boeffla config apps.

Mmm... maybe it should be Beta 7 right?
[Galaxy S III Android Development] andip71:
Yep, corrected.

Thanks

Andi
[Galaxy S III Android Development] sunny1234590:
Thanks a lot for the new version. Will give it a try ASAP!
[Galaxy S III Android Development] fir1996:
[MENTION=7054841]Boeffla[/MENTION] I have flash temaseks cm13 and it have very very great deep sleep time so I was thinking why your kernel does not have deep sleep while screen off because it help's a lot saving the battery look at this picture of temasek's stock kernel.

[IMG="cm13"]http://i65.tinypic.com/zkljxt.png[/IMG]

[IMG="c"]http://i67.tinypic.com/2s0dzz5.png[/IMG]
[Galaxy S III Android Development] andip71:
No problem to have the same deep sleep with my kernel.

Kernel is not holding the majority of wake locks.

Maybe not on Temaseks rom, I cannot speak for that as my kernel is targetting pure CM only.

Andi
[Galaxy S III Android Development] Kenfary72:
[MENTION=947981]Lord Boeffla[/MENTION]

Hi all..

why I only did an hour of screen? with CyanogenMod 11 + 3 boeffla I do ....

my settings ...

someone give me some advice please?

sorry for English are Italian
[Galaxy S III Android Development] andip71:
If I understood you correctly...

CM11 was much more efficient on battery than CM12.x or CM13 (this is why I still prefer CM11 over everything on the S3).

But it looks like your battery is not yet calibrated again or your battery is going slowly dead.

If you, however, did heavy gaming during that hour, then it is no surprise I guess.

Andi
[Galaxy S III Android Development] Kenfary72:
no I have not played ... just a few minutes ... but will settle this problem? becouse the 13 cm is prettier than the 11 you see it more fluid ... but consumes very ... well before burning now with boeffla I placed the temperature was 60 degrees ... before without doing anything ....
[Galaxy S III Android Development] andip71:
LOL, nobody can answer that.

You need to check for wake locks, processes running crazy. The usual stuff.

I never reach 60 degrees and I have hours of SOT.

Andi
[Galaxy S III Android Development] Kenfary72:
with the kernel CyanogenMod 13 was only 60 degrees screen ... for the battery, the screen settings of my boeffla is good? I have to fix another? 45/50 degrees now using apps etc .. but .. it's a question better idle + lpa, after idle, after lpa ... who is good? I do not understand the difference ...
[Galaxy S III Android Development] rpdroky:
Hy Andi , i have a little problem with the configuration app , every time i change a voltage the voltage number text goes blank , when you have the time could you check it out please :)

Cheers :highfive:
[Galaxy S III Android Development] andip71:
Maybe some others can answer. I am not using my S3 anymore, but I am sure some guys can give you some guidance.

And for the idle mode: i recommend idle+lpa

Almost everything for the S3 is explained in the documentation sections on the kernel homepage:

www.boeffla-kernel.de

Andi
[Galaxy S III Android Development] Minto107:
Idle+LPA is best and if you don't understand just don't touch it :) As Andi said CM13 is still polished so wait for newer builds and don't blame kernel! Be thankful that Andi does anything for I9300 when Archi's S3 is dead and he's gone from S3 development, arter97 also. Andi makes amazing job here with supporting End Of Life kernel???

Thank you Andi ;)

Wysłane z mojego Lenovo TAB S8-50LC przy użyciu Tapatalka
[Galaxy S III Android Development] Kenfary72:
yes thanks :)

But if I put the phone should be as -75 undervoolt someone has tried?
[Galaxy S III Android Development] rpdroky:
If you use ZZMOOVE governor (except RELAX Profile) use AFTR+LPA

If you use PEGASUSQ use IDLE+LPA

Cheers :highfive:
[Galaxy S III Android Development] andip71:
Confirmed, but only on CM13 - regardless which phone. This is really funny, must be a CM13 glitch.

I will try to fix that, although I have not yet a clue why it is so :)

Andi
[Galaxy S III Android Development] rpdroky:
That's why i said its a little problem , maybe the fix will come eventualy from CM as they progress in fixing bugs :)

THX Andi :highfive:
[Galaxy S III Android Development] Kenfary72:
One profile good form battery?

But if i put the phone shiuld be ad -75 undervoolt Simeone gas tried?
[Galaxy S III Android Development] rpdroky:
This depends on yre ASV level first , some devices can go -100+ (i have 763mv on 200mhz , 900mv is stock) , some can't handle even -25 ( they start freezing cand crashing and thats why [MENTION=947981]Lord Boeffla[/MENTION] doesn't recommend undervolting )
[Galaxy S III Android Development] Kenfary72:
ah thanks ... OK if I put -75 to try not ruin the phone right?
[Galaxy S III Android Development] rpdroky:
Undervolting doesn't ruin the phone , its just making the device unstable if you reduce the voltages to much , Overvolting yes , that could reduce the CPU life

if -75 is stable (no crash , freezing) , you should use it
[Galaxy S III Android Development] Kenfary72:
ah ok thanks, I wanted to try undervoolt -75, but I fear that hangs .... profile that you are using for the battery?
[Galaxy S III Android Development] rpdroky:
Do a backup of the ROM before messing with voltages (use TWRP recovery) , and disabe Dynamic FileSync in Boeffla APP (to evade data coruption if the phone crashes) , my profile is working only for my device because the voltage pathern defers between the ASV levels

Make a Text on the desktop and write there the voltages u find stable ( this depends on yre luck )

I will upload my profile later on the [Unofficial] Boeffla Kernel Profile Sharing Thread

Apologises to [MENTION=947981]Lord Boeffla[/MENTION] for beeing off-topic
[Galaxy S III Android Development] xeizo:
I installed it again, on the go, is it the correct version compiled Sun 17:56:12 which I succeeded to download?

(not used to hacking when there's no PC available)

Great work anyways!
[Galaxy S III Android Development] nazfalas:
In my case automatic flashing doesn't work and I do it manually through TWRP. The kernel downloaded by the config app had a different name than I was used to: cm-kernel.zip instead of the name including the version. For anyone like me looking for the file...

Thanks for the update! New governor works amazingly well. Slightly higher battery use than lulzactive, but soooo responsive.
[Galaxy S III Android Development] GoGoris:
The new pegasusqplus kernel in beta4 never seems to use more than 2 cores.
[Galaxy S III Android Development] _WiNNa_:
Also with the new beta4, swappiness is reset to 0 after reboot...
[Galaxy S III Android Development] xeizo:
Not true, all cores working happily according to cpu-z! Jumps nicely between 400-1600 MHz on my phone. Using the new governor in balanced mode.
[Galaxy S III Android Development] ekie84:
Will your kernel works on CM11?using the stock kernel i cant turn on the wifi...thanks :D
[Galaxy S III Android Development] andip71:
Don't think so with making changes.

Never tried though...

Had priority on Sammy 4.3 kernel in the past days :)

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] Cleto Gadelha:
There is a fix for wifi. U can find a link in temasek's thread.
[Galaxy S III Android Development] ekie84:
yes i know,i am using temasek kernel :D i just want to other kernel hehe
[Galaxy S III Android Development] tufail.budoo:
Its simply awesome... good job man..

---------- Post added at 07:58 AM ---------- Previous post was at 07:57 AM ----------

Its simply awesome. Good job man..
[Galaxy S III Android Development] Yasounet:
Same issue here, doesn't matter if in battery, standard or balanced, it never uses more than two cores.
[Galaxy S III Android Development] andip71:
Are you really sure?

I mean, did you run an app like Stability Test that really demands all the power?

I had all cores jumping to on if the full power was really required.

Thanks, just trying my best in my small available time.

My current priorities are:

- get version 2.0 stable out (likely today)

- get a first alpha kernel for Samsung 4.3 roms out

- then I will look into CM11 topics

This is weird. Having any other apps that could be conflicting

Or any scripts used in init.d?

You can mail me a debug info file you can create in Boeffla-config App.

Interesting, this is an old bug of the config app (well - lets say... a glitch as in CM world a lot is going on every time so it is hard to keep up to date always).

So, should not really occur anymore.

If so, please also mail me a debug info file next time (or send me the bc.log files from your boeffla-kernel-data folder). Then I can look where it went wrong.

Cheers

Andi
[Galaxy S III Android Development] _WiNNa_:
Just sent you a mail with the debug file...

Thx
[Galaxy S III Android Development] Yasounet:
My bad, thought that stressing phone with couple of more demanding games and 1080p video would ve been enough. It spikes to all 4 cores while testing with antutu, but during every day use, it sticks to max 2, causing choppyness in couple of apps. Worth mentioning that those apps work smooth with zzmoove on yank battery profile. I guess in the end its a trade off between smoothness and battery life ?

Also wanted to use opportunity and thank for feedback, and also for all work you ve put into making our experience with sgs3 much better :)
[Galaxy S III Android Development] andip71:
2.0 stable

Hi all,

2.0 stable is now officially released for CM10.1 and CM10.2

Change log is the same as 2.0-beta4.

Only one exception for the CM10.2 kernel:

IMPORTANT: As per notice of 01.11.2013, my CM10.2 kernels do NOT support proprietary Custom Rom frameworks anymore. So if your Custom Rom did not implement the generic framework class framework-2.jar but his own naming convention, you will receive a boot loop. Do not cry about this here but advise your Custom om cooker to fix this. I will not change this ever again.

The most prominent custom kernels for CM will follow the same approach (aligned between Yank555, Googy, Teufel, Psndna, Temasek and me).

If you have trouble with this and a boot loop, you can still flash back 2.0-beta4 for the moment. But long term you will get in trouble if your Custom Rom team does not support the generic approach.

Out of experience so far:

Cyanogenmod - works

Slim Bean - works

Carbon - works

Fusion - works

ArchiDroid - works

Pac Man - ??

Bam - ??

Enjoy

Andi
[Galaxy S III Android Development] HorstiG:
Thank you for Update, work perfect on Galaxy S3 with Carbon Nightly 11.13. (O.T. nach anfänglichen Anfänger Schwierigkeiten) :D
[Galaxy S III Android Development] Kiszonyogor95:
That was fast update sir :)

Probably going to work on 4.4 kernel in near future or I am wrong?

Cheers and thank you !

Tapnięte z mojego Nexusa 7 2013
[Galaxy S III Android Development] andip71:
Potentially.

But only after 4.3 Samsung Kernel is in stable shape and released as a beta to the folks.

Everything step by step :)

Andi
[Galaxy S III Android Development] DonHuan:
Works fine with LiquidSmooth v2.37! :good:
[Galaxy S III Android Development] andip71:
Allright, I just pushed app version 2.2.19. I hope I could work around this glitch. Apparently Android M does not like buttons in a table cell which are configured with a specific width.

At least on all my phones I tried, this issue is now gone.

Andi
[Galaxy S III Android Development] rpdroky:
I can to confirm that the butons are ideed fixed :victory: , Thanks allot [MENTION=947981]Lord Boeffla[/MENTION]

Cheers :highfive:
[Galaxy S III Android Development] Kenfary72:
Good now see :)

Thanks :)

---------- Post added at 06:53 PM ---------- Previous post was at 06:10 PM ----------

with CyanogenMod 11 I have a problem ...

because the phone does not sleep?

first with 12.1 + boeffla kernel and my phone was turned off, and hours and hours (8 hours) down to 5% for example ...

with CyanogenMod 11 ... use androidmytools to turn off the wake, however, does not sleep ...

does anyone know why?

other question ... best government for the battery? someone has a good setting for the battery?

PS cm13: I tried -75 undervoolt and all ok :)
[Galaxy S III Android Development] konqui15:
Is it only me? With alpha18 for cm12.1 I have no BT_BT wakelook. With alpha19 I got more drain and BT_BT is on top. Checked with better battery stat. I flashed alpha18 over alpha19.

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] Kenfary72:
I have no problems with 12.1 cm of deep sleep .. but I have problems that do not work performance ... for example I can not play with real racing .. instead with 11:13 ... you obviously have the same profiles put ... who gives me advice? I'm sorry for breaking too XD ....

I am use real racing for test performance...
[Galaxy S III Android Development] viktor92:
I remember the term "fatware", and it's 100% valid with android. I've never programmed in android or linux, but how can be posible that the simplest app "eats" several megabytes of ram ??, why windows Xp with 1 Gb of ram can multitask several normal programs like a champ, and in a phone we need 2 or 3 Gb of ram ??. Do android need a big optimization in many aspects or I'm missing something ??

In my phone zram does a big difference doing multitasking, and I was contrary to the idea of using it until KK, but now for me it's default and don't feel any penalty in performance.
[Galaxy S III Android Development] azazello22:
Vuoi una buona durata della batteria? Torna su CM11. CM12 e 13 non sono adatti se brami così tante ore di durata, e nemmeno per giochi particolarmente pesanti come Real Racing. Non so come facciano a capire il tuo inglese, comunque.

Do you want a good battery life? Go back to CM11, as 12 and 13 are not so good in these terms. And they're not so good at managing heavy games such as Real Racing, too.
[Galaxy S III Android Development] Kenfary72:
yes ... but how to set it? to me it does not last very ... more than 12 cm and 13 safe ... but not quite .... any advice you how to set it?
[Galaxy S III Android Development] Kenfary72:
but how do you do? which parameters do you use?
[Galaxy S III Android Development] DodgerTheRunner:
Hi,

in the early morning I had an unexpected reset.

I'm using CM13 from07.01. with your kernel beta7.

Attached you find the last_kmsg.

I think it is an low memory issue, but I'm not sure.

Regards,

Dodger
[Galaxy S III Android Development] ScratMan38:
Because Windows uses compiled executables. The code is compiled to be directly executed by the machine it runs on (x86). So only the compiled code is loaded in memory.

Android uses a java VM in order to use same apps on different platforms (ARM, ARM64, x86... There is no limitation). Apps are not compiled. So the memory must host the system, the apps java code, the java interpreter and the compiled code generated by the interpreter.

It's bigger, but much more flexible as app developers don't have to build their app for several hardware platforms.
[Galaxy S III Android Development] andip71:
Correct, the line in the log is:

"Kernel panic - not syncing: Out of memory and no killable processes..."

So, memory got exhausted. I keep on saying, 1 GB is not enough anymore for todays Android versions and todays big fat apps.

zRam might help for a while, but also is not 100% super stable many times (as over the time it also gets exhausted).

Andi