yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Migual12:
I flashed the same ROM but used OpenGapps. You will find the download link on the cyanogenmod info page for the device at "How to install" https://wiki.cyanogenmod.org/w/I9300_Info
[Galaxy S III Original Android Development] dare74:
cm-13.0-20160822 there are still problems with the camera as soon as you switch to video mode, the picture freezes, and when you take the picture does not keep in the gallery ,restart my phone when a "camera error".
[Galaxy S III Original Android Development] whadi:
did you try to switch between camera and camcorder .. the camera issue is known with bug on this issu
[Galaxy S III Original Android Development] Mrkblo:
Kill the mediaserver and the camera will work again without a reboot (but there are other apps that depend on that, so be aware). There's an alternative CM11 camera that shows that problem less often, a couple of pages back you'll find it.
[Galaxy S III Original Android Development] whadi:
this issue is known, and not fixed yet... you can use third party application, install it and reboot your device everything will works fine
[Galaxy S III Original Android Development] multiwirth:
look in my signature.

This is a simple workarround to use another camera app.

It fixes the camera in cm11 (replacing old apk) and can be used as temporaly workarround for the current camera issue.

Only panorama mode isn´t working, but this is not device specific (tried it on other devices running cm13).

The apk is from cm11 and not optimized to run on android 6.0 due to this the app is crashing in panorama mode.

Its enough to disable the stock camera in settings>apps and install the apk as normal user-app.

I´m also using this, because the ui of the old camera looks nicer for me (fullscreen preview).

Give it a try! :P
[Galaxy S III Original Android Development] edwinnjiru:
"#bugs"

Can't set MTP as default usb action always reverts to charging

Backlight stays on even when set to 30seconds

Restarts occassionally

Good Job on the Rom all in all
[Galaxy S III Original Android Development] sonvegeta:
Thank you.
[Galaxy S III Original Android Development] JohnSmit268:
MTP restarting to charging is the usual way the rom works. You can turn backlight completely off with untickin illuminate buttons. Restarts are usually happens with ram getting full. Try using greenify.
[Galaxy S III Original Android Development] mpsoft:
Problem outgoing calls log Unknown

Anybody problem with outgoing calls log marked Unknown?

Anithing in Zedge download failed?

Im on pico gapps.

Thanks for amazing rom!

Everything else works fine for me!
[Galaxy S III Original Android Development] sonvegeta:
I made another clean flash and I used the Pico Opengapps as suggested, but the problem still persists.
[Galaxy S III Original Android Development] OnDiiish:
Long pressing the home button doesn't open the screen with the latest apps so I could close them anymore. Setting it to a different button doesn't work either. Is there any fix to this?
[Galaxy S III Original Android Development] Apmauj:
Actually Pico opengapps is not mentioned on firrst post...

I'm using micro with no reboots, except when the system load is high... like when I play pokemon go, then all explodes after some minutes.. :D

I had that issue las week, solved when i clean installed a newer version... (now im using snapshot 20/08 and works as intended)
[Galaxy S III Original Android Development] sonvegeta:
I'll make the clean flash with the micro gapps. Hope it works.
[Galaxy S III Original Android Development] sonvegeta:
Lag still persists with the micro gapps. Getting lag in the screen and with music too.
[Galaxy S III Original Android Development] Apmauj:
Have you tried a full clean install (all except external SD..?)

When system gets tricky I make a Format Data (From TWRP wipe menu) reboot, then a full wipe (Wipe > Advanced : all except OTG and external SD..), and then flash rom + gapps, then reboot and wait.. :confused:

Not sure what else can be your problem, it's working normal here...
[Galaxy S III Original Android Development] OnDiiish:
Couldn't access developer options either, I got a message saying "developer options are not available for this user". These problems occurred after flashing boeffla kernel. Had to restore a 2 day old backup to get rid of this weird stuff.
[Galaxy S III Original Android Development] sonvegeta:
I always flash the Rom's I use in this same way. Only in CM13 I saw this type of lag. I was using CM12.1 because of it. I'm using the ROM even with the issues because I like so much the work of the devs who made it.
[Galaxy S III Original Android Development] sonvegeta:
I think I got a clue. I observed the phone for some time, and I think it's about the Wifi: sometimes the wifi suddenly turns off and the phone get so slow that it doesn't work. Could it be it, or a heat problem, or something, else?
[Galaxy S III Original Android Development] nels83:
Do you have ipv6 enabled on your wifi ap ?

