Develop Bugs

[ROM e975] Pure AOSP build based on Google's master branch sources

Gave up trying, this thread is dead
Due to lack of time and due to almost bricking my phone I'm giving up this project and I returned my phone to stock. There are many things that manufacturers configure that are specific to the phone hardwares that all custom ROMs doesn't configure. For example, if battery is too low, phone turns off automatically to avoid reaching 0% as lithium batteries doesn't like to become too empty, if phone is overheating, apps that could cause a high CPU usage bringing more heat, are not executed and, while in high temperatures, you can't increase screen brightness above a calculated percentage. So I think that to maintain my phone's health it's better stock ROM.
Hello everyone! This is my first attempt to build a ROM from the ground up, so it has some problems that I have to address. I could build and boot it successfuly on my e975 device and all hardware seems to work. Currently it's based on platform version 5.0.50.50.50.50
ISSUES:
GApps force closes when you try to create a google account in the smartphone
Phone app is force closing when trying to make or receive calls
Camera
Browser force closes, doesn't start
WORKING
Phone is online for the operator
GPS
Bluetooth
3G
SMS
WiFi
Galery app
Music app
All Google apps, except creating a Google account in the phone
UNTESTED:
NFC (turns on, but don't have any other NFC device to test connectivity)
4G
I would be grateful if the community could help me out to address the ROM issues, pointing me the path to follow. I'm a beginner in ROM development and don't know much of Android's inner parts.
INSTALL INSTRUCTIONS
1 - Download ROM from http://d-h.st/jRme and kernel from http://d-h.st/4tm9
2 - Make a factory reset
3 - Flash the ROM
4 - Flash the kernel (flash it, or won't boot)
5 - Reboot the phone and wait for almost 20 minutes for it's first boot
Sources:
Directly from Google: http://source.android.com/source/downloading.html
Device tree: https://github.com/lollipop-og/android_device_lge_geehrc/tree/aod (thanks to @Kevinjoa)
Kernel binary: Solid_Kernel_V1.5GEE-LP --> http://loller79.altervista.org/ (thanks to @Loller79)

Phone apk issue, some clue?
Well, here is some logcat that I could get from my phone while trying to make a call, here it indicates a null pointer exception, but I don't know the reason. Can someone help me to figure it out?
Code:
01-11 23:37:35.370 628 1733 I ActivityManager: START u0 {act=android.intent.action.CALL dat=tel:xxxx-xxxx cmp=com.android.server.telecom/.CallActivity (has extras)} from uid 10004 on display 0
01-11 23:37:35.444 5296 5296 I Telecom : InCallController: Attempting to bind to InCall com.android.dialer, is dupe? false
01-11 23:37:35.449 5296 5296 I Telecom : CallAudioManager: updateAudioStreamAndMode, mIsRinging: false, mIsTonePlaying: false
01-11 23:37:35.454 5296 5296 I Telecom : CallAudioManager: updateAudioStreamAndMode, mIsRinging: false, mIsTonePlaying: false
01-11 23:37:35.455 5296 5296 I Telecom : CallAudioManager: requestAudioFocusAndSetMode, stream: -1 -> 0
01-11 23:37:35.455 628 1733 I MediaFocusControl: AudioFocus requestAudioFocus() from AudioFocus_For_Phone_Ring_And_Calls
01-11 23:37:35.457 203 203 D audio_hw_primary: adev_set_mode: mode 201-11 23:37:35.468 5296 5296 I Telecom : CallAudioManager: changing audio stat
e from [AudioState isMuted: false, route; EARPIECE, supportedRouteMask: EARPIECE, SPEAKER] to [AudioState isMuted: false, route; EARPIECE, supportedRouteMask: EARPIECE, SPEAKER]
01-11 23:37:35.486 628 628 V GpsNetInitiatedHandler: ACTION_NEW_OUTGOING_CALL - false
01-11 23:37:35.491 628 1733 W InputMethodManagerService: Window already focused, ignoring focus gain of: [email protected] [email protected], token = [email protected]
01-11 23:37:35.505 5296 5296 D AndroidRuntime: Shutting down VM
01-11 23:37:35.506 5296 5296 E AndroidRuntime: FATAL EXCEPTION: main
01-11 23:37:35.506 5296 5296 E AndroidRuntime: Process: com.android.server.telecom, PID: 5296
01-11 23:37:35.506 5296 5296 E AndroidRuntime: java.lang.NullPointerException: in == null
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at libcore.io.Streams.readFully(Streams.java:74)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at java.io.DataInputStream.readShort(DataInputStream.java:152)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:2064)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at java.io.ObjectInputStream.<init>(ObjectInputStream.java:371)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at com.android.i18n.phonenumbers.prefixmapper.PrefixFileReader.loadMappingFileProvider(PrefixFileReader.java:56)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at com.android.i18n.phonenumbers.prefixmapper.PrefixFileReader.<init>(PrefixFileReader.java:48)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at com.android.i18n.phonenumbers.geocoding.PhoneNumberOfflineGeocoder.<init>(PhoneNumberOfflineGeocoder.java:43)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at com.android.i18n.phonenumbers.geocoding.PhoneNumberOfflineGeocoder.getInstance(PhoneNumberOfflineGeocoder.java:57)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at com.android.internal.telephony.CallerInfo.getGeoDescription(CallerInfo.java:561)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at com.android.internal.telephony.CallerInfo.updateGeoDescription(CallerInfo.java:546)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at com.android.internal.telephony.CallerInfoAsyncQuery$CallerInfoAsyncQueryHandler.onQueryComplete(CallerInfoAsyncQuery.java:315)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at android.content.AsyncQueryHandler.handleMessage(AsyncQueryHandler.java:344)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at android.os.Looper.loop(Looper.java:135)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5223)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at java.lang.reflect.Method.invoke(Method.java:372)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:754)
01-11 23:37:35.506 5296 5296 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:644)
01-11 23:37:35.507 628 1658 W ActivityManager: Process com.android.server.telecom has crashed too many times: killing!
01-11 23:37:35.507 628 1658 W ActivityManager: Force finishing activity com.android.server.telecom/.CallActivity

