yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Vix_Sk:
We have to find bugs? You have said that this ROM is all buggy..you don't help The people and you don't help The developer..try to use for some day this ROM and you will see that all things that you said are wrong..for me this ROM works perfectly in this days
[Galaxy S III Original Android Development] deny191:
Please take this talk to Q&A thread, here its not helping anyone.
[Galaxy S III Original Android Development] JohnSmit268:
Personally I think almost all of the bugs are identified and reported and only some minor ones left that some of them will be fixed in the process of CM nightlys. The thing we need now is the OP to come back and fix them!!
[Galaxy S III Original Android Development] Logan:
Never had wifi issue from first built
[Galaxy S III Original Android Development] FadeFx:
You are right, i also hope simon didnt get a new phone for christmass and abandoned the s3...

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] QuietusPlus:
Thought I would report back on the earlier ad2p stuttering workaround I posted.

Switching I/O Schedulers has been working for the past week. I've used my car about 5 times and it consistently worked every time. Either its one hell of a coincidence or it actually does work.

Again, the settings I'm using are NOOP (Internal) and ROW (External).
[Galaxy S III Original Android Development] rchtk:
Very helpful. Read what I asked
[Galaxy S III Original Android Development] deny191:
In that case CM could give new developer.
[Galaxy S III Original Android Development] whoadood:
From what I've seen it's this issue so it probably isn't specific to this device:

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

http://xdaforums.com/nexus-6p/help/intermittent-wifi-disconnect-logs-t3261635

"This means that the device sent 3 unicast ARP requests to the default gateway 10.88.32.1, spaced 1 second apart, and none of them received a response. It then disconnected because a network with a default gateway that does not respond to ARP is typically unusable."

