yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] notstpaul:
One weird thing for me is now the biggest battery drainer is NoRoot Firewall. It's been like that since CM 14. Strange.

---------- Post added at 12:37 PM ---------- Previous post was at 12:34 PM ----------

That seems fine. Privacy Guard is obviously active and some permissions haven't been granted to Play Store. You'll find it in the settings menu. Or you can change the permissions from the app info settings.
[Galaxy S III Original Android Development] Ashraf Iraqian:
fixed when i untucked the play store app in privacy guard :)

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

Hi dear dev.

can i report some important Apps. bug ?

ex: Kinemaster video editor app + Facebook messenger app & about battery drain!

regards
[Galaxy S III Original Android Development] chrzaszczwtrzcinie:
I assume you have twrp, right? So if someone has your phone in their hands they can remove the screen lock from the recovery really easily.
[Galaxy S III Original Android Development] barthezz_x:
if i want to access sd-card file manager says "need root access", why?
[Galaxy S III Original Android Development] qs666:
I have the same problem
[Galaxy S III Original Android Development] notstpaul:
Have you tried giving it root access?
[Galaxy S III Original Android Development] barthezz_x:
no because this (simple action) should be functioning without root, don't you think so
[Galaxy S III Original Android Development] noratroll:
It's about write access. Without root permissions granted the access is limited. I cannot say to which extend it is limited since I always work under root conditions.
[Galaxy S III Original Android Development] baltics:
When I was running it without root, I could use the ROM file manager to access the SD card and transfer files to and from internal storage.
[Galaxy S III Original Android Development] LuciferIII:
I have no school for a week so i don't use my phone that much. But here are my battery stats. I don't know what that big gab betwen is but its probably because i did some stuff here and there and restarted my phone. I didn't charge it even tho it looks like cause sometimes the battery just recharges itself as you all know.

My battery is some chinese 2850mAh. Greenify + Forcedoze + Airplane mode (cause i never get called) + Boeffla kernel + Swift Black substratum theme ;)

Here take a look
[Galaxy S III Original Android Development] joamonster:
Hey guys,

Is your mobile data working on this ROM? I had no problems with earlier CM builds (13 etc). Is it just me?

Thanks!
[Galaxy S III Original Android Development] LuciferIII:
Worka fine,did you configure your APN settings?
[Galaxy S III Original Android Development] joamonster:
The APN settings seems configured. But the phone does not connect to mobile data at all! I tried changing preferred connection to 2G, 3G. No luck.

Any ideas on debugging?

Thanks!
[Galaxy S III Original Android Development] minealex2244:
No need to give up :) I managed to install Viper4Android and I use it since first unofficial builds :D No problems but it depends on the installation steps you made. I'm using an old version of Viper and it is more stable.
[Galaxy S III Original Android Development] dana.marivani:
Hi guys

I feel weak activity in the Community:(,This means that all the problems are solved Ram that no one is talking about it will not.:rolleyes::rolleyes:
[Galaxy S III Original Android Development] LuciferIII:
Yeah pretty much. Hwc is left and maybe getting the sim contacts working again. Anything else i dunno. This ROM is already the best you can find out there.

So what will be next?

Well,i am hungry, delicious Oreo would be an option ;)
[Galaxy S III Original Android Development] Neodgod:
Well great System.

At the same time I guess eventho it's the best it can be better.

HW will be a huge thing.

Also okay, features is one thing.

But I still think performance and battery life can be improved.

Let me make this clear. I am not complaining.

It's fine now.

I just mean there's always room for the better :D
[Galaxy S III Original Android Development] b3nmore:
Anybody? I did a clean flash but still no fix on glonass. There's a bugbash for exactly that problem on the S5 (BUGBASH-383). So maybe the S3 is affected too, worth checking out imo.
[Galaxy S III Original Android Development] Klaerchen:
I see the same problem. There are 4 or 5 Glonass satellites visible with a strong signal, however they are not included in the fix. Tested with own build from April 15th.
[Galaxy S III Original Android Development] minealex2244:
Finally we get it: 7.1.2 https://review.lineageos.org/#/c/167810/
[Galaxy S III Original Android Development] xEmre66:
Niceeee!
[Galaxy S III Original Android Development] tdcfpp:
No
[Galaxy S III Original Android Development] gore2kill4:
wrong thread
[Galaxy S III Original Android Development] Ashley david:
Guys was Hwc fixed on cm 13??
[Galaxy S III Original Android Development] zarere:
No
[Galaxy S III Original Android Development] Scorpionea:
It is fixed in cm12.1
[Galaxy S III Original Android Development] Ashley david:
Thank you
[Galaxy S III Original Android Development] dana.marivani:
We got the news very happy:good:

After that we will see next update?
[Galaxy S III Original Android Development] LuciferIII:
Using the "Thank you" button is enough imo. :good:
[Galaxy S III Original Android Development] minealex2244:
I'm not sure. It isn't included for our device yet. It will be included soon.

---------- Post added at 04:01 PM ---------- Previous post was at 03:59 PM ----------

That's true :D Every thanks button press means a new iPhone is "tested" by TechRax.
[Galaxy S III Original Android Development] LuciferIII:
I think i get the joke,if it is that yt-er :D
[Galaxy S III Original Android Development] dana.marivani:
[MENTION=6371648]minealex2244[/MENTION]
[Galaxy S III Original Android Development] minealex2244:
Q-U-O-T-E=dana.marivani;71902357]

I see that for HwComposer we need to wait until Nameless ROM will get it then we will get the newly fixed HwComposer for LOS 14.1.
[Galaxy S III Original Android Development] zarere:
Where do you see that?
[Galaxy S III Original Android Development] xEmre66:
review.lineageos.org (search for Simon Shields) and see all commits that are related to HWC)
[Galaxy S III Original Android Development] vuut:
Root add-on: https://download.lineageos.org/extras

we are choose which one:??????

su (arm)

su (arm64)

su (x86) for I9300
[Galaxy S III Original Android Development] simono_pl:
@up su (arm)

Wysłane z mojego Redmi Note 3 przy użyciu Tapatalka
[Galaxy S III Original Android Development] LuciferIII:
Use Arm
[Galaxy S III Original Android Development] minealex2244:
http://review.lineageos.org then search Simon Shields and go to next page 2 times. You will see a series of his commits, just click on "android_hardware_samsung" and you will get all the commits :)

---------- Post added at 12:04 PM ---------- Previous post was at 11:59 AM ----------

Kernel is running out of memory without any reason. Looking at last_kmsg can show me that it is panicking and rebooting due to inability to free the RAM allocated memory to kernel (cannot kill other processes). I didn't intensively​ used my phone but our kernel gets only a few MBs to run which is not enough in stressful situations.
[Galaxy S III Original Android Development] dana.marivani:
It is strange to speak about fingerprints letters in the next update:eek:

Did such a thing was to be true:rolleyes:

https://review.lineageos.org/#/c/168789
[Galaxy S III Original Android Development] LuciferIII:
Where can i download fingerprint sensor? :silly:

This is probably for devices with fingerprint sensors,and i don't see any connections to our device,nor is it in our changelog,sowhy do you post this here?

Btw i am not trying to get offensive or anything,i am asking politely.
[Galaxy S III Original Android Development] dana.marivani:
Not insult not require polite I'd like to say our experience, ideas:good:

I'm curious, like you say you is not right for our device

If it is true the Impossible I thought it would be better to control the TV.

You will be surprised that our next list:cool:
[Galaxy S III Original Android Development] minealex2244:
I'm looking for a way to fix the battery drain. Firstly, I inspected the battery stats and I saw that the mobile network, LOS system, screen and Chrome are using more than 14% and then another app is coming with only 7% so we should concentrate on those I mentioned.

I will write a complete guide only when I'll finish my research. For now just do this: Go to Settings >

Apps > Google Play Services > Permissions and disable body sensors which are needed for Google Fit. This won't give a big effect but it's the first step.

P.S. It will add around 30-40 minutes to the battery life. It breaks Google Camera.

---------- Post added at 08:45 PM ---------- Previous post was at 08:30 PM ----------

In addition to this, putting your phone into the airplane mode should help. Concerned about other networking features which will be shut down? As an alternative, go to Dialer, type *#*#4636#*#* then go to Phone information and disable "cell radio signal strength". That will just turn off the radio and you won't receive calls or messages.

---------- Post added at 08:51 PM ---------- Previous post was at 08:45 PM ----------

We fixed 2/4 battery drainers. To fix the screen drainage: disable screen rotation and make the screen brightness to be the minimum possible. How? Settings > Display > LiveDisplay and then Calibrate on-screen colors. Calibrate all colors to 10% to get the minimum brightness possible for our screen.