Because I had this problem when using it. It seems vmsize is too low for ipv6 (crashes when iptables rules are applied).

Defining a fixed ipv4 address on your device might help.
[Galaxy S III Original Android Development] Bart11666:
for me phone becomes laggy when livedisplay is on. can anyone confirm? btw in last few builds strange random reboots i have, before there was not.
[Galaxy S III Original Android Development] gonzikorn:
Zedge failed. But if you closed zedge and open and try download, maybe fixed. This happen me too and work fine, same problem with facebook and google +. Maybe is for the permissions. I don't know..
[Galaxy S III Original Android Development] Mrkblo:
Camera simply doesnt work on latest nightly. You can open it and take pictures, but the phone wont save them. All you get are blank images on your gallery.

EDIT

It seems the problem is related to the sdcard. Works fine if storage location is set to internal.
[Galaxy S III Original Android Development] aeQuitas90:
I noticed that too..

Let's hope it get fixed
[Galaxy S III Original Android Development] ZionMainframe:
Does this mean we get a official maintainer for our device CM14
[Galaxy S III Original Android Development] wiz2596:
Long live i9300[emoji1]

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Original Android Development] sunny1234590:
That is exactly what it should mean. Forkbomb aka Simon Shields will be maintaining CM14 for our device.

Oh yeah! Long live S3!
[Galaxy S III Original Android Development] mpsoft:
Outgoing calls show as Unknown

All my outgoing calls are labeled as "unknown".

On the other side, incoming call history works fine.

Please help. This bug is very annoying.
[Galaxy S III Original Android Development] anhnambroz:
Oh man XD.
[Galaxy S III Original Android Development] JohnSmit268:
I'm hardly stopping myself from asking for ETAs. I'm really excited. Long live S3!! Tnx to Simon Shields.
[Galaxy S III Original Android Development] pintu gti9300:
Omg you just made my day. Thank you Simon shield you are amazing???
[Galaxy S III Original Android Development] gonzikorn:
Look this! It will be true?? I9300 cm14 say :victory:
[Galaxy S III Original Android Development] JohnSmit268:
Yeah. If you read some posts back, you will see that it's true.
[Galaxy S III Original Android Development] gonzikorn:
Yeah. I see it
[Galaxy S III Original Android Development] ChristianTC:
Hello

I'm using Cyanogenmod 13 and I liked very this rom.

I'm using Cyanogenmod 13 without Gapps and everything works fine.

I wanted to ask if you could add support CM13 weather widget to make it work with Geolocation from UnifiedNlp or microG GmsCore, for use Cyanogenmod without Gapps free, without losing any function.

I leave the link to see what I mean:

UnifiedNlp:

http://xdaforums.com/android/apps-games/app-g-unifiednlp-floss-wi-fi-cell-tower-t2991544

microG GmsCore:

http://xdaforums.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616

Thank you very much for your work, It is a wonderful Rom.
[Galaxy S III Original Android Development] Behemoth1702:
@ Maintaining CM14: Although I really appreciate the effort, what good is maintaining a ROM that is becoming slower, less stable and more unresponsive with each release?

The latest CM11 snapshot still runs fast & smooth. I can open google maps without the whole system starving of memory and needing a minute until it eventually hot-reboots. Meanwhile the mmcqd/0 process is using the MOST CPU time, which is not the case with Cm11.

People are reporting (but probably not bug-tracker-reporting) all kinds of bugs.

Please, don't take this personal, I don't mean anything bad by this. It's just that I personally have lost interest in CM, since it just does not run stable on my device anymore. :(

PS: Is logcat cleared after a hot reboot? I imagine myself experiencing a hot reboot, noticing it a few hours later, saving logcat from the app "CatLog" and hoping that it will contain data from before the crash.
[Galaxy S III Original Android Development] JohnSmit268:
The problems you mentioned can all be fixed. The rom is not slow at all. The only thing you have to do is to kill the tasks and apps. This rom is getting more and more stable build by build. It's a shame that some of us skip this truth. Please be respectful. You can surely stay on CM 11 snapshot. There are lots of people here that wanna try CM 14. If you don't want it, nobody forced you to install it. Have a nice day.
[Galaxy S III Original Android Development] Behemoth1702:
They can be fixed: yes, but will they? It does not seem that way. Why not focuss on stabilizing an "old" CM version before jumping onto the new one? It seems nowadays companies and teams are eager to release something "new" instead of something "really stable".

