yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] dark-ryuk:
calender

[MENTION=4122877]curiousrom[/MENTION]

I haven't tried the method you said many times, but I didn't get any results. from the applications into the clock section of the storage section and I tried to empty the storage section. The result calendar improved.

but when I turn on cellular data usage, the use of cellular data still stands January 1, 1970, and how can we solve this?
[Galaxy S III Original Android Development] djeman:
[MENTION=4122877]curiousrom[/MENTION]

Ok it seems to be important to try so I will launch a full build with the commit (2h needed for a full build and upload ...).

I don't know how to rebuild only the part modified, libcore is a weird folder related at core java libraries.

Edit: It's building with the patch set 4.
[Galaxy S III Original Android Development] curiousrom:
Re: Calendar Date 1969 or 1970 Bug - Patch Submitted for Review!

Thanks :good: for replying. :cool:

Maybe you can ask him for advice in the Bugbash?

Wow, 4 patch sets in 5 hours. Maybe you could wait a little bit as it seems he is still working on it?

***
[Galaxy S III Original Android Development] gellmar:
brunch your-devoce-codename will produce incremental build on second and subsequent builds...

---------- Post added at 01:30 AM ---------- Previous post was at 01:28 AM ----------

Four patchsets as three of them were mistakenly uploaded :P This patch is still a hack but at least it solves the issue for all timezones except Atlantic/South_Georgia (it was buggy in 2018e too).
[Galaxy S III Original Android Development] curiousrom:
Re: Calendar Date 1969 or 1970 Bug - Patch Submitted for Review!

So you are LineageOS's Basil Gello? :) And Official maintainer of Samsung Galaxy Tab S 10.5 LTE (chagalllte)?

Not wanting to start a political discussion here but looking at the way they voted I think that people from Atlantic/South_Georgia are buggy anyway. :D

So no way that your patch can replace an other file via TWRP > File manager or via adb or via a TWRP flashable .zip or edited via a root enabled file explorer so I could help testing it?

***
[Galaxy S III Original Android Development] gellmar:
This patch must be built from source. So now - nothing to replace :P

Also, South Georgia is not the southern district of US state of Georgia. It is a group of islands named also Sandwich Islands near Antarctica..
[Galaxy S III Original Android Development] curiousrom:
"It is a remote and inhospitable collection of islands".

I feel warm & fuzzy here in Costa Rica. :)

***
[Galaxy S III Original Android Development] djeman:
[MENTION=4122877]curiousrom[/MENTION]

I have a first result => https://xdaforums.com/showpost.php?p=78113311&postcount=1864

Yep I know but I'm trying to fix latest bugs and with my spreadtrum soc nothing is easy ...
[Galaxy S III Original Android Development] curiousrom:
Re: Calendar Date 1969 or 1970 Bug - Patch Submitted for Review!

Thanks :good:.

It's great that the patch works for time zone Asia/Kuala_Lumpur in your ROM!

Basil Gello asked in https://jira.lineageos.org/browse/B...issuetabpanels:comment-tabpanel#comment-27513 "...and repeat the steps above for all visible timezones".

Could the user do further tests?

Maybe you should report in that BUGBASH-2492 to make it easier for him to follow the case.

***
[Galaxy S III Original Android Development] djeman:
Ok, yesterday I was tired ... I missed this part of the message ^^

So I will build the rom for my device and I will try myself.
[Galaxy S III Original Android Development] gellmar:
[MENTION=1619533]djeman[/MENTION] [MENTION=4122877]curiousrom[/MENTION]

Managed to fix the parsing of tzdata with changes introduced in 2018f. Patchset 5 works for me on all timezones so far. I will also check with tzdata2018e in a next hour.
[Galaxy S III Original Android Development] djeman:
[MENTION=4122877]curiousrom[/MENTION] [MENTION=5214636]gellmar[/MENTION]

All timezones work except South Georgia GMT-02:00.

But I tried the patch set 4.
[Galaxy S III Original Android Development] djeman:
[MENTION=5214636]gellmar[/MENTION]

With the patchset 5 all timezones work for me too ;)
[Galaxy S III Original Android Development] gellmar:
Great, then you can sign-up at https://review.lineageos.org with your Google account and +1 the change, indicating the devices you tested it on.
[Galaxy S III Original Android Development] curiousrom:
Re: Calendar Date 1969 or 1970 Bug - Patch Submitted for Review!

Thanks! :good:

BIG Thanks :good: for building 3 test ROMs (!) + testing + reporting about it. :cool:

That would be https://review.lineageos.org >>> 233993: ZoneInfo: Exclude boundary tz transitions.

