[ROM][EOL][7.1.2][OFFICIAL] LineageOS for T0LTE - Galaxy Note II N7105 Android Development

[ROM][EOL][7.1.2][OFFICIAL] LineageOS for T0LTE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
*/
This rom has reached end-of-life state. There will be no new builds, updates or support for LineageOS 14.1 version.
If you still find this useful the last build was on 20190126 and you can find it in download section.
Working
Graphics
Wifi
Data
RIL
Bluetooth
GPS
Sensors
Vibration
Camera
NFC
Audio
Video Playback
Miracast
Not working/Bugs/Unknown
Data doesn't work until after first boot.
MHL/HDMI doesn't work
Bluetooth audio (may or may not work for you)
MTP crashes when uninstalling an app
LED flashlight doesn't work on SC-02E
Installation
Read the FAQ to familiarize yourself with any issues that may come up
Make sure you are using the latest TWRP version.
Download the latest build and google apps
Copy it to the phone
Factory reset in TWRP (Very important! Do not skip)
Flash LineageOS 14.1
Flash Gapps
Optional: Flash root package
Reboot
Be patient. The first boot will take between 5 - 15 minutes.
Set up everything and reboot again to get radio working
See the FAQ to avoid common issues
Supported Variants
t0lte
GT-N7105/N7105T
SGH-i317/i317M
SGH-T889/T889V
SHV-E250S/E250K/E250L
SC-02E (SGH-N025)
Download
ROM: https://www.androidfilehost.com/?fid=1395089523397906488
TWRP: https://www.androidfilehost.com/?w=files&flid=173497
Gapps: http://opengapps.org
Root: https://download.lineageos.org/extras or Magisk
Changelog
For official builds: cmxlog.com or lineageoslog.com
Below are the changelogs for unofficial builds:
3/18/2017
Moved smdk4x12 RIL class upstream to smdk4412-qcom-common
03/10/2017
Enabled wakelock for flashlight (prevents flashlight from turning off when screen is turned off)
03/07/2017
Updated SELinux for tethering
Enabled RPFILTER for tethering
Remapped menu button to app switcher
03/06/2017
Fix Bluetooth
Better CDMA support
Removed unnecessary RIL shim
03/05/2017
Note: These are the differences from the last official build, not experimental builds.
SELinux now enforcing (policies completely rewritten)
Fixed data issues
Fixed sensors issues
Fix sdcard (internal and external) writing issues
Switched to open source RIL
Enabled ambient display
02/20/2017
Synced with upstream
SELinux updates
Fixed sensors
16.02.2017
Synced with upstream
SELinux updates
RAF bringup and update
Patched radio libs to fix audio
01/14/2017
Initial build
XDA:DevDB Information
[ROM][EOL][7.1.2][OFFICIAL] LineageOS for T0LTE, ROM for the Samsung Galaxy Note II
Contributors
Option58, PoisonNinja, LineageOS team
Source Code: https://github.com/LineageOS/android_device_samsung_t0lte
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Nightly
Created 2017-12-13
Last Updated 2019-07-24

FAQ:
Root
LineageOS removed builtin root, so you need to flash the root package linked above.
Data doesn't work
Reboot. Data doesn't work on the first try
Can't send MMS messages
Reboot. Then, make sure your APN settings are correct.
Dialer not responding during calls/calls not launching dialer
Credits to @paulq75
Settings -> Apps -> tap the cog icons up to the right -> and the set the default Phone app.
A lot of apps force close on system start
Usually happens when switching to/from TouchWiz roms. Solution would be to backup your data to PC and format internal storage. Sometimes even multiple times.
SDCard access denied in app even though I click 'allow'
Known bug. Happens only on first attempt. Solution would be to close the app, remove from recents and start again.
Rom fails to flash or OTA doesn't work
Make sure you are using the latest TWRP version from this thread.
I have some other issue!
See Reporting Bugs below

