yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] mbdroidsony:
*update*

other people have also mentioned root access failing after official update due to using cwm recovery to install update instead of twrp recovery. I was also using cwm to install update. After changing recovery to twrp i can also confirm that root access is now working with official LineageOS 14.1 update. :good:
[Galaxy S III Original Android Development] baltics:
My device is downloading this morning's update using the built in 'updater', it can be installed automatically.

Edit

It is a 5 minute+ boot-up.

It is still Rooted after the install..
[Galaxy S III Original Android Development] baltics:
Having successfully installed the update, and subsequently rebooted, the installer App shows
[Galaxy S III Original Android Development] stefan.slavici:
Is there any changelog available for this update?

I installed it too but don't know what's changed.
[Galaxy S III Original Android Development] zarere:
https://www.cmxlog.com/14.1/i9300/
[Galaxy S III Original Android Development] ripko:
Doesn't work for me. At the end of the download I get an error message and the installation does not start.
[Galaxy S III Original Android Development] qs666:
root vanished after installation
[Galaxy S III Original Android Development] Bometdebanjo:
I also downloaded this mornings update through installer function on my device, all went very smooth and still have root access. Screen recorder changed into recorder with a new "brown"!! (Wtf) logo. Only thing that caught my attention was that i still see a " Cyanogenmodupdater" in my statusbar. I expected "LineageUpdater" I thought rebranding was done by now?

---------- Post added at 11:51 AM ---------- Previous post was at 11:48 AM ----------

You probably used a different root file to get root access?
[Galaxy S III Original Android Development] baltics:
Using TWRP 3.0.2-2 ?

The Lineage root?

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

The one thing I cannot find, is the folder where the installer app stores the ROM update.
[Galaxy S III Original Android Development] qs666:
--

---------- Post added at 12:08 PM ---------- Previous post was at 12:06 PM ----------

SuperSU
[Galaxy S III Original Android Development] baltics:
Chainfire's SuperSu is systemless and needs to be reinstalled whenever the ROM is reflashed, updated or changed.

Edit

But you can only reinstall it after you have successfully installed and rebooted the ROM. This is why the Lineage su is better. It does not need to be reinstalled.
[Galaxy S III Original Android Development] zarere:
Here it is
[Galaxy S III Original Android Development] dana.marivani:
No problem. It's weird that it will be charged soon. Without using the kernel boeffla, only a particle is discharged from the usual past, but thanks for the response.
[Galaxy S III Original Android Development] Noobkid77:
Anyone experiencing lag on fb lite at times and WhatsApp on video updates as well as WhatsApp hanging at times ??
[Galaxy S III Original Android Development] galen2:
Seems next snapshot will come with fixed miracast
[Galaxy S III Original Android Development] Mirajoo7:
Time for snapshot build?
[Galaxy S III Original Android Development] renzreyes21:
Is there a difference between power saving profile and that extreme battery saving mode ? *the one that turns status bar red*

Most of users suggest using the power saving than that extreme mode..
[Galaxy S III Original Android Development] JeOZ:
Is there a solution for the time that takes the incall ui to be shown? It takes long time
[Galaxy S III Original Android Development] LuciferIII:
If someone could explain what exactly they both change :fingers-crossed:
[Galaxy S III Original Android Development] MiguelDJM21:
Videollamadas whatsapp

Tengo un problema grande y es que desde que uso lineage os no puedo hacer video llamadas de whatsapp, mi camara sale en negro y las personas no me pueden ver, he intentado todo y no se como resolverlo, AYUDAA:crying::crying:
[Galaxy S III Original Android Development] Nypan sr:
Rule #4. Use the English language.
[Galaxy S III Original Android Development] xEmre66:
I think he means that video calls don't work on whatsapp and should be fixed. :)

I do not want it for myself, because I sold my S3. Just wanna help him out :)

Regards,

xEmre66
[Galaxy S III Original Android Development] leonardalps:
Hi Guys, whenever i install lineageos on my s3 i9300 it gives me an error saying that sim card not detected....can someone help?

on my first boot it gives me this error...even though my sim card is inserted in the phone.....on the official jelly bean rom this does not happen.....

pls help
[Galaxy S III Original Android Development] Elton47:
I can.

You can enable them both for maximum saving.

Power save Mode: Decreases CPU usage to only 2 out of 4 cores. It does NOT affect getting notifications or background processes.

Battery Saver: *the one that turns the status bar red :D* DOES affect background processes, you will still be able to get notifications but rarely. It also disables Live Display feature if ON.

I always let my phone in Power saving Mode.

