yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] joeyjoey022:
Okay guys, I recently bought a new OEM battery for my phone cause my old one was seriously lacking. I thought I would share some of my battery stats with you all! Also I'm currently on nightly 20160618 and have Greenify working, Xposed Framework as well as Boeffla Kernel installed just so you know! (No settings in kernel changed besides Governor, will mention which - keep reading)

The first set of screenshots are with the Governor set to Pegasusq.

Now these are the results with the Governor set to zzmoove battery plus.

3 hours SoT at 50% mark!

I highly suggest you get your hands on a new genuine battery if you are having battery woes! [emoji2]
[Galaxy S III Original Android Development] PsychoFreaq:
The funny thing is I'm having the same battery times (2 - 3 hours on 50%) on genuine one.

The other thing is that it looses only 3-5% during night, so maybe time calculator is failing?
[Galaxy S III Original Android Development] mavippro98:
I have installed but I can't do the next step of your guide. can you show me by any pictures. please...

---------- Post added at 10:31 AM ---------- Previous post was at 10:16 AM ----------

i can't update to version 25-07 because of MD5's fail. how can i fix it .....
[Galaxy S III Original Android Development] JimTimmler:
Three hours left on 50 ℅ mark? That's horrible!

I have quite similar settings but got rid of ok Google and Google App and deinstalled nfc Service.

Here is what it looks for me:

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Original Android Development] mahe.:
Hope ur SOT is not 3 Hours :)
[Galaxy S III Original Android Development] joeyjoey022:
No man,the 3hrs left at 50% is potentially 3hrs of SoT because I was using my phone the 3hrs prior to the screenshots thus in total potentially a Sot of give/take 6hrs!
[Galaxy S III Original Android Development] disguisedview:
I'm still facing random reboots on Nigthly-20160723...
[Galaxy S III Original Android Development] Sachindave:
Hai...i updated to latest nightly.. but facing no vibration issue
[Galaxy S III Original Android Development] _lightning_:
Still the same at latest nightly. I think it gets fixed soon.

---------- Post added at 10:13 PM ---------- Previous post was at 10:05 PM ----------

Checked again on latest nightly, it is OK.

I'm using the rom as my daily driver since 21.07.2016, never experienced problems with vibration.

If your device's vibration motor is OK, try clean flashing.
[Galaxy S III Original Android Development] JvdW:
I'm having the same annoying problem.

Don't have a solution yet., well....back to stock i guess.
[Galaxy S III Original Android Development] Sssnakey85:
reboot and wifi problems

Hi,

I experience some big issues lately with my WiFi and my phone reboots around 8 times each day on random occasions. Very annoying for a phone to do! :)

So yesterday I did a clean install with the 20160724 nightly, thinking it would have helped me out but it's not. My phone keeps rebooting on random times and when I want to connect to my WiFi at home it freezes. The only thing I can do is to press my powerbutton for a long time so it reboots.

I did a reset on my router as well but nothing helps.

Is there anyone else having these problems? And is it possible to fix?

I'm running CM13 since January 25th and never had big problems until now.
[Galaxy S III Original Android Development] patmes:
I had That problem too with the last builds and i'm back to omga v61 that is 4.3 and i have no problems anymore. At this moment there are too many problems with this rom for daily use.
[Galaxy S III Original Android Development] Bojmjma:
Do you use any screen dimming app? if you do disable it and see what happens.
[Galaxy S III Original Android Development] joker2mbr:
I'm on Resurrection Remix right now (CM13 based as well). I was using the latest version (5.7.1) and it has the same NFC issues as the current CM13 from this thread. I tried downgrading to version 5.6.9 (from May 20th) and now the app is working fine with my NFC card. :) There's also a version 5.7.0, but I didn't try this one.

It really looks like this NFC issue was introduced sometime between the end of May and now and every CM13 based ROM has it. I guess I'll stick with V 5.6.9 from Resurrection Remix at least until I hear something about the NFC issue being fixed on CM13.

Best regards,

joker2mbr
[Galaxy S III Original Android Development] PsychoFreaq:
I did not install any screen dimming app.

The only stuff I have is:

cm-13.0-20160722-NIGHTLY-i9300

