yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] zmix:
Anybody using this with the 1 GB RAM version of the i9300? Is it satisfying? I need a >4.3 Android, ideally something more modern than that, for the phone of my mum, and I do not want her to have any problems. Especially no lag and crashes. All cameras working? She's got the GSM version of the phone.

What is with apps, that require security features, like banking apps? Are they fully compatible?

---------- Post added at 04:14 PM ---------- Previous post was at 04:07 PM ----------

Any reason for the two threads? I feel a little bit confused now... But if it is alpha, I must pass. Need to give my mom the most lean and solid experience possible.
[Galaxy S III Original Android Development] noratroll:
I use the same model running Resurrection Remix based on LOS14.1 - no problems. For perfomance reasons you could flash Boeffla kernel.

Regarding to your apps: You should try.

In worst case you could roll back to stock Samsung Rom using Odin (download at Sammobile or Updato.com)
[Galaxy S III Original Android Development] zmix:
Thanks. I will do so.

It's the N26 banking app, which makes the update needed, since it wants Android 4.4 and the phone only has 4.3. It seems, Samsung did not deliver any other version OTA. Last time I checked it also said, that "phone has been altered" (I rooted it).

Hehe, I try to fiddle around with install/uninstall/root/unlock etc. as little as possible. Last time I did (wanted to install Cyanogen) I managed to brick the telephone part of the phone by overwriting the IMEI or something like that. This phone has some partition, that is sacred which I overwrote... I had to pay a professional to fix it.

I will need to re-read all this stuff.
[Galaxy S III Original Android Development] nobuteru:
Hi,

I ordered rear camera, so next update will be in February or March, if I am lucky in January, thank you for WIFI & host MTP workarounds, I hope to test them soon (never done any search about them, because I was focused only on rear camera), and see if it's OK (I think Lineage 15 will be out).

I would like also to test Lineage on a Samsung Note P605

thank you for saying about me that I am persevering but I can't afford a new smartphone so "it's a situation where you are as poor as **** and you have to become more ingenious than a NASA's engineer"

bye and see you next year!
[Galaxy S III Original Android Development] Android-Banjarmasin:
Is the performance mode in battery mode settings really works?

And how to report the "factory reset when reboot" bug

Thanks
[Galaxy S III Original Android Development] curiousrom:
Performance profile: Performance?

I did not test that Performance profile myself, just found this with the Search Tread performance profile box.

Attachments: Settings > Battery > Battery saver & performance > Device performance > Performance profile: Performance.

*****

What bug? Are you saying that your S3 is getting a factory reset when you reboot? Or in recovery mode? :silly: Or are you referring to this:

***
[Galaxy S III Original Android Development] minealex2244:
See attachment :) It's the start. Not yet done but I thought that you deserve to see it building :D Last steps.
[Galaxy S III Original Android Development] fir1996:
Awesome :fingers-crossed:
[Galaxy S III Original Android Development] LuciferIII:
A successful build? If yes, does it boot?
[Galaxy S III Original Android Development] nobuteru:
Well job man!
[Galaxy S III Original Android Development] minealex2244:
Not yet. :) I got to the apps' building step. That's close to the final build and packaging of the update. I think that everyone should be informed about the current status of the Oreo for S3. The building is taking hours and there are a lot of broken things. I hope that it will boot. If not then I'll try something more.
[Galaxy S III Original Android Development] curiousrom:
Camera Not Working - Custom Flashable Driver?

I just found this thread with a custom S3 I9300 flashable driver maybe you could try it with Lineage 14.1? [FIX][i9300] Camera Failed (All ROM)
[Galaxy S III Original Android Development] nobuteru:
I saw it now, I have downloaded zip patch, can't try soon, waiting delivery for original camera, I will post it maybe at the end of January or February...

thanks anyway
[Galaxy S III Original Android Development] Gizmotech:
I don't have Magisk and I have the same issue of phone going into sleep and the only way to get out of it is to reboot the phone. There is no other way to get it to wake. It is definately a LOS issue as I didn't have any apps installed, just the LOS 14.1 Rom and it went to sleep. Have been unable to find a fix so thinking of going back to stock.
[Galaxy S III Original Android Development] curiousrom:
Black Screen of Death

Good luck if you fix that by flashing an other ROM & please report here if you do fix it as I had the same problem starting after running for more than 2 years an other ROM without any problems & that's why I tried this Lineage 14.1. If it would be a Lineage specific bug I think this thread would be full of users reports.