Trying another build using CM device tree to see what I get. Until now build is going well, I adapted their device tree to AOSP, don't know if it will boot or even finish building successfuly

Congratulations, looking forward to seeing your dev skills go from strength to strength

lsrzj said:
Trying another build using CM device tree to see what I get. Until now build is going well, I adapted their device tree to AOSP, don't know if it will boot or even finish building successfuly
Click to expand...
Click to collapse
Stuck at the bootscreen, not able to connect adb to make a logcat during the boot. Compiled gproj kernel from CM, lost recovery mode, it appears a black background screen with an Android open in the chest and no menu appears. So I'm not able to restore my previous backup using CWM, so I had to put phone in download mode and return to stock, then unlock it, root it, install CWM to restore my previous backup!

Gave up trying
Due to lack of time and due to almost bricking my phone I'm giving up this project and I returned my phone to stock. There are many things that manufacturers configure that are specific to the phone hardwares that all custom ROMs doesn't configure, for example, if battery is too low, phone turns off automatically to avoid reaching 0% as lithium batteries doesn't like to become too empty, and if phone is overheating, apps that could cause a high CPU usage bringing more heat, are not executed and, while in high temperatures, you can't increase screen brightness above a calculated percentage. So I think that to maintain my phone's health it's better stock ROM.

Nai Nai, don't give up, but don't dream too much...
Tip: Start with small projects, don't try to do things that don't even great devs accomplished as a beginner, and for the purpose of your project:
Yes you can build AOSP for an unsupported device, but without knowing what you need to take from other custom ROM repos is very difficult and with wrong blobs, very dangerous. AOSP builds straight from the source code are terrible, at least my G2 build was, old school dialer, lot's of broken and junk stuff, that's why there's AOSP custom based ROM, if you know Git you can create very cool projects, much better than AOSP builds.
eg.:
Choose a good source to get based on, like Paranoid if you don't plan to get lot's of features, pick a good optimized toolchain instead of Google's one, enable some optimizations like -O3 and Graphite, strict aliasing for beginners is not recommended, and debloat getting rid of weird and old apps and wallpapers, the result is amazing.
Here's an example you can follow to learn these stuff, https://github.com/SaberSunset, it's not fully implemented yet on PA but within some weeks it will be the way I want it. There are some articles in my manifest you can read, my project is self explanatory, it teaches in the commits and why I did something, it's a good source to learn.
Good learning;
Boa sorte também... podes me mandar MP se precisar de ajuda.

GalaticStryder said:
Tip: Start with small projects, don't try to do things that don't even great devs accomplished as a beginner, and for the purpose of your project:
Yes you can build AOSP for an unsupported device, but without knowing what you need to take from other custom ROM repos is very difficult and with wrong blobs, very dangerous. AOSP builds straight from the source code are terrible, at least my G2 build was, old school dialer, lot's of broken and junk stuff, that's why there's AOSP custom based ROM, if you know Git you can create very cool projects, much better than AOSP builds.
eg.:
Choose a good source to get based on, like Paranoid if you don't plan to get lot's of features, pick a good optimized toolchain instead of Google's one, enable some optimizations like -O3 and Graphite, strict aliasing for beginners is not recommended, and debloat getting rid of weird and old apps and wallpapers, the result is amazing.
Here's an example you can follow to learn these stuff, https://github.com/SaberSunset, it's not fully implemented yet on PA but within some weeks it will be the way I want it. There are some articles in my manifest you can read, my project is self explanatory, it teaches in the commits and why I did something, it's a good source to learn.
Good learning;
Boa sorte também... podes me mandar MP se precisar de ajuda.
Click to expand...
Click to collapse
I understood what you mean, but problem is that there are many other things to check. I like very much custom ROM's functionalities, I tried this pure AOSP to start modifying it and create something. But, first, I needed to understand how make files interact with each other and many other things, like sepolicy files. Other thing is that, with all custom ROM's I already dealt with, my phone was always too hot and I thought it was something normal as it's a Quadcore processor and the phones LED backlight are very strong. But, when I returned my phone to stock, I could see that I was wrong, what happens with all custom ROM's around is that kernels out there, somehow, doesn't work exactly the same as stock ones. Manufacturers configure something more on kernel/driver/software that avoids phone becoming too hot. So I saw that, to do the same as they do, I should understand my phone's hardware in depth to know what are the correct drivers, what is in stock kernel/driver/software that controls better phone's temperature.... and then implement it in my own ROM. The time to learn about it all, I don't have. I tried to download many kernel sources out there to build too, like Loller79's Solid Kernel. But every time I tried to build, it would give me an error message telling that BATT_2100_LGE was undeclared. If Loller built his binaries based on the sources in his GIT, why his builds weren't failing? If I download CM's GPROJ kernel source I can build it without a problem. I tried with his sources because his kernel binary could boot this pure AOSP build successfuly.
The latest build I tried was with CM's device tree and GPROJ kernel, it booted but stuck at bootscreen and lost CWM, when I booted into it no menu was appearing, just a black background with an android with an open chest. When I tried to return it to stock using LGMobile Support Tool putting phone in download mode, something in that build modified, somehow, the Phone's USB PID and the LG software couldn't detect my phone. The last chance I had to return it to stock was using LG Flashtool 2014 that ignored everything and just uploaded the firmware to the phone.
Thanks for your input here @GalaticStryder

