Develop Bugs

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)

[ROM][Official] AICP - 12.1 - N 7.1 amami

{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago and since then evolved into a mature ROM with the BEST community you can find!!!
Until Lollipop, the Rom has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM when it comes to hardware, drivers and some features.
With the rebrand of CM to LineageOS (LAOS) we are now actually LAOS based with some tweaks from AOSP.
If there are any bugs, either we will sort them out or LAOS team, if it concerns their code base. This rom isn't LAOS supported, so no need to report errors or bugs to them!!
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.
*
*/
Feature list (rough Overview)
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
maxwen
DU team
SlimRoms team
Resurrection Remix team
OmniRom team
SuperLamic, Sony-Lineage-3.4 team, Hazou, Sonyxperiadev
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 12.1
Download link: http://dwnld.aicp-rom.com/?device=amami
No more official Nougat support since focus shifted to Oreo! You can still get my unofficial Nougat builds here:
https://basketbuild.com/devs/SpiritCroc/amami/AICP-n7.1
Full Changelog link: http://dwnld.aicp-rom.com/?device=amami
Google Apps:
Beans gapps
Or
Open GApps (ARM or ARM64 7.1 pico or nano, depending on your phone's architecture)
If you experience a black screen in some apps (e.g. in Youtube or in camera app), please go to Developer options and enable "Disable HW overlays". Alternatively, you can also add a quick setting for this setting after having enabled developer settings. This setting is not persistent, so you will have to set it after each boot!
Reboot to recovery not working
You tell...
The ROM should contain everything you need to enjoy Android Nougat. You don't need to install any Add-Ons, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing, and if possible avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash:
(Again: Don't do it if you don't know it!)
Make sure you have real recovery!
Download the ROM and GApps and transfer them to your device
Boot to recovery (TWRP recommended)
Wipe system, Cache, data and ART/Dalvik cache
Flash ROM Zipfile
Flash/Install GApps (optional, needed for e.g. Google Playstore to work)
Flash/Install the root solution of choice (optional)
Reboot to system
The ROM has GApps persistance in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every OTA update (= ROM Update)!
Supported root solutions:
Magisk v13.x
SuperSU - stable and beta available (Site by CCMT that took over the the marketing from chainfire)
SuperSU - direct download link for the latest SuperSU directly from the dev (chainfire)
Lineage SU-addon (check your needed version: 14.1 arm or arm64) -> the removal zip is available here too.
PREREQUISITE FOR OTA:
To be able to flash using the buildin OTA app that needs TWRP recovery installed to work.
You can still use LAOS recovery and OTA app, but you will need to download the zip file and flash it manually from within your recovery. Zip gets saved in the "AICP_ota" folder on your internal storage.
Please be sure that you are on the latest TWRP recovery.
If you want to contribute to the AICP or wanna see what is being worked on/merged, feel free to visit our Gerrit review system. (Link is at the bottom!!!)
IceColdJelly AICP G+ community
Kernel source: https://github.com/AICP/kernel_sony_msm8974/tree/n7.1
ROM & Additional links:
Gerrit Code Review
Github
You want to see a normal night at the "DEV office", click here!!​
XDA:DevDB Information
Android Ice Cold Project (AICP) 12.1 Amami, ROM for the Sony Xperia Z1 Compact
Contributors
SpiritCroc
Source Code: https://github.com/AICP
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: Unlocked bootloader, real recovery
Based On: AOKP, CyanogenMod, LineageOS, Omni-ROM, DirtyUnicorns
Version Information
Status: No Longer Updated
Created 2016-07-29
Last Updated 2018-03-02

another new rom How is it going with the camera?

NeoAqr said:
another new rom How is it going with the camera?
Click to expand...
Click to collapse
I heard that it's similar to du

Someone have some Screenshots from this ROM ?

FotoMichi said:
Someone have some Screenshots from this ROM ?
Click to expand...
Click to collapse
It looks like normal marshmallow, but wait, I'll install it and give you some

Here are screenshots!
 @SpiritCroc why SIM card don't working? o

CmDaRkShAdOw said:
@SpiritCroc why SIM card don't working? o
Click to expand...
Click to collapse
It's working for me, although the SIM is not recognized immediately, but a few seconds after boot.
Have you tried a reboot? Clean flash? SIM was working for you on DU, am I right? Have you modified the ROM (Xposed, ...)?

SpiritCroc said:
It's working for me, although the SIM is not recognized immediately, but a few seconds after boot.
Have you tried a reboot? Clean flash? SIM was working for you on DU, am I right? Have you modified the ROM (Xposed, ...)?
Click to expand...
Click to collapse
I was waiting a few minutes. Tried reboot, clean flash(wipe system, data,cache, art) on DU was fine, not modified

CmDaRkShAdOw said:
Here are screenshots!
@SpiritCroc why SIM card don't working? o
Click to expand...
Click to collapse
whoop. new SnapDragon camera UI. I wonder if the camera is more stable than DU's . if it doesn't freeze frequently I will go get it now

NeoAqr said:
whoop. new SnapDragon camera UI. I wonder if the camera is more stable than DU's . if it doesn't freeze frequently I will go get it now
Click to expand...
Click to collapse
Yes. It's more stable than du,and photos are better.

SIM is working for me. AudioFX is crashing when starting to play music. Music playing works, but the crash is annoying and I guess equalizer doesn't work.
Also my bluetooth MAC address has a lot of zeros. Is that normal?
Overall looks like a good MM ROM! Thank you!
EDIT: oh. Very important! Flashing this ROM will overwrite your recovery with CM recovery. I hope that the ROM creator can remove it.

SpiritCroc said:
AICP
Click to expand...
Click to collapse
Sudden battery drain a couple of times on 7/24 build, but love it overall, (i usually assume stuff like that has simething to do with Xposed, etc. anyway). Using newest build now. What would really wrap this up nicely is M5 kernel. The idea has been tossed around a little. @Myself5 has said he's willing to build if someone will maintain, (he doesn't have Z1c anymore). Maybe you'd be a candidate...
[GER]Roxxor said:
SIM is working for me. AudioFX is crashing when starting to play music. Music playing works, but the crash is annoying and I guess equalizer doesn't work.
Also my bluetooth MAC address has a lot of zeros. Is that normal?
Overall looks like a good MM ROM! Thank you!
EDIT: oh. Very important! Flashing this ROM will overwrite your recovery with CM recovery. I hope that the ROM creator can remove it.
Click to expand...
Click to collapse
We all should use real recovery by now - can't be overwritten.

levone1 said:
We all should use real recovery by now - can't be overwritten.
Click to expand...
Click to collapse
Of course real recovery can be overwritten, why shouldn't it? It just depends if the flashing procedure writes a new recovery to the recovery partition or not. This is the first time that a ROM flash overwrote my recovery.
And I am using it. I did the Emma bootloader upgrade once and didn't have any compatibility problems with ROMs requiring real recovery. And I used TWRP 3.0.2 and flash it by "fastboot flash recovery".
Didn't this flashing procedure overwrite the recovery for anybody else? I flashed the 29.07 build.
EDIT: Ok. I do not get what is happening here... I flashed TWRP via fastboot and it is still launching CM recovery. I did not experience this strange behavior with CM12.1, DU MM and FXP MM AOSP. With all those ROMs TWRP started without issues.
EDIT2: I found the issue. I think this ROM installs a "unreal recovery" in system. If I push the VolDown Button from the moment I push Power, then TWRP starts. If I only push VolDown when the violet light appears, then CM recovery starts. I find this quite confusing, and I guess this is aimed at people without real recovery. Would be nice if @SpiritCroc could clarify if this is intentional.
I figured that CM recovery is in system, because if I install RR kernel (boot.img) and TWRP (recovery.img) still CM recovery is started if pressing on violet light. It is the only partition I did not overwrite.

levone1 said:
What would really wrap this up nicely is M5 kernel. The idea has been tossed around a little. @Myself5 has said he's willing to build if someone will maintain, (he doesn't have Z1c anymore). Maybe you'd be a candidate...
Click to expand...
Click to collapse
Well, I don't have any experiences with modifying kernel (I've always used the kernel that comes with the ROM in the past).
I can build the kernel together with the ROM, anything else I'd have to learn first...
[GER]Roxxor said:
Of course real recovery can be overwritten, why shouldn't it? It just depends if the flashing procedure writes a new recovery to the recovery partition or not. This is the first time that a ROM flash overwrote my recovery.
And I am using it. I did the Emma bootloader upgrade once and didn't have any compatibility problems with ROMs requiring real recovery. And I used TWRP 3.0.2 and flash it by "fastboot flash recovery".
Didn't this flashing procedure overwrite the recovery for anybody else? I flashed the 29.07 build.
EDIT: Ok. I do not get what is happening here... I flashed TWRP via fastboot and it is still launching CM recovery. I did not experience this strange behavior with CM12.1, DU MM and FXP MM AOSP. With all those ROMs TWRP started without issues.
EDIT2: I found the issue. I think this ROM installs a "unreal recovery" in system. If I push the VolDown Button from the moment I push Power, then TWRP starts. If I only push VolDown when the violet light appears, then CM recovery starts. I find this quite confusing, and I guess this is aimed at people without real recovery. Would be nice if @SpiritCroc could clarify if this is intentional.
I figured that CM recovery is in system, because if I install RR kernel (boot.img) and TWRP (recovery.img) still CM recovery is started if pressing on violet light. It is the only partition I did not overwrite.
Click to expand...
Click to collapse
Real recovery isn't touched by AICP, it still can be accessed the usual way (first press volume button before pressing power & hold until sony logo appears). It's the same way as in DU. In DU, you cannot reboot to recovery or boot to recovery when the sony logo appears after a normal power on. AICP has an inbuilt recovery (CM recovery in this case) that can be accessed via reboot to recovery or when the notification LED is showing during boot up, which can be used instead of real recovery, but doesn't replace it. That's the intended behaviour. If I find the time I might look into replacing the built-in CM recovery with TWRP.
First press & hold volume button, power on -> device boots recovery partition
Power on while not pressing volume buttons -> device boots into ROM
Power on while not pressing volume buttons, then press volume when notification LED lights up -> tell the ROM you want to access recovery, which has no access to real recovery, but uses inbuilt recovery instead