Killing all tasks and apps is a no-go for a long time - android's memory management takes care of that. Also I don't run any big background apps, mostly just WhatsApp, Telegramm and maybe some Poweramp. Surely this does not explain why when I get a chat message on telegram the I/O usage goes nuts and the mmcqd/0 process takes up lots of CPU usage for no apparent reason and I get big lags until the keyboard responds quickly. I am no DEV but I am no android-usage noob, I tried multiple kernels, keep my phone clean (no background apps) and still the performance is worse for me than CM11. Btw people saying "CM13 is as smooth as CM11" - actually INSTALL cm11 and don't dwell in memories. I would be surprised if people thought the multitasking is faster on CM13. The "recent apps" screen alone takes a second longer to open.

Again, I am not bashing against the team, I highly appreciate the effort for making a great ROM that I use ever since I got the i9300. I am just curious about some background processes in the team and in the phone.

I am respectful. Funny that DEVs never get offended, only their fanboy-userbase.

I am willing to test out CM13 again and report every single bug I find properly, catlog and everything. That surely is more than most of the forum users here do. But I don't want to do it if the DEV team is rushing for CM14 instead of making sure CM13 runs as smooth as older versions of CM. With each version of android there are new features and the focuss might be on getting these to work on the i9300 instead of focussing on "old" stuff.

Is the dialler lag fixed yet? On LP and MM there used to be a 2-5 second delay between your phone vibrating from a call to the screen going on - you could barely answer phone calls . And on CM11 screen, vibration and ring tone happen nearly instantly.

So yeah. No disrespect again, just being curious. So people, please, I am as much of a CM fanboy as you are, recommending it to every single one of my friends who complain about bloatware on their phones. It's the internet though so please, if you see an uncomfortable expression or question - don't rush defending your favorite ROM, try to put yourself into the shoes of the guy who writes the post first and have some empathy, even though this is the internet.
[Galaxy S III Original Android Development] JohnSmit268:
I think you should look at the number of the posts the dev wrote. They are all about bugs. Maybe he won't even read your post, and maybe he reads it but won't answer. C'mon you wrote a long letter :). This is the way almost every developer(except the ones announcing the device EOL) goes. The bugs can be fixed in the continue of the development, here, in CM14. S3's ram is LOW, this is the exact thing everyone should accept. I greenify my apps even on stock 4.3 rom. Becaus s3 has a lack of memory. You can't stop the development process!! This is a no-go goal. Srry for OT everyone. I won't answer you anymore mate. This is a development thread. Not a place to discuss our compliments.
[Galaxy S III Original Android Development] wiz2596:
Wo ho ho ho hey dude please take it easy, if you do not like cm 13 nobody is forcing you to flash it, meantime keep cm11 and everybody's happy

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Original Android Development] Behemoth1702:
I know the S3 has little memory yet in all articles I read that with every android version google does things to improve & optimize memory usage... Argument invalid there. I don't really expect BETTER peformance, but at least I expect the same.

But okay, you guys are right - this is not the place to discuss. Could you PM me to a thread better suited for this? Is the Q&A thread better?

by the way - I really LOVE the android 6 features, it's just that the low-level stuff seems slower and it kills the daily usage fun. Hot reboots are unacceptable.
[Galaxy S III Original Android Development] Survivor1990:
I'm on 01/04/16 version and did not upgrade yet because yes, it's 100 % stable. Not a single reboot yet. I never had CM11 because I came from 4.4.2 TouchWhiz directly to CM12.1 CM13 feels much smoother compared to CM 12.1 for me.
[Galaxy S III Original Android Development] ZjemCiKolege:
90% bugs from this thread non-device related :}
[Galaxy S III Original Android Development] Migual12:
I did a dirty flash changing from a April Version of NIGHTLY to SNAPSHOT 0820. Seems to work quite well except the battery. At battery level of about 40-50 % the phone gets suddenly empty and it shuts off. Meanwhile I fully charged and discharged it which didn't help, than I used Battery Calibration App to reset battery memory which did not help either. Does someone have an Idea? Thanks!
[Galaxy S III Original Android Development] JohnSmit268:
Try using a new battery. I never heard of such problem on CM. I'm using that snapshot build right now.
[Galaxy S III Original Android Development] Migual12:
Solution found