I didn't notice any lags or freezes. I never used to get 3 to 4 SoT, but since this setting was implemented, I always get at least 3 hours SoT, compared to a 2 hours one with all other Roms I tried in the past, including marshmallow and early CM14.1.

-Hope I helped!
[Galaxy S III Original Android Development] minealex2244:
I don't know Spanish but I see that you have problems with WhatsApp. This is due to our broken HwComposer. You need to wait until it will get fixed.

Also you should talk in English here so you don't break any rules.
[Galaxy S III Original Android Development] renzreyes21:
Does our device supports /have that "Seamless (A/B) System Update" ??
[Galaxy S III Original Android Development] Tech0308:
Sadly not
[Galaxy S III Original Android Development] Mirajoo7:
Hai guys is there any way to dual boot the stock 4.3 and lineageos?

So that we can use 4.3 and lineage until the HWC fixed
[Galaxy S III Original Android Development] nsaini121:
can anyone explain me what causing the WhatsApp video calling issue?? I know its something related to HWC but I want to know it fully.

can any one help?
[Galaxy S III Original Android Development] minealex2244:
Try DualBoot Patcher.
[Galaxy S III Original Android Development] Samofr:
+1
[Galaxy S III Original Android Development] Ashraf Iraqian:
deleted

[wrong post]
[Galaxy S III Original Android Development] Simon_29:
It isn't compatible with the S3.
[Galaxy S III Original Android Development] Ashraf Iraqian:
Oops!

You are right

i didn't checked it before.

sorry for the this wrong post i thought i will help him.

regards
[Galaxy S III Original Android Development] jani89:
I had the same problem , trying to restore on wifi doest worked for me , i have used cellular data and everything was OK !
[Galaxy S III Original Android Development] Noobkid77:
I recommend you guys use Titanium Backup as the wifi method is sketchy at best but Titanium Backup app restores backups in original state ALL the time
[Galaxy S III Original Android Development] zarere:
Any updates related to

https://xdaforums.com/showpost.php?p=71774792&postcount=1713

BTW the new nightly is here https://mirrorbits.lineageos.org/full/i9300/20170628/lineage-14.1-20170628-nightly-i9300-signed.zip
[Galaxy S III Original Android Development] lollo.21:
Hello to everyone, with today's day build of day 28 has been fixed miracast, has a problem, so lag then disconnect! to you too?
[Galaxy S III Original Android Development] hasanfares:
Does anybody know about screenshot ,how to make it work on lineage what key combination can't seem to make it work , i thought i read in a while back in the thread that it is back to our rom ,am i wrong
[Galaxy S III Original Android Development] Ashley david:
You can make a short cut of screen shot in your power menu in button option in settings
[Galaxy S III Original Android Development] Kippy51:
Or 'volume down' + 'power button' at the same time.

Sent from one of my Sammy devices.
[Galaxy S III Original Android Development] hasanfares:
Thanks it worked
[Galaxy S III Original Android Development] g104:
If my power button is spoiled, any alternative method? I really need the screenshot tiles to be added.

FYI, I tried various apps gave me nothing but trouble.
[Galaxy S III Original Android Development] LuciferIII:
Maybe an app that triggers the power button?
[Galaxy S III Original Android Development] hasanfares:
Try putting the icon on your homescreen or just download an app that has a floating widget
[Galaxy S III Original Android Development] g104:
Tell me which apps can take an instant screenshot? I can't even screenshot properly on my Clash of Clans & unable to hide the navigation bar, quick setting, etc.

---------- Post added at 01:34 AM ---------- Previous post was at 01:32 AM ----------

What icon? If I want to screenshot conversation, during video calls, etc.
[Galaxy S III Original Android Development] minealex2244:
I already told him that he can use DualBoot Patcher which is compatible with our device. I'm not sure if it is fully working but someone should try it. I tried and I was unable to boot into the other ROM (because I was on LOS and the kernel is not supporting dual booting) but it should be fine with stock 4.3.
[Galaxy S III Original Android Development] rocciacoraggiosa45:
hwc news?
[Galaxy S III Original Android Development] minealex2244:
Use this app to get all the buttons including the power button: https://play.google.com/store/apps/details?id=com.smart.swkey.nonroot

---------- Post added at 07:29 PM ---------- Previous post was at 07:21 PM ----------

Simon is hard working on it (https://review.lineageos.org/#/q/owner:simon%40lineageos.org+status:open). It is the hardest thing to fix in this ROM as he needs to adapt the code for our device (porting from Exynos7 to Exynos4), then he needs to work with different kernel drivers and with some system libs.

I think that his commits are now unstable and if we build while repo picking them we would get a bootloop or maybe at least more glitches. Nobody should expect perfection, it is a port :) so bugs might appear.

