Database Users

Problem with [ROM] [4.2.1] cm10.1 unofficial [2-2-13] 3.0.59 kernel & aosp [4.2.2] [

Problem with [ROM] [4.2.1] cm10.1 unofficial [2-2-13] 3.0.59 kernel & aosp [4.2.2] [
Hi guys,
My problem with this ROM on Topic " [ROM] [4.2.1] cm10.1 unofficial [2-2-13] 3.0.59 kernel & aosp [4.2.2] [.65] 2-23-13"
is on option STORAGE in Settings Menu.
Show me a message "Unfortunately. Setting has Stopped".
Have a solution ?

Re: Problem with [ROM] [4.2.1] cm10.1 unofficial [2-2-13] 3.0.59 kernel & aosp [4.2.
Something probably within the rom. Are you trying to mount sd or something?
HTC Vivid with Sense 4+ ICS 4.0.4

Only my SD CARD
[email protected] said:
Something probably within the rom. Are you trying to mount sd or something?
HTC Vivid with Sense 4+ ICS 4.0.4
Click to expand...
Click to collapse

Rotation
Sorry for changing the topic but I have this same ROM and everything works except for landscape mode and auto rotate.

minidz said:
Sorry for changing the topic but I have this same ROM and everything works except for landscape mode and auto rotate.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=38573051&postcount=226
Works for me

New issue
When a take a pic with my camera in autoflash or static flash this pic sometimes is dark as if my phone don have a flash

Confirm OP's issue and...
I can confirm OP's issue. I followed the official downgrade and flash instructions for CM7 yesterday and after getting fed up with that backtracked and installed aosp 4.2.2.2. Storage does crash after 250 to 500 ms.
<del>I'm also having trouble getting 4g connection. I don't have the 4g anymore.</del> Though after updating my baseband to baseband version 12.58.60.25U_26.11.04.03_M I am getting notably better reception in my house. I can't be certain 4g reception isn't just a fluke since I have yet to go out driving. edit: The H icon indicates advanced HSPA+ speeds. No problem. Thank you.
The big issue is getting my camera to work but BIG thanks to Nicgrainer I learned about acatlog and got some interesting information. This problem was happening to me before so I can't rule out a hardware issue but the log is encouraging. I thought I'd done a complete wipe before updating. I did the CWM wipe and dalvik cache wipe but maybe that misses something. The most important parts of the log appear to me the following:
E/QualcommCameraHardware( 104): android::QualcommCameraHardware::QualcommCameraHardware(): build changelist:
E/QualcommCameraHardware( 104): android::QualcommCameraHardware::QualcommCameraHardware(): build date: Thu Feb 21 00:16:30 CST 2013
E/QualcommCameraHardware( 104): android::QualcommCameraHardware::QualcommCameraHardware(): build description: full_vision-eng 4.2.2 JDQ39 eng.fyodor.20130221.001544 test-keys
E/QualcommCameraHardware( 104): android::QualcommCameraHardware::QualcommCameraHardware(): sense version:
D/QualcommCameraHardware( 104): constructor EX
I/QualcommCameraHardware( 104): createInstance: created hardware=0x25cbc0
D/QualcommCameraHardware( 104): startCamera E
D/QualcommCameraHardware( 104): loading liboemcamera at 0x40085dec
D/QualcommCameraHardware( 104): Set main cam and main cam only
I/mm-camera( 104): set sensor selection :0
D/QualcommCameraHardware( 104): Open Device node : /dev/msm_camera/control0
E/QualcommCameraHardware( 104): startCamera X: /dev/msm_camera/control0 open failed: No such file or directory!
E/QualcommCameraHardware( 104): createInstance: startCamera failed!
E/CameraClient( 104): Could not open camera 0: -1
E/CameraClient( 104): initialize: Camera 0: unable to initialize device: Operation not permitted (-1)
I/CameraClient( 104): Destroying camera 0
V/StateManager( 3108): startState class com.android.gallery3d.app.PhotoPage
E/CameraHolder( 3108): fail to connect Camera
E/CameraHolder( 3108): java.lang.RuntimeException: Fail to connect to camera service
And here follows everything relevant to opening the app Camera down to opening alogcat to view the log. Any thoughts?
Code:
[snip]
V/CameraHolder( 3108): open camera 0
I/AwesomePlayer( 104): setDataSource_l(URL suppressed)
D/MediaExtractor( 104): returning default extractor
I/AwesomePlayer( 104): setDataSource_l(URL suppressed)
D/MediaExtractor( 104): returning default extractor
D/dalvikvm( 3108): GC_CONCURRENT freed 95K, 2% free 6677K/6804K, paused 20ms+10ms, total 81ms
D/dalvikvm( 3108): WAIT_FOR_CONCURRENT_GC blocked 13ms
I/CameraClient( 104): Opening camera 0
I/QualcommCameraHardware( 104): openCameraHardware: call createInstance cameraId 0
I/QualcommCameraHardware( 104): createInstance: E
D/DHDiagnostic( 104): android::DHDiagnostic::DHDiagnostic() E
D/DHDiagnostic( 104): android::DHDiagnostic::DHDiagnostic() X
D/DHDiagnostic( 104): android::DHDiagnostic::DHDiagnostic() E
D/DHDiagnostic( 104): android::DHDiagnostic::DHDiagnostic() X
D/CameraPP( 104): CameraPP::CameraPP()
D/SDO_PP ( 104): SDO_PP::SDO_PP()
I/OlaEngine( 104): [Ola_Engine_Create:79] engine build info [ name ] : htc
I/OlaEngine( 104): [Ola_Engine_Create:83] engine build info [ date ] : 2012-02-14 14:49:38
I/OlaEngine( 104): [Ola_Engine_Create:87] engine build info [ version ] : __bulid_revision_226__
D/CameraFace_OLA( 104): create OlaEngine
I/FD ( 104): [Ola_FaceDetector_Create:135] create num : 2
D/CameraFace_OLA( 104): create Ola FD
V/Olaworks( 104): [Ola_BeautyShotEngine_Create] prr(0x001dabc0)
D/CameraFace_OLA( 104): create Ola BS
D/CameraFace_OLA( 104): create Ola SD
D/CameraFace_OLA( 104): create Ola BD
D/CameraFace( 104): alloc face_t 0x2db650 num 10
D/QualcommCameraHardware( 104): Storing the current target type as 2
I/CAF_Sensor( 104): android::CAFSensorListener::CAFSensorListener() E
I/CAF_Sensor( 104): android::CAFSensorListener::CAFSensorListener() X
I/CAF_Sensor( 104): android::status_t android::CAFSensorListener::initialize() E
I/CAF_Sensor( 104): android::status_t android::CAFSensorListener::initialize() X
I/CAF_Sensor( 104): void android::CAFSensorListener::setCallbacks(void (*)(int, void*), void*) E
I/CAF_Sensor( 104): void android::CAFSensorListener::setCallbacks(void (*)(int, void*), void*) X
E/QualcommCameraHardware( 104): android::QualcommCameraHardware::QualcommCameraHardware(): build changelist:
E/QualcommCameraHardware( 104): android::QualcommCameraHardware::QualcommCameraHardware(): build date: Thu Feb 21 00:16:30 CST 2013
E/QualcommCameraHardware( 104): android::QualcommCameraHardware::QualcommCameraHardware(): build description: full_vision-eng 4.2.2 JDQ39 eng.fyodor.20130221.001544 test-keys
E/QualcommCameraHardware( 104): android::QualcommCameraHardware::QualcommCameraHardware(): sense version:
D/QualcommCameraHardware( 104): constructor EX
I/QualcommCameraHardware( 104): createInstance: created hardware=0x25cbc0
D/QualcommCameraHardware( 104): startCamera E
D/QualcommCameraHardware( 104): loading liboemcamera at 0x40085dec
D/QualcommCameraHardware( 104): Set main cam and main cam only
I/mm-camera( 104): set sensor selection :0
D/QualcommCameraHardware( 104): Open Device node : /dev/msm_camera/control0
E/QualcommCameraHardware( 104): startCamera X: /dev/msm_camera/control0 open failed: No such file or directory!
E/QualcommCameraHardware( 104): createInstance: startCamera failed!
E/CameraClient( 104): Could not open camera 0: -1
E/CameraClient( 104): initialize: Camera 0: unable to initialize device: Operation not permitted (-1)
I/CameraClient( 104): Destroying camera 0
V/StateManager( 3108): startState class com.android.gallery3d.app.PhotoPage
E/CameraHolder( 3108): fail to connect Camera
E/CameraHolder( 3108): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder( 3108): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 3108): at android.hardware.Camera.<init>(Camera.java:340)
E/CameraHolder( 3108): at android.hardware.Camera.open(Camera.java:302)
E/CameraHolder( 3108): at com.android.camera.CameraManager.cameraOpen(CameraManager.java:283)
E/CameraHolder( 3108): at com.android.camera.CameraHolder.open(CameraHolder.java:210)
E/CameraHolder( 3108): at com.android.camera.Util.openCamera(Util.java:315)
E/CameraHolder( 3108): at com.android.camera.PhotoModule$CameraStartUpThread.run(PhotoModule.java:316)
W/dalvikvm( 3108): threadid=12: thread exiting with uncaught exception (group=0x40ab4930)
E/AndroidRuntime( 3108): FATAL EXCEPTION: Thread-338
E/AndroidRuntime( 3108): java.lang.RuntimeException: openCamera failed
E/AndroidRuntime( 3108): at com.android.camera.Util.openCamera(Util.java:320)
E/AndroidRuntime( 3108): at com.android.camera.PhotoModule$CameraStartUpThread.run(PhotoModule.java:316)
E/AndroidRuntime( 3108): Caused by: com.android.camera.CameraHardwareException: java.lang.RuntimeException: Fail to connect to camera service
E/AndroidRuntime( 3108): at com.android.camera.CameraHolder.open(CameraHolder.java:219)
E/AndroidRuntime( 3108): at com.android.camera.Util.openCamera(Util.java:315)
E/AndroidRuntime( 3108): ... 1 more
E/AndroidRuntime( 3108): Caused by: java.lang.RuntimeException: Fail to connect to camera service
E/AndroidRuntime( 3108): at android.hardware.Camera.native_setup(Native Method)
E/AndroidRuntime( 3108): at android.hardware.Camera.<init>(Camera.java:340)
E/AndroidRuntime( 3108): at android.hardware.Camera.open(Camera.java:302)
E/AndroidRuntime( 3108): at com.android.camera.CameraManager.cameraOpen(CameraManager.java:283)
E/AndroidRuntime( 3108): at com.android.camera.CameraHolder.open(CameraHolder.java:210)
E/AndroidRuntime( 3108): ... 2 more
W/ActivityManager( 359): Force finishing activity com.android.gallery3d/com.android.camera.CameraLauncher
D/dalvikvm( 359): GC_FOR_ALLOC freed 477K, 16% free 12609K/14908K, paused 143ms, total 144ms
V/NFC ( 3108): this device does not have NFC support
D/dalvikvm( 3108): GC_CONCURRENT freed 162K, 3% free 6937K/7128K, paused 3ms+2ms, total 54ms
D/dalvikvm( 3108): WAIT_FOR_CONCURRENT_GC blocked 9ms
W/SensorService( 359): sensor 00000000 already enabled in connection 0x5fa448 (ignoring)
W/ActivityManager( 359): Activity pause timeout for ActivityRecord{4148f470 u0 com.android.gallery3d/com.android.camera.CameraLauncher}
I/ActivityManager( 359): No longer want com.android.providers.calendar (pid 2789): empty #7
I/Process ( 3108): Sending signal. PID: 3108 SIG: 9
W/InputMethodManagerService( 359): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
I/ActivityManager( 359): Process com.android.gallery3d (pid 3108) has died.
I/WindowState( 359): WIN DEATH: Window{416a86e8 u0 com.android.gallery3d/com.android.camera.CameraLauncher}
I/ActivityManager( 359): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=org.jtb.alogcat/.LogActivity} from pid 553
[/snip]

[Q] Reboot while installing large app

OK so I have Magic 2014 on my tablet, version 1.2.0. I installed it from Amazon Appstore because it worked, whereas Play Store kept throwing errors at me while downloading the extra content. And hence, the in-app content purchases I've made have also been through Amazon.
This evening I tried upgrading the app to 1.4.0 from Amazon. It went through the entire 1.5 GB download, commenced the install... and then promptly rebooted. The app is still sitting at version 1.2.0.
I found the apk file cached in /sdcard/Android/data/files/apks. So I attempted to install from there. Again after about a minute it rebooted.
So, next, I monitored with adb logcat while doing the install. There was a lot of gunk in the log from other apps, so I tried again while enabling Developer Options "Don't keep activities". It was still too much text to monitor in a Command Prompt window, so I tried one more time using:
adb logcat > magic-crash.txt
to save in a text file. Here are the critical moments:
I/ActivityManager( 8603): START u0 {act=android.intent.action.VIEW dat=file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk typ=application/vnd.android.package-archive cmp=com.android.packageinstaller/.PackageInstallerActivity} from pid 17478
I/ActivityManager( 8603): Start proc com.android.packageinstaller for activity com.android.packageinstaller/.PackageInstallerActivity: pid=17705 uid=10044 gids={50044, 1028}
I/ActivityManager( 8603): START u0 {dat=file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk cmp=com.android.packageinstaller/.InstallAppProgress (has extras)} from pid 17705
I/ActivityManager( 8603): Start proc com.android.defcontainer for service com.android.defcontainer/.DefaultContainerService: pid=17730 uid=10013 gids={50013, 1028, 1015, 1023, 2001}
W/ActivityManager( 8603): No content provider found for permission revoke: file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk
I/ActivityManager( 8603): Start proc com.android.vending for broadcast com.android.vending/com.google.android.vending.verifier.PackageVerificationReceiver: pid=17744 uid=10047 gids={50047, 3003, 1028, 1015}
I/PackageManager( 8603): Verification timed out for file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk
I/PackageManager( 8603): Continuing with installation of file:///storage/emulated/0/Android/data/com.amazon.venezia/files/apks/f13e69c1-0c52-489c-95bc-ae7d0475afaf.apk
W/Watchdog( 8603): *** WATCHDOG KILLING SYSTEM PROCESS: Blocked in handler on PackageManager (PackageManager)
W/Watchdog( 8603): PackageManager stack trace:
W/Watchdog( 8603): at android.os.BinderProxy.transact(Native Method)
W/Watchdog( 8603): at com.android.internal.app.IMediaContainerService$Stub$Proxy.copyResource(IMediaContainerService.java:290)
W/Watchdog( 8603): at com.android.server.pm.PackageManagerService$FileInstallArgs.copyApk(PackageManagerService.java:7953)
W/Watchdog( 8603): at com.android.server.pm.PackageManagerService$PackageHandler.doHandleMessage(PackageManagerService.java:960)
W/Watchdog( 8603): at com.android.server.pm.PackageManagerService$PackageHandler.handleMessage(PackageManagerService.java:593)
W/Watchdog( 8603): at android.os.Handler.dispatchMessage(Handler.java:102)
W/Watchdog( 8603): at android.os.Looper.loop(Looper.java:137)
W/Watchdog( 8603): at android.os.HandlerThread.run(HandlerThread.java:61)
W/Watchdog( 8603): *** GOODBYE!
Does this give any clues to why this won't install without rebooting?
Incidentally I also tried to copy the 1.5 GB apk to my desktop and use "adb install -r". However I get this:
could not allocate buffer for 'magic140.apk'
rm failed for /data/local/tmp/magic140.apk, No such file or directory

Incidentally, I also tried taking a Titanium Backup of the 1.2.0 app and restoring the same version over top of itself. This, too, prompted a reboot with a similar logcat message.
Sent from my Nexus 5 using Tapatalk

Any advice would be appreciated. The same apk has no trouble installing on Nexus 5.
Sent from my Nexus 5 using Tapatalk

Update: I ended up going the brute force route. In TWRP recovery I replaced the existing APK version in /data/app/ with the new one, renamed it appropriately, applied chmod 644 and chown system.system to match. Starting it up now to see if that did the trick. Appears to work.

Phone app continuously crashing

First, some information about the device:
1. Samsung Galaxy S5 from TMobile
2. Has Lollipop installed (from OTA update)
3. Factory ROM, not rooted, bootloader still locked, no modifications whatsoever.
For some reason I am getting the "Unfortunately, Phone has stopped" popup continuously. This occurs from the moment I boot up (at lockscreen) and as soon as I press "OK", it comes up about 0.2 seconds later. Makes it very difficult to navigate the device menus.
I have looked at logcats and this exception is what occurs:
Code:
I/Telecom (10435): Call: CallerInfo received for ****: [email protected] { name null, phoneNumber non-null }
I/Telecom (10435): MissedCallNotifier: showMissedCallNotification
D/ScoverManager(10435): serviceVersion : 16908288
D/EcidContact(10435): ECID AOSP VERSION: 2.3.6
D/AndroidRuntime(10435): Shutting down VM
E/AndroidRuntime(10435): FATAL EXCEPTION: main
E/AndroidRuntime(10435): Process: com.android.server.telecom, PID: 10435
E/AndroidRuntime(10435): java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
E/AndroidRuntime(10435): at com.android.server.telecom.secutils.TelecomUtils.getPresentationString(TelecomUtils.java:2917)
E/AndroidRuntime(10435): at com.android.server.telecom.MissedCallNotifier.showMissedCallNotification(MissedCallNotifier.java:191)
E/AndroidRuntime(10435): at com.android.server.telecom.MissedCallNotifier$3$1.onCallerInfoChanged(MissedCallNotifier.java:617)
E/AndroidRuntime(10435): at com.android.server.telecom.Call.access$000(Call.java:74)
E/AndroidRuntime(10435): at com.android.server.telecom.Call$1.onQueryComplete(Call.java:165)
E/AndroidRuntime(10435): at com.android.internal.telephony.CallerInfoAsyncQuery$CallerInfoAsyncQueryHandler.onQueryComplete(CallerInfoAsyncQuery.java:343)
E/AndroidRuntime(10435): at android.content.AsyncQueryHandler.handleMessage(AsyncQueryHandler.java:344)
E/AndroidRuntime(10435): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(10435): at android.os.Looper.loop(Looper.java:145)
E/AndroidRuntime(10435): at android.app.ActivityThread.main(ActivityThread.java:5837)
E/AndroidRuntime(10435): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(10435): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(10435): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1388)
E/AndroidRuntime(10435): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1183)
V/ApplicationPolicy( 783): isApplicationStateBlocked userId 0 pkgname com.android.server.telecom
W/ActivityManager( 783): Process com.android.server.telecom has crashed too many times: killing!
I/dumpstate(10454): begin
D/StatusBarManagerService( 783): manageDisableList userId=0 what=0x0 pkg=WindowManager.LayoutParams
D/CrashAnrDetector( 783): processName: com.android.server.telecom
D/CrashAnrDetector( 783): broadcastEvent : com.android.server.telecom system_app_crash
W/ContextImpl( 783): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1701 com.android.server.analytics.data.collection.application.CrashAnrDetector.broadcastEvent:296 com.android.server.analytics.data.collection.application.CrashAnrDetector.processDropBoxEntry:254 com.android.server.analytics.data.collection.application.CrashAnrDetector.access$100:60 com.android.server.analytics.data.collection.application.CrashAnrDetector$1.onReceive:102
I/SurfaceFlinger( 245): id=21 createSurf (49x49),1 flag=4, Application Error: com.android.server.telecom
I/OpenGLRenderer( 783): Initialized EGL, version 1.4
I/OpenGLRenderer( 783): HWUI protection enabled for context , &this =0x9de366f0 ,&mEglDisplay = 1 , &mEglConfig = 8
E/android.os.Debug( 783): [email protected] > sdumpstate -k -t -z -d -o /data/log/dumpstate_app_error
I/ServiceManager( 345): Waiting for service AtCmdFwd...
D/PowerManagerService( 783): [input device light] handleInputDeviceLightOff
It seems to have something to do with telecom. I have removed the SIM card, SD card, etc. No difference. I have tried clearing app data for contacts, contacts storage, phone app, even "com.android.server.telecom" from ADB SHELL PM CLEAR command, but no change.
Does anyone know what the issue could be? What can I try to do (besides factory reset of course) to fix the issue? Thanks in advance. I can post more logcats if needed.

