yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] hwjrmrm:
Auto rotation Also works for me now
[Galaxy S III Original Android Development] sunny1234590:
All those who says Autorotation is working. Did you all do a clean flash?
[Galaxy S III Original Android Development] Blackinertia:
Auto-rotation is fixed for me. I'm using boeffla kernel beta 22

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Original Android Development] hwjrmrm:
yes
[Galaxy S III Original Android Development] Lucifer III:
Nevermind,works fine for now...
[Galaxy S III Original Android Development] mattern64:
Auto rotation is working flawlessly for me
[Galaxy S III Original Android Development] zaphod010:
Nope...
[Galaxy S III Original Android Development] strider184:
So, I'm still on the February 28th Nightly since all of the March nightlies I tried had major issues. Is it now okay to update to the latest nightly or should I hold off for longer?
[Galaxy S III Original Android Development] izopi4a:
after 1/2 day of usage seems fine
[Galaxy S III Original Android Development] Bart11666:
Yes everything on latest build working fine and smooth, autorotation also working good.

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Original Android Development] FadeFx:
There is nothing you can do, except using an app to restart mediascanner (i dont know which one exactly, as i am not affected of that problem) everytime the problem occures.

Gesendet von meinem LG-H815 mit Tapatalk
[Galaxy S III Original Android Development] back2android:
Mediaserver killer. It will restart the mediaserver. Camera will work without having to restart the phone.
[Galaxy S III Original Android Development] mcgi5sr2:
Just stopping by to say Hi ! Glad to see your still keeping the S3 alive pal
[Galaxy S III Original Android Development] maciocho:
Hi,

All working fine after latest nightly.

One thing that I can see not resolved and don't know if device specific or CM is the battery power options. When in battery menu there is 3 (low, balanced and power) and when accessed by shortcut suddenly there is 5 with low and power clearly doubled as in the pictures attached.

Long live the dev! Thanks!
[Galaxy S III Original Android Development] ouch01:
When I open the camera (Snap) from the lock screen, it has a bug: There is a "double rotation". I mean, aditionally to the camera rotation, the phone rotates too, and the UI gets messy. Just check:

Logcat of the moment when this happens: http://pastebin.com/jN1LmPd1

Last (today's) nightly, dirty flash.
[Galaxy S III Original Android Development] lukaaa477:
is possible to flash option in camera be on screen as shortcut, just like switch front/rear camera?

and also, possible to fix rotating options in camera because not working well, so options not to rotate?
[Galaxy S III Original Android Development] twitwimp:
Thank You. I will try the media scanner killer.
[Galaxy S III Original Android Development] mloc33:
When I open the camera from the lockscreen, the screen is black, the touch to focus seems to be doing its thing, but still a black screen, same with the video, other than that everything else seems to be bang on.
[Galaxy S III Original Android Development] Lucifer III:
Exactly my words
[Galaxy S III Original Android Development] MWin123:
No data connection

I have no data connection on cm-13.0-20160317-NIGHTLY-i9300.zip.

APN is fine, I did a factory reset in TWRP before installing the ROM and gapps. I even flashed the newest modem.
[Galaxy S III Original Android Development] arifnasirshaikh:
[MENTION=6311143]Trafalgar Square[/MENTION] please stop quoteing same thing again and again...It's annoying and he is just reporting. Some people read this things before flashing new nightly. Peace ✌ ☺
[Galaxy S III Original Android Development] Trafalgar Square:
Developer told us, how to report bugs. If you want to report bugs, do it, how its written in OP.
[Galaxy S III Original Android Development] arifnasirshaikh:
Yes quote this everytime.. This is much better. Not long atleast ?
[Galaxy S III Original Android Development] Bart11666:
But Trafalgar's stats is growing by this annoying quotes :D sorry for trolling, peace ! :)

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Original Android Development] Scorpionea:
U are quite right on how it should be done ,but quoting forks post over and over again can get annoying and u can't stop people reporting bugs without log.
[Galaxy S III Original Android Development] Scorpionea:
I've just had first random reboot on latest nightly 0317

Was on viber sending few messages then wanted to go on homescreen and bam hard rebooted

I have logs ready but can't upload them via Tapatalk and since I'm in bed will do it tomorrow via pc soon as possible
[Galaxy S III Original Android Development] tadydrift:
Used for 1 day and still smooth ( exept my missing external power button i got another S3 which is in better condition today so i might flash it aswell :) since CM13 is good
[Galaxy S III Original Android Development] Sma5hley:
Soft Reboot while updating Google account credentials on clean flash.

