yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Neodgod:
I don't care what anyone thinks about my posts.

My statements are real.

I already explained that in idle my battery is dying very fast while the WiFi is on.

When WiFi is off, it's okay. That's why most of you see no probs with the battery life.

You'd probably say "then turn off wifi".

But why? It's just a matter of fixing it.

Why do I say that?

Cause CM13 does not bvrn energy in idle while Wifi is on.

Conpare that average 5H on screen time on CM13 to the 2H on LOS.

So it's absolutely possible. They're just not focusing on that.

Which I stated as understandable (I guess) cause it's a nightly. And also said that I hope it'll be fixed soon.

I can't flash roms on and off all the time cause I need my phone.

I will follow the thread but for now CM13 is better (alhtough around 10% slower).

Basically I said I need a stable, reliable phone, so I'm going back to CM13.

Why are you trying so hard to find something you can argue with me for?

Don't misplace reasonable comments as complaints guys.
[Galaxy S III Original Android Development] RPHemrajani:
Frequent apps crashing

WhatsApp, Instagram, Chrome, etc crashing frequently..! Is it only me? Btw using stock kernel and -0308 Rom :confused:
[Galaxy S III Original Android Development] baltics:
The great advantage of LOS 7.1.1. is that memory management is brilliant.

Assuming the ROM & GAPPs were correctly installed using the optimum recovery app, the likely cause is that you have something in your internal storage which is causing the problem.

Why not capture and post a logcat?

Perhaps someone can help.
[Galaxy S III Original Android Development] mohand06:
I check on LineageOS threads for gt-i9300 only to know about issues or bugs with the roms cause I still like testing custom roms. I have plenty of backed up customs installations (Weekly, RR, CrDroid).

Best way to stop complaining about device as daily driver is to stay on stock Samsung rom. I'm very satisfied with my S3 as second device (beside a more recent A3), stock tw JB 4.3 updated to latest firmware XXUGPE1 (2016), stock kernel: swift, no sim or wifi issues, very good camera, better sound than on custom roms, all the usual goodies and above all very good battery life!
[Galaxy S III Original Android Development] pix106:
I never had so huge drains using this rom.

Such drain may more likely be caused by an app than the system.

Try using a battery stats app to know which app it is (one with many instant notifications, background service...)
[Galaxy S III Original Android Development] Neodgod:
Then it should do the same with CM13. Not 100%, but still.

By the way I use nothing other than fb, fb messenger, viber, nova launcher and XDA.

I already tried deleting nova launcher. No change.

Thank you for your answer :)

Yea, yours is fine cause you don't have wifi on, right?