There are numerous bugs with system apps crashing with lolipop on the S5. My contacts app is constantly crashing, vzw, OTA.

Ended up doing a factory reset, which fixed the issue

I really didn't want to factory reset ?

You need to factory reset after upgrading from KK to LP

That's more of a personal preference. I've seen tons of upgrades on this phone that went fine.

Android.Addiction said:
Ended up doing a factory reset, which fixed the issue
Click to expand...
Click to collapse
Android.Addiction said:
That's more of a personal preference. I've seen tons of upgrades on this phone that went fine.
Click to expand...
Click to collapse
___________________

sensors (acceleration gyroscope orientation etc) issues, nv data dump request

Hello,
i got a D802 phone which apparently has some sensors disabled in some way. When apps try to use them (so the system see them as existent) they fail or crash.
here some example log:
-Orientation:
Code:
W/OrientationEventListener( 957): Cannot detect sensors. Invalid disable
-Calibration:
Code:
E/AndroidRuntime( 7456): java.lang.NullPointerException: Attempt to invoke virtual method 'int android.hardware.Sensor.getType()' on a null object reference
E/AndroidRuntime( 7456): at com.qualcomm.sensors.sensortest.SensorID$SensorTyp e.getSensorType(SensorID.java:61)
E/AndroidRuntime( 7456): at com.android.settings.lge.MotionSensorCalibration$C alThreadRunnable.run(MotionSensorCalibration.java: 228)
E/AndroidRuntime( 7456): at java.lang.Thread.run(Thread.java:818)
-Gravity:
Code:
I/SensorManager(14094): registerListenerImpl() [Sensor: LGE Gravity Sensor, Rate: 200000, SensorEventListener: [email protected]] by com.kfodor.MySensors.SensorView.registerSensorListener():735
D/sensors_hal_SAM( 949): batch:sensor(android.sensor.gravity) handle:29 freq:1 report_rate:1 max:1.000000 min:0.000000
D/sensors_hal_Gravity( 949): enable: handle=29
D/sensors_hal_Gravity( 949): enable: handle=29, freq=1 report_rate=1 batch_rate=0 batched=0 wakeup 0
D/sensors_hal_Gravity( 949): enable: handle=29 synchronous req
I/sensors_hal_SAM( 949): sendEnableReq:sensor(android.sensor.gravity) Sending enable to svc no:20
E/Sensors ( 474): sns_acm_mr.c(776):Request made to disabled service
E/Sensors ( 474): sns_main.c(1331):Error writing request. sns_err 3 error 0 qmi_err 0
E/sensors_hal_Gravity( 949): processResp: Msg 2; Result: 1, Error: 3
D/sensors_hal_Gravity( 949): enable: Received Response: 1
-Acceleration:
Code:
I/sensors_hal_SAM( 949): sendEnableReq:sensor(android.sensor.linear_acceleration) Sending enable to svc no:20
E/Sensors ( 474): sns_acm_mr.c(776):Request made to disabled service
E/Sensors ( 474): sns_main.c(1331):Error writing request. sns_err 3 error 0 qmi_err 0
E/sensors_hal_LinearAccel( 949): processResp: Msg 2; Result: 1, Error: 3
-Rotation:
Code:
I/sensors_hal_SAM( 949): sendEnableReq:sensor(android.sensor.rotation_vector) Sending enable to svc no:18
E/Sensors ( 474): sns_acm_mr.c(776):Request made to disabled service
E/Sensors ( 474): sns_main.c(1331):Error writing request. sns_err 3 error 0 qmi_err 0
E/sensors_hal_RV( 949): processResp: Msg 2; Result: 1, Error: 3
I/SensorManager(14094): removeAllSensors() [Sensor: LGE Rotation Vector Sensor] by com.kfodor.MySensors.SensorView.registerSensorListener():732
I followed a lot of paths to find a solution, different distributions and full revert to all available stock versions. no way.
As my last trial I want to try to compare my NV data with a working one to search for some misconfigured parameter.
I found a great guide on how to access and extract all NV parameters and save to a text file, here:
http://www.droidviews.com/how-to-bac...imei-on-lg-g2/
As you can see, the guide is for changing IMEI, but the application permit to dump all parameters to a file.
I ask some good man to send me his dump. or i can send mine and get the differences. Because this file contains sensitive data, they should be removed (IMEI, S/N, MAC) even if i am not interested in stealing ids!
I have a D802 32GB.
thank you to everyone, hope to receive some useful feedback!.
Fabio T