---------- Post added at 09:00 PM ---------- Previous post was at 08:51 PM ----------

Using Chrome to surf on the surface web? Chrome is using RAM and battery a lot so the fix for it is just to not abuse by using it or use Puffin Browser instead (integrated Flash, mouse and data savings).

The last step would be to get rid of those apps you are no longer using. Every app is running in background (just see any "App info", randomly).

Bluetooth is also a good source of battery drain and GPS too.
[Galaxy S III Original Android Development] LuciferIII:
YOU! Yeah you! TAKE MY THANKS!
[Galaxy S III Original Android Development] dana.marivani:
Thanks for the great guide It was very informative
[Galaxy S III Original Android Development] Simon_29:
I cant agree with your last point. Some apps are running in the background for delivering notifications or something different and those drain a tiny (or dumb apps much) battery. Others or just cached in the ram for faster loading times which is fine (if they are not used opened they probably arent i think). All apps have cache on the internal storage to speed up the loading times. Also in this state they are marked as running which is not really the truth.

To see which apps are running in the background i would check out the active apps (or something similiar) in the developer settings.
[Galaxy S III Original Android Development] minealex2244:
1+1 is 2 (what?). If you have more of these "tiny" drainers you will finally get some drainage from those apps. If you have only a few of them then you are good to go (only by uninstalling unnecessary apps ;) ).

And here is an interesting thing: RAM memory. Everyone knows that every device is working using electricity. This electricity is used to write to the temporary memory (RAM). If you write less to it you conserve battery (not so much but combined with another battery drain "fix" would have some effect).

We need to keep RAM as clean as possible.

---------- Post added at 06:51 AM ---------- Previous post was at 06:45 AM ----------

Not yet complete. Looking in battery stats will tell you that LOS system is draining battery so much. If we don't use Chrome, then we understand that our screen drainage is unstoppable and we choose to use mobile network, the last culprit is LOS system. I want to see which services can be stopped or hibernated. I didn't use Greenify but I'm planning to force Doze Mode. LOS system is syncing too much and we need to fix that. ;)
[Galaxy S III Original Android Development] Simon_29:
The battery usage of the ram is not much compared to other components. And free ram = bad ram
[Galaxy S III Original Android Development] LuciferIII:
Unused RAM = Wasted RAM
[Galaxy S III Original Android Development] dana.marivani:
Certified Good

A new update is 2017-04-19
[Galaxy S III Original Android Development] Egli.Kasa:
Should i clean flash this build because its 7.1.2 ? Or just update from updater as usual
[Galaxy S III Original Android Development] dana.marivani:
Flash Cleaning to do was faster devices,The normal mode
[Galaxy S III Original Android Development] Egli.Kasa:
That wasnt very clear [emoji102]
[Galaxy S III Original Android Development] dana.marivani:
:D:D:D:D:D:D:D:D

That you experience after you know it the way you do
[Galaxy S III Original Android Development] LuciferIII:
Just update as usual
[Galaxy S III Original Android Development] Samofr:
Please dev update the thread title to 7.1.2.

Thank you :)
[Galaxy S III Original Android Development] minealex2244:
As I said: freeing RAM won't give a big effect but it is something :). Having more free RAM is better than having it full. More RAM means more space for kernel and system but full means lag and instability.

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

I see that you are Italian. I wish I could understand all of your posts but your​ English needs some improvements (not a problem for you :D). Do you mean that a clean flash is required only if you want a faster device? If yes then I agree with you. Anyways, this is my daily driver, no clean flash :)

---------- Post added at 02:18 PM ---------- Previous post was at 01:38 PM ----------

For the new build with 7.1.2, dirty flash is OK.
[Galaxy S III Original Android Development] dana.marivani:
I'm sorry you and other friends for my English writing well in fact I am Iranian but you have poor English, however, the great excuse yourself:(:(

But in general, I do not experience as much as you just suggested I:p
[Galaxy S III Original Android Development] minealex2244:
Sorry my bad :D That "marivani" sounds so Italian but it is Iranian.
[Galaxy S III Original Android Development] dana.marivani:
:laugh:

segregate:o

I'm living there marivan-You can take a look at the map iran,kurdestan,marivan

Here is the world's largest fresh water

In principle I am Kurdish, I lived in Iran
[Galaxy S III Original Android Development] Scorpionea:
Clean flashed 0419 aka 7.1.2 and no issue so far (last few weeks I've been on cm11 so it's good to be back on nougat again xD )