A-GAPPS+6.0.1_14.05.2016_v5.2 (from: http://xdaforums.com/android/general/gapps-gapps-6-0-1-minimal-t3276606)

But I've noticed strange - not smooth dimming sometimes.

Do you know if it's possible to turn it off somewhere?
[Galaxy S III Original Android Development] VinnyDD:
Thanks for the reply. This issue seems so unknown, because it affects just that app as far as I know x).

Regardless, I'll try that RR ROM 5.6.9 too.

Hope one day this issue is fixed.

Best regards.
[Galaxy S III Original Android Development] Bojmjma:
sorry, i don't no how.

i am also on 22th bot i don't have problem with permissions.
[Galaxy S III Original Android Development] Migual12:
recommentation for stable version

I would like to flash CM 13 on my GT-i9300. As I read about many issues, can someone recommend a stable version for daily use, no matter if nightly or snapshot? Will there eventually be a new snapshot in the near future?

If I flash nano Gapps, would it be possible to install "Now on Taps" later via Playstore?

Thank you. :confused:
[Galaxy S III Original Android Development] JarAss:
If camera crash error, you don't have to reboot the phone, just install the app from Google Play, named "Camera restarter" and simple one-click fix crash that error without reboot. :)

Yeah blue hue color problém in Snapchat is still and I don't know how to fix it, reboot doesn't help for me.
[Galaxy S III Original Android Development] Csr312:
Hi, I am having troubles trying to update it from the Rom, It tells me that permissions are not conceded. It works just great, and amazingly good with Pokémon Go, thanks you all.
[Galaxy S III Original Android Development] iamNumberThree:
Hi,

I'm currently running nightly of the 24th of July. Seems to be pretty stable (for me). No random reebots or stuttering as of now. Camera seems to be working fine, too. YouTube running perfectly as well. Not sure if you want to use snapchat - can't tell on this one since I'm not using it, but some people reported issues - even though maybe not on this specific nighlty but the issues with snapchat seem to persist.

Only thing I keep noticing over and over is that Facebook App installation/update (every Wednesday :)) is a pain and takes forever, but it installs fine if you wait long enough and don't interrupt your phone while installing - but that's nothing really new.

If you want me to test a specific app on this nighly, let me know - of course it should not require a log-in or a specific account of any kind.

Regards
[Galaxy S III Original Android Development] anhnambroz:
What is the best kernel for this rom? I think it is Boeffla.
[Galaxy S III Original Android Development] noratroll:
I use Boeffla without any issues. I can recommend it.
[Galaxy S III Original Android Development] anhnambroz:
Now i'm using latest nightly and if i flash Boeffla, will it work?
[Galaxy S III Original Android Development] Andi17:
For Sure will it work
[Galaxy S III Original Android Development] frudda:
Thanks will test :good:
[Galaxy S III Original Android Development] Migual12:
Thank you very much. An important App for me is TomTom GO as I use it often. Another feature is wireless charging with an additional coil on the battery. Do you know if it works? Tank you.
[Galaxy S III Original Android Development] vlkr:
Wireless charging

I've done wireless charging for about a year, at first with Lollipop and for some months now with Marshmallow. Never had any issues with it. I guess this is rather a hardware topic, thus independent from what OS you actually use. You know, in fact charging works even if the device is turned off, so no fear.
[Galaxy S III Original Android Development] LikMaiPootey:
I like cm13 alot but had to go back to cm11 becuz of the baterry draining and overheating issues. Just broswing trough settings for 5 mins was enough to burn my phone. Nightlies arent for me ;-; Im using cm11 snapshot and it works flawlessly ;3
[Galaxy S III Original Android Development] frudda:
I got 100% battery improvement an extra day. Phone has good temperature and acts fast

Greenify donating package

(sytemsettings: Wakeup Timer Coalescing 4.4+, Telephony Wakeup, Block state abuse, Greenify system apps) Many into hibernation including google play store

Xposed framework

App: Version 3.0 alpha4 (made by rovo89, Tungstwenty) (to be able to activate Greenify)

Flashed: version 86.0-alt (custom build by wanam 160710)

Boeffla kernel

(Governor: smartass V2) (CPU tweak MAX 1300 Mhz I dont want high peaks which makes phone hot. MINIMUM 300 mhz so it starts fast when want to use the phone. Undervolt light ) (GPU 350 /440 /533 /600...... with overvolt 25mv) Light on display off. Swap 700mb

Other things done:

Front Alert light disabled

Location disabled