wear os app stuck at logo, does nothing...

Hello; This is happening in the latest two custom roms I've tested, being havoc os for chiron (xiaomi mi mix 2) the latest one:
The wear os app stuck at logo, nothing happens. Just installed the rom a few hours ago...
Tried:
Reinstalled the full super open google apps from twrp (just in case something were missing)
Reinstalled the app itself
Reset the watch (in fact, it's not related to the watch as the app itself in the phone is the one that hangs...)
These lines in the matlog makes me thing some service or related thing is missing in the havoc os (and other custom roms) :
04-14 14:43:44.071 W/ActivityManager( 1755): Unable to start service Intent { act=com.google.android.gms.wearable.BIND pkg=com.google.android.gms } U=0: not found
04-14 14:43:44.071 W/ActivityManager( 1755): Unbind failed: could not find connection for [email protected]
04-14 14:43:44.071 E/GmsClient(23038): unable to connect to service: com.google.android.gms.wearable.BIND on com.google.android.gms
04-14 14:43:44.072 W/ActivityManager( 1755): Unable to start service Intent { act=com.google.android.gms.wearable.BIND pkg=com.google.android.gms } U=0: not found
04-14 14:43:44.072 W/ActivityManager( 1755): Unbind failed: could not find connection for [email protected]
04-14 14:43:44.072 E/GmsClient(23038): unable to connect to service: com.google.android.gms.wearable.BIND on com.google.android.gms
04-14 14:43:44.099 W/ActivityManager( 1755): Unable to start service Intent { act=com.google.android.gms.wearable.BIND pkg=com.google.android.gms } U=0: not found
04-14 14:43:44.099 W/ActivityManager( 1755): Unbind failed: could not find connection for [email protected]
04-14 14:43:44.099 E/GmsClient(23038): unable to connect to service: com.google.android.gms.wearable.BIND on com.google.android.gms
Right now I cannot use the watch, it's waiting to be configured. So this is a pain in the a**
Thanks in advance !!!

Try another Gapps. Nikgapps should work for you.