SpiritCroc said:
AICP has an inbuilt recovery (CM recovery in this case) that can be accessed via reboot to recovery or when the notification LED is showing during boot up, which can be used instead of real recovery, but doesn't replace it. That's the intended behaviour. If I find the time I might look into replacing the built-in CM recovery with TWRP.
Click to expand...
Click to collapse
Thank you very much for clarifying!
About the AudioFX issue(somehow I cant attach files):
Code:
11:22:04.332 819 2920 I MediaFocusControl: AudioFocus requestAudioFocus() from [email protected][email protected] req=1flags=0x0
07-30 11:22:04.335 336 6146 D NuPlayerDriver: reset(0xb3a38120)
07-30 11:22:04.335 336 6146 D NuPlayerDriver: notifyListener_l(0xb3a38120), (8, 0, 0)
07-30 11:22:04.335 336 6198 W AMessage: failed to post message as target looper for handler 0 is gone.
07-30 11:22:04.335 336 6198 D NuPlayerDriver: notifyResetComplete(0xb3a38120)
07-30 11:22:04.337 5999 6011 E MediaPlayer-JNI: JNIMediaPlayerFactory: bIsQCMediaPlayerPresent 0
07-30 11:22:04.337 5999 6011 E MediaPlayer-JNI: JNIMediaPlayerFactory: bIsQCMediaPlayerPresent 0
07-30 11:22:04.338 6181 6181 I HeadsetService: Starting service.
07-30 11:22:04.347 336 3033 W AudioFlinger: createEffect() effect not found
07-30 11:22:04.347 6181 6181 E AudioEffect: set(): AudioFlinger could not create effect, status: -22
07-30 11:22:04.347 6181 6181 E AudioEffects-JNI: AudioEffect initCheck failed -3
07-30 11:22:04.348 6181 6181 E AudioEffect-JAVA: Error code -3 when initializing AudioEffect.
07-30 11:22:04.348 6181 6181 E HeadsetService: Cannot initialize effect engine for type: 0bed4300-ddd6-11db-8f34-0002a5d5c51b Error: -3
07-30 11:22:04.348 6181 6181 E HeadsetService: java.lang.RuntimeException: Cannot initialize effect engine for type: 0bed4300-ddd6-11db-8f34-0002a5d5c51b Error: -3
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.media.audiofx.AudioEffect.<init>(AudioEffect.java:411)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.media.audiofx.Equalizer.<init>(Equalizer.java:139)
07-30 11:22:04.348 6181 6181 E HeadsetService: at org.cyanogenmod.audiofx.HeadsetService$EffectSet.<init>(HeadsetService.java:95)
07-30 11:22:04.348 6181 6181 E HeadsetService: at org.cyanogenmod.audiofx.HeadsetService.saveDefaults(HeadsetService.java:521)
07-30 11:22:04.348 6181 6181 E HeadsetService: at org.cyanogenmod.audiofx.HeadsetService.onCreate(HeadsetService.java:389)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.app.ActivityThread.handleCreateService(ActivityThread.java:2923)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.app.ActivityThread.-wrap4(ActivityThread.java)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1446)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.os.Handler.dispatchMessage(Handler.java:102)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.os.Looper.loop(Looper.java:148)
07-30 11:22:04.348 6181 6181 E HeadsetService: at android.app.ActivityThread.main(ActivityThread.java:5475)
07-30 11:22:04.348 6181 6181 E HeadsetService: at java.lang.reflect.Method.invoke(Native Method)
07-30 11:22:04.348 6181 6181 E HeadsetService: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
07-30 11:22:04.348 6181 6181 E HeadsetService: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
07-30 11:22:04.350 336 336 W AudioFlinger: createEffect() effect not found
07-30 11:22:04.350 6181 6181 E AudioEffect: set(): AudioFlinger could not create effect, status: -22
07-30 11:22:04.350 6181 6181 E AudioEffects-JNI: AudioEffect initCheck failed -3
07-30 11:22:04.350 6181 6181 E AudioEffect-JAVA: Error code -3 when initializing AudioEffect.
07-30 11:22:04.351 6181 6181 D AndroidRuntime: Shutting down VM
07-30 11:22:04.352 6181 6181 E AndroidRuntime: FATAL EXCEPTION: main
07-30 11:22:04.352 6181 6181 E AndroidRuntime: Process: org.cyanogenmod.audiofx, PID: 6181
07-30 11:22:04.352 6181 6181 E AndroidRuntime: Theme: themes:{default=, iconPack:org.twelf.cmtheme}
07-30 11:22:04.352 6181 6181 E AndroidRuntime: java.lang.RuntimeException: Unable to start service [email protected] with Intent { act=android.media.action.OPEN_AUDIO_EFFECT_CONTROL_SESSION cmp=org.cyanogenmod.audiofx/.HeadsetService (has extras) }: java.lang.RuntimeException: Cannot initialize effect engine for type: 0bed4300-ddd6-11db-8f34-0002a5d5c51b Error: -3
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3073)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.app.ActivityThread.-wrap17(ActivityThread.java)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1461)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.os.Looper.loop(Looper.java:148)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5475)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: Caused by: java.lang.RuntimeException: Cannot initialize effect engine for type: 0bed4300-ddd6-11db-8f34-0002a5d5c51b Error: -3
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.media.audiofx.AudioEffect.<init>(AudioEffect.java:411)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.media.audiofx.Equalizer.<init>(Equalizer.java:139)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at org.cyanogenmod.audiofx.HeadsetService$EffectSet.<init>(HeadsetService.java:95)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at org.cyanogenmod.audiofx.HeadsetService.addSession(HeadsetService.java:208)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at org.cyanogenmod.audiofx.HeadsetService.onStartCommand(HeadsetService.java:431)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3056)
07-30 11:22:04.352 6181 6181 E AndroidRuntime: ... 8 more
07-30 11:22:04.354 819 835 W ActivityManager: Process org.cyanogenmod.audiofx has crashed too many times: killing!
EDIT: Additional question: Why did you go for omnirom sources and not directly for sonyxperiadev?

