yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] ansh1996:
I'm using the 20160109 build. I have the same opinion. Also couple that with boeffla and i'm getting hilarious deep sleep and great screen on performance. Right now i can say my device is more stable than it ever was on slimkat unofficial.

P.S. if anybody needs my boeffla profile just PM me. I'll send you a link. Cheers :)
[Galaxy S III Original Android Development] DahakePL:
Wifi still turns off by itself, right?
[Galaxy S III Original Android Development] thechosenone43:
Sorry if i reply here but i don't know why i can't send you PM. Something with my settings wrong.

Please PM me your Boeffla Settings. Thank you in advance ??
[Galaxy S III Original Android Development] rchtk:
Stock kernel is still buggy as freq stays at 1400 for a 1% load. Results in 1% batt loss every 1 to 2 minutes. Eventually goes back to 200 after minutes. Its insane.

Boeffla with default settings OK, 200MHz

Not seeing anymore wifi drops with this nightly. Either was a rom bug or I have a different test environment.(seen it only above 1MB/s preventing me from using cmupdater)

So looks like I'm going to keep this ROM :)
[Galaxy S III Original Android Development] rlon23:
Weird I was using boeffla, but when installed the nightly from 20160107 I forgot to flash boeffla, for me stock kernel is working great, never get stuck in 1400mhz.

Gonna try boeffla with the 09 nightly.
[Galaxy S III Original Android Development] tokict:
See On CPU "Frequently Table" tab, most of the time still use 1400 Mhz, so this bug still there.
[Galaxy S III Original Android Development] rlon23:
This is my table with stock kernel.
[Galaxy S III Original Android Development] whoadood:
My phone went full psycho mode and decided to stay awake all night. I wonder what it was up to. Now I'm afraid of falling asleep next to it. Please, send help.
[Galaxy S III Original Android Development] ansh1996:
Check this post here. You will find the link to the profile as well as key features listed here.

http://xdaforums.com/showthread.php?p=64719480

Please leave a thanks if you like my work. :)

Long live I9300 <3
[Galaxy S III Original Android Development] FadeFx:
Guys, neough of custom kernel talk, boeffla has its own thread, go chat there. Also there is nothing wrong with stock kernel, if someone suffers frequency locks he should do some settings with kernel adiutor:

1. Lmk should be set to very agressive

2. Zram should be set to 400mb and swappiness to 85

3. Io sheduler on external sd to row and internal to noop

With those settings i have a smooth system, no frequency locks and no sudden reboots, i can perfectly multitask and there is at best occassional tiny lags, definitely less than with stock touchwiz.

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] Borkse:
To all these guys asking for the battery times of this ROM. I am currently using the nightly from 5 January and the battery life is quite decent. I am using Boeffla Kernel + Greenify + Powernap + Amplify. Standby time is outstanding, losing almost no power at all. See my screenshots. However, there might be a bug concerning the time when wifi is turned on according to the battery settings. Normally it should turn off during stand by with my settings. It's weird that wifi is displayed as on even when the complete phone was turned off over night.
[Galaxy S III Original Android Development] whoadood:
"Boeffla Kernel + Greenify + Powernap + Amplify"

You might as well just turn off the phone.
[Galaxy S III Original Android Development] rchtk:
I am just saying that stock ROM sucks battery ridiculously on my phone right after a clean install. So this ROM , as such is NOT usable for me.

By using an other kernel I proved that it doesn't seem to come from cm core but either kernel or interaction with kernel.

I will try your advice on next cmupdate and will report. These settings hidden in this thread are useless and should either be posted on OP page or as default settings if they prove to be effective.

Anyway, I don't see how my post was off topic in a dev thread. I wouldn't have talked about boeffla unless I would have had a problem as it's the first time I use it.
[Galaxy S III Original Android Development] whoadood:
What do you mean by "wifi drops are caused by ipv6"? My router has no IPv6 support at all, no DHCPv6, no nothing.
[Galaxy S III Original Android Development] sunny1234590:
Little information that I got!

You guys must have seen some merged commits of 'Snap'!

It will run on devices only which are Qualcomm based.

Exynos devices will not be getting it.
[Galaxy S III Original Android Development] rchtk:
Which gapps variant did you use?
[Galaxy S III Original Android Development] rlon23:
OpenGapps mini.
[Galaxy S III Original Android Development] Hemilpatel3296:
Can anyone suggest any good sound mod for this rom.

