# Question
Title: Lg G3 random reboots while it is connected to wifi or data connection
As soon as I toggle wifi or data , my LG G3 is getting restarted . I tried factory reset I tried different rom (everything lolipop 5.0) I restored to a working backup I had about 3 months before. The problem is not going.

EDIT : attaching logs from CATLOG

```
   09-11 09:06:22.110 D/WearableBluetooth( 6796):   at com.google.android.gsf.f.c(SourceFile:107)
    09-11 09:06:22.110 D/WearableBluetooth( 6796):  at com.google.android.gsf.f.a(SourceFile:121)
    09-11 09:06:22.110 D/WearableBluetooth( 6796):  at com.google.android.gsf.f.a(SourceFile:216)
    09-11 09:06:22.110 D/WearableBluetooth( 6796):  at com.google.android.gms.common.b.m.a(SourceFile:336)
    09-11 09:06:22.110 D/WearableBluetooth( 6796):  at com.google.android.gms.common.b.g.a(SourceFile:231)
    09-11 09:06:22.110 D/WearableBluetooth( 6796):  at com.google.android.gms.common.b.e.c(SourceFile:200)
    09-11 09:06:22.110 D/WearableBluetooth( 6796):  at com.google.android.gms.common.b.e.d(SourceFile:211)
    09-11 09:06:22.110 D/WearableBluetooth( 6796):  at com.google.android.gms.wearable.node.eg.e(SourceFile:1919)
    09-11 09:06:22.110 D/WearableBluetooth( 6796):  at com.google.android.gms.wearable.node.eg.a(SourceFile:1771)
    09-11 09:06:22.110 D/WearableBluetooth( 6796):  at com.google.android.gms.wearable.node.eg.a(SourceFile:747)
    09-11 09:06:22.110 D/WearableBluetooth( 6796):  at com.google.android.gms.wearable.node.eg.a(SourceFile:707)
    09-11 09:06:22.110 D/WearableBluetooth( 6796):  at com.google.android.gms.wearable.node.gb.e(SourceFile:233)
    09-11 09:06:22.110 D/WearableBluetooth( 6796):  at com.google.android.gms.wearable.node.gb.a(SourceFile:185)
    09-11 09:06:22.110 D/WearableBluetooth( 6796):  at com.google.android.gms.wearable.node.gb.a(SourceFile:169)
    09-11 09:06:22.110 D/WearableBluetooth( 6796):  at com.google.android.gms.wearable.node.hl.b(SourceFile:420)
    09-11 09:06:22.110 D/WearableBluetooth( 6796):  at com.google.android.gms.wearable.node.hl.a(SourceFile:245)
    09-11 09:06:22.110 D/WearableBluetooth( 6796):  at com.google.android.gms.wearable.node.bluetooth.d.run(SourceFile:112)
    09-11 09:06:22.110 W/WearableConn( 6796): Unexpected runtime exception, error: attempting to read gservices without permission: Neither user 10023 nor current process has com.google.android.providers.gsf.permission.READ_GSERVICES.
    09-11 09:06:22.110 E/AndroidRuntime( 6796): FATAL EXCEPTION: WearableAppLogger
    09-11 09:06:22.110 E/AndroidRuntime( 6796): Process: com.google.android.gms.wearable, PID: 6796
    09-11 09:06:22.110 E/AndroidRuntime( 6796): java.lang.RuntimeException: Package manager has died
    09-11 09:06:22.110 E/AndroidRuntime( 6796):     at android.app.ApplicationPackageManager.getPackageInfo(ApplicationPackageManager.java:112)
    09-11 09:06:22.110 E/AndroidRuntime( 6796):     at com.google.android.gms.playlog.b.<init>(SourceFile:237)
    09-11 09:06:22.110 E/AndroidRuntime( 6796):     at com.google.android.gms.playlog.a.<init>(SourceFile:56)
    09-11 09:06:22.110 E/AndroidRuntime( 6796):     at com.google.android.gms.playlog.a.<init>(SourceFile:39)
    09-11 09:06:22.110 E/AndroidRuntime( 6796):     at com.google.android.gms.playlog.a.<init>(SourceFile:35)
    09-11 09:06:22.110 E/AndroidRuntime( 6796):     at com.google.android.gms.wearable.d.c.handleMessage(SourceFile:91)
    09-11 09:06:22.110 E/AndroidRuntime( 6796):     at android.os.Handler.dispatchMessage(Handler.java:102)
    09-11 09:06:22.110 E/AndroidRuntime( 6796):     at android.os.Looper.loop(Looper.java:135)
    09-11 09:06:22.110 E/AndroidRuntime( 6796):     at android.os.HandlerThread.run(HandlerThread.java:61)
    09-11 09:06:22.110 E/AndroidRuntime( 6796): Caused by: android.os.DeadObjectException
    09-11 09:06:22.110 E/AndroidRuntime( 6796):     at android.os.BinderProxy.transactNative(Native Method)
    09-11 09:06:22.110 E/AndroidRuntime( 6796):     at android.os.BinderProxy.transact(Binder.java:496)
    09-11 09:06:22.110 E/AndroidRuntime( 6796):     at android.content.pm.IPackageManager$Stub$Proxy.getPackageInfo(IPackageManager.java:1876)
    09-11 09:06:22.110 E/AndroidRuntime( 6796):     at android.app.ApplicationPackageManager.getPackageInfo(ApplicationPackageManager.java:107)
    09-11 09:06:22.110 E/AndroidRuntime( 6796):     ... 8 more
    09-11 09:06:22.111 E/wearable( 6796): Unexpected exception in reader or writer:
    09-11 09:06:22.111 E/wearable( 6796): java.lang.SecurityException: attempting to read gservices without permission: Neither user 10023 nor current process has com.google.android.providers.gsf.permission.READ_GSERVICES.
    09-11 09:06:22.111 E/wearable( 6796):   at android.app.ContextImpl.enforce(ContextImpl.java:1943)
    09-11 09:06:22.111 E/wearable( 6796):   at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1972)
    09-11 09:06:22.111 E/wearable( 6796):   at android.content.ContextWrapper.enforceCallingOrSelfPermission(ContextWrapper.java:606)
    09-11 09:06:22.111 E/wearable( 6796):   at com.google.android.gsf.f.c(SourceFile:107)
    09-11 09:06:22.111 E/wearable( 6796):   at com.google.android.gsf.f.a(SourceFile:121)
    09-11 09:06:22.111 E/wearable( 6796):   at com.google.android.gsf.f.a(SourceFile:216)
    09-11 09:06:22.111 E/wearable( 6796):   at com.google.android.gms.common.b.m.a(SourceFile:336)
    09-11 09:06:22.111 E/wearable( 6796):   at com.google.android.gms.common.b.g.a(SourceFile:231)
    09-11 09:06:22.111 E/wearable( 6796):   at com.google.android.gms.common.b.e.c(SourceFile:200)
    09-11 09:06:22.111 E/wearable( 6796):   at com.google.android.gms.wearable.node.ho.a(SourceFile:807)
    09-11 09:06:22.111 E/wearable( 6796):   at com.google.android.gms.wearable.node.hr.a(SourceFile:168)
    09-11 09:06:22.111 E/wearable( 6796):   at com.google.android.gms.wearable.node.fn.a(SourceFile:234)
    09-11 09:06:22.111 E/wearable( 6796):   at com.google.android.gms.wearable.node.fn.c(SourceFile:142)
    09-11 09:06:22.111 E/wearable( 6796):   at com.google.android.gms.wearable.node.fn.call(SourceFile:33)
    09-11 09:06:22.111 E/wearable( 6796):   at com.google.android.gms.wearable.node.hm.a(SourceFile:548)
    09-11 09:06:22.111 E/wearable( 6796):   at com.google.android.gms.wearable.node.hm.call(SourceFile:532)
    09-11 09:06:22.111 E/wearable( 6796):   at java.util.concurrent.FutureTask.run(FutureTask.java:237)
    09-11 09:06:22.111 E/wearable( 6796):   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
    09-11 09:06:22.111 E/wearable( 6796):   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
    09-11 09:06:22.111 E/wearable( 6796):   at java.lang.Thread.run(Thread.java:818)
    09-11 09:06:22.118 E/AndroidRuntime( 6796): Error reporting crash
    09-11 09:06:22.118 E/AndroidRuntime( 6796): android.os.DeadObjectException
    09-11 09:06:22.118 E/AndroidRuntime( 6796):     at android.os.BinderProxy.transactNative(Native Method)
    09-11 09:06:22.118 E/AndroidRuntime( 6796):     at android.os.BinderProxy.transact(Binder.java:496)
    09-11 09:06:22.118 E/AndroidRuntime( 6796):     at android.app.ActivityManagerProxy.handleApplicationCrash(ActivityManagerNative.java:4225)
    09-11 09:06:22.118 E/AndroidRuntime( 6796):     at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:92)
    09-11 09:06:22.118 E/AndroidRuntime( 6796):     at com.google.android.gms.common.app.d.uncaughtException(SourceFile:54)
    09-11 09:06:22.118 E/AndroidRuntime( 6796):     at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
    09-11 09:06:22.118 E/AndroidRuntime( 6796):     at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
    09-11 09:06:22.118 I/Process ( 6796): Sending signal. PID: 6796 SIG: 9
    09-11 09:06:22.123 I/ThermalEngine(  331): Sensor:tsens_tz_sensor8:69000 mC
    09-11 09:06:22.123 I/ThermalEngine(  331): Sensor:tsens_tz_sensor7:74000 mC
    09-11 09:06:22.123 I/ThermalEngine(  331): Sensor:tsens_tz_sensor6:70000 mC
    09-11 09:06:22.123 I/ThermalEngine(  331): Sensor:tsens_tz_sensor5:73000 mC
    09-11 09:06:22.188 I/ThermalEngine(  331): Sensor:tsens_tz_sensor8:69000 mC
    09-11 09:06:22.188 I/ThermalEngine(  331): Sensor:tsens_tz_sensor7:75000 mC
    09-11 09:06:22.188 I/ThermalEngine(  331): Sensor:tsens_tz_sensor6:70000 mC
    09-11 09:06:22.188 I/ThermalEngine(  331): Sensor:tsens_tz_sensor5:71000 mC
    09-11 09:06:22.253 I/ThermalEngine(  331): Sensor:tsens_tz_sensor8:69000 mC
    09-11 09:06:22.253 I/ThermalEngine(  331): Sensor:tsens_tz_sensor7:72000 mC
    09-11 09:06:22.253 I/ThermalEngine(  331): Sensor:tsens_tz_sensor6:69000 mC
    09-11 09:06:22.253 I/ThermalEngine(  331): Sensor:tsens_tz_sensor5:70000 mC
    09-11 09:06:22.319 I/ThermalEngine(  331): Sensor:tsens_tz_sensor8:75000 mC
    09-11 09:06:22.319 I/ThermalEngine(  331): Sensor:tsens_tz_sensor7:70000 mC
    09-11 09:06:22.319 I/ThermalEngine(  331): Sensor:tsens_tz_sensor6:70000 mC
    09-11 09:06:22.319 I/ThermalEngine(  331): Sensor:tsens_tz_sensor5:73000 mC
    09-11 09:06:22.337 E/MusicWearableListener(  354): GoogleApiClient suspended: 1
    09-11 09:06:22.384 I/ThermalEngine(  331): Sensor:tsens_tz_sensor8:73000 mC
    09-11 09:06:22.384 I/ThermalEngine(  331): Sensor:tsens_tz_sensor7:70000 mC
    09-11 09:06:22.384 I/ThermalEngine(  331): Sensor:tsens_tz_sensor6:74000 mC
    09-11 09:06:22.384 I/ThermalEngine(  331): Sensor:tsens_tz_sensor5:76000 mC
    09-11 09:06:22.384 I/ThermalEngine(  331): ACTION: CPU - Setting CPU[0] to 2726400
    09-11 09:06:22.384 I/ThermalEngine(  331): ACTION: CPU - Setting CPU[1] to 2726400
    09-11 09:06:22.384 I/ThermalEngine(  331): ACTION: CPU - Setting CPU[2] to 2726400
    09-11 09:06:22.384 I/ThermalEngine(  331): ACTION: CPU - Setting CPU[3] to 2726400
    09-11 09:06:22.422 D/libEGL  ( 3739): loaded /vendor/lib/egl/libEGL_adreno.so
    09-11 09:06:22.424 D/libEGL  ( 3739): loaded /vendor/lib/egl/libGLESv1_CM_adreno.so
    09-11 09:06:22.427 E/BufferQueueProducer(  292): [StatusBar] dequeueBuffer: BufferQueue has been abandoned
    09-11 09:06:22.427 W/Adreno-EGLSUB( 5737): <DequeueBuffer:720>: dequeue native buffer fail: No such device, buffer=0x0, handle=0x0
    09-11 09:06:22.427 E/BufferQueueProducer(  292): [StatusBar] dequeueBuffer: BufferQueue has been abandoned
    09-11 09:06:22.427 W/Adreno-EGLSUB( 5737): <DequeueBuffer:720>: dequeue native buffer fail: No such device, buffer=0x0, handle=0x0
    09-11 09:06:22.427 W/Adreno-EGL( 5737): <qeglDrvAPI_eglSwapBuffers:3702>: EGL_BAD_SURFACE
    09-11 09:06:22.427 W/OpenGLRenderer( 5737): swapBuffers encountered EGL_BAD_SURFACE on 0xaed29140, halting rendering...
    09-11 09:06:22.441 D/libEGL  ( 3739): loaded /vendor/lib/egl/libGLESv2_adreno.so
    09-11 09:06:22.449 I/ThermalEngine(  331): Sensor:tsens_tz_sensor8:74000 mC
    09-11 09:06:22.449 I/ThermalEngine(  331): Sensor:tsens_tz_sensor7:70000 mC
    09-11 09:06:22.449 I/ThermalEngine(  331): Sensor:tsens_tz_sensor6:72000 mC
    09-11 09:06:22.449 I/ThermalEngine(  331): Sensor:tsens_tz_sensor5:73000 mC
    09-11 09:06:22.449 I/ThermalEngine(  331): ACTION: CPU - Setting CPU[0] to 2880000
    09-11 09:06:22.449 I/ThermalEngine(  331): ACTION: CPU - Setting CPU[1] to 2880000
    09-11 09:06:22.449 I/ThermalEngine(  331): ACTION: CPU - Setting CPU[2] to 2880000
    09-11 09:06:22.449 I/ThermalEngine(  331): ACTION: CPU - Setting CPU[3] to 2880000
    09-11 09:06:22.450 I/Adreno-EGL( 3739): <qeglDrvAPI_eglInitialize:410>: EGL 1.4 QUALCOMM build: Nondeterministic_AU_msm8974_LA.BF.1.1.1_RB1__release_AU ()
    09-11 09:06:22.450 I/Adreno-EGL( 3739): OpenGL ES Shader Compiler Version: E031.25.03.00
    09-11 09:06:22.450 I/Adreno-EGL( 3739): Build Date: 12/11/14 Thu
    09-11 09:06:22.450 I/Adreno-EGL( 3739): Local Branch: mybranch6275889
    09-11 09:06:22.450 I/Adreno-EGL( 3739): Remote Branch: quic/LA.BF.1.1_rb1.16
    09-11 09:06:22.450 I/Adreno-EGL( 3739): Local Patches: NONE
    09-11 09:06:22.450 I/Adreno-EGL( 3739): Reconstruct Branch: NOTHING
    09-11 09:06:22.473 D/AndroidRuntime( 6138): Shutting down VM
    09-11 09:06:22.480 E/AndroidRuntime( 6138): FATAL EXCEPTION: main
    09-11 09:06:22.480 E/AndroidRuntime( 6138): Process: com.android.phone, PID: 6138
    09-11 09:06:22.480 E/AndroidRuntime( 6138): java.lang.RuntimeException: android.os.DeadObjectException
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at android.net.TrafficStats.getMobileIfaces(TrafficStats.java:624)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at android.net.TrafficStats.getMobileTcpTxPackets(TrafficStats.java:368)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at com.android.internal.telephony.dataconnection.DcTrackerBase$TxRxSum.updateTxRxSum(DcTrackerBase.java:498)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at com.android.internal.telephony.dataconnection.DcTrackerBase.updateDataActivity(DcTrackerBase.java:1538)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at com.android.internal.telephony.dataconnection.DcTrackerBase$3.run(DcTrackerBase.java:375)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at android.os.Handler.handleCallback(Handler.java:739)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at android.os.Handler.dispatchMessage(Handler.java:95)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at android.os.Looper.loop(Looper.java:135)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at android.app.ActivityThread.main(ActivityThread.java:5374)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at java.lang.reflect.Method.invoke(Native Method)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at java.lang.reflect.Method.invoke(Method.java:372)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:911)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
    09-11 09:06:22.480 E/AndroidRuntime( 6138): Caused by: android.os.DeadObjectException
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at android.os.BinderProxy.transactNative(Native Method)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at android.os.BinderProxy.transact(Binder.java:496)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at android.net.INetworkStatsService$Stub$Proxy.getMobileIfaces(INetworkStatsService.java:239)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at android.net.TrafficStats.getMobileIfaces(TrafficStats.java:622)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     ... 12 more
    09-11 09:06:22.480 E/AndroidRuntime( 6138): Error reporting crash
    09-11 09:06:22.480 E/AndroidRuntime( 6138): android.os.DeadObjectException
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at android.os.BinderProxy.transactNative(Native Method)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at android.os.BinderProxy.transact(Binder.java:496)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at android.app.ActivityManagerProxy.handleApplicationCrash(ActivityManagerNative.java:4225)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:92)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
    09-11 09:06:22.480 E/AndroidRuntime( 6138):     at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
    09-11 09:06:22.480 I/Process ( 6138): Sending signal. PID: 6138 SIG: 9
    09-11 09:06:22.494 I/ServiceManager(  290): service 'simphonebook' died
    09-11 09:06:22.494 I/ServiceManager(  290): service 'iphonesubinfo' died
    09-11 09:06:22.494 I/ServiceManager(  290): service 'isms' died
    09-11 09:06:22.494 I/ServiceManager(  290): service 'phone' died
    09-11 09:06:22.494 I/ServiceManager(  290): service 'sip' died
    09-11 09:06:22.494 I/ServiceManager(  290): service 'isub' died
    09-11 09:06:22.514 I/ThermalEngine(  331): Sensor:tsens_tz_sensor8:75000 mC
    09-11 09:06:22.514 I/ThermalEngine(  331): Sensor:tsens_tz_sensor7:71000 mC
    09-11 09:06:22.514 I/ThermalEngine(  331): Sensor:tsens_tz_sensor6:72000 mC
    09-11 09:06:22.514 I/ThermalEngine(  331): Sensor:tsens_tz_sensor5:75000 mC
    09-11 09:06:22.534 E/BootAnimation( 3739): couldn't find audio_conf.txt
    09-11 09:06:22.545 W/BootAnimation( 3739): Audio service is not initiated.
    09-11 09:06:22.551 E/DisplayManager( 8395): Could not get display information from display manager.
    09-11 09:06:22.551 E/DisplayManager( 8395): android.os.DeadObjectException
    09-11 09:06:22.551 E/DisplayManager( 8395):     at android.os.BinderProxy.transactNative(Native Method)
    09-11 09:06:22.551 E/DisplayManager( 8395):     at android.os.BinderProxy.transact(Binder.java:496)
    09-11 09:06:22.551 E/DisplayManager( 8395):     at android.hardware.display.IDisplayManager$Stub$Proxy.getDisplayInfo(IDisplayManager.java:254)
    09-11 09:06:22.551 E/DisplayManager( 8395):     at android.hardware.display.DisplayManagerGlobal.getDisplayInfo(DisplayManagerGlobal.java:119)
    09-11 09:06:22.551 E/DisplayManager( 8395):     at android.view.Display.updateDisplayInfoLocked(Display.java:766)
    09-11 09:06:22.551 E/DisplayManager( 8395):     at android.view.Display.getSize(Display.java:451)
    09-11 09:06:22.551 E/DisplayManager( 8395):     at com.facebook.rti.mqtt.common.b.g.d(UserAgent.java:102)
    09-11 09:06:22.551 E/DisplayManager( 8395):     at com.facebook.rti.mqtt.common.b.g.a(UserAgent.java:53)
    09-11 09:06:22.551 E/DisplayManager( 8395):     at com.facebook.rti.mqtt.e.h.a(MqttClient.java:1294)
    09-11 09:06:22.551 E/DisplayManager( 8395):     at com.facebook.rti.mqtt.e.h.a(MqttClient.java:701)
    09-11 09:06:22.551 E/DisplayManager( 8395):     at com.facebook.rti.mqtt.e.h.s(MqttClient.java:854)
    09-11 09:06:22.551 E/DisplayManager( 8395):     at com.facebook.rti.mqtt.e.h.r(MqttClient.java:655)
    09-11 09:06:22.551 E/DisplayManager( 8395):     at com.facebook.rti.mqtt.e.h.q(MqttClient.java:535)
    09-11 09:06:22.551 E/DisplayManager( 8395):     at com.facebook.rti.mqtt.e.h.a(MqttClient.java:89)
    09-11 09:06:22.551 E/DisplayManager( 8395):     at com.facebook.rti.mqtt.e.i.run(MqttClient.java:288)
    09-11 09:06:22.551 E/DisplayManager( 8395):     at java.lang.Thread.run(Thread.java:818)
    09-11 09:06:22.554 E/QCOM PowerHAL( 3739): Failed to acquire lock.
    09-11 09:06:22.580 I/ThermalEngine(  331): Sensor:tsens_tz_sensor8:75000 mC
    09-11 09:06:22.580 I/ThermalEngine(  331): Sensor:tsens_tz_sensor7:70000 mC
    09-11 09:06:22.580 I/ThermalEngine(  331): Sensor:tsens_tz_sensor6:72000 mC
    09-11 09:06:22.580 I/ThermalEngine(  331): Sensor:tsens_tz_sensor5:74000 mC

```

