yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] curiousrom:
Most Active Android Versions & Google Play Store Stats

Interesting link, Thanks :good:.

Check Distribution dashboard on Android Developers

and/or the attachment:

***
[Galaxy S III Original Android Development] curiousrom:
Big LineageOS 14.1 for S3 Update 2018-11-01

After skipping the last 4 updates because 3 of them had no changes & 1 had only 2 minor time zone commits the LineageOS 14.1 for S3 Update 2018-11-01 has a lot of meat in it including a Oct. 5 security patch & a Chromium Webview update which is used by the stock Browser as well as many other browsers & apps besides several other commits as seen in the LineageOS i9300 Changelog https://download.lineageos.org/i9300/changes/ with 32 changes in total for this build!

Using the built-in LineageOS OTA updater > Settings > About phone > LineageOS updates > went smoothly as usual: from the moment I tapped Install > automatic reboot in TWRP to full reboot in stable system it took about 9 minutes a shown in a stopwatch.

After testing a little bit everything looks peachy.

Note to [MENTION=5975813]Ashraf Iraqian[/MENTION], [MENTION=4426785]abelenki[/MENTION] & [MENTION=7513127]Nobby1960[/MENTION]: the date in the stock Calendar is fine.

Thank you to the LineageOS Team & [MENTION=5405215]forkbomb444[/MENTION] (maintainer of the S3 i9300) for supporting our device. :good:

***
[Galaxy S III Original Android Development] multiwirth:
I asked for the Nvidia Shield Tablet on it´s thread for LineageOS 14.1 and they told me "because it is based on qualcomm camera and the shield has no qualcomm hardware"

So this device comes with the aosp camera aswell

I don´t know if this is true but what I know, it runs on other devices aswell and I´m not 100% sure but in times of CM13, snap was integrated into the snapshots for the galaxy s3 and in the nightly builds.

Not 200% sure but it should be from a LineageOS 14.1 build for m8:

Probably an very old build since it doesn´t have the QR code scanner and my m8 runs unoffical LineageOS 15.1 since it was released.

Maybe it is even from the old CM13 snapshot builds for i9300 since in both cases, the apk should be the same

Apk attached
[Galaxy S III Original Android Development] ArdaCsknn:
I am wondering what are those changes included in terms of stability and to fix bugs.
[Galaxy S III Original Android Development] Darth Bidder:
The changelog is literally on their site. The link to their site is on the first post.
[Galaxy S III Original Android Development] ArdaCsknn:
I already know but I can't just understand easily what the changes are for. Even I checked one by one and tried to understand something then decided to ask to here. Thanks for your understanding.
[Galaxy S III Original Android Development] ExTrEmEe:
Does anyone have problem with installing apps on latest version? Just clean installed LOS, stock kernel, OpenGApps Pico, and su addon, and cant install apps from playstore or apks.
[Galaxy S III Original Android Development] abelenki:
last two releases are totally broken. the last stable version is lineage-14.1-20181018-nightly-i9300-signed.
[Galaxy S III Original Android Development] ExTrEmEe:
just tried that version, same thing. Then it can be something with opengapps.
[Galaxy S III Original Android Development] curiousrom:
Re: Clean Install, Cannot Install Apps & Open GApps Corrupted?

No problem installing .apk's or from Play Store on LineageOS for S3 i9300 build 2018-11-01 updated from a S3 LineageOS Super Clean Install done in November 2017 & updated at least 20 times since then.

What did you wipe exactly or did you Format Data + wipe as described in that post?

Did you install Open GApps Pico immediately after LineageOS without rebooting in between the two as it must be done? The LineageOS su addon can be flashed at anytime after initial install & reboot.

Exact name of your Open GApps Pico file? For example: open_gapps-arm-7.1-pico-20180528-03.zip.

Check in the phone where you have that file & Open GApps creates logs automatically after you flash it so you could check for errors in open_gapps_debug_logs-2018-your-date.tar.gz and open_gapps_log-2018-11-01.tar.txt for example.

What happens if you go to Play Store > My apps & games & check for updates?

You could turn off the phone then back on & capture a logcat via adb while trying to install apps & look for errors (E/ and/or packageinstaller).

***

That is simply not true @ least for build 2018-11-01. :cowboy:

***

Open GApps Download Corrupted?

Yes. If you go to the download page https://opengapps.org/?api=7.1&variant=pico you can click on Older Releases which I prefer to use for fast direct downloading with Internet Download Manager for example instead of their script.

Most importantly check the MD5 Checksum as linked in their download pages to make sure your download is not corrupted.