And I did use it. And it said Android OS, Idle, Android system and other stuff like that.
[Galaxy S III Original Android Development] tonga01:
"My day" function finally appeared on my S3!! It isn`t connected with an update. I just woke up, opened the app and the magic happened. :)
[Galaxy S III Original Android Development] Razvan:
Thread cleaned for OT posts.

[MENTION=4426785]abelenki[/MENTION], please read my PM.

Regards,

Razvan

Forum Moderator
[Galaxy S III Original Android Development] LKHN:
I am on Stock ROM 4.3. Only reason is Front Camera working on video calls (Whatsapp, Viber etc.). [MENTION=5405215]forkbomb444[/MENTION] any hope about that on LOS14.1 ? :rolleyes:
[Galaxy S III Original Android Development] LuciferIII:
Oh my looord ,thank you.
[Galaxy S III Original Android Development] pix106:
wifi is on, but no well-known battery eater like facebook :)
[Galaxy S III Original Android Development] xEmre66:
Thank you so much!!!
[Galaxy S III Original Android Development] johnaddams83:
03/15 has severe problems with SIM card. Phone process crash randomly. The phone doesn't recognize the 2 sims I have (different operators), a total mess, and I only figured this out after setting the whole phone from zero. Holy phuck. We
[Galaxy S III Original Android Development] minealex2244:
Thank you, Răzvan. Having the thread clean mean easy access to valuable information.
[Galaxy S III Original Android Development] andrescm:
Strange, I'm not having a single problem. In fact so far I still haven't seen the famous "MTP crash" message either [emoji1]
[Galaxy S III Original Android Development] LuciferIII:
Lucky you.

But just to be sure,try to open the build in file manager and see if it crashes.
[Galaxy S III Original Android Development] notstpaul:
No serious problems like that for me.
[Galaxy S III Original Android Development] andrescm:
I'm sorry I don't understand what you mean with "open the build".
[Galaxy S III Original Android Development] g104:
try tap in the app named as "Files"

literally, "MTP Host has stopped" will be appeared after few secs only.

now u try go tap in again no issue right? reboot/switch off your S3 & try again the same error will be shown for the 1st time u try to tap in.

if u tried to uninstall any apps the "MTP Host has stopped" will be triggered too.
[Galaxy S III Original Android Development] LuciferIII:
Build-in file manager.

The app that you manage your files.

Its called "Files" .
[Galaxy S III Original Android Development] MARCOSOFT:
I installed the latest version (from 4.3 full format to 7.1.1) and the calls made by bluetooth have a lot of noise, even being totally imperceptible!

Anyone with this problem?
[Galaxy S III Original Android Development] zarere:
Anyone knows which is the latest version (ROM) where viber,whatsapp video calls are working?
[Galaxy S III Original Android Development] LuciferIII:
They never worked till now.
[Galaxy S III Original Android Development] zarere:
I' m confused so viber and whatsapp video are working on the latest Lineage ROM?
[Galaxy S III Original Android Development] LuciferIII:
No,they don't work.
[Galaxy S III Original Android Development] andrescm:
Ha, you mean "built-in" ;). Well I confirm the crash is still there :D
[Galaxy S III Original Android Development] LuciferIII:
Sry that i typed it like that,i read it myself and got confused too :silly:
[Galaxy S III Original Android Development] Samofr:
They work on Lineage but not on our device yet.
[Galaxy S III Original Android Development] AlecSpence:
Yes the "MTP Host has stopped" error appears when you first launch Files (the built-in file manager), as it can do at other points using this OS. I've struggled to work out exactly what it means, but have not experienced any adverse effects other than the error message.

Early days, but I currently really like the latest 20170315 build. While 20170301 was also good, I'd found a moderate dip in battery life with 20170308, which appears to have gone away with 20170315. I've seen some other bizarre claims about atrocious battery life, but that's simply not been my experience with any of the LOS builds for the i9300, though they've varied.

No idea how anyone's getting 4-5 hours of screen time, but I'm delighted if my phone lasts a whole day with over an hour's screen time - not previous CM version has been any better, nor has Samsung's stock OS for me. I'm also mystified by claims that wifi is a power sucker - in my experience the exact opposite is true. Wifi is much better on the battery than mobile data, though a really poor wifi signal can be a drain. I use apps like FB, but I'm not a gamer or a music listener. I also don't really do video, which appears to have been a problem for others. No idea how much charge my phone loses overnight, as that's when I charge it.

I must once again say that LineageOS is the best thing to have happened to my i9300 in the last 4 years. Slicker and more battery-friendly than anything I've tried before.
[Galaxy S III Original Android Development] lepicane1:
Can't find where (if) this has been addressed in the latest changelog, however with this build the long press power button torch issue has been resolved for me.
[Galaxy S III Original Android Development] Neodgod:
Okay guys..

I've been thinking.

So on LOS my battery life in idle while wifi is on is very bad.

Is there anyone who has wifi Always turned on?

How is your battery life?

Mine if I turn wifi off, is great. Even mobile data is using less battery than wifi while idleing.

I don't want to complain. I want to resolve the issue.

Can any of you help?

I did test it like a week ago and it was android system that's using the energy.

By the way I have lock screen turned off. Can dat influence the idle time?

Or is there anyone who has wifi turned on all the time and has the same issue?
[Galaxy S III Original Android Development] abelenki:
it usually works correctly after reboot, but in several hours it's working incorrectly.
[Galaxy S III Original Android Development] lepicane1:
That was the case with the two previous builds for me. With this build I have been testing regularly and it still works (last reboot yesterday afternoon).

Have not installed any new apps for a while now, so the only difference is between the various builds.
[Galaxy S III Original Android Development] i9000usersa:
I keep wifi on all the time and idle battery drain is about 1-2% per hour. As mentioned by someone else, if your connection is poor it might drain. Or may be your wifi router is the problem? Also, there is an issue with the wifi with some routers that cause it to disconnect, and then when it tries to reconnect it can slow down and lock up for a while. That can be worked around by using a static ip address. I'm not sure if battery drain is related to that issue, but you might want to try using a static ip address and see if it helps.

---------- Post added at 06:18 PM ---------- Previous post was at 06:14 PM ----------

Also, have you tried using better battery stats? It may be that you have apps causing wakelocks or a lot of background activity. When you are on mobile data it may restrict activity so that you don't run out your data plan but when on wifi it may be always active.

P.s. I'm on 0301 weekly.
[Galaxy S III Original Android Development] Neodgod:
Hmm interesting.

Thank you for your answer.

On CM13 my battery life is good.

How is that possible? :D

Alright, I'll check bbs again.

Hopefully I will be able to use LOS
[Galaxy S III Original Android Development] AlecSpence:
Like I said a couple of posts above I have wifi always on, and am very happy with battery life. Generally I find battery life worse on mobile data, but probably less bad now than with previous versions of CM or stock.
[Galaxy S III Original Android Development] Drollach Gûntar:
Media player issue is still exist on the latest weekly.Its very annoying bug.

Can i use mediaserver killer or smth like that in this rom ?
[Galaxy S III Original Android Development] Logan:
To kill media server type in terminal:

su (to grant root access)

Killall cameraserver

Now you are done.
[Galaxy S III Original Android Development] minealex2244:
Killing cameraserver won't help him to stop mediaserver bugs from being annoying. Instead it will increase the chances of a random reboot to occur. Mediaserver is very sensitive, nobody should touch it untill it gets some bugfixes.

By the way, just got a Cardboard and our phone is just awesome :) The 3D graphics are somehow laggy but I ignore that. Did Samsung predicted the power of VR and Android 7.1 for years 2016 and 2017 since 2012?
[Galaxy S III Original Android Development] Klaerchen:
I compared battery life with Wi-Fi always on as opposed to only if required (my normal mode). The drain is about 2.5% per hour in both modi.

See attached image.
[Galaxy S III Original Android Development] enren:
Is it just me or cLock doesn't retain the custom location option after a reboot ?

Edit: To clarify, I'm talking about the weather widget.
[Galaxy S III Original Android Development] LuciferIII:
Still broken for me :rolleyes:
[Galaxy S III Original Android Development] Neodgod:
Thank you guys for your answers. I'll see what's going on with my device.
[Galaxy S III Original Android Development] HectorAguirre:
I am getting random reboots with the 2 latest version. I did clean flash 2 versions before, and dirty afterwards

---------- Post added at 06:57 PM ---------- Previous post was at 06:55 PM ----------

Any suggestion to avoid the RR? Thanks
[Galaxy S III Original Android Development] Samofr:
On 8-3 build, i got some rr after i was using ram-hogging apps (specially firefox). Other than that, the rom is perfect.

PS: i still didnt test the latest build for this issue.
[Galaxy S III Original Android Development] steveengr:
Just from today without any change on my phone (i have 15/03 build) when i receive a call , i hear the call sound ringing , but there is nothing on screen to answer the call.Does anyone know what may happend ?Anyone else with same problem maybe?

edit:i tried to dirty flash 15/03 build but didn't fix it
[Galaxy S III Original Android Development] AlecSpence:
I've found CM/LineageOS to be sluggish on incoming calls for ages. This was mentioned earlier in this thread with a little more explanation from minealex2244.

A quick test just now, based on listening on a separate phone calling my i9300. It's two rings before the phone starts ringing, and then another 2 before the screen turns on, and two more before the incoming call screen appears - that's 6 rings in total before I am in a position to answer the call.

Not sure if this is at all degraded from previous builds, though.
[Galaxy S III Original Android Development] johnaddams83:
Ok so it's been 2 days with 15/03. Somehow Phone & SIM problems managed to fix themselves after some SIMs exchanges, airplane mode activations and restarts. Only 2 or maybe 3 things bothers me: No vídeo call on WhatsApp; Incoming Call takes a while to appear on the phone screen, Video recording lags badly (i tested native câmera, Cinema FV-5, Snap Camera HDR, A Better Camera, etc, it lags and recovers sometimes gives a ghosting effect, also framerate is very unstable) Regarding câmera quality, it has Always been poor on CMs, but i think Camera FV-5 is doing a good job on taking decente pictures. The color balance is MUCH BETTER than stock câmera, and it enables touch to focus too.

Another thing, root. I was used to the old CM13 where we had an option on developer mode to enable root, however with LOS there's only Off and ADB Only. My câmera keeps crashing at a lower rate than on CM13 but i can't kill the câmera drivers anymore because no app recognizes the root. How can i enable the root so i can fix the câmera without rebooting? Thanks in advance.

I'm averaging 2h50 SOT, its not great but not that bad, the power saving feature makes me feel that its saving a lot of battery, i would say in stock i would average about 3h30.
[Galaxy S III Original Android Development] Neodgod:
I'm always doing clean installs.

Try installing it with full wipe. It'll probably help. :)

---------- Post added at 01:18 PM ---------- Previous post was at 01:16 PM ----------

johnaddams83

You can find a flashable root activator file on the LOS website. It's also mentioned in the first post. :)
[Galaxy S III Original Android Development] LuciferIII:
Omg what the hell,i cant reply ,xda labs glitched my reply twice and just displays half of the quote...

Well, Johanddams to get root.

Go to official lineage downloads,and download root addon zip. Flash,ignore any error,enable root in dev settings as always.

Use root to fix cameraserver.
[Galaxy S III Original Android Development] minealex2244:
Can you tell us more details? E.g. GApps, kernel etc. Here is a video which explains how magically fix RRs: https://youtu.be/JmvCpR45LKA

Just joking :) Do not use battery performance profile intensively, uninstall unused apps, do not install too many mods and be sure to keep your system as clean as possible. And remember that every S3 is unique (mine is made in 2015 and maybe yours in 2013 so it is somehow different than mines in terms of hardware).

---------- Post added at 02:39 PM ---------- Previous post was at 02:36 PM ----------

Never forget that you have 1/3 chances to get a random reboot by killing cameraserver. It is very sensitive. Same for mediaserver.
[Galaxy S III Original Android Development] Neodgod:
same lol

---------- Post added at 01:44 PM ---------- Previous post was at 01:41 PM ----------

My board is from 2015 aswell :D
[Galaxy S III Original Android Development] johnaddams83:
Thanks guys i tried to flash the ZIP (root) but it gave me an error never bothered to check again HOWEVER i just entered the menu again and had more options like Apps only. So it worked even when said if failed on flashing, curious! Thanks anyway!
[Galaxy S III Original Android Development] MARCOSOFT:
Bluetooth issue!

I installed the latest version (from 4.3 full format to 7.1.1) and the calls made by bluetooth have a lot of noise, even being totally imperceptible!

Anyone with this problem?
[Galaxy S III Original Android Development] andrescm:
Will try this afternoon. Music streaming works fine.
[Galaxy S III Original Android Development] Hesham Sleem:
Hello...

can someone help me to odex this rom ?
[Galaxy S III Original Android Development] MARCOSOFT:
Hello,

I also have this problem (latest version)! Have you found a solution?

Is it solved with any version?

Thanks.
[Galaxy S III Original Android Development] ubuntero:
The issue is finally resolved by flashing modem as described in post:

http://xdaforums.com/galaxy-s3/orig-development/rom-cyanogenmod-13-nightlies-i9300-t3272811/post70222395#post70222395

Additionally, there is need for "WB-AMR SETTINGS" to be set OFF to use bluetooth without voice distortion or use only 2G.
[Galaxy S III Original Android Development] MARCOSOFT:
What version of Lineage are you using?

In my case I am using the latest lineage-14.1-20170315-nightly-i9300-signed version and after installing Spirit2 from Playstore, it informs that the Kernel does not have FM radio function.

In other words, the application starts, but the kernel does not support FM radio!

What version are you using or have you changed the kernel?

Thank you.
[Galaxy S III Original Android Development] galen2:
Sorry for ot, anyone have XXUGMK6 modem on zip to install via twrp?, i use XXUGNA8 and i have robotic sound on bt calls, my girlfriend said "gregorian songs" lol, i want to try if this solve the problem, normal calls works perfect.
[Galaxy S III Original Android Development] Ashraf Iraqian:
no problem like this in the ROM

i guess you are used new cover "safe the screen from crashing" and placed on the Sensor .. or maybe you need to clean it.

regards
[Galaxy S III Original Android Development] LKHN:
Please read F.A.Q. section in this thread :)

Robotic voice during calls?

Try using the I9300XXUGMK6 modem. Instructions are here.
[Galaxy S III Original Android Development] xEmre66:
Go to Settings > Apps > "Settings" button at right top hand corner > there, look if you have set a standard app for phone calls. If not, then set it to Telephone App and your problem will be fixed.

I had the same problem and I fixed it thanks to other XDA members here. :laugh:
[Galaxy S III Original Android Development] MARCOSOFT:
FM RADIO

I am using the latest lineage-14.1-20170315-nightly-i9300 and after installing Spirit2 from Playstore, it informs that the Kernel does not have FM radio function.

In other words, the application starts, but the kernel does not support FM radio!

Does anyone have the FM radio working?

Thank you.
[Galaxy S III Original Android Development] mohand06:
I'm a long time user of Spirit2 FM radio on my I9300, on stock as well as on any custom rom CM or LineageOS and it always worked fine (the best true radio FM app out there!) You're not having an issue with the kernel, maybe you should change your firmware or clean flash another build. I'm keeping that old S3 only for that radio FM!
[Galaxy S III Original Android Development] MARCOSOFT:
What version of LineageOS do you have installed and the functional Spirit2 (Radio FM)?
[Galaxy S III Original Android Development] minealex2244:
I'm using Spirit FM for a log time (Spirit2) and everything is working. I can even listen FM without any headset :). I'm using Spirit2 V. 2015_04_14.6. It works for every Lineage build.
[Galaxy S III Original Android Development] mohand06:
Spirit2 V. 2014_11_12

Already said works on all custom roms. Now, I'm on stock 4.3 updated to XXUGPE1 (latest 2016)
[Galaxy S III Original Android Development] kbarni:
SpiritFM needs root access to access the radio module. So you must flash the SU addon and grant SpiritFM superuser rights, when it asks.

I used this app without problems with the last 4 weeklys of LOS, with stock kernel and Boeffla.
[Galaxy S III Original Android Development] lincons:
I use it starting from January .GPS is not working
[Galaxy S III Original Android Development] Simon_29:
It is. Try to tighten the screws of the device.
[Galaxy S III Original Android Development] Ashraf Iraqian:
stream app fixed in latest update of our ROM :) AND WORKING VERY NICE

Thanks For this Amazing ROM :D :highfive:
[Galaxy S III Original Android Development] Ashraf Iraqian:
SS
[Galaxy S III Original Android Development] Premindia87:
For some reason the viper4android is getting killed when screen is off. Music turns off and gets to normal playing mode without viper when screen its off. I tweaked all the settings in the battery optimization. Kept viper in notification still its getting killed. It used to work properly in cm14.1 but lineage its not. I am an audiophile could not think of OS without viper4android.
[Galaxy S III Original Android Development] Klaerchen:
Crash in Bluetooth Scan

Hi [MENTION=5405215]forkbomb444[/MENTION]

the current lineageos for i9300 (all commits until March 18th) has a problem with scanning for new Bluetooth devices.

If I start scanning with no other devices ready for pairing in the neighborhood, then there is no problem, i.e. after some seconds the scanning finishes without results. This can be reiterated without trouble.

If however a pairable device (tried with headset as well as Windows PC) is available, the device is not responding, the little "turning wheel" continues rotating, however after a minute or so, the phone reboots (warm reboot).

This sequence is reproducible. A logcat that starts with a scan of the first type and afterwards with a scan of the second type described, followed by the crash of the system is attached and a last_kmesg.

The lineage build with all commits up to March 8th worked correctly with Bluetooth scans. So it should be a commit in between. Do you have an idea?

Regards,

Klaerchen
[Galaxy S III Original Android Development] kabatronix:
Bluetooth issue confirmed on 15.03 build

reproducable on two independent devices running latest 15.03 weekly.

Reboot is quite brutal, reseting i.e. ringtone to default

No Bluetooth issues with 08.03 build

kabatronix :)
[Galaxy S III Original Android Development] lincons:
working on another rom. (hyper rom )

It opens Google maps and takes it to high accuracy and waits to find its position. (Lineage Os)
[Galaxy S III Original Android Development] Premindia87:
When screen off viper4android is getting killed did any one noticed the issue.
[Galaxy S III Original Android Development] PRO>KOMP.<:
I recorded video testing random TOP 5 games on Galaxy S3 with LineageOS 14.1

[YOUTUBE]eCVz8SAY7Ss[/YOUTUBE]

https://www.youtube.com/watch?v=eCVz8SAY7Ss

All games works good, maybe Asphalt 8: Airborne little laggy but its ok :).
[Galaxy S III Original Android Development] stewazy:
Can someone give me the last stable build of CyanogenMod 13 I wanna go back to it and wait for a bit before trying lineage is again. Root detection does not work properly, it gives me only ADB. Also YouTube app froze on me for a couple of times. I had to reboot the phone. Thanks in advance. Also battery drains way too fast, I have everything on greenify except Gmail.
[Galaxy S III Original Android Development] Logan:
Who missed touchwiz style?!

Here is some screenshots of nova launcher with DreamUX leaked icons (S8) and some widgets, all information will be added soon.

(Screenshots from my i9300)