please Help

# Answer
> 1 votes
After long testing and trying out all the custom roms and kernals , I gave the phone to the service center and they found the problem to be with battery due to water damage.

I have no clue why it is so , since The battery was giving me easily 1 day charge. I replaced the battery and now its not getting restarted .

Thanks everyone for the help and suggestions.

---
Tags: wi-fi, 5.0-lollipop, reboot, mobile-data, lg-g3
---


# Question
Title: Flashed wrong recovery on a QTAB with no bootloader or fastboot. What can I do?
Hey guys I was just tinkering, and it was stupid of me not to take a backup of any kind. Anyway, QTAB doesn't have a bootloader or fastboot menu. When I try adb reboot bootloader or fastboot, it goes to back to recovery. Now the problem with recovery is I cant use it. Home button makes selection go up and power key does nothing.. and cwm is not touch supported.

I have the stock system.img but no stock recovery. I could try another twrp recovery. But that's what i want to know how to do it.

I've googled and tried various stuff. no luck

# Answer
> 0 votes
Without knowing the exact device model you have I can only tell you to go to the **website and download the appropriate firmware**. Get the right file depending on your model number and read the instructions for flashing the stock firmware. This will give you a complete stock tablet back (system.img / recovery.img / boot.img etc).

The instructions seem pretty straight forward even though the procedure is a little bit weird...anyway:

Software needed: **PhoenixSuit**

> Step 1 :Open PhoenixSuit application
>
> Step 2: Choose firmware tab
>
> Step 3: Select the image file from your computer
>
> Step 4:Unplug the qtab + Click upgrade
>
> You will see this message : "Upgrade Firmware to Device?" Press Yes
>
> Then you will see this message "No Device attached!" - Press Ok
>
> And press ok for the third message also
>
> 1. Now long press your power button for atleast 10 seconds
> 2. Press one hardware key except the power button and do not release
> 3. Connect the device to the computer
> 4. Click power key for about 10 times
> 5. Release all keys and the device will upgrade
>
> If it didn't work, repeat these 5 steps Instructions taken from **here**.

---
Tags: recovery-mode, fastboot, bootloader
---


title: Fail in restoring WhatsApp chats

text:
# Question
Title: Fail in restoring WhatsApp chats
I followed the steps below to restore WhatsApp chats:

1. On my old phone, I backed up my chats to an SD card
2. Insert the SD card into the new phone
3. Moved the whole WhatsApp folder to the new phone from the SD card
4. Install WhatsApp on a new phone and register and then it said there is a backup file found, asked if I would like to restore it.
5. I clicked restore, so WhatsApp processes.... for around 1-2 minutes, WhatsApp quits itself, prompt "Unfortunately, WhatsApp has stopped"

The WhatsApp version on both my old and new phone is the same.

So how can I restore my chat history?

# Answer
> 5 votes
Try this, from the Whatsapp FAQ.

> To restore from a backup, follow these steps:
>
> 1. Uninstall WhatsApp.
> 2. Decide which backup file you want to restore.
> 3. Rename that file from "msgstore-YYYY-MM-DD.1.db.crypt" to "msgstore.db.crypt"
> 4. Install WhatsApp
> 5. When asked to restore, tap \[Restore\]

# Answer
> 4 votes
When you put the backup file onto your new phone, make sure you put it in the WhatsApp folder that is located *on* your *phone* and not the SD card in your new phone. There are 2 WhatsApp folders, one on your phone and one on the SD card, so make sure you put the backup onto your *new phone* because I kept putting it in the SD card folder and it didn't work.

# Answer
> 1 votes
The file name in the `Whatsapp/Database/` folder should be `msgstore.db.crypt`. If it has a date, etc. then rename it to `msgstore.db.crypt` only. In my case, it was `msgstore.db.crypt8`. I rename it `msgstore.db.crypt` and it worked.

# Answer
> 0 votes
Apparently, there are issues with the restore when you use a different phone number. I could not completely figure out what caused the problems in my case, but I was finally able to restore my data when I used the same cell phone number for activation (I have a dual SIM phone) as I used on my old phone.

So, I guess the bottom line is:

1. Use the same Google account ("@gmail" vs "@googlemail")
2. Use the same cell phone number

---
Tags: whatsapp-messenger, restore
---


title: Authorize adb in recovery mode

text:
# Question
Title: Authorize adb in recovery mode
I need to authorize `adb` in recovery mode on my Galaxy S3 I9300 (international edition) in order to make a backup of my files.

The problem is that I cannot boot the cyanogenmod which is install on the phone and I don't know why.

Currently I have ClockworkMod Recovery 6.0.4.3 and when I try `adb pull /sdcard/DCIM` I get the following message:

`error: device unauthorized. Please check the confirmation dialog on your device.`

Please help me, I have a lot of valuable information on my phone which I need to recover.

# Answer
> 1 votes
In order to pull the files with ADB from my phone I flashed the latest TWRP recovery with ODIN (3.0.7, not the latest), then by default you have an authorized ADB devise in recovery, so I just entered

`adb pull /sdcard/*`

and waited for the files to transfer.

---
Tags: cyanogenmod, adb
---


# Question
Title: Google+ not signing in in Clash of Clans
I have tried to install the last update of Clash of Clans, it always failed, so I uninstalled it and installed it again. Succeeded.

Now I have to login to my village, I used Google+ before, so after I started the game it loaded then there's little G+ Sign in button, I tapped it, it loaded and then there was a blue button to sign in, I tapped it and it loaded for a while and then restarted the game

Now whenever I click sign in it shows that loading icon and then nothing happens, the game continues to show the tutorial

I have tried to clear Google Services Framework/Play Services/Play all with no luck

I have also tried to clear Clash of clans data without luck too

I have tried to continue the tutorial and creating new village and then signing in but meh

I am now very frustrated I want to restore my kingdom in Clash of Clans

Pleaee help.

# Answer
Well the problem was a bit weird

Actually the problem was that there was a newer version of the game, they difference was in the minor release number

Neither Google Play or the game itself prompted me for the update, I downloaded the APK fro. third-party websites and sideloaded it and now it works pretty good

Also if you're are in the one of the blocked countries by Google, try some VPN app
> 0 votes

---
Tags: google
---


# Question
Title: chrome://downloads/ does not available in Google Chrome for Android
I have a Samsung Galaxy Tab s2 and Google Chrome for Android is compatible with my Tab, so I installed it.

I clicked on a link to download a video file. Google chrome showed a toast message that the download has been started.

However, after this toast, I can't find where chrome downloaded the file.

I query `chrome://downloads` , but the browser displays `"This web page is not available "`

# Answer
> 3 votes
There's a separate **Downloads** app, which shows a list of downloads from all apps. Downloads are saved in the "Downloads" directory in the SD card, which means that downloaded videos show up in the "Downloads" album in **Gallery**.

# Answer
> -2 votes
On Android 4.4, you can access the download history in the App titled “My files.”

---
Tags: internal-storage, chrome-for-android
---


# Question
Title: Pull down notifications from the center of the screen in Android 5.1 on Sony Xperia
On my previous phone (sorry, I didn't set it up myself, so I can't give any more details than "some kind of Android") I was able to pull down the notifications by swiping down from the center of the screen (or anywhere really). On my new Sony Xperia running Android 5.1, the same can only be accomplished by swiping down from the very top of the screen, which is quite a stretch to make.

Is there a way to change this? I couldn't find anything in the settings.

# Answer
> 1 votes
If you are using the stock launcher, chances are there aren't settings for that. I know that with a custom launcher like Nova Launcher, there are gestures that you can set up to do what you are looking for.

Nova Launcher on Google Play

Nova Launcher Prime on Google Play

---
Tags: 5.1-lollipop, sony-xperia, notification-bar
---


# Question
Title: Why is 'no connection' error appearing while accessing Google Play store?
I have this common, annoying problem while trying to access Google Play Store from my phone. It just shows 'no connection', and won't load, even though the internet access is surely working. The suspected cause is a synchronization error of my Google account, likely due to incorrect time settings (it's reported while running WhatsApp for example). Here's what I've done so far:

1. Set the time automatically
2. Manually set the time, without using the network
3. Clearing cache of Google Play store application
4. Reinstalling Google Play store manually using .apk
5. Logging out and back in with my Google account
6. Rooting the phone and using ClockSync app to set the time
7. Doing a factory reset of my device
8. Making sure Freedom application is not installed

I'm slowly running out of ideas...if anyone has the smallest hint, I'll be really grateful. I'm using Android 4.2.2.

# Answer
> 1 votes
*Try clearing the app data and cache of Google service framework.*

1. Go to Settings
2. Apps
3. Scroll to ALL
4. Google Services Framework
5. Clear data and cache
6. Disable and Enable back
7. Reboot phone

---
Tags: google-play-store, sync, 4.2-jelly-bean, google, clock
---


# Question
Title: Can an app keep onto its root access permissions after the phone is turned off?
My question is plain and simple. Can an app keep onto its root access permissions after the phone is turned off? Is there a way an app with root access can keep this permission and start running with this permission without asking for it again once the device is turned back on?

For all I know, it can not, but it can be set to "grant root access whenever it demands" by superuser app.

The reason I ask this question is: I talked to the support service of the spy apps such as mSpy or FlexiSpy (apps that fetch your every single info but requires root access) which accept their app would not survive a factory reset but insist that their app would keep working properly after a reboot.

# Answer
> 0 votes
Apps like SuperSU will remember your decision regarding root access to an app and will give that reply each time the app asks, unless you specify otherwise in the settings. Make sure your app starts after the device boots.

If your application needs root permissions during boot (not after the device has booted) you'll need to enable "su during boot" (SuperSU)

---
Tags: root-access, superuser
---


# Question
Title: How do I get my mobile data to work again, after the new Android 5.1 update?
I am having an issue with mobile data no longer working. Mobile data *was* working the day after updating to Android 5.1 on my Nexus 5. But now (1 day later) it is not connecting to mobile data. It just has the cellular icon, with an exclamation point.

I've tried toggling data, airplane mode, WiFi, rebooting, factory reset, and resetting the SIM card. The last thing I tried is to call my carrier and go through 2 hours of troubleshooting. They said the only thing left for them to do is send me a new SIM card. It makes no sense.

Everything else works fine. I can make and receive calls. Texting works. And WiFi works as well. Just not the mobile data. The weird thing is that it stopped working on the first day of my mobile data cycle. But the carrier swears that all is well on their side.

# Answer
> 0 votes
* Try a different sim card.
* Check if the `APN settings` are right.
* Check for a bug fix `OTA update`.

If the steps above didn't help please leave a comment.

# Answer
> 0 votes
I've had a similar experience: I need to select settings, then under 'Wireless & networks' hit the 'More' option, then select Mobile Networks, then enable Data Roaming, and then switch it off again. And bang, my mobile data works again. Somewhat similar to hopping on one leg and chanting.

The problem that remains is that every time I walk out of range of a WiFi network my phone is connected to, I loose mobile data and have to do this routine again. It's getting a little tiring :(

# Answer
> 0 votes
Mine won't connect to mobile data when I toggle it on, but if I leave it toggled on and reboot, it connects on reboot.

# Answer
> 0 votes
After the 5.1 upgrade in my phone it wouldn't connect to my home wifi. I tried several of the fixes on this site and none worked. When I tried to connect it would ask for my password but when I put my password in the connect was still greyed out. After more than a few tries, the light dawned. It didn't want my Century Link password, it wanted the **key passphrase on the bottom of the wifi router.** That worked. I hope this works for you.

Johnny Blaha

---
Tags: nexus-5, stock-android, mobile-data, 5.1-lollipop
---


