Sent from my GT-N7100 using XDA Free mobile app
Affichage des articles dont le libellé est restart. Afficher tous les articles
Affichage des articles dont le libellé est restart. Afficher tous les articles
mardi 25 août 2015
dimanche 23 août 2015
Random restart and bootloop problems
hi guys, i'm a note 3 international version(SM-N9005) owner. Since a couple of months ago my device updated to the last version of lollipop available in Italy (ITV) start to restart randomly and stuck in bootloop and the only way to revive the device is to do a factory reset from recovery. This situation is very frustrating and drives me mad because every time i lost all data. My device is full stock, i've never rooted it and never done any sort of modding including changing recovery. There's a way to avoid this situation?
vendredi 21 août 2015
air command on s pen restart note 4
it is as it shown in the title the s pen words fine and everything, but as soon as i press the button on it to show air command the phone restarts with a msg for 1 sec or less that a process is not responding
jeudi 20 août 2015
[Q] Stucked at bootanimation after restart
I've posted this question in the ROM thread but not all read that threat so maybe you can help me
Has anyone got some problems getting stuck at the bootanimation after rebooting the phone? One of 3 reboots gets me stucked at the bootanimation, I have to hold the power and volume to power off the phone and when it reboots is optimising the application wich takes like 15 minutes to do that. That is what is bothering me. The fact that I have to wait 15 minutes to optimize the applications. I think it has something to do with Xposed.
Besides that the ROM is working flawless. Is the latest stock 5.1.1 with xposed and about 8-10 modules.
Has anyone had this problem?
Thank you!
Has anyone got some problems getting stuck at the bootanimation after rebooting the phone? One of 3 reboots gets me stucked at the bootanimation, I have to hold the power and volume to power off the phone and when it reboots is optimising the application wich takes like 15 minutes to do that. That is what is bothering me. The fact that I have to wait 15 minutes to optimize the applications. I think it has something to do with Xposed.
Besides that the ROM is working flawless. Is the latest stock 5.1.1 with xposed and about 8-10 modules.
Has anyone had this problem?
Thank you!
mercredi 19 août 2015
Xperia Z auto restart
Hi, my xperia Z 5.0.2 rooted no BLU is sometime auto restart. How can i fix this matter? Plz help me.
mardi 18 août 2015
NEED HELP!! My nexus is on some kind of restart loop!!
My nexus suddenly reboot and keep doing the same thing every time, i can put my pin and all but after 1 min of put the pin my phone reboot and do the same thing over and over. I try to flash a new ROM but even after doing that my phone restore my previous ROM and even the files and settings. I try to change the recovery to TWRP and after the restart my recovery change to my old recovery(cwm) i dont know what else to do. I try everything, flash, wipe, unroot,root, restore to factory rom and nothing. PLS I REALLY NEED HELP!! Thank you.
lundi 17 août 2015
Restart at Sony logo
i had wiped data and cache from the recovery menu of xperia c after that the phone keeps restating at sony logo and that chinese software which is there in that phone doesnt get detected to flash so how can i flash original rom.
jeudi 13 août 2015
Constant BSOD and restart, BUGCODE_USB_DRIVER Error. Help!
I installed Windows 10 a few days ago. Since then, my computer regularly restarts and says it's because of a BUGCODE_USB_DRIVER error. This seems to only be a problem when I have my wireless keyboard and mouse attached through a wireless USB device. I have a Microsoft sculpt comfort keyboard and mouse.
So far, I've:
System Information (local)
computer name: MASTER-PC
windows version: Windows 10 , 10.0, build: 10240
windows dir: C:\WINDOWS
Hardware: 10249RU, LENOVO, Emerald Lake
CPU: GenuineIntel Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8499900416 total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 8/14/2015 1:10:28 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump1315-16765-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE000F505A410, 0xFFFFE000F5A3DB10, 0xFFFFE000F8261A0C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 8/14/2015 1:10:28 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: usbport.sys (USBPORT!USBPORT_GetHciMn+0x1096B)
Bugcheck code: 0xFE (0x4, 0xFFFFE000F505A410, 0xFFFFE000F5A3DB10, 0xFFFFE000F8261A0C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 8/13/2015 9:48:56 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump1315-17750-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE0001F817560, 0xFFFFE0001F37FA50, 0xFFFFE00020D1CA0C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 8/13/2015 9:19:10 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump1315-17703-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE001F2DA49D0, 0xFFFFE001F3C0EAE0, 0xFFFFE001F50C34DC)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 8/13/2015 9:07:54 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump1315-22093-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE001A0CEEB60, 0xFFFFE001A2070470, 0xFFFFE001A201344C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 8/13/2015 8:16:29 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump1315-40312-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE001E199DCF0, 0xFFFFE001E24BCA90, 0xFFFFE001E68E1A0C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
So far, I've:
- Uninstalled and reinstalled all USBs.
- Updated all of my drivers.
- Completely reinstalled Windows 10.
- Updated the computers BIOS.
System Information (local)
computer name: MASTER-PC
windows version: Windows 10 , 10.0, build: 10240
windows dir: C:\WINDOWS
Hardware: 10249RU, LENOVO, Emerald Lake
CPU: GenuineIntel Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8499900416 total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 8/14/2015 1:10:28 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump1315-16765-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE000F505A410, 0xFFFFE000F5A3DB10, 0xFFFFE000F8261A0C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 8/14/2015 1:10:28 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: usbport.sys (USBPORT!USBPORT_GetHciMn+0x1096B)
Bugcheck code: 0xFE (0x4, 0xFFFFE000F505A410, 0xFFFFE000F5A3DB10, 0xFFFFE000F8261A0C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 8/13/2015 9:48:56 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump1315-17750-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE0001F817560, 0xFFFFE0001F37FA50, 0xFFFFE00020D1CA0C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 8/13/2015 9:19:10 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump1315-17703-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE001F2DA49D0, 0xFFFFE001F3C0EAE0, 0xFFFFE001F50C34DC)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 8/13/2015 9:07:54 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump1315-22093-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE001A0CEEB60, 0xFFFFE001A2070470, 0xFFFFE001A201344C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 8/13/2015 8:16:29 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump1315-40312-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE001E199DCF0, 0xFFFFE001E24BCA90, 0xFFFFE001E68E1A0C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Asus Fonepad 7 ME372CG doesn't restart while updating, reset not possible?
Hey,
i am new to this forum. I have a weird issue with my Asus Fonepad 7 ME372CG while updating. The Device is NOT rooted or flashed in any way.
When updating the Fonepad shuts down and is supposed to restart. The Problem is, the Fonepad does not start again and cant be turned on again for several hours. If you hold the Power button the device vibrates and the screens flashes for a millisecond, but thats all.
After some hours the Fonepad will eventually start again, but the update is not installed.
The same happens when I tried to reset the Fonepad in "Droid Boot" modus.
Any suggestions how i can fix the problem. I just want to have the device running normally again, or with stock android.
Thanks in advance!
i am new to this forum. I have a weird issue with my Asus Fonepad 7 ME372CG while updating. The Device is NOT rooted or flashed in any way.
When updating the Fonepad shuts down and is supposed to restart. The Problem is, the Fonepad does not start again and cant be turned on again for several hours. If you hold the Power button the device vibrates and the screens flashes for a millisecond, but thats all.
After some hours the Fonepad will eventually start again, but the update is not installed.
The same happens when I tried to reset the Fonepad in "Droid Boot" modus.
Any suggestions how i can fix the problem. I just want to have the device running normally again, or with stock android.
Thanks in advance!
mercredi 12 août 2015
Random reboots (restart reason = 77665501)
Had my M8 Since Nov 2014 and almost immediately installed CM. Been on CM11m12 for 6+ months and the phone has been fine. softkey area of screen started to die, so got a replacement M8 from VZW. Restored everything via nandroid and all seemed well.... until the phone now will randomly reboot -- even when I'm not using it and its just sitting on the desk. pulled logcat, etc and it appears something is causing it to shutdown, but I'm unable to determine exactly what.
Thoughts?
Thoughts?
Code:
[69899.843696] c0 27034 wakeup sources: 'PowerManagerService.WakeLocks' 'PowerManagerService.Display' 'radio-interface' 'ges_wake_lock', time left 148 ticks;
[69900.771346] c3 263 pid:263(vold)(parent:1/init) (mmcblk1p1) umounted filesystem.
[69900.773494] c3 263 pid:263(vold)(parent:1/init) (fuse) umounted filesystem.
[69900.790603] c3 263 pid:263(vold)(parent:1/init) (mmcblk1p1) umounted filesystem.
[69900.814516] c3 1 init: untracked pid 1152 exited
[69901.558108] c2 26076 binder: 25885:26076 transaction failed 29189, size 184-0, brdr_fp 33
[69901.558296] c2 26076 binder: 25885:26076 transaction failed 29189, size 184-0, brdr_fp 33
[69901.558435] c2 26076 binder: 25885:26076 transaction failed 29189, size 184-0, brdr_fp 33
[69901.558520] c2 26076 binder: 25885:26076 transaction failed 29189, size 184-0, brdr_fp 33
[69901.558596] c2 26076 binder: 25885:26076 transaction failed 29189, size 184-0, brdr_fp 33
[69901.558674] c2 26076 binder: 25885:26076 transaction failed 29189, size 184-0, brdr_fp 33
[69901.744472] c3 1 init (1:1) triggered SysRq
[69901.744484] c3 1 SysRq : Emergency Remount R/O
[69901.747732] c3 26064 pid:26064(kworker/3:0)(parent:2/kthreadd) (mmcblk0p39) umounted filesystem.
[69901.747817] c3 26064 zcache: destroyed pool id=3, cli_id=65535
[69901.786145] c3 26064 pid:26064(kworker/3:0)(parent:2/kthreadd) (mmcblk0p27) umounted filesystem.
[69901.786233] c3 26064 zcache: destroyed pool id=4, cli_id=65535
[69901.846377] c3 26064 EXT4-fs (mmcblk0p49): re-mounted. Opts: (null)
[69901.894739] c3 26064 EXT4-fs (mmcblk0p48): re-mounted. Opts: (null)
[69901.896789] c3 26064 EXT4-fs (mmcblk0p22): re-mounted. Opts: (null)
[69901.896946] c3 26064 Emergency Remount complete
[69901.945742] c3 1 kernel_restart: system_dirty=1
[69901.945758] c3 1 notify_efs_sync_call: board_mfg_mode=0
[69901.945771] c3 1 [K] set_modem_efs_sync: wait for modem efs_sync
[69902.309964] c1 0 CPU1: msm_pm_power_collapse: change clock rate (old rate = 0)
[69902.596923] c3 26022 [LED]qpnp_led_set id: 1 value 0 status: 255
[69902.818060] c1 0 CPU1: msm_pm_power_collapse: change clock rate (old rate = 0)
[69902.871122] c2 0 CPU2: msm_pm_power_collapse: change clock rate (old rate = 0)
[69902.873906] c3 25630 msm_vidc: 4: Opening video instance: eaf83000, 0
[69902.886963] c3 25630 pil_venus fdce0000.qcom,venus: venus: loading from 0x0f500000 to 0x0fa00000
[69902.938865] c3 25630 pil_venus fdce0000.qcom,venus: venus: Brought out of reset
[69902.953430] c3 1 check_modem_efs_sync_timeout: modem efs_sync done.
[69902.953442] c3 1 [FLT]TPS reboot_notify_sys: 1
[69902.953449] c3 1 [FLT]TPS flashlight_turn_off
[69902.953851] c3 1 [FLT]TPS flashlight_turn_off 0
[69902.955103] c3 1 mdss_fb_release_all: try to close unopened fb 2! from init
[69902.955118] c3 1 mdss_fb_release_all: try to close unopened fb 1! from init
[69902.964096] c3 26078 msm_vidc: 4: Closed video instance: eaf83000
[69902.966931] c3 1 mdss_fb_release_all: remove process init from tracking, pid=1 mfd->ref_cnt=0
[69902.966943] c3 1 mdss_fb_release_all: unknown process init pid=1 mfd->ref=0
[69902.966967] c3 1 [<c010c19c>] (unwind_backtrace+0x0/0x11c) from [<c041b3c4>] (mdss_fb_release_all+0x368/0x4a0)
[69902.966982] c3 1 [<c041b3c4>] (mdss_fb_release_all+0x368/0x4a0) from [<c041b528>] (mdss_fb_shutdown+0x2c/0x3c)
[69902.966997] c3 1 [<c041b528>] (mdss_fb_shutdown+0x2c/0x3c) from [<c04b07c0>] (platform_drv_shutdown+0x14/0x18)
[69902.967013] c3 1 [<c04b07c0>] (platform_drv_shutdown+0x14/0x18) from [<c04ad390>] (device_shutdown+0xf0/0x138)
[69902.967029] c3 1 [<c04ad390>] (device_shutdown+0xf0/0x138) from [<c01b382c>] (kernel_restart_prepare+0x2c/0x3c)
[69902.967043] c3 1 [<c01b382c>] (kernel_restart_prepare+0x2c/0x3c) from [<c01b3880>] (kernel_restart+0x24/0x68)
[69902.967058] c3 1 [<c01b3880>] (kernel_restart+0x24/0x68) from [<c01b3b80>] (sys_reboot+0x1f4/0x268)
[69902.967074] c3 1 [<c01b3b80>] (sys_reboot+0x1f4/0x268) from [<c01064c0>] (ret_fast_syscall+0x0/0x30)
[69902.968715] c3 26078 msm_vidc: 4: Opening video instance: eaf84000, 1
[69902.970381] c3 26078 ------------[ cut here ]------------
[69902.970396] c3 26078 WARNING: at ../../../../../../kernel/htc/msm8974/drivers/base/firmware_class.c:684 __request_firmware+0x40/0xd8()
[69902.970416] c3 26078 [<c010c19c>] (unwind_backtrace+0x0/0x11c) from [<c01a0894>] (warn_slowpath_common+0x48/0x60)
[69902.970432] c3 26078 [<c01a0894>] (warn_slowpath_common+0x48/0x60) from [<c01a0964>] (warn_slowpath_null+0x18/0x1c)
[69902.970447] c3 26078 [<c01a0964>] (warn_slowpath_null+0x18/0x1c) from [<c04bc064>] (__request_firmware+0x40/0xd8)
[69902.970461] c3 26078 [<c04bc064>] (__request_firmware+0x40/0xd8) from [<c04bc10c>] (request_firmware+0x10/0x14)
[69902.970480] c3 26078 [<c04bc10c>] (request_firmware+0x10/0x14) from [<c012fc88>] (pil_boot+0x50/0xa74)
[69902.970495] c3 26078 [<c012fc88>] (pil_boot+0x50/0xa74) from [<c015a270>] (subsystem_get+0x7c/0x110)
[69902.970513] c3 26078 [<c015a270>] (subsystem_get+0x7c/0x110) from [<c061c6a8>] (venus_hfi_load_fw+0x170/0x748)
[69902.970531] c3 26078 [<c061c6a8>] (venus_hfi_load_fw+0x170/0x748) from [<c05ff8f0>] (msm_comm_try_state+0x32c/0x1814)
[69902.970546] c3 26078 [<c05ff8f0>] (msm_comm_try_state+0x32c/0x1814) from [<c0605b10>] (msm_vidc_open+0x43c/0x5b0)
[69902.970561] c3 26078 [<c0605b10>] (msm_vidc_open+0x43c/0x5b0) from [<c05f87dc>] (msm_v4l2_open+0x30/0xd4)
[69902.970579] c3 26078 [<c05f87dc>] (msm_v4l2_open+0x30/0xd4) from [<c06757cc>] (v4l2_open+0xa8/0xe4)
[69902.970595] c3 26078 [<c06757cc>] (v4l2_open+0xa8/0xe4) from [<c025fa44>] (chrdev_open+0x104/0x12c)
[69902.970611] c3 26078 [<c025fa44>] (chrdev_open+0x104/0x12c) from [<c0259c40>] (__dentry_open+0x1b4/0x29c)
[69902.970626] c3 26078 [<c0259c40>] (__dentry_open+0x1b4/0x29c) from [<c025aa5c>] (nameidata_to_filp+0x50/0x5c)
[69902.970642] c3 26078 [<c025aa5c>] (nameidata_to_filp+0x50/0x5c) from [<c0267c3c>] (do_last+0x7cc/0x800)
[69902.970656] c3 26078 [<c0267c3c>] (do_last+0x7cc/0x800) from [<c0267f60>] (path_openat+0x2f0/0x388)
[69902.970670] c3 26078 [<c0267f60>] (path_openat+0x2f0/0x388) from [<c0268024>] (do_filp_open+0x2c/0x78)
[69902.970684] c3 26078 [<c0268024>] (do_filp_open+0x2c/0x78) from [<c025ade0>] (do_sys_open+0xdc/0x1d8)
[69902.970698] c3 26078 [<c025ade0>] (do_sys_open+0xdc/0x1d8) from [<c01064c0>] (ret_fast_syscall+0x0/0x30)
[69902.970708] c3 26078 ---[ end trace da227214a82491bb ]---
[69902.970717] c3 26078 pil_venus fdce0000.qcom,venus: firmware: venus.mdt will not be loaded
[69902.970727] c3 26078 pil_venus fdce0000.qcom,venus: venus: Failed to locate venus.mdt
[69902.984580] c0 1 mdss_fb_release_all: fb0 release=true (ref=0)
[69903.149622] c0 1 [DISP] mdss_dsi_panel_off:-
[69903.157365] c0 1 [DISP] htc_m8_panel_power_on: en=0
[69903.182333] c0 1 [DISP] htc_m8_panel_power_on: en=0 done
[69903.184358] c0 238 mdss_fb_release_all: try to close unopened fb 0! from surfaceflinger
[69903.184414] c0 238 mdss_fb_release_all: try to close unopened fb 0! from surfaceflinger
[69903.187598] c0 1 set_rt5506_regulator:set regulator to PWM mode
[69903.203486] c0 1 rt5506_shutdown: enable gpio 62
[69903.223560] c0 1 rt5506_shutdown: reset rt5501
[69903.223585] c0 1 rt5506_write_reg: write reg 0x0 val 0x4
[69903.224952] c0 1 rt5506_shutdown: disable gpio 62
[69903.224974] c0 1 set_rt5506_regulator:set regulator to AUTO mode
[69903.225343] c0 1 [USB] android_shutdown ret : 0
[69903.226026] c0 1 mmc0: sdhci_msm_shutdown enter
[69903.226042] c0 1 sdhci_msm_shutdown: Lock eMMC
[69903.226057] c0 1 mmc0: sdhci_msm_shutdown leave
[69903.226389] c0 1 Restarting system with command ''.
[69903.226442] c0 1 Kernel command line: console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 zcache androidboot.emmc=true androidboot.serialno=FA44xxx ats=0 vmalloc=400m zygote_oneshot=on androidboot.rom_type=NORMAL androidboot.baseband=1.12.20.1211 androidboot.efuse_info=SL androidboot.mode=normal androidboot.bootloader=3.19.0.0000 kernelflag=0x0 debugflag=0x0 androidboot.devicerev=4 pcbid.bid=3 abnrst=0 radioflag=0x0 radioflagex1=0x0 radioflagex2=0x0 androidboot.pagesize=2048 androidboot.cid=VZW__001 androidboot.mid=0P6B20000 androidboot.engid=0 imc_online_log=0 color_ID= acpu.footprint=(0x3) androidboot.dq=PASS androidboot.batt_poweron=good_battery kmemleak=off rpm_debug.enable=0 androidboot.carrier=Verizon androidboot.keycaps=qwerty androidboot.ddrmid=(0x3) androidboot.lb=1 uif= ro.op=0 td.sf=0 td.td=1 td.ofs=328 td.prd=1 td.dly=0 td.tmo=300 hlog.ofs=628 un.ofs=696 qf.st=1 androidboot.podt=0x7D0 mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_m8_sharp_novatek_35595_1080p_cmd dap=6
[69903.226590] c0 1 [K] Going down for restart now
[69903.226647] c0 1 msm_restart: Kernel command line: console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 ehci-hcd.park=3 zcache androidboot.emmc=true androidboot.serialno=FA44xxx ats=0 vmalloc=400m zygote_oneshot=on androidboot.rom_type=NORMAL androidboot.baseband=1.12.20.1211 androidboot.efuse_info=SL androidboot.mode=normal androidboot.bootloader=3.19.0.0000 kernelflag=0x0 debugflag=0x0 androidboot.devicerev=4 pcbid.bid=3 abnrst=0 radioflag=0x0 radioflagex1=0x0 radioflagex2=0x0 androidboot.pagesize=2048 androidboot.cid=VZW__001 androidboot.mid=0P6B20000 androidboot.engid=0 imc_online_log=0 color_ID= acpu.footprint=(0x3) androidboot.dq=PASS androidboot.batt_poweron=good_battery kmemleak=off rpm_debug.enable=0 androidboot.carrier=Verizon androidboot.keycaps=qwerty androidboot.ddrmid=(0x3) androidboot.lb=1 uif= ro.op=0 td.sf=0 td.td=1 td.ofs=328 td.prd=1 td.dly=0 td.tmo=300 hlog.ofs=628 un.ofs=696 qf.st=1 androidboot.podt=0x7D0 mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_m8_sharp_novatek_35595_1080p_cmd dap=6
[69903.227390] c0 1 msm_restart_prepare: restart by command: []
[69903.227415] c0 1 set_restart_reason: set restart reason = 77665501
[69903.227432] c0 1 set_restart_msg: set restart msg = `'
[69903.227469] c0 1
[69903.227484] c0 1 [K] Restarting Linux version 3.4.0-g001341f (build02@cyanogenmod) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Wed Nov 12 03:16:44 PST 2014
[69903.227497] c0 1
[69903.227695] c0 1 Calling SCM to disable SPMI PMIC arbiter
No errors detectedlundi 10 août 2015
Samsung Glaxy s6 Restart as open any installed app :(
Purchased new glaxy s6 dual SM-G920FD ....
phoen working fine but as i install any app from playstore and as i open that installed app phone restart.....
How To fix ?
chekd aevery thing like reset etc
phoen working fine but as i install any app from playstore and as i open that installed app phone restart.....
How To fix ?
chekd aevery thing like reset etc
samedi 8 août 2015
Restart Xperia Z after Update
I have updated the Dirtyunicorn Rom and my device is working fine but from last day the device turn off and won't turn on by pressing the power button, so by chance i press and hold the power button along with volume up the device turns on it read all the apps and then display the home screen. This is happening after 3 to 5 hours. If this is a ROM problem than suggest me the best lollipop ROM and Kernal. And someone suggest me install stock ftf I dont know which region to install or which firmware i have .434 or .253
Restart Xperia Z after Update
I have updated the Dirtyunicorn Rom and my device is working fine but from last day the device turn off and won't turn on by pressing the power button, so by chance i press and hold the power button along with volume up the device turns on it read all the apps and then display the home screen. This is happening after 3 to 5 hours. If this is a ROM problem than suggest me the best lollipop ROM and Kernal.
vendredi 31 juillet 2015
Wifi tethering keeps giving no internet access until restart
I connect to the internet on both my laptop and my other phone via my Samsung Galaxy Tab 2 7" by wifi tethering.
Sometimes the internet works for a while and then i get that yellow exclamation mark on the wifi signal bars at the bottom right corner of my laptop screen (i am running windows 8. Same when i was running windows 7). Hover the mouse over it and it says "no internet access". So in order to get internet access to come back, i have to restart the Tab. As soon as i restart it, internet access comes back like normal. A min later, same thing happens. Internet access goes. Sometimes it goes within secs of restarting the Tab and tethering! sometimes a few minutes, sometimes hours...its just random like that. Nothing that i am doing/ru nning in spesific to cause this to happen either. It just randomly decides to go. Some days are good and some arent.
2 things are for sure...1) its not the laptop cz as soon as it goes on it, whatever other devices that are connected to the tab's interent also lose internet access. The connection never breaks though. Just the internet access. 2) Restarting the Tab immedietely fixes the ptoblem...although sometimes just temporarily.
The internet on the Tab itself works fine at all times.
Any ideas what is going on and how to fix it?
Sometimes the internet works for a while and then i get that yellow exclamation mark on the wifi signal bars at the bottom right corner of my laptop screen (i am running windows 8. Same when i was running windows 7). Hover the mouse over it and it says "no internet access". So in order to get internet access to come back, i have to restart the Tab. As soon as i restart it, internet access comes back like normal. A min later, same thing happens. Internet access goes. Sometimes it goes within secs of restarting the Tab and tethering! sometimes a few minutes, sometimes hours...its just random like that. Nothing that i am doing/ru nning in spesific to cause this to happen either. It just randomly decides to go. Some days are good and some arent.
2 things are for sure...1) its not the laptop cz as soon as it goes on it, whatever other devices that are connected to the tab's interent also lose internet access. The connection never breaks though. Just the internet access. 2) Restarting the Tab immedietely fixes the ptoblem...although sometimes just temporarily.
The internet on the Tab itself works fine at all times.
Any ideas what is going on and how to fix it?
jeudi 30 juillet 2015
Flash Lumia 535 Dual sim to Single sim - Automatic keyboard add after restart
Heyy,
I just bought Lumia 535 Dual Sim, I hate the second sim icon in the top bar as I don't have a second sim active. I have been reading this forum for tutorials to flash my Lumia 535. (Just Read: http://forum.xda-developers.com/show....php?t=2515453)
I was wondering if it was possible to flash it with a single sim firmware (Rm-1091) so that the second sim icon disappears without losing any functionality. If so, can someone help me as when I type my product code in navifirm, it gives only one firmware.
Moreover, whenever I restart my Lumia, a persian keyboard is automatically added, any way to fix that?
I tried Hard resetting it but when it resets, the default language is Slovensky. I dont know why that is. I have to change it to English (United States) but speech has English (United Kingdom) by default.
Help appreciated!
I just bought Lumia 535 Dual Sim, I hate the second sim icon in the top bar as I don't have a second sim active. I have been reading this forum for tutorials to flash my Lumia 535. (Just Read: http://forum.xda-developers.com/show....php?t=2515453)
I was wondering if it was possible to flash it with a single sim firmware (Rm-1091) so that the second sim icon disappears without losing any functionality. If so, can someone help me as when I type my product code in navifirm, it gives only one firmware.
Moreover, whenever I restart my Lumia, a persian keyboard is automatically added, any way to fix that?
I tried Hard resetting it but when it resets, the default language is Slovensky. I dont know why that is. I have to change it to English (United States) but speech has English (United Kingdom) by default.
Help appreciated!
Inscription à :
Articles (Atom)