Camera restarter app when camera hangs use it someone gave me the tip.

fstrim every night (dont know if its needed but its run trim every night)

Disabled Wifi when phone idle

Greenify icon on desktop to be able to hibernate apps when needed

Phone has way better temperatures and it starts fast and the flow of the phone is better.

It dont overheat. But dont try this at home if u dont know what you are doing. You can brick the phone
[Galaxy S III Original Android Development] patmes:
Is there a way too remove the google now bar on the screen with the google now launcher.
[Galaxy S III Original Android Development] noratroll:
I recommend using Nova Launcher instead.
[Galaxy S III Original Android Development] g104:
anyone here always turn on DND mode? flash new rom or gapps & reboot with DND mode turned ON will cause "unfortunately settings has stopped"

https://review.cyanogenmod.org/#/c/153700
[Galaxy S III Original Android Development] iamNumberThree:
Hi,

I cannot comment on wireless charging, but somebody else has in the meantime. So I'll take that one off of my list... :)

On the TOMTOM GO... I just installed it... 78MB download for the app itself... 1GB for the "DACH - MAP". Download and installation (app and map) went smoothly, so no problem there.

Planning of routes seems to be working well (at the first glimpse) - better phone-hardware would make the calculation quicker, I guess, but since route planning/calculation works pretty slow on stand alone gps navigation devices, too, I would assume that's something one could live with.

Since I do not have the upgrade - and do not want it - I only get 75 km of free navigation. I will test (most likely) tomorrow on my way to work. That should still give enough of an indication whether the "GPS & TOMTOM App"-interworking works as well. I'll get back to you...
[Galaxy S III Original Android Development] UweRammelt:
Screenshot on Power button?

Hi all!

Is there a way to place the Screenshot function to the power button?

For example: pressing the power button about one second a menu appears "Switch off", "Restart", "Screenshot" ....

Kind regards,

UR
[Galaxy S III Original Android Development] LKHN:
Sure. Go to Settings >> Button >> Power menu and put a tick to Screenshot.

Please ask such questions at Q&A section -> http://xdaforums.com/galaxy-s3/help/qa-cyanogenmod-13-nightlies-i9300-t3275604
[Galaxy S III Original Android Development] UweRammelt:
Perfect - thank you !!

Oh, I did not found this section before ...

Kind regards,

UR
[Galaxy S III Original Android Development] immarcel:
Okay, so i got a random reboot using google street view, and now I'm stuck in a bootloop. Tried taking the battery out, no success, the phone automatically boots and reboots after the logo, so I can't get into recovery. Any suggestions?
[Galaxy S III Original Android Development] andrescm:
Check the power button, it might be stuck. A simple test: take out the battery and then put it again. If the phone turns itself on automatically, bingo.
[Galaxy S III Original Android Development] immarcel:
No, i don't think it has to do with the power button. I somehow got into recovery, wiped the cahce and dalvik (only those), then the phone proceeded to takeme through the cm setup process, deleted all my apps. So, I painfully install all of them, and it turned off, and bootloop again. Also, it kept freezing every 30 seconds.

EDIT: i can't even get into download mode

EDIT 2: After repeatedly pushing the power button, the problem seems to be fixed
[Galaxy S III Original Android Development] adrianinsaval:
I ocassionally have the same issue, power button is the problem, I usually fix it by pressing and strongly tapping the zone of the power button especially the back of the phone near the button. The frequency of the problem was reduced when I found out and adjusted a loose screw, I also have one screw missing so that might be the cause, I suggest checking if there are loose or missing screws. Sorry if I have bad english.
[Galaxy S III Original Android Development] flipswitch5point:
Faulty power button. Had mine replace in a shop about a year ago. You can get them on eBay if the shop will charge you less for bringing your own button and you're willing to wait (the shop may have in stock - call first) Replace the button, this will keep happening over and over.
[Galaxy S III Original Android Development] andrescm:
It happened to me about six months ago, since then no more trouble. I cross my fingers!
[Galaxy S III Original Android Development] iamNumberThree:
Hi,

O.K. So I did some further testing on the TOMTOM Go App... I used this this morning to navigate to work -- even thoug I know the way :laugh: - on my motorbike.