HTC One M9 WWE - CPU unknown and a bunch or weird issues

Hello everyone,
I'm having problems trying to figure it out what's happening with my HTC One M9. Right now the phone is
S-OFF
Software status: modified
Bootloader unlocked​
It's running latest software 3.35.401.12. Upgraded via official OTA from 1.32.401.8 (flashed using link found here).
The problem I have right now is that when I reboot in download mode and chose hardware information the CPU appears unknown and some other weird stuff. Quote:
LCD: HIME FHD Tianma/Renesas video mode dsi panel?
CPU: UNKNOWN
CPU rev: 2.1
DDR: 00000001, 3GB
cx voltage Error
mx voltage Error
No CPU param
RFG_3: Error
CRADIO: N/A​
The phone works properly most of the times, but after every some time (might be month or even 2 days) it reboots itself and then is unusable unless I do a factory reset. After the "fatal" reboot I was able to pull logs and they were full with stuff like this:
HTML:
07-13 16:33:43.069 22059 22059 E AndroidRuntime: FATAL EXCEPTION: main
07-13 16:33:43.069 22059 22059 E AndroidRuntime: Process: com.google.process.gapps, PID: 22059
07-13 16:33:43.069 22059 22059 E AndroidRuntime: java.lang.RuntimeException: Unable to start receiver com.google.android.gms.auth.be.proximity.authorization.bt.AuthorizationBluetoothService$AutoStarter: android.database.sqlite.SQLiteException: Can't downgrade database from version 2 to 1
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.app.ActivityThread.handleReceiver(ActivityThread.java:2824)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.app.ActivityThread.access$1800(ActivityThread.java:150)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1484)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.os.Looper.loop(Looper.java:168)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5845)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:797)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:687)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: Caused by: android.database.sqlite.SQLiteException: Can't downgrade database from version 2 to 1
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.database.sqlite.SQLiteOpenHelper.onDowngrade(SQLiteOpenHelper.java:360)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:254)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:163)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at com.google.android.gms.auth.be.proximity.b.a.a(SourceFile:43)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at com.google.android.gms.auth.be.proximity.b.c.a(SourceFile:175)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at com.google.android.gms.auth.be.proximity.authorization.bt.b.a(SourceFile:213)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at com.google.android.gms.auth.be.proximity.authorization.bt.AuthorizationBluetoothService$AutoStarter.onReceive(SourceFile:246)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: at android.app.ActivityThread.handleReceiver(ActivityThread.java:2810)
07-13 16:33:43.069 22059 22059 E AndroidRuntime: ... 8 more
07-13 16:33:43.684 22098 22098 E AndroidRuntime: FATAL EXCEPTION: main
I got the phone SH with Viper ROM on it. It had issues related to WiFi hardware and also random reboots (but after reboot everything worked). Then I tried to back to stock rom/firmware and the phone worked for ~ 3-4 months. Then it did the reboot happened, I did a factory reset, and worked again for ~ 2 days.
Any ideas how I can fix/debug this? Or can it that my MID and CID are completely wrong and I need a different ROM?
mid: 0PJA10000
cid: HTC__102​

Did you flash twrp too?. Which version twrp do you have, which version supersu?.
A LOT of sqlite issues there, could be related rather than responsible..
Beamed in by telepathy.

I don't have TWRP and no root. I try to keep my phones as stock as possible since I don't need that stuff. The error log is after the "reboot" happened. The events succeeded as following
reboot (out of the blue)
reboot loop for a while
I'm not sure, but I think I was able to clear the cache from bootloader/recovery
phone started by I had a lot of issues (Google Apps keep crashing)
fetched the log (posted above)
So I also think the logs are more like the effect of the problem. I wasn't able to fetch the kernel logs (I saw that you can usually ready what caused a kernel panic), but since was happening twice now, I expect it to happen again. That's why I want to be prepared and try to get as much information as I need.
Another theory is that NAND is broken, and the phone works until it gets to write in a bad block. But I don't know how to properly test that.
BTW: the phone is my backup phone. So I can do a lot of test with it for the next few days without worrying about data.

