yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] barathrr96:
Hi.. I had an issue on our los on Feb build.. the phone never unlocks on after screen locked when mobile data on.. my phone is Singapore starhub i9300 .. everything was fine.. I need to restart the phone then to open .. else when in using mobile data I had to not put my phone in lock.

To overcome this I had to flash coffee kernel..

But after some days.. the phone has hanged a lot.. not able to do basic stuffs like calling, WhatsApp too..

So for now I have switched to stock starhub Singapore TouchWiz os..
[Galaxy S III Original Android Development] Dr.N@:
Android Go for s3 is a Chance in near future
[Galaxy S III Original Android Development] curiousrom:
S3 Black Screen Freezing - Sudden Death Syndrome - eMMC Chip Check

Thanks :good: for reporting back, even if it took 3 months. ;)

Could you do me a favor & run this app which is not working on LineageOS but does on Samsung 4.3: eMMC Brickbug Check and post a screenshot as I am beta testing an eMMC memory check app & it could be useful for the dev? My guess is that it will report this:

Samsung GT-i9300

eMMC chip

VTU00M

FW Rev 0xf1

Brick Bug?

Yes. Insane chip.

If you remember I also had a daily black screen freezing problem on my S3 i9300 running the custom NeatROM Lite based on Samsung 4.3 after several years of using it without any problems which got me to try LineageOS & the problem was still there. I solved it as I described here: S3 Black Screen Freezing Fix - Sudden Death Syndrome & now it's been more than 3 months w/o even freezing once running LineageOS 14.1.

It took me a while to figure these out :eek: : for LineageOS users you can get the free app Phone INFO Samsung and check in these panels. If you have the same info then you have the defective eMMC chip and lightning can strike at any time. I would suggest to do as described in the Black Screen Freezing Fix link above as preventive maintenance & it will make your phone faster as well:

HARDWARE

Hardware Revision: MP 1.100

PERSONAL

DEVICE ID

Android Serial Number: 4df13xxxxxxxxxxx the third & fourth character is the firmware revision for the eMMC memory chip. If it's f7 then you are OK.

You can also use the LineageOS built-in Terminal Emulator if enabled in Developer Options & type what is in bold here:

i9300:/ $ su

i9300:/ # cd /sys/class/block/mmcblk0/device

i9300:/sys/class/block/mmcblk0/device # cat type name date serial cid

MMC

VTU00M

06/2012

0x3c930cb7

15010056545530304df1xxxxxxxxxxxx ←←← Check characters 19 & 20

cat cid | cut -b 19,20

f1 ←←←

Note: The | is available in LOS stock AOSP keyboard under: ?123 then tap =\<

Or using adb:

C:\adb>adb devices

List of devices attached

* daemon not running. starting it now at tcp:5037 *

* daemon started successfully *

4df13cxxxxxxxxxx device

C:\adb>adb shell