I used dolby on my earlier ROM, i dont know it works on this or not.

Sound is very less.
[Galaxy S III Original Android Development] ansh1996:
Boeffla kernel has some sound tweaks called boeffla-sound. You can ry it out. Works really well for me.
[Galaxy S III Original Android Development] scorthyn:
same for me, with achille audiophile equalizer setting its awesome
[Galaxy S III Original Android Development] lukaaa477:
can you post those lmk values,im using boeffla so can change it there
[Galaxy S III Original Android Development] JohnSmit268:
That's enough. Finish talking about custom things. There IS a Q&A to talk about custom stuff there. Anybody knows where simon is. His last activity refers to 2016/1/2 !!
[Galaxy S III Original Android Development] FadeFx:
So if you go to wifi settings - extended, you have only one ipv6 adress? Probably it is just a weak wifi signal, or, and that may also be a reason for some issues, the back of the device housing has some screws that are not so tight and the wifi antenna has weak contact to the mainboard.

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] sunny1234590:
That's exactly what I want to know.

Well, seems he is busy with his own life. :) All we can do is wait.

[MENTION=5405215]forkbomb444[/MENTION]
[Galaxy S III Original Android Development] whoadood:
In that screen I only have one IPv6 address. According to ifconfig, it belongs to the "p2p0" interface, which according to Google, is used for "Wi-Fi Direct", whatever that is.

My WiFi signal is excellent, sitting at -55 dBm as of now.

I'm taking a look at logcat and my router's log at the same time, waiting for it to drop the connection.

---------- Post added at 06:07 PM ---------- Previous post was at 05:51 PM ----------

By looking at the logs it looks like it is this problem, although I'm not really sure.

https://code.google.com/p/android/issues/detail?id=196035

http://xdaforums.com/nexus-6p/help/intermittent-wifi-disconnect-logs-t3261635
[Galaxy S III Original Android Development] lukaaa477:
What are very aggressive lmk values?
[Galaxy S III Original Android Development] FadeFx:
Use kernel audiutor, open low memory killer settings and scroll down all the way.

https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] rchtk:
So, after few experiments, it seems that my CPU stays at high frequency only when my sdcard is present.

sdcard is a sandisk formatted as exfat , 64GB and contains a dozen movies.
[Galaxy S III Original Android Development] FadeFx:
Then its the media scanner, it will take a few minutes after boot to scan your media for changes.

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] rchtk:
No

The processor does barely nothing (less than 5% idle), media scanner is not even in the top processes

Frequency keeps most of the time at 1400Mhz for at least an hour (time before I give up)

Only 3 cores out of 4 are used (just discovered this, might be a cause or consequence of the first)

If I change kernel, freq is coherent with cpu load and using 4 cores

So... the problem clearly lies in the kernel under specific scenarios..

Anyway, I'm fed up rebooting and going to enjoy my phone :good:
[Galaxy S III Original Android Development] meexx:
Hi, Any chance to fix wifi drop out in standby ? This is a must have on the phone. Thanks for your great work

Gesendet von meinem SM-T805 mit Tapatalk
[Galaxy S III Original Android Development] whoadood:
I have also downloaded and flashed the Boeffla kernel, I'll see if this helps with the constant battery drain.
[Galaxy S III Original Android Development] Bojmjma:
Same is here, one of the cores is most of the time is offline.

View attachment 3604764
[Galaxy S III Original Android Development] Berta Paneslowski:
I use CM13 since two weeks (latest nightly) and there are some problems that persists.

- wifi goes offline in Deep Sleep, after reactivate screen it re-connect

- (various) browsers crash when play embedded videos in fullscreen

- flashlight turns off when display turns off

- sometimes bluetooth sound stutters, restarting phone resolve this

Any ideas to solve this?
[Galaxy S III Original Android Development] deny191:
This all are known problems for most.
[Galaxy S III Original Android Development] -=|MisterY|=-:
CF.lumen

I'm still interested in getting CF.lumen to work on S3. As mentioned earlier, I had it working on CM 12.

Also, it worked fine on Nexus 7 with Android 6. Today I installed CM 13 on the tablet and CF.lumen worked without any tweaks. However, it is not prompting for root access on start-up so I'm guessing it is working in non-root mode. There is no indication of the active mode.