# Question
Title: What it takes to update nightly CM12.1 in TWRP?
I want to install the latest cm12.1 nightly update, but I am worried about doing something wrong.

The .zip file is already downloaded. My recovery mode is TWRP and I would like to know if I need to wipe, clear, or do something like that in TWRP options.

Thanks!

# Answer
If you're already using a Cyanogenmod Build from the same developer then you can just go ahead and install the update without wiping anything.

If you're using a stock (based) rom on your device and you want to install cyanogenmod for the first time then you should wipe /system, /data/, /cache, /dalvik cache. This will be a clean install, so all your data may get lost. As always adviced: Make a backup (in TWRP) first so you're on the safe side. If something goes wrong you don't have to worry and just restore your backup without any hassle. Furthermore you can save your existing application + app data with Titanium Backup from the Playstore and restore them when the installation has finished :)
> 2 votes

---
Tags: cyanogenmod, updates, twrp
---


title: Connecting With pc via USB

text:
# Question
Title: Connecting With pc via USB
I use Symphony w71.Though it would connect with PC but after root I find no option to connect with PC.It charge but not connect with computer.My phone debug option is on also enabling Root permission.What should I do now??

# Answer
> 1 votes
Once you connect your phone to your PC, unlock your phone and follow these steps

Pull down the **Status/Notification bar**. You must be able to see the type of connection. Press on it.

You must be able to see several options like **Media device(MTP)**, **Camera(PTP)**, **Charge only** and **Mass storage(UMS)**.

For your requirements, I suggest you choose the **MTP** connection. The UMS would just mount your SD card as an external device and ignore the internal storage.

You must be able to view your phone being connected to your PC by now and I would suggest you keep your screen unlocked till you disconnect your phone from the PC

# Answer
> 0 votes
Maybe you should only use an other usb-cable. Many cables have the middle two pins (which are for the data) in a position were it does not connect to pc, but the both pins left and right(which are for the power) are connected. So your device is loading but your pc says there is no mobile phone connected. Sorry but in my opinion many manufacturer do this with purpose :/ Hope this helps you :)

---
Tags: usb
---


# Question
Title: Where are the captions stored for images that are sent or recieved in WhatsApp?
When sending images in WhatsApp, there is an option to add caption to it. This caption is visible on image, at the receiving end, but when this image is copied or forwarded, only image is sent? (although the selection shows image caption also selected)

Is the image caption not in the image file itself Or its stored separately somewhere locally and so that part is dropped?

How can I forward the image along with its caption?

# Answer
This is a bug in Whatsapp. It should send both image and caption.

It's present both in Android and iPhone versions. Doesn't matter if you user the FORWARD ("Arrow/Forward") or the SHARE feature, both loose the original caption.

You and everyone with this problem can (and should) send a bug report thru the app by accessing the Settings panel \> help \> Contact us.
> 3 votes

# Answer
> "but when this image is copied or forwarded, only image is sent":

Well, This is not true, as selected image along with conversation can be forwarded from Conversation/Chat.

**May be your WhatsApp App version is bit old? I tested this on mine(App version:2.11.432, Running on Android 4.2)**

To Answer your specific question: Below can be steps

1. Select Image along with caption that you wants to forward.
2. Choose "Arrow/Forward" Button. This will open "Select contact" screen.
3. Click "OK" when asked about forwarding to selected contact.

And this should forward image from conversation/chat along with Image's caption to intended recipient.
> 0 votes

# Answer
When you re-forward follow this step:

Instead of forwarding the message directly from WhatsApp (using right Arrow on top right) use Share button -\> Choose WhatsApp and add the caption again!
> 0 votes

# Answer
This is the workaround I found: instead of *forwarding* select *share*, -\> then select Whatsapp -\> select contact or group -\> type caption again on image... too much effort but will work for emergencies.

Links to similar issues reported

How can I send WhatsApp's image captions to email with images?

http://www.androidpit.com/app/com.whatsapp/problem-in-forwarding-picture-messages-with-some-text-in-it
> -1 votes

---
Tags: applications, whatsapp-messenger, images, data-transfer
---


title: Package Name Info for Android Apps

text:
# Question
Title: Package Name Info for Android Apps
Hi I would like to know if there exists a website where in once you enter the name of the android app gives you all the related info of that particular app. I am especially interested in the `Package Name` of the app.

I know about the site `Droid Icon`(Link) and also the app called Package Name viewer and have tried both out.

The App `package name viewer` works excellently but only returns the info of the apps installed on my device and not all. So for the information I need I have to install the app first. Which is a tedious job if we need to do it for 10 or more apps.

Droid Icon web site gives numerous package names which are at times not correct.

So I would like to know if there exists another source for my specific requirement.( i.e package names).

# Answer
> 0 votes
Picking up my own example from above comment on the question: Simply use your Google-Fu. Here's mine:

intitle:"quick dial" site:play.google.com

Hits: 197. Now try that for 50 or 100 apps. For most of them, the result list will be shorter – if the devs thought of more unique names:

intitle:"secure backup" site:play.google.com

Hits: 3, Exact hits: 1 (easy to tell by the title). Hover the URL: `com.sentinal`.

\[intitle:"stripsearch" site:play.google.com\] Yuck. Got me. Need to improve my Google-Fu:

intitle:"stripsearch" site:play.google.com inurl:"store/apps": 1 hit. Exact. Correct.

Repeating #1 with the new foo: Much better, just 196 hits (oops).

---

I just notice I forgot the explanation:

* `intitle`: What appears as `<TITLE>` in your browser window's title bar. With *Google Play Store*, this includes the *App name* – so this is where we put our search term
* `site`: Restrict the search to a specific site. In our case, that's the *Google Play Store* – where most apps are listed. Same could be done with e.g. *Aptoide* (e.g. `intitle:"quick dial" site:store.aptoide.com` returns 3 hits) – but wouldn't work with *F-Droid* (the `<TITLE>` with them is always 'F-Droid', no matter what)
* `inurl`: a string being part of the URL. I used this in my example to fix my search to apps – without that, results included *Google Books*, *Google Music*, and probably even more (everything sold via *Google Play Store*)

---
Tags: applications
---


title: Mp3 not showing in library

text:
# Question
Title: Mp3 not showing in library
I spent an hour trying to get this to work so I could get some sleep in my noisy hospital bed last night.

I wanted to listen to some noise on loop. I downloaded some waves lapping type music.

It's on my internal SD and is an mp3.

Clicking the file in Astro browser doesn't open the file in a player fully but only a popup preview window. It's in the foreground, doesn't offer many controls and stops playing when the focus is removed.

Searching for the file in all 3 of my players doesn't result in anything, even after a restart. I have also tried a SD card rescan utility from the play store.

Music apps I tried were Fusion, Bubble UPNP and the Samsung Music App. All of which seem to rely on some internal media index. Frustratingly I can't simply browse to the file from inside the apps, I have to search the library.

It should not take an hour and a post to here to figure out how to manually play a simple file, added to my phone in such a way.

It would be great if it were like Windows or osx and allow the user to "Open with... ", and then select the app. I know you can dig in and change this, but it's a more permanent solution for a temporary requirement.

Anyway I must be loosing my mind:)

How can I add this file to my library from within Android or otherwise open this file in a full player to make use of controls like loop etc?

---

Update from a comment on an answer:

It's mp3, and plays in the popup player just fine. Perhaps the tags are corrupted and somehow blocking it from appearing in the library. I tried an mp3 tag utility and it can't see the file in the folder. So perhaps it is corrupt in some way.

# Answer
> 0 votes
As already suggested your files are most likely wrong tagged or not tagged at all.

In order to be recognized by apps relying on meda scanning, mp3 files need to contain at least a valid "title" id(3) tag.

On linux you can check your file with the tool "eyeD3" which can be installed on debian based distris from the package: eyed3

A simple:

> eyeD3 /path/to/mp3/file

should give you all id information.

If there is no title tag you can tag by:

> eyeD3 -t yourtitle /path/to/mp3/file

If you push this file now to your device and perform a reboot it should be recognized by the media scanner.

# Answer
> 1 votes
If it doesn't turn up in the library even after a reboot (which should definitely have triggered the media scanner to add it to the library), the only reason I can think of is some `.nomedia` file being in the path. You can try to analyze that (finding whether there is one), or...

There are media players *not* using the library, mainly for FolderPlay & AudioBooks. Using one of those, you can navigate to that folder from within the app, and play the files. If that doesn't work either, the files might be corrupted or using an unsupported format.

# Answer
> 0 votes
I found an album that android would refuse to recognise, until I renamed the files. I'm guessing android doesn't like the three dots (elipsis):

Original name:

> ...And You Will Know Us By the Trail of Dead - 05 - The Rest Will Follow

New name:

> 05 - The Rest Will Follow

---
Tags: music-player, media-scanner, mp3-player
---


# Question
Title: Does "fastboot flash recovery <recovery-file.img>" command work with any android device?
The command is used to flash a recovery. Do you have to use odin like tools to flash it or you can just use adb?

Thank you

# Answer
First, to clear the confusion, fastboot and adb are two different modes/states. Now to answer your question, it depends whether your phone supports the fastboot protocol (all Android phones support adb, this is not the case for fastboot).

If it so happens that your smartphone is fastboot capable, then the `fastboot flash recovery file.img` command will work.
> 0 votes

---
Tags: adb, rom-flashing, fastboot
---


# Question
Title: Cellular data shutting off when i shut off wifi and vice versa
I bought a motorola moto g gen 3 a few days back and encountered a bug i can't wrap my head around.