Thank you for this information. It looks like they finally fixed the EAP authentication error which gave us the screen mirroring bug.
[Galaxy S III Original Android Development] leonardalps:
guys!! pls help i keep getting no sim card detected error on my phone. can anyone help me fix this
[Galaxy S III Original Android Development] Simon_29:
Clean your sim card and your sim card port.

Restore your efs.

If it doesnt work flash the stock rom.
[Galaxy S III Original Android Development] dana.marivani:
Take a look Baseband grant See if you have it If you have EFS It's solved

If not available, you must install the corresponding modem

I had this problem for 18 days until I finally realized that it was Baseband:D:D
[Galaxy S III Original Android Development] ryanpatel122296:
guys i think i have something that can help....

These buildprop tweaks should help save some RAM. I will explain you one by one.

ro.config.low_ram=true

persist.sys.force_highendgfx=true

dalvik.vm.jit.codecachesize=0

ro.config.max_starting_bg=3

ro.sys.fw.bg_apps_limit=6

config.disable_atlas=true

ro.config.low_ram=true : This should turn off specific memory-intensive features that work poorly on low-memory devices.

persist.sys.force_highendgfx=true : Allow transparency in the status bar and enable highend graphics without disabling the low RAM flag.

dalvik.vm.jit.codecachesize=0 : Reducing the max size of the cache can help somewhat with memory usage, but if set too low will send the JIT into a thrashing mode. So, that's why I disabled entirely.

config.disable_atlas=true : Disable Atlas service.

ro.config.max_starting_bg=3 & ro.sys.fw.bg_apps_limit=6 : Reduce the allowed amount of apps in background, this will free more the RAM. I reduced the values because the default low RAM ones was still high for me.

maybe these should be incorporated into the builds cuz this along with some of my personal buildprop and kernel tweaks my rom flys...i get 440-460mb free ram...
[Galaxy S III Original Android Development] LuciferIII:
What do you experts think about this?
[Galaxy S III Original Android Development] Elton47:
I am not an "expert", but couldn't resist to state that it is not recommended to limit max background apps to 6 (for my usage at least).

I do respect some of these tweaks, but I always use some power saving ones instead, which I can share if anyone wants!

Thanks!

Edit: I have a persistent 350-450Mb of RAM when no apps running in the Foreground (but they are all active background processes) without a single tweak!

For optimal performance, anyone could use any kind of RAM swap virtualization or zRAM/xRAM. I do not suggest messing with RAM or Heap Sizes from build.prop.
[Galaxy S III Original Android Development] Tech0308:
Could you share your tweaked as well please
[Galaxy S III Original Android Development] minealex2244:
These tweaks are just limiting the performance of the system in order to get some MBs of free RAM. We can simply install a custom kernel and use zRAM + KSM + CPU OC 1.7 GHz and we are done. If we want the stock kernel then we can use Kernel Adiutor to use zRAM and KSM. Uninstalling unnecessary apps (system or third party) will also add some free RAM and battery life.
[Galaxy S III Original Android Development] Elton47:
pm.sleep_mode=1

ro.ril.disable.power.collapse=0

profiler.force_disable_err_rpt=1

profiler.force_disable_ulog=1

dalvik.vm.checkjni=false

dalvik.vm.execution-mode=int:jit

ro.ril.power_collapse=1

power_supply.wakeup=enable

ro.mot.eri.losalert.delay=1000

ro.config.hw_fast_dormancy=1

ro.config.hw_power_saving=1

windowsmgr.max_events_per_sec=150

ro.max.fling_velocity=12000

ro.min.fling_velocity=8000

ro.min_pointer_dur=8

ro.media.enc.jpeg.quality=100

ro.config.nocheckin

End of Tweaks.

Focused mainly on Power Saving.

P.S.: I also included some display quality tweaks, better scrolling, better signal, disable anonymous data sending / checking / collecting.

End of Post.

Start of another Post... .

Agreed! Another extra opsion would be to freeze some apps that aren't being used so often, which are still in background, so they can be like uninstalled apps, freeing up the overall RAM memory.