In my case recently after a Open GApps download for an other device 3 times on a Windows 10 PC it said download complete but the files were smaller & the MD5 Checksum was all wrong.

For example if you download open_gapps-arm-7.1-pico-20181102.zip download also open_gapps-arm-7.1-pico-20181102.zip.md5 in a different location then use a utility to calculate the MD5 of the main file & compare it to the data in the second file.

7-Zip can do that as well as Hash Checker in the Windows Store for example. (screenshot of a Open GApps download MD5 check fail using Hash Checker)

You can also do it in the phone with a free app like Hash Calc (Checksum Utility) as seen in the screenshot but you can't install apps in your case. :eek:

***
[Galaxy S III Original Android Development] ExTrEmEe:
Wiped system, cache(both), data. Then flashed LOS(lineage-14.1-20181101-nightly-i9300-signed.zip), then OpenGapps Pico (open_gapps-arm-7.1-pico-20181102.zip), then su addon(addonsu-14.1-arm-signed.zip). Everything done without restarting. Some apps installs fine like Viber, Instagram... but Chrome throws error (code:190). So i thought, google apps doesn't work, because of Play Protect certification showing that Device is not certified. So i tried Google Calendar and Maps and it works. Also some apks installs fine, some throws "There was a problem parsing a package." Those apks are not corrupted, because i have used them, so it's something with system.

[MENTION=4122877]curiousrom[/MENTION], thx for confirmation that it works for you, so i can install latest versions, and try to find what's wrong with this.
[Galaxy S III Original Android Development] curiousrom:
Re: Clean Install, Cannot Install Apps & Open GApps Corrupted?

Thanks for the additional troubleshooting info.

So not being able to install any apps vs. not being able to install some apps is different.

Try the suggestions above including Format Data + S3 Black Screen Freezing Fix - Sudden Death Syndrome which may fix some corrupted memory sectors.

Check in logcat for errors descriptions. Maybe you can install SysLog that makes capturing logs fast & easy.

"Play Protect certification showing that Device is not certified..." - That does not matter for the S3 LineageOS. Check this lengthy XDA portal article: How to Fix the “Device is not Certified by Google” Error.

I did those steps & it still shows as Not certified in Play Store's hamburger but everything is peachy.

To try to reproduce your problem I would need to install from Play exactly the same apps you have a problem with but that I have not installed already.

Edit: [MENTION=6104076]ExTrEmEe[/MENTION] wiping Data in TWRP does not wipe internal sdcard. Only wipe internal storage or Format Data does. Check this thread about error 190 & this reply on the next page.

From the clean install post: From this TWRP FAQ page:

***
[Galaxy S III Original Android Development] ExTrEmEe:
[MENTION=4122877]curiousrom[/MENTION] thanks for help. I know that when you tick data, it doesn't format internal storage, I rarely do that, and never had problems(and I did lot of ROM flashing), till now. Just did "format data", then system and cache, installed ROM and gapps and everything works now. Installed su add-on , and everything is still working. Based on logs it was something with permissions and package installer couldn't read files somehow, but it works now.
[Galaxy S III Original Android Development] Ashraf Iraqian:
Calendar not fixed to yet...!
[Galaxy S III Original Android Development] abelenki:
re-install lineage-14.1-20181018-nightly-i9300-signed.
[Galaxy S III Original Android Development] kurtn:
[MENTION=4122877]curiousrom[/MENTION] lineageOS wiki install instruction has changed? In point 7 of install ... Heimdall there is a gap. I see no method to power off from download mode, except removing battery.
[Galaxy S III Original Android Development] curiousrom:
Re: Flashing TWRP on Stock Samsung Firmware

You are referring to the LineageOS Wiki Install LineageOS on i9300.

I can read @ the present under Installing a custom recovery using heimdall:

They should add to step 7: ...and release the buttons as soon as you see the Samsung Galaxy S III logo and delete With the device powered off.

The important point is if you do not disable auto-reboot in either Heimdall or Odin the device will revert to the default Samsung recovery after flashing TWRP.

This is a one time thing as after rebooting in TWRP it will fix that & will always boot in TWRP.

So step 7 should be:

7- Manually reboot into recovery:

Hold Home + Volume Up + Power and release the buttons as soon as you see the Samsung Galaxy S III logo.

You don't have to turn off the S3 in Download mode after the flashing of TWRP is done as you can then reboot directly in TWRP Recovery after unplugging the phone.

Removing the battery @ this stage is not good IMO.

"With the device powered off" is a mistake & I will report it. Or maybe [MENTION=5405215]forkbomb444[/MENTION] will see this post as maybe he modified that Wiki page: https://review.lineageos.org/q/owner:simon%40lineageos.org+project:LineageOS%2Flineage_wiki