***
[Galaxy S III Original Android Development] Psycho103:
Not asking for ETA. Just want to know, is forkbomb still working on S3 or he stopped? And if he is, what is he currently working on?
[Galaxy S III Original Android Development] curiousrom:
Bye-bye Oreo for S3

***
[Galaxy S III Original Android Development] Sobhan Mazaheri:
Simon Shields abandoned Oreo's project for S3?:crying:
[Galaxy S III Original Android Development] Hesham Sleem:
why you think Simon Shields only one works on S3

oreo is really ported to S3 by [MENTION=5695278]ChronoMonochrome[/MENTION]

and it works fine but we still wait Simon to make 4.2 kernel for our beloved S3
[Galaxy S III Original Android Development] gellmar:
UPDATE: The fix is merged now. Waiting for November ASB to merge and all 14.1 devices will be rebuilt.
[Galaxy S III Original Android Development] curiousrom:
[UNOFFICIAL][8.1.0] LineageOS 15.1 [BETA][11.11.2018]

This [UNOFFICIAL][8.1.0] LineageOS 15.1 [BETA][11.11.2018] for S3 i9300 project is progressing quite fast. As of today:

***

"...we still wait Simon to make 4.2 kernel" - Well looking at his GitHub page https://github.com/fourkbomb I don't see any work done on it in the last month and a half.

So hopefully that Oreo project can work without it.

***
[Galaxy S III Original Android Development] Sly Fox007:
He's probably just busy with exams, which should be done in a week or so.
[Galaxy S III Original Android Development] Nobby1960:
Great thing, well - how do you say here in Germany: Gut Ding braucht Weile = good things take time :good: :good: :)
[Galaxy S III Original Android Development] curiousrom:
Updates for S3 Now Monthly Instead of Weekly

Because LineageOS 14.1 is now in maintenance mode with less changes justifying new builds the LineageOS automated build schedule was changed and the S3 i9300 will get updates only once a month like all other 14.1 devices as explained in the XDA portal here: LineageOS moves to nightly 15.1 builds, monthly 14.1 builds

You can see the original commit here: 234086 (Merged as 19b2b7a ): Nightly + Monthly Builds. (click on lineage-build-targets and search page w/ i9300)

And also here: https://github.com/LineageOS/hudson/blob/master/lineage-build-targets

The next update for S3 i9300 will probably be on 2018-11-15 & will include a November security patch as well as the calendar bug fix ZoneInfo: Exclude boundary tz transitions as seen in https://download.lineageos.org/i9300/changes/

In case of a major bug a new build may be released sooner than a month later so in Settings > About phone > LineageOS updates > 3-dots > Preferences > turn on Auto updates check (screenshot) or manually > 3-dots > Show changelog or visit once in a while https://download.lineageos.org/i9300/changes/

I find it interesting that in the LineageOS subreddit thread Why Make LineageOS Builds With Zero Changes? zifnab06 (Tom Powell, one of the 9 LineageOS directors & dev) replied here "It's an item on a backlog a few miles long. Previously (with cm) this lead to a massive influx of "where's my build" but he is the one that created the commit.

I was suggesting to do an automatic check & if there are no change then don't make a build with no change but they decided to go monthly instead.

Moral: be careful what you wish for. :eek:

***
[Galaxy S III Original Android Development] stephendt0:
Hey guys, quick question - is there much I can do about battery drain on the recent builds? I am seeing around 4.5% battery drain per hour whilst on flight mode, and only Wi-Fi enabled. No Google account signed in, and a clean flash. Android OS is eating 32% of the battery and showing that it has kept my phone awake around 7.5hrs out of 25hrs or so. On the latest available (November 1st) at the moment.
[Galaxy S III Original Android Development] ArdaCsknn:
Turn off Wi-Fi and Mobile Data and wait an hour to test it.
[Galaxy S III Original Android Development] ASVP_MSFT:
I found the app right after I posted the question lol but thanks.

Tried the site but it wouldn't work for me but thanks nonetheless.

Edit: Turns out it was my internet.
[Galaxy S III Original Android Development] ubuntero:
Bluetooth issue - audio noise

[MENTION=5405215]forkbomb444[/MENTION]

Phone Informations

* Lineage version: lineage-14.1-20170206-nightly-i9300

* Gapps version: open_gapps-arm-7.1-nano-20170207

What you did:

* Wipe data: TWRP 3.0.2.2 factory reset

* Upgrade from previous official cm build: n, clean install from recovery

* Restore with titanium backup: n

You're using (if yes write which one) :

* Task killer: n

* Phone cleaner / Battery enhancer apps: n

