[OFFICIAL][WEEKLY][7.1.2] LineageOS 14.1 for i9300

Search This thread

kabatronix

Member
May 1, 2010
5
19
Bluetooth issue confirmed on 15.03 build

reproducable on two independent devices running latest 15.03 weekly.
Reboot is quite brutal, reseting i.e. ringtone to default

No Bluetooth issues with 08.03 build

kabatronix :)
 
  • Like
Reactions: Klaerchen

stewazy

Senior Member
Oct 20, 2015
126
19
Can someone give me the last stable build of CyanogenMod 13 I wanna go back to it and wait for a bit before trying lineage is again. Root detection does not work properly, it gives me only ADB. Also YouTube app froze on me for a couple of times. I had to reboot the phone. Thanks in advance. Also battery drains way too fast, I have everything on greenify except Gmail.
 

Logan

Retired Forum Moderator
Who missed touchwiz style?!
Here is some screenshots of nova launcher with DreamUX leaked icons (S8) and some widgets, all information will be added soon.

(Screenshots from my i9300)
 

Attachments

  • Screenshot_20170319-201609.jpg
    Screenshot_20170319-201609.jpg
    86.2 KB · Views: 378
  • Screenshot_20170319-201720.jpg
    Screenshot_20170319-201720.jpg
    97.6 KB · Views: 370
  • Screenshot_20170319-201007.jpg
    Screenshot_20170319-201007.jpg
    58.7 KB · Views: 374
  • Screenshot_20170319-201108.jpg
    Screenshot_20170319-201108.jpg
    60.8 KB · Views: 368

minealex2244

Senior Member
Jan 29, 2015
1,503
1,581
24
Baia Mare
When screen off viper4android is getting killed did any one noticed the issue.

I can't confirm it. ViperFX is working without any bugs or crashes.

---------- Post added at 09:34 PM ---------- Previous post was at 09:05 PM ----------

Hi @forkbomb444
the current lineageos for i9300 (all commits until March 18th) has a problem with scanning for new Bluetooth devices.
If I start scanning with no other devices ready for pairing in the neighborhood, then there is no problem, i.e. after some seconds the scanning finishes without results. This can be reiterated without trouble.
If however a pairable device (tried with headset as well as Windows PC) is available, the device is not responding, the little "turning wheel" continues rotating, however after a minute or so, the phone reboots (warm reboot).
This sequence is reproducible. A logcat that starts with a scan of the first type and afterwards with a scan of the second type described, followed by the crash of the system is attached and a last_kmesg.
The lineage build with all commits up to March 8th worked correctly with Bluetooth scans. So it should be a commit in between. Do you have an idea?
Regards,
Klaerchen

4 things:
1. Unconfirmed (tested with 2 devices and I could pair with them and then to transfer files).
2. Are you using Boeffla kernel because I see some "HOTPLUG" strings in your lkmsg? (Do not forget to not report bugs if you are using a custom kernel).
3. Your lkmsg shows us a successful reboot! Everything was shut down safely and voluntary.
4. There isn't any Bluetooth related commit in the period you mentioned.
This thing is unconfirmed.

---------- Post added at 09:37 PM ---------- Previous post was at 09:34 PM ----------

Custom Tiles are ready to be built :D https://review.lineageos.org/164360
 
  • Like
Reactions: Simon_29

Logan

Retired Forum Moderator
I can't confirm it. ViperFX is working without any bugs or crashes.

---------- Post added at 09:34 PM ---------- Previous post was at 09:05 PM ----------
@minealex2244 ViperFX guitaredhero 13.2.2017 zip works just the audio cuts for half sec and continues when turning screen off or switching to background, but viper stays processing same as ARISE works too with selinux permissive (Tested with boeffla kernel).
For viperFX guitaredhero is recommended.

XtremeMusic doesn't process well in LOS in samsung devices causes lag and effect fades out.
 
Last edited:

minealex2244

Senior Member
Jan 29, 2015
1,503
1,581
24
Baia Mare
I can't confirm it. ViperFX is working without any bugs or crashes.

---------- Post added at 09:34 PM ---------- Previous post was at 09:05 PM ----------
@minealex2244 ViperFX guitaredhero 13.2.2017 zip works just the audio cuts for half sec and continues when turning screen off or switching to background, but viper stays processing same as ARISE works too with selinux permissive (Tested with boeffla kernel).
For viperFX guitaredhero is recommended.

XtremeMusic doesn't process well in LOS in samsung devices causes lag and effect fades out.

I'm using LolliViper (ViperFX for Lollipop), an old version and I don't know how later Viper work. I just want stability and LolliViper has it.
 

Klaerchen