App presented with white screen then hung and rebooted. Couldn't grab log, but here is the last_kmsg.
[Galaxy S III Original Android Development] Tom Jerry:
0317 build stable so far

Same here. Used this build all day and it's the most stable so far. Auto-rotation fixed (I did a dirty flash btw). Battery life is ok. Big up to the devs!! :victory:
[Galaxy S III Original Android Development] sn0w89:
flashing with last nightly dont help, bluetooth see another device but dont recive or transfer files, plus find issue with translation on alarm, not critical but it is.
[Galaxy S III Original Android Development] rhyzan:
Just dirty flashed 03.17 Nightly. Rotation is fixed... And ROM doesn't lag when I connect to the Internet... I might give this a day to play around. That's my review so far.

Any news if the ZRAM-random reboot problem is solved?
[Galaxy S III Original Android Development] senaferdy79:
Then probably you should report the bugs tomorrow
[Galaxy S III Original Android Development] deny191:
I get system ui crash when deleting do not disturb tile after clean flash.

Also my clock crash after there is alarm (ringing) and I cancel it.
[Galaxy S III Original Android Development] rashidcm2004:
solved
[Galaxy S III Original Android Development] rhyzan:
Did you turn off your ZRAM? Some say this might be the reason for the random reboots. Turn it off or go to a lower value.

However, I'm gonna turn on ZRAM on 200 to test if it works.

Device: GT-I9300 on CM13

This post is posted on mobile so don't expect too much. Have a nice day!
[Galaxy S III Original Android Development] rchtk:
<0>[ 3453.574811] c2 Kernel panic - not syncing: Out of memory and no killable processes

Default kernel? No kernel adiutor modification?
[Galaxy S III Original Android Development] FadeFx:
Definitely caused by zram/lmk bot working well hand in hand.

Gesendet von meinem LG-H815 mit Tapatalk
[Galaxy S III Original Android Development] g104:
disable/enable zram didn't cause boot-loop on my S3.
[Galaxy S III Original Android Development] cobras3:
Where are the log files guys?

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

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Original Android Development] Maxoobidou:
The clock bug was introduced by the r22 update. There is a fix under review in the gerrit.

[MENTION=5405215]forkbomb444[/MENTION] : I have a random reboot I can easily reproduce. Whenever I try to update Facebook through Google Play Store, it says "installing..." for a few minutes, then the phone gets really slow, to the point where it reboots. Happened 3 times already, so I clean restarted, did the update again to get a cleaner last_kmsg :

http://pastebin.com/TbPFNC0b

I'm on 03 13, tell me if you need anything else.
[Galaxy S III Original Android Development] barthezz_x:
google maps fc when trying to find location
[Galaxy S III Original Android Development] whoadood:
It's not like this ROM has been OOMing since day one, right?
[Galaxy S III Original Android Development] Scorpionea:
[MENTION=5405215]forkbomb444[/MENTION]

i have attached last_kmsg from my last random reboot (also there is logcat if it can be usefull but dont think so)
[Galaxy S III Original Android Development] mattern64:
i am currently on 17/3 and its working smoothly but can the same be said of 18/3. i wish to flash. any advice?
[Galaxy S III Original Android Development] Scorpionea:
Nope,i didint touch anything on stock kernel all default settings

will see how it goes today,if i get another reboot will turn it off and see how it works

thx
[Galaxy S III Original Android Development] FadeFx:
No, its since cm12...

Gesendet von meinem LG-H815 mit Tapatalk
[Galaxy S III Original Android Development] Sma5hley:
All stock. Removed some CM system apps with the open gapps config script.

No kernel mods.
[Galaxy S III Original Android Development] babb1:
please give me a link for the review
[Galaxy S III Original Android Development] volk204:
http://review.cyanogenmod.org/#/c/136674/
[Galaxy S III Original Android Development] cobras3:
Using latest nightly 18.03.

I can't reproduce system UI Crash on the latest nightly 18.03, when deleting "do not disturb" tile after a clean flash.

[MENTION=1260344]Maxoobidou[/MENTION] post edited. I wanted to help, didn't know that this bug is not device specific.

Can't reproduce google maps fc on the last 03.18. After 6 seconds it finds me :D do you disabled permission of google maps to use the location?

Edit: [MENTION=3807917]volk204[/MENTION] then the clock fc will be fixed. tnx
[Galaxy S III Original Android Development] barthezz_x:
figured out that it has something to do with compass calibration, after doing that its working fine :good:
[Galaxy S III Original Android Development] Maxoobidou:
[MENTION=6353535]cobras3[/MENTION] : the clock fix is in review, which means it isn't merged yet. It is not a device specific bug, please stop reporting it in this thread.

Also, the FB bug is a oom bug. Facebook is about as heavy as an app as it gets, and its installation gives me a oom reboot. I have no doubt that everyone else should be able to update without issues. But it gives us somewhat of a way to study the oom issue and get reports on it.

As to why I use it: I rarely do, maybe once a week. But the handling of photos (which is about 90% of what I use the app for: viewing and uploading pictures) of the third party apps are really bad, as they only parse the facebook website.
[Galaxy S III Original Android Development] Schildkloete:
Have to add an error with WiFi. Doesnt drop out only in standby, also when active. Sometimes 5 times in a minute, sometimes 1 in an hour. Pretty annoying when surfing vor playing, error is there since nightly build from mid of february.

Best Regards
[Galaxy S III Original Android Development] rhyzan:
Random WiFi drops is fixed since March. Are you on the latest nightly?

Device: GT-I9300 on CM13

This post is posted on mobile so don't expect too much. Have a nice day!
[Galaxy S III Original Android Development] Maxoobidou:
[MENTION=5405215]forkbomb444[/MENTION] : I saw that you bumped up zram and swappiness in an attempt to solve the oom issues. I don't think that's going to work.

As said earlier, updating Facebook gave me a random reboot (due to memory issues). I could reproduce that reboot 7 times over a few days (every time I tried to update the app).

I just tried disabling zram, and no reboot, no oom issue during the update.

This should show that zram was the issue, not the amount of RAM available on the device.

I know you're caught up in SamsungDoze and Advanced Display stuff, but I just thought I'd let you know.

Here are 2 of the last-kmsg, should you need them:

http://pastebin.com/TbPFNC0b

http://pastebin.com/UAJh95F4

[EDIT]

Please discard. FB didn't actually update, the installation was stopped for some reason. I tried again and got the same reboot, this time without zram.

Here is the last ksmg: http://pastebin.com/fRtpBudL
[Galaxy S III Original Android Development] Bishopandme:
In dl now on my S3 !

Ths for tjis job...

B
[Galaxy S III Original Android Development] JohnSmit268:
Bug Report

[MENTION=5405215]forkbomb444[/MENTION]

**Description**

I reported a bug long time ago but didn't have time to get xposed free logcat. So as I see everyone reported 17 March nightly as pretty stable and bug free, I updated from 2 March nightly to 17 March nightly with clean install to check if the bug is gone, but it was still there so I took logcat from it. The bug is with some games mostly with clash royale crashing and lagging. In clash royale I couldn't start an attack cause when I started it, the game crashed on the loading. And when I clear data of it sometimes gets fixed but still have so many lags. I'm sure this bug is not present in 28 Feb and 2 March nightly as I tried them too.

**Logcat**

Attached to this post.

**Note**

Please reply this post when you found something. I really want to update my phone but I can't do that cause of the bug.
[Galaxy S III Original Android Development] Ahmed Usman:
Snapchat video recording turns out to be processed in negative colors. Any help?
[Galaxy S III Original Android Development] iamNumberThree:
Additionally: Due to admin settings for Exchange Sync I have to enter a 4 digit code in order to unlock the screen. Alarm-Clock App used to override this so I wouldn't have to enter the 4-digit unlock code first in order to turn off the Alarm or set it to snooze. So currently, the alarm starts and the display stays black... It used to activate itself so one could turn off the alarm or set it to snooze. Would that be covered in the review as well?

Cheers
[Galaxy S III Original Android Development] crisvg:
I dirty flashed 18 nightly over 17 and the vídeo playing bug is solved

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Original Android Development] Gokulbalram:
Facebook is too heavy for the phone. It makes the device heat up a lot and pretty much messes your device up. In case you really really want the app, download the Alpha apks off APKMIRROR and disable auto-update for Facebook.

Also one thing people fail to realize is that the S3 has a very poorly documented chipset. You might ask why competitive Snapdragon devices have better performance, and that is because CAF. They have am entire list of commits to help with the OS' performance, while we don't. All we have is a bunch of commits by devs who somehow just figured it out (logs probably idk). Thank Samsung for the experience. If anybody wants to know why Samsung doesn't document it's chipset well:

Samsung was actually very very appreciative of Custom ROMs early in the Galaxy S- Galaxy S2 era. They even handed free S2s to the CM team for development. It all went downhill when a certain leaked firmware update started bricking S2 and Note devices. This wasn't a normal brick that could be fixed by JTAG, the only solution was to change the entire motherboard. Ever after this incident, things went haywire, the CM team even helped Samsung, but alas, communication reduced, Samsung started playing dirty. Any chance to make the source close sourced, they took it. They did this (still doing it) to prevent any kind of issues with a custom ROM (this is what I deduced). Even their current S7 flagship is influenced by this, where the Snap 820 variant is impossible to flash upon.

Yes, this is the same story off XDA, Andrew Dodd (entropy512), but I bothered to put this up here to inform everybody about what they're into here, although it is kind of OP :/

Now if I've gotten something wrong, feel free to help fix it :)
[Galaxy S III Original Android Development] frenzi2016:
Go to ubication, advanced and enable wifi search....
[Galaxy S III Original Android Development] arifnasirshaikh:
If you want to install Facebook...

Turn on caffeine tile for 10 or more mins from notification panel. Then install Facebook from playstore.(don't do anything while installing, phone will get laggy as hell)

This works for me everytime.

I think when screen goes off. Cpu power itself down and ram for some reason goes out of memory thus causing phone to restart. Just my thoughts, I might be wrong. But try the solution, it will guarantee work.
[Galaxy S III Original Android Development] sarath870:
Waiting for snapshot of cm13 for galaxy s3...

Any idea when it will be released...??

Thanks

Chandu
[Galaxy S III Original Android Development] arifnasirshaikh:
When developer decides.. ?
[Galaxy S III Original Android Development] A.Diego:
hi, I am using your rom and I feel good. I would ask if you can force the volume of calls while using a Bluetooth headset because it is low. What can I do for my galaxy s3? The sound of music feels good but the call is too low. thanks to those who respond. regards.
[Galaxy S III Original Android Development] whoadood:
http://review.cyanogenmod.org/#/c/137173/
[Galaxy S III Original Android Development] ZjemCiKolege:
Wow advanced display fix :o
[Galaxy S III Original Android Development] arifnasirshaikh:
Check your Pm
[Galaxy S III Original Android Development] A.Diego:
I do not understand. You can explain better?:confused:
[Galaxy S III Original Android Development] sgs9:
PM = Private Message, look in your xda account :)
[Galaxy S III Original Android Development] rhyzan:
Random reboot here on 03.17. Occured about 14:38 today. I only turned on Wifi, closed the screen, doing my business and when I opened the screen, it hard rebooted.

ZRAM is turned off. Custom LMK values. I'm on Boeffla Kernel (I know that it's not stock. It's obvious. But the commits of this kernel are based on CM stock kernel so might as well report here too.) No mods.

Attached is the last_kmsg. Will report to my kernel thread too for their heads up.
[Galaxy S III Original Android Development] FadeFx:
Usually you should not post any issues with custom kernel installed. However, what is your "custom lmk settings"?

Gesendet von meinem LG-H815 mit Tapatalk
[Galaxy S III Original Android Development] rhyzan:
I know that. But as I said, commits of the stock kernel are also updated to Boeffla and it's probably not a kernel problem.

Right now is 48/60/72/84/96/120.
[Galaxy S III Original Android Development] back2android:
Have you tried changing your lmk values to more aggressive?

I am using 48/96/144/168/192/216.
[Galaxy S III Original Android Development] FadeFx:
Guys i think your "foreground app" and "visible app" value is way too high, try something like 16,32,64,96,128,196 these values have always worked well for me. In some situations an oom unfortunately still can happen, but if you force the system to keep more mem free, it will happen earlier.

Gesendet von meinem LG-H815 mit Tapatalk
[Galaxy S III Original Android Development] maciocho:
Hi,

Anyone noticed that we lost those small pretty icons next to app notifications like "press again to exit"? I see all gone except for the messaging app.