Thanks :D I did not consider this as everything worked well with the NIGHTLY. On the other hand I did several full charge cycles after flashing SNAPSHOT 0820 for training and I use the battery since January only. As I have another new battery here I will try it and report if the issue will be fixed than.

EDIT: After trying a new battery, it worked well. Therefore, no issue with CM. I did not consider the battery as the shutdown of the phone at 40% happend right after changing from NIGHTLY to SNAPSHAT 0820. Thanks again for the hint JohnSmit268 :good:
[Galaxy S III Original Android Development] andrescm:
Frankly the only three things missing in CM13 are, IMHO, HW+ codec support, better OTG pen drives support and better Bluetooth performance (stuttering anyone?). All else is a 10, no hot reboots for me, doesn't fail me when I need it, it's really good. As someone said before and I agree, most problems are probably not ROM related. But I do share a point: whether CM14 is a go or not, please continue improving CM13 at least to reach a stable release.
[Galaxy S III Original Android Development] gonzikorn:
Hello people! Anyone know how i fix the camera error? And what kernel work fine in snapshot 08/20?
[Galaxy S III Original Android Development] pedro_86:
Hi guys,

Does anyone know how to capture the screen in this build ?

Thx
[Galaxy S III Original Android Development] JohnSmit268:
I don't think that any differences were made. It should be power+ volume down.
[Galaxy S III Original Android Development] anhnambroz:
Power and Volume down :)

---------- Post added at 12:15 PM ---------- Previous post was at 12:14 PM ----------

Boeffla Kernel :D
[Galaxy S III Original Android Development] sonvegeta:
Really, thank you for cm14!

---------- Post added at 10:23 ---------- Previous post was at 10:16 ----------

Really, it's very good, but I don''t know why is getting so many lags on my device.
[Galaxy S III Original Android Development] pedro_86:
I am asking because power + volume down doesn't work in my case.

Is there kind of software which can make it instead pressing those two buttons ?

Or maybe they are saved in some android path ?

Thx
[Galaxy S III Original Android Development] anhnambroz:
Setting/Buttons/Power Menu/Screenshot :). Then you can long press power button to take the screenshot :)
[Galaxy S III Original Android Development] zalimtayyar:
I can't be more agree.

Dear devs; [MENTION=5405215]forkbomb444[/MENTION]

First of all please don't get me wrong, I deeply respect and admire all of your work.

I wanted to give a shot to latest snapshot. All I see is a new but much more "choked" phone. Our good old S3 phones don't have enough resource to keep up with 6.0. It is obvious.

As soon as I return to the CM11 I felt the speed and fluidty instantly.

If you want to challence yourself as a coder be my guest, I have no problem with that.

But if your first aim is to give an extra lifetime to the S3 phones please turn back to the CM11.

Because higher version numbers has nothing to give beyond a "placebo" effect.

Respects...
[Galaxy S III Original Android Development] pintu gti9300:
With respect

No body's gonna use s3 forever

No body's gonna flash cm 11 again

Every body's using cm 13

Every body will flash cm 14 when it will be available