Senior Member
4 things:
1. Unconfirmed (tested with 2 devices and I could pair with them and then to transfer files).
2. Are you using Boeffla kernel because I see some "HOTPLUG" strings in your lkmsg? (Do not forget to not report bugs if you are using a custom kernel).
3. Your lkmsg shows us a successful reboot! Everything was shut down safely and voluntary.
4. There isn't any Bluetooth related commit in the period you mentioned.
This thing is unconfirmed.
(1) Interesting, that pairing works on your devices!
(2) The build consists only of the LineageOS repositories without foreign components, i.e. standard kernel. Our devices comes with pegasusq governor which is a hotplugging governor as far as I know.
(3) Could it be, that a warm-reboot of Android does not do a kernel-reboot? Then the last_kmesg dates from my previous reboot to start with a clean environment. Not from the Bluetooth-initiated warm reboot.
(4) The following are the last before Android died:
Code:
03-19 09:16:04.192 10393 10436 E [EGL-ERROR]: void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x4a863808); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3
03-19 09:16:04.193  2015  2400 E BufferQueueProducer: [com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity] dequeueBuffer: BufferQueue has been abandoned
03-19 09:16:04.193 10393 10436 E [EGL-ERROR]: void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x4a863808); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3
03-19 09:16:04.193  2015  3250 E BufferQueueProducer: [com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity] dequeueBuffer: BufferQueue has been abandoned
03-19 09:16:04.193 10393 10436 E [EGL-ERROR]: void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x4a863808); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3
03-19 09:16:04.193  2015  2585 E BufferQueueProducer: [com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity] dequeueBuffer: BufferQueue has been abandoned
03-19 09:16:04.194 10393 10436 E [EGL-ERROR]: void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x4a863808); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3
03-19 09:16:04.198 10092 10584 E JavaBinder: *** Uncaught remote exception!  (Exceptions are not yet supported across processes.)
03-19 09:16:04.198 10092 10584 E JavaBinder: DeadSystemException: The system died; earlier logs will point to the root cause
03-19 09:16:04.202 10092 10104 E JavaBinder: *** Uncaught remote exception!  (Exceptions are not yet supported across processes.)
03-19 09:16:04.202 10092 10104 E JavaBinder: DeadSystemException: The system died; earlier logs will point to the root cause
03-19 09:16:04.203 10092 10105 E JavaBinder: *** Uncaught remote exception!  (Exceptions are not yet supported across processes.)
03-19 09:16:04.203 10092 10105 E JavaBinder: DeadSystemException: The system died; earlier logs will point to the root cause
03-19 09:16:04.782 10122 10122 D AndroidRuntime: Shutting down VM
03-19 09:16:04.783 10122 10122 E AndroidRuntime: FATAL EXCEPTION: main
03-19 09:16:04.783 10122 10122 E AndroidRuntime: Process: com.android.systemui, PID: 10122
03-19 09:16:04.783 10122 10122 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
especially the line:
Code:
E BufferQueueProducer: [com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity] dequeueBuffer: BufferQueue has been abandoned
shows, that the Bluetooth settings app is part of the problem.
 

minealex2244

Senior Member
Jan 29, 2015
1,503
1,581
24
Baia Mare
(1) Interesting, that pairing works on your devices!
(2) The build consists only of the LineageOS repositories without foreign components, i.e. standard kernel. Our devices comes with pegasusq governor which is a hotplugging governor as far as I know.
(3) Could it be, that a warm-reboot of Android does not do a kernel-reboot? Then the last_kmesg dates from my previous reboot to start with a clean environment. Not from the Bluetooth-initiated warm reboot.
(4) The following are the last before Android died:
Code:
03-19 09:16:04.192 10393 10436 E [EGL-ERROR]: void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x4a863808); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3
03-19 09:16:04.193  2015  2400 E BufferQueueProducer: [com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity] dequeueBuffer: BufferQueue has been abandoned
03-19 09:16:04.193 10393 10436 E [EGL-ERROR]: void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x4a863808); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3
03-19 09:16:04.193  2015  3250 E BufferQueueProducer: [com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity] dequeueBuffer: BufferQueue has been abandoned
03-19 09:16:04.193 10393 10436 E [EGL-ERROR]: void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x4a863808); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3
03-19 09:16:04.193  2015  2585 E BufferQueueProducer: [com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity] dequeueBuffer: BufferQueue has been abandoned
03-19 09:16:04.194 10393 10436 E [EGL-ERROR]: void __egl_platform_dequeue_buffer(egl_surface*):1618: failed to dequeue buffer from native window (0x4a863808); err = -19, buf = 0x0,max_allowed_dequeued_buffers 3
03-19 09:16:04.198 10092 10584 E JavaBinder: *** Uncaught remote exception!  (Exceptions are not yet supported across processes.)
03-19 09:16:04.198 10092 10584 E JavaBinder: DeadSystemException: The system died; earlier logs will point to the root cause
03-19 09:16:04.202 10092 10104 E JavaBinder: *** Uncaught remote exception!  (Exceptions are not yet supported across processes.)
03-19 09:16:04.202 10092 10104 E JavaBinder: DeadSystemException: The system died; earlier logs will point to the root cause
03-19 09:16:04.203 10092 10105 E JavaBinder: *** Uncaught remote exception!  (Exceptions are not yet supported across processes.)
03-19 09:16:04.203 10092 10105 E JavaBinder: DeadSystemException: The system died; earlier logs will point to the root cause
03-19 09:16:04.782 10122 10122 D AndroidRuntime: Shutting down VM
03-19 09:16:04.783 10122 10122 E AndroidRuntime: FATAL EXCEPTION: main
03-19 09:16:04.783 10122 10122 E AndroidRuntime: Process: com.android.systemui, PID: 10122
03-19 09:16:04.783 10122 10122 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
especially the line:
Code:
E BufferQueueProducer: [com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity] dequeueBuffer: BufferQueue has been abandoned
shows, that the Bluetooth settings app is part of the problem.
Did you noticed that EGL errors? I see that your HwComposer fails to load a texture. Is not Bluetooth related. For majority of the EGL related errors the SystemUI will crash (you can already see this). If a process crashes then the "host" of that process will die (Settings app) then the system. Simon Shields is already working to fix HwComposer :). Try a clean flash with Aroma GApps.
 
  • Like