Cheers
[Galaxy S III Original Android Development] back2android:
Actually am not facing any reboots.

As i mentioned few days earlier that as per one of the app, it shows that all the apps are considered as visible apps by android system. So the system starts killing apps only when it reaches to visible apps level. So i intentionally set a high threshold value for visible apps, so that i get more free available ram for fluidity plus i don't get any random reboots on these values.
[Galaxy S III Original Android Development] Uri0550:
Hello there!

I've seen posts that You've managed to fix rotation bug since 17th march build. Is there any possibility to share that knowledge? Because i9305 developers can't figure out how to solve this problem :( and all newer builds have this bug :(
[Galaxy S III Original Android Development] sunny1234590:
Why don't you ask the developers to get in contact with forkbomb?

That would be the best option.
[Galaxy S III Original Android Development] Uri0550:
He just replied in one of i9305 threads :)
[Galaxy S III Original Android Development] whoadood:
Logs of commits are public, there isn't any magic involved.
[Galaxy S III Original Android Development] mamopada:
Stock cm recovery auto update not working causes a loop when installing it
[Galaxy S III Original Android Development] Maxoobidou:
It's been said heaps, but the supported recovery on the i9300 is TWRP.

[MENTION=5405215]forkbomb444[/MENTION]: Is the coming nightly 19 03 safe to use ? I saw you merged some AdvancedDisplay stuff, but not all, and I think you removed it but I'm not entirely sure.

[EDIT]

Just re-checked, and you did remove it : http://review.cyanogenmod.org/#/c/137235/, should be safe then.
[Galaxy S III Original Android Development] Scorpionea:
There are also changes to memory and random reboot issue that has been on 0317

Also KSM is been enabled in next nightly
[Galaxy S III Original Android Development] St3ve32:
I'm really curious to see if ksm won't cause the can't connect to camera issues again..
[Galaxy S III Original Android Development] rhyzan:
Ahh ****. Wrong timing to go back to CM11. I just settled in.

Oh well, I'll return to nightlies as soon as I finished my thesis and ****. No biggie.
[Galaxy S III Original Android Development] hwjrmrm:
clean flashed 0319，no these issues now.
[Galaxy S III Original Android Development] Scorpionea:
Dirty flashed from previous 0317 to 0319 and so far no issues at all,working fine including camera ect ;)
[Galaxy S III Original Android Development] racky29:
Just flashed 0319, but my camera is black screen, this is the first time I've had camera issue, does anyone else have this on this nightly

Edit: camera now works after reboot
[Galaxy S III Original Android Development] Tiberian076:
bt and auto-receiver

When use bt with auto-receiver (jvc) in receiver not displayed dialed and received calls. An error is displayed. At older version its work fine.
[Galaxy S III Original Android Development] itizar1:
I can't do them for now since I am back to old rom. But authentication type is WPA2. And I am sure something is wrong about channel. Whenever I had that issue, I chose a random channel (tried most of them) from modem and problem is gone until a sudden connection loss or long time screen-off-being, then I change it again and it's solved again.
[Galaxy S III Original Android Development] ansh1996:
I have changed a lot of things..if you want i can PM you my profile :)
[Galaxy S III Original Android Development] FadeFx:
Didnt you read this:

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] ansh1996:
[MENTION=5405215]forkbomb444[/MENTION], after using the unofficial build for more than 24 hours, here is my report.

1. Screen flickering: i used a variety of apps in this period, such as facebook, vine, messenger, snapchat, whatsapp, settings, even some heavy games. I can be sure that i DID NOT notice any flickering in any of the apps, NOT EVEN ONCE. So its safe to say, in my opinion, that with this build the flickering issue is all but gone. :)

2. App Crashing and soft reboots: Using some apps like spotify and facebook for the first time, logging in to them made the app real slow and not responding. It kinda just happened when using the app for the first time. Apps like vine after some time of usage gave me a soft reboot to deal with. Now this could be due to just low memory, but it didnt feel like it. If you could look into this issue it would be great.

3. I didn't use wifi in this period as i have unlimited data for 2 months ;)

4. Battery life is not that good, but that would probably be fixed in coming builds.

5. Heads up: are NOT working except for system apps like low battery notification and incoming calls and also messaging. So user apps don't show heads up.

Thats all i have for now, hope this helps you. By the way, if you can please let us know what you did to fix the flickering issue, I'd love to know :)

Ciao.