GCam Port | Google Camera APK v9.2 (May 2024) › Forums › Samsung Device Forums › Galaxy S3 GSM – i9300 › Galaxy S3 LineageOS 14.1, Nougat 7.1 ROM
- This topic has 87 replies, 30 voices, and was last updated 5 years, 3 months ago by Siba.
- AuthorPosts
- February 6, 2017 at 1:32 PM #12401Linux UserParticipant
Thanks for the clarification. Which means the WiFi is working.
February 6, 2017 at 1:34 PM #12402Linux UserParticipantSimilar issue was reported for Galaxy S3 as well: GApps not working on Galaxy S4 Lineage 14.1
I doubt if this is a Lineage 14.1 BUG !!
Wait for the upcoming releases or verify the same with the unofficial build and see if the behavior is same.February 6, 2017 at 1:42 PM #12404Linux UserParticipantHi,
I am on14.1-20170113-UNOFFCIAL-i9300 and do not face these issues. GPS and Wifi are working fine.I have sudden reboots sometimes.
I asked previously how to debug, but no answer. :-(
But still, this is the best I saw for last years.
BR./Miro
February 6, 2017 at 5:06 PM #12416Linux UserParticipantHi miro, thanks for the update.
Sudden reboot may be caused by a kernel panic or kernel crash. Obviously I can help you finding the logs but you have to download the code and start debugging by yourself for now.
I am planning to write few topics which will help a user (precisely an advanced user) to capture logs, download and analyze source code to find out a possible BUG in the kernel. Why I said kernel, is because an application BUG will not cause the phone to reboot but a kernel bug can. Unable to write on those topics because of lack of time. Please forgive me for that, but I will write it very soon for sure.
February 6, 2017 at 5:18 PM #12419Linux UserParticipantSorry I forgot to mention how to get the logs.
In case of a kernel panic, below file will be generated:
/proc/last_kmsgThis file will not be there in case of a normal reboot. So, the next time your phone reboots, you can capture the above file using ADB. I hope you know the command how to capture the file.
If not then use the following command:
c:\ adb shell
# cat /proc/last_kmsg > /sdcard/last_kmsg
# exit
$ exit
c:\ adb pull /sdcard/last_kmsg
Analyze the log. To find out the actual BUG you need to have the same source code from which the ROM is built ! I hope this will work for you. :)
February 8, 2017 at 2:59 PM #12514Linux UserParticipantAbout the changelog of the new build
lineage-14.1-20170206-nightly-i9300-signed.zip ???February 11, 2017 at 12:40 PM #12661Linux UserParticipanti want to update to lineage os nightly official from liniage os 14.1 unofficial. do i have to wipe data???
February 11, 2017 at 8:26 PM #12675Linux UserParticipantThere are a few bugs in this:
MTP host sometimes crashes randomly
Serial Number (Hardware) changed after installation – network still works
Smooth, but lags in some Messenger (FB) games e.g. Bat ClimbNot sure if software related but sometimes, when charging it only recognises as charging of USB rather than AC.
However, it is generally smooth with most other things and good enough for daily usage.
February 11, 2017 at 9:23 PM #12680Linux UserParticipantIf you are on CyanogenMod 14.1 then you need not to wipe data but there is a procedure you need to follow: How to upgrade from CyanogenMOd 14.1 to Lineage OS 14.1.
If you are on other ROM then you need to wipe(most probably).
February 15, 2017 at 5:52 AM #13140Linux UserParticipantHi,
I’m on lineage-14.1-20170206-nightly-i9300-signed.zip but, when I try to update to lineage-14.1-20170213-nightly-i9300-signed.zip , get this error (image), similar when I install SU. I did a clean install before this update.
- AuthorPosts
- You must be logged in to reply to this topic.