Reactions: Klaerchen

LKHN

Senior Member
Aug 3, 2014
200
117
Baku
Download Latest CM13 Build

Can someone give me the last stable build of CyanogenMod 13 I wanna go back to it and wait for a bit before trying lineage is again. Root detection does not work properly, it gives me only ADB. Also YouTube app froze on me for a couple of times. I had to reboot the phone. Thanks in advance. Also battery drains way too fast, I have everything on greenify except Gmail.

Download: cm-13.0-20161220-SNAPSHOT-ZNH5YAO3XN-i9300.zip (307.8 MB)
sha1: 3f081f1017831a97c97ec3ae72dc9788a1c9a9df
Mirrors: Google Drive | MEGA | Yandex Disk | Cloud Mail.Ru
 
Last edited:
  • Like
Reactions: stewazy and xEmre66

LuciferIII

Senior Member
Feb 26, 2016
1,016
574
Prizren
I also have no problems so far.
Only a bit slow and the mtp server is crahsing but that's only the stock file manager and takes no effect to the functionality

Well,that confirms that everyone has the same crash.(even tho it already was a known issue)

---------- Post added at 12:14 PM ---------- Previous post was at 12:11 PM ----------

I hear that our device is the 3rd most popular device with Lineage users.
 
Well,that confirms that everyone has the same crash.(even tho it already was a known issue)

---------- Post added at 12:14 PM ---------- Previous post was at 12:11 PM ----------

