[ROM] LineageOS 14.1 for Samsung Galaxy J3 (2016) [SM-J320FN/F/G/M] [UNOFFICIAL]

[LINGGV]

my data usage

 

[PuYaU]

maybe i need full wipe :laugh::laugh::laugh:

Edit: full wipe not solving the issue :crying::crying:

Sent from my Samsung SM-J320G using XDA Labs

 

[oned_gk]

I just flash the latest LOS14 without wipe data. There is no issue with data usage information because i have two months data usage saved in the phone. Maybe full wipe causing the issue.

 

[LINGGV]

is this a bug? I can't turn off airplane mode from the power button

 

[PuYaU]

on build 20-10-2018.. ok :good:

Sent from my Samsung SM-J320G using XDA Labs

 

[bontxa]

I just flash the latest LOS14 without wipe data. There is no issue with data usage information because i have two months data usage saved in the phone. Maybe full wipe causing the issue.

Just a question: if don't wipe data you don't lose user app?

 

[djeman]

Yep if you wipe only cache, system and cache-dalvik nothing is lost.
You can always create a nandroid backup before.

@PuYaU Weird bug :x
It seems to be a lineage bug, I tried a search on google and the first result => https://jira.lineageos.org/browse/R...ira.plugin.system.issuetabpanels:all-tabpanel

@LINGGV I don't know if it's a bug or not ... I will inspecting.
We have all the problem.

 

[bontxa]

Yep if you wipe only cache, system and cache-dalvik nothing is lost.
You can always create a nandroid backup before.

Thanks for the answer. where can i see the differences with previous version?

 

[djeman]

It's hard to describe all modifications ^^
First I update lineage sources at each time so to view lineage modifications it's here => https://review.lineageos.org/#/q/status:merged+branch:cm-14.1

After you can check my commits on github and I wrote a little description when I shared the build :
https://forum.xda-developers.com/showpost.php?p=78051880&postcount=1813

 

[Mahfujurr]

The 2nd November build for j320F has issue with date management. It counts up to the year 2009 and then go back to 1st January, 1970. When the time and date are updated via auto update some apps and setting items get the correct time and date, and others (such as, calendar, massage, notification system) are stuck with the date 1st January, 1970. And so the data usage is showing 0 unit as of 1970. The stock calendar app opens but shows 1st January,1970 as the date and goes up to the year 2009 then go back to 1970. If the stock calendar app is replaced by the google calendar app (from open gapps) the app just crash and close. Please, fix it..! After facing this problem I had to flash the build from June, since it is the last build i kept a backup of.

 

[Alex_Saito]

Is it possible to enable srgb mode?
Sorry for my bad English, but I am from Russia.

 

[djeman]

https://source.android.com/devices/tech/display/color-mgmt
We have nothing for this system if you speak of that.

Maybe the dev option that not works ? I will check.

Edit: I think we need an hwcomposer 2 to have a chance to get the option ...

 

[djeman]

The 2nd November build for j320F has issue with date management. It counts up to the year 2009 and then go back to 1st January, 1970. When the time and date are updated via auto update some apps and setting items get the correct time and date, and others (such as, calendar, massage, notification system) are stuck with the date 1st January, 1970. And so the data usage is showing 0 unit as of 1970. The stock calendar app opens but shows 1st January,1970 as the date and goes up to the year 2009 then go back to 1970. If the stock calendar app is replaced by the google calendar app (from open gapps) the app just crash and close. Please, fix it..! After facing this problem I had to flash the build from June, since it is the last build i kept a backup of.

The 20 october build not have the problem.
j3xnlte => https://drive.google.com/open?id=1oemqsQYMM5RlMvJjjBQU-pwQmugAoHDu
j3xlte => https://drive.google.com/open?id=1rZP9O712OwaoDkO4SAGPAH41ivl5358-

I'm waiting for the fix, the bug is signaled.

 

[MaQeez]

The 2nd November build for j320F has issue with date management. It counts up to the year 2009 and then go back to 1st January, 1970. When the time and date are updated via auto update some apps and setting items get the correct time and date, and others (such as, calendar, massage, notification system) are stuck with the date 1st January, 1970. And so the data usage is showing 0 unit as of 1970. The stock calendar app opens but shows 1st January,1970 as the date and goes up to the year 2009 then go back to 1970. If the stock calendar app is replaced by the google calendar app (from open gapps) the app just crash and close. Please, fix it..! After facing this problem I had to flash the build from June, since it is the last build i kept a backup of.

Running same 2 november build on j320f but i'm not experiencing any problems with the calendar app

 

[djeman]

https://jira.lineageos.org/browse/BUGBASH-2492
Me too I have not the problem, not all users have it ... need more logs and informations on the bug to find exactly the problem.
It seems to be linked at the tzdata update.

 

[Mahfujurr]

Is it possible that by mistake, I flashed the J320FN rom on my j320F and hence the bug occurs.?

Many many thanks bro, for the link of 20 October build.

 

[djeman]

https://jira.lineageos.org/browse/BUGBASH-2492
Me too I have not the problem, not all users have it ... need more logs and informations on the bug to find exactly the problem.
It seems to be linked at the tzdata update.

If you have the bug and if you want to help, the dev on the problem asks for an information.

To all watchers of the bug:
Please show the output of:
"adb shell getprop persist.sys.timezone"
on affected setups.

You can post the result as a reply at this message => https://forum.xda-developers.com/showpost.php?p=78100790&postcount=5148
Adb is not required, you can use a terminal emulator to enter "getprop persist.sys.timezone".

 

[PuYaU]

Is it possible that by mistake, I flashed the J320FN rom on my j320F and hence the bug occurs.?

Many many thanks bro, for the link of 20 October build.

FN model have NFC but F/G/M models dosent have NFC..
bug date 1970 come from lineage os. not come from our maintainer device djeman. so we have to wait for lineage os to fix it first..

this is what i understand now

Sent from my Samsung SM-J320G using XDA Labs

 

[ich0]

Is this a working possibility for our bluetooth? Or is the current instability preventing this? Improve Bluetooth audio quality on headphones without aptX or LDAC by ValdikSS

and can we fork on github to add signature spoofing before building?

NanoDroid patcher isn't working on dirtyflashing your Los14 updates, the survival script completes successfully but after booting the microg self-test doesn't detect any patching of services.jar

 

[PuYaU]

The 2nd November build for j320F has issue with date management. It counts up to the year 2009 and then go back to 1st January, 1970. When the time and date are updated via auto update some apps and setting items get the correct time and date, and others (such as, calendar, massage, notification system) are stuck with the date 1st January, 1970. And so the data usage is showing 0 unit as of 1970. The stock calendar app opens but shows 1st January,1970 as the date and goes up to the year 2009 then go back to 1970. If the stock calendar app is replaced by the google calendar app (from open gapps) the app just crash and close. Please, fix it..! After facing this problem I had to flash the build from June, since it is the last build i kept a backup of.

the 1970 bug is lineage os bug.. not device maintainer fault.. :laugh: stay happy and wait until lineage os developer fix it and after that our device maintainer will up latest build



Sent from my Samsung SM-J320G using XDA Labs