Sorry for the double post, but I don't want to create another topic for this. I tried to make a nandroid backup today, but without flashing twrp
Code:
fastboot boot twrp-2.8.7.0-hima.img
I selected all partitions, except cache, but this happened (see link to "screenshot" below). Is it normal? Does it mean anything? I mounted system as "read-only".
i.imgur.com/RQsbxzT.jpg (apparently I'm not allowed to post links, so you have to copy/paste this)

com.android.phone crashes - anyone have source code for mediatek telephony apk?

I have a Q7 (LM-Q610YM) which crashes whenever I put a SIM in it. Boots fine without a SIM, but as soon as it connects to the network the com.android.phone process crashes. I have never rooted the phone, and have tried a full factory reset.
The top of the stack trace in the logcat is:
Code:
--------- beginning of crash
E AndroidRuntime: FATAL EXCEPTION: DcHandlerThread
E AndroidRuntime: Process: com.android.phone, PID: 1955
E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'int java.lang.Enum.ordinal()' on a null object reference
E AndroidRuntime: at com.mediatek.internal.telephony.dataconnection.DcFailCauseManager.getSuggestedRetryDelayByOp(DcFailCauseManager.java:218)
E AndroidRuntime: at com.mediatek.internal.telephony.dataconnection.MtkDataConnection.getSuggestedRetryDelay(MtkDataConnection.java:1541)
E AndroidRuntime: at com.mediatek.internal.telephony.dataconnection.MtkDataConnection$MtkDcActivatingState.processMessage(MtkDataConnection.java:937)
E AndroidRuntime: at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:992)
E AndroidRuntime: at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:809)
E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
And I'm trying to find out exactly what it is trying to do here in case there is something I can do to fix it.
Does anyone have any idea where I can find the source to the com.mediatek.internal.telephony.dataconnection.DcFailCauseManager?
Alternatively, I have the KDZ file for a similar build (Q610YM10e_00_0117.kdz). I have extracted the dz file and the contained bin files, but not having any luck trying to combine the multiple "system_a_999999.bin" files into a useable file system. The first file has what looks like a valid ext4 header, but if I just concatenate them all together the resulting file appears to be too small and fails to mount with the following error:
Code:
EXT4-fs (loop1): bad geometry: block count 932166 exceeds size of device (620672 blocks)
LM-Q610YM
Android Version: 8.1.0
Kernel Version 3.18.79
Build Number: Q11019
Software Version: V10e-AUS-XX
Thanks

[10] LineageOS 17.1 for z3