I like new gallery app ,would be happier with snap then old camera but oh well
[Galaxy S III Original Android Development] LuciferIII:
I think there was a download here somewhere.

You can look find it for sure.
[Galaxy S III Original Android Development] johnaddams83:
Old snap doesnt work in nougat. Takes black pictures. I tried myself
[Galaxy S III Original Android Development] ahmed95magdi:
Is the latest version stable enough to be a daily driver?

and if not, what is the most stable version released till date?, thanks
[Galaxy S III Original Android Development] LuciferIII:
Yes its stable enough.
[Galaxy S III Original Android Development] DiamondPol:
After latest update my google camera stopped working :/ Any solutions for that?
[Galaxy S III Original Android Development] DiamondPol:
Nope, it doesn't help :/
[Galaxy S III Original Android Development] minealex2244:
Camera Restarter is not perfectly compatible with Android 7.1 :/

---------- Post added at 09:19 AM ---------- Previous post was at 09:16 AM ----------

Please tell us more details and send a screenshot. I want to know whether it's a temporary problem or a persistent one.

Try

su
killall cameraserver

This is sensitive and in some cases it will give a reboot so be prepared. If it's persistent then clear data and reboot.

Which one is better? Greenify or ForceDoze?

To continue my battery drain fix guide here is the last important thing I want to cover: Doze. We need to reduce the frequency of the syncing processes and Greenify was the first candidate. I got almost no effect. Then I used ForceDoze and it works way better than Greenify. We increased our battery life (using the entire guide) while using the phone and in stand-by.

Is battery drain fixable? Yes but why? Because it is caused​ by ignorance. Google added a lot of useless stuff which is draining battery faster than in 6.0 and we need to remove or disable these stuff.
[Galaxy S III Original Android Development] DiamondPol:
It just crushes, tries to load and it gets back to home screen (in less than a second). The "su | killall cameraserver" didn't helped :/
[Galaxy S III Original Android Development] minealex2244:
Try cleaning data. My Google Camera (v 2.7.0.10) is working.
[Galaxy S III Original Android Development] LuciferIII:
I think 2.7 never worked for me,but i tried 2.5 and it worked but that was like 2 moths ago. And no,it was not the camera server bugging.
[Galaxy S III Original Android Development] dana.marivani:
Mine is working fine version 2.7.00.8

But if the Permissions and disable body sensors Is google camera does not work:good:
[Galaxy S III Original Android Development] g104:
[MENTION=6371648]minealex2244[/MENTION] FYI, the Camera Restarter works on 7.1.x
[Galaxy S III Original Android Development] minealex2244:
Not really efficient for me :'( I'll try again but it didn't had any good effect when I tested it.
[Galaxy S III Original Android Development] Fatih666:
Proximity sensor problem. The screen does not open during a call.
[Galaxy S III Original Android Development] minealex2244:
It works for me. Try rebooting your device.
[Galaxy S III Original Android Development] Fatih666:
I have a screen saver. Proximity setting or sensor off setting may work. for me
[Galaxy S III Original Android Development] dev.xda:
"Camera blocked" error happened with all apps i tried:

a better camera

camera fv5

camera zoom

kamera

google kamera (2.5.052)

open camera

then i disabled for every camera app "allow running in background" via privacy guard.

now i can use these apps without blocking the cam.

just a workaround ;)

[MENTION=507649]devs[/MENTION]:

my i9300 with LOS without gapps and approx. 100 apps is running nearly perfect. faster than orig sumsang stuff. really fine job done!

but i am no socalled soc media user - no , wa, tw etc. - just k9 & conversations.

when warranty for my i9305 ends i will put LOS in it.

reading both groups i dont understand the issues of i9305. is the diff in HW more than mem & radio?