Reporting Bugs
When reporting an issue, please provide the following information:
Device (N7105, i317, 889, etc.)
Build Date
Logcat when the issue occurs (http://forum.xda-developers.com/showthread.php?t=1726238)
If it's a random reboot, also provide the following information:
Kernel logs. Run "adb shell su -c cat /proc/last_kmsg > /sdcard/Download/kernel.txt" and grab kernel.txt from the Download folder on your phone
Building LineageOS
Follow the instructions at https://source.android.com/source/initializing.html and https://source.android.com/source/downloading.html.
When you get to repo init, use the url https://github.com/LineageOS/android.git -b cm-14.1
repo sync
Edit roomservice.xml in .repo/local_manifests/ and edit it so it looks like this
repo sync
. build/envsetup.sh
brunch t0lte

OH SNAP!!

Wow. You're Comeback! I will try.

Here we go !
Looks like gapps link is down ATM.
Thank you for this new build !
Sent from my SGH-I317 using XDA-Developers Legacy app

Thanks for the new toy to play with bro. Rom boots, takes forever but none the less it boots into the os (so give it a few) which runs like butter. Unfortunately data doesn't connect at all just stays saying connecting. Looking forward to future updates for this bad boy...

Nice to see you come back to this device :good: Too late to mess with it tonight, but I'll flash in the A.M.
I was just trying to build this myself today, but kept getting errors during the build. New to building CM/Lineage, but I'll keep plugging away. Glad to see it's possible to get it to work. I still have hope lol

thanks so much!
Sent from my E6653 using Tapatalk

Is this marked as "unofficial" because it is self build from the LineageOS Sources or are there changes to the sourcecode? And if so what are they?
Will give this one a go once i'm home.

Wowwww thanks Dev.

dzee206 said:
Thanks for the new toy to play with bro. Rom boots, takes forever but none the less it boots into the os (so give it a few) which runs like butter. Unfortunately data doesn't connect at all just stays saying connecting. Looking forward to future updates for this bad boy...
Click to expand...
Click to collapse
Can you at least make and receive calls and texts?
kozmo21 said:
Nice to see you come back to this device :good: Too late to mess with it tonight, but I'll flash in the A.M.
I was just trying to build this myself today, but kept getting errors during the build. New to building CM/Lineage, but I'll keep plugging away. Glad to see it's possible to get it to work. I still have hope lol
Click to expand...
Click to collapse
Sync the sources and try again, as I've upstreamed a bunch of build fixes. Also, cherry-pick https://review.lineageos.org/#/c/156547/, as that fixes the SELinux build errors. Finally, you'll probably want to add androidboot.selinux=permissive to CONFIG_CMDLINE in arch/arm/configs/cyanogenmod_t0lte_defconfig, because otherwise it won't boot with SELinux enforcing.
peterhugelberg said:
Is this marked as "unofficial" because it is self build from the LineageOS Sources or are there changes to the sourcecode? And if so what are they?
Will give this one a go once i'm home.
Click to expand...
Click to collapse
This is unofficial because it is self built, although the code is directly from upstream. I've been commiting patches the past few days to get t0lte to build, which you can see at https://review.lineageos.org/#/q/project:LineageOS/android_device_samsung_t0lte. The only other change that I haven't uploaded to Gerrit is setting SELinux to permissive (because LineageOS developers don't allow SELinux to be set to permissive on official builds)

PoisonNinja said:
Can you at least make and receive calls and texts?
Click to expand...
Click to collapse
No I wasn't able to. I'll try again later on.

PoisonNinja said:
Can you at least make and receive calls and texts?
Sync the sources and try again, as I've upstreamed a bunch of build fixes. Also, cherry-pick https://review.lineageos.org/#/c/156547/, as that fixes the SELinux build errors. Finally, you'll probably want to add androidboot.selinux=permissive to CONFIG_CMDLINE in arch/arm/configs/cyanogenmod_t0lte_defconfig, because otherwise it won't boot with SELinux enforcing.
This is unofficial because it is self built, although the code is directly from upstream. I've been commiting patches the past few days to get t0lte to build, which you can see at https://review.lineageos.org/#/q/project:LineageOS/android_device_samsung_t0lte. The only other change that I haven't uploaded to Gerrit is setting SELinux to permissive (because LineageOS developers don't allow SELinux to be set to permissive on official builds)
Click to expand...
Click to collapse
Little feedback:
I can make receive calls, but no sound
Data doesn't work for me either
GPS does work on even on "device only"
Video works on YouTube
MTP error with stock file manager, no problem with 3rd party ones
I don't have arch/arm/configs/cyanogenmod_t0lte_defconfig, In mine it's arch/arm/configs/lineageos_t0lte_defconfig, I don't have any cyanogen anything there... but I'll change it there. Actually, think that was the error I had an hour into the build. It had something to do with libselinux, then... ninja: build stopped: subcommand failed. Hope that fixes it and I can build :fingers-crossed:
Thanks for the tip :good:

I can call. But no sound sending and receiving call.
Data connection is not established.

Same here... No data and no calls.

kozmo21 said:
Little feedback:
I can make receive calls, but no sound
Data doesn't work for me either
GPS does work on even on "device only"
Video works on YouTube
MTP error with stock file manager, no problem with 3rd party ones
I don't have arch/arm/configs/cyanogenmod_t0lte_defconfig, In mine it's arch/arm/configs/lineageos_t0lte_defconfig, I don't have any cyanogen anything there... but I'll change it there. Actually, think that was the error I had an hour into the build. It had something to do with libselinux, then... ninja: build stopped: subcommand failed. Hope that fixes it and I can build :fingers-crossed:
Thanks for the tip :good:
Click to expand...
Click to collapse
Whoops, you're right. I mean lineageos_t0lte_defconfig. Don't forget to cherry-pick the commit I linked earlier, which should fix the libselinux error.
Jetiman said:
I can call. But no sound sending and receiving call.
Data connection is not established.
Click to expand...
Click to collapse
prbs1982 said:
Same here... No data and no calls.
Click to expand...
Click to collapse
Have you checked the mute settings? Try toggling it.

PoisonNinja said:
Have you checked the mute settings? Try toggling it.
Click to expand...
Click to collapse
Yes, Speaker on-off / mic on-off, does not change anything. No speech outgoing and reaching.

It appears that i9305 has the same radio hardware as the N7105. Roberto Gibellini has been doing a lot of work, I'll see if I can port some of the stuff over.
This reminds of the early CM13 days, when we had to use a chroot to get the radio to work

PoisonNinja said:
It appears that i9305 has the same radio hardware as the N7105. Roberto Gibellini has been doing a lot of work, I'll see if I can port some of the stuff over.
This reminds of the early CM13 days, when we had to use a chroot to get the radio to work
Click to expand...
Click to collapse
thanks for the hard work, we all owning a n7105 thank you :good:

Related

[ROM][UNOFFICIAL][6.0.1][T235/Y] CyanogenMod 13 For Galaxy Tab 4 7.0 LTE [BETA]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod 13 for the Samsung Galaxy Tab 4 7.0 LTE​By Hennymcc and CTXz​
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
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. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Before you start
This ROM is only for the T235 and T235Y
Code:
*
* Your warranty will be voided !
*
* 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.
*
Special Thanks
@hennymcc For his huge effort and contributions on Exynos 3470 related devices
@tyktak For the testing
And of course the entire CyanogenMod team!
What is Fixed
Incoming Calls
Red flashy frames
Lock Screen
CM setup Wizard
Google Setup Wizard
RIL (SIM Detection)
Youtube
Videos
Wifi
What is not working
Auto Rotate stops working after some time
Unswitchable preffered networks (Stuck on 3g but actually LTE)
SElinux
Instructions
How to install CM 13
If you don't have TWRP yet, get it from here : TWRP 3.0.0 for Samsung Galaxy Tab 4 7.0 LTE
Download the ROM and the Gapps that are located below on to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot
In case things go wrong make a backup
After the backup has completed return to home
WARNING : The next three steps WILL delete all your your data but not your internal storage
Select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home
Select install and locate the ROM zip
After you selected the ROM select add more zips and select your Gapps zip
Finally swipe to install
When all of this is done, reboot into system, wait, and enjoy CyanogenMod 13 on your Galaxy Tab 4 7.0 LTE
How to ROOT
In CM 13, enable the developer options
Select Root access
Select Apps Only (Or Apps and ADB if you use ADB)
Done
Downloads
Lastest recommended CyanogenMod release for the Galaxy Tab 4 7.0 LTE T235 : ROM
All my releases can be found here : Android File Host
Gapps : Open Gapps
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Requests for other devices
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of CM's framework (Ex. Adding Samsung Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Change Log
Code:
2016/3/19
- Fixed incoming calls
- Synced to newest CM sources
2016/3/13
- Synced to newest CM sources
2016/3/13
- Fixed RIL (SIM detection)
- Updated to Lollipop Kernel
2016/3/10
- Fix Crash on CM and Google setup Wizzard
2016/2/28
- Switch from -eng to -userdebug
- Fixed Wifi
- Fixed CM Wizzard crash
- Fixed Lockscreen (Crash after entering sleep)
- Fixed Youtube Videos Crashing
- Fixed Videos freezing device
- Removed Flashy frames (By switching from -eng to -userdebug)
2016/2/27 - CM released
Screen Shots
XDA:DevDB Information
CyanogenMod 13 For Samsung Galaxy Tab 4 7.0 LTE, ROM for the Samsung Galaxy Tab 4
Contributors
CTXz, hennymcc
Source Code: https://github.com/cm-3470
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Beta
Created 2016-02-27
Last Updated 2016-03-19
Reserved
Q&A
Q: Will this work on T2XX
A: This build is ONLY for the LTE variant of the 4 inch tab. I have not tried if this rom works on the T235Y (should probably work though). However the LTE version has an Exynos 3470 where else the Wifi version has a Marvell chip (I have some bad experience with that chip *cough* attempt to get CM working on it *cough*). PLEASE DO NOT TRY TO FLASH THIS ON ANY OTHER DEVICE THAN THE T235 OR T235Y.
Q: What about the T230!!!
A: As mentioned in my TWRP thread. Sub77 will send me a T230, and I can give it a shot again to build at least CM11 on it.
Q: How long till <insert issue here> gets fixed
A: ETA's (Short for Estimated Time of Arrival) aren't tolerated that well on XDA. Please remember that this is only a hobby!
Reserved
Looking forward to run this on my SM-T235. Only if it isn't Monday tomorrow, i would test run this ROM.
New build released, links have been updated!
Code:
2016/2/28
- Switch from -eng to -userdebug
- Fixed Wifi
- Fixed CM Wizzard crash
- Fixed Lockscreen (Crash after entering sleep)
- Fixed Youtube Videos Crashing
- Fixed Videos freezing device
- Removed Flashy frames (By switching from -eng to -userdebug)
If RIL isn't working yet, i assume one won't be able to make call. Correct?
Gandicela said:
If RIL isn't working yet, i assume one won't be able to make call. Correct?
Click to expand...
Click to collapse
Not via phone, however you can call via wifi (skype etc)
I have been looking forward to this ROM for a while and I really appreciate your effort in this. Thank you very much!
Flashed it and deleted the setupwizard.apk as suggested but the CM setup wizard still crashes after pressing skip on "SIM card missing" tab. Any suggestions how to bypass this?
Any possibility for kernel with overclocking CPU and GPU functions for our tab?
Raido182 said:
I have been looking forward to this ROM for a while and I really appreciate your effort in this. Thank you very much!
Flashed it and deleted the setupwizard.apk as suggested but the CM setup wizard still crashes after pressing skip on "SIM card missing" tab. Any suggestions how to bypass this?
Any possibility for kernel with overclocking CPU and GPU functions for our tab?
Click to expand...
Click to collapse
Hey, i'll fix that issue in my next build, however I need to get my PC running again before I can start anything new
CTXz said:
Hey, i'll fix that issue in my next build, however I need to get my PC running again before I can start anything new
Click to expand...
Click to collapse
I'm patiently waiting, Mate. Quality work takes time. Thanks hugely for supporting our device.
So excited!
I have 2 SM-T230's for my boys, If you need someone to test something please let me know. (I am hoping that this will have the Marshmallow feature to use the SDcard as internal memory)
Thanks Andi
therealbroxy said:
I have 2 SM-T230's for my boys, If you need someone to test something please let me know. (I am hoping that this will have the Marshmallow feature to use the SDcard as internal memory)
Thanks Andi
Click to expand...
Click to collapse
Sorry mate, this thread is t235 only
CTXz said:
Sorry mate, this thread is t235 only
Click to expand...
Click to collapse
I know but...... you mentioned someone was sending you a 230, you might have time in the future, this might be the closest I get to seeing 6 on my Tab 7, A slim chance is still a chance! so I am still excited
I'm looking for someone to test my new build, my tester seems to be away at the moment, PM me if you're willing to test
CTXz said:
I'm looking for someone to test my new build, my tester seems to be away at the moment, PM me if you're willing to test
Click to expand...
Click to collapse
Is it for the 20160308 degaslte build? I've downloaded it and i try to find time to test tonight. Or is it another built?
Gandicela said:
Is it for the 20160308 degaslte build? I've downloaded it and i try to find time to test tonight. Or is it another built?
Click to expand...
Click to collapse
Hey, thanks but my tester returned, I'll update the OP
CTXz said:
Hey, thanks but my tester returned, I'll update the OP
Click to expand...
Click to collapse
No problem
I've dirty flashed the actual build over last lp build by hennymmc. Generally the last build works well but ril doesn't work with boh7 baseband. The camera preview hang up after taking a photo. If you take a new picture, the photo shows in gallery but the preview doesn't work.
New build released, links have been updated
Code:
2016/3/10
- Fix Crash on CM and Google setup Wizzard
CTXz said:
New build released, links have been updated
Code:
2016/3/10
- Fix Crash on CM and Google setup Wizzard
Click to expand...
Click to collapse
@CTXz
Thanks very much indeed for this ROM. It's running good, however i just want to point out 2 really minor things (aside from the RIL stuff).
1. Sensitive notification drawer, as from my hlte CM12.1, "Contents hidden" for any apps in the notification drawer
2. Quick unlock option inside Lockscreen menu

[UNOFFICIAL][a5xelte][SM-A510F]Lineage OS 15.1 for A5 2016

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Introduction
Thanks to my very generous donors I managed to buy an A5 2016 cheap on eBay and have ported our new device tree and kernel to this device.
This is far more stable and much snappier than the previous releases available as the new kernel/tree is much quicker.
Features and ImprovementsStable
Fast​What worksCalls, SMS, Mobile Data
Camera
NFC
WiFi
Bluetooth
Torch
Fingerprint scanner
SELinux Enforcing​What doesn't workSome 2D animation stuttering (WIP)
Occasional Camera HAL crashes (same HAL bugs as A3)Fixed in 27/05/2019 release
VoLTE (will never work on LOS)
You tell me​Installation
Download the latest LOS build and transfer it to your phone
Install the latest TWRP (Available Here)
Make a full backup (just in case something goes wrong)
Do a full wipe (Cache, Dalvik Cache, Data, System)
Install LOS
If you are installing GApps do it at the same time (preferably in the same install queue)
Install Magisk if you want root
And finally boot, the first boot can take several minutes as it optimises all the apps
DownloadsLatest releases are uploaded HERE
OpenGapps HERE
TWRP is availableHERE
Magisk is available HERE​SourceExynos7580 device tree/kernel sources are available here
LineageOS sources here​Thanks@Stricted
@l-0-w
@alexax66
@macs18max (BT call audio fix)
@Borduni
And all others who have contributed to the Exynos projects​A special thanks to my donorsMarkus Anders
@D4ND310
@epicwilmo
@tyson
@thebinf
@Herti
@pixelou
@xavier66​XDA:DevDB Information
Lineage OS 15.1 for A5 2016, ROM for the Samsung Galaxy A Series
Contributors
danwood76, stricted
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Created 2019-04-27
Last Updated 2019-05-27
Changelog
Code:
Changes in the 23/06/2019 release:
[INDENT]camera: added new workaround to fix remaining HAL crashes (Google Camera should work now)
June Android security patch
LOS updates
[/INDENT]
Older changes listed below:
Code:
Changes in the 27/05/2019 release:
[INDENT]camera: improved camera wrapper to fix camera crashes (still avoid google camera)
LOS updates[/INDENT]
Code:
Changes in the 17/05/2019 release:
[INDENT]ramdisk: tune VM parameters to fix issues with MTP (thanks [user=7341346]@IvoDi[/user])
WiFI: fixed MAC address loading
Android May security update[/INDENT]
Code:
Changes in the 04/05/2019 release:
[INDENT]sepolicy: Fix denial that caused fingerprint reader to fail (thanks @antonyc828 and @LilDead)
kernel: Fix an issue in the charger that would cause charge to fail if the phone had not been plugged in for 20+ hours
[/INDENT]
Code:
Changes in the 03/05/2019 release:
[INDENT]kernel: added a workaround for the DMA busy issue that was causing reboots when switching to amplifier
kernel: fixed WiFi android version check
kernel: disabled GPU debug trace to try and speed up rendering in situations where HWC cannot be used
kernel: removed previous DMA NULL ptr dereference hack as it did not help
[/INDENT]
Code:
Second release of the day (lineage-15.1-20190503_2-UNOFFICIAL-signed-a5xelte):
[INDENT]Updated Bluetooth configuration to fix calling
[/INDENT]
Code:
Changes in the 29/04/2019 release:
[INDENT]device tree: pulled in the correct power_profile.xml from stock (fixes reported battery size)
kernel: Fixed a NULL ptr dereference in the sound DMA code that causes a system reboot
[/INDENT]
Code:
Changes in the 26/04/2019 release:
[INDENT]Initial release
[/INDENT]
Build Instructions
1. Setup a LineageOS build environment based on one of the supported LineageOS 15.1 devices: https://wiki.lineageos.org/index.html
Note: All commands below are executed from the LineageOS root directory
2. Initialise the LineageOS repositories
repo init -u git://github.com/LineageOS/android.git -b lineage-15.1
3. Sync the repos (can take a log time, around 30GB of downloads)
repo sync
4. Create the .repo/local_manifests directory and add the a5xelte manifest (attached)
mkdir .repo/local_manifests/
cp ~/Downloads/a3xelte.xml .repo/local_manifests/
5. Sync our device trees in
repo sync
6. Setup the build environment
source build/envsetup.sh
7. Finally start the build:
brunch lineage_a5xelte-userdebug
To pull in new changes it is usually only necessary to repeat steps 5 - 7.
mmm.. looks good, I will try bruh.
good job
Good rom
Hi bro thanks for rom and thank you for support i am tested rom and i saw 2 problem :
1-firstly sometimes notification animations getting lag(i think not important)
2-i get only one time random reboot While connecting my 5ghz wifi
Also kernel optimizations are good i got 3530 geekbench score
Last one will u build pie?
Thanks for all
SimurgAnka said:
Hi bro thanks for rom and thank you for support i am tested rom and i saw 2 problem :
1-firstly sometimes notification animations getting lag(i think not important)
2-i get only one time random reboot While connecting my 5ghz wifi
Also kernel optimizations are good i got 3530 geekbench score
Last one will u build pie?
Thanks for all
Click to expand...
Click to collapse
1. I have seen this too, it is odd as we use the same software stack on the A3 and S5NEO and get really smooth composer/animation performance. I am looking in to this.
2. Are you able to copy out the /proc/last_kmsg file and send it to me via pm? You will need root. I have seen a random kernel crash related to audio that I am looking in to, it may be the same issue but the last_kmsg will help.
There are no real "kernel optimisations" as such, our kernel started as the stock A510F kernel which we updated for Oreo. We used this as our base for the A3 and S5NEO as it was the latest kernel with the most frequent updates. I just recently divided it might be nice to port this to it's original device
With regards to Pie, I will be making Pie builds in the near future. I just wanted to get a stable and tested Oreo ROM before I add the Pie patches.
Hi bro i got one more time random reboot in the lockscreen,sorry bro i cant send logcat or /proc/last_kmsg because i am restarted my phone .I guess random reboot reason is not wifi . If i get one more time, i will send you bro also maybe u can know me ,we are speaked discord many time . Last one ui is fully smooth but only notification bar animations do that.
SimurgAnka said:
Hi bro i got one more time random reboot in the lockscreen,sorry bro i cant send logcat or /proc/last_kmsg because i am restarted my phone .I guess random reboot reason is not wifi . If i get one more time, i will send you bro also maybe u can know me ,we are speaked discord many time . Last one ui is fully smooth but only notification bar animations do that.
Click to expand...
Click to collapse
The crash I saw occurred just after I unlocked it via fingerprint, but the logs revealed that it was not fingerprint related but was related to the audio driver.
The /proc/last_kmsg file is persistent after a reboot, that is why I have asked for it. It may be the crash I have seen but I need more logs to confirm exactly where the issue occurs.
Regards,
Danny
danwood76 said:
The crash I saw occurred just after I unlocked it via fingerprint, but the logs revealed that it was not fingerprint related but was related to the audio driver.
The /proc/last_kmsg file is persistent after a reboot, that is why I have asked for it. It may be the crash I have seen but I need more logs to confirm exactly where the issue occurs.
Regards,
Danny
Click to expand...
Click to collapse
Good luck bro
Uploading a new release, changes:
device tree: pulled in the correct power_profile.xml from stock (fixes reported battery size)
kernel: Fixed a NULL ptr dereference in the sound DMA code that causes a system reboot
Installed the rom, bugs which i found at this moment: (I'm sorry for my bad English, I from Poland)
1. Laggy notification center, and lock screen (but not always)
2. MTP not always work
3. Audio causing reboots (on stock music player less often than on liked by me "Retro Music Player")
And i not found a option to change lock screen wallpaper.
Rom is very fast - faster than other builds of lineage 15.1 and 16 for this phone
sometimes i get reboot when open app.
idk why, i try to clean install, and same too.
but this rom so smooth and really fast.
no lag for pubg ?
thank you so much sir.
btw this kernel not support fast charging?
---------- Post added at 05:45 AM ---------- Previous post was at 05:42 AM ----------
KaroloBC said:
Installed the rom, bugs which i found at this moment: (I'm sorry for my bad English, I from Poland)
1. Laggy notification center, and lock screen (but not always)
2. MTP not always work
3. Audio causing reboots (on stock music player less often than on liked by me "Retro Music Player")
And i not found a option to change lock screen wallpaper.
Rom is very fast - faster than other builds of lineage 15.1 and 16 for this phone
Click to expand...
Click to collapse
update to latest build bro..
Hi,
Which gapps? 8.0 or 8.1?
Amathagma said:
Hi,
Which gapps? 8.0 or 8.1?
Click to expand...
Click to collapse
arm 8.1 pico bro
Fingerprint don't work and Randomly reboot. Please help me <3
skaptes said:
Fingerprint don't work and Randomly reboot. Please help me <3
Click to expand...
Click to collapse
which your build? 27/29?
my phone not have fingerprint issue.
Sent from my [device_name] using XDA-Developers Legacy app
thank you very much. The fastest and most stable rom
The last build with nano gapps. Don't work fingerprint
skaptes said:
The last build with nano gapps. Don't work fingerprint
Click to expand...
Click to collapse
try to clean install? wipe system, cache, data, internal.
if still problem, try flashing firmware samsung to latest version on 2019.
because i don't have thats problem.
but idk. maybe someone like you too..
Sent from my [device_name] using XDA-Developers Legacy app
se.developers said:
arm 8.1 pico bro
Click to expand...
Click to collapse
Why arm?
Phone is recognized as arm64 in the beginning.

[ROM][OFFICIAL][montana][10] LineageOS 17.1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
LineageOS 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. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
Instructions:
Download the latest build, official TWRP (3.3.1 and newer) and GApps (if you need them)
Flash the downloaded TWRP via fastboot
Boot to recovery
Format system, vendor, data, cache, and dalvik cache
Reboot to recovery
Flash the latest build
Flash GApps and any other necessary add-ons
What's working:
WiFi
Camera and Camcorder
Bluetooth
NFC
Fingerprint - Oreo firmware required
GPS
OTG
Video Playback
Audio
RIL
VoLTE/VoWiFi
USB tethering/audio
SELinux: Enforcing
Known issues:
You tell me
Downloads:
Official builds: Download
Recovery: Official TWRP
Google Apps: OpenGApps (nano package is advisable, but you definitely should avoid using stock/super packages)
Reporting Bugs
All bugs should be reported here: Issue Tracker
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
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. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS 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:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thanks to:
@GivFNZ for testing my builds
@wiktorek140, @karthick mostwanted, @wh0dat, @KalilDev, @AsD Monio, @GoldeneyeS2, @Steve Mathew Joy and @rajatgupta1998 for their hard work on our device sources
LineageOS team
Changelogs:
Code:
2020-11-19:
Updated kernel based on Moto's Moto One (deen) QPKS30.54-12-23 tag and CAF's LA.UM.8.6.r1-05300-89xx.0 tag
Updated Moto Actions UI
Improved boot animation speed and smoothness
Partially resolved perf HAL spam in logs
2020-11-15:
Added support for montana_retcn (XT1799-2)
Fixed a bug where the back flash wouldn't work properly when taking a photo using Snap
Fixed a bug where loudspeakers would crackle on some VoIP calls
Improved RIL stability
Improved Wi-Fi stability
Increased ZRAM to 1.33GB
Updated kernel based on Moto's Moto One (deen) QPKS30.54-12-22 tag and CAF's LA.UM.8.6.r1-04700-89xx.0 tag
Updated Moto Actions UI
November security patch
2020-10-11:
Added customizable vibration intensity in Settings > Accessibility
New FM radio app
Added support for factory reset protection (only partially effective)
Fixed boot with SELinux: Enforcing on GSIs
October security patch
2020-09-23:
Minor improvements and under the hood changes (check technical changes for more details)
2020-09-20:
Improved GPS stability
Fixed an issue where there would be random UI lag
2020-09-17:
Fixed an issue where you couldn't exit from offline charging mode
2020-09-16:
Fixed offline charging
2020-09-15:
Actually fixed random color inversion that could occur (Note: Color calibration in LiveDisplay is no longer available as a result of fixing the bug)
Fixed bootloop when enabling secure startup
Fixed manual network selection
Fixed dual SIM menu not appearing - needs testing
Mobile data settings now only displays 3 modes (LTE, 3G and 2G)
September security patch
2020-09-11:
Fixed random color inversion that could occur
2020-09-10:
Fixed Wi-Fi Display
Updated listen blobs to Q
Added support for Color profiles (Settings > Display > Colors)
Fixed an issue where you couldn't connect to certain Wi-Fi networks
2020-09-08:
Initial release.
Source code:
Common device tree: https://github.com/LineageOS/android_device_motorola_msm8937-common
Device tree: https://github.com/LineageOS/android_device_motorola_montana
Kernel: https://github.com/LineageOS/android_kernel_motorola_msm8953
Reserved
Reserved
Nice job, thanks a lot for your working on it
Thanks Jarl for keeping montana alive!
:good:
New build is up. Check OP for changelog. Downloads as always are in the OP, but you may update via the Updater app if you wish. Happy flashing! :fingers-crossed:
Just flashed it, working very fine, thanks a lot.
A minor bug I can't explain : some of the menus stay in English even if I select another language.
Will moto actions be add?
Everything else working fine
Random color inversion. Flashed last build
does this and lineage os 16 need something apart from oreo firmware? because i tried both with all twrp versions available and when rebooting after flashing zip it just always send me to the bootloader.
i have model xt1790
before i was on carbon rom and was working fine so i dont know what is wrong here, also tried lineage os from AsD Monio and works fine just the initial setup a bit buggy
recovery log: https://pastebin.com/Y0GjaHtZ
logcat right after reboting to recovery after wiping all then flashing this rom: https://pastebin.com/mvVQ12Zb
janinetavs said:
Will moto actions be add?
Everything else working fine
Click to expand...
Click to collapse
Settings > System > Advanced
janinetavs said:
Random color inversion. Flashed last build
Click to expand...
Click to collapse
v1.2? Nobody has experienced random color inversion for that one.
rakion99 said:
does this and lineage os 16 need something apart from oreo firmware? because i tried both with all twrp versions available and when rebooting after flashing zip it just always send me to the bootloader.
i have model xt1790
before i was on carbon rom and was working fine so i dont know what is wrong here, also tried lineage os from AsD Monio and works fine just the initial setup a bit buggy
recovery log: https://pastebin.com/Y0GjaHtZ
logcat right after reboting to recovery after wiping all then flashing this rom: https://pastebin.com/mvVQ12Zb
Click to expand...
Click to collapse
No, but please make sure to use the latest TWRP version. You must also format data (not wipe). Also, recovery logs won't help due to them only showing what's happening in the recovery.
Just flashed v1.2 working also fine
One question though : on the Moto Camera v6.2 app the HDR option is no more visible (it was on latest Pie builds).
Edit : persistent even when installing via the Moto Camera Thread tutorial
JarlPenguin said:
No, but please make sure to use the latest TWRP version. You must also format data (not wipe). Also, recovery logs won't help due to them only showing what's happening in the recovery.
Click to expand...
Click to collapse
rn im on latest 3.4.0-1 and i tried both format and wipe, dirty flashing from the other los 17.1 and other rom just to test but all end in always booting to bootloader menu its weird never happened something similar and only happen with your lineageos 16 and 17.1 roms
rakion99 said:
rn im on latest 3.4.0-1 and i tried both format and wipe, dirty flashing from the other los 17.1 and other rom just to test but all end in always booting to bootloader menu its weird never happened something similar and only happen with your lineageos 16 and 17.1 roms
Click to expand...
Click to collapse
Do you have full Oreo firmware installed? Also can't do anything without logs
Dan Mornill said:
Just flashed v1.2 working also fine
One question though : on the Moto Camera v6.2 app the HDR option is no more visible (it was on latest Pie builds).
Edit : persistent even when installing via the Moto Camera Thread tutorial
Click to expand...
Click to collapse
It's because we use HAL3 now. Certain functions won't work because we use deen blobs instead of stock camera blobs
janinetavs said:
Will moto actions be add?
Everything else working fine
Click to expand...
Click to collapse
They already are?
Yes they are, you have to look in the right menu
JarlPenguin said:
Do you have full Oreo firmware installed? Also can't do anything without logs
Click to expand...
Click to collapse
i didn't remember but looks like i got a old one or a fix fingerprint zip most probably, took me a day to find a working link to full 8.1 and after 2 updates from ota i got M8937_37.13.03.75R baseband and now worked perfectly your rom thank you for keeping alive our moto g5s

ROM][11.0.0][Himaul/himawl] LineageOS 18.1 [Unofficial]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10.0 (Q), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
LineageOS 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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for Lineage OS is available in the LineageOS Github repo. And if you would like to contribute to Lineage OS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing Lineage OS 18.0 your device?
Coming from a SENSE ROM?
Enable all location services: Settings > Location > (all location services) = On
Coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash LineageOS.
Optional: Install the Google Apps addon package.
Downloads
Downloads
ROM - https://mirror.codebucket.de/claymore1297/LineageOS/18.1/hima
Google Apps - https://mirror.codebucket.de/claymore1297/GAPPS/
TWRP Recovery (SAR) - https://github.com/CaptainThrowback/android_device_htc_hima/releases
XDA: DevDB Information
LineageOS 18.0, ROM for the HTC One (M9)
Contributors:
@Claymore1297
@k4y0z
ROM OS Version: 11 R
ROM Kernel: Linux 3.10.108
Kernel Source: https://github.com/Claymore1297/android_kernel_htc_msm8994
SELinux: enforce
Requirements
HTC Firmware: 4.x
TWRP: 3.4.0-0 - with SAR support
special thanks to:
@root-expert
Version Information
Status: Beta
What is working
WiFi
Bluetooth
IR
Camera (including video recording)
Telephony (Calls, MMS/SMS and Mobile data)
Audio (Record and Playback)
Video Playback
GPS
NFC
What is not working
FM Radio
Bug report
Bug reports without a proper description of the issue and a log will be ignored!
You don't know howto take a log - see here:
How to take system logcats, kernel logs, and dmesg on Android
Wondering how to take logs on Android? In this guide, we tell you about the various common logs on Android and how to collect them.
www.xda-developers.com
https://lmgtfy.com/?q=how to get android logs&p=1&s=g
How to Build
XDA:DevDB Information
LineageOS 18.0, ROM for the HTC One (M9)
Contributors:
Claymore1297, k4y0z
Source Code: https://github.com/lineageos
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: 4.x
Based On: LineageOS
Version Information
Status: Beta
Created 2020-12-06
Last Updated 2020-12-06
*reserved*
*reserved*
Hello Claymore,
first of all: Thanks so much for keeping our phone alive and absolutely up to date!
I was so excited to install LOS 18.0 and especially was fully convinced to finally get rid of the very annoying "echo in voice calls"-bug.
I already tested the AICP 16.0 (built 2020-11-15) and it was fixed (as promised ) (as already posted here).
So I just installed very very fresh (wiped everything (cache, data, system, yes even the internal storage)) the lineage-18.0-20201206-UNOFFICIAL-hima.zip .
Here it comes: the echo is still there, not fixed !!!!! Oh no ! Do you have any idea what the difference is between aicp and los regarding voice calls? There must be something.
Changing volume still has no effect even when you put the call on speakers.
Everything else works (as far as I have tested for now) perfectly!
I had so much hope in that....could you please take another look on this echo in voice calls issue and fix it as on aicp.
Again: Thank you so much for your work.
Pfony said:
Hello Claymore,
first of all: Thanks so much for keeping our phone alive and absolutely up to date!
I was so excited to install LOS 18.0 and especially was fully convinced to finally get rid of the very annoying "echo in voice calls"-bug.
I already tested the AICP 16.0 (built 2020-11-15) and it was fixed (as promised ) (as already posted here).
So I just installed very very fresh (wiped everything (cache, data, system, yes even the internal storage)) the lineage-18.0-20201206-UNOFFICIAL-hima.zip .
Here it comes: the echo is still there, not fixed !!!!! Oh no ! Do you have any idea what the difference is between aicp and los regarding voice calls? There must be something.
Changing volume still has no effect even when you put the call on speakers.
Everything else works (as far as I have tested for now) perfectly!
I had so much hope in that....could you please take another look on this echo in voice calls issue and fix it as on aicp.
Again: Thank you so much for your work.
Click to expand...
Click to collapse
thanks for the headsup - I forget to merge this kernel-commit into new LOS-tree. will be included in next build!!
Hi,
where can I download TWRP 3.4.0-0 with SAR support?
Hello jkrajcir,
you can download from here: twrp-3.4.0-0-hima.img
@Claymore1297 :
short feedback from your most recent build:
- live display not working + you cannot change color temperature right now
- under "styles & wallpapers" if you want to change from one icon shape to another it is not always applied
- LOS updater gives an error message (most likely because there aren't any !?!?)
livedisplay isn't ready I think.
Which error you get on updater? also logs could be useful here...
Claymore1297 said:
livedisplay isn't ready I think.
Which error you get on updater? also logs could be useful here...
Click to expand...
Click to collapse
Regarding the updater please refer to the following screenshot:
Also very interesting is the "last checked" date
please try again.
Claymore1297 said:
please try again.
Click to expand...
Click to collapse
I think it works again. Great job
Pfony said:
Hello Claymore,
first of all: Thanks so much for keeping our phone alive and absolutely up to date!
I was so excited to install LOS 18.0 and especially was fully convinced to finally get rid of the very annoying "echo in voice calls"-bug.
I already tested the AICP 16.0 (built 2020-11-15) and it was fixed (as promised ) (as already posted here).
So I just installed very very fresh (wiped everything (cache, data, system, yes even the internal storage)) the lineage-18.0-20201206-UNOFFICIAL-hima.zip .
Here it comes: the echo is still there, not fixed !!!!! Oh no ! Do you have any idea what the difference is between aicp and los regarding voice calls? There must be something.
Changing volume still has no effect even when you put the call on speakers.
Everything else works (as far as I have tested for now) perfectly!
I had so much hope in that....could you please take another look on this echo in voice calls issue and fix it as on aicp.
Again: Thank you so much for your work.
Click to expand...
Click to collapse
Same to me. Echo is still there
Echo apart, great job!!!
Got error 64 on installing opengapps_arm11 posted (i believe for wrong 32bit architetture) but the NikGappsCore64 did well (i don't know which differences there are).
I can't find in development options how to enable advanced reboot (for reboot into twrp)
@Claymore1297
Just to let you know:
also in your current LOS 18 (20201206) build there still is the problem with unstable bluetooth connections in cars as already described in the LOS 17.1 thread here.
Now I also experienced very unstable bluetooth connections in a Mercedes (2017) with the "command online"-system.
To be more specific:
bluetooth itself is enabled the hole time but opening calls fails at first attempt and after some time waiting the phone starts a second attempt automatically and the call is established correctly. Also, and that is even worse, when having somebody on the phone, after round about 1 minute the call ends or the call's audio is switched to the phone instead of the car's audio-system.....veeery annoying .
As assumed in my LOS17.1 post (link above) maybe it has something to do with the phone's switching into lockscreen/sleep after some time of touch-inactivity with the phone and I often get this "worked around" by just click on the power butten (to wake it up from sleeping?!)
Does anybody else has any similar experience with bluetooth + phone calls + car's audio-system or am I the only one ?
Thanks for your investigation .
Pfony said:
@Claymore1297
Just to let you know:
also in your current LOS 18 (20201206) build there still is the problem with unstable bluetooth connections in cars as already described in the LOS 17.1 thread here.
Now I also experienced very unstable bluetooth connections in a Mercedes (2017) with the "command online"-system.
To be more specific:
bluetooth itself is enabled the hole time but opening calls fails at first attempt and after some time waiting the phone starts a second attempt automatically and the call is established correctly. Also, and that is even worse, when having somebody on the phone, after round about 1 minute the call ends or the call's audio is switched to the phone instead of the car's audio-system.....veeery annoying .
As assumed in my LOS17.1 post (link above) maybe it has something to do with the phone's switching into lockscreen/sleep after some time of touch-inactivity with the phone and I often get this "worked around" by just click on the power butten (to wake it up from sleeping?!)
Does anybody else has any similar experience with bluetooth + phone calls + car's audio-system or am I the only one ?
Thanks for your investigation .
Click to expand...
Click to collapse
My Bluetooth and calls are fine but I'm unable to make wifi hotspot
do yall know if file-based encryption is supported on this kind of device ? Cause I tried enabling it and now my phone is stuck in a bootloop :/
Edit:
TWRP is okay again.
but i‘ve problems with battery after flashing. At Night the Battery was 47% but today morning the battery was empty.
Any solutions for this issue?
I had a huge battery drain as well. For some reason I had to flash TWRP again 3.4.0. Because I wanted to use Francos Kernal Manager I installed Magisk to root my phone. The problem disappeared. Coincidence or not, I don't know.
Before the device got unusually warm as well during normal usage.
haseebhamid said:
My Bluetooth and calls are fine but I'm unable to make wifi hotspot
Click to expand...
Click to collapse
Cannot activate hotspot, the toggle switch off immediately
I recently flashed this build on my m9 and i was very surprised.
How did you manage to get that hardware DSP to work correctly?
No more distortion and proper limiter wow that´s amazing!
I saw you reverted the commit from here, would this work just that simple on 17.1 aswell?

LineageOS 18.1 Android 11 for GT-N5100 GT-N5110 GT-N5120 treblelized BETA FINAL EOL

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 for the n51xx on LineageOS 18.1.
Don't forget, this is a early beta build, so you will face bugs and don't expect a fully functioning ROM,
this ROM is not finished and may not be able to be used as a daily driver,
for this I would recommend my LOS 16.0 version or /e/.
At first I want to thank @forkbomb444, @rINanDO, @ChronoMonochrome and all the others who are working on the exynos 4 devices, also big thanks to @prkfsz for donating me a n5120 and also the shipping cost.
Also big thx to @cngbrick for donating a n5100.
For sure there are many other people who did there work, it's open source and this is the reason why android
is great in general.
It already took me a few hundred hours and it will become more and more to support you with great updates.
Here you can see how far everything is working:
Spoiler: Whats working
Boot
Audio
Bluetooth
Graphics
Main camera
Wifi
USB
Video playback (HW/SW)
OTA Updates
RIL
GPS
Tethering via USB, WIFI and Bluetooth
consumerir transmitter (IR Blaster)
Sensors
Spoiler: Whats not working
Bluetooth headset in a mobile call
Maybe random reboots
Maybe more
Spoiler: Links
TWRP
N5100 ROM
N5110 ROM
N5120 ROM
If you are going to use Gapps,
here you can download them:
Open Gapps
For the others, you can use microG in future.
If you want to pass the safety net check, root your device with magisk, Selinux is disabled.
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
Spoiler: Changelog
30.04.2021
04.05.2021
20.08.2021
24.08.2021
26.08.2021
10.11.2021
11.11.2012
12.11.2021
09.01.2022
22.02.2022
19.04.2022 FINAL
Spoiler: How to improve GPS
You could use a gps.conf from https://app.box.com/s/w57s1v1n3hie7l5lk28i for your location and replace /system/etc/gps.conf.
Or you try GPS Server Optimizer app for a faster 3D fix.
For both methods you need root rights.
Spoiler: How to encrypt
If you plan to encrypt your device, the first step is to backup all your important stuff.
Reboot into recovery and choose:
Wipe->Advanced Wipe->Data (check)
Choose "Repair or Change File System" and afterwards "Resize File System".
After this step, choose Reboot System and you can start to encrypt your drive.
If you can't find this option in the settings by your own, use the search function and type "encryption" and you can start.
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
Spoiler: Don't like my boot picture?
If you don't like it, reboot into recovery and type the following command:
adb shell (or use TWRP's terminal)
bash /data/param_restore.sh
reboot
Uploaded a prepared package to build your own boot picture
download
XDA:DevDB Information
[ROM][11.x][N5100/N5110/N5120][BETA] LineageOS 18.1, ROM for the Samsung Galaxy Note 8.0
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 11.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.5.X
Based On: LineageOS
Selinux: permissive, this makes only sense as soon the ROM is stable.
Version Information
Status: Beta
Created 2021-04-26
Last Updated 2022-04-19
Interested in flashing your first GSI on your Note 8.0?
Yes this is real, you can find more informations here:
[GSI][11][ EXYNOS4 SMDK4412 ][N8000, N801X, N8020, I9300, N5100, N51XX, N7100, ...][ALPHA] [EOL]
Here you will find my exynos4 compatible GSI's. This work is based on the magic of @phhusson, so thank you very much for this. Don't forget, that you need an treblelized ROM to support this. Do you like my work? Than you can simply hit...
forum.xda-developers.com
非常感謝你。
它將發布N5100版本嗎?
Translation:
thank you very much.
Will it release the N5100 version?
PangJi said:
非常感謝你。
它將發布N5100版本嗎?
Click to expand...
Click to collapse
Please write in english, if you can't, use google translate .
I will publish a N5100 version today or tomorrow, it depends on my spare time I will have.
@html6405
Good evening, I'm waiting for the version for the n5100.
Thank you for doing the firmware.
I tried to run the firmware on the n5100 device from n5110, the following errors are boot animation, the problem with Wifi sees but does not connect, the problem with Selinux is disabled.
I'm waiting for the firmware for the n5100 to be released))
@html6405
Spoiler: 1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you for this rom ,version alpha.
I installed the rom and gapps test version according to your instructions on my Samsung Note 8 Wifi GT-N5110
Not working: Wifi. Login credentials are accepted and saved for my wifi network; but from there it keeps searching and searching for IP number and so on for some time and than ends up with the error 'Authentication failed'.
After completing the install I tried tot connect Wifi again, but same result as mentioned above.
XdaFoxygen said:
the problem with Wifi sees but does not connect, the problem with Selinux is disabled.
Click to expand...
Click to collapse
ruchri said:
Not working: Wifi. Login credentials are accepted and saved for my wifi network; but from there it keeps searching and searching for IP number and so on for some time and than ends up with the error 'Authentication failed'.
Click to expand...
Click to collapse
Hmm ok, try the version from today, wifi is working in my case very well, if it's than still not working,
check if the .mac.info file exists in /efs/wifi.
@html6405
Booth animation at the beginning is a little curve.
Screen brightness problems at 37%, very dim.
Microfreezes are visible in energy saving mode.
When recording the screen, everything lags terribly, I use the system screen recording utility.
Didn't find the key backlight setting item.
SELinux problem is disabled and writes a warning Trust.
And he also writes This assembly is signed with public keys.
Mac-address Wi-Fi devices 00:00:00:00:00.
Error when enabling developer mode, Wifi does not want to connect to the network.
Video
Thanks for your efforts!
Sorry, answered wrong person. See below​
html6405 said:
Hmm ok, try the version from today, wifi is working in my case very well, if it's than still not working,
check if the .mac.info file exists in /efs/wifi.
Click to expand...
Click to collapse
Tnank you for your reply.
OK, I will wait for that version, which is not on line by now; only 20210428 for N5100. Meanwhile I reinstalled 18.1-20210426 N5110 en checked /efs/wifi, but folder efs is empty.
ruchri said:
OK, I will wait for that version, which is not on line by now; only 20210428 for N5100. Meanwhile I reinstalled 18.1-20210426 N5110 en checked /efs/wifi, but folder efs is empty.
Click to expand...
Click to collapse
Than you didn't mount /efs, it shouldn't be empty.
XdaFoxygen said:
SELinux problem is disabled and writes a warning Trust.
And he also writes This assembly is signed with public keys.
Click to expand...
Click to collapse
Selinux will be the last thing, like on LOS 16.1. It doesn't make much sense as long it is in early alpha stage.
And yes, I'm signing my builds with public keys because it's unofficial.
XdaFoxygen said:
Mac-address Wi-Fi devices 00:00:00:00:00.
Click to expand...
Click to collapse
This must not be true, it is also zero when the Mac is ok, this is a hal issue and at the moment just an optical thing.
At the moment I'm also facing some shutdown issues on my N5100, so I guess it will be the same in your case,
but yeah, it's just a test version...
html6405 said:
Selinux will be the last thing, like on LOS 16.1. It doesn't make much sense as long it is in early alpha stage.
And yes, I'm signing my builds with public keys because it's unofficial.
This must not be true, it is also zero when the Mac is ok, this is a hal issue and at the moment just an optical thing.
At the moment I'm also facing some shutdown issues on my N5100, so I guess it will be the same in your case,
but yeah, it's just a test version...
Click to expand...
Click to collapse
I was glad to help with testing, we need to work with optimization, there are micro-freezes.
Notice the pixels visible in the top control bar.
In general, the firmware is not bad.
XdaFoxygen said:
I was glad to help with testing, we need to work with optimization, there are micro-freezes.
Notice the pixels visible in the top control bar.
In general, the firmware is not bad.
Click to expand...
Click to collapse
It will take time, that this firmware will be good enough to be used as a daily driver.
There are many icons missing in hdpi resolution, this will also take time until they are available,
this is why you see the pixels.
Update 28.04.2021:
Introduced triple buffering for a smoother experience
Implemented button to switch off stylus icon hovering
Many Kernel back ports made
Brought back BOARD_CANT_REALLOCATE_OMX_BUFFERS, this will fix for example YouTube kids crash
Security patch level 05.04.2021
Enabled fast charging
Much more small fixes / optimizations
I'm facing a new shutdown bug with this version, I will work on this the next day's / week's, please report me if it is the same behaviour in your case.
html6405 said:
Than you didn't mount /efs, it shouldn't be empty.
Click to expand...
Click to collapse
Mounted. In /efs/wifi there is only 1 file /.mac.cob containing the digits 08:37:3D:E8:F1:5F
ruchri said:
Mounted. In /efs/wifi there is only 1 file /.mac.cob containing the digits 08:37:3D:E8:F1:5F
Click to expand...
Click to collapse
Ok this is good, this file contains your mac address, this file should be copied at the init process,
you could try to restart from zero, maybe then it's working.
html6405 said:
Ok this is good, this file contains your mac address, this file should be copied at the init process,
you could try to restart from zero, maybe then it's working.
Click to expand...
Click to collapse
Confirmation:
Wifi works after installing 2021-04-28. Great!
Some bugs already mentioned and commented by you:
boot animation
selinux/trust warnings (of course, public keys)
Display time-out: shutdown bug. I worked around this by setting time-out at 30 minutes.
Besides all this: Donated for your wonderful projects in general. Vielen Dank dafür!
ruchri said:
Display time-out: shutdown bug. I worked around this by setting time-out at 30 minutes.
Click to expand...
Click to collapse
This didn't worked for me, as soon the device goes to sleep, its simply off, never had such a case, but I will figure it out.
Thank you very much for your donation .

Categories

Resources