* Non-stock kernel: n

* Modified kernel settings: n

* Other mods: n

Bug info:

* Last version it worked on: cm-11-20160115-SNAPSHOT-XNH0E0O00N-i9300 and cm-14.1-20161207-UNOFFICIAL-i9300 by pesci2k

* Repro steps

There is audio noise/distortion when using bluetooth headset during voice call. Sometimes there is no audio at all. The logcat in attachment:

~ 23:31 - the bluetooth devices were paired

~ 23:32 - the voice call was set up

PS. The issue was finally resolved by flashing modem as described in post (for internal speaker) and additionally setting up "wb-arm settings" off (for bluetooth headset).
[Galaxy S III Original Android Development] qb74:
what's the best way to update? dirtyflashing the .zip with twrp or manual update through the settings menu?
[Galaxy S III Original Android Development] tugay12:
Both are same, but I think it's easier and safer to update from the settings.
[Galaxy S III Original Android Development] Ashraf Iraqian:
Hi guys

after last update when i put my device to charge ? the LED light ? is too much and paining my eyes! how to make it low led like past?

Thanks in Advance
[Galaxy S III Original Android Development] i9000usersa:
I have the same issue. I had to disable battery charging LED. I would appreciate it if I could make the light slightly dimmer.
[Galaxy S III Original Android Development] tugay12:
Yes, I noticed that too. For now you can try choosing a dark color.
[Galaxy S III Original Android Development] Ashraf Iraqian:
OK but how?
[Galaxy S III Original Android Development] tugay12:
Go to Settings > Notifications > Tap the Settings icon on top right > Select "Battery light" from the list.
[Galaxy S III Original Android Development] Ashraf Iraqian:
Sorry I forgot the place :D

thank You
[Galaxy S III Original Android Development] Ashraf Iraqian:
Wrong Post

Deleted
[Galaxy S III Original Android Development] i9000usersa:
Bump.

I posted this yesterday and already it's many pages back, which I guess is a good thing for development of this ROM in terms of activity, but I would appreciate a little help. Anyone?

I thought also may be it might be a modem issue. Can I flash any of the cwm flashable zip modems from some of the other thrrads in twrp? Does it matter if flash a jb 4.1 compatible modem? I ask because I think I might want to try an i9300T modem, because I read those work better for 850mhz. I am on an at&t mvno which I believe uses 850mhz. Any advice would be much appreciated.
[Galaxy S III Original Android Development] Kippy51:
No answer for your problem, but I wouldn't try flashing through TWRP. ALWAYS flash modems through Odin, after switching off your phone and booting into 'Download' via buttons. Not through the power menu!

You can try 'old' (4.1) modems, but most ROMs recommend the latest one you can find for your device.
[Galaxy S III Original Android Development] noratroll:
the best way generally is clean flash. but usually this is more time consuming.
[Galaxy S III Original Android Development] teddino:
Data usage in weekly cycle time

Hello

I am an italian user and for my carrier reasons I need an data usage cycle time weekly.

This option was already done in old releases:

https://review.cyanogenmod.org/c/55594/

https://review.cyanogenmod.org/c/55595/

someone know why this option are removed from the rom?

Thanks
[Galaxy S III Original Android Development] i9000usersa:
Do you know if I can use mobile Odin? I don't have Samsung drivers installed and I would rather try to keep doing everything on the phone itself. Also, can you explain why op links to a complicated procedure in flashing his modem and not a simple flashing with Odin or whatever? I have read that Samsung stock firmware modems can't be flashed on cm. Is that still true? I guess that would mean I have to find cm compatible modems?
[Galaxy S III Original Android Development] baltics:
Odin was created by Samsung. It enables owners of Samsung devices to flash Samsung software. It also allows owners of Samsung devices to flash TWRP and some other third party software. It is best used with the device connected to a Windows computer.

Lineage ROM cannot be flashed using ODIN.

The method of flashing this ROM is not complicated. It is remarkably straightforward.
[Galaxy S III Original Android Development] Kippy51:
You are changing something in the base of your phone, so I wouldn't advise mobile Odin. To much risk of problems. Of course you can use Sammy modems! I wouldn't know of any 'cm compatible' modems.

Sent from one of my Sammy devices
[Galaxy S III Original Android Development] althon:
You can try here. It's in Russian and there are modem that can be flashed through recoveryhttp://4pda.ru/forum/index.php?showtopic=403183&view=findpost&p=23664775 Just make sure to choose the right one, otherwise you'll loose network connection.
[Galaxy S III Original Android Development] andrescm:
As Odin works for you, TWRP works for me and in its defense I can say flashing through TWRP does not depend on any USB cable, thus shortening the chain and reducing the possibility of something going wrong. I've tried many modems and always flashed them from TWRP, I even made my own zips extracting modems from stock ROMs.
[Galaxy S III Original Android Development] itachi uchia:
You may try to flash koffee kernel with addons and Magisk to root.