{
"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:
/*
* 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.
*/
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Images
Here are some Screenshots of this ROM.
Ask me
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
Installation instructions
Prerequisites:
Unlocked Sony Xperia Z3
Latest firmware .291
Fastboot drivers to install TWRP
Micro-USB Cable to connect your phone to your computer
Install:
Reboot to TWRP. *
Wipe cache, dalvik cache, data and system.
Format data to get rid of encryption.
Install ROM.
Install 10.0 Gapps for ARM. **
* recommended TWRP: Download TWRP
** optional
Update:
Get the latest build
Boot into TWRP
Flash the downloaded build
Reboot, if you don't wipe system backuptool will handle to reapply your modifications, for example: GApps.
Downloads
Download ROM
MD5: 78a54bc2c55ce935a97b4c16cebe3c69
Addons
OpenGapps
BiTGApps
microGISG (Alternative GApps microG based)
Magisk
SU-Addon
Thanks
Whole LineageOS Team for this amazing ROM
@rcstar6696
@Myself5
@drakonizer
@tomascus
@koron393
@nailyk
@SpiritCroc
I hope I haven't forgot anyone
Bugs
WHAT'S BROKEN
Tell me
XDA:DevDB Information
LineageOS 17.1 z3, ROM for the Sony Xperia Z3
Contributors
NeoArian & Mr.Tom_Tom
Donate to support development:
Donate via PayPal to NeoArian *** Our main contributor for LineageOS 16 & 17 for Z3 and Z3 Compact ***
Donate via PayPal to LineageOS
ROM OS Version: 10.x
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 2020-08-18
Stable Release Date: 2020-05-01
Current Beta Version: 2020-02-23
Beta Release Date: 2020-02-08
Created 2019-10-17
Last Updated 2020-08-18

Working LOS17 build achieved
Yep, here it is: LineageOS 17 with Android 10 for our good old Z3. Shinano's not dead (yet)!
Thanks to @NeoArian for sharing repos, manifests and some hints. Behavior seems to be similar to the Z3c build.
The following links are provided for testing purposes only and may be deleted in a few days, please refer to the "official" download links of the thread owner (thanks @ronidianpatisa).
Warning: the links below are now outdated, use the download links in post #1 please
Download: LOS 17 ROM for Z3, compiled as userdebug for TESTING ONLY (alternate hoster here)
Download: Related MD5 checksum file
Download: TWRP for Z3, compatible with Android 10 ROMs for TESTING ONLY
Download: GAPPS BETA
What I have tested so far: checklist working/not working (again, thanks to @NeoArian for this idea and the initial list)

What about Z3 Dual support ? Can D6633 users test the rom safely ?

Thanks @ MrTom_Tom for the sharing of the early LOS 17 build. Very nice from you.
One question: For what stands tbd in the linked checklist?
Nevetheless i will wait for the builds from NeoArian with working encryption.

I have tested your Android 10 rom for z3! Here it is some issues that I have found!
1. when device is power off, if that time you charge your phone until you unplug usb charge cable you cant turn on your phone.
2. when you flash android 10 test rom zip and gapps zip , your sony xperia z3 logo will start and reset itself "loop" until you hold power button and volume up key hold together to power off your phone. Solution that I find is " after you power off phone, Hold power button and volume down key 5 sec , twrp recovery windows will pop up, then Wipe cache, dalvik cache, data and system. 1. first, install android 10 zip rom ,reboot phone then power off the phone, reboot in twrp recovery and flash gapps- pico or micro.
3. Battery percentage icon doesn't show on status bar.
4. some google sound cant be saved.
5. Pixel launcher crashes all the times.
6. power off charge doesn't show battery percentage.. .. during the charge screen doesn't turn off. I guess, these are common lineageOS kernel issue .
7. There is no sony xperia z3 FM radio app..
8. Digital wellbeing apps keep stoping.
.
.
.

dhacke said:
[...] i will wait for the builds from NeoArian with working encryption.
Click to expand...
Click to collapse
Yes, please do not use this build as a daily driver yet! But we are happy for every feedback on the test build.
dhacke said:
For what stands tbd in the linked checklist?
Click to expand...
Click to collapse
tbd = to be determined = not yet tested
elmxx said:
1. when device is power off, if that time you charge your phone until you unplug usb charge cable you cant turn on your phone.
2. when you flash android 10 test rom zip and gapps zip , your sony xperia z3 logo will start and reset itself "loop" until you hold power button and volume up key hold together to power off your phone. Solution that I find is " after you power off phone, Hold power button and volume down key 5 sec , twrp recovery windows will pop up, then Wipe cache, dalvik cache, data and system. 1. first, install android 10 zip rom ,reboot phone then power off the phone, reboot in twrp recovery and flash gapps- pico or micro.
3. Battery percentage icon doesn't show on status bar.
4. some google sound cant be saved.
5. Pixel launcher crashes all the times.
6. power off charge doesn't show battery percentage.. .. during the charge screen doesn't turn off. I guess, these are common lineageOS kernel issue .
7. There is no sony xperia z3 FM radio app..
8. Digital wellbeing apps keep stoping.
Click to expand...
Click to collapse
First of all, thanks for testing and providing feedback!
Regarding your comments:
1. Confirm, known issue: checklist working/not working
2. Are you sure you wiped DATA during your first flash? I do not think it is necessary to wipe SYSTEM.
3. Cannot confirm that issue. Icon is present, and when you swipe down, a percentage value is shown next to the icon.
4. Not sure what you mean by that
5. This is by design since Android P, unfortunately. Please see this explanation.
6. I guess You're right
7. Confirm, known issue. (Honestly speaking I was not expecting that someone will miss that FM radio.)
8. I would expect that there are some dependencies to other google stuff. Can someone confirm that?

Thanks you for your concern and your hard work along with your dedication.
Mr.Tom_Tom said:
Yes, please do not use this build as a daily driver yet! But we are happy for every feedback on the test build.
tbd = to be determined = not yet tested
First of all, thanks for testing and providing feedback!
Regarding your comments:
1. Confirm, known issue: checklist working/not working
2. Are you sure you wiped DATA during your first flash? I do not think it is necessary to wipe SYSTEM.
3. Cannot confirm that issue. Icon is present, and when you swipe down, a percentage value is shown next to the icon.
4. Not sure what you mean by that
5. This is by design since Android P, unfortunately. Please see this explanation.
6. I guess You're right
7. Confirm, known issue. (Honestly speaking I was not expecting that someone will miss that FM radio.)
8. I would expect that there are some dependencies to other google stuff. Can someone confirm that?
Click to expand...
Click to collapse
----------------------------------------------------------------------
Yes, I wiped cache, dalvik cache, data but I did wipe system either. May be wipe the SYSTEM wasn't such a good idea!
ignore " 4. some google sound cant be saved."
Offline FM radio my favorite apps as you know you don't need internet to listen stations.
You are right , when you swipe down, a percentage value is shown next to the icon but without swipe down you wont able to see percentage value even if you enable it.
I think this rom will be better then pie rom.... Thanks for your time.

Mr.Tom_Tom said:
Yes, please do not use this build as a daily driver yet! But we are happy for every feedback on the test build.
tbd = to be determined = not yet tested
First of all, thanks for testing and providing feedback!
Regarding your comments:
1. Confirm, known issue: checklist working/not working
2. Are you sure you wiped DATA during your first flash? I do not think it is necessary to wipe SYSTEM.
3. Cannot confirm that issue. Icon is present, and when you swipe down, a percentage value is shown next to the icon.
4. Not sure what you mean by that
5. This is by design since Android P, unfortunately. Please see this explanation.
6. I guess You're right
7. Confirm, known issue. (Honestly speaking I was not expecting that someone will miss that FM radio.)
8. I would expect that there are some dependencies to other google stuff. Can someone confirm that?
Click to expand...
Click to collapse
On Android pie, digital wellbeing is not working unless gapps is installed. After installing gapps, digital wellbeing works like a charm. At least on android pie, I can confirm that.

Deleted

Today I took a look at the issue with Digital Wellbeing as reported by @elmxx.
I can confirm the issue - when trying to access Digital Wellbeing through Settings, the app force closes.
Log Cat excerpt:
Code:
10-19 21:47:20.091 19366 19366 D AndroidRuntime: Shutting down VM
10-19 21:47:20.092 19366 19366 E AndroidRuntime: FATAL EXCEPTION: main
10-19 21:47:20.092 19366 19366 E AndroidRuntime: Process: com.google.android.apps.wellbeing, PID: 19366
10-19 21:47:20.092 19366 19366 E AndroidRuntime: java.lang.RuntimeException: java.lang.SecurityException: getUnsuspendablePackagesForUser: Neither user 10100 nor current process has android.permission.SUSPEND_APPS.
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at jex.run(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:883)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:100)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7356)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: Caused by: java.lang.SecurityException: getUnsuspendablePackagesForUser: Neither user 10100 nor current process has android.permission.SUSPEND_APPS.
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:2071)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2039)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1987)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.content.pm.IPackageManager$Stub$Proxy.getUnsuspendablePackagesForUser(IPackageManager.java:7072)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.app.ApplicationPackageManager.getUnsuspendablePackages(ApplicationPackageManager.java:2368)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at bzd.get(PG:1)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at doj.get(PG:10)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at bzb.a(PG:2)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at kik.a(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at kxx.a(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at kxy.run(PG:27)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at laq.run(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at jgl.run(PG:3)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at jen.run(PG:4)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at java.lang.Thread.run(Thread.java:919)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: Caused by: android.os.RemoteException: Remote stack trace:
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.app.ContextImpl.enforce(ContextImpl.java:1896)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1924)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at com.android.server.pm.PackageManagerService.getUnsuspendablePackagesForUser(PackageManagerService.java:13936)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:3326)
10-19 21:47:20.092 19366 19366 E AndroidRuntime: at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:4028)
10-19 21:47:20.092 19366 19366 E AndroidRuntime:
I think the key info here is:
Code:
Neither user 10100 nor current process has android.permission.SUSPEND_APPS
I will look into that in more detail later, but it might be not that simple that there are some GAPPS missing.
Update:
I guess I found a solution, test was successful and submitted a patch already. Problem should be fixed in future builds.