I started the app and set up the route. I felt like cleaning the display before I put my mobile phone into the protective casing. So for cleaning I pushed the power button to switch the display off when I finished cleaning I wanted to reactivate the display and pushed the power button again. The app didn't recover and crashed. :( So I restarted the app, set the route/destination again and turned the phone to see the image/map in landscape mode - the screen turned into landscape mode and the app crashed again. :( Both those test-cases I retested and in both of those cases the crash DID NOT reoccur - which is good :)

After having restarted the app again I set the destination (again) and put the phone into my protection-case which I have for use on the motorbike and let it do the navigation to the place I am working at. I (on purpose) deviated from the planned route to see whether the route-recalcualtion works. All of that worked flawlessly. The recalcualtion of the route was done very quickly / almost instantaniously. The S3 never lost the GPS signal on the way. The way to work usually takes me about 30 - 35 minutes, today it took (due to traffic) about 45 minutes. Those 45 minutes drained the battery from ~55% at the start to 23% - which is pretty decent compared to battery on a stand-alone device specifically designed for navigation. So with a completely charged battery and without recharging along the way/route you will get about 2 - 2,5 hours of battery life. I did not use the "Battery Saving Mode" the TOMTOM app provides - so I do not know how many additional minutes this would give you. One thing I noticed when taking the SGS3 out of the protective case is that it got insanely hot - but so do stand-alone devices in this protective case - since those casings need to be water-proof and do not have any ventilation. But all in all (besides the two app-crashes in the beginning which did not reoccur) this worked very well. Let me know if you want me to test anything else with this app - I still have 35 km of free navigation (out of 70 km) left in app-test-mode before I would need to upgrade to the full version... :good::good::good:

Regards
[Galaxy S III Original Android Development] andrescm:
Alright, some breaking news on this one.

First of all, this commit did fix part of the bluetooth problem. Before it I wasn't able to maintain 10 seconds of continued audio, so the problem was real and the fix worked too. But today I discovered the second cause for the stuttering: distance. And no large distance, just 1 meter will do. If I keep the phone in my pants or the front seats of my car, the music is flawless. I put the phone on the back seat and there's the stuttering. Move the phone back to front and sounds perfect again.

Since having the phone in the back seat is very common because my daughter plays music with it, I know for sure this didn't happen with CM 12.1 nor CM 11. So in light of my limited knowledge of things, my best guess would be this is something related to a lower bluetooth transmission power (perhaps to improve battery life?).

I'd like to provide a logcat if someone kindly tells me how to make one, unless the devs know this issue won't show up there.
[Galaxy S III Original Android Development] Migual12:
Hi, thanks, I am just flashing CM13 nightly from 24th. Did first a recovery of stock rom in case of problems. Will than test TomTom.[emoji1]
[Galaxy S III Original Android Development] djedjy:
Am I the only one with the problem of volume steps?? Is it a bug or?
[Galaxy S III Original Android Development] broken-arrow:
Yes the mobile get hot, the temp or soc protection not work properly (not at all a guess, some talk about this before).

So surfing and gaming do my mobile hot, some time is crashing=reboot to (get really slow and soon crash).
[Galaxy S III Original Android Development] Migual12:
Thank you for the profound tests. I flashed nightly 24 yesterday and it runs smooth. Installed also TomTom Go with 5 GB Western Europe map and tried it just few km with the car. It worked quite well. It showed also traffic jams on the map and imported my destinations. The main problem with Stock Android 4 is that TomTom might stop without warning and the only possibility is to install it newly with 5 GB of maps. This error is reported in many fora. It happened to me during last holiday which was a mess, as I had a bad internet access. This is one of the main reasons to try CM13. I will report after some weeks tryal or immediately if the error appears with CM13. [emoji15] [emoji15] [emoji15]
[Galaxy S III Original Android Development] joeyjoey022:
Does anyone know if there is cm13 based rom with working HW+ for I9300? I really want HW+ working on here,but CM have never had working HW+ for the S3 ever (?)

Heck if someone would teach me how to code or how to implement it into the build I would happily do it myself! :(
[Galaxy S III Original Android Development] _lightning_:
FIXED, thanks.

Edit: Lock screen camera quick launch visor screen layout problem. It was in attachment.
[Galaxy S III Original Android Development] viktor92:
AFAIK, CM13 still doesn't support HW+, but CM 12.1 does.
[Galaxy S III Original Android Development] Scorpionea:
Nameless rom has hw+ working ever since it was released for lollipop or marshmallow ;)
[Galaxy S III Original Android Development] joeyjoey022:
Nameless is not Cm-based. It's AOSP bruh...
[Galaxy S III Original Android Development] jesus693:
anyone knows how to remove the # that is on one side of the hour. I also try to update but I get error trwp
[Galaxy S III Original Android Development] lithoc:
That's a root access permission indicator. It means, some of your apps are running root access