In first place, I been sending unicast ARP requests with the `arping' utility from another device to my router and it has always responded to them. Then, I wonder if it's reasonable to expect for a router to respond to ARP requests in 3 seconds. A flaky wireless connection could be losing packets and that wouldn't mean it should be dropped in only 3 seconds.
[Galaxy S III Original Android Development] Vix_Sk:
I disabled the option to say if an unprotected WiFi is available..and all works fine..i play COC whitout problem...only one time i have this problem of The WiFi that drop...but was at The first boot..after it never happens
[Galaxy S III Original Android Development] JohnSmit268:
Don't judge that fast if he wants to leave at least he will tell us. And wish this won't happen Simon is the fastest developer I've seen in bug fixes! If he is offline and merged nothing it can only mean that he is busy now. Anyway he is a human and can be busy like all of us. He has a life to manage :)
[Galaxy S III Original Android Development] deny191:
Personally in that case I'd rather prefer a no-life developer then [emoji14]
[Galaxy S III Original Android Development] rlon23:
I know this device have low ram, but why a device like the Moto E never get a kernel panic when I use several apps?

There is something wrong with the ROM, I also tried STOCK 4.3 ROM and never had a reboot.
[Galaxy S III Original Android Development] FadeFx:
I am using (abd suggesting btw) your settings as well and can say that it at least is better than without. However, sometimes it still stutters, but this only occures if the device wasnt rebooted for a longer period of time.

Btw, currently i am testing some tweaks to governor to get a bit more screentime out of the battery by reducing the upscaling. Seems to work well so far and the device still is smooth, will test for a bit longer and post my mods tomorrow or so...

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] Romflasher69:
You have no idea how wrong you are. The CM team doesn't assign developers to maintain a device, it's completely up to the developer to decide which device they're gonna be maintaining upon, and we should all be grateful that Simon took his time to bring MM for this outdated 4 yrs old phone. He's the one who solved most of the major issues with MM and got RIL fully working, so without him, we wouldn't have had Official CM nightlies nor any of the other MM ROMS out there for the i9300.

So do a little research before you write things.

Edit: If Simon decides to stop maintaining, that's fine because at end of the day, this is really old device with crapxynos SoC. There are better, cheaper phones out there and mid-range phones are better than this one for just $150 or less.
[Galaxy S III Original Android Development] FadeFx:
You seem to have no idea how that all works... cm doesnt give developers. Also it has nothi g to do with your or my preferences except the one of the dev.

However, if you prefere a no life dev, just give up your life and become a dev because that is how it works...

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] QuietusPlus:
Couldn't agree more. I was ready for the inevitable, that our i9300 would no longer be getting updates. Suddenly Simon pops up and official builds return, which like I've mentioned before run better than unofficial CM12 builds ever did (still appreciate the effort those devs put in of course).

He deserves some love. And let's give him some time please, its not like he's getting paid for this, he has a real life...
[Galaxy S III Original Android Development] deny191:
Guys, no need to go rough.

My post about no-life developer was intended to be funny. I'm a big fan of CM13, I highly respect Simon's work.

But not logging in to XDA for over a week I find a bit unacceptable in today's world.
[Galaxy S III Original Android Development] JohnSmit268:
Cause it's not only about the ram. CPU and GPU is also important and ram chipset is important too. You can't say why iPhone 5s have 1GB ram and compare it to s3. Even rams have technology differences and comparing between two device without comparing every aspect is useless. And yes, this ROM is in beta stage and still in development so slow downs, hard reboots, soft reboots and kernel panics can be expected and is not surprising. (Even though I NEVER had any of em).
[Galaxy S III Original Android Development] rlon23:
iOS is a completely different topic, Android uses virtualization that's why we need more ram. I guess the Moto E is a better device than the S3 then.
[Galaxy S III Original Android Development] whoadood:
Because there are some configuration values regarding RAM and swap and how they are handled that must be configured properly, and they aren't configured properly in this ROM.

Android does not use any kind of virtualisation to run apps.
[Galaxy S III Original Android Development] RisinT96:
Doesn't android use a Java Virtual Machine?.... Ah wait, it changed with ART to native code.

(Cause dalvik uses JVM)
[Galaxy S III Original Android Development] whoadood:
Calling Dalvik or ART "virtual machines" is oversimplifying what they do. Also, if you think a Java Virtual Machine is akin to a virtual machine such as a Windows guest inside a Linux host running inside VMware, that is not the case.

The behaviour of ART and whatever iOS does is almost the same. Dalvik did a JIT (just in time) compilation of the intermediate bytecode, while ART does an AOT (ahead of time) compilation of the same bytecode. That's why ART runs apps faster but they take a much longer time to be installed (remember the "optimising apps" screen you see when you install a new ROM? It was much faster with Dalvik).
[Galaxy S III Original Android Development] rchtk:
Did you use any specific options for arping? With default options it only sends broadcast ARP (debian sid kernel 4.2)

I've compiled and tried with arp-sk to craft arp requests, in my case .254 is my router, my host is .27

wget http://sid.rstack.org/arp-sk/files/arp-sk-0.0.16.tgz
apt-get install libnet1-dev
./configure
make
cd src
./arp-sk -w -d 192.168.1.254 -S 192.168.1.27 -D 192.168.1.254 -i wlp3s0

This will for sure send an unicast ARP request and you need to check tcpdump to see your router answer (or play with arp -d and arp -an but that might give false positive results)

My router answer to unicast requests.

I would anyway expect the host to send a broadcast request again before concluding that the router is not reachable.

---------- Post added at 11:35 PM ---------- Previous post was at 11:31 PM ----------

I had disabled this option at the first flash but forgot to disable it again at subsequent ones. Typical scanning problems..

Looks like it helps. Have set the phone to keep active when charged and haven't got any disconnection yet. Let's see.

Thanks!
[Galaxy S III Original Android Development] whoadood:
Thank you, I was mistaken then. This is the output and I think it confirms it works. I would expect it not to work, honestly, since my router runs OpenWrt with a couple of patches on it.

root@ubuntu:~# tcpdump -i eno33553360
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eno33554960, link-type EN10MB (Ethernet), capture size 262144 bytes
23:35:02.668951 ARP, Request who-has router.lan tell ubuntu.lan, length 28
23:35:02.670912 ARP, Reply router.lan is-at xx:xx:xx:xx:xx:xx (oui Unknown), length 46
23:35:07.669900 ARP, Request who-has router.lan tell ubuntu.lan, length 28
23:35:07.681180 ARP, Reply router.lan is-at xx:xx:xx:xx:xx:xx (oui Unknown), length 46
23:35:12.671051 ARP, Request who-has router.lan tell ubuntu.lan, length 28
23:35:12.672873 ARP, Reply router.lan is-at xx:xx:xx:xx:xx:xx (oui Unknown), length 46
23:35:17.671747 ARP, Request who-has router.lan tell ubuntu.lan, length 28
23:35:17.674596 ARP, Reply router.lan is-at xx:xx:xx:xx:xx:xx (oui Unknown), length 46
23:35:22.672308 ARP, Request who-has router.lan tell ubuntu.lan, length 28
23:35:22.675324 ARP, Reply router.lan is-at xx:xx:xx:xx:xx:xx (oui Unknown), length 46
23:35:27.673238 ARP, Request who-has router.lan tell ubuntu.lan, length 28
23:35:27.675093 ARP, Reply router.lan is-at xx:xx:xx:xx:xx:xx (oui Unknown), length 46
[Galaxy S III Original Android Development] whatsgood:
Hey guys, I did a bit of questioning in the Moto E forum about LMK and zram values, and a user kindly posted their default values. I think it will be interesting if you guys could test these out and report back with your experiences. http://xdaforums.com/showpost.php?p=64741863&postcount=365

One thing to note is that S3 kernels don't have adaptive lmk like Moto E kernels so this possibly might not give best results
[Galaxy S III Original Android Development] RisinT96:
Yeah .... that's not entirely correct either.

Dalvik does use a virtual machine, it uses JIT to compile frequently executed short segments of bytecode into native machine code, (here comes the VM part: ) but it interprets the rest of the code.

Before android 2.2 dalvik was completely interpreting the code, without compiling the traces into native code.

What ART does is compile all of the code into native code upon installation.

Which is exactly what I said: Dalvik uses a virtual machine, while ART does not.
[Galaxy S III Original Android Development] sunny1234590:
Music Visualizer works on January 10 nightly?
[Galaxy S III Original Android Development] FadeFx:
Remember the settings i suggested? Thats exactly that for lmk and the zram he uses is only 20mb smaller... only swappiness he uses 60 which is way less than i do.

Btw, i have read about that adaptive lmk before, probably this could be implemented here as well. Too bad [MENTION=5405215]forkbomb444[/MENTION] is not available currently, would like to know what he thinks...

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] galen2:
Could u say to me what have to be that question with cm device based development? why u ask that on this thread and no on Q&A thread?
[Galaxy S III Original Android Development] LKHN:
in Settings>> Sounds >> Other Sounds When disable / enable sounds give that error. Clean install 20160110 Nightly. I think it isn't reason to come back 12.1 and not disturbing me.
[Galaxy S III Original Android Development] whatsgood:
Oh right I didn't realise that. But yes this adaptive lmk looks like a helpful feature. I would be interested to see how it affects day to day usage. As far as these LMK + zram settings go, they're working well for me. :good:
[Galaxy S III Original Android Development] ansh1996:
I read somewhere above that this ROM works fine without zRam. Is there someone who can second this with results or screenshots please? You can PM me or just reply in the Q&A section (dodging the Stop OFF-TOPIC posts here).

Also maybe android 6 may have fully implemented ART and thats why now less RAM is required to run apps. Thats a great thing IMO.
[Galaxy S III Original Android Development] JohnSmit268:
I had this problem. Simply reflash the ROM clean and the issue will be gone.
[Galaxy S III Original Android Development] frazzmark:
When I try to call someone, after the call is finished, the dialer can't remember the number I just called and says simply "unknown". If i start the call but I close it before the person answers, the number shows correctly. Anyone else has this problem?
[Galaxy S III Original Android Development] LKHN:
Thanks for reply and solution :)
[Galaxy S III Original Android Development] sunny1234590:
We already know that the battery backup on MM builds is less than what stock touchwiz offers.

Why don't you try antutu?
[Galaxy S III Original Android Development] arifnasirshaikh:
For me i didn't see much or any difference.. Btw its my point of view.
[Galaxy S III Original Android Development] viktor92:
I don't think so. Since KK I believe zram is a must for our device, don't know why so many have concerns about to use it, I'm doing it a for long time and runs very well, the effect on multitasking (even light) is evident. Sure if I could I would deactivate it, but lets face it: with the amount of memory the S3 has, now it's a necessity, and from my experience the use of zram is more than justified.
[Galaxy S III Original Android Development] knuckles1978:
Have you not gone away yet?

Why are you continuing to come here only to post complaints and say how awful the ROM is?

It's not productive, you're just spamming the thread with complaints like you've spent money on buying this ROM and are an unsatisfied customer.

Go use another ROM and stop spamming this thread, nobody is interested in your complaints, and read up on how to properly flash a ROM or something.
[Galaxy S III Original Android Development] viktor92:
From what I've read and I've experienced, that extreme battery consumption you had it's a rare case, not the norm. With CM 12.1 on standby I got 1% on about 3 hours, and maybe a little more, and with CM 13 the values are not far behind than those of CM 12.1.

Anyway if you are happy with stock rom, this is what it counts, so stay with it. ;)
[Galaxy S III Original Android Development] Drollach Gûntar:
With stock kernel, all cpu cores stuck at 1400 and eats my battery too much.Boeffla kernel solved this problem.
[Galaxy S III Original Android Development] knuckles1978:
Ahh I see, you're here to do a public service to prevent random strangers from wasting their time flashing what in your opinion is a substandard quality ROM. /s

If my experience was as you describe, I wouldn't be using this ROM either.

Well, you've now notified everyone how terrible it is. You can go use a different ROM now and leave people in here to talk development. This isn't a complaints thread.
[Galaxy S III Original Android Development] ansh1996:
How is that a fair comparision? Check the awake times first of all. And also if you're talking about DS then obviously that would be better on stock. But remember that with little customization you can get the same DS battery consumption.

---------- Post added at 05:54 PM ---------- Previous post was at 05:51 PM ----------

As an experiment. I did try turning off zRam. At first it was okay and i thought maybe i should've used the stock. But then as apps got opened and closed device became so slow that i had to wait 10-15 seconds for the call to be placed after clicking the call button.

Now I'm back to zRam. All is good again.
[Galaxy S III Original Android Development] sanguinesaintly:
Let's get something straight - every phone and every user is different. We all have different experiences whether it's stability, performance, battery life or whatever. The purpose of this thread is to report issues with the ROM in its stock condition, not to throw around accusations of lying just because another user gets a better result than you do.

No-one is spreading lies, and you are not preventing people from "losing their time" The majority of users here are willing to take the time and effort to flash the ROM in order to find and report real issues, not to find the "perfect" ROM, or to indulge in name-calling.

If this ROM isn't for you, whether it's not a good fit for your particular phone, whether it doesn't play nice with your apps or addons or kernel, or whether you're flashing in an unconventional manner (I don't really care which), then use whatever works for you, but lay off the badmouthing.

Rant over - let's get back to being constructive.
[Galaxy S III Original Android Development] viktor92:
I can't believe that you call liar to another user that doesn't have your problems !!!, I've told you that YOUR experience it's a rare case and in no way shared for the majority of this rom users !!!.

Please do YOU and US a favor, stay with stock rom and FORGET ALL ABOUT THIS MM ROM.
[Galaxy S III Original Android Development] Misterxcs:
Go away !

Be happy or go away ! Have respect to others and to the people wo make this rom possible in their free time ! This a very good room and if you are frustrated in your live or i don´t know or crying about the battery life and other thinks ...then tell it your mother :)
[Galaxy S III Original Android Development] Survivor1990:
Too many idiots out there: a few days ago (just go back a few pages) I had battery times about 10 hours in standby, when wifi was on. Now I know that the reason was a stupid malfunction of my Telekom-Router. I deactivated its WiFi and I'm using my older DIR-615's WiFi again.

My phone is running since 09.01.2016 - 16:55 and I have 48 % left. These are better results I ever had on 12.1 (does not mean that I don't appreciate the work).

So if your phone has bad standby times, check your router first instead of calling us liars.

(Stock Kernel, no greenify etc.)
[Galaxy S III Original Android Development] Flummi.FFM:
One more idea could be to just try the following values from the stock 4.3 kernel:

Zram 300 MB

Swappiness 60

Lmk 24/31/38/48/55/67

Because i also had never reboots on stock 4.3 Firmware
[Galaxy S III Original Android Development] FadeFx:
Dont you get big lags when opening an app or a bigger website with those lmk values?

Imo this way too less free ram during run, so before opening an app it has to clear some ram first.

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] Flummi.FFM:
I tried these settings for 3-4 hours now.

I am using whatsapp, Telegram, chrome and some other apps, 87 in total. Including some apps like Hill climb racing and need for speed no limits.

At the Moment i can't complain at all. I will give you more feedback if something is laggy
[Galaxy S III Original Android Development] hamza touati:
hello guys I want to ask you if the '''' bug = cpu stuck at max has been fixed '''' ????
[Galaxy S III Original Android Development] Vix_Sk:
I think yes..for me it works well..good deep sleep and use 1400 MHz only when play games
[Galaxy S III Original Android Development] Flummi.FFM:
Yes it seems to be gone
[Galaxy S III Original Android Development] sunny1234590:
I still think that it exists on stock kernel however, on boeffla kernel it's not felt by me at least!
[Galaxy S III Original Android Development] K.chez:
Any bugs so far with the latest nightly
[Galaxy S III Original Android Development] JohnSmit268:
I'm still facing it.
[Galaxy S III Original Android Development] Llun:
Hello. I have been using the GREAT CM 13 since 4 days ago but now my phone has no sound. No sound in videos, ringtones, notifications, etc. All is mute. Have any of you guys experienced this?
[Galaxy S III Original Android Development] pintu gti9300:
I am using this ROM from 24.12.15 to till date I think it's time to point some bugs

I am on stock kernel

1. CPU still stuck @ 1400 sometimes(build 10.01.205)

2.WiFi drops ONLY ON OTA SCREEN (Even screen is on or off) except this I didn't see any

3. If I click pictures for 5 to 6 times while recoding a video the recording button blurred & device goes to do not disturb mode I have no option to stop the recording

4. Screencast didn't works recorded videos are broken

5. Can't search cell network manually (Always ended with no network found)

6. I can't see Google search bar in recent menu even its turned on

Battery life is great almost 3.10hrs SO time

I didn't except much from a 3.5yrs old 2100mah battery

I don't know whether it will help or not
[Galaxy S III Original Android Development] rchtk:
Not having this issue

---------- Post added at 08:57 PM ---------- Previous post was at 08:49 PM ----------

Do you have an sdcard? If yes, does rebooting without it fixes the issue?

As for my feedback, fresh install after complete wipe, 3 cores at 1400 3rd core unused.
[Galaxy S III Original Android Development] FadeFx:
Today i had an eye at the frequency lock bug and found out that, when it occures, always we have 3 cores active, two of them show nearly no load, the third core shows 100% load in kernel adiutor but not in cooltool. Now if i disable the one or two cores with kernel adiutor it doesnt help, the lock however goes away as soon as i enable all cores. So for me it looks like there is a bug in hotplugging logic. Thats also the reason i didnt actually see the issue as a real bug because it goes away by itselfs if the system is forced to switch on all 4 cores due to higher load.

Also i have to admit that boeffla kernel has that issue fixed, but thats probably because there is no stock pegasuq governor in boeffla.

Gesendet von meinem GT-I9300

---------- Post added at 09:48 PM ---------- Previous post was at 09:44 PM ----------

Can you try using a different governor than pegasusq and see if the problem persists?

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] viktor92:
Two days ago I've tried nightly 9/1, and it runs fine, but the problems I had with 1/1 are there, internal root doesn't work well, can't restore nothing with MyBackup Pro before flashing CF SuperSu, can't uninstall system apps (only disable it), and external SD and USB OTA are not properly detected. I will stay on CM 12.1 and try to resist longer to test another nightly.
[Galaxy S III Original Android Development] rchtk:
Too late, already flashed another kernel. Will do on next and perform really high load test.

I use trepn profiler for seeing cores activity. Quite professional app.

Even with boeffla core3 is often off.

Personnaly my concern is with battery. I loose 30% during a 7h night.. This night will tell with zero app and sync disabled but I fear modem problems in bad 3G conditions..
[Galaxy S III Original Android Development] Vix_Sk:
During nigths 8 hours i lose 4%