With respect ?
[Galaxy S III Original Android Development] JohnSmit268:
I don't know why everybody keeps posting that developing CM14 for i9300 is a bad idea. C'mon if some guys don't like to use it, then don't. If one of these posts you guys write could turns into stopping of the CM14 development progress, it was stopped till now. We are happy to receive CM14, isn't that obvious? If you guys are unhappy with this so please RETURN TO CM11 and keep your ideas for yourself. While the most users of this forum are eagerly waiting for CM14 release to install, I don't know what is the meaning of these posts. Please if you can't help the development process, don't try to stop it at least.
[Galaxy S III Original Android Development] wiz2596:
It has been told many times that nobody is forced to flash a ROM, keep what you feel most comfortable to and everybodys happy, life keeps going on

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Original Android Development] ZjemCiKolege:
Omg i can't read this spam for me I9300 get new life with lolipop and MM :] kitkat is 100% worst :]
[Galaxy S III Original Android Development] wiz2596:
By the way CM 14 is coming guys, stay tunned

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Original Android Development] zalimtayyar:
OMG. You can't even stand to hear a different opinion. What is wrong with you guys? Is it to hard to write without being impolite or banishing people to the out of the topic?
[Galaxy S III Original Android Development] JohnSmit268:
Lol. Mate I check my phone every 15 minutes to see if CM14 is released or not. Then you come here saying that we should go back to developing CM11!! What would you expect else than this answers you've received. You're idea is kinda stupid. Nobody returns to CM11!! Either the device is EOL or we will get CM14. Accept it or not. CM11 is history. It is already pretty stable as you noted. So, no time to waste for CM11. Why should the dev spend his time for a stable build?! If all the devs do it this way. Then we will have no new apps, android releases, roms, and whatsoever. Srry for any impoliteness me or anybody else had to you, but think a little before posting. Think of the answers that you will receive.
[Galaxy S III Original Android Development] nanotech17:
Just installed this lovely rom in my device - may I know how to enable data indicator on the status bar?

Thanks in advance

---------- Post added at 02:08 AM ---------- Previous post was at 01:48 AM ----------

After updating the Superuser via twrp it bootlooped hihi

---------- Post added at 02:24 AM ---------- Previous post was at 02:08 AM ----------

Now it's back to normal after I flashed the latest SU manually via twrp
[Galaxy S III Original Android Development] LKHN:
#1. Offical CM13 Nightly has not statusbar indicator feature.

#2. You dont need flash Superuser or SuperSU. The System have inbuilt su and working robust you can just activate its in Developer Settings. :cool:
[Galaxy S III Original Android Development] noratroll:
You might try using "Xposed Additions" in order to map any action to any key.
[Galaxy S III Original Android Development] Neikon66:
Can anyone help me fix these battery consumption so exaggerated? I do not use the phone and the battery is spent in a few hours

Pictures with wakelock info and more stats

http://imgur.com/a/zbDnC

Example picture

[IMG="batery stats"]http://i.imgur.com/WnmJsh9.png[/IMG]
[Galaxy S III Original Android Development] sno111:
does this rom have any problems, can it be used as a daily driver?
[Galaxy S III Original Android Development] JohnSmit268:
As I see, there are not a lot of problems. But the only way to find out if it is for you or not is to install it.
[Galaxy S III Original Android Development] andrescm:
Do you use greenify?. Anyway, I think your battery consumption is just normal.
[Galaxy S III Original Android Development] dimuthu7:
Deleted
[Galaxy S III Original Android Development] sno111:
i do not have a galaxy s3 currently because i'm waiting for it's screen to get fixed. I will install it as soon as it's done.
[Galaxy S III Original Android Development] pedro_86:
Hi,

I have similar problem like Neikon66 about my battery life time.

I attached the ss from my GS3 in rar archive.
[Galaxy S III Original Android Development] Andi17:
Hello all,

What can i Do to fix the camera crashing without to Reboot the Phone? Snapshot 20160820
[Galaxy S III Original Android Development] slonioo:
Instal MediaServer Killer :) each time camera crushes you will have to run the app
[Galaxy S III Original Android Development] bruce.bane:
Have you noticed problems with built-in firewall? I mean the two options in privacy settings of particular app - disabling WiFi access and mobile data. With one of my apps, I checked both options and the app still uses data in the background. Can it be used instead of of regular firewall (like DroidWall)?
[Galaxy S III Original Android Development] ets2_volvo:
100% charged and plugged off in 9:00 AM, not used all of time, looked 11:00 PM, 80% battery very good, not lags but not prefered play game in outside. Because cyanogenmod very hungry and when u play game eats very hard battery.
[Galaxy S III Original Android Development] sno111:
Works pretty good.
[Galaxy S III Original Android Development] whadi:
just go to setting-app and give the camera all permissions .. hopefully it works .. it works fine for me
[Galaxy S III Original Android Development] hdgremix:
hello

Since yesterday, I try to install this rom with Gapps installation loop, I tested with all Gapps.

I install with TWRP, I did all the wipe and then reboot and install the Rom at the same time that Gapps but loop ...
[Galaxy S III Original Android Development] rp158:
[MENTION=6530439]Andi17[/MENTION]: if camera crashs further, find Search Thread at the top right and enter camera fix