elmxx said:
Offline FM radio my favorite apps as you know you don't need internet to listen stations.
Click to expand...
Click to collapse
As you @elmxx have been the first to provide a detailed feedback I took some time to look after your FM Radio request, see updated post #2. It isn't working perfect as explained here by @NeoArian.
AbdullahSayed said:
What about Z3 Dual support ? Can D6633 users test the rom safely ?
Click to expand...
Click to collapse
Sorry, I have zero experience with the Dual Sim variant, I do not hink it will currently work.

FM Radio
Thanks adding FM Radio app. it works well.
E-mail app. keeps closed. The one "e-mail app" which it comes with lineageos. I just want to let you know.
Thanks for your time.

Thanks for the great work guys! It's awesome to see our shinano getting a 10 build. Will flash ASAP. Keep it up!

elmxx said:
E-mail app. keeps closed. The one "e-mail app" which it comes with lineageos. I just want to let you know.
Click to expand...
Click to collapse
Yes, ignore the LOS email and calender app for the moment, they are buggy but the LOS team is working hard to fix them soon.

Flashing LineageOS rom without Gapps!
I just did flash lineageos rom without flashing Gapps! Here is what I found.......
Every lineageos apps work fine except message app. not getting Text Message Notifications. ------> " google message app works fine".
By the way, May be Gapps beta caused E-mail "keep closed" issue! I am not sure.

C:\adb>fastboot flash recovery TWRP-Z3-recovery-Android10-2019-10-11-TESTING.img
sending 'recovery' (13310 KB)...
OKAY [ 0.687s]
writing 'recovery'...
OKAY [ 0.906s]
finished. total time: 1.594s
fastboot reboot-bootloader
I can not boot in to recovery ?????