[GER]Roxxor said:
EDIT: Additional question: Why did you go for omnirom sources and not directly for sonyxperiadev?
Click to expand...
Click to collapse
I'm a bit lazy and they have inline kernel building while sonyxperiadev use a prebuilt kernel.
Additionally, they have some more modifications like TWRP configs which can become handy when building some custom ROMs, and they even have some commits cherry-picked from CM device tree (e.g. in order to enable reboot to recovery), while sonyxperiadev is clearly aimed at pure AOSP.
It worked fine when I was experimenting with different device trees for DU, and for now I just stick with it.
I think I'm going to directly fork sonyxperiadev when Nougat arrives, though

Now this thead has explained a lot of my confusion regarding recovery i have tried ACIP but because there was only 2-3 Cpu gouvernors and device was always hot (something is causing increased temps and batt drain)anyway there are 2 recoverys one that we call real recovery and that one after power on which flashes alongside ROM.
And if you lower the freq of cpu you will get random reboots
Sent from my D5503 using XDA-Developers mobile app

Verry nice Rom. Camera is a bit more stable than the du one.
For me Autorotation don't work.

I'm sorry. SIM Card works fine. Last time I had issue while flashing and I ignored it. Today SIM card didn't work on DU. Don't know why.

New build is up.
- Fix sensors not working (e.g. no working auto-rotation)
I was surprised by how few people noticed/complained about that...

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