keep going on!
[Galaxy S III Original Android Development] Fatih666:
please i want proximity sensor repair fix , how can i do ?
[Galaxy S III Original Android Development] ackzsel:
I think you need to flash another ROM first to rule out any hardware issues.
[Galaxy S III Original Android Development] xEmre66:
I think you have hardware issues as [MENTION=4784361]ackzsel[/MENTION] says.
[Galaxy S III Original Android Development] Fatih666:
I have boeffla kernel and modem fix for imei problem. I do not know how the proximity sensor is broken. The distance is 0cm everywhere. If I can fix it with ADB, it is getting corrupted again when I restart it. How do I flash the original proximity sensor files? I organized without breaking ROM. How can we resolve this, friends?
[Galaxy S III Original Android Development] minealex2244:
The proximity sensor has nothing to do with the modem so you can keep the IMEI fix. I wonder which is the physical condition of your phone. Maybe your proximity sensor got broken by something which is blocking it (maybe screen protector).
[Galaxy S III Original Android Development] Fatih666:
When I search from the search screen and write the echo 1 > /sys/class/sensors/proximity_sensor/prox_cal

command with adb when the screen is black, the problem is solved. But every time I restart, my settings become corrupted, I have to do the same things again.
[Galaxy S III Original Android Development] minealex2244:
For me that value is 0,15. But as I said: maybe there is something which is blocking the sensor to see the distance. This happened to my father because of a plastic screen protector. He had the exact same problem.
[Galaxy S III Original Android Development] dana.marivani:
Hi guys

Why do you think [MHL To HDMI Media Adaptor] Not supported??

help me..

Tnx
[Galaxy S III Original Android Development] Simon_29:
It needs Samsung drivers that are only available in sammy based roms.

Also i tested it and it lets the device crash.
[Galaxy S III Original Android Development] rapain:
anyone notice charging rate,, problem? it seems when you charge it,, is not increasing the amount of power,,, but when you turn off is already has it amount of power...
[Galaxy S III Original Android Development] Ashley david:
Yes mine also is charging really slow
[Galaxy S III Original Android Development] Shonky*:
Anyone got NFC working on the i9300? I've been unable to get NFC reading of MIFARE Classic 1k since CM11 / Kitkat. CM13 had the same problem. Problem is this phone in particular I want to use for NFC reads.

Running latest LineageOS 14.1 20170419 nightly with Google Apps pico and just NFC Tools from the app store. Everything else as completely stock from a fresh install with all partitions wiped. Everything else seems to run OK.

It appears to have started back sometime after CM11 but hard to say where exactly it stopped working.

It does recognise the card is there, but can't read even the UID of it. CM11 on the exact same hardware works fine and I can go backwards and forwards (completely wiping of course).
[Galaxy S III Original Android Development] Fatih666:
It writes a value of 0.15. I am sure this is not hardware problem. It's definitely a software problem. But I do not know why. echo 1 > /sys/class/sensors/proximity_sensor/prox_cal is running. Just every time I need to do it again after the restart.
[Galaxy S III Original Android Development] tdcfpp:
It requires more than a year reverse-engineering to get it working. Exynos7 is old now, so there's no much time for exynos4.
[Galaxy S III Original Android Development] minealex2244:
That is just a super temporary value. Maybe in-call it gets stuck at 0 pretending that the phone is near your head and the screen won't turn off.

You need to try another modem version. Try the original one (the first ever modem you had).

Maybe this version is made for another sensor or for the same sensor but another revision.
[Galaxy S III Original Android Development] dana.marivani:
I wonder Official Android 4.3 Jelly Bean OTA I used my side support

But I could not find a way for him:(

---------- Post added at 15:18 ---------- Previous post was at 15:18 ----------

Yes that's right, But I Exynos 4412 Quad I could of course with Official Android 4.3 Jelly Bean OTA I used

But have you ever could with this custom ROMs 7.... contact up, if I plug it immediately after restart

The purpose of the questions that I asked.We ask the community to find her way

Thanks to all
[Galaxy S III Original Android Development] minealex2244:
Did forkbomb added fast charging? :D My phone gets charged in 45 minutes (full) and rarely in 1 hour and 20 minutes.
[Galaxy S III Original Android Development] Pasindu88:
lmao we have fast charging now :laugh:. That should be false battery detail showing in battery menu. I had this problem few times in the past. Turn off phone & remove battery for 10 mins. Then add it back & turn on phone. It should fix this fast charging issue :D.

Edit:- I still don't understand why Lineage OS team delaying OMS support. All other roms based on LOS already have OMS support
[Galaxy S III Original Android Development] xEmre66:
Yes I noticed that as well it's actually charging pretty fast. It even charges fast with an 0.7A charger.. but when I use my S7 Fast Charging adapter it charges in 38min (full, from 24% to 100%)
[Galaxy S III Original Android Development] minealex2244:
OMS needs to be very stable.

Also the battery drainage is normal even with "fast charging". :)