Hello,
My Axon 7s (the dual cam one) (https://www.gsmarena.com/zte_axon_7s-8658.php) has an overheating issue. The battery melts dows super fast and the phone heats up alot even in standby with no sim card and wi-fi enabled. Factory reset did not helped at all. It is Android 7.1.1, ZTE2018V1.1.0B11. Is there any way to install custom firmware or update the stock one, ore anything else that will help prevent this issue?
Thanks!
no its not possible
It sounds like a bad battery more than a software issue. The Axon 7s does have some comments online saying it overheats frequently however.
If you're comfortable in doing so and your warranty has expired; I would try replacing the battery and maybe even the thermal paste inside.
After resetting the phone, the problem disappeared. It was cool for 2-3 hours. Then I logged in my google account, installed Viber and it started heating and draining the battery again. The Phone is 4 months old. Never played games on it. Only Facebook and Viber. I had another Axon 7 (without "s") before with the same problem. Changed the battery 2 times and nothing happened. Still discharges super fast...
Markovo said:
After resetting the phone, the problem disappeared. It was cool for 2-3 hours. Then I logged in my google account, installed Viber and it started heating and draining the battery again. The Phone is 4 months old. Never played games on it. Only Facebook and Viber. I had another Axon 7 (without "s") before with the same problem. Changed the battery 2 times and nothing happened. Still discharges super fast...
Click to expand...
Click to collapse
Had the same problem - in my case MediaServer locked up upon a corrupt MP4 file and utilitzed 1 core at 100% constantly. That caused my phone to overheat. Battery life was terrible.
Try to hook your phone up to your computer and open "ADB shell" and type "top -m 10" - you will see the top 10 processes that cause CPU utilization. If there is a process that hogs your CPU you know where to look closer. I found out that a corrupt MP4 video file was the culprit. After deleting it and a reboot my phone was fixed and felt lie new. Hope that helps...
I used ADB Shell too show the processes.
Here is the result:
Code:
Load: 3.33 / 3.59 / 3.64
CPU usage from 51297ms to 39789ms ago (2020-05-13 12:06:18.533 to 2020-05-13 12:06:30.042):
0.9% 2504/kworker/u8:10: 0% user + 0.9% kernel
0.6% 2599/system_server: 0.2% user + 0.4% kernel / faults: 58 minor
0.5% 53/ksmd: 0% user + 0.5% kernel
0.5% 7125/kworker/u8:11: 0% user + 0.5% kernel
0.5% 8893/kworker/u8:0: 0% user + 0.5% kernel
0.4% 16/ksoftirqd/2: 0% user + 0.4% kernel
0.2% 2426/gx_fpd: 0% user + 0.2% kernel
0.2% 3238/com.android.systemui: 0.2% user + 0% kernel / faults: 7 minor
0.1% 42/smem_native_rpm: 0% user + 0.1% kernel
0.1% 2963/thermal-engine: 0.1% user + 0% kernel
0.1% 6642/com.google.android.webview:s: 0.1% user + 0% kernel
0.1% 7323/kworker/0:2: 0% user + 0.1% kernel
0.1% 7703/kworker/2:5: 0% user + 0.1% kernel
0% 20/ksoftirqd/3: 0% user + 0% kernel
0% 34/kworker/0:1: 0% user + 0% kernel
0% 348/cfinteractive: 0% user + 0% kernel
0% 464/servicemanager: 0% user + 0% kernel / faults: 1 minor
0% 614/[email protected]: 0% user + 0% kernel
0% 635/healthd: 0% user + 0% kernel
0% 3390/com.android.phone: 0% user + 0% kernel / faults: 4 minor
0% 7695/kworker/3:4: 0% user + 0% kernel
0% 8940/kworker/2:1: 0% user + 0% kernel
1.3% TOTAL: 0.1% user + 0.8% kernel + 0% iowait + 0.3% irq + 0.1% softirq
Code:
[H[JTasks: 580 total, 1 running, 573 sleeping, 0 stopped, 2 zombie
Mem: 3860956k total, 3633324k used, 227632k free, 117192k buffers
Swap: 1048572k total, 0k used, 1048572k free, 1886212k cached
400%cpu 2%user 1%nice 7%sys 390%idle 0%iow 0%irq 0%sirq 0%host
[7m PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS [0m
2551 system 18 -2 2.5G 284M 186M S 5.0 7.5 0:26.34 system_server
6370 shell 20 0 11M 3.0M 1.7M R 4.0 0.0 0:01.31 top -n 10
6068 root 20 0 0 0 0 S 0.6 0.0 0:00.21 [kworker/u8:12]
464 logd 30 10 24M 4.6M 1.4M S 0.6 0.1 0:03.44 logd
347 root RT 0 0 0 0 S 0.6 0.0 0:01.27 [cfinteractive]
895 root 20 0 0 0 0 S 0.3 0.0 0:01.05 [kworker/u8:10]
622 system RT 0 86M 3.3M 2.3M S 0.3 0.0 0:01.36 android.hardwar+
287 root 20 0 0 0 0 S 0.3 0.0 0:00.26 [kworker/u8:9]
54 root 25 5 0 0 0 S 0.3 0.0 0:00.40 [ksmd]
47 root RT 0 0 0 0 S 0.3 0.0 0:00.55 [irq/263-cpr3]
6354 shell 20 0 13M 1.0M 776K S 0.0 0.0 0:00.04 adbd --root_sec+
6194 system 20 0 2.1G 39M 19M S 0.0 1.0 0:00.06 com.zte.emode
6132 u0_a30 20 0 2.1G 59M 34M S 0.0 1.5 0:01.79 com.android.mms
6128 root RT 0 0 0 0 D 0.0 0.0 0:00.54 [mdss_fb0]
6120 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/3:5]
6104 system 20 0 2.1G 43M 23M S 0.0 1.1 0:00.11 zte.com.cn.alar+
6087 u0_a115 20 0 2.1G 38M 18M S 0.0 1.0 0:00.10 com.qualcomm.ti+
6077 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/u8:16]
6076 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/u8:15]
[?25h[0m[1000;1H[K[?25h[0m[1000;1H[K0.0 0.0 0:00.00 [kworker/u8:14]
Code:
[H[JTasks: 577 total, 1 running, 570 sleeping, 0 stopped, 2 zombie
Mem: 3860956k total, 3630552k used, 230404k free, 117216k buffers
Swap: 1048572k total, 0k used, 1048572k free, 1886212k cached
400%cpu 1%user 0%nice 4%sys 395%idle 0%iow 0%irq 0%sirq 0%host
[7m PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS [0m
6385 shell 20 0 11M 3.0M 1.7M R 4.3 0.0 0:00.63 top -n 10
6354 shell 20 0 13M 0.9M 788K S 0.3 0.0 0:00.06 adbd --root_sec+
6068 root 20 0 0 0 0 S 0.3 0.0 0:00.60 [kworker/u8:12]
622 system RT 0 86M 3.2M 2.3M S 0.3 0.0 0:01.72 android.hardwar+
347 root RT 0 0 0 0 S 0.3 0.0 0:01.38 [cfinteractive]
54 root 25 5 0 0 0 S 0.3 0.0 0:00.67 [ksmd]
12 root 20 0 0 0 0 S 0.3 0.0 0:00.66 [ksoftirqd/1]
7 root 20 0 0 0 0 S 0.3 0.0 0:01.33 [rcu_preempt]
6194 system 20 0 2.1G 39M 19M S 0.0 1.0 0:00.06 com.zte.emode
6132 u0_a30 20 0 2.1G 59M 34M S 0.0 1.5 0:01.81 com.android.mms
6128 root RT 0 0 0 0 D 0.0 0.0 0:00.65 [mdss_fb0]
6120 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/3:5]
6104 system 20 0 2.1G 43M 23M S 0.0 1.1 0:00.11 zte.com.cn.alar+
6087 u0_a115 20 0 2.1G 38M 18M S 0.0 1.0 0:00.10 com.qualcomm.ti+
6077 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/u8:16]
6076 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/u8:15]
6075 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/u8:14]
6069 root 20 0 0 0 0 S 0.0 0.0 0:00.16 [kworker/u8:13]
6066 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/u8:11]
6045 root 20 0 0 0 0 S 0.0 0.0 0:00.02 [kworker/1:5]
It seems alright to me...
Related
Hi all,
There's a weired issue regarding bluetooth connections (Freeze, Reboots).
Now i located the process which makes the device so slow:
with 'top -n 1' comes the following result (adb shell):
Code:
User 95%, System 1%, IOW 0%, IRQ 0%
User 289 + Nice 2 + Sys 4 + Idle 9 + IOW 0 + IRQ 0 + SIRQ 0 = 304
PID CPU% S #THR VSS RSS PCY UID Name
4964 125% S 10 20332K 2152K fg bluetoot /system/bin/btld
5100 1% R 1 836K 404K fg root top
3070 0% S 9 215000K 23768K bg app_3 com.android.bluetooth
2599 0% S 8 231232K 37832K fg app_50 com.android.wallpaper
2495 0% S 58 327856K 67728K fg system system_server
6 0% S 1 0K 0K fg root khelper
10 0% S 1 0K 0K fg root async/mgr
13 0% S 1 0K 0K fg root suspend
14 0% S 1 0K 0K fg root sync_system_wor
256 0% S 1 0K 0K fg root sync_supers
258 0% S 1 0K 0K fg root bdi-default
260 0% S 1 0K 0K fg root kblockd/0
269 0% S 1 0K 0K fg root kseriod
280 0% S 1 0K 0K fg root kmmcd
287 0% S 1 0K 0K fg root bluetooth
303 0% S 1 0K 0K fg root kconservative/0
313 0% S 1 0K 0K fg root kadctsd
330 0% S 1 0K 0K fg root khungtaskd
331 0% S 1 0K 0K fg root kswapd0
379 0% S 1 0K 0K fg root aio/0
if i kill the process '4964 ' (kill -9 4964)
the system works fine again (just bluetooth doesn't until you restart it)
How to make your SGT freeze:
I've tried it with several Bluetooth devices and the BT_Serial_Tester:
Just bond your device, run BT_Serial_Tester -> Paired Devices and selcet your device. If BT Connected shows "true" then after exiting the software the sgt will freeze.
Our test devices:
RoyalTek RBT-1000
BlueSerial RS232 Adapter
firmtech btwin RS232 Adapter
So here's the mighty question: Is it possible to restart the /system/bin/btld process in a secure way?
Or are there other ROMs which have fixed the issue?
thanks in advance
Tom
From my experience, all Galaxy based devices have sometimes troubles when loading firmware in hciattach. There are some patches floating that try to rest bluetooth before loading firwmare, but none of that seems to fix anything for my CyanogenMod7 builds. I modified the code that starts bluetooth to stop hciattach service (which calls brcm_patchram_plus) after a timeout so BT can be restarted manually.
See https://github.com/cmsgs/android_device_samsung_galaxytab/blob/master/patches/bluetooth.c.patch
Thanks for your reply.
So am i right that:
- there's a bluetooth issue regarding several devices (for me is the SPP important)
- no fix availble
- the only 'workaround' is to kill the btld process and manually restart bluetooth.
Ok that's really bad news i think. On my HTC desire HD there's no such problem (nevertheless there are some Errors regarding Bluetooth in the LogCat)
thanks
Tom
t3e said:
Thanks for your reply.
So am i right that:
- there's a bluetooth issue regarding several devices (for me is the SPP important)
- no fix availble
- the only 'workaround' is to kill the btld process and manually restart bluetooth.
Ok that's really bad news i think. On my HTC desire HD there's no such problem (nevertheless there are some Errors regarding Bluetooth in the LogCat)
thanks
Tom
Click to expand...
Click to collapse
If you are using official Samsung ROM you should complain to them about it.
As for Inspire 4G (same thing as Desire HD), it's cool but the battery life sucks, especially compared to the Tab ;-) I am running Revolution 3.2 ROM on my Inspire and the gps is broken -;(
I have the same bug with the original ROM from Bell
I am able to reproduce the bug most of the time with Sports tracker after about 10-20min with my Zephyr HxM
with CM7 there's no problem
I think i got a solution for us
We've designed our software to exit it when the user hit "Exit".
(System.exit(0) surely not recommended) So and thats why the SGT starts to freeze.
now we don't kill our process and the SGT don't freeze.
But the annoying part is, when you're debugging..
Each time you want to debug your software, the running app is killed on the SGT and the issue is back on...
I've gone from Typhoon CyanogenMod to HyperDroidGBX-v12 and it seems that Hyperdroid keeps connecting to wifi in intervals and waking up the phone which has taken a lot more battery over night than CyanogenMod did. I love the speed of Hyperdroid so I was wondering if there is anything I can do?
When I switched the phone on using Cyanogen I saw him switch off the mobile data connection and switch on wifi. Hyperdroid doesn't seem to manage it like that. Can I customize this?
edit: I found the option under wireless to switch if off when the phone is asleep but I don't think he's doing as he's told (my phone is male, in case you're wondering)...
I've attached a screen of my phone over night with HyperDroid. It kept waking up without the screen being on. I assume that's the root of all evil...
The only app that syncs on my phone atm is the GMail app, no facebook or others.
Any suggestions?
Thanks
edit:
I've searched some more and there were people who's wireless went to sleep when they didn't want it to, the opposite of my problem. I've done a clean install of HyperDroid again and the problem persists, at least the wireless not switching off. Since that worked with CyanogenMod I assume that's the root cause. I'm surprised this hasn't picked up on before, assuming other people have the same problem.
I guess I'd like to know if there are any simple file swaps I can perform like changing drivers between the two mods?
editv2:
Wireless seems to at least switch off now. I tried killing inactive apps. I'll see what happens from here.
Usually it's apps polling for updates.
This includes Facebook, Twitter etc. Are you using Google Latitude? That can wake the device every few minutes.
To check for wakelocks
Code:
cat /proc/wakelocks
It happened again last night that the phone appears awake for quite some time. I've got the wakelocks (which I don't know how to interpret). I'll post them and a screenshot of battery. I'm hoping to either hear a solution or that it's normal.
It seems like he had a much more quiet night tonight. I wish I had paid more attention to it while using Cyanogen. I've installed the battery current widget so that should be interesting as well.
Cheers.
Code:
name count expire_count wake_count active_since total_time sleep_time max_time last_cha
nge
"alarm" 957 0 0 0 23959014779 21546905463 384429936 9723528995498
"wlan_wake" 19027 0 49 0 86119018687 44324798717 1083984373 9683300205212
"main" 17 0 0 0 7736565871862 0 5511280593319 9680620426163
"event4-252" 34973 0 0 0 3475555677 0 6408692 9680155307754
"msmfb_idle_lock" 54032 0 0 0 4743530364 0 278686529 9680154453261
"ds2746-battery" 667 0 0 0 9070099039 8503753803 39886474 9679912631970
"alarm_rtc" 562 8 0 0 63026972383 63025843229 1034118654 8779276859239
"KeyEvents" 35993 0 0 0 4014678958 84869382 86914061 9679667270643
"event3-252" 216 0 0 0 124999996 73455813 16967773 9679666141493
"gpio_input" 52 0 9 0 528106698 122161869 10437012 9679665958387
"event5-252" 284 0 0 0 16235353 0 762939 9675881534557
"usb_mass_storage" 1 0 0 0 229509429930 0 229509429930 9228090579970
"power-supply" 135 0 0 0 70007320 41687016 2685547 9673667392715
"power-supply" 7 0 0 0 6774905 3875733 2532958 9673667209609
"power-supply" 7 0 0 0 10894774 2655028 5859375 9673667087539
"wlan_rx_wake" 1078 1078 0 0 1729369137961 185800921021 21577879641 9670940219862
"qmi" 17 17 0 0 8471907985 1995538327 509357909 9670940189344
"SMD_DATA5" 563 563 120 0 491717996183 412869000741 9329598383 9670940189344
"event0-252" 35776 0 0 0 2916259736 0 3112793 9603342624641
"gpio_kp" 83 0 2 0 14742034892 22491454 1275268561 9585008335097
"AudioHardwareQSDOut" 16 0 0 0 94738861105 704864502 20176086427 8977790592174
"audio_pcm_suspend" 14 0 0 0 211352722187 422058099 35328094487 8977790500621
"audio_pcm_idle" 14 0 0 0 211352630634 0 35328094487 8977790500621
"SMD_RPCCALL" 7382 0 555 0 636077998 468994259 26184081 8977783267956
"rpc_read" 214 0 0 0 6530761 457767 1831054 8977783237438
"ApmCommandThread" 56 0 0 0 1433898924 0 895629880 8825111423477
"radio-interface" 38 0 0 0 41765899679 4004455570 1961944580 8786906162243
"rpc_read" 4429 0 0 0 192779566 184631377 244141 8779275638536
"rpc-interface" 537 0 0 0 889831583 863678015 41290284 8239455598513
"rpc_read" 535 0 0 0 1028228754 170288083 348480225 8239453920046
"AudioHardwareQSDIn" 9 0 0 0 147654846199 0 32158020026 7760196196386
"proximity" 1 1 0 0 3892520753 0 3892520753 5763470148164
"event1-252" 8 0 0 0 274658 0 91552 5734318414763
"mmc_delayed_work" 3 2 0 0 13576922628 0 8541424561 5511892785725
"msm_camera" 2 0 0 0 12680633542 0 10539916988 5504792504962
"msm_camera_wake" 2 0 0 0 12680633542 0 10539916988 5504792504962
"s5k3e2fx" 2 0 0 0 12293823244 0 10387512209 5504791894611
"flashlight" 1 0 0 0 116271973 0 116271973 5472884484944
"rpc_read" 2 0 0 0 70556639 0 41900634 56937371906
"event2-252" 0 0 0 0 0 0 0 0
"SMD_DATA7" 0 0 0 0 0 0 0 0
"SMD_DATA6" 0 0 0 0 0 0 0 0
"port_list" 0 0 0 0 0 0 0 0
"vbus_present" 0 0 0 0 0 0 0 0
"msm_serial_hs_dma" 0 0 0 0 0 0 0 0
"msm_serial_hs_rx" 0 0 0 0 0 0 0 0
"audiojack" 0 0 0 0 0 0 0 0
"headset" 0 0 0 0 0 0 0 0
"microp_i2c_present" 0 0 0 0 0 0 0 0
"rpc_server" 0 0 0 0 0 0 0 0
"rpc_read" 0 0 0 0 0 0 0 0
"vdec_suspend" 0 0 0 0 0 0 0 0
"vdec_idle" 0 0 0 0 0 0 0 0
"i2c" 0 0 0 0 0 0 0 0
"unknown_wakeups" 0 0 0 0 0 0 0 0
"deleted_wake_locks" 193 0 0 0 117065426 0 32287599 0
"kgsl" 2981 0 0 1068695066 4845796179890 688535376655 128397308351 9725263797740
"PowerManagerService" 1061 0 0 52465057371 7525105867782 1338152315208 5239685516362 96738674
65953
"vbus_present" 2 1 0 740221282954 5984945089112 108139678944 5244723806158 8986111270887
"SMD_DS" 176 176 0 0 103807277355 31379227646 1803994144 9680271884899
#
Hey guys! Before you read no, this is not a scream of help, yes im soft bricked but im not a noob. I just need advice as I dont know build.prop config.
So I installed wallet and got that working using the tool here http://forum.xda-developers.com/showthread.php?t=2278276
Got her working just fine and its all swell. Used it a bunch.
Then something weird happened, I was in a LTE area for my first time and I wanted to test it out. But for some reason I couldnt connect to the internet in any way... odd because status in android was saying LTE:14 connected. Mobile state: connected, and data was NOT off....
So I thought it must have been the build.prop change. So I was realllly stupid....
I installed this app, http://forum.xda-developers.com/showthread.php?t=2044362 for when I showed my dad thats what he needed for his GS3.
I forgot I didnt use that app.... so I restored the build.prop in the app, but since it was never used I think it just deleted her. ..
Anyway, im in ADB. I have a flashing blue LED and I can get to system fine. I grabbed a build.prop from here http://forum.xda-developers.com/showthread.php?t=2245079
And pushed it to /system as build.prop (not build.prop.txt, i tried that, no worky.)
She still doesnt boot.... thoughts?
I dont want to odin because of all the work I have done. And yet, it seems so simple to fix because android boots. Just after the S4 splash is no boot anim.... but I can adb shell.........
Thanks guys!
odin doesnt wipe /data anymore, so its not that much of a setback, more of an update.
Haas360 said:
Hey guys! Before you read no, this is not a scream of help, yes im soft bricked but im not a noob. I just need advice as I dont know build.prop config.
So I installed wallet and got that working using the tool here http://forum.xda-developers.com/showthread.php?t=2278276
Got her working just fine and its all swell. Used it a bunch.
Then something weird happened, I was in a LTE area for my first time and I wanted to test it out. But for some reason I couldnt connect to the internet in any way... odd because status in android was saying LTE:14 connected. Mobile state: connected, and data was NOT off....
So I thought it must have been the build.prop change. So I was realllly stupid....
I installed this app, http://forum.xda-developers.com/showthread.php?t=2044362 for when I showed my dad thats what he needed for his GS3.
I forgot I didnt use that app.... so I restored the build.prop in the app, but since it was never used I think it just deleted her. ..
Anyway, im in ADB. I have a flashing blue LED and I can get to system fine. I grabbed a build.prop from here http://forum.xda-developers.com/showthread.php?t=2245079
And pushed it to /system as build.prop (not build.prop.txt, i tried that, no worky.)
She still doesnt boot.... thoughts?
I dont want to odin because of all the work I have done. And yet, it seems so simple to fix because android boots. Just after the S4 splash is no boot anim.... but I can adb shell.........
Thanks guys!
Click to expand...
Click to collapse
Here is a TOP of what my phone is running right now. She is HOT. What is that IRQ?
[email protected]:/ # top
top
User 2%, System 57%, IOW 0%, IRQ 0%
User 30 + Nice 0 + Sys 692 + Idle 490 + IOW 0 + IRQ 1 + SIRQ 0 = 1213
PID PR CPU% S #THR VSS RSS PCY UID Name
46 2 18% S 1 0K 0K root irq/243-msm_iom
42 1 17% D 1 0K 0K root irq/102-msm_iom
47 3 10% D 1 0K 0K root irq/243-msm_iom
43 0 9% R 1 0K 0K root irq/102-msm_iom
13703 0 1% S 1 1224K 676K shell gzip
188 2 0% S 4 17616K 5364K root /system/bin/vold
13714 3 0% R 1 1392K 552K root top
13702 2 0% S 1 1164K 652K shell dumpstate
12 2 0% S 1 0K 0K root ksoftirqd/2
13 3 0% S 1 0K 0K root migration/3
15 3 0% S 1 0K 0K root ksoftirqd/3
16 1 0% S 1 0K 0K root khelper
17 1 0% S 1 0K 0K root suspend_sys_syn
18 1 0% S 1 0K 0K root suspend
20 1 0% S 1 0K 0K root irq/203-msmdata
21 0 0% S 1 0K 0K root sync_supers
22 0 0% S 1 0K 0K root bdi-default
23 1 0% S 1 0K 0K root kblockd
24 0 0% S 1 0K 0K root msm_slim_ctrl_r
25 0 0% S 1 0K 0K root khubd
26 1 0% S 1 0K 0K root irq/343-max7769
27 1 0% S 1 0K 0K root irq/84-msm_iomm
28 1 0% S 1 0K 0K root irq/84-msm_iomm
29 1 0% S 1 0K 0K root irq/96-msm_iomm
30 1 0% S 1 0K 0K root irq/96-msm_iomm
31 1 0% S 1 0K 0K root irq/94-msm_iomm
32 1 0% S 1 0K 0K root irq/94-msm_iomm
33 1 0% S 1 0K 0K root irq/92-msm_iomm
34 1 0% S 1 0K 0K root irq/92-msm_iomm
35 1 0% S 1 0K 0K root irq/100-msm_iom
36 1 0% S 1 0K 0K root irq/100-msm_iom
37 1 0% S 1 0K 0K root irq/86-msm_iomm
38 1 0% S 1 0K 0K root irq/86-msm_iomm
39 1 0% S 1 0K 0K root irq/90-msm_iomm
40 1 0% S 1 0K 0K root irq/90-msm_iomm
41 1 0% S 1 0K 0K root irq/88-msm_iomm
44 1 0% S 1 0K 0K root irq/98-msm_iomm
45 1 0% S 1 0K 0K root irq/98-msm_iomm
48 1 0% S 1 0K 0K root irq/269-msm_iom
49 1 0% S 1 0K 0K root irq/269-msm_iom
50 1 0% S 1 0K 0K root l2cap
51 1 0% S 1 0K 0K root a2mp
52 1 0% S 1 0K 0K root cfg80211
53 1 0% S 1 0K 0K root rpciod
54 1 0% S 1 0K 0K root modem_notifier
55 1 0% S 1 0K 0K root smd_channel_clo
56 1 0% S 1 0K 0K root smsm_cb_wq
58 1 0% S 1 0K 0K root qmi
59 1 0% S 1 0K 0K root nmea
60 1 0% S 1 0K 0K root msm_ipc_router
61 1 0% S 1 0K 0K root apr_driver
62 1 0% S 1 0K 0K root mdm_queue
63 1 0% S 1 0K 0K root irq/337-mdm sta
64 1 0% S 1 0K 0K root irq/319-mdm pbl
65 0 0% S 1 0K 0K root kswapd0
66 3 0% S 1 0K 0K root fsnotify_mark
67 1 0% S 1 0K 0K root ecryptfs-kthrea
68 1 0% S 1 0K 0K root nfsiod
69 1 0% S 1 0K 0K root cifsiod
70 1 0% S 1 0K 0K root crypto
84 1 0% S 1 0K 0K root mdp_dma_wq
85 1 0% S 1 0K 0K root mdp_vsync_wq
86 1 0% S 1 0K 0K root mdp_pipe_ctrl_w
87 1 0% S 1 0K 0K root mdp_cursor_ctrl
88 1 0% S 1 0K 0K root hdmi_hdcp
89 1 0% S 1 0K 0K root irq/111-hdmi_ms
90 1 0% S 1 0K 0K root dtv_work
91 1 0% S 1 0K 0K root vidc_worker_que
92 1 0% S 1 0K 0K root vidc_timer_wq
93 1 0% S 1 0K 0K root sii8240-cmdwq
94 1 0% S 1 0K 0K root sii8240-aviwq
95 1 0% S 1 0K 0K root irq/365-sii8240
96 1 0% S 1 0K 0K root smux_notify_wq
97 1 0% S 1 0K 0K root smux_tx_wq
98 1 0% S 1 0K 0K root smux_rx_wq
99 1 0% S 1 0K 0K root smux_loopback_w
100 1 0% S 1 0K 0K root k_hsuart
101 1 0% S 1 0K 0K root diag_wq
102 1 0% S 1 0K 0K root diag_cntl_wq
103 1 0% S 1 0K 0K root diag_dci_wq
104 1 0% S 1 0K 0K root diag_bridge_wq
105 1 0% S 1 0K 0K root kgsl-3d0
106 2 0% S 1 0K 0K root kworker/u:2
107 1 0% S 1 0K 0K root irq/330-wcd9xxx
108 1 0% S 1 0K 0K root kworker/1:1
109 1 0% S 1 0K 0K root spi_qsd.0
116 1 0% S 1 0K 0K root usbnet
117 1 0% S 1 0K 0K root hsicctl0
118 1 0% S 1 0K 0K root hsicctl1
119 1 0% S 1 0K 0K root hsicctl2
120 1 0% S 1 0K 0K root hsicctl3
123 1 0% S 1 0K 0K root mdm_bridge
124 1 0% S 1 0K 0K root ks_bridge:1
125 1 0% S 1 0K 0K root ks_bridge:2
126 1 0% S 1 0K 0K root k_rmnet_mux_wor
127 1 0% S 1 0K 0K root mtp_read_send
1 2 0% S 1 952K 828K root /init
129 1 0% S 1 0K 0K root uether
131 1 0% S 1 0K 0K root kpsmoused
132 1 0% S 1 0K 0K root f54_status_work
133 1 0% S 1 0K 0K root irq/36-synaptic
134 1 0% S 1 0K 0K root iewq
135 1 0% D 1 0K 0K root kinteractiveup
136 1 0% S 1 0K 0K root irq/664-msm-sdc
137 1 0% S 1 0K 0K root binder
138 1 0% S 1 0K 0K root kcompcached
139 1 0% S 1 0K 0K root irq/573-fuelgau
140 1 0% S 1 0K 0K root max77693-charge
141 0 0% S 1 0K 0K root mmcqd/0
142 1 0% S 1 0K 0K root ssp_debug_wq
143 1 0% S 1 0K 0K root irq/651-SSP_Int
144 1 0% S 1 0K 0K root ssp_sensorhub_t
145 1 0% S 1 0K 0K root ES325
147 1 0% S 1 0K 0K root rq_stats
148 1 0% S 1 0K 0K root deferwq
149 1 0% S 1 0K 0K root sec_jack_wq
150 1 0% S 1 0K 0K root irq/638-flip_co
151 1 0% S 1 0K 0K root irq/662-cypress
152 1 0% S 1 0K 0K root cypress_touchke
153 0 0% S 1 0K 0K root cypress_touchke
154 1 0% S 1 0K 0K root mmcqd/2
155 1 0% S 1 0K 0K root sec-battery
156 1 0% S 1 0K 0K root barcode_firmwar
157 3 0% S 1 0K 0K root kworker/3:1
158 2 0% S 1 0K 0K root kworker/2:1
159 2 0% S 1 596K 396K root /sbin/ueventd
160 3 0% S 1 0K 0K root kworker/u:3
161 2 0% S 1 0K 0K root jbd2/mmcblk0p26
162 1 0% S 1 0K 0K root ext4-dio-unwrit
164 1 0% S 1 0K 0K root jbd2/mmcblk0p16
165 1 0% S 1 0K 0K root ext4-dio-unwrit
167 0 0% S 1 0K 0K root jbd2/mmcblk0p29
168 1 0% S 1 0K 0K root ext4-dio-unwrit
169 2 0% S 1 0K 0K root flush-179:0
171 1 0% S 1 0K 0K root jbd2/mmcblk0p18
172 1 0% S 1 0K 0K root ext4-dio-unwrit
174 0 0% S 1 0K 0K root jbd2/mmcblk0p10
175 1 0% S 1 0K 0K root ext4-dio-unwrit
187 2 0% S 1 1000K 180K system /system/bin/servicemanager
193 0 0% S 1 17840K 344K system /system/bin/qseecomd
195 2 0% S 1 916K 324K system /system/bin/sh
204 2 0% S 1 1516K 668K root /system/bin/rild
206 2 0% S 5 5148K 196K system /system/bin/ddexe
207 2 0% S 3 3960K 648K system /system/bin/kiesexe
208 2 0% S 1 1512K 664K system /system/bin/smdexe
209 0 0% S 1 1868K 652K system /system/bin/dttexe
213 2 0% S 1 1860K 432K system /system/bin/connfwexe
214 3 0% S 2 8408K 2820K radio /system/bin/sec-ril
215 0 0% S 2 4896K 1324K radio /system/bin/at_distributor
219 0 0% S 1 17588K 240K radio /system/bin/diag_uart_log
220 2 0% S 1 2176K 644K system /system/bin/npsmobex
223 0 0% S 2 20580K 6828K fg drm /system/bin/drmserver
227 0 0% S 1 1944K 684K keystore /system/bin/keystore
232 1 0% S 2 6680K 1860K fg system /system/bin/bintvoutservice
237 2 0% S 1 2956K 712K camera /system/bin/mm-qcamera-daemo
245 3 0% S 1 924K 128K shell /system/bin/immvibed
249 0 0% S 3 24716K 2512K system /system/bin/cnd
252 2 0% S 2 2368K 560K system /system/bin/mm-pp-daemon
260 0 0% S 3 20084K 664K system /system/bin/time_daemon
264 0 0% S 2 2328K 564K nobody /system/bin/rmt_storage
265 2 0% S 21 38672K 904K root /system/bin/thermal-engine
266 2 0% S 1 1260K 484K system /system/bin/qcks
269 0 0% S 5 4512K 204K shell /sbin/adbd
274 0 0% S 3 19940K 476K system /system/bin/qseecomd
285 2 0% S 4 21956K 808K radio /system/bin/qmuxd
296 1 0% S 1 0K 0K root k_gserial
307 0 0% S 1 8016K 4560K system /system/bin/secure_storage_d
emon
418 2 0% S 1 0K 0K root kworker/2:2
582 2 0% S 3 41764K 7204K media /system/bin/samsungpowersoun
play
678 1 0% S 1 0K 0K root mobicore_log
718 3 0% S 5 5328K 516K system /system/bin/mcDriverDaemon
760 0 0% S 1 1172K 472K system /system/bin/efsks
765 1 0% S 1 0K 0K root ehci_wq
766 0 0% S 1 0K 0K root irq/337-hsic_pe
770 0 0% S 1 0K 0K root dun_ctrl_hsic0
771 0 0% S 1 0K 0K root rmnet_ctrl_hsic
777 2 0% S 1 840K 320K system sh
778 0 0% S 1 2996K 2320K system /system/bin/ks
1166 0 0% S 1 988K 192K system /system/bin/secstarter
1968 1 0% S 1 0K 0K root kworker/1:2
2163 1 0% S 9 59420K 8076K fg system /system/bin/surfaceflinger
2175 1 0% S 4 65892K 58932K fg graphics /system/bin/bootanimation
2543 3 0% S 1 0K 0K root kworker/3:2
5199 0 0% S 1 0K 0K root kworker/0:1
8624 1 0% S 1 0K 0K root kworker/u:0
11920 1 0% S 1 1068K 488K install /system/bin/installd
13207 2 0% S 8 9676K 904K root /system/bin/netd
13208 2 0% S 2 3680K 908K fg system /system/bin/sensorhubservice
13209 2 0% S 4 153748K 57604K root zygote
13218 0 0% S 1 0K 0K root kworker/u:1
13436 0 0% S 32 202376K 54296K fg system system_server
13546 3 0% S 1 9408K 5040K root /system/bin/debuggerd
13664 0 0% S 1 924K 484K shell /system/bin/sh
13669 3 0% S 1 924K 488K root sh
13697 3 0% t 3 59968K 10440K media /system/bin/mediaserver
13701 1 0% S 1 912K 324K root sh
13737 1 0% Z 1 0K 0K root su
128 1 0% S 1 0K 0K root file-storage
2 1 0% S 1 0K 0K root kthreadd
3 0 0% S 1 0K 0K root ksoftirqd/0
4 0 0% S 1 0K 0K root kworker/0:0
6 0 0% S 1 0K 0K root migration/0
7 1 0% S 1 0K 0K root migration/1
9 1 0% S 1 0K 0K root ksoftirqd/1
10 2 0% S 1 0K 0K root migration/2
Dallenn said:
odin doesnt wipe /data anymore, so its not that much of a setback, more of an update.
Click to expand...
Click to collapse
Wait so if I odin, I will still have the apps installed and google wallet? (and system settings)
That sounds too good to be true
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
kennyglass123 said:
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Click to expand...
Click to collapse
Right! I should have known that!!! thanks for moving it! sorry
Sent from my SAMSUNG-SGH-I337 using xda premium
There is a bug with the latest android N, only the little cores seems to work. You can check it with cpu-z and a stress test.
Also, more info here: https://code.google.com/p/android/i...porter Opened&groupby=&sort=-opened&id=206819
Do you think this will be a quick patch or stay like it until the next developer preview?
It's stil a beta, maybe there will be a patch or in the next preview...the performance overall isnt that affected. You can also change the kernel .
Enrolled in beta last night did OTA to N will check cpu z see if same battery life still sucks 6am - 1:30pm and 17% left ?
Sent from my Nexus 5X using Tapatalk
i don't have this bug i don't know why
i ceched it with elemental x app
I don't have this issue either. All six cores running properly.
took the OTA from DP2 to DP3 and can confirm its happening to me too. i'll try installing the system image and see if that fixes it.
I'm not sure this is a problem with N but rather a problem with the apps you're using to measure the CPU cores themselves.
There's a command: adb shell cat /proc/stat
Type that in terminal with your phone connected and check it out
Now i'm no wiz at android or anything, but the columns it gives back are readings of how long the cpu cores have spent in certain states.
The meanings of the columns are as follows, from left to right:
user: normal processes executing in user mode
nice: niced processes executing in user mode
system: processes executing in kernel mode
idle: twiddling thumbs
iowait: waiting for I/O to complete
irq: servicing interrupts
softirq: servicing softirqs
Tayos-Mac-Pro:~ TayoOnabule$ adb shell cat /proc/stat
cpu 29779 16626 40322 263858 3638 5754 3666 0 0 0
cpu0 11365 9362 17248 101562 2611 2185 1182 0 0 0
cpu1 6731 3452 9271 30395 319 846 700 0 0 0
cpu2 6258 2891 7887 31142 243 708 572 0 0 0
cpu3 1245 391 3335 33573 216 458 469 0 0 0
cpu4 2344 377 1433 33444 130 1422 299 0 0 0
cpu5 1834 150 1146 33740 116 133 440 0 0 0
intr 2777034 0 3 0 3 0 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 618895 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 96044 0 0 0 0 0 0 0 343 0 0 136 0 0 0 0 0 2236 2 5 0 0 0 0 0 12538 0 0 0 0 0 0 0 0 0 0 274 0 0 0 0 2 416 2 0 2 0 0 0 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 22521 0 0 0 0 0 0 0 0 0 0 0 0 26715 0 0 0 112 12660 0 346 0 25 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 381885 0 0 0 0 0 0 0 1413 0 0 0 0 0 0 1011 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 12595 0 6 0 0 0 0 20317 7011 0 0 0 121135 0 0 1141 0 0 0 0 0 0 0 0 1 0 0 14757 619 0 0 0 0 0 548 0 1839 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6983 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 9189 0 0 0 0 52677 0 0 0 0 0 0 288 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 529 26 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 0 94 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 21 0 0 0 0 0 0 0 0 0 0 0 303 0 0 0 0 292 0 2147 3 66 509 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 341 3643 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 131 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 161 0 0 0 0 0 0 0
ctxt 5896731
btime 1463686046
processes 11422
procs_running 1
procs_blocked 0
softirq 1957987 1198 375954 3331 23764 1198 1198 288344 370196 1092 891712
Tayos-Mac-Pro:~ TayoOnabule$
Click to expand...
Click to collapse
Edit: I also can't see the big cores working in CPU-Z, but doing this command it is obvious that they are actually working... apart from anything else N is so buttery smooth they must be working
/proc/stat actually shows that the 2 big cores are working. Cpu-z or cpu-x seem slow (or even fail) to update core speed. Try same with Antutu's cpu info (Info > cpu info > more) or tinycore (cpu profil, system info) and run a cpu heavy task that doesn't get low priority or stops when in background. Both should show actual values while on cpu-z/-x the big cores are still marked sleeping/stopped.
Are you sure this isn't thermal throttling? After the image first installed the cores temp was too high so it throttled the large cores off... once temps stabilized the big cores came back online. I think this is just a CPUZ bug to be honest.
It's just CPU-Z.
You can't expect every application to function properly on developer previews.
What's best way to return to M flash factory image suppose will loose everything? as I did OTA update from M to N and didn't loose anything
Sent from my Nexus 5X using Tapatalk
DoobyDroid said:
What's best way to return to M flash factory image suppose will loose everything? as I did OTA update from M to N and didn't loose anything
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I can answer that one! just go back to the enrol page and click unroll device from beta your phone will receive a ota for latest build , unfortunately its a wipe so back up important tack first.........
Yeah my Android N is rooted i use kernel auditor with the stock supersu kernel and it shows cores working.
very low score in geekbench 3/antutu on n preview 3
the cores are definitely offline
meisking1 said:
very low score in geekbench 3/antutu on n preview 3
the cores are definitely offline
Click to expand...
Click to collapse
Nope they are not, CPUZ is just having hard time detecting the cores on N.
Those two benchmark tools are notoriously worthless and doesn't maximize all the cores of multi-core SoC.
Antutu used to be good until they changed the scoring system and gave favor to crippled phones like iCrap and some android with low resolution and fast graphics processor.
Geekbench only uses Core 1 at 100% and 2 a little bit lower and the rest are like 10-25% load.
{
"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"
}
Consider S820 vs A9
They are both head to head in single core IPC and yet the A9 manages to score 4.5K on multicore result while S820 only about 5.3K.
Joms_US said:
Nope they are not, CPUZ is just having hard time detecting the cores on N.
Those two benchmark tools are notoriously worthless and doesn't maximize all the cores of multi-core SoC.
Antutu used to be good until they changed the scoring system and gave favor to crippled phones like iCrap and some android with low resolution and fast graphics processor.
Geekbench only uses Core 1 at 100% and 2 a little bit lower and the rest are like 10-25% load.
Consider S820 vs A9
They are both head to head in single core IPC and yet the A9 manages to score 4.5K on multicore result while S820 only about 5.3K.
Click to expand...
Click to collapse
So is there any app that can detect if the cores are running?
playing asphalt 8 and its lagger than in mm
i am curious if the cores are really running
meisking1 said:
So is there any app that can detect if the cores are running?
playing asphalt 8 and its lagger than in mm
i am curious if the cores are really running
Click to expand...
Click to collapse
CPU stats does for me.
On stock system thermal throttling kicks in early and big cores are meant as short time boosts not permanent speed up. So you'll see relatively little use anyway
The animations of Android N in slowmotion
http://www.bitfeed.co/page/the-animations-of-android-n-in-slowmotion-video
I just got a Pixi 7 from T-mobile on thursday, and there is a app on the Play Store called Kingo ROOT that I used to root my Pixi. So I used AGK Fire, and loaded it onto my Fire Stick, and ran it. I also had to put SuperUser on the Fire Stick. Now I have root, and disabled the Blacklist, and ota updates.
If this is known, and a guarded secret, please let me know
I was surprised that it worked
Which Kingo root app (imagine you type in Kingo root) is it the first selection? from the playstore did you use? Im wanting my fire stick 5.0.5.1 Rooted also. Cheers
@jaminmc
do you mean that one? https://www.kingoapp.com/
Tried 5 times now and I get root failed. Im using the one downloaded straight from www.kingoapp.com. Maybe he used a different version?
sconnyuk said:
Maybe he used a different version?
Click to expand...
Click to collapse
He used the play store version
Rooting app in playstorw? That won't last long. Lol
Sent from my iPhone using Tapatalk
Yes I read that he used playstore version but when I try to get the playstore version I cant seem to find it, so went directly to the website of the app he used. I tried v3.1 and no success.
@jaminmc Can you link us to the play store app?
Im currently waiting on a replacement fire tv stick to arrive tomorrow and im wondering if its going to come on 5.0.5 or 5.0.5.1 any idea people?
Tried all 3 versions of Kingo root. 2.5, 2.9 and 3.1. None have been successful in rooting 5.0.5.1. I can only assume the op is mistaken.?
Here is the exact APK I used. I also had to have the app "Rotate screen orientation " lock all apps in landscape mode, as kingo wants to open in portrait.
Below should be all you need...
You will need a mouse, or I just used "RemoteMouse" with my iPhone.
The first time I ran it, I thought it froze, and I held the center, Play-pause buttons to reboot the Fire Stick, and on reboot, I ran it again, and it worked. While it was rebooting, the progress bar started moving. SuperUser needs to be installed for it to work.
I Installed BusyBox, as uname isn't on the Fire Stick by default. I also did the Home button double-press disable as proof that it is on 5.0.5.1
Code:
$ adb shell
[email protected]:/ $ su
[email protected]:/ # uname -a
Linux localhost 3.0.31+ #3 SMP PREEMPT Sun May 15 01:19:40 UTC 2016 armv7l GNU/Linux
[email protected]:/ # cat /proc/cmdline
console=none androidboot.hardware=montoya androidboot.selinux=enforcing [email protected] lpj=12001280 androidboot.serialno=70940507607XXXXX s.irdrop=534 silicon.type=Typical_Fast usb_charge_type=wall_charger uboot_timestamp=2015-11-12
[email protected]:/ # pm disable com.amazon.venezia/com.amazon.venezia.list.AppsLibraryDeeplinkEventReceiver
Component {com.amazon.venezia/com.amazon.venezia.list.AppsLibraryDeeplinkEventReceiver} new state: disabled
[email protected]:/ # top
User 10%, System 4%, IOW 0%, IRQ 0%
User 51 + Nice 11 + Sys 29 + Idle 521 + IOW 0 + IRQ 0 + SIRQ 0 = 612
PID PR CPU% S #THR VSS RSS PCY UID Name
144 0 3% S 18 57844K 4144K fg system /system/bin/surfaceflinger
3091 1 3% S 74 1055380K 42464K fg u0_a23 com.waxrain.airplaydmr
5361 0 2% S 40 1099740K 54800K fg amz_u0a4 com.amazon.bueller.photos
3235 0 1% S 70 1047828K 41356K bg amz_u0a3 com.amazon.whisperlink.core.android
5782 0 0% R 1 2500K 984K fg root top
51 0 0% S 1 0K 0K fg root VCHIQ-0
29 1 0% S 1 0K 0K fg root ksmd
1225 0 0% S 1 0K 0K fg root usb-thread
3148 0 0% S 1 964K 180K fg u0_a23 /data/data/com.waxrain.airplaydmr/files/wdog2
52 0 0% S 1 0K 0K fg root VCHIQr-0
1167 0 0% S 22 989300K 28336K fg system com.amazon.device.services
1060 1 0% S 91 1076764K 65484K fg system system_server
15 1 0% S 1 0K 0K fg root i2c_master_rese
16 1 0% S 1 0K 0K fg root i2c_master_rese
17 1 0% S 1 0K 0K fg root knllog
18 0 0% S 1 0K 0K fg root sync_supers
19 0 0% S 1 0K 0K fg root bdi-default
20 1 0% S 1 0K 0K fg root kblockd
21 0 0% S 1 0K 0K fg root kworker/0:1
22 0 0% S 1 0K 0K fg root khubd
23 1 0% S 1 0K 0K fg root cfg80211
24 1 0% S 1 0K 0K fg root kworker/1:1
25 1 0% S 1 0K 0K fg root rpciod
26 1 0% S 1 0K 0K fg root bcm_hsotgctrl_e
27 1 0% S 1 0K 0K fg root khungtaskd
28 1 0% S 1 0K 0K fg root kswapd0
30 0 0% S 1 0K 0K fg root fsnotify_mark
31 1 0% S 1 0K 0K fg root nfsiod
32 1 0% S 1 0K 0K fg root crypto
50 0 0% S 1 0K 0K fg root VCHIQka-0
53 1 0% S 1 0K 0K fg root VCHIQs-0
54 0 0% S 1 0K 0K fg root vc-watchdog
55 1 0% S 1 0K 0K fg root kworker/u:1
62 1 0% S 1 0K 0K fg root dwc_otg
63 1 0% S 1 0K 0K fg root DWC Notificatio
64 1 0% S 1 0K 0K fg root f_mtp
65 1 0% S 1 0K 0K fg root file-storage
66 1 0% S 1 0K 0K fg root kinteractiveup
67 1 0% S 1 0K 0K fg root SPUM proc threa
68 1 0% S 1 0K 0K fg root SPUM done threa
73 1 0% S 1 0K 0K fg root SPUM proc threa
74 1 0% S 1 0K 0K fg root SPUM done threa
79 1 0% S 1 0K 0K fg root binder
80 1 0% S 1 0K 0K fg root irq/156-caph-in
81 1 0% S 1 0K 0K fg root AudioCtrlWq
82 1 0% S 1 0K 0K fg root VC-FB-Read
83 0 0% S 1 0K 0K fg root SMIO
1 1 0% S 1 920K 404K fg root /init
85 0 0% S 1 0K 0K fg root mmcqd/0boot0
86 0 0% S 1 0K 0K fg root mmcqd/0boot1
87 0 0% S 1 0K 0K fg root mmcqd/0rpmb
88 0 0% S 1 900K 212K fg root /sbin/ueventd
90 0 0% S 1 0K 0K fg root jbd2/mmcblk0p15
91 1 0% S 1 0K 0K fg root ext4-dio-unwrit
94 1 0% S 1 0K 0K fg root flush-179:0
98 0 0% S 1 0K 0K fg root jbd2/mmcblk0p18
99 1 0% S 1 0K 0K fg root ext4-dio-unwrit
100 0 0% S 1 0K 0K fg root jbd2/mmcblk0p17
101 0 0% S 1 0K 0K fg root ext4-dio-unwrit
112 0 0% S 1 0K 0K fg root jbd2/mmcblk0p5-
113 0 0% S 1 0K 0K fg root ext4-dio-unwrit
121 0 0% S 1 1148K 496K fg root /system/bin/sh
139 0 0% S 5 6548K 776K fg logd /system/bin/logd
140 1 0% S 1 1588K 148K fg root /sbin/healthd
141 0 0% S 1 2392K 648K fg root /system/bin/lmkd
142 0 0% S 1 1248K 464K fg system /system/bin/servicemanager
143 1 0% S 3 5820K 1084K fg root /system/bin/vold
145 1 0% S 7 8540K 576K fg system /system/bin/mcDriverDaemon
153 0 0% S 9 10816K 952K fg root /system/bin/netd
157 0 0% S 1 1816K 516K fg root /system/bin/debuggerd
158 1 0% S 1 1944K 608K fg install /system/bin/installd
162 0 0% S 2 21404K 2824K fg root /system/xbin/vitals_collection_agent
164 0 0% S 11 42528K 2740K fg media /system/bin/mediaserver
165 1 0% S 11 31636K 2336K fg system /system/bin/tvserver
169 0 0% S 5 6392K 752K fg system /system/bin/vclmk
176 1 0% S 5 6296K 768K fg system /system/bin/cecdaemon
177 0 0% S 1 4364K 1160K fg keystore /system/bin/keystore
178 1 0% S 6 966408K 29072K fg root zygote
179 1 0% S 3 4028K 832K fg media_rw /system/bin/sdcard
180 0 0% S 1 1324K 308K fg root /system/bin/btremoted
182 0 0% S 8 7728K 252K fg shell /sbin/adbd
245 1 0% S 1 0K 0K fg root kauditd
289 1 0% S 1 0K 0K fg root mc_log
338 0 0% S 1 0K 0K fg root kworker/0:2
462 0 0% S 5 19892K 3296K fg drm /system/bin/drmserver
562 0 0% S 1 1064K 164K fg root daemonsu:mount:master
744 1 0% S 3 3116K 268K fg root daemonsu:master
760 0 0% S 1 19892K 3296K fg drm /system/bin/drmserver
1221 1 0% S 1 0K 0K fg root wlfc-mon-thread
1224 0 0% S 1 0K 0K fg root wl_event_handle
1363 1 0% S 12 983240K 25584K bg amz_u0a6 com.amazon.tv.ime
1412 0 0% S 1 5120K 1660K fg wifi /system/bin/wpa_supplicant
1420 1 0% S 14 976792K 23916K bg amz_u0a5 com.amazon.precog
1432 1 0% S 15 984600K 25028K fg amz_u0a7 com.amazon.vizzini
1444 0 0% S 16 984768K 24252K bg amz_u0a1 com.amazon.device.logmanager
1471 1 0% S 20 985444K 33868K bg amz_u0a4 com.amazon.imp
1499 1 0% S 25 997252K 33224K bg amz_u0a6 com.amazon.tcomm
1526 0 0% S 43 1063040K 43428K bg amz_u0a6 com.amazon.tv.launcher
1606 1 0% S 47 1016240K 29824K bg amz_u0a2 com.amazon.client.metrics
1631 0 0% S 18 983648K 25428K bg amz_u0a2 com.amazon.device.settings
1755 0 0% S 1 972K 352K bg amz_u0a5 logcat
1819 1 0% S 21 996956K 32564K bg amz_u0a6 com.amazon.tv.launcher:MediaBrowseServiceProcess
1836 1 0% S 15 987772K 31968K bg amz_u0a5 com.amazon.kso.blackbird:BlackbirdServiceProcess
1849 1 0% S 1 1112K 340K fg nobody /system/bin/dnsmasq
1870 1 0% S 1 1040K 400K bg amz_u0a2 logcat
1888 1 0% S 1 1108K 384K fg root /system/bin/sh
1980 0 0% S 51 1085684K 50744K bg amz_u0a3 com.amazon.avod
2006 0 0% S 12 974432K 25608K bg u0_a2 com.amazon.device.controllermanager
2029 1 0% S 24 1002908K 32408K bg amz_u0a6 com.amazon.tv.launcher:GlobalNavProcess
2135 1 0% S 1 1112K 364K fg dhcp /system/bin/dhcpcd
2136 1 0% S 1 1116K 200K fg root /system/bin/sh
2137 1 0% S 1 1108K 180K fg root /system/bin/sh
2166 0 0% S 1 1012K 332K fg root /system/bin/ping
2167 1 0% S 1 2428K 568K fg root grep
2197 1 0% S 1 0K 0K fg root kworker/1:2
2410 1 0% S 27 1000832K 26080K fg bluetoot com.android.bluetooth
2419 0 0% S 1 1292K 656K fg root /system/bin/sh
2763 0 0% S 28 1001428K 35632K bg u0_a30 com.kingouser.com
2812 1 0% S 1 3116K 204K fg root daemonsu:10030
3672 1 0% S 20 993760K 41456K fg u0_a15 de.belu.firestopper
3695 0 0% S 32 1002416K 32272K fg u0_a22 com.guidology.android.remotemouseforfiretv
3740 0 0% S 13 993576K 26520K bg u0_a29 net.loadinghome.rotatescreenorientation
3809 1 0% S 2 5168K 448K fg root daemonsu:0
3870 1 0% S 10 972256K 22728K bg u0_a2 com.amazon.device.controllermanager:BluetoothReceiver
3896 0 0% S 53 1045076K 46868K bg amz_u0a7 com.amazon.venezia
3958 1 0% S 14 983116K 28788K bg amz_u0a1 com.android.providers.downloads
4255 1 0% S 10 981540K 22468K bg amz_u0a5 com.amazon.kso.blackbird
4283 0 0% S 10 972264K 22368K bg u0_a2 com.amazon.device.controllermanager:WifiReceiver
4347 0 0% S 1 1116K 560K fg shell /system/bin/sh
4363 0 0% S 1 1064K 472K fg shell su
4366 0 0% S 1 5176K 580K fg root daemonsu:0:4363
4370 1 0% S 1 1120K 564K fg root tmp-mksh
4509 1 0% S 21 1005348K 37920K bg amz_u0a5 com.amazon.kindle.cms
4570 0 0% S 16 989604K 32044K bg amz_u0a6 com.amazon.storm.lightning.services
4619 1 0% S 11 975212K 26652K bg amz_u0a7 com.amazon.sync.service
4849 1 0% S 10 974256K 26656K bg amz_u0a5 com.amazon.securitysyncclient
5405 1 0% S 22 1000016K 34880K fg amz_u0a4 com.amazon.bueller.photos:core
84 0 0% S 1 0K 0K fg root mmcqd/0
2 0 0% S 1 0K 0K fg root kthreadd
3 0 0% S 1 0K 0K fg root ksoftirqd/0
5 0 0% S 1 0K 0K fg root kworker/u:0
6 0 0% S 1 0K 0K fg root migration/0
7 1 0% S 1 0K 0K fg root migration/1
9 1 0% S 1 0K 0K fg root ksoftirqd/1
10 1 0% S 1 0K 0K fg root khelper
11 1 0% S 1 0K 0K fg root netns
12 1 0% S 1 0K 0K fg root suspend
13 1 0% S 1 0K 0K fg root i2c_master_rese
14 1 0% S 1 0K 0K fg root i2c_master_rese
Did someone try this on a FireTV 1 with 5.0.5.1? I am not at home right now, so I can't try.
I will try it today... Did you install Super User after rooting or before?
cuki3r3k83bln said:
Did you install Super User after rooting or before?
Click to expand...
Click to collapse
jaminmc said:
SuperUser needs to be installed for it to work.
Click to expand...
Click to collapse
Tried this as you did jaminmc and still fails, any other variable you might of done? Cheers
jaminmc said:
Here is the exact APK I used. I also had to have the app "Rotate screen orientation " lock all apps in landscape mode, as kingo wants to open in portrait.
Below should be all you need...
You will need a mouse, or I just used "RemoteMouse" with my iPhone.
The first time I ran it, I thought it froze, and I held the center, Play-pause buttons to reboot the Fire Stick, and on reboot, I ran it again, and it worked. While it was rebooting, the progress bar started moving. SuperUser needs to be installed for it to work.
Click to expand...
Click to collapse
I tried it on a 5.0.5.1 Fire TV Stick, replicating what you say, and also failed. I did not need a mouse btw since pressing the center button on the remote starts the rooting process.
If you're not just trolling us, the only thing I can think of is that there's some sweet spot during the rooting attempt that the device needs to be restarted which you hit, since you say "while it was rebooting, the progress bar started moving." Do you remember what percentage it was stuck at? It never goes past 90% for me and then eventually says root failed after about 2 minutes at 90%. When the bar started moving while it rebooted, did it go past 90%?
If there is some sweet spot to reboot at, my guess is it's from when it stops at 90% to 50 seconds later. Around 50 seconds after it stops at 90%, the app tries to mount the system partition as writable and fails.
Tried the same with running su before and after kingo root and restarted at several times while it was at 90 % but had no luck until now...
I finally got root succeeded, the way I did it was as per op instructions. When it gets to 90 percent I waited around 45 seconds then held home/play pause down. Restsrted then re launched Kingo ?
Tried it too with my second FTV Stick running 5.0.5.1 and it fails...