Edit: [MENTION=8031265]kurtn[/MENTION] I found an older version of that i9300 install page on web archive & it does not say in step 7 "With the device powered off" http://web.archive.org/web/20171102142712/https://wiki.lineageos.org/devices/i9300/install

Personally I hate Heimdall if on a Windows PC or Mac so that's why I wrote S3 LineageOS Super Clean Install & Samsung Firmware using Odin instead. It's similar to step # 4 in that post:

***
[Galaxy S III Original Android Development] Nobby1960:
I know no other way except to remove the battery, to power off the phone from download mode without a reboot into bootloader. You can try to press the power button for 20 sec.
[Galaxy S III Original Android Development] the-spea76:
Good night. It's to inform that I did the update with the last nightly manually and it's working.:laugh::good:;)
[Galaxy S III Original Android Development] curiousrom:
Re: Flashing TWRP on Stock Samsung Firmware & Removing Battery

Not necessary to turn off the phone as described above I did it 3 times on S3 i9300 while flashing TWRP ,1 time on S5 & 2 times on a S5 Mini, etc: after disconnecting the phone while it is in Download mode you can reboot it directly in Recovery w/o turning off the phone.

For me removing the battery while the device is in Download mode or if it is stuck in a boot loop or frozen is like turning off a car while going @ 50 km/h. Not good & asking for future trouble & corrupted files IMO. :eek:

I remember that some users reported in this thread problems after removing the battery twice to get out of a bootloop but I can't find those posts @ the present.

"You can try to press the power button for 20 sec." - That's the way to do it if stuck in some freezing or boot loop process. It's called a forced Hard reboot & takes usually 8-10 sec.

The power button should be released as soon as the screen turns black so it's turned off instead of rebooting like if you release the Power button later when the Samsung logo of the bootloader process appears.

***

Glad you fixed your updating problem & Thanks :good: for reporting back. :cool:

Edit: "Good night..." - I live in a different time zone (Costa Rica) and good afternoon would be more appropriate as I read your post. ;)

***
[Galaxy S III Original Android Development] the-spea76:
Ok so nice afternoon. Here it's 10pm GMT (in winter time)
[Galaxy S III Original Android Development] unknown_one:
Check out the Galaxy S3 Android Development forums, you will see a surprise :D. Android Oreo for the S3 is now available. Thanks [MENTION=5695278]ChronoMonochrome[/MENTION] [MENTION=5405215]forkbomb444[/MENTION] [MENTION=2222292]rINanDO[/MENTION]
[Galaxy S III Original Android Development] Sly Fox007:
It's just an alpha and it's not very usable yet.
[Galaxy S III Original Android Development] curiousrom:
Guys, why not include a link? :confused:

[ROM][UNOFFICIAL][8.1.0] LineageOS 15.1 [ALPHA]

And why summon 3 devs with a @ in a post that is just a pointer w/o any link or content? :rolleyes:

***
[Galaxy S III Original Android Development] dark-ryuk:
calender

im using samsun s3 and last rom. but There are problems on the calendar. The calendar starts on January 1, 1970. if you correct it. I also get the mtp machine stopped error when uninstalling an application.
[Galaxy S III Original Android Development] abelenki:
install lineage-14.1-20181018-nightly-i9300-signed, until the problem is fixed:

https://mirrorbits.lineageos.org/full/i9300/20181018/lineage-14.1-20181018-nightly-i9300-signed.zip
[Galaxy S III Original Android Development] curiousrom:
Calendar Date Bug & MTP Host as stopped

Welcome to XDA! :cool:

Is your date problem with stock Calendar or Google calendar?

Try > Settings > Apps > Calendar > Storage > Clear Data.

Check in > Settings > Date & time > turn on Automatic date & time and Automatic time zone. If they were already selected by default try toggling off and set date, time & time zone manually.

Then if you have one > Settings > Accounts > Google > 3-dots > Remove account > reboot > Settings > Accounts > Add account Google.

MTP Host as stopped is a known issue. Check the easy fix: LineageOS S3 i9300 Known Issues Workarounds - Bugs

You keep posting this over & over instead of trying to find a solution. :)

IMO current build 2018-11-01 is good for the reasons described here: Big LineageOS 14.1 for S3 Update 2018-11-01.

Here I made some screenshots with your username just for you of S3 i9300 LineageOS 14.1 build 2018-11-01 Google Calendar (downloaded from Play Store) in the first group of 3 screenshots and the other one is the event shown automatically in the stock LineageOS calendar.

