Unpacking ramdisk failed. Aborting...
Updater process ended with ERROR: 1
I just auto-flashed from the app, it works perfectly. I'm on stock OxygenOS 3.1.4, TWRP 3.0.3.0.
Same for me. Don't know why this happened. I hate my life.
I'll try. By the way, in r1 an r2 I was suffering a reboot everytime I received a call.
03-14 15:09:11.557 3049 4879 D WifiService: Client connection lost with reason: 4
03-14 15:09:15.026 3049 13951 E ActivityManager: Error reading /data/anr/traces.txt
03-14 15:09:15.026 3049 13951 E ActivityManager: java.io.FileNotFoundException: /data/anr/traces.txt: open failed: ENOENT (No such file or directory)
03-14 15:09:15.026 3049 13951 E ActivityManager: at libcore.io.IoBridge.open(IoBridge.java:452)
03-14 15:09:15.026 3049 13951 E ActivityManager: at java.io.FileInputStream.<init>(FileInputStream.java:76)
03-14 15:09:15.026 3049 13951 E ActivityManager: at android.os.FileUtils.readTextFile(FileUtils.java:236)
03-14 15:09:15.026 3049 13951 E ActivityManager: at com.android.server.am.ActivityManagerService$21.run(ActivityManagerService.java:13180)
03-14 15:09:15.026 3049 13951 E ActivityManager: Caused by: android.system.ErrnoException: open failed: ENOENT (No such file or directory)
03-14 15:09:15.026 3049 13951 E ActivityManager: at libcore.io.Posix.open(Native Method)
03-14 15:09:15.026 3049 13951 E ActivityManager: at libcore.io.BlockGuardOs.open(BlockGuardOs.java:186)
03-14 15:09:15.026 3049 13951 E ActivityManager: at libcore.io.IoBridge.open(IoBridge.java:438)
03-14 15:09:15.026 3049 13951 E ActivityManager: ... 3 more
03-14 15:09:15.032 12041 12046 E art : Unable to open stack trace file '/data/anr/traces.txt': Permission denied
03-14 15:09:15.045 3049 3370 V BoostFramework: BoostFramework() : mPerf = [email protected]
03-14 15:09:15.045 3049 3370 V BoostFramework: BoostFramework() : mPerf = [email protected]
03-14 15:09:15.046 5971 6009 I art : Wrote stack traces to '/data/anr/traces.txt'
03-14 15:09:15.051 3049 13951 D DropBoxManagerService: file :: /data/system/dropbox/[email protected]_09_15_046.txt.gz
03-14 15:09:15.068 6300 6300 I Binder_3: type=1400 audit(0.0:651): avc: denied { ioctl } for path="socket:[142485]" dev="sockfs" ino=142485 ioctlcmd=7704 scontext=u:r:surfaceflinger:s0 tcontext=u:r:surfaceflinger:s0 tclass=unix_stream_socket permissive=1
03-14 15:09:15.068 6300 6300 I Binder_3: type=1400 audit(0.0:652): avc: denied { ioctl } for path="socket:[142485]" dev="sockfs" ino=142485 ioctlcmd=7704 scontext=u:r:surfaceflinger:s0 tcontext=u:r:surfaceflinger:s0 tclass=unix_stream_socket permissive=1
03-14 15:09:15.079 3049 13949 D DropBoxManagerService: file :: /data/system/dropbox/[email protected]_09_15_073.txt.gz
03-14 15:09:15.079 3049 5777 E Watchdog: Triggering SysRq for system_server watchdog
03-14 15:09:15.079 3049 5777 W Watchdog: *** WATCHDOG KILLING SYSTEM PROCESS: Blocked in handler on foreground thread (android.fg)
03-14 15:09:15.079 3049 5777 W Watchdog: foreground thread stack trace:
03-14 15:09:15.080 3049 5777 W Watchdog: at java.lang.Object.wait(Native Method)
03-14 15:09:15.080 3049 5777 W Watchdog: at com.android.internal.util.AsyncChannel$SyncMessenger.sendMessageSynchronously(AsyncChannel.java:820)
03-14 15:09:15.080 3049 5777 W Watchdog: at com.android.internal.util.AsyncChannel$SyncMessenger.access$100(AsyncChannel.java:740)
03-14 15:09:15.080 3049 5777 W Watchdog: at com.android.internal.util.AsyncChannel.sendMessageSynchronously(AsyncChannel.java:654)
03-14 15:09:15.080 3049 5777 W Watchdog: at com.android.internal.util.AsyncChannel.sendMessageSynchronously(AsyncChannel.java:667)
03-14 15:09:15.080 3049 5777 W Watchdog: at com.android.server.wifi.WifiStateMachine.syncGetLinkLayerStats(WifiStateMachine.java:2423)
03-14 15:09:15.080 3049 5777 W Watchdog: at com.android.server.wifi.WifiServiceImpl.reportActivityInfo(WifiServiceImpl.java:774)
03-14 15:09:15.080 3049 5777 W Watchdog: at com.android.server.am.BatteryStatsService.pullWifiEnergyInfoLocked(BatteryStatsService.java:1221)
03-14 15:09:15.080 3049 5777 W Watchdog: at com.android.server.am.BatteryStatsService.updateExternalStats(BatteryStatsService.java:1346)
03-14 15:09:15.080 3049 5777 W Watchdog: at com.android.server.am.BatteryStatsService$BatteryStatsHandler.handleMessage(BatteryStatsService.java:108)
03-14 15:09:15.080 3049 5777 W Watchdog: at android.os.Handler.dispatchMessage(Handler.java:102)
03-14 15:09:15.080 3049 5777 W Watchdog: at android.os.Looper.loop(Looper.java:148)
03-14 15:09:15.080 3049 5777 W Watchdog: at android.os.HandlerThread.run(HandlerThread.java:61)
03-14 15:09:15.080 3049 5777 W Watchdog: at com.android.server.ServiceThread.run(ServiceThread.java:46)
03-14 15:09:15.080 3049 5777 W Watchdog: *** GOODBYE!
03-14 15:09:15.080 3049 5777 I Process : Sending signal. PID: 3049 SIG: 9
03-14 15:09:15.105 13936 13936 W System : ClassLoader referenced unknown path: /system/priv-app/Mms/lib/arm
03-14 15:09:15.124 13119 13126 E art : Unable to open stack trace file '/data/anr/traces.txt': Permission denied
03-14 15:09:16.018 500 500 I Gobi : vendor/qcom/proprietary/RIDL/RIDLClient/RIDLSQL.cpp:2500: GetTransState() EBADF
03-14 15:09:16.018 500 500 I Gobi : vendor/qcom/proprietary/RIDL/RIDLClient/MainCore.cpp:1550: Failed to get TransState, rc 9
03-14 15:09:16.018 500 500 I Gobi : vendor/qcom/proprietary/RIDL/RIDLClient/RIDLSQL.cpp:2500: GetTransState() EBADF
03-14 15:09:16.018 500 500 I Gobi : vendor/qcom/proprietary/RIDL/RIDLClient/RIDLSQL.cpp:2500: GetTransState() EBADF
You don't happen to be using CFQ do you?
Part of the cause was with the display driver. When I fixed that, I didn't have one. I switched over to CFQ and low and behold, they were back. Updated the kernel above with a few changes and switched to Zen. After nearly a day I have yet to have one. They are fixed for me with the build I posted. CFQ seems to expose an MMC bug that Sultan's pointed out to me in the past. I haven't had one for nearly two days now without CFQ and with the display changes that were merged.
You had an issue somewhere else, I don't touch WiFi, but if you had other Kernel/custom roms installed and they ship/replace the stock WiFi module then there's nothing I can do because I don't touch anything related to WiFi.
Come on franco i never expected such reply from you,
This sux. Keep you're head up mate! Many of us waiting for you're kernel for CM13 and LOS
Fingers crossed 
I'm not merging PRs blindly. Leaving all cores online is fine, they'll hit retention and power collapse pretty quickly if nothing is running on them. There's a lot of work when offlining and onlining cores. I do the same on the Nexus 5, all cores online all the time.Come on franco i never expected such reply from you,Maybe i can help in fixing some stuff(you wont need it) .
Most importantly-
I like your idea of keeping all 4 cores active, most people might not be aware of the reason. But keeping 4 cores active might not help much since its a 3.4
- Onyx isnt like other devices
- Never merge PRs blindly
Haha i was just lurking original dev section for a while and saw what's going on. I'm aware of the cores thing, intel uses same methodology, many users might freak out without knowing anything about it lolI'm not merging PRs blindly. Leaving all cores online is fine, they'll hit retention and power collapse pretty quickly if nothing is running on them. There's a lot of work when offlining and onlining cores. I do the same on the Nexus 5, all cores online all the time.
It's just a shame ****ing OP builds the WiFi drivers as a module and they compile it with the rom (static linking it to the Kernel sources). The current wlan.ko has outdated drivers & it has a lot of issues. If I build the module myself things are way harder to manage so it's not something I want to do. Other than that current sources are pretty much the same patches I use for the N5 (SD801 is just an updated revision of the SD800) and it's flawless. r4 will have more fixes though.
Did I set my standard so high my reply shocked you?