And I don't run any launcher, Magisk, Expose or what not themes. Plain vanilla full wipe Lineage rooted with nano gapps.

I posted this a couple of days ago in this thread:

Caveat: my power button got stuck in the depress position 2 days ago & my charging port/cable connection is flaky. Sometimes I need to disconnect/reconnect because the charging rate is too low.

I used this crazy trick to turn on S3 I9300 with broken power button: https://www.youtube.com/watch?v=HYpkTXWC9XI

From the megathread **Ultimate GS3 sudden death thread** (and I have that chip) Edit: the eMMC check app crashes on Lineage.
[Galaxy S III Original Android Development] Gizmotech:
The issue only started after installing Lineage on my S3. Prior to this, I had been on Stock JB without any issues even though I am aware some people are experience like issues on stock. Hence I believe my phone is not one of the affected ones and this is more of a lineagos issue. For me it only happened after installing LOS.

Neverthelss, I was unable to check what my eMMC is as the app does not seem to open on linageos 14.1.
[Galaxy S III Original Android Development] curiousrom:
Thanks for reporting back as I checked & eMMC app crashes on Lineage. Will edit my post above. I checked the chip on 4.3 ROM.
[Galaxy S III Original Android Development] Gizmotech:
As I am searching for for a fix, the phone has gone to sleep. I see I have notification as I see the notification indicator flashing however there is no way of waking the phone. Tried putting the charger cable in, tried double pressing poer button, double tapping, screen-shotting...nothing wakes the phone. It happens about 7 times a day estimated.

I am on official Linageos 14.1 without any custom kernal. The only extra thing I did was root is using Chainfire root as LOS Root add-on did not work, recovered with Titanium Backup and then unrooted and removed Titanium Backup. The problem seems not to be a new one judging by past threads reported but I cannot find anywhere a solution anywhere.
[Galaxy S III Original Android Development] minealex2244:
LOS issue? How do you explain that a lot of LOS users got root working without breaking anything? It's not an LOS issue.

Where are the logs to prove that it's an LOS issue?

If it would be an LOS issue then someone would had fixed it or users wouldn't be able to use root at all on LOS for any phone (and everyone would know that). But these things didn't happen so it's not LOS team's business.

Edit: I got an idea: post here the last_kmsg when frozen before you are forcing the reboot.
[Galaxy S III Original Android Development] Gizmotech:
I deduced it is a LOS issue based on the fact that the issue is not there on stock Samsung JB. I am not saying that root is a possible cause of the problem rather giving a bit of background information that I did not use LOS Root add-on in my case. I am not alone in this deep sleep problem with the LOS rom which is not present on Stock for many users. Also the problem is not that the phone freezes rather the screen wont come on. The notification indicator often flashes where there is an unread notification hence I don't think the issue is the phone freezes rather not coming out of sleep.
[Galaxy S III Original Android Development] curiousrom:
Black Screen & Clean Install

So that's different from mine as it dies or freeze with a black screen (no way to know which) & needs a reset with 8 seconds long press of power button or boot in Recovery or battery removal (not recommended).

What you did could introduce problems. Best is a clean slate: after backup of your data: format internal memory, wipe everything & flash LOS, the LOS root & the gapps if you want them one after the other before rebooting to OS.

Clean Install

What is your recovery version? Is it the most recent twrp-3.1.1-0-i9300? I downloaded the .img version from TeamWin TWRP here and flashed it with my old Philz recovery directly from the phone & not with Odin or heimdall as I could not get the USB drivers to work on Windows 10.

I followed exactly this guide: How to wipe in TWRP properly? and the Installing LineageOS from recovery part of the wiki including step 10 & 11 for ROOT & gapps.

And install all apps fresh after that & not from a backup.

Edit: new lineage-14.1-20171129-nightly-i9300-signed.zip & gapps available.

By the way after trying both gapps AROMA & nano, next time I will use AROMA again as you can make granular choices.

***

Edit:

Could you explain how to do that when frozen?
[Galaxy S III Original Android Development] Gizmotech:
I can't see how its different because when there is no notification, its like your and requires the long press power button, boot to recovery or battery removal

I have already done this more than once

Yes

I used gapps nano

root/proc/last_kmsg. There is no way to do it when frozen/screen off. I think it may be possible via adb.
[Galaxy S III Original Android Development] ArdaCsknn:
I also have black screen problem.Phone is not waking for some reason.I guess its happening because of the magisk root.There are no problems with su addon.
[Galaxy S III Original Android Development] anarchist1017:
Yes definitely due to magisk faced the same problem went back to lineagesu
[Galaxy S III Original Android Development] imperiuspt:
My sound via Headphone jack is very low, any one with this problem? is there a way to fix it. And no, its not the headphones, on other places gives a good sound.

thanks
[Galaxy S III Original Android Development] Gizmotech:
Well I don't have Magisk and its happening to mines.
[Galaxy S III Original Android Development] minealex2244:
I'm feeling bad for you guys. Everyone should get the same beautiful LOS experience.

Thank you [MENTION=3526104]Gizmotech[/MENTION] for the last_kmsg. I think that you removed the battery to be able to reboot your phone. If you received a notification (sometimes you will receive it but it will freeze before letting you know that you got a notification) then the kernel will freeze. If the kernel is freezing it's because of root or a failed attempt to remove root (even if it said that it was a successful removal). It's very simple: you get a notification and it freezes. Maybe it will give a sound and the LED light maybe not. What's sure is that the kernel will freeze. Lastest SuperSU has this issue fixed. If you want it working then dirty flash latest build again. Tell me if the issue was fixed and avoid root until that time. After you'll tell me the results you can flash latest SuperSU and tell me again what happened. Do not remove root. This is always a dangerous thing.
[Galaxy S III Original Android Development] Gizmotech:
Thank you for your suggestion. I shall flash again and not root the phone and monitor progress and shall keep you posted. This will at least confirm that the problem is not with the LOS ROM and more a root/unroot issue.
[Galaxy S III Original Android Development] ArdaCsknn:
I got backup before flashing Magisk.So just restored and there isn't any problem.
[Galaxy S III Original Android Development] Psycho103:
Whenever I turn on WiFi hotspot the hotspot timeout gets reset to never timeout. Anyone else facing this?
[Galaxy S III Original Android Development] curiousrom:
Which SuperSU? | TWRP 3.2.0-0 Update & App

Which SuperSU are you suggesting? Is it this one http://www.supersu.com/download (not the apk app, the recovery zip) or addonsu-14.1-arm-signed.zip as recommended in the Install LineageOS on i9300 Wiki?

My S3 crashed again when charging @ 92% which it was doing when running an other 4.3 ROM after 2 years without problems. I attached the last_kmsg.log copied after rebooting. I you could take a look, would be appreciated as I am a total noob on this subject.

This is after a super clean install with full formatting & wipe as described in my post here.

I can see a panic line in it:

vmalloc=144m oops=panic pmic_info=65 cordon=e6b21b1e37d15c7ad5232c6087e63276

But I suspect a hardware problem.

***

TWRP 3.2.0-0 Update Notes I tried the TWRP app to install it but too many clicks & it links to your browser to download it & the app leaves quite a footprint & a running network traffic tracking service (InsightService) even if opting out of it as seen in the attachments.

Better to download it TWRP for i9300, copy to external SD card root & flash with your current recovery IMO.

Played with recovery TWRP 3.2.0-0 but did not flash a ROM with it yet. Looks good.

***
[Galaxy S III Original Android Development] minealex2244:
SuperSU. The other one is not SuperSU, it is LineageSU.

Edit: Don't zip last_kmsg. Just make it a .txt file. I don't like to download it.
[Galaxy S III Original Android Development] LuciferIII:
Xda has a limited txt file size that you can upload.

Thats probably why he did that.
[Galaxy S III Original Android Development] minealex2244:
That file won't exceed any limit. Last_kmsg won't be more than 512 kb. That is the limit for every last_ksmg for default.
[Galaxy S III Original Android Development] TEXHUKCA:
Hello the font renders badly with weird thin/thick weights and dont recognise any colors in the apps.Can anyone help me ?
[Galaxy S III Original Android Development] minealex2244:
The extension shouldn't be .text :D lol. Use .txt. SuperSU is more stable and complex. Also it has a lot of built-in security features. The content you hid only shows how you powered your device on. You can ignore that thing as it won't help you in discovering any issue. What's before that is very important. You'll be able to answer to the question: "what happened that led to a reboot?".
[Galaxy S III Original Android Development] curiousrom:
Please explain how to get last_kmsg after crash then as I copied it right after 1 reboot.

You did not reply to previous post question:
[Galaxy S III Original Android Development] minealex2244:
Just copy the last_ksmg after the reboot with a file manager you like. Then add .txt extension to that file to be allowed to upload it on XDA.
[Galaxy S III Original Android Development] curiousrom:
That is exactly what I did. Immediately after reboot but you say there is no relevant info in it.

Searching web @ the present to see if possible to connect via ADB while frozen.

.text was a typo lol but still able to open it w/ Notepad & Wordpad while invalid extension for the forum attachments.

***
[Galaxy S III Original Android Development] minealex2244:
That's a command line to tell the kernel what to do when a fatal error is detected (it will panic). Use pastebin for last_ksmg if you what or HIDE tag.
[Galaxy S III Original Android Development] Ashraf Iraqian:
hi guys

TWRP 3.2.0-0 Released

https://dl.twrp.me/i9300/
[Galaxy S III Original Android Development] Gizmotech:
Right, so this is where I am now. I have wiped and formatted and installed LineageOS 14.1 again. I did not root it this time to eliminate whether superuser or root was causing the sleep issue. I can confirm that it is still going to sleep and no way to wake it up other than holding the power button down for a period of time and letting the phone reboot.

To confirm that the screen had switched off/sleep and the phone just did not power off (for whatever reason), I put the charger in which confirmed the phone had not powered off as I would have seen the charging indicator on the center of the screen and notification light on.

Before LineageOS, this problem did not exist on stock Samsung JB. For this reason, I deduce that the issue is with the rom itself. I have attached the last_kmsg if anyone wants to have a look. I pulled the file using ADB after restart as I couldn't pull it from the phone due to no root.
[Galaxy S III Original Android Development] minealex2244:
It looks like this is worse than on S6 Oreo. We only have freezes but it happens randomly. On your phone it just freezes the userspace when the screen is off. On my S3 I'm running the 20171004 build and it works perfectly.
[Galaxy S III Original Android Development] Gizmotech:
I will install your build and update.

UPDATE: I can't. It does not exist on the Lineage Website anymore.
[Galaxy S III Original Android Development] curiousrom:
Old Lineage vs New

Why not backup, update to current build and tell us how it's working for you?

New users naturally install the most recent build so that would be useful to them.
[Galaxy S III Original Android Development] aser_elhbayeb:
Off-Topic، I'm having a problem with Package Installer, the install button refuses to work as if it is disabled.

Any idea?
[Galaxy S III Original Android Development] h2aroon:
Do you have any screen overlay app like blue screen filter. If you have then disable and try.
[Galaxy S III Original Android Development] minealex2244:
Wow. I never experienced anything like that since I'm using Android. Grab the log of Package Manager with an app like Logcat Extreme then post it here.
[Galaxy S III Original Android Development] g104:
I've tried to use TWRP 3.2.0-0-31344a3b flashed lineage-14.1-20171129-nightly-i9300-signed, boeffla kernel & opengapps w/o any issue, but troublesome to make the boeffla config showing the exact recovery version.
[Galaxy S III Original Android Development] minealex2244:
Boeffla is Boeffla. Not our business. There are other ways of getting support directly from Lord Boeffla.
[Galaxy S III Original Android Development] aser_elhbayeb:
Yes I have one, and it was the one causing the issue.

Thanks a lot.

Problem solved. Thanks for trying to help.
[Galaxy S III Original Android Development] aldrin3010:
I think Lord Boeffla mentioned somewhere that TWRP doesn't provide a way for apps to check the installed version. The way the config app reads the TWRP version is from the backup logs. You can try making backup of any partition through recovery and then open the configuration app. It must show the correct version after that.
[Galaxy S III Original Android Development] zarere:
Check here

https://xdaforums.com/galaxy-s3/dev...able-27-03-t2449408/post71420950#post71420950
[Galaxy S III Original Android Development] Kippy51:
When I go to the OP and 'downloads' I still see the 1004 build in the list. Just tried and I get 'Not found'. Sorry! But if you really want it, I can upload it to Dropbox; just let me know.
[Galaxy S III Original Android Development] LuciferIII:
Don't worry about boeffla app not showing the exact TWRP version.

I think there is a way to fix that but it's not really a big deal. Thats a know issue.

Edit : Oops, someone already answered with a solution ^^
[Galaxy S III Original Android Development] Gizmotech:
I would appreciate that if you would. Thank you.
[Galaxy S III Original Android Development] Kippy51:
Started the upload, but it will take almost an hour. Will send you the link in PM later! ?
[Galaxy S III Original Android Development] Kippy51:
Check your PM! Hope it works for you :laugh:
[Galaxy S III Original Android Development] Gizmotech:
I clean flashed build 20171004 immediately after I received your link. I have not rooted the phone or anything. Have not flashed any kernals. Just the original LineageOS and it has just happened again. Black screen and not waking up. I am exhausted now and have decided to either go back to Stock JB or just get a new phone. I needed LineageOS because Barclays Bank have stopped supporting JB hence I upgraded. Thanks to all who helped.
[Galaxy S III Original Android Development] dana.marivani:
Guys, Assignment Oreo what happened?!
[Galaxy S III Original Android Development] curiousrom:
LineageOS 20171004 Freezing

Installing stock ROM is the best way to check if it's a hardware problem or not.

Please report back if it fixed your freezing problem. Good luck!
[Galaxy S III Original Android Development] ArdaCsknn:
Try some stock ported 4.4 roms maybe it can help.
[Galaxy S III Original Android Development] Kippy51:
I'm sorry it didn't work ... Read all your messages back and now I wonder if it can't be a proximity sensor problem. There are apps to check that. But as [MENTION=4122877]curiousrom[/MENTION] said: flash stock and please let us now if that DID work!
[Galaxy S III Original Android Development] minealex2244:
The build stopped at 99% with a stupid error. :( I didn't have enough time to find a proper fix but I now one. I'm sure that it won't boot. But fortunately I know how to fix that. Also I'll try to fix WiFi, Bluetooth, GPS, vibrator and RIL.
[Galaxy S III Original Android Development] minealex2244:
I think that if I adapt this commit to my cache size error everything will be OK.

Edit: And maybe this too.
[Galaxy S III Original Android Development] ArdaCsknn:
https://www.blog.google/products/android/introducing-android-oreo-go-edition/

Google introducing Oreo Go edition.Did you look at it?
[Galaxy S III Original Android Development] mpsoft:
In camera, why is green line in 16:9 mode?

Thanks for amazing rom!!!:)
[Galaxy S III Original Android Development] Noobkid77:
The latest build went into a boot loop I left my phone on downloading a file I had two apps open in the background then it went into a boot loop on the latest build not sure why that happened but the fix was clear cache n dalvik cache then my phone returned to normal
[Galaxy S III Original Android Development] AlecSpence:
Does the same for me, but still records a 16:9 photo - though the viewfinder doesn't show the whole shot.

I'm using Open Camera as a workaround at the moment.

It's about the only flaw I've found in this ROM which has brought my i9300 back to full life again.
[Galaxy S III Original Android Development] eriol1:
Just upgraded from cm13 (some nightly from a few months ago).

Wasn't sure when to flash gapps so flashed together with experimental.

Basically what I did:

- Updated recovery by flashing twrp 3.0.2-2

- Flashed Experimental (migration) build.

- Flashed open gapps pico arm 7.1

- Reboot system. (took around 20 minutes)

- Flashed latest weekly.

- Reboot system. (took around 10 minutes)

- remembered I need root, flashed su addon.

- reboot system.

- all seems well. No problems with the migration.

So far so good :)

Thanks!

(really enjoying the quick response feature btw...)

Sent using XDA One
[Galaxy S III Original Android Development] froycard:
In my opinion, this ROM is pretty stable and working flawless (so far). But I detected the same issue as the previous release (prior to LineageOS: cyanogenmod), and it's that it is impossible to access the Ext-SD memory card using the default File Manager app although you select Root permission from the setting. Although this can be sorted out by installing other file manager applications, such as Total Commander. Has anybody found a way to fix this or a workaround?
[Galaxy S III Original Android Development] qs666:
https://download.lineageos.org/extras
[Galaxy S III Original Android Development] abelenki:
yes:

https://xdaforums.com/showpost.php?p=70352156&postcount=8850

https://xdaforums.com/galaxy-s3/ori...14-1-i9300-t3544531/post70833718#post70833718
[Galaxy S III Original Android Development] tonga01:
Has anyone tried the rom with I9300XXUGNA8 modem? Does it still cause robotic voice during calls?