I've noticed that multiple people, including myself, have had multiple issues with random reboots on various ICS roms. Well it was driving me crazy, so I decided to catch it in the act. Please see this from my logcat:
Code:
04-18 17:04:36.799 E AlarmManagerService: android_server_AlarmManagerService_set to type=2, 115438.634000000
04-18 17:04:36.799 V AlarmManager: trigger WAKEUP Alarm{41c5fcd8 type 2 android}
04-18 17:04:36.809 W dalvikvm: threadid=13: thread exiting with uncaught exception (group=0x40c231f8)
04-18 17:04:36.809 E android.os.Debug: [email protected] > dumpstate -k -t -n -z -d -o /data/log/dumpstate_sys_error
04-18 17:04:36.809 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: android.server.ServerThread
04-18 17:04:36.809 E AndroidRuntime: java.lang.NoSuchMethodError: com.android.server.WimaxService.access$1002
04-18 17:04:36.809 E AndroidRuntime: at com.android.server.WimaxService$4.onReceive(WimaxService.java:1150)
04-18 17:04:36.809 E AndroidRuntime: at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:728)
04-18 17:04:36.809 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:605)
04-18 17:04:36.809 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:92)
04-18 17:04:36.809 E AndroidRuntime: at android.os.Looper.loop(Looper.java:137)
04-18 17:04:36.809 E AndroidRuntime: at com.android.server.ServerThread.run(SystemServer.java:986)
04-18 17:04:36.834 I dumpstate: Check if stand-alone
04-18 17:04:36.859 I dumpstate: begin
I went back through several saved logcats after these reboots, and the signature looks the same. It looks to me as if the WiMax service (WimaxService.java) is calling an invalid method (com.android.server.WimaxService.access$1002), and causing android server to crash with a FATAL exception.
Now, I'm not a programmer, but does anyone have any ideas on how we can investigate the code and see if we can make a workaround? Thoughts anyone? I'll keep at this.
I'm not a program either, but I know Team Nocturnal had this same issue on a couple of their ROMs and Mijjah was working on it. Not sure if he has any logs of it happening.
I do know he's working on an AOKP rom as well, which I'm using, and I haven't had the issue yet.
Maybe post this in the dev thread of the rom you are using. I think we can all benefit from this Im sick of my phone rebooting while using 4g!!
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)
{
"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...
Hi,
I have just installed LineageOS for microg 19 (19-20220522-microg-bramble) on my Pixel 4a 5g and I am receiving a regular popup every few minutes saying that "Intent Filter Verification Service has stopped".
From what I have read this is used to call another application on the phone (based on what type of thing needs to be handled)??
The logs I am getting with logcat do not seem to lead me towards anything (see below from two examples). I'm not sure if anyone has any suggestions on what could be causing this or where else I can look??
My suspicion is that this is something to do with not having the google apps (using microg instead) but not sure. I did find one other mention of it here, but no solution
Note: I did have LineageOS for microg 18 installed previously which did not exhibit this behaviour...
Example1:
Code:
05-31 23:53:49.627 966 966 D Zygote : Forked child process 10622
05-31 23:53:49.628 1718 2114 I ActivityManager: Start proc 10622:com.android.statementservice/u0a74 for service {com.android.statementservice/androidx.work.impl.background.systemjob.SystemJobService}
05-31 23:53:49.632 10622 10622 I libc : SetHeapTaggingLevel: tag level set to 0
05-31 23:53:49.644 1357 1429 I adbd : jdwp connection from 10622
05-31 23:53:49.646 10622 10622 D ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
05-31 23:53:49.638 0 0 I : c7 10622 binder: 10622:10622 ioctl 40046210 7fea0fb8d4 returned -22
05-31 23:53:49.651 1718 14826 D CompatibilityChangeReporter: Compat change id reported: 168419799; UID 10074; state: DISABLED
05-31 23:53:49.655 10622 10622 D CompatibilityChangeReporter: Compat change id reported: 171979766; UID 10074; state: DISABLED
05-31 23:53:49.658 10622 10622 D ApplicationLoaders: Returning zygote-cached class loader: /system/framework/android.test.base.jar
05-31 23:53:49.667 10622 10622 V GraphicsEnvironment: ANGLE Developer option for 'com.android.statementservice' set to: 'default'
05-31 23:53:49.667 10622 10622 V GraphicsEnvironment: ANGLE GameManagerService for com.android.statementservice: false
05-31 23:53:49.668 10622 10622 V GraphicsEnvironment: Neither updatable production driver nor prerelease driver is supported.
05-31 23:53:49.668 10622 10622 D NetworkSecurityConfig: No Network Security Config specified, using platform default
05-31 23:53:49.668 10622 10622 D NetworkSecurityConfig: No Network Security Config specified, using platform default
05-31 23:53:49.687 10622 10639 D CompatibilityChangeReporter: Compat change id reported: 160794467; UID 10074; state: DISABLED
05-31 23:53:49.689 1718 14826 D CompatibilityChangeReporter: Compat change id reported: 171306433; UID 10074; state: DISABLED
05-31 23:53:49.757 10622 10641 E AndroidRuntime: FATAL EXCEPTION: pool-3-thread-2
05-31 23:53:49.757 10622 10641 E AndroidRuntime: Process: com.android.statementservice, PID: 10622
05-31 23:53:49.757 10622 10641 E AndroidRuntime: java.lang.IllegalStateException: Data cannot occupy more than 10240 bytes when serialized
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.Data.toByteArrayInternal(Data.java:417)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.Data$Builder.build(Data.java:846)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.OverwritingInputMerger.merge(OverwritingInputMerger.java:44)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.impl.WorkerWrapper.runWorker(WorkerWrapper.java:227)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.impl.WorkerWrapper.run(WorkerWrapper.java:137)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.impl.utils.SerialExecutor$Task.run(SerialExecutor.java:91)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at java.lang.Thread.run(Thread.java:920)
05-31 23:53:49.761 1718 10645 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
05-31 23:53:49.762 10622 10641 I Process : Sending signal. PID: 10622 SIG: 9
05-31 23:53:49.782 1718 14826 I ActivityManager: Process com.android.statementservice (pid 10622) has died: cch+5 CEM
05-31 23:53:49.782 1718 2118 I libprocessgroup: Successfully killed process cgroup uid 10074 pid 10622 in 0ms
05-31 23:53:49.782 966 966 I Zygote : Process 10622 exited due to signal 9 (Killed)
Example2:
Code:
05-31 23:54:24.620 966 966 D Zygote : Forked child process 10707
05-31 23:54:24.620 1718 2114 I ActivityManager: Start proc 10707:com.android.statementservice/u0a74 for service {com.android.statementservice/androidx.work.impl.background.systemjob.SystemJobService}
05-31 23:54:24.625 10707 10707 I libc : SetHeapTaggingLevel: tag level set to 0
05-31 23:54:24.639 1357 1429 I adbd : jdwp connection from 10707
05-31 23:54:24.640 10707 10707 D ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
05-31 23:54:24.633 0 0 I : c3 10707 binder: 10707:10707 ioctl 40046210 7fea0fb8d4 returned -22
05-31 23:54:24.650 1718 14826 D CompatibilityChangeReporter: Compat change id reported: 168419799; UID 10074; state: DISABLED
05-31 23:54:24.654 10707 10707 D CompatibilityChangeReporter: Compat change id reported: 171979766; UID 10074; state: DISABLED
05-31 23:54:24.660 10707 10707 D ApplicationLoaders: Returning zygote-cached class loader: /system/framework/android.test.base.jar
05-31 23:54:24.678 10707 10707 V GraphicsEnvironment: ANGLE Developer option for 'com.android.statementservice' set to: 'default'
05-31 23:54:24.678 10707 10707 V GraphicsEnvironment: ANGLE GameManagerService for com.android.statementservice: false
05-31 23:54:24.679 10707 10707 V GraphicsEnvironment: Neither updatable production driver nor prerelease driver is supported.
05-31 23:54:24.680 10707 10707 D NetworkSecurityConfig: No Network Security Config specified, using platform default
05-31 23:54:24.680 10707 10707 D NetworkSecurityConfig: No Network Security Config specified, using platform default
05-31 23:54:24.699 10707 10724 D CompatibilityChangeReporter: Compat change id reported: 160794467; UID 10074; state: DISABLED
05-31 23:54:24.700 1718 4358 D CompatibilityChangeReporter: Compat change id reported: 171306433; UID 10074; state: DISABLED
05-31 23:54:24.726 1315 1315 I cnss-daemon: nl80211 response handler invoked
05-31 23:54:24.726 1315 1315 I cnss-daemon: nl80211_response_handler: cmd 103, vendorID 4980, subcmd 13 received
05-31 23:54:24.727 1017 2427 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-31 23:54:24.765 10707 10726 E AndroidRuntime: FATAL EXCEPTION: pool-3-thread-2
05-31 23:54:24.765 10707 10726 E AndroidRuntime: Process: com.android.statementservice, PID: 10707
05-31 23:54:24.765 10707 10726 E AndroidRuntime: java.lang.IllegalStateException: Data cannot occupy more than 10240 bytes when serialized
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.Data.toByteArrayInternal(Data.java:417)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.Data$Builder.build(Data.java:846)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.OverwritingInputMerger.merge(OverwritingInputMerger.java:44)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.impl.WorkerWrapper.runWorker(WorkerWrapper.java:227)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.impl.WorkerWrapper.run(WorkerWrapper.java:137)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.impl.utils.SerialExecutor$Task.run(SerialExecutor.java:91)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at java.lang.Thread.run(Thread.java:920)
05-31 23:54:24.768 1718 10731 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
Sorry I don't have a solution for you but since you are using LineageOS+microG on a Pixel phone, you might be interested in switching to CalyxOS as they seem to already have a workaround in place even though the bug isn't fixed yet.
See here under "Issues":
CalyxOS News
📰 Read about what we're working on, important announcements, and upcoming events.
calyxos.org
Relevant commit:
https://review.calyxos.org/c/CalyxOS/vendor_calyx/+/7976
As a bonus, with CalyxOS you also get better security than just LineageOS+microG thanks to bootloader relocking.
I am suffered by that bug too. I can't see any harm by this, but it is annoying. The patch in CalyxOS is just to hide that problem as a workaround.
I filed a bug report here:
Intent filter verification service / com.android.statementservice regularly crashing on LineageOS for microg · Issue #1740 · microg/GmsCore
I am aware this is a very unclear specification of a bug. It is not clear who and what is responsible for this - can be also Android12 (LOS). But it seems to be that the combination of LOS and micr...
github.com
Please report there all your findings @maloo1 and @johnfocker
So I ended up following @johnfocker's suggestion and installed CalyxOS (android 12) and it does "fix" the issue.
I guess Calyx is a perfect fit for my needs anyway (microg, locked boot loader, great polished daily driver) so Ill probably stick with it unless I end up with a phone that is not supported.
It would make sense to have it fixed in microg thou if thats the root cause... I'll see what I can add to the bug...
Thanks again!
Very strange. The messages disappear to pop up after some time.
Lately I installe the new Magisk 25 and BetterBatteryStats (XDA) and it appears again - althoug I am not sure that was really reason. There is continiously changes in phone, so difficult to nail it down.
Quote from flipreverse:
This seems to be a bug in AOSP: https://android.googlesource.com/platform/frameworks/base/+/4978d1ad10293900e9b5feea349abd09ceb6e710
The LOS repo android_frameworks_base does not have this commit at the moment. I'll cherry-pick that one, and give it a try.
Click to expand...
Click to collapse
ale5000 said:
Quote from flipreverse:
Click to expand...
Click to collapse
ist this the bug fix?
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/334683
kurtn said:
ist this the bug fix?
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/334683
Click to expand...
Click to collapse
Yes.
ale5000 said:
Yes.
Click to expand...
Click to collapse
Just too late for the lineage.microg.org August round of builds.