First of: this post: Cellular data not working since 5.1 Lollipop flash adresses the same issue but since I created this account today and I lack reputation I cannot answer in that post ... I find this a rather weird designchoice for an answer based website but hey, you guys have your reasons :D hence I have to make this kind of repost :( I am sorry for that. Also for my English, its not my native language.

On the issue: I have android 5.1.1 which came standard on the phone. I set it up to my liking and for a day everything worked fine. I am from Belgium and have a data plan with mobile vikings. I think they use the Base communication lines.

But since I woke up a few days ago I can't get my cellular data to work like it should. When wifi is enabled cellular data is also enabled. But from the second i lose my wifi connection OR is shut it off I ALSO lose my cellular data connection and instantly an exclamationmark pops right up alongside the data icon. Hence it feels like they are somehow connected but set up wrong. It feels as if the purpose is to automaticaly enable cellular date when you lose wifi connection and vise versa but somehow it bugs and works the other way round.

In that other post people suggested to ask my provider about it. Changing phones might have done something on their end but so far i did not get response. The things I tried myself were shutting the phone off and on again, removing and reinserting the simcard, fizzling with options, googling like mad, factory reset and probably something I forgot. All to no avail.

My previous phone was a windowsphone nokia lumia and all worked well there. Because of problems with the battery and my drive to go android again I bought the moto g.

Please dear androiders, help me! I am losing my mind :D

# Answer
I have a Nexus 5 with 5.1.1, and was experiencing the same thing.

It was a bit weird; I think the problem started with the 5.1.1 upgrade, but it's didn't kick in fully as a problem 100% of the time until sometime last week (1st week of September). Prior to that it was an intermittent problem, dropping about quite regularly, but returning pretty quickly.

Anyway, I rooted the phone, and reinstalled 5.1 and it's all working properly now.
> 0 votes

# Answer
I phoned mynprovider and we went over some options. Turns out there is nothing wrong with my phone but my APN settings were set-up erroneously. We went over those options and I set them up accordingly. Quick reboot and problem solved.

So for all you guys with the same symptoms, don't hesitate to call your providers helpdesk to run over your APN settings!
> 0 votes

# Answer
Running Moto G 3rd Gen at 5.1.1. Had all the same issues start the first couple days of September. Not sure what prompted the issue, but we all seemed to have it occur at the same time; is that when 5.1.1 went out?
Searched my carrier support pages for the proper settings and noticed that for "non-carrier devices" (my Moto is unlocked and not sold by them) they have slightly different APN settings. I had to change the APN field. Once I changed that, my data was back. BUT that lasted less than a day before it went back to no data again. Still missing some piece of this puzzle...
> 0 votes

---
Tags: wi-fi, motorola-moto-g, 5.1-lollipop, mobile-data, bugs
---


# Question
Title: Mirroring content from Android device to Television without Chromecast
Besides buying the Google Chromecast HDMI stick, is there a way to mirror the content from an Android KitKat device to a "dumb" (i.e. not "smart") HDMI Television?

Solutions using Roku, Amazon Fire Stick, Blu-Ray players, or other devices are welcome.

The simpler, the better.

# Answer
I personally use Amazon Fire TV and the Amazon Fire Stick and it works fine. The Microsoft Wireless Display Adapter is supposed to work with Android devices as well.

How to use display mirroring on the Fire TV and Stick (from Amazon's website):

> To quickly start display mirroring, on your Amazon Fire TV remote press and hold the Home button and select Mirroring. Then connect your compatible device. Swipe down from the top of the screen to open Quick Settings, and then tap Settings. Tap Display & Sounds, and then tap Display Mirroring.
> 2 votes

---
Tags: 4.4-kitkat, television, screen-mirroring
---


# Question
Title: Samsung S3 only boots into safe mode. Also plays a female voice reading everything on homescreen
Recently, my Samsung S3 GT-19300 somehow went off and immediately restarted itself into safe mode. I assume in safe mode there are limited thing that will function on the phone? But in my case nothing seems to be working. All I hear is a strange female voice reading everything on my phones' desktop.

I have restarted the phone several times following various instruction on how to turn off safe mode but all to no avail, the problems is still persisting. It has a funny icon of a hand telling you to stop.

Do you know of any way to fix this? I’d like to be able to fix this, not minding having to do a factory reset if at all possible.

# Answer
Can you provide a screenshot? Also to deactivate the voice just go to Accessibility and deactivate Talk-back.
> 0 votes

# Answer
Please go into your BIOS settings by completely shutting off your phone, and press power + volume down key. Send a picture of this. You can toggle between settings using volume. Try and press "Continue normal boot" or similar.
> 0 votes

---
Tags: samsung-galaxy-s-3, safe-mode
---


# Question
Title: Handling Notifications - Vibrations / Screen / Tones?
My HTC One seems to vibrate for every damn notification that comes on. When it does this, the screen does not come on and there's no sound. I know how to turn notifications off, but I"m trying to figure out how define when a notification :

a) Turns on the screen so I can see the notification without having to turn the phone on, go to the notifications screeen, etc.

b) Provides a audio notification / tone

c) Does or does NOT vibrate

Personally, I find the vibrate with no sounds and no screen to be the most annoying.

# Answer
> 1 votes
This worked for me on my HTC One M8

First Go to Settings, then go to Accessibility, and click Notification Reminder to Off

http://www.reddit.com/r/htc/comments/2w3op7/htc\_one\_m8\_lollipop\_notification\_constant/

# Answer
> 0 votes
First, make sure you have priority interruptions only. You can change your priorities here.

<sub>(Click image to enlarge)</sub>

You can also disable notifications, so your phone won't buzz.

---
Tags: notifications, htc-one
---


# Question
Title: Does Android continue to run after phone is switched off?
I was wondering about this: it seems that when you set an alarm, even if you switch off your smartphone, on reaching that time the alarm manages to ring.

Is the Android framework still running and hence the Alarm Service is able to detect change in time, or other reason?

# Answer
> 7 votes
There was a question here asking if it is an expected behavior, it has two answers saying not much more as simple yes.

I am going to answer this question as a question of *why* is it so, whether Android is running, and how it works if not.

The answer is: **no**, Android is not running nowhere, nor is Linux underneath him. Wake up on alarm is a hardware feature which was around a long time and was actually very common a time ago. The feature involves hardware. And because of the associated costs, I think, manufacturers started to implement it less and less. There is quite a lot of expensive phones today, which don't have it.

The alarm clock while power off feature has nothing to do with Android or whatever OS is on the phone. Any device today is never quite completely off. There are always few chips powered. No conspiracy here, those chips in question are well documented power chips, without any special spying powers if that is in question. We can say a phone, or other device, is *on* if it's processor is on. That can be woken-up by various events, only one of which is the power button. If you plug a charger to a powered off phone, it will power on, determine what's happened, then it shows a battery charging graphics. There is usually separate boot for each such event. One of such could be a signal from an alarm clock. You have phones which shows such alarms while they boot to special alarm clock mode, and then you have phones which will go through normal boot to show alarm in its alarm App.

But it's not just to send the wake signal. Phones offer multiple alarms, you have timezones, silent modes, and there need to be a way to store the alarm value from an alarm app when you set an alarm time into the clock chip. I don't think it's all such a big deal, especially when a basic clock is usually there somewhere anyway, but it's cheaper without it.

---
Tags: alarm, power-on
---


title: List all activities of an app

text:
# Question
Title: List all activities of an app
I have an Android phone which is *not* rooted.

Is there any way I can obtain/export a list of all installed packages ***with their available activities***?

ADWLauncher has an activity picker in its custom shortcut feature. It lists things like:

```
Calculator
  Calculator(.Calculator)
Camera
  Camera(.Camera)
  Camcorder(.VideoCamera)
  Camera(.Camera_dual)
  Camera(.VideoCamera_dual) ...

```

I have apps which generate a list of installed packages, but how can I get something like this showing all the activities?

# Answer
You can have a look at all Activities of an app by using QuickShortcutMaker app. It's quite a funny app which can make a shortcut to specified activity of any program, so you can even launch those hidden ones.
> 1 votes

# Answer
Install Apex Launcher from the Play Store. Open the Widgets and you can find a widget named **Activities** (with blue Apex Launcher icon). Place the widget in your home screen and open it. You will see the list of all app's activities listed.

Screenshot - Click to enlarge image
> 0 votes

---
Tags: applications
---


title: OneDrive - Android sign-in error

text:
# Question
Title: OneDrive - Android sign-in error
Same error for 2 weeks now: get notification saying sign-in error for one-drive, I try and enter password, says email address or password is wrong, so I reset password, then it goes away for an hour or two, then same error, repeat. Have googled but doesn't seem to be a solution out there - any help here? I would delete it but I like the back up service.

# Answer
Had the same issue. I cleared the app cache and force stopped the app and it all worked again.
> 0 votes

---
Tags: onedrive
---


# Question
Title: replaced screen now having issues :( galaxy s4 i9505
Good afternoon guys and gals please bear with me as i'm new to this forum anywho i've recently replaced my screen on my galaxy s4 after attempting to replace just the shattered glass and failed! went to go power on the phone for the first time with the new screen and everything was great............................................. .................... for about 5 minutes the screen has freaked out big time on the odd occasion will display properly most of the time its just freaking out. Ive managed to do a factory reset using the android device manager and that seemed to help it out for 10 minutes until it returned to freaking out. Could this be software related? As it booted up fine before the freaking out and is still allowing me to use the touch screen as i can hear the phone unlock. Or should i be contacting the person i got the screen from asking for my money back? My phone was completely fine running wise until i had to change over the screen. i hope you guys canhelp me out as im stuck in a rut as to what to do

galaxy s4 i9505 international variant running stock touchwiz

# Answer
Your display issue is almost certainly a bad connection on one of the ribbon cables that connect the display to the circuit board. One of the two cables you had to disconnect didn't get fully seated in the connector, leaving some traces intermittent. Assuming the connector wasn't damaged when you disconnected the old screen, you may be able to restore correct operation by disassembling to the point where you disconnected the screen and digitizer cables, then carefully following instructions to reconnect those ribbons, followed by completing the reassembly.

You should also be able to install the battery and power up the phone to check things before fully reassembling, which will save time if you have to take several tries to get a good connection.
> 0 votes

---
Tags: samsung-galaxy-s-4, screen
---


title: How to update rooted android (nexus 5)

text:
# Question
Title: How to update rooted android (nexus 5)
I have rooted Nexus 5 device with Android 5.1.1. Now system shows updates are available. But on restarting it shows error screen, virtually making it impossible to update.

Is it possible to update rooted android OS, and if yes how (without wiping out any data)?

# Answer
You have to use the Android SDK, specifically the command fastboot, to flash the stock system.img and stock recovery.img. Only flash the boot.img only if a custom kernel has been flashed, if not, this isn't required. With USB Debugging enabled in Settings - Developer Options, you'll need to boot into the bootloader. You'll also need the factory image for the current version of stock you are running.

You'll need to use the commmands:

```
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img

```

Rooting modifies /system, which OTA's will check and fail. Also, any other recovery except for stock recovery will also fail to flash the OTA.
> 1 votes

---
Tags: 5.0-lollipop, root-access, nexus-5, ota-update
---


# Question
Title: Do every Android version store the PIN/passwords at the same file?
I find a *hateful* peculiarity of Android its nagging usual **changes between versions** in the paths for some system files and configuration variables. Even when I assume it is expectable on newborn operating systems.

I have read that the **PIN number** for unlocking the screen is stored (cyphered, I pressume) at `/data/system/password.key` . So, for example, if I do:

```
# rm /data/system/password.key

```

... I will be able to delete it (of course priorly mounting the partition system as read/write, booting via Recovery, connecting via ADB shell, on a rooted device... blah blah blah).

Could this change **work on every version of Android**? Or this storage file is version-dependent?

# Answer
> 2 votes
According to this source

> Android stores this pattern in a special file called password.key in /data/system/. As storing the pattern in plain text wouldn’t be very save, this time Android stores an salted SHA1-hashsum and MD5-hashsum of the PIN or password. The numeric PIN and the alphanumeric passwords are processed in the same way...
>
> Due to the fact that the hash is salted this time, its unfeasible to crack the password with help of a dictionary attack. For cracking the password it is important to get the salt and enough time for attempting a brute force attack. The salt is a string of the hexadecimal representation of a random 64-bit integer.

From this page it seems you are correct in believing that the password is located here in at least the 2.2 versions of Android and later.

---
Tags: password, android-versions
---


# Question
Title: Remember wifi password but never automatically connect
I have both my wifi password and my friend's saved. Since they live nearby sometimes it will automatically switch to theirs if the signal is stronger. I don't ordinarily want to use their connection unless I'm over there or my internet is down.

Is here any way to make android only automatically connect to my wifi without forgetting the other's password? It is long and impossible to memorize so forgetting the network is a huge pain.

Running ICS, and have root if needed.

# Answer
Not exactly what you may have intended, but still a possible solution: Using an app like

you can generate a QR Code of your friend's Wifi connection, print it, laminate it (for protection), and put it into your wallet. Now, whenever you want to use that Wifi network, take out the QR-Code, scan it with Barcode Scanner -- and get connected. For a "log-out" simply disconnect, and *remove* the network from your list (to keep your device from autoconnecting).

Not quite elegant -- but it saves you from typing the long password everytime. Side-Effect: Print out the QR multiple times, and give it to your friend's for other guests. Do the same for your own Wifi. Now you never have to tell your passwords: To permit your guests to connect, somply show them the QR-Code to scan (and have them delete the network from their devices when they leave, as Android stores Wifi-passwords unencrypted).
> 7 votes

# Answer
Hmm, as said before I am afraid that there is no such setting available. BUT there is a handy little app that lets you create widgets that let you switch your networks with a single tap. So when you realize you are connected to your friend's network, simply press the button on your homescreen and you will be connected to your own network again.

You can find the app here: Wifi Manager.
> 1 votes

# Answer
Have you tried going to your **wpa\_supplicant** file and changing the priority on the networks? The settings will be save in regular text and they'll easy to read and figure out.

If you have a Root explorer like ES file or any other you can find it by looking here → `/data/misc/wifi/wpa_supplicant.conf`

Note : *Also there are some apps that let you do this if you don't want to try and find the file yourself*
> 1 votes

---
Tags: wi-fi
---


# Question
Title: how to unlock android 5 if pattern is forgotten?
I had forget my pattern lock and now my mobile asks for it. I tried for 100 times but neither it ask for google account nor something. Even I cant format by using power button and volume. Plz help

# Answer
Reboot the phone and Clear the flash memory. but in this Situation You will lost all the data which is stored in phone memory.
> -2 votes

---
Tags: 5.0-lollipop
---


# Question
Title: App Won't Load After Link /data/app to 2nd SD-Card Partition
Lenovo S920 Android 4.2.1

Basically, I want to link my **/data/app** to **/system/sd/app** (2nd SD Card partition).

I have mount my 2nd partition on boot to **/system/sd/app** correctly.

Here what I got when run "mount":

```
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/emmc@preload /preload ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data
=ordered 0 0
/emmc@android /system ext4 ro,relatime,noauto_da_alloc,commit=1,data=ordered 0 0

/emmc@usrdata /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=or
dered 0 0
/emmc@cache /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ord
ered 0 0
/emmc@protect_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_all
oc,commit=1,data=ordered 0 0
/emmc@protect_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_all
oc,commit=1,data=ordered 0 0
/dev/block/mmcblk1p2 /system/sd ext2 rw,relatime 0 0 // Mount correctly
/dev/block/vold/179:97 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp43 7,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

```

Look at **/dev/block/mmcblk1p2 /system/sd ext2 rw,relatime 0 0**. It looks mount fine.

Here what I got when run "ls -l /data/":

```
-rw------- system system 131072 2015-09-17 15:23 3D.bin
drwxrwx--- bluetooth net_bt 2015-09-17 14:51 @btmtk
-rw-rw---- nvram nvram 34466 2015-09-17 14:31 AllFile
-rw-rw---- nvram nvram 14600 2015-09-17 14:31 AllMap
-rw-rw-r-- nvram nvram 30 2015-09-17 15:05 BT_Addr
-rw-r--r-- root root 80 2015-09-17 15:05 Test.log
drwxr-xr-x root root 2015-09-17 15:16 aee_exp
drwxrwx--x gps system 2015-09-17 15:05 agps_supl
drwxrwx--- system system 2015-09-17 14:31 amit
drwxrwxr-x system system 2015-09-17 15:05 anr
lrwxrwxrwx root root 2015-09-17 15:12 app -> /system/sd/app
drwx------ root root 2015-09-17 14:31 app-asec
drwxrwx--x system system 2015-09-17 14:49 app-lib
drwxrwx--x system system 2015-09-17 14:31 app-private
-rw------- system system 1048576 2013-09-17 07:00 appbank
drwx------ system system 2015-09-17 14:33 backup
-rw------- system system 0 2015-09-17 14:31 combo_t32.cmm
drwxrwx--x system system 2015-09-17 14:49 dalvik-cache
drwxrwx--x system system 2015-09-17 14:49 data
drwxr-x--- root log 2015-09-17 14:31 dontpanic
drwxrwxr-- drm system 2015-09-17 14:33 drm
-rw------- root root 42 2015-09-17 15:05 etm.backup
-rw------- root root 1238 2015-09-17 15:05 link2sd-debuggerd.log
drwxr-x--x root root 2015-09-17 14:31 local
drwxrwx--- root root 2015-09-17 14:30 lost+found
drwxrwxrwx shell shell 2015-09-17 14:31 mdl
drwxrwx--- media_rw media_rw 2015-09-17 14:31 media
drwxrwx--t system misc 2015-09-17 15:05 misc
drwxrwx--- root nvram 2015-09-17 14:31 nvram
-rw------- system system 4194304 2015-09-17 15:17 piggybank
drwx------ root root 2015-09-17 15:23 property
drwxrwx--x system system 2015-09-17 14:31 resource-cache
srwx------ system system 2015-09-17 15:17 server
drwxr-x--- root shell 2015-09-17 14:31 ssh
drwxrwxr-x system system 2015-09-17 15:35 system
drwx--x--x system system 2015-09-17 14:31 user

```

Look at **lrwxrwxrwx root root 2015-09-17 15:12 app -\> /system/sd/app**. It looks linked fine.

Here when I run "ls /system/sd/app":

```
com.UCMobile.intl-1.apk
com.altermyth.bima.tablet-2.apk
com.android.chrome-1.apk
com.android.vending-1.apk
com.appstar.callrecorder-2.apk
com.bbm-2.apk
com.bookmark.money-2.apk
com.cilctel.crono-1.apk
com.estrongs.android.pop-2.apk
com.evernote-1.apk
com.facebook.orca-2.apk
com.google.android.apps.books-1.apk
com.google.android.apps.maps-1.apk
com.google.android.apps.plus-1.apk
com.google.android.calendar-2.apk
com.google.android.gm-1.apk
com.google.android.gms-1.apk
com.google.android.googlequicksearchbox-1.apk
com.google.android.inputmethod.latin-1.apk
com.google.android.play.games-1.apk
com.google.android.talk-1.apk
com.google.android.tts-1.apk
com.google.android.youtube-1.apk
com.hellotext.hello-2.apk
com.instagram.android-2.apk
com.keramidas.TitaniumBackup-1.apk
com.mxtech.videoplayer.ad-2.apk
com.opera.browser-2.apk
com.opera.browser.classic-1.apk
com.shazam.android-2.apk
com.skype.raider-1.apk
com.supercell.clashofclans-2.apk
com.trello-2.apk
com.twitter.android-2.apk
com.whatsapp-2.apk
com.yahoo.mobile.client.android.mail-1.apk
jackpal.androidterm-2.apk
jp.naver.line.android-2.apk
net.openvpn.openvpn-1.apk
org.rojekti.clipper-2.apk
os.tools.scriptmanager-1.apk

```

It seems fine when I first linked it, but after I reboot. It didn't work.

How to fix this problem?

UPDATE:

I test link an \*.apk file to `/data/temp/` folder. `temp` folder is in internal storage. So, it isn't 2nd partition. I just want to make sure that link is work in internal storage, but it seems link failed shown like this:

Look at com.dotgears.flappybird-1.apk

When I do `ls -l` in /data/app:

```
lrwxrwxrwx root     root              2015-09-23 07:58 com.dotgears.flappybird-1
.apk -> /data/temp/com.dotgears.flappybird-1.apk

```

Any idea what is going on?

UPDATE:

It seems whatever I copy an \*.apk file to new location. It seems failed. It actually not failed but somehow when I properties my \*.apk that I copied to new location. I click on it, it show nothing. Like, their **icon didn't show, version: N/A, size: N/A, Package Name: N/A**

# Answer
After rebooting, any mounts you have made which your ROM isn't configured to automatically do will be lost. You could write your own init.d script, or you could use an app, like Mounts2SD, which will set it up for you and comes with a nice interface to boot.
> 0 votes

---
Tags: custom-roms, rom, app2sd, link2sd
---


# Question
Title: Facebook Messenger consumes a lot of battery even if no messages are sent/received
I recently installed Facebook Messenger and it seems to be consuming a lot of battery, even if no messages are sent/received in a day.

Below is the battery usage for reference. As you can see Messenger used 12% of battery even though I did not use it the entire day, exceeding even the screen usage.

Is there a way to fix this? Uninstalling the app is my last option as sometimes I do want to send/receive messages on it.

# Answer
Both the Facebook and Facebook Messenger apps are notorious for excessive battery use. Seriously, social media is nowhere near important enough to warrant killing your phone battery. One way to help is to make sure that location reporting is turned off for both apps. You should actually go through all of the settings for both apps and disable every single thing you definitely don't need. All of the battery-sucking features are enabled by default.

Of course, the best thing to do is kick Facebook's apps to the curb and just access it through the mobile browser... but that's just my opinion,
> 2 votes

# Answer
Here are my **opinions.**

Firstly there is an application called "WatchDog Task Manager". You can install this application (or use the free version) and configure it so it kills processes exceeding certain thresholds. This can be set for the parameter of CPU or battery usage. This is primarily for CPU.

Another application you could configure is "SnapDragon BatteryGuru". Now this is highly opinion based, but I used this on my Samsung, HTC One M7 and M8 and noticed improved battery life. This application monitors your daily habits for battery and places certain application rules for when it syncs. This could assist in restricting FB (or even Messenger) from hogging battery.

You could also go to the extent of installing "Memory Booster" which has several additional add-ins such as task killers and battery saving technics. I would not really believe this suitable, but it is a worthy mention.

Of course there are many other applications that you could look into that apparently help boost your battery life. The key to boosting battery life is minimising applications that actively have "wakelocks". More on wakelocks can be read here: What are wakelocks?

Feel free to comment on this if I have missed anything or your disagree with this. If you believe this a sufficient and correct answer, please mark it so.
> 1 votes

# Answer
I highly recommend Greenify to take care of these battery sucking applications.
> 0 votes

---
Tags: 5.0-lollipop, battery, battery-life, motorola-moto-g2, facebook-messenger
---


title: Android boot loop after fresh install

text:
# Question
Title: Android boot loop after fresh install
Phone: Nexus 4 with the latest android 5.1.1. Accidentally I broke my screen and turned off my phone. After a month my screen was replaced and then I got stuck in the boot loop at the start.

I've made factory reset in both android recovery and TWRP recovery.

I've tried to install popular ROMs (Chroma) and google factory images: all from the latest LMY48M to the old ones. Installation was OK, but after install I have a boot loop (flying dots, or rotating circles, etc - I have been waiting for hours). I made it to start the system - only with the oldest factory image: JDQ39 (4.2.2)

After android started and some configuration made (wifi, google account), after some time, phone tells me about system update 4.3. I agreed and got stuck in the boot loop again.

I know that there are tons of `stuck in boot loop` questions, but usually solution is to clean cache, factory reset, or reinstall. And I have boot loop stucking after factory reset and fresh install. Do you have any ideas how to fix this?

I think, I can live with 4.2.2, but maybe it's possible to get 5.1 working back?

P.S. All installations (adb sideload of ROMs or ./flash-all.sh for factory images) where finished successfully. The only error I got was `unable to mount /usb-otg` in TWRP while factory reset (anyway it said that reset was done). But I think it's not the reason, isn't it?

**Update:** I've tried all factory builds from official source. They come with script that manually run `fastboot` to flash images:

```
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.07.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-occam-lmy48m.zip

```

It always finished with success - no errors. But after restart - boot loop freezes. Also, I've always made a factory reset before flashing factory images. I've tried both via original recovery.img and via TWRP (with Dalvik cache)

**Update2:** Here is my `adb logcat` on start of working 4.2.2. I've managed to get it only after turning on `USB debugging`. My question is - will the `USB debugging` mode reset after wiping data? I want to try install 5.1.1 factory image again and to collect `adb logcat` data. But if USB debugging option is resetted, then I will have no result again.

# Answer
> 1 votes
Do a factory image flash using fastboot,taking special care to update the partition data,bootloader and radio images. Partition data means the ebr/mbr/preloader partitions. The manual flash implies that you must flash each partition manually, just so that you are sure that everything was flashed correctly, even if the script executed without errors.This should resolve the issue. If it doesn't, maybe a flash using Qualcomm MSMDownloader will work. It would help if you could upload the names of the images in the factory image archive, so that I can find out which partitions may be causing the problem

---
Tags: nexus-4, factory-reset, boot-loop, twrp
---


title: Samsung Galaxy s4 won't boot

text:
# Question
Title: Samsung Galaxy s4 won't boot
I have a Samsung Galaxy s4 which is rooted and has cyanogenmod and cwm recovery installed on it, which I have been using for several months with absolutely no issues, until today. All of a sudden, my phone shut itself off, and now it will not boot. When I try to turn it on, all I get is the Samsung logo for about a second, then it goes black. I managed to get into download mode, but going into the recovery (which professor google told me I could do with power + home + volume up) did not work.

Taking my phone in to get it repaired/replaced is not an option, since my warranty is void (and I can't just trick them by unrooting it and flashing the stock rom because of that knox flag that is tripped as soon as you mess with the bootloader).

If all else fails, I will do whatever it takes, although I would prefer to recover some data from the phone first (contacts, pictures, etc)

I have a USB cable to connect it to my computer (windows), and I also have a microSD card I could use to load something onto it if that could possibly fix anything.

# Answer
I solved my own issue, and am now posting the solution I found as an answer.

The battery had died without me realizing it. I originally tried to charge the phone for about half an hour (before posting the question) but had no luck. I then tried again later on using a different charger which did work.
> 0 votes

---
Tags: samsung-galaxy-s-4, clockworkmod-recovery, unbricking
---


# Question
Title: remove google account from android device
if i sync a google account account to my android mobile, all my gmail, contacts will be synced with the google account and i can view my mobile contacts, photos from a web browser in pc by signing in my google account right. now my question is simple. if i remove my google account from my android mobile, will i still be able to view the already synced contacts and photos from a web browser in pc through internet?

# Answer
Yes. If you have synced the account properly then you will be able to access all your content from browser even though you remove the account from android device.
> 1 votes

# Answer
Yes, you will still be able to view any of that synced data that you can view from a different device.
> 0 votes

# Answer
My understanding of this process is not technically correct. For a full explanation of how this process works read: How Google Sync Works and Google Sync.

I will give my understanding of the matter and hope it

Lets say you have Contact\_A on your Phone. When you configure a G-Mail account on your phone to sync your contacts Google grab Contact\_A from your local device (phone) and then syncs with your *Google* account. Once this is done, this contact is then associated with your google account and is added to their database. This is controlled by Google and when you login to their service you're accessing your account through their product.

By syncing (and completing) this on your phone, Google will then store a copy of all the contacts on their server and will allow you to access this via a browser. You can successfully unlink your phone.

Obviously this method does not allow you to keep your phone and cloud sync unless you re-add. The best option here for you (I assume) would be to simply disable the "sync contacts" field on your phone.

If you believe anything here is wrong please feel free to correct me - I'm here to learn too. If a sufficient answer please mark it so.
> 0 votes

---
Tags: google-account
---


title: Insufficient Storage Space?

text:
# Question
Title: Insufficient Storage Space?
I just bought an SD card with 8GB of memory (My old one had 2GB) and it's still saying I can't download or update any apps, and that there is insufficient storage space. I have an LGMS659 and I am very frustrated. Please help?

# Answer
> 0 votes
Loren, this is most likely due to your **internal storage** being full. By default, applications may be installing to your local storage. The easiest solution here will be to uninstall any unimportant applications and then install AppMgrIII or a similar application. This will then allow you to migrate larger applications to your SD card.

From memory (this may not be accurate) all applications that are not system installed applications can be moved to the SD card.

If you feel I have answered this please mark it so. If there is anything I have missed, or something wrong, let me know.

---
Tags: sd-card
---


# Question
Title: New full-screen share UI - move app to top
In Android 5's new share UI - full-screen, with "prioritized" apps - how do I move arbitrary app into the top, priority section? Not my app, just one that I use often.

Say I want to move "Drive" to the top section. Is there a way to remove G+ from the top section?

# Answer
> 0 votes
It is prioritized according to frequency of use. Whichever apps house most for sharing will eventually go to the top of the list, and they will be sorted in alphabetical order.

---
Tags: 5.0-lollipop, share-menu
---


# Question
Title: move apps to internal memory from system memory?
I have LG e405. How do i get downloaded apps /any app from system/phone memory to goto internal memory?there are heaps more that i need to know but most apps and things seem to have disappeared from phone , now no room to reinstall them? This 3rd or 4th time has happened. Ok will not be far away, thanks

# Answer
> 0 votes
You have to go into your application manager in the settings. Clicking on each individual app will bring up the status and information screen for that app. Some apps will have the option to 'Move To External Storage'. Press that and let it do its thing and the app will be on your SD Card.

Keep in mind that not all apps can be moved to external storage. This is a specific functionality of applications. You'll find fairly regularly that applications do not have the move functionality.

# Answer
> 0 votes
If you mean internal memory as in the internal sd card, you can use the app manager option in settings to do it, unless your phone ships with merged storage. In that case, you will need to root and use a dedicated app like Link2SD to move apps to the external inserted microSD card.

---
Tags: insufficient-memory
---


# Question
Title: Where does Google MyTracks store recorded files?
I am not 100% sure of this but I seem to remember that in previous versions of MyTracks the recorded files were stored at **/mnt/sdcard/MyTracks**. But this does not seem to be the case any more. By previous I mean version prior to *at least* version **2.0.4** which is what I currently have.

I have recorded several tracks but can't find the files at **/mnt/sdcard/MyTracks**. In fact there is no such folder name on that location. So where does it store recorded files now? I need the GPX files.

I tried searching for "mytrack" and also "mytracks" (case insensitive) in File Expert app at **/mnt/sdcard** but it found no folders. It did find some files.

```
com.google.android.maps.mytracks
/mnt/sdcard/android/data/com.google.android.maps.mytracks

cache_vts_com.google.android.maps.mytracks.0
/mnt/sdcard/android/data/com.google.android.maps.mytracks/cache/

```

And additional 4 files in the same location. But I can't see any GPX files in here. Attempting to search at root causes File Expert process to crash.

# Answer
> 4 votes
I'm still not sure where actual MyTracks data is stored. I think it's stored somewhere in the internal memory, not in the external memory. But I have found a way to export the GPX data.

1. Start MyTracks.
2. Press Menu button.
3. Tap "Save all to external storage".
4. Tap "Save as GPX".

> Saved x tracks to /mnt/sdcard/MyTracks/gpx.

At least some of the data for Google MyTracks is stored at **/data/data/com.google.android.maps.mytracks**. But to view **/data/data** you need to enable the root explorer in the phone and you need root access.

To enable root explorer in File Expert:

1. Start File Expert.
2. Press Menu button.
3. Tap More.
4. Tap Settings.
5. Tap File Explorer Settings.
6. Check Root Explorer option.

For this to work you need root access on the phone, i.e. the phone needs to be rooted. Also, sometimes you will need to mount the file system as writable, and you can do this too within the app settings.

(I tried the same thing with ES File Explorer but I was unable to even view the root folder / with it, it was only able to view /sdcard. So therefore I recommend using File Explorer instead.)

# Answer
> 1 votes
Be sure to check Google Drive because the app can store/sync to the "My Tracks" folder.

# Answer
> 1 votes
I think track data is stored in **mytracks.db** rather than in any type of GPS file. This database is located at the below path. (root required to pull it out)

> /data/data/com.google.android.maps.mytracks/databases/mytracks.db (and its -journal file)

You can view it by a SQLite tool such like SQLite Expert, and find detailed data of each track.

Recently, the touch panel of my mobile device was broken during recording. That's why I'm here... In conclusion I have copied the database simply to the other device, and then all tracks were recovered including the unfinished track.

Steps:

1. Install MyTracks on the new device.
2. Pull **mytracks.db** and **mytracks.db-journal** from the old device.
3. Put **mytracks.db** and **mytracks.db-journal** into the new device, overwrite the original files.
4. Launch MyTracks on the new device. All tracks are recovered.

---

Finally, if you'd like to get GPX files, export them manually as your own answer mentioned. It might be the only way I know.

# Answer
> 0 votes
On my Galaxy S4 running My Tacks 2.0.10 the pictures taken with the app end up in this directory in the camera's memory (not the SD Card):

```
MyTracks\pictures

```

There are subdirectories created for each track that I've taken pictures on. They are named `MyTracks123`, `MyTracks134`, etc.

The full path of the main directory appears to be:

```
/storage/emulated/0/MyTracks/pictures

```

These pictures are automatically synced to my other devices where I have My Tracks installed. This means I'll have to stop taking pictures on a track from within My Tracks. I also don't like that I can't tell My Tracks to put the pictures on the SD Card. Oh well, easy enough to just take the pictures outside of My Tracks.

I also do not see the pictures being synced up to the My Tracks directory on my Google Drive. Just the `.kmz` files seem to be synced there.

---
Tags: mytracks
---


title: No passwords stored in Webview

text:
# Question
Title: No passwords stored in Webview
I have an ASUS tf101. Have rooted it and installed SQLite Editor. Have found the Webview file. There is listed some web adresses, but under passwords the fields are blank. I desperately need one of these passwords, but why are they not listed there? The password for the spesific site was typed in the browser just a few weeks ago.

# Answer
Just use the Forgot Password option for the website. The passwords are encrypted and you can't find them like that.
> 0 votes

---
Tags: password, webview
---


title: Work around on an unrooted LG 4

text:
# Question
Title: Work around on an unrooted LG 4
Had a rooted phone for years til and LG update bricked my last phone. Now I had to upgrade to an LG 4 ( Sprint is my carrier BTW) Problem is... I can't find the setting to enable USB debugging, nor, does it appear, that I can unlock the UICC. I like the phone so this isn't really a problem, but, I hate having the bloatware. (ie I would rather access facebook via the browser than keep this data-eater on my phone. Does anyone know how to work around this block so that I can remove the unwanted bloatware without rooting the phone?

Thanks in advance.

# Answer
I thought about posting this as an edit, but I feel an answer will better suit the community. Here is what I found.

To unlock the developer options on an LG4 Go into settings... about phone..Software info. Finally, tap "Build Number" 7 times. Now back out to the main menu and there will be a choice for Developer Options. From here you can enable USB debugging and enjoy all of the other tools available. Rooting the phone from this point is easy.
> 0 votes

---
Tags: rooting, lg, bloatware
---


title: Sony xperia m4 aqua memory

text:
# Question
Title: Sony xperia m4 aqua memory
I would like to ask if there is a way to bypass limitations of internal memmory delegated for applications as my mobile operator I bought phone from added some useless bloatware which after removing apps that were possible to remove brings me only to 1.8GB of space for applications.

As I would really like to play some of new games which have size of additional data as big as 500MB it is impossible to have many applications installed, because all data is stored into internal memory instead of memory card.

Reason is, application partition in internal memory is mounted as /storage/sdcard and external sd card is mounted as /storage/sdcard1

Because of this, there is no way to move applications to sd card (only manually, but they cant find their data, because they defaultly search in /storage/sdcard mountpoint) as it will move them just to other partition of internal memory.

My question is, is it possible to bypass this problem without actually rooting phone? Will there be software udate that will change method of mounting or solve it in some other way (like creating symbolic links to external card as data folder of application)?

# Answer
Enter the following commands in a terminal emulator after you have rooted and installed busybox:

```
su
ln -s /storage/sdcard1/Android/obb/ /storage/sdcard/Android/obb/

```

Copy the games extra data (`.obb`) files to `Android/obb/` folder on your SD card from your computer. This may or may not work with games downloaded from Google Play, I have not tested it.
> 0 votes

---
Tags: sony-xperia
---


title: TWRP patching /system

text:
# Question
Title: TWRP patching /system
I recently flashed a stock system image to take an OTA update and have only *booted* to TWRP since. (I didn't flash it) I did root, though. When I was browsing /system I found that reboot-from-recovery.p was renamed to reboot-from-recovery.bak
My question is was this done by SuperSU or TWRP? and could this be the only modification?

Thanks.

# Answer
> 0 votes
It's done by TWRP.

If you're rooted, SuperSU modifies /system as well to put files there to give you root.

---
Tags: rooting, recovery-mode, twrp
---


# Question
Title: What's the difference between "Contacts" and "People details?"
In Settings -\> Accounts -\> Google, when I tap on my Google account, I see a "Sync settings" page with a list of different Google services that can be synced (App Data, Calendar, Drive, Gmail, Google Play Books, etc.).

This list includes both "Contacts" and "People details." What is meant by "People details" and how does this differ from "Contacts?"

Are there any negative outcomes I would expect from disabling sync of "People details" (i.e. what would break?)

# Answer
> 9 votes
**Contacts** under Accounts, helps in syncing Google-Contacts (Phone contacts saved )
More on Contacts sync adapter here

**People details** deals with information regarding Google play games and Google+ (Game buddies and people in your circles on Google+)
More on People sync adapter here

# Answer
> 1 votes
This is a little bit of a guess since you didn't specify your device... Contacts is normally part of the stock Android operating system while People is usually part of the launcher or service provider software. They are virtually the same app with different skins or interfaces. The People apps usually also incorporate all of your contacts, including social media. Contacts will most likely only show Gmail and phone contacts unless you alter the settings.

Hope this helps!

---
Tags: settings, sync, google-account
---


# Question
Title: Restrict Data consumtion by playStore Over WIFI
My Google Play Store application has gone haywire.It is downloading heavily without even notifying anything about what it is downloading and the rate has gone up by 2.5 times in past 2 days.I tried everything to stop it.I selected do-not auto update apps in play store settings and turned off all kinds of Sync.But it still isn't working. Is there any way i can restrict data consumed by my google play store on WiFi? I have a rooted device.

# Answer
you can start clearing data cache for play store app in .. settings\>apps\>all apps\>play store\>clear data.

It would probably solve your issue if it still lingers than remove your google account from settings\>accounts\>google account\>remove this account.

Add again the same account with your credentials.. it would solve the issue.
> 0 votes

---
Tags: google-play-store, 4.4-kitkat, google-play-services
---


title: Nexus 5 Reboot loop

text:
# Question
Title: Nexus 5 Reboot loop
Today my Nexus 5 turned itself off, and then whenever I try to start it again, it loops rebooting - it shows the google logo, then starts the boot animation, then powers off and starts over.

I've tried to get into recovery mode with the volume+power keys, but when I'm able to get into the recovery screen, it shuts off in about the same amount of time and reboots again.

What can I do to fix this?

I did run the upgrade to 5.1.1, but it was a few days ago so I'm not sure whether that would be related.

# Answer
In the end, nothing I tried worked - it went into the reboot loop even from inside the boot loader screen, so I couldn't get into recovery mode.

I sent it to LG and they repaired it for free even though it was supposed to be out of warranty.
> 0 votes

# Answer
I think you encountered the issue with a stuck power button. I had the exact same behaviour that also went away without explanation to return a few weeks later. I read the one trick is to bang it in a hard surface and shock the button out of its stuck state.

The second time it occurred I actually found a much more gentle way to temporarily fix this. Take an electric tooth brush without brush and push the oscillating shaft onto the backside and side of the phone close to the power button. After a few seconds of that my phone was back in working order.

And I felt strangely like Mc Gywer.

\*Update: This temporary fix still works two months later. So it was not so temporary considering the lifecycle of a modern smartphone.

\*Update 2: This fix worked fore a few years. Now the Nexus is permanently stuck in a reboot loop and no toothbrushes or other vibrating tools will fix it.
> 10 votes

# Answer
On an earlier version of Lollipop, after an update, my Nexus 5 would turn off randomly and enter a boot loop. I tried entering recovery just as you did but it too kept rebooting. I researched reasons for a boot loop and discovered some users of the Nexus 5 have faulty power buttons.

Try repeatedly tapping the power button as if to get it unstuck. See if the boot loop stops because of this action. If it stops, carefully hold your N5 so that the power button does not get stuck and turn on your phone. Perhaps jiggle the phone a little after the long press to ensure the button jiggles too.

It sounds simple but this reliably booted my phone when it had troubles. I installed Gravity Screen (free in Google Play) and try my best not to use the power button. I have not had many troubles since and am on a long streak for no issues.

I mention it happening after an update but I would guess the issue is just coincidental with the update. Best of luck.
> 3 votes

# Answer
Try going into fastboot mode. Its comparatively much easier to go into fastboot mode. To go into fastboot mode, turn off your phone and press and hold `volume down + power keys` at same time until you get to a black screen with android logo and a bunch of stuff written.

Now there you also have option to boot into recovery, just press volume buttons to switch to boot modes and when it says `recovery`, press power button to select boot into recovery option.

**Possibility 1:**

You were able to go into recovery.

Here you can also try to factory reset and boot your phone. If that doesn't work, proceed below.

***Case 1:***

You have the rom to flash inside your phone (sdcard).

if you do have rom inside phone then just wipe `system, cache, dalvic` and if rom isnt same as the once currently installed on your phone (the one that is bootlooping), then you also need to wipe `data`.

***Case 2:***

You were able to boot into recovery but dont have any rom inside phone to flash.

* In this case, setup ADB, connect phone while its in recovery to adb.
* Download a rom for your phone (you can head over to XDA to look for rom and download one you like). Just download it to your pc.
* Connect your phone to pc using USB.
* Open cmd and enter the command `adb push PathAndNameOfROMFile.zip /sdcard/`. This will push the rom file you downloaded above to sdcard.
* Wipe your system, dalvic cache, cache and data (recommended, but not necessary if you downloaded same rom as previously installed on your phone).
* Reboot.

**Possibility 2:**

You were unable to go to recovery due to whatever reason.

Boot into fastboot mode again.

**Option 1:**

*Try wiping data and factory resetting from here (I wont be responsible for your data here).*

* To factory reset, first setup adb from link provided above. Then go to download mode and connect phone to pc.
* Open CMD/Terminal. And enter these commands:

fastboot erase data fastboot erase cache

Now try rebooting. If that didn't work, move on to *Option 2*.

**Option 2:**

(*We are going to flash a factory image.*)

* So first, download factory image for your phone here.
* Extract downloaded archive using winrar.
* Connect your phone to pc using USB.
* Execute the flash-all.bat script (for Windows) or flash-all.sh(for MAC and LINUX) in the folder where you extracted the factory images.

---

**NOTES:**

For MAC: You'll have to edit the flash-all.sh, and add "./" before every fastboot command.

This script will also flash stock recovery. If you are not sure that your recovery is ok, then let this happen. Otherwise if you are sure that your recovery is fine and not corrupt. delete the file with word `recovery` in it. Open and edit whatever flash script you will be using to flash and remove these lines:

```
fastboot erase recovery
fastboot flash recovery recovery.img

```

---

**Semi-Case 1:**

Everything flashes fine.

In this case just skip the `Semi-Case 2` and move on.

**Semi-Case 2:**

*There is some problem flashing some specific part.*

In this case, you can try flashing manually.

Run these commands *One by One* in cmd/terminal (replace `C:/` with path to where you extracted the archive):

```
fastboot flash bootloader C:/image-hammerhead-xxxx/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-hammerhead-xxxx/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-hammerhead-xxxxx/system.img
fastboot flash userdata C:/image-hammerhead-xxxxx/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)

fastboot flash boot C:/image-hammerhead-xxxx/boot.img

fastboot flash recovery C:/image-hammerhead-xxxx/recovery.img
(Skip the above command if you dont want to flash stock recovery and are sure that your current recovery is not corrupt).

fastboot erase cache

```

This will manually flash everything. Hopefully this time it should be fine.

---

* Wait for everything to flash.
* After everything has finished flashing, use volume buttons to select `recovery` option from fastboot and press power button to boot into it.
* Select factory reset and reboot phone. You will turn on and you although are still rooted (just need to install a custom recovery and supersu from play store).

Hope this helps.
> 1 votes

# Answer
There are a number of long winded threads on the Nexus product forums about this. Some people get resolution by replacing or fixing the power button, as noted already here. Others by replacing the battery, others by sending to LG for replacement. I saw at least two reports of cures by rooting and going to an older kernel (5.0, 5.1).

The fact that so many of the reports cluster around 5.1.1 update make me suspicious that the hardware approach (button, battery) address the true problem, but hey if it lets you get another few months or year out of the device go for it.

For me my phone *seems* be fixed (only 24 hours free and clear so far), but I don't know what the magic was. What I did follows, the presence of next step indicates the previous one didn't work (phone still rebooted or shutdown spontaneously).

* Reset to factory default using Settings menu
* Reset to factory defaults using Recover Mode in bootloader
* Use WugFresh Nexus Root Kit to unlock bootloader, root the phone
* WugFresh revert: Flash stock image and unroot (which uses the most recent official 5.1.1 image)

At this point the phone finally stabilized, going ~15 hours without a reboot or shutdown.

In the middle I talked to Google and LG customer service, I'll add details of that to another answer. Since I'm so deep in now I've since re-unlocked and rooted and applied PureNexus ROM and GAPPS. So far so good, but it's only been a few hours.

\**Update: celebration was premature. Phone is still rebooting, though frequency has diminished. Looks like I go back to stock and wait much longer before trying anything else, including reinstalling most used apps. :-( \**

Sources:
> 1 votes

---
Tags: nexus-5, boot-loop
---