7[r[999;999H[6n8i9300:/ $ su

i9300:/ # cd /sys/class/block/mmcblk0/device

i9300:/sys/class/block/mmcblk0/device # cat type name date serial cid

MMC

VTU00M

06/2012

0x3c930cb7

15010056545530304df1xxxxxxxxxxxx ←←← Check characters 19 & 20

i9300:/sys/class/block/mmcblk0/device # cat cid | cut -b 19,20

f1 ←←←

***

Unlocking Problem?

Thanks :good: for reporting back. :cool:

Did you install Magisk (+ some modules maybe?) and/or custom kernel instead of the LineageOS super user addonsu-14.1-arm-signed.zip by any chance?

I am following this thread since November 2017 and I did not see any other user reporting a unlocking problem while running stock LineageOS 14.1.

***
[Galaxy S III Original Android Development] lyolic:
Wake up time

I think it isn't normal. Are there any ideas how to fix it?
[Galaxy S III Original Android Development] Ashraf Iraqian:
More free RAM is the only fix ;)
[Galaxy S III Original Android Development] lyolic:
I didn't try myself, but I've heard that in RR it takes about 1-2 second :)

If smb can confirm this?
[Galaxy S III Original Android Development] orgert:
idk , im running the experimental build 14.1 and so far it works great , its been like more than 2 months now and i never had any problem, i dont use any mod , everything is stock, just the rom and open gapps pico :victory:
[Galaxy S III Original Android Development] lyolic:
How long does it take to turn on screen when you receive incoming call?
[Galaxy S III Original Android Development] orgert:
its not instantaneous, but not more than 1 second i think
[Galaxy S III Original Android Development] Robert-R:
Didn't you encounter any camera-crashes?
[Galaxy S III Original Android Development] orgert:
i dont use the camera that much , but i havent had any problem ,im testing it right now ( opening it several times ) its not crashing :victory:
[Galaxy S III Original Android Development] curiousrom:
S3 i9300 In Call Wake Up Time #2

:eek: I don't believe it.

Could you use MatLog as described in the In Call Wake Up Time post & attach the log.txt to a reply?

Please specify: Wifi sleep if on battery, cellular data only or GSM, deep sleep or not.

You ask everybody that question but did not post the time for your S3 lol.

Maybe [MENTION=3526104]Gizmotech[/MENTION] and [MENTION=7830862]barathrr96[/MENTION] who posted a page or 2 ago that they are running Samsung stock 4.3 on their S3 i9300 could contribute a reply?

***
[Galaxy S III Original Android Development] lyolic:
3-5 seconds
[Galaxy S III Original Android Development] orgert:
first call did have a delay, second one didn't , i use s3 mostly for things that need root , and i keep it mostly in airplane mode, as i dont have root on my main phone , (MiA1)

so here u have the log , hope ive done it the correct way , and the app crashed once
[Galaxy S III Original Android Development] ArdaCsknn:
I don't know why but now I can't flash Lineage 14.1 anymore.After flashing the rom it opens the setup wizard and every system app starting to stop.And after few seconds phone reboots itself.Tried 4.3 stock ROM it works well.But I can not able to flash lineage anymore.
[Galaxy S III Original Android Development] curiousrom:
S3 i9300 In Call Wake Up Time #3 - Logcat

Thanks :good: for posting the log. :cool:

You are running [EXPERIMENTAL][7.1.2] LineageOS 14.1 for i9300 on your S3 correct?

I searched your log for hwcomposer and it's not involved when receiving a call & turning on the screen. Here are some selected lines, your system is very lean with no apps interfering during the in call wake up process:

03-14 18:07:20.942 I/DisplayManagerService(2379): Display device changed state: "Built-in Screen", OFF

03-14 18:07:20.966 I/PowerManagerService(2379): Sleeping (uid 1000)...

...

03-14 18:08:27.462 I/Telecom (2379): : Adding new incoming call with phoneAccountHandle

03-14 18:08:27.864 I/Telecom (2379): AsyncRingtonePlayer: Play ringtone.

03-14 18:08:31.247 I/DisplayManagerService(2379): Display device changed state: "Built-in Screen", ON

31.247 - 27.462 = 3.785 seconds. That is similar to my S3 running Official LineageOS 14.1. Time between Play ringtone and "Built-in Screen", ON = 3.383 seconds.

In your second In Call Wake Up time test the phone was not asleep yet as you did not wait long enough after turning the screen off so it was faster:

03-14 18:09:39.462 I/Telecom (2379): : Adding new incoming call with phoneAccountHandle

03-14 18:09:39.798 I/Telecom (2379): AsyncRingtonePlayer: Play ringtone.

03-14 18:09:42.313 I/DisplayManagerService(2379): Display device changed state: "Built-in Screen", ON

42.313 - 39.462 = 2.851 seconds.

"...and the {MatLog} app crashed once - I can see that in the log :) :

--------- beginning of crash

03-14 18:10:50.262 E/AndroidRuntime(5970): FATAL EXCEPTION: main

03-14 18:10:50.262 E/AndroidRuntime(5970): Process: com.pluscubed.matlog, PID: 5970

*****

I checked on a more recent (2015) S5 Mini G800H with similar specs as the S3 (2012) but with more RAM	1.5GB instead of 1GB and running Samsung stock 6.0.1 w/ root and it's In Call Wake Up Time is faster and it turns on the screen first then plays the ringtone: 4.902 - 3.282 = 1.62 second

03-13 00:22:03.282 D/MARsPolicyManager( 1693): SSRMSJ:: detected wakeup!!

03-13 00:22:03.572 D/Telephony( 2416): TelephonyConnectionUtils: getUpdatedSecCallExtra call state[INCOMING]

03-13 00:22:03.622 I/Telecom ( 1693): TelecomServiceImpl$1: Adding new incoming call with phoneAccountHandle

03-13 00:22:04.812 D/InCall ( 3296): - - TURN_ON_SCREEN_FOR_NEW_INCOMING

03-13 00:22:04.812 D/PowerManagerService( 1693): [api] wakeUp (uid: 1001 pid: 3296) eventTime = 71501206

03-13 00:22:04.812 D/InputManager-JNI( 1693): setInteractive(true)

03-13 00:22:04.812 I/PowerManagerService( 1693): !@[ps] Screen__On - 124 : wakeUp: (uid: 1001 pid: 3296) (0)

03-13 00:22:04.812 I/WindowManager( 1693): Screen turning on...

03-13 00:22:04.812 I/PowerManagerService( 1693): Waking up from sleep (uid 1001)...

03-13 00:22:04.832 I/DisplayManagerService( 1693): Display device changed state: "Built-in Screen", ON

03-13 00:22:04.902 I/Telecom ( 1693): SecAsyncRingtonePlayer: Play ringtone.

4.902 - 3.282 = 1.62 second
[Galaxy S III Original Android Development] orgert:
well its not a big deal considering the s3 is 6 years old , and runs 7.1.2 quite good , i've moved on long ago from this phone , but its still fun fashing and trying roms on it :D
[Galaxy S III Original Android Development] curiousrom:
Cannot Flash Lineage 14.1 anymore

That's bad. :eek: Try:

Do a super clean Format Data and wipe as described in this this guide: How to wipe in TWRP properly? and reboot in TWRP Recovery and do the format/wipe one more time & reboot before installing LIneageOS. If all is OK run these apps as described in S3 Black Screen Freezing Fix - Sudden Death Syndrome to fix possible bad memory sectors problem.

Check the integrity of your LineageOS (which version?) download's sha256 as described in this post > step 4.

Or download again LineageOS or try a different build date.

You did not install Magisk or a custom kernel, right?

Install only LineageOS, reboot in System, test & if all is ok you can boot in Recovery again to install Open Gapps and/or LOS addon or other super user.

Good luck & please report back if it worked or not. :cool:

*****

Yes it's quite amazing how well the S3 i9300 keeps going on & running firmware it was not supposed to and I agree: "...its not a big deal".

***
[Galaxy S III Original Android Development] rekibor:
Hi,

I ran into another problem: I still was on nightly from 28.2.18 and this morning the phone re-bootet twice while reading an article through the web browser. Setup was all original, clean flash, SuperSU, no custom kernel or whatsoever. Web browser that comes with Lineage was used. Udated now to the most recent nightly and will come back, if it happens again. It happened couple of times a day when I was still on CM though.

Cheers,

rekibor
[Galaxy S III Original Android Development] blizeH:
Not sure what to do - I've got CWM-based recovery v6.0.4.7 and for some reason I can't get Windows to see the phone in recovery mode, even having installed the drivers via Zadig.

This means not only can I not get Lineage onto my device, it also means I can't replace CWM with Heimdall.

Any suggestions please? Really at a loss here, tempted to give in and get a new phone but that seems really wasteful when I'm 99% sure the problems I'm having with the device are just software related.

Thanks
[Galaxy S III Original Android Development] Kippy51:
And using Flashify from Playstore or Rashr?
[Galaxy S III Original Android Development] curiousrom:
Installing TWRP & Heimdall

Heimdall is hell to install on a Windows PC. If you must, use Odin instead: https://xdaforums.com/showthread.php?t=2711451

Check Odin Install Method (No Root Required) chapter of https://twrp.me/samsung/samsunggalaxys3internationalexynos.html and note that you need to use the TWRP .tar version and the phone must be in Download mode (Home + Volume Down + Power buttons) & NOT in Recovery mode.

When coming from stock Samsung firmware & recovery the Odin (or Heimdall) method is required.

***

For my S3, I copied to the external sdcard the most recent TWRP .img (currently twrp-3.2.1-0-i9300.img) from https://dl.twrp.me/i9300/ and installed it with my old Philz recovery directly from the sdcard & not with Odin or Heimdall.

I'm not sure 100% but it should work also w/ CWM recovery v6.0.4.7 and reboot in recovery after it's done and do a EFS Partition Backup.

Then reboot in System, connect to PC & copy LineageOS, Open Gapps & addon to external sdcard. Or use the phone to download them.

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 Open Gapps & LineageOS su add-on.

I really hate the first part of the LOS install wiki as it's overly complicated with adb to simply copy files to the phone & the cr@ppy Heimdall recommendation for Windows.

Please report back if it worked for you or not.

***
[Galaxy S III Original Android Development] ArdaCsknn:
I'm not able to backup my data because windows not recognizing my phone.I will report back as soon as posibble.

No I'm not using any custom kernel or other things.I tried without flashing gapps but even without it it says google framework stopped.
[Galaxy S III Original Android Development] blizeH:
Thanks, I'm not using either since I can't reliably get the phone to boot, and when it does, Google app constantly crashes, the home screen refreshes, and eventually it restarts again :(
[Galaxy S III Original Android Development] curiousrom:
Can you backup your data to external sdcard?

You don't need those apps to install TWRP. Did you try what I suggested above?
[Galaxy S III Original Android Development] ArdaCsknn:
It looks like this fixed my problem.I don't know what caused it before.

But now my imei not available.And don't know how to fix it.
[Galaxy S III Original Android Development] curiousrom:
No IMEI - EFS Partition Backup Restore Fix

"...now my imei not available." - Restore your EFS partition backup.

If you don't have one or did not include it in a full backup made with TWRP and if you are lucky: install stock S3 i9300 Samsung firmware and if it works again make a S3 EFS Partition Backup - No Service, No IMEI & No SIM Card Fix after installing TWRP that you can use when having those problems when running a custom firmware. That post includes how to restore info & screenshots.

***
[Galaxy S III Original Android Development] ArdaCsknn:
I had a backup in my sdcard luckily.And fixed it last night.Thaanks for your help :)
[Galaxy S III Original Android Development] Robert-R:
Unable to connect to linux via MTP, suddenly.

So far, I always could connect my S3 to my linux-Mint-18.2 _pc via MTP. Today I could not achieve this anymore (Lineage-build 0221).

When I enable MTP-transfer on the S3, the device list on Mint shows "GT I9300", but also the message: "Unable to couple MTP-device" appears.

To avoid its error-message, I had stopped MTPhost; I have restarted it, and rebooted. I have tried an other cable.

Any ideas?
[Galaxy S III Original Android Development] curiousrom:
S3 MTP Transfer Linux Mint Not Working?

The S3 i9300 LineageOS MTP Host is in use when connecting a USB device to the S3 using an OTG cable so you can keep it disabled when connecting to a computer. More info: MTP Host as stopped - Crashing Bug Workaround Fix S3 LineageOS

Did you try with > Developer Options > Android debugging (ADB) enable and when connecting to computer > Notification > tap USB charging this device > Tap for more options > Transfer files (which is MTP)? Does Transfer photos (PTP) work on your Linux Mint computer?

Or w/ Android Debug Bridge (ADB) disabled?

Or reboot computer w/ S3 in MTP mode connected to it?

Try connecting S3 w/ MTP to an other computer (PC if you can). If it works then go here maybe? https://forums.linuxmint.com/

Did your Linux got an update that may have affected the MTP transfer function?

Or update LineageOS to current 2018-03-15?

***
[Galaxy S III Original Android Development] ExTrEmEe:
In which app you have most HWC crashes?

I have only experienced hwc crashing with instagram. Other apps work fine, even instagram over chrome works fine. Youtube, mxplayer, quickpic never crashed hwc. Thats strange.
[Galaxy S III Original Android Development] barathrr96:
Thanks for sharing me some info..

Before I was on RR rom it had the problems like phone not unlocking while mobile data on. so I never locked when mobile data on to use the phone without any issue.

Then I switched to LOS14.1 latest to check whether it persists there. It was there also. Then with one of our xda friend's suggestion I tried kofee kernel which cleared the problems but eventually on time it started hanging a lot and causing other problems like call reception ui never showed up, all apps including phones will not respond and force stop, when wifi or mobile data on all notifications rush up to hang permanently(this is also there in stock os but if not did any action on screen it manages to run). Let me see how I can follow ur shared instructions on that page.

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

I jus now checked with the app mention .. it's shows yes for the insane emmc chip.0xf1

---------- Post added at 10:00 AM ---------- Previous post was at 09:20 AM ----------

Can I follow the procedure for emmc defective chip on my stock os?

After it is successful, should I again perform when installing any other rom?
[Galaxy S III Original Android Development] Robert-R:
Thanks, I have tried your suggestions. (I never could establish an MTP-connection to my Windows-10; some users did, but they may loose data-files on their android-device.)

I suspect that MTP-libraries (libmtp) at my linux-Mint need updating; newer versions are available, but my Mint didn't offer them as updates, so far. I could install them manually, but it is not urgent for me.

File transfer works well via the OTG/ usb-stick; I can use this as a work-around.
[Galaxy S III Original Android Development] curiousrom:
S3 Windows 10 & MTP Driver - Insane eMMC Memory Chip Fix

My laptop runs Windows 10 64-bit & I never had any MTP problems or lost any "data-files" when connecting the S3 to it. Here is a screen capture I just made of Device Manager with the S3 connected in MTP mode:

You can get the most recent Samsung USB driver for mobile package: https://www.samsung.com/us/support/owners/product/galaxy-s-iii-t-mobile >> Manual & Downloads > Software > See more > Device(Install),USB Driver Version 1.5.65.0 JAN 03,2018 29.73 MB

Or direct download here but with above you get the latest version if Samsung updates it: http://org.downloadcenter.samsung.c...USB_Driver_for_Mobile_Phones_ver_1.5.65.0.exe

Some people install Samsung's Kies, connect the phone & after uninstall it as it will not remove the drivers: https://www.samsung.com/us/support/owners/app/kies

Maybe some people are loosing files because of a bad USB data cable or shabby USB hub or touching the phone or cable and breaking the connection? :eek:

"...via the OTG/ usb-stick; I can use this as a work-around. - Good thinking. ;)

*****

Insane eMMC Memory Chip Fix

It weird that you had the same unlock problem on RR & LineageOS. Maybe you did not do a clean install? Format Data & wipe as described in this guide (including reboot in Recovery before installing any OS).

The app Trimmer as described in S3 Black Screen Freezing Fix - Sudden Death Syndrome requires ROOT.

The idea is to run the process on a clean install with the minimum data & apps to be able to clean the maximum memory space. If 75% of the memory is already taken then it will try to find the bad sectors on only 25% of it.

It's not necessary to repeat the entire process after installing an other ROM but using Trimmer once in a while can only help make the phone faster.

You can root your S3 running stock Samsung firmware with Chainfire's proven CF-Auto-Root. Using Phone INFO Samsung > General > if it says Device Type: m0 & Product Name: m0xx then get your firmware version in Settings > About phone then find it here and create a CF-Auto-Root package: https://desktop.firmware.mobi/device:51

You can then use apps requiring ROOT without having to install a custom ROM. Note that it's not required if you want to install TWRP on it as you may know already.

Trimming quotes: when replying to a long post like you did above you can delete some content between
[Galaxy S III Original Android Development] Robert-R:
https://borncity.com/win/2017/08/30/windows-10-has-an-mtp-problem-with-android-devices/

It's dated 2017-08-30, so it might be cured by now.
[Galaxy S III Original Android Development] curiousrom:
Thanks for the link. I never did or tried that but it makes sense:

"You cannot move files between folders located on your Android device’s memory (internal memory or sd card) using Windows 10, because this will cause data loss.

If you want to copy files from on folder to another folder of your Android device, using Windows 10, this operation fails. The files don’t arrive in the destination folder, it just doesn’t work. "

I use a File Manager app on the phone to do that and not when connected to the computer but will try it when I have the time for it.

That said I moved or copied thousands of files between the S3 & PC via MTP & never had any problems.

***
[Galaxy S III Original Android Development] dana.marivani:
I have the same problem,But it's strange I'm taking the phone to a recovery twrp environment

Fortunately there MTP at PC Will appear,Then the files will be transferred

It seems Microsoft has a problem

My system:Win10 pro 1709 64bit

Hoping to solve this problem