The events were synced to my Google account & seen on my other devices' calendars.

On the S3 I prefer the stock LineageOS calendar because it uses less RAM & CPU & uninstalled Google calendar after making the screenshots.

If you guys with a calendar date problem try the suggestions above & if it does not work and you don't submit a bug report with a logcat to the LineageOS Team then it will never get fixed.

See How to submit a bug report.

You can use an app like Syslog to capture logs quickly & easily.

Edit 2: - [MENTION=4426785]abelenki[/MENTION] - I found some recent bug reports: BUGBASH-2492 Calendar date stuck to 1969 / 1970 and REGRESSION-2188 Jan 1 1970 bug so you guys can sign-up in jira, vote up the bug & add your device name, build number & details.

Edited to add: That's on 100% stock Official Lineage 14.1 on S3 i9300 (currently 2018-11-01 updated from 2018-09-27) + Open Gapps ARM Pico + Lineage ARM su add-on for root and TWRP 3.2.3-0. No custom kernel, Magisk, Substratum or system modifications of any kind.

***.
[Galaxy S III Original Android Development] Ashraf Iraqian:
Hi [MENTION=4122877]curiousrom[/MENTION]

thanks for help and exactly about select off Automatic time zone feature ,

i am in Arabian standard time Already and the problem disappeared when i changed the time zone from Baghdad to Moscow...!

and now the calendar is in correct date.

Can you explain this issue?
[Galaxy S III Original Android Development] curiousrom:
Re: Calendar Date 1969 or 1970 Bug Workaround

Thanks :good: for reporting back. :cool:

Well as explained in Calendar w/ Wrong Date & Time Zone Commits LineageOS build 2018-10-25 had only 3 changes and two of them are related to time zone; tzdata stands for Time Zone Data: zoneinfo: Update tzdata to 2018f and icu: Update tzdata to 2018f those were updated in build 2018-11-01 with zoneinfo: Update tzdata to 2018g and icu: Update tzdata to 2018g and probably carried the Calendar wrong date bug.

It could be only for certain time zones as I am in Central America UTC−06:00 without day-light saving changes because near the equator. & my Calendar date is fine while you are in UTC+3 hours. Do you have day-light saving where you live?

I added this to the LineageOS S3 i9300 Known Issues Workarounds - Bugs:

[MENTION=4426785]abelenki[/MENTION] [MENTION=9546895]dark-ryuk[/MENTION] and other users with the Calendar 1969 / 1970 wrong date bug can you confirm that > Settings > Date & time > turn off Automatic date & time and Automatic time zone and set date, time & time zone manually works for you too?

That could be useful info for the LineageOS Team. :cool:

***
[Galaxy S III Original Android Development] djeman:
I think it's a problem on all cm14.1, one user of my rom has the problem ... but it's not an official release so I can't report the bug :x

https://xdaforums.com/showpost.php?p=78085737&postcount=1840
[Galaxy S III Original Android Development] imperiuspt:
hello

this last update on y phone was no good.

How to roll back??
[Galaxy S III Original Android Development] dark-ryuk:
@curiousrom

[MENTION=4122877]curiousrom[/MENTION]

First of all, thank you very much for taking the time and informing me. my problem was in the stock rom. I did what they said, but no solution. I gave my vote by going to the places you directed. because I gave you very valuable information.
[Galaxy S III Original Android Development] curiousrom:
Re: Calendar Date 1969 or 1970 Bug - Working on A Fix

[MENTION=5975813]Ashraf Iraqian[/MENTION] [MENTION=9546895]dark-ryuk[/MENTION] [MENTION=4426785]abelenki[/MENTION] [MENTION=1619533]djeman[/MENTION] & other users with the Calendar wrong date bug: turn back on automatic time & automatic time zone & reboot to reproduce the problem as LineageOS developer Basil Gello and author of the tzdata commits linked above is currently actively working on fixing the problem & requested this in BUGBASH-2492 Calendar date stuck to 1969 / 1970:

Either connected to a computer via adb: Please show the output of:

adb shell getprop persist.sys.timezone

Or on the phone using a Terminal emulator:

getprop persist.sys.timezone

My S3 not affected by the wrong date bug it returns: America/Costa_Rica

You could either post in the Bugbash or here & I will do it for you.

***
[Galaxy S III Original Android Development] Ashraf Iraqian:
Hi

thank you for daily help for all S3 users :good:

i can't use adb feature

but i am used Stock terminal and nothing appear!

SS added
[Galaxy S III Original Android Development] curiousrom:
Re: Calendar Date 1969 or 1970 Bug - Working on A Fix