End of "another Post...".
[Galaxy S III Original Android Development] aser_elhbayeb:
Can you explain each one at a time what is it for?
[Galaxy S III Original Android Development] ryanpatel122296:
i have been using these tweaks for 1 month now and everything is butter smooth with no lags except for in snapchat, these tweaks disable useless background stuff i have researched this for the past 3 months about build props and etc, the power saving feature buildprop is usless as it makes the device lag as soon as you start it up from screen off also i dont use swap or zram as i have noticed it makes my cpu work extra therefore creates more heat.... since i use this as my main phone i use snapchat and for that i need all my cpu resources.....here is the full list of my tweaks...

ro.HOME_APP_ADJ=1

persist.sys.purgeable_assets=1

persist.service.pcsync.enable=0

persist.service.lgospd.enable=0

debug.performance.tuning=1

hw2d.force=1

ro.secure=0

persist.sys.NV_FPSLIMIT=60

persist.sys.NV_POWERMODE=1

persist.sys.NV_PROFVER=15

persist.sys.NV_STEREOCTRL=0

persist.sys.NV_STEREOSEPCHG=0

persist.sys.NV_STEREOSEP=20

windowsmgr.max_events_per_sec=250

ro.min_pointer_dur=8

ro.max.fling_velocity=12000

ro.min.fling_velocity=8000

persist.sys.scrollingcache=3

ro.securestorage.knox=false

ro.config.hw_quickpoweron=true

wifi.supplicant_scan_interval=180

ro.mot.eri.losalert.delay=1000

ro.media.enc.jpeg.quality=100

debugtool.anrhistory=0

profiler.force_disable_err_rpt=1

profiler.force_disable_ulog=1

profiler.debugmonitor=false

profiler.launch=false

profiler.hung.dumpdobugreport=false

persist.android.strictmode=0

ro.kernel.android.checkjni=0

ro.kernel.checkjni=0

logcat.live=disable

ro.config.low_ram=true

dalvik.vm.jit.codecachesize=0

persist.sys.force_highendgfx=true?

i also use greenify with myandroidtools pro....my cpu is under clocked to 100mv for each step, gpu overclocked to 350-640.....

lmk values are:

90

90

100

110

120

120

if you guys wanna know more about my other tweaks i still have lots more....

(p.s: Although im new to posting and stuff guys i suggest you try my tweaks first i mean i have been reasearching my tweaks list for the past year since cm13 days so just try it and hey you might enjoy the performance).
[Galaxy S III Original Android Development] Elton47:
pm.sleep_mode=1 #Changes to signal when screen is off. (battery friendly).

ro.ril.disable.power.collapse=0 #Enabling Power Collapse to preserve battery life.

profiler.force_disable_err_rpt=1 #Disable error reporting = true (1)

profiler.force_disable_ulog=1 #Disable logging = true

dalvik.vm.checkjni=false #Disable JNI checking that leads to slowdowns.

dalvik.vm.execution-mode=int:jit #Enable JIT compiler (for perf. boost)

ro.ril.power_collapse=1 #Battery life when screen is off. (can work combined with ro.ril.disable.power.collapse=0).

power_supply.wakeup=enable #Enable fast wake up from sleep mode.

ro.mot.eri.losalert.delay=1000 #1000ms Delay to Alerts.

ro.config.hw_fast_dormancy=1 #Enable fast dormancy for better signal.

ro.config.hw_power_saving=1 #It says for itself.

windowsmgr.max_events_per_sec=150 #Scrolling smoothly

ro.max.fling_velocity=12000 #Scroll-related

ro.min.fling_velocity=8000 #again

ro.min_pointer_dur=8 #again

ro.media.enc.jpeg.quality=100 #100% of original image's quality.

ro.config.nocheckin=1 #Disables google's checkin services and stops sending anonymous usage data.

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

Keeping launcher in memory tweak is Deprecated as per Android 4.1

Here are some Deprecated tweaks that I recommend NOT to use:

#ro.HOME_APP_ADJ=1

#ro.FOREGROUND_APP_ADJ=1

#ro.PERCEPTIBLE_APP_ADJ=1

#ro.VISIBLE_APP_ADJ=1

#ro.FOREGROUND_APP_MEM=1

#ro.VISIBLE_APP_MEM=1

#ro.SECONDARY_SERVER_MEM=1

#ro.BACKUP_APP_MEM=1

#ro.HOME_APP_MEM=1

#ro.HIDDEN_APP_MEM=1

#ro.EMPTY_APP_MEM=1

#ro.PERCEPTIBLE_APP_MEM=1

#ro.HEAVY_WEIGHT_APP_MEM=1

#ro.CONTENT_PROVIDER_MEM=1
[Galaxy S III Original Android Development] tito_puente:
Everytime I use an actual ROM on old hardware I get bad battery life. I thougt newer android versions have better battery management, doze mode and so on?