[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.

[Help Request] Huawei Watch 3-F60 [Model GLL-AL00] install GMS / Play Store

Trying to follow this thread, says the HW3 is eligible, but unsuccessful in logging into MicroG. Has anyone else been able to install Play Store?
Steps so far:
Code:
adb shell pm disable-user com.android.packageinstaller
adb install huagu3.apk
adb shell appops set com.bishua666.luxxx1 GET_USAGE_STATS allow
Disable route to internet.
Set date on phone to July 20, 2020 and sync watch.
Open huagu3 on watch and allow full access
Step 1 successful.
Step 2 immediately closes app
adb install 01_MicroG.apk -> success
Open MicroG and try to add account, app immediately closes.
logcat:
Code:
--------- beginning of crash huagu3
07-20 15:56:27.370 12290 12290 E AndroidRuntime: FATAL EXCEPTION: main
07-20 15:56:27.370 12290 12290 E AndroidRuntime: Process: com.bishua666.luxxx1, PID: 12290
07-20 15:56:27.370 12290 12290 E AndroidRuntime: android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.settings.DATE_SETTINGS }
MicroG:
07-20 15:56:37.557 12395 12395 E AndroidRuntime: FATAL EXCEPTION: main
07-20 15:56:37.557 12395 12395 E AndroidRuntime: Process: com.google.android.gms:ui, PID: 12395
07-20 15:56:37.557 12395 12395 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.google.android.gms/org.microg.gms.auth.login.LoginActivity}: java.lang.UnsupportedOperationException
Appreciate any assistance in advance, thanks.
Ref:
Install native GMS, Google Play Store directly on Harmony OS 3.0 (Tested Feb 2023)
How to install GMS Harmony OS 3.1 has newer processes https://forum.xda-developers.com/t/install-native-gms-on-harmony-os-3-1-tested-may-2023-on-huawei-mate-x3.4583737/ *** IMPORTANT NOTE *** I am working on the step by step instructions, stay...
forum.xda-developers.com
Current Eligible Devices:
Huawei Wear Series
HUAWEI WATCH 3

Hi,
Exactly the same for me ...