It seems there is a problem again with the XDA forum attachments as I can't see yours. Try editing your post > Advanced & first delete the attachment & then attach it again.

You could try with the much better Terminal Emulator by Jack Palevich which can copy/paste & send transcripts via email when long pressing the screen but this time try with su if rooted:

su

getprop persist.sys.timezone

***

Edit: [MENTION=5975813]Ashraf Iraqian[/MENTION] I just tried with the built-in Terminal enabled in Developer Options & it works fine without su as you can see in the attachment. Are you sure you did not make a typo & typed exactly:

getprop persist.sys.timezone

***
[Galaxy S III Original Android Development] Ashraf Iraqian:
yes
[Galaxy S III Original Android Development] Ashraf Iraqian:
Edit oh sorry i am typed prop prob it wrong :eek:
[Galaxy S III Original Android Development] curiousrom:
Lol. :D You typed "getprob" instead of getprop.
[Galaxy S III Original Android Development] Ashraf Iraqian:
yeah because i am so tired in the job today :rolleyes:

the problem not fixed!

on Moscow time zone working well but on my timezone not.
[Galaxy S III Original Android Development] dark-ryuk:
I uploaded the last rom, but the calendar didn't improve. my time zone true but calender is 1970

Europe/ İstanbul

i hope this bug fixed as soon as possible

[MENTION=4122877]curiousrom[/MENTION] [MENTION=5975813]Ashraf Iraqian[/MENTION]

I have downloaded google calendars to use. but the application does not open. I'm giving the permissions later when it comes to the first screen. Application closes automatically. I think the calendar application's error is affecting it.
[Galaxy S III Original Android Development] curiousrom:
Update 2018-11-08 Zero Changes & Calendar Bug

There is zero changes in update 2018-11-08 so it will not change anything as seen in https://download.lineageos.org/i9300/changes/

Uninstall Google Calendar because it's affected also and only introduces an other useless variable in the mix.

Europe/Istanbul is UTC+2 but with current DST (Daylight Saving Time): UTC+3 so as described above > Settings > Date & time > turn off Automatic date & time and Automatic time zone.

Then in the same panel > Select time zone > choose Moscow which is also UTC+3 (GMT+03:00), clear Apps > Calendar > Data & reboot.

"i hope this bug fixed as soon as possible"- We all do & a LineageOS dev is working actively on it. The best is to help him with data in BUGBASH-2492.

Like all LineageOS devs he is an unpaid volunteer so patience and a cup of soothing chamomile tea may help meanwhile. ;)

***

Edit [MENTION=9546895]dark-ryuk[/MENTION]: Get a Flag!

Tip: go to your XDA profile in this panel https://xdaforums.com/profile.php?do=editprofile and add info > Devices Samsung Galaxy S3 > Service provider as it's useful for troubleshooting & it will show when clicking the arrow under the username in a browser > City & Home country & then you will get a flag under your username which gives an international flavor to this thread IMO.

***
[Galaxy S III Original Android Development] dark-ryuk:
[MENTION=4122877]curiousrom[/MENTION]

I've done what you said. but back again in the 1969-1970 range. or when I look at the data usage range, it still shows the years 1969-1970.
[Galaxy S III Original Android Development] curiousrom:
Well it works for 2 people. I can't explain why it does not work for you, sorry.

***
[Galaxy S III Original Android Development] dark-ryuk:
Thank you very much for trying to help. It's enough for us to take care of us.
[Galaxy S III Original Android Development] curiousrom:
Re: Calendar Date 1969 or 1970 Bug - Patch Submitted for Review!

Good news, I submitted your info as seen in your attachment in the BUGBASH-2492:

getprop persist.sys.timezone

Asia/Baghdad

And LineageOS dev Basil Gello posted in it:

So the 233993: ZoneInfo: Stop searching on INT32_MAX transitions patch is now up for Review @ the present by some important LineageOS contributors including Kevin F. Haggerty (haggertk) who is one of the LineageOS Directors, Head developers & S5 kltexxx 15.1 family maintainer so we can expect a merged commit coming soon in a future S3 i9300 14.1 update.

[MENTION=1619533]djeman[/MENTION] - Check https://jira.lineageos.org/browse/B...issuetabpanels:comment-tabpanel#comment-27513 if you want to try it right away in your ROM.

***

So the moral of this is that creating or contributing to a Bugbash (bug report) is the best way to help solving a problem instead of just *****in' in some threads. ;)

Note: always search https://jira.lineageos.org/ before creating a duplicate for the same problem which only makes it harder for the devs. And post in it with your device details + vote up + follow it so you can reply to the dev's questions.

***