So, obviously the reason lies somewhere in the code that gets compiled for I9300. I wonder if anybody is interested in this.
[Galaxy S III Original Android Development] rlon23:
Random reboot

Hi, this is the 3rd time I have a random hard reboot (GT-I9300 logo) when trying to watch a video on instagram, it doesnt happen often.

I read that the last kernel message could help, so here it is.
[Galaxy S III Original Android Development] tokict:
Wich kernel are u using?
[Galaxy S III Original Android Development] rlon23:
Stock kernel.
[Galaxy S III Original Android Development] tokict:
With stock setting? Or?
[Galaxy S III Original Android Development] rlon23:
In kernel auditor:

Very agressive LMK

Swappines: 85

Z-Ram 400MB

I/O scheduler, external ROW, internal ROW.
[Galaxy S III Original Android Development] tokict:
Try stock setting then.

It's probably because of your settings are not realy good to run on s3.

I'm on stock kernel with stock settings, and bever had any single random reboot.
[Galaxy S III Original Android Development] rlon23:
I started using this settings since yesterday, before that I also had hard reboots with all stock settings in stock kernel thats why I posted the last_kmsg.
[Galaxy S III Original Android Development] tokict:
When usually "random reboot" happen to you?

Because for me, with stock kernel + stock settings i never had it.

But with boeffla kernel, it happen to me.

From your last_ksmg file, i found this. It mean, maybe it's our hardware limitation.
[Galaxy S III Original Android Development] scorthyn:
Is there a way to hide the brightness bar in Quick settings? Not even with xposed + gravity box seems to go away. Thanks. (Also when i edit the tiles it doesnt stay as i choose to, bug report :D)
[Galaxy S III Original Android Development] kbh9229:
try temasek rom.
[Galaxy S III Original Android Development] bruno$0:
I install this version on my s3 and its great! I got only a small issue on WiFi sinal streght. How i can fix it. Even if i star at beside WiFi rooter the signal is 50%. Thank in advice.
[Galaxy S III Original Android Development] deny191:
What Im worried the most about every nightly is actually flashing. As we all know memory that is used in our devices is wearable. If I flash 280 MB every day, how long will it last? Is that system partition trully a partition? I also used CyanDelta, but it seems that its flashing even more MB.
[Galaxy S III Original Android Development] mamopada:
Anyone else experiencing that if you hit the volume buttons and the volume bar appears that sometimes the arrow for the advanced setting is missing
[Galaxy S III Original Android Development] ianpocks:
Why is not working all cores?? Antutu said that one core is sleeping. I don't know if this is normal or only it is a bug.... Otherways for me this last nightly is fine, sure wifi drop my battery .

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Original Android Development] knuckles1978:
Not an issue. This phone I'm using is about 3 or 4 years old. It's had ROMs flashed on it hundreds of times. Yes, the chip will only take so many writes, but it's unlikely you'll kill it by flashing ROMs, and if you do, well it's a 3 or 4 year old phone anyway. If you don't wanna take the risk then don't flash it.

This phone I'm using now must have had at least 500 flashes...
[Galaxy S III Original Android Development] sunny1234590:
Snapdragon camera needs to be implemented by Simon ( [MENTION=5405215]forkbomb444[/MENTION]) !!

Got this info from Google + page of CM

Can anyone contact him regarding this?
[Galaxy S III Original Android Development] ScratMan38:
It won't work on S3, Snapdragon Camera is made for some of the Qualcomm Snapdragon processors embedding specific features. S3 uses Samsung Exynos processor.
[Galaxy S III Original Android Development] sunny1234590:
A build of AICP for S3 did have the snap camera included!
[Galaxy S III Original Android Development] whoadood:
That's something you have to live with, I'm afraid. Nobody forces you to flash every nightly. New nightlies hardly come with any improvements anyway.

---------- Post added at 02:21 PM ---------- Previous post was at 02:18 PM ----------

I've had tons of reboots because of low memory. Android is supposed to kill the apps that haven't been used recently, but the settings that come with the ROM are absolutely awful. Moments ago I had to stare at a white screen for 10 seconds when I tried to open Gmail.
[Galaxy S III Original Android Development] lauren:
i look forward to your patch for the snapdragon camera... after all you *must* implement it because i *want* it

