yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] it'sup:
im getting "updater process error 7" when flashing the newest Rom, Was it made to be flashed over the last version?
[Galaxy S III Android Development] InTheY2K:
Which version of TWRP are you using?
[Galaxy S III Android Development] leleobhz:
Did ext4 entire format. Kernel is weird someway: Release #3 works well and ok (But may have the 800mhz issue).

Kernel of #3 works well even with Magisk. The weirdness starts after SafetyPatch. Kernel boots randomly normal or in download mode (But 90% of times in download mode). There is no logcat of this. When boot happens "normally", the first step of logcat happens well, but the second connection to logcat does not get anything and phone behaves like a bootloop. This behaviour has never happened with #2.

I suspect strongly @flither issue with battery is a bit relationed with this kernel context change, because kernel madness increases if Im using a charger, sometimes even displaying the second battery charge icon when powered off (This second battery icon is a kernel in "charge mode").
[Galaxy S III Android Development] ChronoMonochrome:
I didn't test installation with Magisk. Unfortunately I have no clues how exactly it works, so due to certain changes in ROM / kernel and in the Magisk itself it may or may not work, and there are too much of factors that may result in device behaving unpredictably. So I would suggest testing a clean installation.
[Galaxy S III Android Development] nur gopa:
why build #3 not advertised yet , and when it will be ready ?
[Galaxy S III Android Development] jc9896:
deep sleep appears to cause really bad scrolling lag, at least on the latest test build (#3) from my testing. (bad scrolling jerkiness and dropped frames mostly)

these issues are solved by using Wake Lock app and setting to PARTIAL_WAKE_LOCK.
[Galaxy S III Android Development] leleobhz:
Hello!

Magisk works mounting overlays under /system. It mounts each file it needs specifically overriding the original file. Magisk tracks the list for each magisk module, so it overmounts only the specific files they need.

Even a clean install does misbehaviour too. If possible, can you enable last_kmsg/pstore?

* https://sites.google.com/site/zhuow...onandroid60andabovesysfspstoreconsole-ramoops

* http://docs.halium.org/en/latest/porting/debug-build/dmesg.html

Also, can you test you build with lastest TWRP from site? I suspect the mkfs from TWRP may be someway different from what you kernel expect:

~ # mkfs.ext2 -h
mkfs.ext2: invalid option -- h
BusyBox v1.22.1 bionic (2019-04-11 05:32 +0000) multi-call binary.

Usage: mkfs.ext2 [-Fn] [-b BLK_SIZE] [-i INODE_RATIO] [-I INODE_SIZE] [-m RESERVED_PERCENT] [-L LABEL] BLOCKDEV [KBYTES]

-b BLK_SIZE Block size, bytes
-F Force
-i RATIO Max number of files is filesystem_size / RATIO
-I BYTES Inode size (min 128)
-L LBL Volume label
-m PERCENT Percent of blocks to reserve for admin
-n Dry run

~ # uname -a
Linux localhost 3.0.101-CM-gca2a2d5 #1 SMP PREEMPT Thu Apr 11 05:40:57 UTC 2019 armv7l GNU/Linux
~ #
[Galaxy S III Android Development] ChronoMonochrome:
Thanks, I know all those basics stuff. If you look into more details on how exactly it works (which I have no clues about), it envolves a certain requirements to the kernel / ROM, which may or maybe not met.

It's already enabled. You can't get last_kmsg after rebooting to a bootloader, because it (probably) gets overwritten by the bootloader itself.

Indeed that looks weird. I didn't test a latest TWRP (I'm using 3.2.3 version).

I'll retest it - and check for all those bugs mentioned here, but which somehow I can't reproduce so far - once I have a spare time.
[Galaxy S III Android Development] leleobhz:
Curiously I can't read it from TWRP from official site. Its possible to manually extract this from storage?

Also, from you git repo, the process to build twrp is working? I can try build it here to check what is missing.
[Galaxy S III Android Development] joam280:
After installing the latest version lineage-16.0-20190411, I recover data correctly but lose wifi signal after a while. Any solution?
[Galaxy S III Android Development] SILELICA:
Instaling Murata wifi fix zip.
[Galaxy S III Android Development] ChronoMonochrome:
This log is saved not in the storage, but rather in the RAM. So under a certain circumstances it can be loss even without rebooting to bootloader.

Yeah, latest time I've been building TWRP 3.2.3 on LOS 15.1 sources a few months ago.

It should be buildable at least, I only had to include OmniROMs bootable/recorery-twrp and busybox repos.
[Galaxy S III Android Development] leleobhz:
Nice! Ill try to build.

Just a note: @ChronoMonochrome - you paypal link is broken :(
[Galaxy S III Android Development] flither:
So it seems it randomly sucks out the battery when ON too. I left the phone for couple of hours, everything turned off (no wifi, no bluetooth, airplane mode on, no Gapps or other s**t). After few hours battery went from 40% to 0. Battery graph again showing nothing unusual
[Galaxy S III Android Development] rfmalta:
just wanted to say great job!

the only thing that did not work was my selfie camera... is there a fix for that? I'm on april's rom

thanks
[Galaxy S III Android Development] Bvukaso:
For me.. it gives an error first, but after that when I open camera again it is working in selfie mode.

Rom has similar battery draining thing as 8.1

However it is very fast.. and with some fixes it could be the best ever.:good:
[Galaxy S III Android Development] Sobhan Mazaheri:
Is there a way to install the latest version of Google Camera?:confused:
[Galaxy S III Android Development] jc9896:
Gcam is 64 bit, GS3 is 32 bit.

There is a 32 bit Gcam in the forums (edit: Google Camera Mods subforum) somewhere, you might be able to get it to work if Camera2 API can be enabled successfully.
[Galaxy S III Android Development] rfmalta:
Yes it worked... just had to force stop the camera app

Also noticed the battery draining problem but it is charging faster too... very strange

Even with the small problems this rom is much better than the official 14.1 los... if development continues will be the best EVER for sure!
[Galaxy S III Android Development] ashu_jstme:
How do I update to latest builds ?

I was able to flash build number 20181205, I am not able to flash the latest ones. Getting updater error number 7 while doing so. Says

“this build is for GT-I9300 and your is . “

How do I install the latest build ?

Note- I was unable to flash the new build because of above error when installing fresh. I had to flash 20181205, others where throwing error number 7.

Thanks for this awesome ROM by the way .?

Appreciate you spending time developing this.
[Galaxy S III Android Development] rfmalta:
Are you on latest TWRP? Did you factory reset before installing (clean install)?
[Galaxy S III Android Development] deentky:
(sorry for my english)

Hi there

LOS 16 is very fast. I was testing the last three LOS (14.1, 15.1, 16), and 16 is a beast in terms of speed and efficiency. But I don't use it anymore. Unfortunately, it's not stable for me. I was testing it for two days and I've come across an annoying bug. Almost every time I turned on my phone or reboot, some very strange things happened on the screen where I type in my SIM PIN:

- the phone freezes,

or

- the phone won't let me type my PIN,

or

- the phone itself typed the PIN (LOL!), the phone must have somehow entered the wrong PIN three times, because there was an information that the card had been blocked! (LOL!), luckily, the card hasn't been blocked,

or

- the screen was black and the status bar was flashing,

or

- the screen was utterly messed up, as if three screens overlapped at once (SIM PIN screen, phone PIN screen, and status bar).

There was nothing I could do but take out the batteries.

And it happened every 2-3 reboots.

My setup:

- lineage-16.0-20190411-UNOFFICIAL-i9300

- MindTheGapps-9.0.0-arm-20190216_211054

- addonsu-16.0-arm-signed

Everything was done correctly, without errors.

Apps installed:

- open camera

- instagram

- swiftkey

- messenger lite

- notatnik

- txtpad

Other than that, LOS16 was fine. Very, very fast. The camera was kinda unstable though (problems when switching between front and rear, and also with video recording - a lot of skips).

I'm sorry that I can't reproduce this weird bug and deliver the logs, but I don't have much time and I need a 100% working phone, so I switched back to LOS 14.1
[Galaxy S III Android Development] aveyo:
I suggest making changes to the profile via Kernel Adiutor app to improve stability.

cpu guvernor: zzmoove, turntables profile number:5 for balanced responsiveness or 2 for a bit more battery or 11 / 10 for a bit more performance

schedule work quees on awake cpus unticked for more responsiveness or ticked for more battery savings

io scheduler internal:cfq - readahead:512kb, external:fiops - readahead:1024kb.

everything else default, make sure apply-on-boot is ticked for cpu and io categories.

very important Kernel Adiutor settings - apply on boot delay = instant and hide notification + disable toast

as for sim pin.. I strongly advise disabling it and instead use screen lock pin (reason being gsm starts later on in the boot process)
[Galaxy S III Android Development] ashu_jstme:
Yes I did a clean install. I tried flashing new TWRP version. After flashing my phone went into boot loop and not coming out of it. I cannot load recovery mode, it restarts before TWRP recovery can load, somehow I am able to go into Download mode. THe moment I put battery in phone it goes into loop. Do not know what to do now ?
[Galaxy S III Android Development] rfmalta:
If your phone is not hardware damaged you should be able to flash an official samsung rom with odin/heimdall. Then you could try installing it again.
[Galaxy S III Android Development] ashu_jstme:
Thanks for the reply. I tried flashing Samsung stock firmware using Odin which was successful but bootloop didn't went away. Phone was restarting every 2 seconds. I checked the power button, it was intact and not stuck.

What resolved my issue was installing a different recovery app, I completely dismantled my phone till, cleaned it and assembled it and then I used Philz touch recovery and then tried booting and this time it booted into recovery mode. I was able to flash latest build this time.

I think this was related to TWRP, updating TWRP to latest version almost bricked my phone. Thanks guys for your responses.
[Galaxy S III Android Development] Bvukaso:
I think there is also some kind of power management problem. Sometimes in idle state phone goes very hot and it can lead to black screen. It is rare, but it happens.

The good thing, as somebody mentioned above, is that battery charging is very fast.
[Galaxy S III Android Development] Leon:
What is the best kernel to use with this rom?
[Galaxy S III Android Development] Nobby1960:
Pull out the battery for 10 minutes and push the power button for a longer time. After this, try to flash different TWRP recovery versions (.tar) for the GT-I9300 direct via Odin. It seems only like a soft brick. After every flash try to jump into recovery mode. If it works, do a full wipe.
[Galaxy S III Android Development] nur gopa:
where last update 2019-04-27 ?
[Galaxy S III Android Development] dana.marivani:
We are in absolute silence, there is no news of the new update :(
[Galaxy S III Android Development] ropuhorasi:
Thanks for the great effort :good:

Will we wait a lot for the new update ?:confused:
[Galaxy S III Android Development] Sobhan Mazaheri:
I guess [MENTION=5695278]ChronoMonochrome[/MENTION] focuses on a new linux kernel 4.13
[Galaxy S III Android Development] ChronoMonochrome:
I have to announce that probably there won't be new releases for a while.

I don't see a point in releasing a new build before I can address some instabilities pointed in regard of the latest (April's) test build.

That's a long running project. While it would be very nice to have a new kernel source, it would rather be more real to say, that it's not going to happen that soon.

But you're right though, I'm looking for ways of having a new kernel source, have no idea if that would be the mainline one or the same LineageOS kernel but just with some fixes.

Either way, it would require a lot time to figure out ways of fixing bugs pointed here, so please patient and for now stick with a more stable ROM (probably LOS 14.1?).
[Galaxy S III Android Development] gianogli:
Which are the instabilities/bugs you discovered in the latest test build?

Could you write these bugs in a list? In this ways, if there is someone able to help you, he could start debugging one issue at time. :)

In meantime... Thanks for your great work on this project! :)
[Galaxy S III Android Development] Bvukaso:
Yes , it could be great if this could be some kind of community project, not one man army. :)
[Galaxy S III Android Development] ropuhorasi:
test build 11/4

We were waiting you to fix bugs and release a new build :(
[Galaxy S III Android Development] nur gopa:
What is the best build ?

9.03.2019 - build #2

or

11/4/2019 - test build
[Galaxy S III Android Development] SakthivelNadar:
I'm currently trying to make his LOS 16.0 stable, would you like to help me? if yes then pm me!:)
[Galaxy S III Android Development] javedgh:
any new stable vision los 16
[Galaxy S III Android Development] sgs9:
H'll release a new build as soon as ...

It's not faster with stupid requests and it's very rude.
[Galaxy S III Android Development] leooportilla:
Problem with WiFi

Good I'm testing the ROM in my S3 i9300 but everything works perfectly, but at the time of turning the Wi-Fi on and off, it does not reconnect, it only remains in "Saved", nor do I know if they have a solution for that so they can help me , thank you
[Galaxy S III Android Development] bacinoc:
Have we lost hope? And died this work? :(
[Galaxy S III Android Development] InTheY2K:
Read [MENTION=5695278]ChronoMonochrome[/MENTION]'s post from May, 12th.
[Galaxy S III Android Development] Ruben8ap:
Good morning friends

One question, the doze mode is enabled in the last build of April?

Thanks :)
[Galaxy S III Android Development] Skynet30:
I tested this ROM on my S3 which I just use as a fitness tracker / emergency phone for outdoor sports. Overall this ROM is already very impressive considering it is labeled alpha and I would not have thought to see Android 9 on this old phone. I can report that the GPS is in fact not in a workable state: It takes a couple of minutes to get an initial lock but the lock is often lost and takes too long to recover in order for apps to work sensibly with it.

I.e. a fitness tracker isn't able to properly record an activity and a car navigation would probably be inadvisable. The GPS does work well enough on 14.1 which I normally use but it can take some time to get an initial lock as well, although once locked it does get subsequent locks much quicker.

If this GPS issue were fixed, I think this ROM would already be good enough to use as a daily driver.
[Galaxy S III Android Development] Mad-Marty:
Hi, thanks for working on LOS 16.

Any chance of getting a "official" build?

While I don't know whats required to be tagged official, i believe working SELinux is the most complicated part?

Would be great to have a official being hosted on lineageos.org with regular updates.

Also it could be flashed dirty and work.
[Galaxy S III Android Development] nimasalehi72:
Has anyone had a problem with device's IMEI? I installed the ROM last night and I noticed that the device's IMEI is not shown through *#06# or the "About" section in Settings. although everything works fine with calling and getting signals.
[Galaxy S III Android Development] Vegggen:
Yep, lost IMEI and got no sim detected message. Not able to make any calls.

Restoring efs or full nandroid backup did not help.

Had to reinstall stock Samsung rom.

Possibly an IMEI repair tool could have done the trick, did not try that.

Edit: Still having issues with sim not detected, starting to suspect sim slot hardware issue...
[Galaxy S III Android Development] irinapoika:
after I tested build 11/4

i found this bugs

-when i receive calls i see black screen and i cant answer , i must press home button and open screen lock and answer , and the phone becomes very slow . sometimes i can't answer . and incoming call delay for 7 to 10 second until the phone rings .

-when i use battery saver and want to connect the charger , the phone appear black screen and freezing and need to restart .

- when i open the phone and Type the PIN code , appear message ( SIM PIN operation Failed) . and I'm sure the code is right .

- many time the phone freezing without open many programs and services in background . and appear message (System UI has stopped working)

- sometimes sounds don't work in the phone . and you must restart the phone

I thank you for your effort and wonderful work :good:, I hope we get new next built without above bugs and with enable SELinux enforcing and more stable .:fingers-crossed:

thanks again :good:
[Galaxy S III Android Development] andybla:
just wake the phone from sleep first and then plug in the charger
[Galaxy S III Android Development] Sobhan Mazaheri:
Waiting for a new build

Hi Mr [MENTION=5695278]ChronoMonochrome[/MENTION]

Do you still work on this rom?

When will the new build #3 be ready?
[Galaxy S III Android Development] slonioo:
Uuuu... The ?storm will start soon?

Please don't ask the developer for ETA, when he works for free?
[Galaxy S III Android Development] F_master25:
He has already made it very clear that it is a long and hard job, with no deadlines, just wait and if you can help then help.
[Galaxy S III Android Development] FPetePF:
If he is still working on it is an entitled question. Dont be so rude. Sometimes people need some motivation. And perhaps this questions to be interested in can help. :o
[Galaxy S III Android Development] someOn3:
It is a legit question. The same with debian. Debian is expected to be released somewhere in Q3 or Q4 of 2019. Probably.

I am wondering the same because: if the OS does not work on my phone until Q4 of 2019, i probably go and buy a new phone.

Not to stress the dev, but to know where i am.

If he says this will take 3-5 years, thats ok, but then i will go with another phone and let the s3 off in the drawer until its released.
[Galaxy S III Android Development] ChronoMonochrome:
I'm not getting enough time to support this project, so if anyone waiting for soon updates, unfortunately it's not going to happen soon.

I can't work continuously supporting just one project so I switched for now to others. I have some other devices to work on, plus some non-Android dev projects.

Fixing the rest bugs of this ROM mentioned here in the latest posts (battery drain, overheating, etc and so on) doesn't seem to be straightforward for now, so I will return as soon as I'll come up with any working solution.

It seems like there are some more devs working on Pie builds now, so you can try one of those builds and help devs reporting bugs.

I won't do any promises, but when Q released (should be released in August), I'll definetely try it out. But no any promises, as it still seems to be unclear whether it's ever will be possible to run it on this phone.
[Galaxy S III Android Development] vuut:
about Gapp which one ????????
[Galaxy S III Android Development] djemilbakhti:
UNOFFICIAL CrDroid v5.4 android 9

https://xdaforums.com/galaxy-s3/development/rom-unofficial-crdroid-v5-4-t3938176
[Galaxy S III Android Development] Sobhan Mazaheri:
Mr [MENTION=5695278]ChronoMonochrome[/MENTION]

Can you only update source to r40?
[Galaxy S III Android Development] leleobhz:
Isn't a good idea try to port Project Treble to S3 base? So this way, any new android upgrades will be straightforward. I think is a best (And longer) approach than fix a specific rom. What you think about?

Also, I'm not a skilled developer, but I can search something and try to send some patch or test distro (Since I have the phone).
[Galaxy S III Android Development] ChronoMonochrome:
That should be a long-term fix that can persist even Android upgrades, if all the Treble stuff is implemented in a recommended way.

At the current stage, it probably should be possible to boot up a GSI (Generic System Image), since we aren't using any hacks in android sources (the latest hack used here can be eliminated by setting lowram property), but I'm too lazy to work on it.

Will try whenever I'm again in a mood to work on it.
[Galaxy S III Android Development] vuut:
try on my friend because S3 still has users

Gửi từ SM-A510FD của tôi bằng cách sử dụng Tapatalk

---------- Post added at 01:44 AM ---------- Previous post was at 01:20 AM ----------

thanks U for hard work

gapp ARM...... which we choice?????? 6.7.8 or 9.0

---------- Post added at 01:47 AM ---------- Previous post was at 01:44 AM ----------

flashing it with newest TWRP 3.3.0

---------- Post added at 02:36 AM ---------- Previous post was at 01:47 AM ----------

Does it have Root?????

Can i fláhing Magisk-v19.3.zip???? then flash Rom
[Galaxy S III Android Development] Sobhan Mazaheri:
Hi Mr. [MENTION=5695278]ChronoMonochrome[/MENTION]

Thanks Your efforts

Should we be ready for the new Build and be happy?

(We have been waiting for this great thing for a long time)
[Galaxy S III Android Development] SakthivelNadar:
Hi, i have made an optimized version of this rom and today i'm releasing a new build! :)

https://xdaforums.com/galaxy-s3/development/rom-optimized-lineageos-16-0-team-t3940142

plz test and let me know :)
[Galaxy S III Android Development] Sobhan Mazaheri:
Tnx for your support

Mr. [MENTION=5695278]ChronoMonochrome[/MENTION] no longer develops this ROM?:confused:
[Galaxy S III Android Development] SakthivelNadar:
he is helping me with this rom;) maybe when he get time, he will release an update to this rom:)
[Galaxy S III Android Development] Sobhan Mazaheri:
I installed rom:

There is still a black problem with the page after the call

There is a restart random issue
[Galaxy S III Android Development] SakthivelNadar:
Do a clean flash
[Galaxy S III Android Development] Sobhan Mazaheri:
Super clean flash installation
[Galaxy S III Android Development] SakthivelNadar:
strange, i didn't had that issue
[Galaxy S III Android Development] 3mad7ajeb:
can you made it for sch-i535 & sch-r530u please?

can you made it for sch-i535 & sch-r530u please ?
[Galaxy S III Android Development] InTheY2K:
Hi everybody,

I've installed this ROM several times now on my S3 (GT-I9300), but it just won't boot. It gets stuck at the boot animation with the arch and the moving circles.

I tried all the variations I could think of. With and without gapps, with and without magisk, dirty and clean, with or without formatting data, and all combinations thereof.

Nothing works.

And yes, I am aware that the initial boot after the installation can take a while, but not an hour.

What could be the issue here?

Gesendet von meinem F1 mit Tapatalk
[Galaxy S III Android Development] crisdotti:
Try re-download the file
[Galaxy S III Android Development] SAVITAR B.:
Try installing the newest version of TWRP. And then just fully wipe everything,then install the ROM and after that wipe cache and dalvik.It should work fine. There is also an optimized version of this ROM, make sure to try it out:laugh:
[Galaxy S III Android Development] InTheY2K:
I do have TWRP 3.2.3-0, which is the latest according to dl.twrp.me: twrp-3.2.3-0-i9300.img.tar6.5M2018-07-30 02:51:23 EDT

Like I said, I DID completely wipe AND format everything. Why wipe cache again, after installing the ROM when it has been wiped before?

Which optimized version do you mean? I've looked into several threads here, and all said that they're far from being in a state, yet, where the ROM could be used as a daily driver.
[Galaxy S III Android Development] -CynicalX-:
That isn't the latest TWRP, 3.3.0-0 is

https://anonymousfiles.io/eTTuUGxG/