I hear that our device is the 3rd most popular device with Lineage users.
Maybe.
It's one of the most popular devices like HTC HD 2 which is still important for many modders.
The S3 will never die!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 181
    zYkSW7S.png

    LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.

    Code:
    #include "std_disclaimer.h"
    /*
     * Your warranty is void.
     *
     * I am not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at me for messing up your device, I will laugh at you.
     */

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.

    Wiki
    Official LineageOS Wiki: http://wiki.lineageos.org/devices/i9300

    Known issues
    @curiousrom has a list of known issues/workarounds. You can see them here: https://xdaforums.com/showpost.php?p=76224958&postcount=4419

    Installation
    (NOTE: if you experience robotic voice during calls: see the FAQ for a fix)
    Upgrading from CyanogenMod/unofficial LineageOS without wiping


    First time LineageOS 14.1 installation on your Galaxy S III:
    • Read the official Wiki page
    • Flash a custom recovery via Heimdall or Odin
    • Push GApps (arm) and the Lineage 14.1 zip to your device
    • Boot into Recovery
    • Perform factory reset
    • Flash the Lineage 14.1 zip from SD card
    • Flash GApps from SD card
    • Reboot

    Upgrading from earlier version of LineageOS:
    • Update your recovery - Lineage Recovery will be done automatically, TWRP can be downloaded from here (NOTE: you need 3.0.2-2 or higher to automatically install updates in Lineage 14.1)
    • Push the new Lineage 14.1 zip to your SD card
    • Boot into Recovery
    • Flash the Lineage 14.1 zip from SD card
    • Flash the most recent GApps for 7.1 if you are upgrading from earlier android version
    • Reboot

    Downloads

    Reporting bugs

    Bug reports belong on JIRA. See our wiki for more information on using JIRA.

    I do not check this thread regularly for bug reports. Using JIRA makes tracking down & debugging bugs a lot easier. Feel free to use this thread to discuss bugs, though :)

    • DO NOT report bugs if you're running a custom kernel
    • DO NOT report bugs if you've modified system files
    • DO NOT report bugs if you've installed xposed and/or other mods
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • See how to submit a bug report for the appropriate place to report your bug (NOTE: the majority of bugs need to go in the BUGBASH tracker, which is only open on weekends).
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues or bugs already reported on JIRA. Any bug not reported in the bug report format below may be ignored.

    Code:
    Phone Informations
    * Lineage version
    * Gapps version
    What you did:
    * Wipe data: y/n
    * Upgrade from previous official cm build: y/n
    * Restore with titanium backup: y/n
    You're using (if yes write which one) :
    * Task killer
    * Phone cleaner / Battery enhancer apps
    * Non-stock kernel
    * Modified kernel settings
    * Other mods
    Bug info:
    * Last version it worked on
    * Repro steps

    Getting help

    You can ask for help on our subreddit, on IRC: #LineageOS on Freenode

    F.A.Q.
    Root?
    Flashable zips to install/uninstall root can be found here. Download the "arm" variants.

    Robotic voice during calls?
    Try using the I9300XXUGMK6 modem. Instructions are here.

    GPS Issues?
    Probably a hardware issue. Try tightening the screws on the back of the device, or see this video for more information (thanks to @baltics for the link)

    The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

    XDA:DevDB Information
    LineageOS 14.1 for i9300, ROM for the Samsung Galaxy S III I9300

    Contributors
    forkbomb444
    Source Code: https://github.com/LineageOS

    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 3.0.x

    Version Information
    Status: Nightly

    Created 2017-01-25
    Last Updated 2018-04-30
    97
    A little Oreo update for you all...

    Linux 4.17 will have support for the S3/Note 2. (So with a little bit of modification, you could install a regular Linux distro and use it on your phone!). I'm working on getting the notification LED driver submitted upstream - it should land for 4.18, probably along with support for the back/menu keys.

    I've gotten audio working, but it's in need of more testing. I also manages to test the camera:
    Yq7qXCO.jpg


    I've managed to successfully load the firmware onto i9300/n7100's modem. Currently I'm working on rewriting the kernel driver that RIL communicates with - Samsung's old implementation was unnecessarily complex, and they made some interesting design decisions in the way the driver behaves... Hopefully that will be done relatively soon - you can watch the progress here
    75
    I've got a few updates for you all :)

    The bad news:
    A few things are broken with the HWC (Video recording is the main one at the moment). I've been quite busy recently IRL, so haven't had much time to work on this.
    Android 7.1.2 doesn't boot, something's super weird during very early boot (it hangs waiting for threads to finish before starting the system server). Fixing this is my priority for the moment.

    The good news:
    I understand a little better how the camera HAL works, hopefully I'll be able to properly fix video recording (instead of using a hack in frameworks like we do now).
    I may even have some more free time in the next few weeks (no promises...)
    67
    Hi!

    Android O has a lot of changes, including to the kernel. Google supports as far back as 3.10 (five years old!). Backporting these changes to Linux 3.0 (seven years old!) might be possible, but no matter how hard I try, the kernel will have huge numbers of vulnerabilities. Going forward, more and more effort will be required to continue maintaining it.

    So, before working on Oreo I've decided to port i9300/i9305/n7100/t0lte to mainline Linux. This is going to take a while - I started working on this in earnest at the end of last year. Currently, there's no OpenGL support - so instead I've been using a traditional Linux distribution to develop on.

    Currently, there's a pretty neat list of things working (keep in mind, I haven't even attempted to boot Android on this yet...):
    • Display + panel brightness (on S3 and Note 2)
    • USB
    • Capacitive keys
    • Hardware keys
    • Sensors (on S3 only)
    • Wifi
    • Notification LED
    • HDMI (untested)
    • Cameras (untested)
    • Touchscreen (on S3 and Note 2)
    • Charging

    Fortunately, the lima project exists for OpenGL on Mali 400. So far, it can render spinning cubes - but I don't think it's quite far enough to handle Android yet...

    That leaves the main things left to figure out:
    • GPS (will require a lot of work - reversing the protocol used...)
    • Modem (I've started working on i9300/n7100, but it's not yet booting fully)
    • BT (should be super easy)
    • Audio
    • Note 2 sensors
    • Note 2 S-Pen support

    You can see my progress in my github repository.
    61
    Reserved

    Builds are up! :)