*shakes head*
[Galaxy S III Original Android Development] rchtk:
Android is supposed to kill it *unless its score is set so* that it is not allowed to kill them.

https://lwn.net/Articles/391222/

/proc/pid/oom*

That's what your log shows : out of memory and no killable process.

I don't have such oom problem and have lots of processes running. I'm running boeffla with default settings.
[Galaxy S III Original Android Development] sanguinesaintly:
Please read the relevant threads - Snap camera is discontinued in that "other" ROM - it's a Snapdragon camera - the clue is in the name.
[Galaxy S III Original Android Development] knuckles1978:
Funny how this has to be spelled out to some. :D
[Galaxy S III Original Android Development] lauren:
dud seriously - i think you missed the sarcasm in my post - it was aimed at the whiny OP demanding features be added to the ROM
[Galaxy S III Original Android Development] knuckles1978:
I know, I was agreeing with you lol
[Galaxy S III Original Android Development] sanguinesaintly:
My reply was aimed at sunny1234590 - sorry - I did get your joke !
[Galaxy S III Original Android Development] whoadood:
I went back to stock. Pretty sad for me, but the ROM is in a very very bad state as of now. Very poor default LMK/swappiness/zram values, only 3 out of 4 cores are in use, CPU frequency stuck at 100% from time to time without a reason, WiFi drops constantly, camera takes a long time to start, ridiculous battery drain, lags lags and more lags... I hope more work is done on this in the future so I can go back because I really like the AOSP experience but, right now, the stock Samsung ROM is just better, despite TouchWiz.

Greetings.
[Galaxy S III Original Android Development] Borkse:
Are you kidding me? Samsung stock ROM is the most horrible ROM for the S3 I have ever seen. It was almost like a new phone to me as soon as I got rid of TouchWiz. I just can't understand what you are complaining about. ZRam isn't needed with this ROM, CPU works very fine with the Boeffla Kernel. Yes, WiFi has some bugs but they appear very rarely (at least in my case). Camera is working decently, too. Battery time is nice as well, especially in stand by.

But you shouldn't forget that this ROM still is in development which means bugs are still there and will hopefully become fixed in the near future. For my purposes, this ROM already works perfectly. The smooth and sharpness is outstanding and I do not want to miss it.
[Galaxy S III Original Android Development] rchtk:
To be fair to cm, i think most of the problems come from M itself (just google wifi marshmallow or battery) so it gets even worse on unsupported hardware.

If I dont' find a solution to wireless shutdown (not only in standby) I'll go back to my previous rom archidroid (stock no way)

That really looks like low level driver problems. Also having modem annoyance when signal is low.
[Galaxy S III Original Android Development] whoadood:
As bad as everything in the Samsung stock ROM is, it is better than CM.

And yes I know it's still in development. And I'm sure it'll improve. Then I'll come back. :)

"The smooth and sharpness is outstanding" just made me laugh, sorry. I don't have 10 seconds to spare every time I open the Google, Gmail or Chrome apps. :)
[Galaxy S III Original Android Development] Vix_Sk:
What this ROM is very very bad? For me this ROM is better than any other ROM that i tried..i find The bug of WiFi only one time..i have installed boeffla kernel and xposed and greenify..and run very well without bug..Also in lollipop rom i have a bug of image in amazon app and issue with bluetooth..that in this ROM work perfect..don't blame this ROM that is excellent..do a clean flash
[Galaxy S III Original Android Development] knuckles1978:
I disagree, but I suppose it's possible that some people will have problems that others don't. I'm assuming you did a full clean install etc. I used opengapps, the aroma installer version because you can then select exactly the level of gapps you want on a per-app basis. And I changed kernel to boeffla.

My experience of this ROM is that it's absolutely daily driver material, and in fact it's the fastest and smoothest ROM I've used on the s3. I switched zram off and made the default lmk values just a little bit more aggressive, not much. I value smoothness and performance over the ability to multitask half a dozen apps at the same time. The S3 is low on memory, it's far from the best device to be multitasking with. But that doesn't bother me at all.

All zram does is give you virtual (slow) memory, with the added expense of using a load of CPU cycles to process it all, putting unnecessary extra load on the CPU as well. It's not worth it. Forget about multitasking. If you want a phone that can handle running 6 apps at a time then the galaxy s3 isn't the right device for you. Kill the zram, keep it to one or two apps in memory at a time, and you'll have a much more pleasant experience.