I have bought a new battery for my old S3, an Anker 2.200 mAh. Yesterday I used the device the whole day, installed some apps on the clean flashed LOS 14. I had about 1,5 hours display time, but more battery consumption was caused by "standby" and "Google Play".

Can this be correct? Also on my Nexus4 I had very bad battery life with cm and lineage.

What can I do?
[Galaxy S III Original Android Development] ryanpatel122296:
thats what alot of people think but with my testing i can prove this....try using a third party launcher(i use nova), and use this tweak then go to developer settings and go to background process limit and select no background processes then go to running services and press show cached process you will see that maybe beisde google play services you will find that all except the launcher is not cached.... this and after using this tweak i have also found that using any app lite or heavy as soon as i press home button and go to the launcher it comes up without any delay whatso ever....this proves that it does stay cached and ready to use for the best experience.

if anyone else wants to prove these tweaks do not work feel free to ask for screenshots and more im ready to show you guys that these tweaks do actually help. plus im the type of guy who picks up the smallest details so iv tried and tested each tweaks loads of times....

also using the sleep mode tweak and low power tweaks like i said just makes the phone lag when you start it up from screen off its better to just undervolt the cpu depending on your asv level, mine is 2 so consider mine to be second to lowest quality though i can still achieve -100mv, people with better asv levels can achieve -125mv

other than that the only way is to just disabled services, broadcast recievers, and actions using myandroidtools app.

---------- Post added at 09:07 AM ---------- Previous post was at 08:44 AM ----------

dude your tweaks just caused me to bootloop! and i cant seem to edit the buildprop through adb so that means im gonna have to flash everything all over again!!!! and i had just set everything up from a clean flash 3 days ago...
[Galaxy S III Original Android Development] Samofr:
Is there any tweak that can force GPU to make the graphical layer compositions instead of the HWC until it gets fixed ? Maybe we might gain some battery
[Galaxy S III Original Android Development] aser_elhbayeb:
I'm on the try for all the buildprob values except for the first one, which I read it's not recommended changing, I will see for the next couple days and report back.

Report: I wanna ask if there is some value related to Split Screen feature?

I noticed that SystemUI is now force closed when enabling it.
[Galaxy S III Original Android Development] Elton47:
Sorry to hear that. Do not flash anything. Go to TWRP and open terminal, type vi /system/build.prop

It will open as a text editable file, press i from keyboard and you are in edit mode (a.k.a. Insert mode). Remove the lines you added, press ESC, press :wq (including the dots : ) and press Enter. Reboot. I always back up system files before I interact with them.

BTW, my tweaks didn't cause the bootloop, as I use them for a long time. I also have to say that I used some of your tweaks with mine and I am having a nice battery life and performance is very great. Battery tweaks Never slow down your device if the tweaks are from build.prop, other kernel-related tweaks do slow the phone down.

P.S.: The launcher is being kept in memory, I know, but I don't think that old tweak will work on sdk 26 Android O, based on a git documentation.

Thanks for the tweaks and I hope you fixed the bootloop without flashing anything :(
[Galaxy S III Original Android Development] multiwirth:
I flashed the 2017-06-21 build today as clean install wiped only /system /data /cache /dalvik and installed the rom from internal storage.

First boot seems to be as always.

After setting up i saw thst everything on my internal storage has gone...

Reboot to TWRP to double check:

TWRP setup appears...

This build did a full wipe!!!

What happened to this build?

Is this a known bug and is it in every build from this date so should I be careful with other devices?
[Galaxy S III Original Android Development] notstpaul:
Strange! I only do the dirty flashes and didn't lose anything.
[Galaxy S III Original Android Development] multiwirth:
I use the device only for testing and mostly CM11 due to the extremly high performance but sometimes I flash LOS14.1 to check it´s development state.

So it isn´t a big problem for me but such things shouldn´t happen.
[Galaxy S III Original Android Development] ryanpatel122296:
thanks for the tip but since i was out in the day and i am using the s3 as my main phone i just reflashed lineage on top as a quick fix.....nice to here these tweaks are helping you out....and i dont really know how the bootlooped happened but its fixed now....also do you know how to make the memory footprint of the android system smaller my goal is to get atleast 500mb on free with nothing open cause i know that people usually say free ram is wasted ram but i read somewhere that androids garbage collection works better when you have 3 to 4 times the amount of free ram compared to used ram... also what you should try is with system app remover delete everything you dont need and also use myandroidtools to disable service and broadcast receivers believe me it makes a difference and in the content provider section you can even disable ads in the apps..