Technoolli said:
C:\adb>fastboot flash recovery TWRP-Z3-recovery-Android10-2019-10-11-TESTING.img
sending 'recovery' (13310 KB)...
OKAY [ 0.687s]
writing 'recovery'...
OKAY [ 0.906s]
finished. total time: 1.594s
fastboot reboot-bootloader
I can not boot in to recovery ?????
Click to expand...
Click to collapse
try "fastboot flash FOTAKernel TWRP-Z3-recovery-Android10-2019-10-11-TESTING.img"
(hopefully its twrp 3.3.1 - otherwise download it https://downloads.sourceforge.net/p...-t3981381&ts=1571749352&use_mirror=netcologne )
enter recovery by pressing vol down + power.
---------- Post added at 01:28 PM ---------- Previous post was at 01:25 PM ----------
---------- Post added at 01:25 PM ---------- Previous post was at 01:17 PM ----------
elmxx said:
Thanks adding FM Radio app. it works well.
E-mail app. keeps closed. The one "e-mail app" which it comes with lineageos. I just want to let you know.
Thanks for your time.
Click to expand...
Click to collapse
aaahhhh.. the fm radio... the one least appreciated feature of modern phones.
have you found a way to change stations with the headset button?

nikapos said:
try "fastboot flash FOTAKernel TWRP-Z3-recovery-Android10-2019-10-11-TESTING.img"
(hopefully its twrp 3.3.1 - otherwise download it https://downloads.sourceforge.net/p...-t3981381&ts=1571749352&use_mirror=netcologne )
enter recovery by pressing vol down + power.
---------- Post added at 01:28 PM ---------- Previous post was at 01:25 PM ----------
---------- Post added at 01:25 PM ---------- Previous post was at 01:17 PM ----------
aaahhhh.. the fm radio... the one least appreciated feature of modern phones.
have you found a way to change stations with the headset button?
Click to expand...
Click to collapse
I do not get into recovery like that, fastboot flashing does not work anymore ...

Technoolli said:
I do not get into recovery like that, fastboot flashing does not work anymore ...
Click to expand...
Click to collapse
ok then, start over.
1. flash original .291 rom with flashtool
2. make sure your bootloader is unlocked
3. enter fastboot to flash 3.3.1 twrp recovery to FOTAPartition
4. press power button holding down volume button until you feel one short vibration.
hope this does the trick. however this is not the proper thread to discuss unbricking or installing recoveries.

Thank you, but with the Flashtool I can not select the firmware ... Can I flash it somehow different? I just can not do more in the gas pedal, also I do not come in the recovery or Android system ... help

[EOL][11.0][OFFICIAL] LineageOS 18.1 for Oneplus 5 & 5T

{
"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 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.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
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.
*/
HOW TO INSTALL LINEAGEOS:
- Official instructions
- In short: sideload in Lineage recovery (suggested) / flash in TWRP
HOW TO UPDATE LINEAGEOS:
- Download update from Updater app
- Install update
DOWNLOADS:
LineageOS 18.1: Official Oneplus 5, Official Oneplus 5T
Google Apps: MindTheGapps
Recovery: Suggested: Lineage recovery for Oneplus 5, Oneplus 5T | Alternative: TWRP
DEVELOPER RESOURCES
LineageOS source code:
- https://github.com/LineageOS
Device tree:
- android_device_oneplus_cheeseburger
- android_device_oneplus_dumpling
- android_device_oneplus_msm8998-common
Kernel:
- android_kernel_oneplus_msm8998
Android version: Android 11
Kernel version: Linux 4.4.y
Required firmware: OxygenOS 10.0.1 (shipped with ROM, no need to install manually)
Telegram group: https://t.me/los_op5

Issues:
- Safetynet does not pass. Magisk hide & MagiskHide Props Config help here.
- Wireless display does not work
Notes:
- Relocking bootloader https://forum.xda-developers.com/t/...s-18-1-for-oneplus-5-5t.4173997/post-84770085 (thanks for @Eric_Lev ) (not suggested though)

Really appreciate your efforts dude
Will try this out

Would you consider removing the lineage recovery from future builds?

Any idea about oneplus 5t

Added to the OnePlus 5 Index Thread here.

T1mb3 said:
ROM OS Version: 2.3.x Gingerbread
Click to expand...
Click to collapse
You most probably forgot to update this entry, just wanted to let you know. Thanks for this ROM Really appreciated!

JulianXhokaxhiu said:
You most probably forgot to update this entry, just wanted to let you know. Thanks for this ROM Really appreciated!
Click to expand...
Click to collapse
There actually is no option higher than Android 10 yet

JulianXhokaxhiu said:
You most probably forgot to update this entry, just wanted to let you know. Thanks for this ROM Really appreciated!
Click to expand...
Click to collapse
T1mb3 said:
There actually is no option higher than Android 10 yet
Click to expand...
Click to collapse
As you can read in Big Changes To XDA Forums are Coming Soon with the transition to Xenforo all DevDB threads will eventually be reverted to "normal" threads. For this reason, it was decided not to add the option "A 11" anymore.

T1mb3 said:
There actually is no option higher than Android 10 yet
Click to expand...
Click to collapse
Having said this...
Oswald Boelcke said:
As you can read in Big Changes To XDA Forums are Coming Soon with the transition to Xenforo all DevDB threads will eventually be reverted to "normal" threads. For this reason, it was decided not to add the option "A 11" anymore.
Click to expand...
Click to collapse
...you can always edit the first post using the edit button at the end of the post (instead of using the edit project option for DevDB threads) and manually change it to Android 11.

Is it rooted?
Does this pass SafetyNet?

sergio_sant said:
Is it rooted?
Does this pass SafetyNet?
Click to expand...
Click to collapse
This is not rooted by default. Latest Magisk works for that purpose.
This does not pass safetynet. I will have to look for a solution. Other ROMs use kernel-side patches for safetynet and those are not allowed in LineageOS.

UPDATE:
* Sync LineageOS sources
* SELinux is now enforcing
* TWRP does not get overwritten by Lineage recovery for now. This may change when LineageOS makes their decision on the topic.
* More detailed changelog
* Download

T1mb3 said:
UPDATE:
* Sync LineageOS sources
* SELinux is now enforcing
* TWRP does not get overwritten by Lineage recovery for now. This may change when LineageOS makes their decision on the topic.
* More detailed changelog
* Download
Click to expand...
Click to collapse
Hi，bro. I am trying to build los18 for oneplus5t, should I use pick this commit https://review.lineageos.org/c/LineageOS/android_packages_apps_Settings/+/287931 as you said to avoid that TRWP does get overwritten by Lineage recovery， is it right？

kpzhao said:
Hi，bro. I am trying to build los18 for oneplus5t, should I use pick this commit https://review.lineageos.org/c/LineageOS/android_packages_apps_Settings/+/287931 as you said to avoid that TRWP does get overwritten by Lineage recovery， is it right？
Click to expand...
Click to collapse
I did it this way: https://github.com/LineageOS-cheese...mmit/65b18d38368955a5a9cac58d09bf5c867624fb53

Great work, thanks for this rom. I LOVE IT
this is the 1st custom rom i install and the instructions were smooth. I did upgrade because oneplus stopped supporting OP5 and just sent a message in the community app giving fake excuses for the delays.
I noticed this bug
some apps that has the option to login with fingerprint doesn't work properly ( i.e. TD Canada Trust, Manulife)
as soon as the phone tries to communicate with the fingerprint reader, it freezes. 1st login in Manulife app, it asks if you want to allow or deny access to fingerprint reader, if you deny, it will let you login with the password if you remember it. if you accept, it hangs.
In TD Canada Trust app, first time you login with your password, it gives you a popup asking you if you want to enable fingerprint login, and you cant press anything other than closing the app.

T1mb3 said:
UPDATE:
* Sync LineageOS sources
* SELinux is now enforcing
* TWRP does not get overwritten by Lineage recovery for now. This may change when LineageOS makes their decision on the topic.
* More detailed changelog
* Download
Click to expand...
Click to collapse
Can't call through VoLte, Volte cannot call!
Cannot tap to wake(settings-Display-Advanced-Tap to wake)

Hello，I build los18 for 5t successfully as your building guild . However it is no sim card and I get this log
10-12 10:12:46.522 21233 21233 E PhoneInterfaceManager: [PhoneIntfMgr] getIccId: No UICC
10-12 10:12:46.621 21233 21233 E AndroidRuntime: FATAL EXCEPTION: main
10-12 10:12:46.621 21233 21233 E AndroidRuntime: Process: com.android.phone, PID: 21233
10-12 10:12:46.621 21233 21233 E AndroidRuntime: java.lang.IllegalArgumentException: value of system property 'gsm.version.baseband' is longer than 91 characters: MPSS.AT.2.0.c4.7-00070-8998_GEN_PACK-2.271073.1.277412.1,MPSS.AT.2.0.c4.7-00070-8998_GEN_PACK-2.271073.1.277412.1
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.SystemProperties.set(SystemProperties.java:236)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.sysprop.TelephonyProperties.baseband_version(TelephonyProperties.java:140)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.telephony.TelephonyManager.setBasebandVersionForPhone(TelephonyManager.java:10107)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.telephony.GsmCdmaPhone.handleMessage(GsmCdmaPhone.java:2850)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7656)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
10-12 10:12:46.656 764 3655 E IPCThreadState: attemptIncStrongHandle(77): Not supported
10-12 10:12:46.656 764 3545 E IPCThreadState: attemptIncStrongHandle(82): Not supported
10-12 10:12:46.656 764 3830 E IPCThreadState: attemptIncStrongHandle(79): Not supported
10-12 10:12:46.657 764 3545 E IPCThreadState: attemptIncStrongHandle(78): Not supported
10-12 10:12:46.784 21323 21323 E CarrierIdProvider: read carrier list from ota pb failure: java.io.FileNotFoundException: /data/misc/carrierid/carrier_list.pb: open failed: ENOENT (No such file or directory)
10-12 10:12:47.593 0 0 E [20201012_10:12:47.591117]@3 synaptics,s3320: all finger up
Could you give me some suggestion?

kpzhao said:
Hello，I build los18 for 5t successfully as your building guild . However it is no sim card and I get this log
10-12 10:12:46.522 21233 21233 E PhoneInterfaceManager: [PhoneIntfMgr] getIccId: No UICC
10-12 10:12:46.621 21233 21233 E AndroidRuntime: FATAL EXCEPTION: main
10-12 10:12:46.621 21233 21233 E AndroidRuntime: Process: com.android.phone, PID: 21233
10-12 10:12:46.621 21233 21233 E AndroidRuntime: java.lang.IllegalArgumentException: value of system property 'gsm.version.baseband' is longer than 91 characters: MPSS.AT.2.0.c4.7-00070-8998_GEN_PACK-2.271073.1.277412.1,MPSS.AT.2.0.c4.7-00070-8998_GEN_PACK-2.271073.1.277412.1
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.SystemProperties.set(SystemProperties.java:236)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.sysprop.TelephonyProperties.baseband_version(TelephonyProperties.java:140)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.telephony.TelephonyManager.setBasebandVersionForPhone(TelephonyManager.java:10107)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.telephony.GsmCdmaPhone.handleMessage(GsmCdmaPhone.java:2850)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7656)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
10-12 10:12:46.621 21233 21233 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
10-12 10:12:46.656 764 3655 E IPCThreadState: attemptIncStrongHandle(77): Not supported
10-12 10:12:46.656 764 3545 E IPCThreadState: attemptIncStrongHandle(82): Not supported
10-12 10:12:46.656 764 3830 E IPCThreadState: attemptIncStrongHandle(79): Not supported
10-12 10:12:46.657 764 3545 E IPCThreadState: attemptIncStrongHandle(78): Not supported
10-12 10:12:46.784 21323 21323 E CarrierIdProvider: read carrier list from ota pb failure: java.io.FileNotFoundException: /data/misc/carrierid/carrier_list.pb: open failed: ENOENT (No such file or directory)
10-12 10:12:47.593 0 0 E [20201012_10:12:47.591117]@3 synaptics,s3320: all finger up
Could you give me some suggestion?
Click to expand...
Click to collapse
Hi,
Pick this commit: https://github.com/LineageOS-cheese...mmit/def355758a279ff756f2f6f580db161aa0fb805b

T1mb3 said:
Hi,
Pick this commit: https://github.com/LineageOS-cheese...mmit/def355758a279ff756f2f6f580db161aa0fb805b
Click to expand...
Click to collapse
You are a good man, sir. I am very appreciated for your help.