It will increase your battery usage. https://xdaforums.com/galaxy-s3/development/kernel-koffee-t3728423
[Galaxy S III Original Android Development] curiousrom:
New Monthly Update 2018-11-17 for S3 i9300 LineageOS 14.1

As explained in the post above Updates for S3 Now Monthly Instead of Weekly the updates for all LineageOS 14.1 devices are now monthly.

The new monthly Update 2018-11-17 for S3 i9300 LineageOS 14.1 is out and contains several valuable changes as seen in the changelog including a November security patch (2018-11-05) as well as the calendar bug fix ZoneInfo: Exclude boundary tz transitions.

It seems like from now on it will be around the 18th. of each month that the new monthly builds for S3 i9300 will be released.

TimSchumi (LineageOS Team Member - Legacy Versions) posted here in the LineageOS subreddit: "It's a new schedule. Every day, two or three devices get built, so that they are evenly distributed across the month.".

***

Battery Drain Feedback?

[MENTION=4586534]stephendt0[/MENTION] - 3 users replied to your "...4.5% battery drain per hour" question. Could we get some feedback on the suggestions or you could Thanks :good: the post(s) who were useful to you as this is the way to learn if a suggestion was helpful or not. :cool:

***
[Galaxy S III Original Android Development] stephendt0:
Thanks for the super detailed reply. Sorry I haven't had a chance to respond, life has been a bit nuts. My S3 is just an old phone I brought back from the dead, so I haven't been able to do much testing, but I suspect that Wi-Fi is the primary cause for my issues. I have multiple Wi-FI APs that share the same SSID, and I find that in some places it'll keep disconnecting and switching Wi-Fi networks on its own, even though there is strong signal to a nearby AP. I have a tonne of other devices and none of them exhibit this issue. Possibly an issue with the baseband I am using. My baseband is I9300UBUGNK1. Will update and provide logs once I get a chance to look into it. Otherwise it is working well.
[Galaxy S III Original Android Development] curiousrom:
Re: 4.5% Battery Drain per Hour? - Wifi Switching & Modem

"...life has been a bit nuts..." - That's good as it ain't boring then. ;)

Settings > Battery and/or BetterBatteryStats > Kernel wakelocks > wlan… may give some clues if it's really Wifi eating the battery.

"...in some places it'll keep disconnecting and switching Wi-Fi networks on its own" - There are a few things you can tweak & see if it makes any differences:

Disable or enable cell data.

Settings > Data usage > Wi-Fi data usage > check if some rogue app is downloading lots of stuff.

Set a Static IP on your S3 for that network instead of DHCP as described in Wi-Fi Causing Reboot, Freeze, Crash Bug Workaround - Static IP

Settings > Wi-Fi > 3-dots > Advanced > Wi-Fi region code > set to Australia like you flag says. I set mine to my region Costa Rica & it did make a signal strength difference including the number of weaker networks the S3 finds.

Settings > Wi-Fi > cog > Saved networks > long press your network > Forget > reboot & reconnect.

Settings > Wi-Fi > cog > Keep Wi-Fi on during sleep > if it's set to Always try Never instead. If it's set to Never then try Always.

Settings > Wi-Fi > cog > disable Network notification. Or enable if it was disabled which is using more battery.

Settings > More > turn off NFC which saves battery anyway if you don't use it.

Settings > Location > 3-dots > Scanning > disable both Wi-Fi & Bluetooth scanning which saves battery.

Maybe the old S3 does not like your network's settings?

You could try some apps like Super WiFi Manager or WiFi Prioritizer but that would be my last choice.

"...Possibly an issue with the baseband I am using. My baseband is I9300UBUGNK1..." - I never found an authoritative answer about it but several advanced users said on XDA that the modem does not affect Wifi.

Anyway I am also using I9300UBUGNK1 (2014-Nov-6) which works best in Costa Rica in combination with my network provider & also tried the most recent S3 modem I9300XXUGOK1 (2015-Nov-25). I attached both as TWRP flashable files to this post. In the OP of that thread you can find NEUGOA1 (2015-Jan-26). That's the 3 most recent modems for the S3 i9300.

Please report back if you fix your issue or not. :cool:

***
[Galaxy S III Original Android Development] KeDbl_DeDa:
curious and how to progress? will it be the core?
[Galaxy S III Original Android Development] stephendt0:
Alright - did a little more testing overnight and now I'm getting great standby time. I think the option that really did it was to only keep Wi-Fi on whilst sleeping when plugged in. For this device, things like notifications aren't that important, and now my battery life is great. Thanks! As for the Wi-Fi switching, I haven't seen it since I disabled Wi-Fi scanning, so we'll see how things go.
[Galaxy S III Original Android Development] Psycho103:
I installed latest SlimKAT for testing, used it for a day and flashed Official LOS14.1 again the internal storage wasn't showing up so I clean flashed it again still same problem. So I flashed stock ROM using odin. Everything was working fine on stock ROM so I flashed latest TWRP using Odin. And flashed latest LOS build (20181117) with arm gapps 7.1 pico and addon su. Now I'm having no network. I clean flashed LOS again to see if that was some problem. Still no luck. IMEI is showing in about phone so there is no invalid IMEI. I've flashed using Odin before. This never happened.
[Galaxy S III Original Android Development] curiousrom:
Re: IMEI Showing but No Cellular Network

Thanks :good: for providing good troubleshooting info.

Try these:

With Wifi off, turn off the S3, wait 5 seconds & turn back on. I had your no network problem a few times when using the Soft Restart option in the advanced Power menu but this off/on or a hard restart fixed the problem.

LineageOS > Settings > Wireless & networks > More > Cellular networks > Access Point Names > APN > and be 100% sure that they are correct. If you make a change turn off/on the phone. To make it easy that's why I recommend to write down the correct working APN settings in step #1 of S3 i9300 LineageOS Super Clean Install & Samsung Firmware

See point #6 in LineageOS S3 i9300 Known Issues Workarounds: 6- Several users reported in this thread having the No Service error (No SIM - Network Unknown) after installing LineageOS 14.1 coming from stock Samsung 4.3 or after updating LineageOS: it can be easily fix if you made previously a EFS Partition backup using TWRP.

More details, workaround if you don't have a backup & EFS Partition backup restore info here: S3 How to do a very important EFS Partition Backup - No Service Fix

What is your current modem/baseband? I attached the most recent S3 i9300 modem I9300XXUGOK1 (2015-Nov-25) and the one I am using in Costa Rica I9300UBUGNK1 (2014-Nov-6) as TWRP flashable files to this post. In the OP of that thread you can find NEUGOA1 (2015-Jan-26). That's the 3 most recent modems for the S3 i9300.

Please report back if you fixed your problem or not. :cool:

***
[Galaxy S III Original Android Development] Psycho103:
Thank you for your help but none of these fix worked for me.

1. Reboot doesn't solve it.

2. I did take EFS backup but mistakenly wiped my Internal storage. So I don't have that.

3. In network settings everything is greyed out so can't change APN.

4. I tried flashing modem still same.

I will try flashing stock ROM again. I live in India so the region code is INS. Can someone please upload latest INS firmware to Drive or Mega? It'll help a lot because I'm having problem in downloading from other sites.
[Galaxy S III Original Android Development] curiousrom:
Re: IMEI Showing but No Cellular Network - No EFS Backup

When doing a backup with TWRP you can select EFS Partition only while running the stock Samsung firmware as described in the links above.

If you did a full TWRP backup including EFS while running LineageOS or other custom firmwares you can restore only the EFS partition if you wish.

You did not say from which sites you tried to download the Samsung firmware but I always had luck & good speed with updato.com.

You don't have to download the Samsung firmware for India, you can get the most recent one if you wish. See https://updato.com/firmware-archive-select-model?q=GT-I9300&rpp=15&order=date&dir=desc&exact=1

You can right-click Download on the chosen firmware page, copy the link & paste it in Internet Downloader Manager for example which downloads via up to 8 download streams. I find it very fast & reliable.

Edit: [MENTION=7619683]Psycho103[/MENTION] - updato.com labels the modem/baseband as "Phone" on their download pages. Checking for the most recent firmware for India INS as you mentioned in this download page it says: Phone I9300DDUGNB1. So you can download the unbranded version (XX) from the EFSv2 Modem Collection thread: XXUGNB1 - *20.02.14*.

If you don't have good reception & data speed with one of the 3 more recent modems linked above you can always flash that one after flashing the most recent stock Samsung firmware & testing it.

***
[Galaxy S III Original Android Development] Psycho103:
I flashed the firmware file I had on my PC. Booted it. Flashed TWRP. Took an EFS backup. Then clean flashed LOS14.1 20181117. Had the same problem again. Restored the EFS and now it works like charm.