Motivated by the aptX codecs for CM14.1 bluetooth stack found by dh.harald (https://forum.xda-developers.com/oneplus-3/themes/mod-aptx-codec-t3521228) I present:
APTX (HD) support for CyanogenMod 13 based ROMs - V1.2
I ported the aptx codec offloading support from the latest Qualcomm bluetooth stack over to the bluetooth stack from CM 13. After a full week of porting and bugfixing I managed to get it to work on my Galaxy S5 running CM13!
Please go ahead and test this on other devices (or other Marshmallow based ROMs, if the bluetooth stack's API is equal to the API from CM13, it should work).
If it does not work for you, dirty flash your ROM again, the modification should be overwritten.
Requirements
ARMv7 device (sorry, no ARM64 or x86 support!)
CM13.0 ROM (for 14.X see dh.harald's thread)
aptX capable headset/speaker
Download
aptXforCM13_v1.2.zip (AFH)
aptXforCM13_v1.2.zip (Github)
Installation
1. Install zip from recovery
2. Add the following to the /system/build.prop file
Code:
persist.bt.a2dp_offload_cap=sbc-aptx-aptxhd
Search your log for the line I bt_btif_media: btif_a2dp_encoder_init Selected Codec aptX to see if it works.
Confirmed devices
Samsung Galaxy S5 (klte) on CM 13.0 (SD801)
OnePlus 3 on CM 13.0 (SD820)
OnePlus 3 on BJRR (SD820)
Galaxy S6 Edge+ on CM13 (Exynos 7420)
LG G2 D802 on CM13 (SD800)
Version history
V1.2 - This release incorporates two security fixes for bionic and bt library (CVE-2017-0422, CVE-2017-0602)
V1.1 - Improved A2DP buffer sizes, fixing audio glitches and reduces CPU usage
V1.0 - Initial release
Build from source code
If you want to integrate this mod to your own build/ROM, use the following repositories:
https://github.com/mh0rst/android_bionic for bionic (In repo mainfest.xml: <project path="bionic" name="mh0rst/android_bionic" groups="pdk" />)
https://github.com/mh0rst/android_system_bt (In repo mainfest.xml: <project path="system/bt" name="mh0rst/android_system_bt" groups="pdk" revision="cm-13.0-with-aptx" />)
Impossible to download, ads everywhere, but no file...
ElDonTheo said:
Impossible to download, ads everywhere, but no file...
Click to expand...
Click to collapse
Sorry for that, I didn't realize these sites had so many ads. Will upload to github and AFH this evening, make a suggestion if you want the file somewhere else.
Works fine here on a OnePlus3 with CM 13.0 nightly 20161107 (latest available version). I tested with a VTIN bluetooth 4.0 in-ear headphones.
Thanks a lot for this!!!
Works also fine on Sultan's CM13 for OP3.
Thank you very much for porting this to Marshmallow!
I need for xiaomi mi5.
lockdlock said:
I need for xiaomi mi5.
Click to expand...
Click to collapse
I don't know what bluetooth stack is used by the mi5, at least for their official ROM. Because they are using the Snapdragon 820 processor it might be the standard fluoride stack, which may work. Just try to flash this mod, if it doesn't work, re-flash your original ROM.
I know the mi5 has unofficial cm13/14.1 support, you could try to flash one of those and then try my mod (for cm13) or dh.haralds mod (for cm14.1)
Download is great now, thanks
But I couldn't make it work, it breaks the Bluetooth, which cannot be enabled :/
Galaxy Tab Pro 8.4 - RR unoffical
Same thing as mentioned above, it breaks the Bluetooth functionality.
Flashed it with and without dalvic / cache cleaning on htc one mini 2 with cm13
Does it need specific modifications to get it run?
Off topic: I read something on the forum - Snapdragon LLVM Compiler is just for the system not for compiling apps, right?
ElDonTheo said:
Download is great now, thanks
But I couldn't make it work, it breaks the Bluetooth, which cannot be enabled :/
Galaxy Tab Pro 8.4 - RR unoffical
Click to expand...
Click to collapse
Are you usung RR 5.8.0 or 5.7.4? Can you post a complete logcat of trying to enable bluetooth?
MrAnswer said:
Same thing as mentioned above, it breaks the Bluetooth functionality.
Flashed it with and without dalvic / cache cleaning on htc one mini 2 with cm13
Does it need specific modifications to get it run?
Off topic: I read something on the forum - Snapdragon LLVM Compiler is just for the system not for compiling apps, right?
Click to expand...
Click to collapse
I looked at the logcat you provided and the source of the ROM, but the creator didn't release the manifest used to build the ROM, therefore I can't check for differences between the bluetooth stacks. I don't want to raise hopes, it is very hard for me to solve bugs in combination with devices I don't own and without meaningful logcat or (obvious differences in) the source code.
The only specific modification my mod needs is a small modification to libc (symbols needed by aptx library, which was originally compiled for Nougat), and this is already included in my mod. It is likely that your ROMs modify libc or has a different bluetooth stack than CM13.
The snapdragon compiler AFAIK was introduced with the nougat repositories, and can be used for both system and app compiling (at least the native parts of the apps). I don't use it ATM, because I still compile for Marshmallow based CM13.
Dear @brhorst
I have a SM-G928F and @Rainbow_Dash CM13 ported rom ,
before using your codec :
music streaming Bluetooth work but lot of noise
Call with bluetooth work but lot of noise
after used your aptx codec :
music streaming Bluetooth work weel !!!!
Call with bluetooth work but lot of noise
my question is , can I manage to use the libs for "call throught bluetooth"?
Br
Elkhardioui said:
Dear @brhorst
I have a SM-G928F and @Rainbow_Dash CM13 ported rom ,
before using your codec :
music streaming Bluetooth work but lot of noise
Call with bluetooth work but lot of noise
after used your aptx codec :
music streaming Bluetooth work weel !!!!
Call with bluetooth work but lot of noise
my question is , can I manage to use the libs for "call throught bluetooth"?
Br
Click to expand...
Click to collapse
Hi,
unfortunately, the playback of audio and call handling is separated in the bluetooth standard (Audio => A2DP, Calling => HFP) and stack and cannot be mixed or exchanged in an easy way.
This makes perfect sense, because the requirements for both use cases are totally different: Audio should have best quality, latency is not an issue, whereas during a call, low latency is very important, which is gained as a trade off from audio quality.
I didn't touch the HFP part of the stack, maybe backporting it from nougat or newest Qualcomm repositories can help. As I can't reproduce the problem (don't have a S6 Edge), this has to be done by a developer with such a device.
I'm sorry I can't help you otherwise than having a great music listening experience via bluetooth.
brhorst said:
Hi,
unfortunately, the playback of audio and call handling is separated in the bluetooth standard (Audio => A2DP, Calling => HFP) and stack and cannot be mixed or exchanged in an easy way.
This makes perfect sense, because the requirements for both use cases are totally different: Audio should have best quality, latency is not an issue, whereas during a call, low latency is very important, which is gained as a trade off from audio quality.
I didn't touch the HFP part of the stack, maybe backporting it from nougat or newest Qualcomm repositories can help. As I can't reproduce the problem (don't have a S6 Edge), this has to be done by a developer with such a device.
I'm sorry I can't help you otherwise than having a great music listening experience via bluetooth.
Click to expand...
Click to collapse
Dear sir,
Thank for your answer, I understand the situation, anyway good job and thank you for your amazing job
Would there be ARM64 support for this aptx codec CM13 ?
L649288 said:
Would there be ARM64 support for this aptx codec CM13 ?
Click to expand...
Click to collapse
It's working fine on OnePlus 3 which is ARM64
lekronop said:
It's working fine on OnePlus 3 which is ARM64
Click to expand...
Click to collapse
I installed it on Xiaomi Redmi 3 Pro, cm13 64bit, bluetooth stopped working at all. Restored system from backup.
Confirmed working on LG G2 D802 CM13, thank you!
01-30 12:11:57.563 I/bt_btif_media(3161): btif_a2dp_encoder_init Selected Codec aptX
L649288 said:
Would there be ARM64 support for this aptx codec CM13 ?
Click to expand...
Click to collapse
L649288 said:
I installed it on Xiaomi Redmi 3 Pro, cm13 64bit, bluetooth stopped working at all. Restored system from backup.
Click to expand...
Click to collapse
Arm64 would be possible if we could find arm64 versions of the libaptXScheduler.so and libaptX-1.0.0-rel-AndroidXXXX.so files. You may find them in firmware images of ARM64 devices supporting Nougat and aptX.
Then it would only be a matter of compiling the bluetooth stack against arm64.
Given the backwards compatibility of ARMv8, it might work if the bluetooth stack is compiled for ARM64. I can make a test build for ARM64 when I have some spare time (probably around March), or you could try to use my repositories to fire up your own build.
Firstly, thanks for working to backport this.
I also tested this on kenzo with a LineageOS 13 build from 2017-02-13 with Feb security patches. Unable to turn on BT. Can provide debug logs if needed.
h4waii said:
Firstly, thanks for working to backport this.
I also tested this on kenzo with a LineageOS 13 build from 2017-02-13 with Feb security patches. Unable to turn on BT. Can provide debug logs if needed.
Click to expand...
Click to collapse
Yes, please provide a logcat when you try to turn on BT. I can look into it when I get some spare time (don't have any atm).
Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now 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.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo.
Device-specific source code for the Samsung Galaxy S II Plus:
https://github.com/ghsr/android_device_samsung_galaxys2plus-common
https://github.com/ghsr/android_device_samsung_i9105p
https://github.com/ghsr/proprietary_vendor_samsung_galaxys2plus-common
https://github.com/ghsr/android_kernel_samsung_galaxys2plus-common
Compatibilitiy patches:
https://github.com/doriandiaconu/android_build-tools_galaxys2plus-common
Do not submit bugs on CyanogenMod issue tracker
Downloads
ROM: https://basketbuild.com/devs/DorianDiaconu/CM11
GApps: http://wiki.cyanogenmod.org/w/Gapps
What works?
Wi-Fi
Bluetooth
RIL (Calls, SMS, Mobile Data)
Sensors (Accelerometer, Compass, Light, Proximity, etc.)
Camera (photo & video)
Video playback
Audio (playback & recording)
GPS
Everything else not listed under "known issues"
Issues
Known device specific Issues
screenrecord does not work
Stock browser does not use hardware acceleration (Please use Firefox, Google Chrome, Dolphin, etc)
Known Sources Issues
Bluetooth Headset not working
FM Radio does not work (you can use SpiritFM, but I'm not providing support for any problem)
Does not work on 4.1 stock ROM's bootloader, please upgrade to 4.2 before flashing
Installation
Make a backup!
Make sure you are rooted
Be sure that you have the 4.2.2 bootloader
Install a custom recovery
Install the ROM using your custom recovery
Optionally install the Google Apps Addon
Wipe data if coming from stock
Don't submit bugs to me, if you didn't do a full wipe and you are coming from another ROM
For GT-I9105 flash NFC destroyer by @GHsR
FAQ
Can you include Feature X into your ROM?
No. This ROM will have CyanogenMod's feature set.
Can you include S-Note/S-Planner/MultiWindow/Insert Samsung App Here?
No. This is an AOSP ROM and cannot have TouchWiz applications.
Can you include call recording?
No. CyanogenMod does not include call recording to avoid potential legal issues.
Can you add Feature X to the stock ROM?
No. I don't work on stock ROMs.
What kernel does this ROM use?
A slightly modified version of the stock kernel, the source code is linked above.
I've heard that Broadcom doesn't release source, how can you make this ROM?
Contrary to the popular belief, userspace driver source code is not always required to make an AOSP-based ROM as long as the proprietary binaries shipped with the device does not modify the API too heavily (or is from a very different version of Android). Instead of modifying the source code of the drivers, the Android source code was adapted to be able to use the proprietary binaries.
Can I use your ROM as a base?
http://source.android.com/source/licenses.html
Most of Android/CyanogenMod is licensed under the Apache License with other small parts licensed under other open-source licenses. Which means that you may modify and redistribute without asking for permission as long as the proper credits is given and it is not misappropriated as being the official CyanogenMod. (In other words, you must say that it is based on pawitp's unofficial CyanogenMod, but is not related to CyanogenMod in any other way.)
Reporting bugs
You are allowed to report bugs only in this thread.
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.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
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. The following is a useful format to follow.
Code:
What is your:
- Phone model (I9105 or I9105P):
- Radio (baseband):
- CM version:
- CM Download URL:
- GApps version:
Did you:
- Wipe:
- Restore with titanium backup:
- Reboot after having the issue:
Are you using:
- A task killer:
- A non-stock kernel:
- CMSettings/Performance settings (other than stock):
- Other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Screenshots
F2FS
From CM 11.0 M10, it is supposed to be compatible with LuK1337 's EXT to F2FS ROM converter:
http://forum.xda-developers.com/galaxy-s2-plus/development/linux-ext-to-f2fs-rom-converter-t2840303
Thanks
- The CyanogenMod team for providing a great ROM. Without all the compatibility work which went into it, this ROM would've been much harder to make
- @pawitp - for patches
- @CoolDevelopment, @LuK1337, @GHsR, @andixlm, @beastaki23 and other I9105/P and I9082 devs
If you like it, use it and don't forget to press the "Thanks" button or send me a beer via PayPal.
XDA:DevDB Information
[M12] Cyanogenmod 11.0, ROM for the Samsung Galaxy S II Plus
Contributors
doriandiaconu
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: 4.2.2
Based On: CyanogenMod
Version Information
Status: Stable
Stable Release Date: 2016-03-26
Created 2015-05-20
Last Updated 2016-07-16
New version online. Which would probably be the last version of CM11. It isn't really getting many updates.
Changelog:
- New device tree (with CM12 changes).
- Nebula kernel
- Optimized with ArchiDroid (Thanks to @JustArchi)
- ROM and kernel optimized with Linaro.
Thanks @GHsR for the help and @haky 86 for help in some technical problems.
This ROM is now as speedy as it could be. Both i9105/p are uploaded.
Gonna resurrect PAC/AOSPA KK now.
is the stock browser hardware accelerated ? or it remains an issue even after changing the tree ?
doriandiaconu said:
New version online. Which would probably be the last version of CM11. It isn't really getting many updates.
Changelog:
- New device tree (with CM12 changes).
- Nebula kernel
- Optimized with ArchiDroid (Thanks to @JustArchi)
- ROM and kernel optimized with Linaro.
Thanks @GHsR for the help and @haky 86 for help in some technical problems.
This ROM is now as speedy as it could be. Both i9105/p are uploaded.
Gonna resurrect PAC/AOSPA KK now.
Click to expand...
Click to collapse
Vibration is not working..atleast for me..great rom tho
DenisRonaldo798 said:
Vibration is not working..atleast for me..great rom tho
Click to expand...
Click to collapse
It's really because of the device tree. It isn't compatible with nebula kernel.
bloodofJesus said:
I saw a patch for vibration fix for nebula on github, does that not work ?
Click to expand...
Click to collapse
The device tree itself doesn't include the VibrationHW.java and I forgot to add it.
bloodofJesus said:
Wow, I'm utterly impressed, the speed is impressive, too bad archidroids optimizations don't work on lollipop , is it just me or lollipop is too heavy for the s2 plus ?
Click to expand...
Click to collapse
They should be working on LP. I'm getting some assembler errors at the moment. Hope to sort them out fast.
good job
doriandiaconu said:
The device tree itself doesn't include the VibrationHW.java and I forgot to add it.
Click to expand...
Click to collapse
hello @doriandiaconu,
you think that you can rewrite the ROM with support for vibration? because I think that this ROM is the best for our samsung s2 plus.
I believe that the best ROM in performance for this phone is the Cyanogenmod based on kitkat that is faster and more stable for constant use over time
I have tried both the ROM [5.1.1] Resurrection Remix® Lollipop v5.4.5 and the ROM [5.1.1] CandyRoms Candy5 Lollipop for GT-i9105 / P V2.5.1
It' true that these ROMs (lollipop) are nice with lots of features, but after a while of using, the phone is slow especially the dialer and often become almost unusable until the next reboot
---------- Post added at 05:01 PM ---------- Previous post was at 04:30 PM ----------
bloodofJesus said:
Wow, I'm utterly impressed, the speed is impressive, too bad archidroids optimizations don't work on lollipop , is it just me or lollipop is too heavy for the s2 plus ?
Click to expand...
Click to collapse
yes, I think like you that lollipop is too heavy for our phone...
problem with images
hello, after I have installed this version of ROM with the pico Gapps in the links below [new edit], many icons and images in google playstore are corrupted? any of you have this problem?
thanks
[edit]
I understood the problem: is't the new version of google playstore
In fact, taking a file with an older version of gapps the problem does not occur
[new edit]
sorry, but I committed an error when writing above. the gapps that I used the first time are the 5.1.x on the link http://forum.xda-developers.com/paranoid-android/general/5-1-x-5-0-x-4-4-x-pa-gapps-mirror-t3069879
I used the PICO version with an updated version of play store & play services
while those of the first page of this treat work great (but there are not the PICO version)
cappoccia said:
hello @doriandiaconu,
you think that you can rewrite the ROM with support for vibration? because I think that this ROM is the best for our samsung s2 plus.
I believe that the best ROM in performance for this phone is the Cyanogenmod based on kitkat that is faster and more stable for constant use over time
I have tried both the ROM [5.1.1] Resurrection Remix® Lollipop v5.4.5 and the ROM [5.1.1] CandyRoms Candy5 Lollipop for GT-i9105 / P V2.5.1
It' true that these ROMs (lollipop) are nice with lots of features, but after a while of using, the phone is slow especially the dialer and often become almost unusable until the next reboot
---------- Post added at 05:01 PM ---------- Previous post was at 04:30 PM ----------
yes, I think like you that lollipop is too heavy for our phone...
Click to expand...
Click to collapse
I will try to do it.
If I am not wrong vibration is work on this tree
https://github.com/hak86/android_device_samsung_s2vep/blob/cm-11.0/
at last IF i have port the new kernel successfully I will try to update kitkat version too xD
haky 86 said:
If I am not wrong vibration is work on this tree
https://github.com/hak86/android_device_samsung_s2vep/blob/cm-11.0/
at last IF i have port the new kernel successfully I will try to update kitkat version too xD
Click to expand...
Click to collapse
But it wasn't on the one ghsr did. I'm not using vibration so I didn't really intend to keep it XD
file gapps
bloodofJesus said:
I have this problem as well, which gapps did you use to fix this problem ? could you link it please ? thanks. @bloodofJesus
hello, these are oK: https://www.androidfilehost.com/?fid=23311191640114013
note that you need to re-flash the rom with the new gapps file
Click to expand...
Click to collapse
Cyanogenmod 11 CM12 - BEST SCORE for s2 plus
This ROM gives the best ANTUTU BENCHMARK score for this device: 14150
with lollipop 5.1.1 the score was from 12800 to 13100
This rom is confirmed as the fastest for this phone! if there was the vibration and adaptive brightness would be the best!
cappoccia said:
This ROM gives the best ANTUTU BENCHMARK score for this device: 14150
with lollipop 5.1.1 the score was from 12800 to 13100
This rom is confirmed as the fastest for this phone! if there was the vibration and adaptive brightness would be the best!
Click to expand...
Click to collapse
Adaptive brightness works nice for me, so what's the problem?
But I miss vibrations so much, how could such a perfect ROM have no vibrations? We need it, guy, do sth with it, please
TyMoOteUuSz said:
Adaptive brightness works nice for me, so what's the problem?
But I miss vibrations so much, how could such a perfect ROM have no vibrations? We need it, guy, do sth with it, please
Click to expand...
Click to collapse
True, I want to install this rom, but without vibration I can't do anything
help for Adaptive brightness
TyMoOteUuSz said:
Adaptive brightness works nice for me, so what's the problem?
But I miss vibrations so much, how could such a perfect ROM have no vibrations? We need it, guy, do sth with it, please
Click to expand...
Click to collapse
the problem is that when I check it, it simply doesn't work....do you have an idea? you think it could be the language settings of the device?
I will try to change to a different language...
[edit]
with english language, same result: doesn't work.
how did you se it's working? have you tried to set the backlight to low level and then see how it's light automatically?
TyMoOteUuSz said:
Adaptive brightness works nice for me, so what's the problem?
But I miss vibrations so much, how could such a perfect ROM have no vibrations? We need it, guy, do sth with it, please
Click to expand...
Click to collapse
I will fix vibration and adaptive brightness. Just give me some time. I got a few exams in this period. I'm also trying to fix the LP builds.
cappoccia said:
the problem is that when I check it, it simply doesn't work....do you have an idea? you think it could be the language settings of the device?
I will try to change to a different language...
[edit]
with english language, same result: doesn't work.
how did you se it's working? have you tried to set the backlight to low level and then see how it's light automatically?
Click to expand...
Click to collapse
Ye, I've set brightness to the lowest possible, and was slowly making it brighter and brighter, and - as my settings app is white with dark-green header - the header turned completely black, and it simply worked XD or maybe it's just me understanding the ,,adaptive brightness'' wrong, sorry if so.
TyMoOteUuSz said:
Ye, I've set brightness to the lowest possible, and was slowly making it brighter and brighter, and - as my settings app is white with dark-green header - the header turned completely black, and it simply worked XD or maybe it's just me understanding the ,,adaptive brightness'' wrong, sorry if so.
Click to expand...
Click to collapse
unfortunately when I enable the adaptive backlight the screen remains dark and does not light as in other ROM I tried....
---------- Post added at 03:04 PM ---------- Previous post was at 03:02 PM ----------
doriandiaconu said:
I will fix vibration and adaptive brightness. Just give me some time. I got a few exams in this period. I'm also trying to fix the LP builds.
Click to expand...
Click to collapse
Many Thanks! I will wait for your new versione. good luck for your exams
here is for testing
Carbon Rom 5.1.1 msm8960_jbbl
...i have found it on chinese website and just reupload it
Info:
-made in china by Moonlight Rom
-based on Android 5.1.1
-carbonrom fibers
Download Link:
CARBON-5.1.1-Final-moto_msm8960_jbbl.zip - 309.66 MB
gapps not included
EDIT...tested by me and works...only is needed to delete some chinese apps and install normal keyboard
Thank you!
2 questions: how is the Speed? I´ve read that cm 12.1 roms are eating up too much ram to run smoothly on our phone.
And on this Chinese blog, there are a few roms, did you also test their Moto MSM8960_jbbl通刷 FlymeOS5.1.6.24R or Moto MSM8960_jbbl通刷 Suda1.1 安卓5.1.1 V4.0 ?
From the Changelog, these roms are all a bit the same functions.
I really love the Network Speed indication (from the xposed Framework modules). Didn´t know it was already built- in meanwhile into new Roms.
God, this "checking sd card for errors" is killing me. It´s a nice rom, but what is this 5.1. **** of external sd card handling which cannot mount the external card, even though it is ok.
Would you please upload again because link download is dead
dedik46 said:
Would you please upload again because link download is dead
Click to expand...
Click to collapse
here you go -> https://pc.cd/HHActalK
first I have to say that the rom is luxury and I liked a lot and I've had at a XT925 (razr hd)
although I have the XT925 but for this series of phones is the same thanks to the unified code and hardware similarities
I would now like to ask if anyone has already tested the hdmi output in this rom, that I do and not audio output by hdmi
and another that had problems was with the video playback but we already have solved changing a few libs
but what if it matters me is whether the audio output hdmi works and if not to be left on one side and not burn the neouronas trying to fix it, but I think the problem comes from the kernel ...
and there is no nfc but that I do not use so do not bother me ...
EIDT: audio output by hdmi is working now i dont kno how make it work but... ITS WORKING :highfive::victory:
ok now is time for make a flasheable zip.... and the question is... how to make a flasheable zip from a backup of TWRP 3.0.2
Credits:
@gr8nole for his device trees.
Lineage OS
SOURCE:
- Cyanogen: https://github.com/CyanogenMod
-Lineage OS: https://github.com/lineageos
DEVICE SPECIFIC SOURCES
- Kernel: https://github.com/gr8nole/android_kernel_samsung_smdk4x12
- Common T31x device: https://github.com/gr8nole/android_device_samsung_lt01-common
- SM-T310: https://github.com/gr8nole/android_device_samsung_lt01wifi
- SM-T311: https://github.com/gr8nole/android_device_samsung_lt013g
- SM-T315: https://github.com/gr8nole/android_device_samsung_lt01lte
-Vendor blobs: https://github.com/gr8nole/proprietary_vendor_samsung
-smdk4412-common: https://github.com/cyanogenmod/android_device_samsung_smdk4412-common/
-Samsung Service Mode: http://github.com/CyanogenMod/android_packages_apps_SamsungServiceMode
-Samsung Hardware: http://github.com/CyanogenMod/android_hardware_samsung
Download:
T310
lineage-13.0-20171001-UNOFFICIAL-lt01wifiNot tested.
lineage-13.0-20170324-UNOFFICIAL-lt01wifiNot tested.
lineage-13.0-20170129-UNOFFICIAL-lt01wifi Unofficial january security update. Lineage OS didn't release security update for android 6.0.1.
lineage-13.0-20161230-UNOFFICIAL-lt01wifi
cm-13.0-20161217-UNOFFICIAL-lt01wifi
cm-13.0-20161111-UNOFFICIAL-lt01wifi
cm-13.0-20161019-UNOFFICIAL-lt01wifi
cm-13.0-20161008-UNOFFICIAL-lt01wifi
T311
lineage-13.0-20171001-UNOFFICIAL-lt013g Not tested.
lineage-13.0-20170324-UNOFFICIAL-lt013g Not tested.
lineage-13.0-20170129-UNOFFICIAL-lt013g Not tested. Unofficial january security update. Lineage OS didn't release security update for android 6.0.1.
cm-13.0-20161217-UNOFFICIAL-lt013g Not tested.
cm-13.0-20161112-UNOFFICIAL-lt013g Not tested.
cm-13.0-20161019-UNOFFICIAL-lt013g Not tested.
T315
lineage-13.0-20170324-UNOFFICIAL-lt01lte Not tested.
lineage-13.0-20170129-UNOFFICIAL-lt01lte Not tested.Unofficial january security update. Lineage OS didn't release security update for android 6.0.1.
cm-13.0-20161217-UNOFFICIAL-lt01lte Not tested.
cm-13.0-20161112-UNOFFICIAL-lt01lte Not tested.
cm-13.0-20161019-UNOFFICIAL-lt01lte Not tested.
all my files
Gapps:
opengapps
Choose:
Platform: ARM
Android:6.0
Variant: naco or pico
INSTALLATION
First time installing Lineage OS to your Galaxy Tab 3 8.0, or coming from another ROM
- TWRP 3.0
- Copy GApps and Lineage OS ZIPs to your internal or external SDCard
- Boot into Recovery
- DO A DATA WIPE / FACTORY RESET
- Flash Lineage OS zip
- Flash GApps zip
- Reboot
- optional :FLASH SUPERSU
Please note:
I only sync and compile this rom. I use gr8nole device tree.
I built this rom and I like to share it here on xda as it is. I'm not an IT programmer (my Knowledge in programming is very limited) and I do not have very often free time.
If someone find a fix for a bug, I will recompile the rom with that fix. But I will not fix bugs by myself because I do not have the Knowledge and time to learn.
I will not respond to any comment except comments that will help me fix the rom.
Don't ask for ETA. I will try to build the rom every month when the Android security patch level is released.
UPDATE DECEMBER 2016: CyanogenMod Is Dead, and Its Successor is Lineage OS
Nice but Can I dirty flash this over gr8nole' rom?
I can confirm it works perfectly on t311 and you can dirty flash from gr8nole's CM 13
working great here, i did a total wipe then then the rom, then gapps, then supersu for good measure (i prefer it to the CM one as i dislike notifications on root stuffs). everything is lovely, although so far i've only done some normal testing/use then have had it playing perktv videos nonstop without issue.
thanks for the update(s - very appreciated!!
Doze mode is working great when using Naptime
Nice
works in my SM-T311
Thanks m8
Hope you keep maintaining this rom
I found a bug, device will shut down after using ir remote, I hope you fix this ?
Tested 2 days on T315 normal use, works flawlessly no problems what so ever with full root SU Xposed installed. all good. Thanks for the great work regards @gr8nole .
EDIT : Bugs report :
Device will restart by itself sometimes ( Not many times happens ) but it will restart when it gets little stuck or pressure sometimes
it will restart many times when using CAM application , Aftermarket CAM application installed and works fine without restarting
Whatsapp (IN APP) Cam video recording doesn't work , have to use installed cam app
Recording voice using Whatsapp isn't clear.
Second MIC (SPEAKERPHONE Mic ) doesn't work
Bluetooth Music works fine but NOT Bluetooth Calls ( In calls U only hear your voice echo )
otherwise reading other comments on other roms seems to to have more bugs.
LTE 4g and voice calls works fine, everything else works fine
IR remote works great Using PEEL SMART APP for Samsung
thanks
New builts with security patch November 2016
New builts with security patch December 2016
Very thanks!
Thank you very much for completing this ROM. I found out, that there is the DRM Bibliothek missing (SM-T310), but not on equal ROM for SM-T520 . Someone knows to fix it?
Very good rom for sm 315 and very fast. Thank you. 2 bugs: mirracast dont working, and the sound of key, i disable from options but still make sound.
Thank you so much! Your ROM runs perfect on my T310. I got one noobish question: where can I get the SuperSU? I just found one quite old thread about this. Thx in advantage!
nope, that method doesnt work with 6.0.1, had to do a dirty flash to get rid of it.
Does the camera and bluetooth work correctly?
RiTCHiE007 said:
Does the camera and bluetooth work correctly?
Click to expand...
Click to collapse
I justed tested that for you. Tried a Bluetooth speaker, taking photos and video recording, everything seems to work perfect ?
Droehnemeier said:
I justed tested that for you. Tried a Bluetooth speaker, taking photos and video recording, everything seems to work perfect
Click to expand...
Click to collapse
Thank you for taking the time and test all these so thumbs up!!
RiTCHiE007 said:
Thank you for taking the time and test all these so thumbs up!!
Click to expand...
Click to collapse
You are welcome :good: enjoy flashing
I have cm 13.1 on Samsung sm-t310 and works fine... What's dirty flash and what's easiest way to upgrade to lineage?
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
https://developer.sony.com/develop/open-devices/
Unified 4.4 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Bug tracker
https://github.com/sonyxperiadev/bug_tracker/issues
Now you can build the latest Android with the latest 4.4 kernel
jerpelea said:
Now you can build the latest Android with the latest 4.4 kernel
Click to expand...
Click to collapse
Does it also mean that the official firmware from Sony will be updated with this new kernel?
I am not a developer but built it following the guide using the sources since a few months back. Boots and runs. Even used it for a time. But couldn't get fingerprint sensor to work properly. When I used 8.0 branch it was working but very slow and roughly. (Nowhere near the sensitivity of the stock rom) now with 8.1 branch can't get it register fingerprints. Sensor works, starts enrollment and progresses, but at the last step it gives error. However seems like more sensitive and faster than before. Another problem is the battery drain when idle. When using the phone daily routine not that bad, slightly less screen on time compared to stock but the real problem idle battery drain. %15-20 in 6-7 hours. According to battery starts appears to be related to Google play services which is always a serious battery killer for custom roms for years. Other than these did not notice any serious problems. And all this without any changes or tweaks. Straight from the source. Good job Sony imo.
@maluus Don't know if this also applies to compiling roms, but Sony just (march 8) released a new version (v11) of the odm image, which solves fingerprint enrollment issues you seem to describe for the omnirom 8.1 build:
https://developer.sony.com/file/dow...es-for-aosp-oreo-android-8-1-kernel-4-4-loire
Yeah heard of it. I was using v10 oem image last time. When i get back to home I'll try with v11 and will see if fingerprint issue is solved. If it's ok i can use it as daily as it is. If battery drain problem is solved too it will be pretty much everything i expect.
Vendor v11 is out
https://developer.sony.com/develop/open-devices/latest-updates
battery drain is fixed and new kernel binary will be released today
FM-radio will work someday on kugo in custom roms?
Anyone tried a recent aosp build with v11 binaries yet? Does fingerprint works correctly and accurately? How is the battery life compared to the stock? What is screen on time?
Just installed an AOSP build from March 15th together with v11 binaries and Micro GApps. Fingerprint is working.
And the battery life? I'm home though. I'll be building soon ?
droncheg said:
FM-radio will work someday on kugo in custom roms?
Click to expand...
Click to collapse
for the Open Devices project
in Android 7.x the FM Radio is enabled
in Android 8.x the FM Radio is disabled
Regards
J
For user security dm-verity and File Based Encryption are enabled by default
Please disable them only if you are developing new features
Regards
J
@jerpelea
Will the Sony Xperia XZ2 be added?
MartinX3 said:
@jerpelea
Will the Sony Xperia XZ2 be added?
Click to expand...
Click to collapse
we are finalizing the last steps before adding it
Regards
J
All build guides are updated with the Security updates
https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
Here is the list of all known bugs. If you find bugs you can always open a ticket in the bug tracker and we will check it ASAP.
https://github.com/sonyxperiadev/bug_tracker/issues
@jerpelea, do you know if there is a modem binary file for this phone that's compatible with T-Mobile VoLTE in the US? The XZ1C has a compatible file (amss_fsg_lilac_tmobile_us_ims_tar.mbn). The stock ROM doesn't, but I'm trying to get VoLTE working and this file would certainly help (if it exists).
Last night I built again. First thing I noticed is how well fingerprint reader works. It's like stock. Congrats to the devs for good job. Camera including video recording and Bluetooth works. But camera seems 1-2 mm smal from sides. Charging issue persists. As Harry pointed 3 amp chargers doesn't work. I tried 2 other chargers. 2.1 amp charger work normally. But 1 amp charger starts do disconnect and connect again after 43-44%. (I'll share the logs with devs) Another problem I noticed is that I can't root with magisk. Tried ver 16, 17 and 18. I can flash from twrp without error but when the device boot up neither Magisk manager is installed nor device is rooted. I did not try with supersu. Another thing to mention is that device boots up pretty slow. Boot crash still happens sporadically.
PS: Supersu works. Sometimes device lags heavily. I noticed especially on chrome and some banking apps.
PS 2: Sharing logs. (Includes 3 amp charging attempt and 2.1 amp charging)
little off, very very basic question, and I could not seem to find the answer.
I understand how to set up a build environment and build an image to the phone, but how about the developer.sony.com latest section binaries?
are they already built images? how will it be different if I build mine following the instructions?
Cheers,
You'll build rom first then you still need to flash that binaries too. They are not alternatives to your home build rom. They are part of the os which you won't be able to homebrew, for your device to work properly.
Code:
/*
* Your warranty is now 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.
*
*/
Hi,
here you can find my version of LineageOS 20 for our Samsung Galaxy S3 (I9305).
This is a alpha build, also from the LineageOS side, there are typical functions still missing, so don't install it if you want a completely stable and completed ROM and don't report my already listet bugs!
Attention:
Sometimes it needs another reboot to find the sim card.
When you have BitGapps installed, you have to reflash them after every update!
Here you can see how far everything is working for now.
Spoiler: Whats working
Boot
Audio
Bluetooth
Graphics
Cameras
Sensors
Wifi
GPS
USB
Video playback (HW/SW)
Tethering via USB
RIL
OTA-Updates
Tethering via WIFI and Bluetooth
much more...
Spoiler: Whats not working
Random reboots
NFC
SD-Card can't be formatted as internal storage, this will cause a bootloop
Spoiler: Links
TWRP
ROM direct link
I9305 ROM
ROM Mega
Spoiler: Changelog
26.01.2023
13.03.2023
Spoiler: How to improve GPS
You could use a gps.conf from https://app.box.com/s/w57s1v1n3hie7l5lk28i for your location and replace /vendor/etc/gps.conf.
Or you try GPS Server Optimizer app for a faster 3D fix.
For both methods you need root rights.
I would recommend to use microG instead of BitGapps,
here you can find the installation instructions:
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][13.x][I9305][ALPHA] LineageOS 20.0, ROM for the Samsung Galaxy S3 LTE
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 13.x T
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Version Information
Status: Alpha
Created 2022-11-08
Last Updated 2023-03-13
Does the tmobile s3 need a different rom? I'm upgrading all my old phones I just found. You happen to be working on all the phones I have.
kerryking1 said:
Does the tmobile s3 need a different rom? I'm upgrading all my old phones I just found. You happen to be working on all the phones I have.
Click to expand...
Click to collapse
I'm sorry to tell you that the T-Mobile S3 has a different chipset (Qualcomm Snapdragon S4 Plus MSM8960) so this is not compatible.
This device never reached a higher android version than 7, I would love to bring Android 13 to this device, but I don't own this model.
html6405 said:
I'm sorry to tell you that the T-Mobile S3 has a different chipset (Qualcomm Snapdragon S4 Plus MSM8960) so this is not compatible.
This device never reached a higher android version than 7, I would love to bring Android 13 to this device, but I don't own this model.
Click to expand...
Click to collapse
Are you in the US?
kerryking1 said:
Are you in the US?
Click to expand...
Click to collapse
No, I'm in Europe...
Would it be possible to port if I tested it?
kerryking1 said:
Would it be possible to port if I tested it?
Click to expand...
Click to collapse
Not really, this would slow down the process too much.
Hi there. I stumbled over this thread? Are compiled versions of the Rom available? Just for testing a nonrooted device? Cheers
rattesack3 said:
Hi there. I stumbled over this thread? Are compiled versions of the Rom available? Just for testing a nonrooted device? Cheers
Click to expand...
Click to collapse
1.03 GB folder on MEGA
2 files
mega.nz
Thanks will give it a try soon! Everytime i thought there were device at eol, they last longer. Hopefully this isn' t true for the gt-i9305.
Can you give some instructions to build the Rom on my own?
Do you think I could just swap boards? The boards look the same.
rattesack3 said:
Can you give some instructions to build the Rom on my own?
Click to expand...
Click to collapse
Write me a PN and I will help you.
kerryking1 said:
Do you think I could just swap boards? The boards look the same.
Click to expand...
Click to collapse
I fear that the mainboard could not fit into the case, but idk, you could give it a try.
I asked a seller on ebay and they said it doesn't work.
Is porting to a different chipset like starting over on port?
kerryking1 said:
Is porting to a different chipset like starting over on port?
Click to expand...
Click to collapse
I would have to start from the last developement state.
But at first I would make the device tree's for A13 ready, fix the build (there could be many problems), make the kernel ready and so on...
There would be a lot of work todo.
Hello,
the volume of voice recordings (e.g. whatsapp or signal) has always been too low for me in Lineage OS. In order for my interlocutors to understand me properly, I always had to increase the volume by changing the mixer_paths.xml in /root/vendor/etc/. Here is the video:
Unfortunately this file does not exist in Lineage OS 20. Does anyone know how to increase the volume of voice recordings here?
I'm so grateful you have brought my N8000 and i9305 back to life!
My children are learning and playing on my N8000 tablet. I have donated for N8000.
I re-wiped and installed your latest on i9305
20.0-20221108-HTML6405-i9305.zip
MicroG
Disabled animations
Android UI is running fast!
I tested YouTube app. It works but drops some frames on 360p, and any higher quality levels it drops a lot of frames.
scrcpy working nicely (not used with YouTube of course)
I'm still testing etc. It looks like i9305 will be useful with your ROM
-------------
Regarding your 3.4 kernel for "S3" (probably i9300?)
@html6405
Downloads for : Samsung Galaxy S3 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Please excuse my ignorance about kernels on Samsung Android.
Kernel Q1. Can your 3.4 "S3" Kernel work on S3 LTE i9305?
No Q2: Would you be able to compile 3.4 kernel for i9305?
Yes Q2. If I install html6405_kernel_-e48ea6b54b22-m0-3.4.zip Must I also install boot_img_3.4.img
Yes Q3. In what order do I install the kernel zip and boot_img zip?
Update 26.01.2023:
Synced with latest LineageOS sources
Set swappiness back to 100
Fixed SamsungDoze
Update 13.03.2023:
Synced with LineageOS sources from February
Moved to faster ota server
Possible fix for gralloc crash