I've not had any problems like you've had with CPU cores staying at 100% load or anything. Not had any crashes. All I've had is a nice stable, fast phone.

By all means go back to stock if that's what you want to do, but if you had problems with cores staying at 100% and lmk problems, I can assure you that there must have been something borked with your particular installation of the ROM or the tweaks you made to it, and not the ROM itself.
[Galaxy S III Original Android Development] Borkse:
I just can't share your experience. Maybe you are doing heavy multitasking or whatever. I limit my CPU frequency to 1000 MHz and it is still faster than any previous ROM.

Have you done a clean flash? Do you use the Boeffla Kernel? 10 seconds is definitely not normal with this ROM.
[Galaxy S III Original Android Development] whoadood:
I read about zram pages back and I thought it was in use on this phone, turns out it is not? I don't know.

My installation was clean, and I had done absolutely no tweaks-no custom kernel, no lmk changes, absolutely nothing, and it was barely usable.

I understand in a phone with 1 GB of RAM, apps are supposed to die often (sometimes as soon as they go to the background) but in this case it sometimes looked like it tried to keep them all alive at once, which led to constant and absurd lags.

The battery drain and WiFi drop problems are not debatable, I have shown several screenshots of them in the past.

---------- Post added at 06:43 PM ---------- Previous post was at 06:41 PM ----------

If you are going to tell me "yes this ROM is usable but you have to change the kernel, swappiness, LMK values, remove zram, install Xposed and Greenify", I will take that as a joke--it's like I tell you a Renault 5 is **** and you say "yes but if you change the engine, the transmission, you paint it and you change the seats, it's as good as new!".
[Galaxy S III Original Android Development] Vix_Sk:
you can't use a haevy multitasking with this device -.-" do a clean install and put boeffla kernel and sue greenify..i child too can do this..don't talk Mike this is complicate...are things that can do only a dev..and you will sede that this is ROM is pretty perfect..i use this ROM for 3 days and i have a drop of WiFi only when I installed The ROM bit after..i don't have any bug...ANY..and no lag..all run perfect..don't blame The ROM The people have to run it if they want marshmallow..because it runs wery well
[Galaxy S III Original Android Development] knuckles1978:
Your experience is not everyone's experience. I'm not debating that you personally didn't have WiFi issues etc. But I don't, and that tells me that it's something to do with your install.

If it was the ROM, then my experience would be the same as yours, with CPU cores locked at 100%, WiFi issues, horrible slow downs. I've not had any of that (had a small WiFi issue that is now gone), so it can't be the ROM.

And I'm not running greenify, amplify, or any of that stuff. I made a 5 minute couple of changes to the kernel configuration app, which isn't exactly changing the engine, transmission, and giving it a new paint job..
[Galaxy S III Original Android Development] sanguinesaintly:
Calm down boys - this is not the place for "my ROM is faster than your ROM" - we are "supposed" to be finding bugs, not scoring points - so clean flash - stock kernel - no addons - let's get this ROM as good as it can be and then go for the bells and whistles. If you can't get it to perform to your liking, then maybe, just maybe it's not right for your phone (or you're doing something wrong). Every phone is different, and there is nothing to be gained from slagging each other off.

Rant over - let's get back on topic.
[Galaxy S III Original Android Development] rchtk:
I am curious about people having no wireless drop. What are your settings? unless you stare at your screen, the only way to see disconnection is to use an app that needs constant connection (for me, juicessh doesn't keep a connection)

edit: also i am in a crowded place 10+ AP and rather bad gsm signal
[Galaxy S III Original Android Development] JohnSmit268:
No need for kernel change just use greenify and it will do the trick. For me stock kernel is just as fast and battery saving as boeffla. Guys that are complaining about bad stock values and wrong LMK and swapiness and zram values have at least 10 processes open in the same time and it will surely kill the phone cause it hardly have 850 MB of ram. I think greenify+xposed+greenify donation pack will always and on all s3 roms do the trick. You can't complain about stock kernel or stock values when you have so many processes opened and running and refuse to kill it with any task killer app. I personally NEVER had even a soft reboot on this rom. Anyway it's not a note5!! It's a s3 and you must get over with it and kill the opened processes.