To remove the # , either disable root access completely in developer mode or kill the apps that using the root permission
[Galaxy S III Original Android Development] slonioo:
Or instal SuperSU as root handler - it doesn't show this i on than.
[Galaxy S III Original Android Development] rchtk:
Alarm clock is not working for me. It just says ''alarm missed''. Anyone facing the issue? Is there any fix?
[Galaxy S III Original Android Development] iamNumberThree:
Is the audio file you chose as an alarm sound playing on another/any other audio player on the phone?
[Galaxy S III Original Android Development] Logan:
There is xposed module called disable su indicator which has been merged in different module called "all my" or try "cm settings"
[Galaxy S III Original Android Development] DrmohamedShawky:
after today's build i have nothing to complain about

everything is perfect for me except for the camera

rom is very snappy, no lags, even the damn heavy Facebook works very smooth

battery life is ok

never faced the wifi drop issue

hope someone make a fix for the camera like [MENTION=5161352]JustArchi[/MENTION] fix for cm 11

thanks a lot [MENTION=5405215]forkbomb444[/MENTION] , you did a great work man
[Galaxy S III Original Android Development] deny191:
What is exactly your problem with camera?
[Galaxy S III Original Android Development] FadeFx:
I think it was a problem in stock kernel as well, but am not totally sure. However, it is not anymore now.

To not confuse devs with bigs that are either solved or even not present in the rom, we should not discuss hete unless the bug appears on latest build without modifications like custom kernels, xposed, viper4android and whatnot...

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] izopi4a:
yea, its damn annoyingly smooth, i have colleagues with newer phones that i can outperform.

Google maps navigation calculates like every single turn and displays it, while with cm12.1 it was not enough ram, and navigation wasn't perfect.

Damn my phone feels new.
[Galaxy S III Original Android Development] DrmohamedShawky:
sometimes i have to cant connect to camera error

i tried different camera apps but non were perfect always have resolution issue with video

open camera is the best of i have ever tried till now
[Galaxy S III Original Android Development] FadeFx:
I guess this will never be solved, there are at least three different camera modules built into our devices, one works perfect most of the time, the other two make problems like this more or less often.

Media scanner killer seems to be the only working option except rebooting after each failure...

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] cubeever:
Load "mediasever killer" APP from the play store and give me a feedback it it works! :)
[Galaxy S III Original Android Development] Logan:
Try mediaserver killer from google play
[Galaxy S III Original Android Development] JustArchi:
Just wanted to stop by to say that I'm very glad somebody picked it up and fixed everything what was broken. Cheers.
[Galaxy S III Original Android Development] deny191:
I don't remember getting a single "Cannot connect to camera". And I take quite some pics, atleast 100 daily. Only issue that is bothering me is video recording freeze while taking shots.
[Galaxy S III Original Android Development] DrmohamedShawky:
thank you guys for your reply will try and feedback :)

Edit : it worked :)

thanks again

---------- Post added at 12:57 PM ---------- Previous post was at 12:56 PM ----------

it was awesome fixed every single camera error in asop

wish we could have such a fix in CM 13

---------- Post added at 12:59 PM ---------- Previous post was at 12:57 PM ----------

with pic i have no problem

that error only appear with videos then i have to restart to get the camera working
[Galaxy S III Original Android Development] hamza touati:
[MENTION=5161352]JustArchi[/MENTION] are you going to make ArchiDroid 3.2 for i9300 now that we have official cm13 ???????? please :(
[Galaxy S III Original Android Development] Andi17:
Very much thanks for your explanation, but i don't will change my Modem because i don't know which adventage i have if i change it. :) and I don't know how to change. I flash only New Roms :)
[Galaxy S III Original Android Development] JustArchi:
No, I ended supporting SGS3.
[Galaxy S III Original Android Development] Kord:
Okay, it's same on the stock kernel, all 4 cores online and locked at 1,4ghz. It's definitely something with ROM, but what? :confused: