yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] multiwirth:
It occurs not often and I'm more interested in a working HWC.

The phone is slow and laggy even with boeffla Kernel with OC and a faster hotplug governor which turns on and off the cores to get the performance when needed.

LineageOS should come with another governor out of the box.

Pegasusq is extremly slow.
[Galaxy S III Original Android Development] ArdaCsknn:
You can try experimental build. It has a working HWC (kinda).Also its not that slow.Faster than all Sam based roms.Multitasking working great.I can switch app to app really fast.
[Galaxy S III Original Android Development] Samofr:
Maybe he's saying that substratum is preventing him from updating the rom .. ?
[Galaxy S III Original Android Development] multiwirth:
I tried that build but I was facing some little issues like video playback and record was completely impossible (freeze)

Don't know what happened exactly but the same video file can be played on the offical build
[Galaxy S III Original Android Development] Noobkid77:
Lol maybe :confused::p
[Galaxy S III Original Android Development] ArdaCsknn:
Yeah there is some problems with video recording but didnt face any issues with playback.But dont use custom kernel if you dont want to face another problems.
[Galaxy S III Original Android Development] anarchist1017:
I didn't face any issues with video recording..video playback is smooth in the experimental build...could play x265 animes 10bit on s/w mode no lag..phone barely heated up
[Galaxy S III Original Android Development] rocciacoraggiosa45:
hello news, when bug appear, i put my finger on sim card in phone and make a pressure on it and i have back signal and sim :confused:
[Galaxy S III Original Android Development] LuciferIII:
Then it's a hardware problem.

Nice meme though ;)
[Galaxy S III Original Android Development] rocciacoraggiosa45:
how i can make a costant pressure on sim card for permanent fix?
[Galaxy S III Original Android Development] Martell:
I had a similar issue yesterday. Put a small piece of tape + a piece of paper onto the sim card that pushes the card against the contacts and it works again.
[Galaxy S III Original Android Development] minealex2244:
Hmm this story is starting to be interesting. Can you try with another SIM card to see if the problems are fixed? If they got fixed then your SIM card is the problem and you should replace it. If not then the SIM slot is partially damaged. In a repair service they should have a new one for max 5 dollars (it's just a piece of aluminium with some connectors which you can replace at home for free). Doing that, you won't need any piece of paper constantly ;)
[Galaxy S III Original Android Development] minealex2244:
This thread is really quiet for some time. I wonder what happened.

Anyway, as I said (some time ago), I started working on an Oreo build. I'll fix all the errors in building which will appear (now I'll fix something in the kernel) and I hope that it will boot at least. The graphics driver will be broken, WiFi, Bluetooth etc. superbroken but I'll try to fix them. I'm really curious about the result, whether I'll succeed or not. [MENTION=2222292]rINanDO[/MENTION] is a very kind dev who is helping me really much. I'm using his work on S2 to build Oreo for S3. I'll keep you informed about the progress.
[Galaxy S III Original Android Development] fir1996:
Its quite because of slow progress , also great to hear that you are working on 8.0 for s3 really looking forward to this hope you release "alpha" build for testing soon;)
[Galaxy S III Original Android Development] ArdaCsknn:
I also noticed that there aren't many things going on.At least Simon trying his best and you are working on a bootable Oreo build. I'm very thankful.Want to ask why every time a new version of Android comes everything stopping working and brokes?Isn't it using the same drivers as 7.0?
[Galaxy S III Original Android Development] anarchist1017:
Forkbomb has given a exp build of nougat with 99.99% working hwc maybe the next build that is released will be the final for nougat..with few minor adjustments*fingers crossed*
[Galaxy S III Original Android Development] minealex2244:
The answer is that these drivers won't be always compatible with the latest changes in Android OS.
[Galaxy S III Original Android Development] qb74:
oh it's gonna take a while till he merges the hwc-working LOS14.1 commits to official builds, considering how 'many' people report bugs (could be really wrong here) :D

honestly, you should consider helping forkbomb with the HWC on the experimental build, would be a lot more benefficial than a buggy oreo release.
[Galaxy S III Original Android Development] minealex2244:
I would do that but I'm not good at graphic drivers :'( But hey I will try some fixes for Oreo (after I get it working, at least a working WiFi :eek:).
[Galaxy S III Original Android Development] dev.xda:
lineage-14.1-20171122-nightly-i9300-signed.zip

sha256: Hash type not supported

?!?
[Galaxy S III Original Android Development] Martell:
Yeah, that was a McGyver solution, worked within 5 minutes. However, I am capable to change the sim card slot or even repair a phone electronically, I have become too lazy to do it. I needed to do it very fast for my daughter as a second phone for her second sim card for only some weeks of her time of visit our home. :cool:

---------- Post added at 17:05 ---------- Previous post was at 17:00 ----------

It's off topic, but serious - Google Play is evil!

https://qz.com/1131515/google-colle...ons-even-when-location-services-are-disabled/
[Galaxy S III Original Android Development] dana.marivani:
negative
[Galaxy S III Original Android Development] Noobkid77:
Hi [MENTION=6371648]minealex2244[/MENTION] this is off topic I was wondering since you using the S6 with a custom ROM are your fast charge speeds affected in anyway. It will go a great deal into me deciding on an S6 on future
[Galaxy S III Original Android Development] minealex2244:
I'm dualbooting stock 7.0 and 8.0. Fast charging is still working on 8.0 even if it doesn't say that it is in fast charging mode.
[Galaxy S III Original Android Development] nobuteru:
Hello,

sorry if it isn't the correct place where ask help/info

I have a 100% working S3 I9300 international, if I put lineage 14.1 last version 22 November, back camera and flash light doesn't works (every fine only MTYP host error when I use resource explorer apps), when I open any camera sw it told me can't connect to camera (screen black), I have done some search and follow also :

xdaforums.com/galaxy-s3/development/fix-camera-stopped-error-samsung-based-t2499158

I got rear camera fw version AKFJ03

phone fw version AKFJ03

can't upgrade camera firmware button disabled

secret code doesn't work on lienange, so I re-fash original stock ROM, I also read to copy original firmware driver from /system/cameradata

but there aren't any *.bin file only two yuv

also check /system/etc/ but not camera directory or firmware

someone can help me to get full lineage 14.1 working?

sorry for bad English

thank you have a nice day
[Galaxy S III Original Android Development] Noobkid77:
That's awesome :) because I'm having a hard time deciding on the LG G5 and S6 for 2018 but I'm glad to hear the S6 still has Fast charge :D
[Galaxy S III Original Android Development] minealex2244:
Think about S7 which has external storage and is water resistant. If you don't want it then S6 is the phone for which I'm working (on its kernel) and it is super powerful.
[Galaxy S III Original Android Development] zarere:
Is that a i9300 thread or I'm wrong?Guys please use private messages or something.We don't want to read things about different phones in a thread specifically created for i9300.Thank you in advance.
[Galaxy S III Original Android Development] minealex2244:
Uhm... Dualbooting is still i9300 related ^_^. Sorry for offtopic.
[Galaxy S III Original Android Development] :
Hi, I recently installed the ROM. it works nice, although, the charging speed is very slow. like 2% in an hour slow.

Any recommendation for kernel to solve this problem?
[Galaxy S III Original Android Development] anarchist1017:
https://xdaforums.com/galaxy-s3/development/kernel-boeffla-kernel-2-2-stable-27-03-t2449408

You cannot change the charge rate on stock kernel..u need to flash a custom kernel(above) for this ROM..you will have option to change the charge rate

This is the only custom kernel for s3 with active development for this ROM
[Galaxy S III Original Android Development] curiousrom:
Charging Rate App? Battery Status LED Notifications? Black Screen Death

I don't think it's a ROM or Kernel problem because when you turn off the phone & plug it in a wall charger the ROM is not involved. Try an other cable or make sure your charging port does not have some pocket lint inside preventing a good contact. I used a toothpick & vacuum cleaner on the mic hole as well to fix a low volume recording level.

When running Neatrom 4.3 on my I9300 I used the Play Store app Galaxy Charging Current Free which showed the charging current (mA) and changing cables it told me if the cable was bad but it's not working with Lineage 14.1. Edit: The app got updated and now works fine with Lineage 14.1 with root.

I also tried Accu​Battery but it gave the "charge controller" error in Lineage 14.1 shown in the screen capture below.

If somebody knows an app that works with Lineage 14.1, please tell me.

Meanwhile a hardware alternative is a very cheap in-line USB power meter on Fleabay like shown in the attachment below. I ordered one but it will take 2 months+ to get to my village on top of a mountain cloud forest. :rolleyes:

S3's charging ports are known to be problematic according to a tech I talked with and as our S3's are getting old they don't hold the USB cable firmly in place anymore.

I ran Neatrom 4.3 on my I9300 for a couple of years but recently I was getting the dreaded black screen of death when keeping the phone plugged overnight. After pressing the Power button for 8 seconds to reset, the battery nearly always showed 100%. It also started to shutdown randomly while unplugged more & more. That got me to try this Lineage 14.1 & the problem showed up again but only when plugged & fully charged.

Last night with TWRP I formatted the internal memory, wiped everything & installed lineage-14.1-20171122-nightly-i9300-signed.zip & open_gapps-arm-7.1-nano-20171123.zip & addonsu-14.1-arm-signed.zip. Right after booting I ran this sequence 4 times to try to fix the random freezing problem as recommended by some S3 users: Dummy file Generator > Internal memory > Generate dummy files until Storage is full (it may freeze before reaching 100% but will get higher the next time you do it) > delete all the dummy files > run Trimmer (help to restore NAND Chips performance) & repeat both apps 4 times.

I will report after a couple of days if it fixed the problem or not. And will buy an other cable just in case.

Battery Status LED Notifications?

I can see the battery LED notification turning red when the battery is low, yellow when charging but noticed that it turns solid green when reaching 91% and when near 100% it's solid, then starts pulsating after a while then sometimes turns off and repeat the solid & flashing cycle a while later. Is it the same for you or a quirk on my phone only? It could be related to my sudden death problem. I tried with an other battery, same results.

+++

Don't be shy & click Thanks if a post is useful to you. :good:

+++
[Galaxy S III Original Android Development] aser_elhbayeb:
Galaxy Charging Current is working for me or at least I can make it work,

but I'm afraid I can't tell you how here in the post because of the forum rules.
[Galaxy S III Original Android Development] curiousrom:
Ampere Charging Current App NOT Working!

Did you change the "background service settings" in a Galaxy Charging Current Pro version? If so what is that value?

Anyway I found the free Ampere which is showing the maximum 1,000 mA charging rate for my S3 with a wall adapter of at least a 5v 1A output capacity.

Sorry guys for wasting your time. I was wondering why Ampere was not showing the discharge rate when the phone is disconnected as advertised on it's Play page and found out that it was showing fake charging data not based on the phone itself but on the "USB cable/charger configuration" according to the app developer.

You can swipe the panel in the app & you see the new screen cap where Charge rate & Max USB curr. are blank. :rolleyes: So the big 1000 mA on top is a lie.

There is a function in the app to produce a System Info screen: "Touch 6 times the Build version in Settings/About Ampere" so that's the second capture with several errors & stuff missing. I am also posting the report here as charging/discharging data was readable but some apps in my S3 I9300 running Android 4.3 & seem broken in Lineage 14.1 for our devices.

The third screen capture was made with Logcat Extreme (Settings > priority level > Errors) where I counted 200 "BatteryStatsService: no controller energy info supplied" errors in 5 hours.

##App info

Ampere Version: v2.13

##Device info

Model: samsung, GT-I9300

Brand: samsung

Hardware: smdk4x12

Android version: 7.1.2 (25)

Build ID: NJH47F, m0

Board: smdk4x12

Display: lineage_i9300-userdebug 7.1.2 NJH47F 2d0f3bbed8

Product: m0xx

Cpu: armeabi-v7a

##Battery Manager info

Status: CHARGING (2)

Health: Good (2)

Plugged: AC (1)

Level: 57

Temperature: 30 °C

##Charge info

Charge Type: ---

Charge Rate: ---

##Battery Manager properties

Capacity: 57

Charge Counter:* NOT SUPPORTED

Current Average: 100

Current Now: 999

Energy Counter:* NOT SUPPORTED

##Old Measurement Interfaces

Sorry, no interface found!

##Measurement Service

Background service is NOT running

Charging state: Charging

Plugged state: AC charger

Health state: Good

Error state: ---
[Galaxy S III Original Android Development] Flegmon:
People are talking about charging meanwhile i have 307 percent
[Galaxy S III Original Android Development] curiousrom:
Camera Problem & MTP temp fix

How did you find your camera firmware version so I can check on my S3 I9300 w/ camera working fine on lineage 14.1 last version 22 November 2017?

Did you try with the free apps Camera FV-5 Lite or Open Camera and rebooting?

While it does not affect my camera which is set to save to external SD card, to temporary fix the MTP error if you are rooted & enabled Developer options: Settings > Developer options > Select USB Configuration > select Charging then go back and > Select USB Configuration again > select MTP. Or reboot.

---------- Post added at 12:25 PM ---------- Previous post was at 12:20 PM ----------

OMG! Do you live in the Fukushima Daiichi nuclear disaster zone?
[Galaxy S III Original Android Development] nobuteru:
Hello!

I used *#34971539# secret code on I9300 with original Samsung's ROM, android 4.3, I think, is impossible with Lineage, secret codes doesn't works

yes sure, with open camera always on Lineage, only black screen, I think it is a driver problem, today I rooted with Odin and cf auto tar file my phone, and I saw /data/cfw "SlimISP_AK.bin", I have done some search with driver name AKJF03 with google, I only find some Russian sharing their photos, if it is a rear camera driver , if I copy it on my PC, after flashing Lineage where I have to put it or to do, to make Lineage use it?????

My test was done on the same phone with only original Lineage 14.1 ROM, no GApps, root or so on... (like kernels, I didn't know there are)

I not have any idea what to do, can you tell me where to post it to get help?, here I think is for developers and testers...

Thank you, I will try, when I have to test some workaround to solve rear camera problem, my I9300 was of my mother, it died, I repaired it with new logic board, rear camera was included, I think that camera is specific for Russian market and maybe no Russian loading Lineage on I9300 international, so no logs about it with that specific driver...
[Galaxy S III Original Android Development] Bojmjma:
[MENTION=4122877]curiousrom[/MENTION]

I converted "Galaxy Charging Current" app to a system app and it worked for me.
[Galaxy S III Original Android Development] aser_elhbayeb:
No, the solution is related to some other app.

The max charging current for i9300 is 1000 mA on wall adapter, and 500 mA on usb, and changing these values is a Kernel modification.

I checked the app's accuracy through a low quality cables, where it starts at 1000 and it keeps dropping till 500, while on other good quality cables the current is stable at 1000 (also checked through Ampere).
[Galaxy S III Original Android Development] curiousrom:
Camera Not Working, Firmware & Driver

Correct the code does not work in Lineage.

"SlimISP_AK.bin" - Here is an old I9300 XDA thread & the OP speaks about SlimISP.bin & using dial code to flash back camera driver to phone so it would not work with Lineage but maybe there is an alternative method in the thread or your could pm him? Galaxy S III General > JB 4.1.2 and Camera Driver

Here a Russian guy said "I have (note 2) camera firmware AKFJ03. Because of this, the camera does not work on the 4.4.4 custom" according to Google translate.

"...I repaired it with new logic board" - The plot thickens! Was it a I9300 mobo?

Please report back if you find a solution elsewhere. Just curious.
[Galaxy S III Original Android Development] dana.marivani:
[MENTION=4122877]curiousrom[/MENTION]

I have this problem too charging is very slow I'm sure of the battery and charging cable

In normal mode, when I need a battery with the app CPU X I will test Maximum voltage and minimum voltage 3700mV &4000mV But if I restart my phone voltage4200mV Arrives

This is my personal opinion

Excessive use of Memory will slow down charging ,In the settings section>Memory>Apps start on boot>Stop every application that you did not need right now

This method has a little effect on my charge
[Galaxy S III Original Android Development] Logan:
I got a better record ??? 4 years old lit battery
[Galaxy S III Original Android Development] Noobkid77:
Wow you don't see that everyday :laugh::laugh::laugh:
[Galaxy S III Original Android Development] lollo.21:
guys do not decompile a apk for some time, are there new programs to decompile apk with nougat and windows 10?
[Galaxy S III Original Android Development] curiousrom:
Ampere Charging Current App NOT Working!

What a waste of time, sorry! Found out that Ampere is not working in lineage-14.1-20171122-nightly-i9300-signed.zip, it's just fake charging data. I edited my post in the previous page with some info and 200 BatteryStatsService errors in 5 hours according to Logcat Extreme. And that's not while running a battery app.

Here is a screen cap of an other app "Charging current" not working.

Still looking for an app that would report charge/discharge rate for Lineage 14.1 on I9300 that would work like it did in Android 4.3. Edit: Galaxy Charging Current Free got updated and is now compatible with S3 i9300 LOS 14.1 with ROOT. Shows charging rate (mA) but not discharging rate running on battery due to S3 limitations.

***
[Galaxy S III Original Android Development] nobuteru:
Hello ,

I have read already saw that threads, so now I have opened my S3 removed rear camera, on the flat cable is written 7100, for me is for the note 2, I think I have got mobo + old rear camera from supplier, maybe is that or maybe isn't so, I am checking, I just want to ask, if I need to buy a S3 rear camera this is it the correct one? (from pictures on the cable gt-i9300 v1.2g, For Samsung Galaxy S3 iii i9300 i9305 T999 I747, I sent message to supplier)

https://it.aliexpress.com/item/Repl...-5b48-4d2d-bf4d-f4754ff504e8&rmStoreLevelAB=3

the history of this S3 :

1) old mom's phone... destroyed, I mean mobo, so I bought new one mobo, I replaced it by myself

2) 100% working, everything

3) with only lineage, no gapps, root and so on, no rear camera no flash light working

4) re-flashed original firmware, come back to point (2)

5) today I removed rear camera and put old one, now S3 is very slow, camera doesn't work, secret code to update rear camera flash crash

I don't know if old rear camera "burned" like old mobo, or if I need to reflash stock ROM

I will keep updated, let me test also a factory reset

please I need from someone info about rear camera I want to purchase, if I must do that

thanks,

bye
[Galaxy S III Original Android Development] curiousrom:
I would have stopped right there or maybe flash a custom proven ROM like NeatRomLite I9300 4.3 which I used for 2 years w/o any problems.

In this ifixit guide (with nice photos) Samsung Galaxy S III Rear-Facing Camera Replacement they sell (expensive) a "Galaxy S III and Note II Rear Camera" compatible with both model but not all models.

Good luck!
[Galaxy S III Original Android Development] anarchist1017:
Will project treble be in anyway helpful for Oreo porting on our s3??..or is it just for newer models?....just curious
[Galaxy S III Original Android Development] alanzhoffmann:
It's just for new models, the ones coming with Android 8 out of the box and updated with Treble (not all of them getting Oreo will have it)
[Galaxy S III Original Android Development] nobuteru:
I will try to find a rear camera from chinese reparing center in my city, if I don't succeed, I will buy the one show here, I am chatting just now with seller, but my next update will be in February or March... I hope Lineage 15 (android 8.1??) will be out :D:p

I would like to put on Lineage 7.1.2 because allow me to use extern sd card as internal storage, Lineage is updated, security patch level november, stock rom... still in 2015, with Lineage I can use apps that not run on android 4.3, the main problems that I have with Lineage are :

mtp host error, a little bit boring and noise, but not so important, I will try your workaround

rear camera that I hope to solve it soon

I hope it's connected with rear camera firmware not compatible (as I see today with broken camera and stock ROM test), but I see Lineage rebooting by itself, I see when go out from home and lost wifi signal and when I come back in house and it try to reconnect to my wifi net, this is very serious, I have to put pin os sim card and I am not "online" with phone net for incoming calls, I hope not a real bug

however thanks anyway!

Hope to update you soon
[Galaxy S III Original Android Development] minealex2244:
Good news and bad news:

I was working all day on Oreo and I got to 77% to build it (previously I got to 14% and then got an error). I'm close to the final build :)

Unfortunately everything will be broken (maybe even the boot up). Even SELinux is broken. It will be just a proof of concept, just a simple Oreo taste but I'll try to fix bugs in my free time. Until then my biggest hope is that the build will at least boot up.

Again, if anyone wants to contribute you are free to do it. Just PM me.
[Galaxy S III Original Android Development] curiousrom:
Wi-Fi Causing Reboot, Freeze, Crash Bug Workaround - Static IP

This is a known bug on current Lineage 14.1 for S3 I9300 for some users on some Wi-Fi networks and related to DHCP.

The workaround suggested by some users & the S3 ROM's developer is to set a Static IP for your S3 on the network causing problem. You cannot set your S3 to have a static IP for all networks, all the time. Only for a given network when connected to it.

Wi-Fi reboot or crash workaround set Static IP on your S3 for that network:

1- Connect to the Wi-Fi network that causes the problem

2- Settings > Wi-Fi

3- Long press that network's name

4- Modify network

5- Advanced options

6- IP settings > tap DHCP & change to Static

7- Save or go back

You can test by walking out of range of the Wifi network and back in range again.

Please add known bug & workaround to the F.A.Q. in post #1 Mr. LineageOS 14.1 for S3 dev & OP [MENTION=5405215]forkbomb444[/MENTION] )

***
[Galaxy S III Original Android Development] Simon_29:
Thank you [MENTION=4122877]curiousrom[/MENTION] for your instructions. I think [MENTION=5405215]forkbomb444[/MENTION] should add it to the F.A.Q. because it will be asked again and again.