Database Users

Eris msm_pm_wait_state reboot syndrome?

Hi folks,
Long time since I popped in here.
I'm wondering if you've seen behavior similar to this before:
Spontaneous reboots during suspend/resumes (that is, an app running but the screen is off) which *sometimes* result in output like this at the tail end of /proc/last_kmsg
Code:
[ 2331.773132] msm_pm_wait_state(80, 0, 0, 0) failed 10d29
[ 2331.773132] msm_sleep(): msm_pm_wait_state failed, 10d29
[ 2331.929382] msm_pm_wait_state(80, 0, 0, 0) failed 10d29
[ 2331.929382] msm_sleep(): msm_pm_wait_state failed, 10d29
No errors detected
I can manage to run logcat as a background process (the syndrome seems to involve the kernel PM (Power Management) suspend/resume function, as it refuses to occur when plugged in to USB); sometimes I also see
Code:
09-01 21:07:58.371 273 416 E RPC : error writing RPC packet: 22 (Invalid argument)
as the last line in the logcat. I don't know what is lost in the logcat output after that due to buffering, but the "No errors detected" in /proc/last_kmsg seems to point away from a kernel panic. And yet the phone reboots in a decidedly ungraceful fashion... if all filesystems were flushed I would expect to see something in the logcat about a reboot.
Test conditions:
Kernel: 2.6.29-DecaFuctCFS-dirty-9ff84b92 ([email protected]) (gcc version 4.4.0 (GCC) ) #5 PREEMPT Thu Jan 27 22:14:44 EST 2011
ROM: Condemned Soul's CCM7-V21 Vanilla
CM CPU min/max: 245/729 (* I don't think this matters)
Governor: ondemand
Other: Screen must be off and phone disconnected from external (USB) power for this reboot to occur; my test condition also includes the phone in Airplane mode. (I do not know if the latter is necessary for bug expression).
I can add more detail, but I didn't want my post to get too long. I can cause this to happen deterministically (a delay of one to several minutes before the phone reboots). The app involved uses the GPS hardware...
Anyhow... does this syndrome sound familiar at all?
bftb0
PS Yes this is a real-world scenario - I want to do GPS track recording in areas without cell/wifi service, so... running without USB power and no radios (for battery conservation) is a priority.

"ping" command seems to reboot Nexus 10 with various ROMs

I'm an app developer, and have now received three reports of Nexus 10s, each with a different ROM, rebooting immediately after the Linux "ping" command is invoked.
ROMs include, but are not limited to:
mrRobinson's buttered AOKP (reported 26 April 2013)
ParanoidAndroid 3.90 (reported 3 August 2013)
CM10.2 (reported 17 August 2013)
I believe the early first case is a 4.2 ROM, while the second two are 4.3.
The exact ping command I'm invoking is:
Code:
ping -n -w 6 -c 5 somecomputername
The options on that command are:
-n (no hostname lookup, numeric output only)
-w 6 (6 second deadline)
-c 5 (stop after sending at most 5 ECHO_REQUEST packets)
I'm guessing just "ping somecomputername" will cause the problem though.
I'm posting this because I'm curious to see how widespread the issue might be. As it stands I have no idea where to report it. There may be a problem somewhere upstream of these ROM developers, but whether that's in AOSP or in common code used in a variety of ROMs is unknown to me.
If anyone could kindly check whether there device reboots as result of a ping command, I'd greatly appreciate it. I'm especially interested in whether or not a stock device will do it. And obviously, please do bear in mind that the device might spontaneously reboot if you try this.
Thanks!

Code:
/ # ping -n -w 6 -c 5 www.cnn.com
PING cnn-56m.gslb.vgtf.net (157.166.248.11) 56(84) bytes of data.
--- cnn-56m.gslb.vgtf.net ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 5007ms
/ # ping -n -w 6 -c 5 www.spiegel.de
PING www.spiegel.de (62.138.116.3) 56(84) bytes of data.
64 bytes from 62.138.116.3: icmp_seq=1 ttl=246 time=38.5 ms
64 bytes from 62.138.116.3: icmp_seq=2 ttl=246 time=48.5 ms
64 bytes from 62.138.116.3: icmp_seq=3 ttl=246 time=45.5 ms
64 bytes from 62.138.116.3: icmp_seq=4 ttl=246 time=47.6 ms
64 bytes from 62.138.116.3: icmp_seq=5 ttl=246 time=47.0 ms
--- www.spiegel.de ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 38.520/45.452/48.500/3.603 ms
Works without reboot on flaming monkey, trinity_tn TX10.
BTW: -n only makes sense when pinging on addresses. -n suspresses reverse lookups but no lookups.

I'be forgotten to paste my third test: pinging an unresolveble hostname. Works without crash too.

I'll confirm I've got the same problem. Running Cyanogenmod (cm-10.2-20131102-SNAPSHOT-M1). All it takes is a ping <host> it reboots. Never noticed it until today. But never tried until today as far as I remember.

Android OS keeping phone awake even with clean flash

Hello,
So I was on a rooted stock firmware and noticed Android OS keeping my phone awake a lot and drainig battery. I cleaned caches, nothing. I then clean flashed, the same.
Now I reflashed the stock image XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml.zip, even the BTFM.bin which I almost didn't notice, and locked the phone up.
And now even on the newest stock firmware for my region (unrooted) it's still doing it. Out of a night on my nightstand, with moto display off, Android OS kept the phone awake for 4 hours, taking about 10% of the battery.
I did a dumpsys power if it's at all helpful:
Code:
POWER MANAGER (dumpsys power)
Power Manager State:
mDirty=0x0
mWakefulness=Asleep
mWakefulnessChanging=false
mIsPowered=true
mPlugType=2
mBatteryLevel=89
mBatteryLevelWhenDreamStarted=0
mDockState=0
mStayOn=false
mProximityPositive=false
mBootCompleted=true
mSystemReady=true
mHalAutoSuspendModeEnabled=true
mHalInteractiveModeEnabled=false
mWakeLockSummary=0x0
mUserActivitySummary=0x0
mRequestWaitForNegativeProximity=false
mSandmanScheduled=false
mSandmanSummoned=false
mLowPowerModeEnabled=false
mBatteryLevelLow=false
mDeviceIdleMode=false
mDeviceIdleWhitelist=[10000, 10019]
mDeviceIdleTempWhitelist=[]
mLastWakeTime=28711674 (328144 ms ago)
mLastSleepTime=28760836 (278982 ms ago)
mLastUserActivityTime=28714835 (324983 ms ago)
mLastUserActivityTimeNoChangeLights=28600112 (439706 ms ago)
mLastInteractivePowerHintTime=28765970 (273848 ms ago)
mLastScreenBrightnessBoostTime=0 (29039818 ms ago)
mScreenBrightnessBoostInProgress=false
mDisplayReady=true
mHoldingWakeLockSuspendBlocker=false
mHoldingDisplaySuspendBlocker=false
Settings and Configuration:
mDecoupleHalAutoSuspendModeFromDisplayConfig=false
mDecoupleHalInteractiveModeFromDisplayConfig=true
mWakeUpWhenPluggedOrUnpluggedConfig=true
mWakeUpWhenPluggedOrUnpluggedInTheaterModeConfig=false
mTheaterModeEnabled=false
mSuspendWhenScreenOffDueToProximityConfig=true
mDreamsSupportedConfig=true
mDreamsEnabledByDefaultConfig=true
mDreamsActivatedOnSleepByDefaultConfig=false
mDreamsActivatedOnDockByDefaultConfig=true
mDreamsEnabledOnBatteryConfig=false
mDreamsBatteryLevelMinimumWhenPoweredConfig=-1
mDreamsBatteryLevelMinimumWhenNotPoweredConfig=15
mDreamsBatteryLevelDrainCutoffConfig=5
mDreamsEnabledSetting=true
mDreamsActivateOnSleepSetting=false
mDreamsActivateOnDockSetting=true
mDozeAfterScreenOffConfig=true
mLowPowerModeSetting=false
mAutoLowPowerModeConfigured=false
mAutoLowPowerModeSnoozing=false
mMinimumScreenOffTimeoutConfig=10000
mMaximumScreenDimDurationConfig=7000
mMaximumScreenDimRatioConfig=0.20000005
mScreenOffTimeoutSetting=60000
mSleepTimeoutSetting=-1
mMaximumScreenOffTimeoutFromDeviceAdmin=2147483647 (enforced=false)
mStayOnWhilePluggedInSetting=0
mScreenBrightnessSetting=77
mScreenAutoBrightnessAdjustmentSetting=0.03515625
mScreenAutoBrightnessAdjustmentOverrideFromWindowManager=NaN
mScreenBrightnessModeSetting=1
mScreenBrightnessOverrideFromWindowManager=-1
mUserActivityTimeoutOverrideFromWindowManager=10000
mTemporaryScreenBrightnessSettingOverride=-1
mTemporaryScreenAutoBrightnessAdjustmentSettingOverride=NaN
mDozeScreenStateOverrideFromDreamManager=0
mDozeScreenBrightnessOverrideFromDreamManager=-1
mScreenBrightnessSettingMinimum=3
mScreenBrightnessSettingMaximum=255
mScreenBrightnessSettingDefault=77
mDoubleTapWakeEnabled=false
Sleep timeout: -1 ms
Screen off timeout: 10000 ms
Screen dim duration: 2000 ms
UID states:
UID 1000: 0
UID 1001: 0
UID 1027: 0
UID 1037: 16
UID u0a0: 6
UID u0a2: 0
UID u0a8: 16
UID u0a10: 16
UID u0a15: 16
UID u0a17: 10
UID u0a19: 3
UID u0a24: 16
UID u0a29: 10
UID u0a30: 10
UID u0a32: 10
UID u0a33: 6
UID u0a34: 6
UID u0a37: 10
UID u0a44: 6
UID u0a47: 0
UID u0a49: 3
UID u0a57: 16
UID u0a60: 5
UID u0a69: 16
UID u0a71: 16
UID u0a76: 5
UID u0a82: 7
UID u0a89: 10
UID u0a95: 16
UID u0a101: 16
UID u0a102: 12
UID u0a104: 16
UID u0a106: 10
UID u0a115: 16
UID u0a121: 16
UID u0a132: 10
UID u0a138: 16
UID u0a154: 16
UID u0a170: 16
UID u0a171: 6
UID u0a173: 4
UID u0a175: 10
UID u0a185: 16
UID u0a193: 16
UID u0i8: 15
UID u0i9: 5
Wake Locks: size=0
Suspend Blockers: size=4
PowerManagerService.WakeLocks: ref count=0
PowerManagerService.Display: ref count=0
PowerManagerService.Broadcasts: ref count=0
PowerManagerService.WirelessChargerDetector: ref count=0
Display Power: state=OFF
Wireless Charger Detector State:
mGravitySensor={Sensor name="Gravity", vendor="Motorola", version=1, type=9, maxRange=9.80665, resolution=2.9928435E-4, power=5.65, minDelay=10000}
mPoweredWirelessly=false
mAtRest=false
mRestX=0.0, mRestY=0.0, mRestZ=0.0
mDetectionInProgress=false
mDetectionStartTime=0 (never)
mMustUpdateRestPosition=false
mTotalSamples=0
mMovingSamples=0
mFirstSampleX=0.0, mFirstSampleY=0.0, mFirstSampleZ=0.0
mLastSampleX=0.0, mLastSampleY=0.0, mLastSampleZ=0.0
If anyone could help out I'd be grateful.

Is your phone a xt1572 or xt1575?

Problems with Video recording on PACROM MM.

EDIT: This has been resolved. Updating vendor blobs and device trees fixed the issue. Thank you for your time.
Greetings Developers,
I would really appreciate some help. By God's grace, in the T-Mobile S4 development thread http://forum.xda-developers.com/galaxy-s4-tmobile/development/rom-pac-rom-mm-t3400111 , I have put together several Marshmallow Roms, namely PAC Rom and AOKP MM, that have the same problem. The camera works to take pictures, but cannot record video. It "appears" to be recording in the built in camera app, but does not actually save the recording. If I use another app, such as OpenCamera, it stops the recording as soon as I try to start. I am relatively new to development, and any help would be greatly appreciated, as well as fully recognized and credited.
Below is the logcat errors/fails when using the CM camera app, and the OpenCamer app. I just really want to get this fixed for the people who are using the roms. I hate to sell them short because I've made some sort of error.
In my inexperienced opinion, this appears to be an audio problem. I have compared the mediarecorder.cpp and similar files between CM13 and my roms, and they are identical. I was wondering if it might be vendor blobs, so I borrowed them from Beanstalk (where the camera video recorder function works), but that did not work either.
I am pretty sure that it is not the app, because using any video recording app fails to actually record the video.
Code:
Here are the fails from the logcat. I am only focusing on the errors, stops, or fails.
Using the built in Camera app:
07-12 06:43:32.459 244 3766 I MediaCodecSource: encoder (audio) stopped
07-12 06:43:32.459 244 652 I MediaCodecSource: puller (audio) stopping
07-12 06:43:32.461 244 3847 E OMXNodeInstance: setConfig(1d:google.vorbis.decoder, ConfigPriority(0x6f800002)) ERROR: Undefined(0x80001001)
07-12 06:43:32.461 244 3847 I ACodec : codec does not support config priority (err -2147483648)
07-12 06:43:32.462 244 3847 I MediaCodec: MediaCodec will operate in async mode
07-12 06:43:32.467 244 3846 I NuPlayerDecoder: [OMX.google.vorbis.decoder] resubmitting CSD
07-12 06:43:32.468 244 3846 I NuPlayerDecoder: [OMX.google.vorbis.decoder] resubmitting CSD
07-12 06:43:32.469 244 3775 D ALSAStreamOps: setParameters(): keyRouting with device 0x0
07-12 06:43:32.469 244 3775 E ALSAStreamOps: must not change mDevices to 0
07-12 06:43:32.470 244 3775 D AudioStreamInALSA: standby
07-12 06:43:32.470 244 3775 D AudioStreamInALSA: standby
07-12 06:43:32.470 244 3775 D ALSADevice: standby: handle 0xb216c1c0 h 0x0
07-12 06:43:32.472 244 3848 W SoftVorbis: vorbis_dsp_synthesis returned -135
07-12 06:43:32.473 244 3848 W SoftVorbis: vorbis_dsp_synthesis returned -135
07-12 06:43:32.500 3612 3612 E MediaRecorder: stop failed: -1007
07-12 06:43:32.502 3612 3612 E CAM_VideoModule: java.lang.RuntimeException: stop failed.
07-12 06:43:33.984 244 3647 W AMessage: failed to post message as target looper for handler 0 is gone.
Using the OpenCamera App for comparison:
07-12 06:50:28.951 244 4439 E ACDB-LOADER: Error: ACDB EC_REF_RX returned = -8
07-12 06:50:28.976 244 4436 E SoftAVCEnc: Error in extractGraphicBuffer
07-12 06:50:28.976 244 4435 E ACodec : [OMX.google.h264.encoder] ERROR(0x80001001)
07-12 06:50:28.976 244 4435 E ACodec : signalError(omxError 0x80001001, internalError -2147483648)
07-12 06:50:28.976 244 4435 E ACodec : [OMX.google.h264.encoder] ERROR(0x80001001)
07-12 06:50:28.976 244 4435 E ACodec : signalError(omxError 0x80001001, internalError -2147483648)
07-12 06:50:28.977 244 4434 E MediaCodec: Codec reported err 0x80001001, actionCode 0, while in state 6
07-12 06:50:28.977 244 4439 D ALSADevice: setHardwareParams: buffer_size 16384, period_size 4096, period_cnt 4
07-12 06:50:28.977 244 4431 E MediaCodecSource: Encoder (video) reported error : 0x80001001
07-12 06:50:29.124 4180 4180 E MediaRecorder: stop failed: -1007
So, the errors or fails that are the same are these:
ACDB-LOADER: Error: ACDB EC_REF_RX returned = -8
MediaRecorder: stop failed: -1007
These are both audio errors. It appears that the audio is creating an error, so the video will not save. Unless someone out there knows better (be sure to correct me, I'm still learning). So I will be looking at MediaRecorder and ACDB-LOADER and audio problems.
Once again, any assistance would be greatly appreciated! Thanks!

Guyz,
I have A PAC ROM in My Lenovo Vibe K5 (GAPPS PICO PACKAGE INSTALLED) and The Rear Camera isn't working....
SPECS- Arm64
Android 6.0
Tell me how to fix this problem???????????????

Lumia 520 Unable to find a bootable option

Yesterday, I was running some apps (WeChat, Photo, etc) on my phone, but then my phone starts to lag, and suddenly restart by itself, and the following error appears after small NOKIA logo:
"ERROR: Unable to find a bootable option. Press any key to shutdown"
I've tried all possible solution I've found, which is:
1) Hard reset key combo: hold "volume down" until exclamation mark shown. (no exclamation mark shown for me)
2) Windows Device Recovery Tool
- it shown model phone is "Lumia phone" and Firmware version is unknown.
- When press install, it shown error once it starting to flash FFU, and show "Operation ended with failure. Software installation failed. Please try restarting your device, and try software installation again..."
3) Nokia Care Suite
- same as WDRT, when boot to flash mode, it shown error when the program try to flash FFU.
- FFU downloaded by WDRT, it shown error that said FFU is invalid
- FFU downloaded from http://lumiafirmware.com/ error message
Code:
DEV_REPORTED_ERROR_DURING_PROGRAMMING: 0x00030003
Exception:
Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.MurzimProgrammingException: DEV_REPORTED_ERROR_DURING_PROGRAMMING: 0x00030003
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__c(Object state)
4) "Unbrick Lumia without JTAG"
- THOR2 can't find connection on the following command
Code:
thor2 -mode emergency -hexfile HEX.hex -mbnfile msimage.mbn -orig_gpt
Error:
Code:
Debugging enabled for emergency
Initiating emergency download
Operation took about 11.00 seconds.
THOR2_ERROR_CONNECTION_NOT_FOUND
THOR2 1.8.2.18 exited with error code 84000 (0x14820)
- can't "flash" vpl to phone
Code:
thor2.exe -mode vpl -maxtransfersizekb 1 -vplfile C:\ProgramData\Nokia\Packages\Products\rm-915\XXX.vpl
Error
Code:
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2.exe -mode vpl -maxtransfersizekb 1 -vplfile C:\ProgramData\Microsoft\Packages\Products\RM-914\RM914_059S3J0_3058.50000.1425.0004_034.vpl
Process started Fri Sep 30 19:47:41 2016
Logging to file C:\Users\...\AppData\Local\Temp\thor2_win_20160930194741_ThreadId-4880.log
Parsing VPL file C:\ProgramData\Microsoft\Packages\Products\RM-914\RM914_059S3J0_3058.50000.1425.0004_034.vpl
Successfully parsed VPL
Flashing .ffu file RM914_3058.50000.1425.0004_RETAIL_apac_malaysia_307_04_441880_prd_signed.ffu (SW version 3058.50000.1425.0004)
Debugging enabled for uefiflash
Initiating FFU flash operation
WinUSB in use.
isDeviceInNcsdMode
isDeviceInNcsdMode is false
Device mode 6 Uefi mode
[THOR2_flash_state] Pre-programming operations
Disable timeouts
Get flashing parameters
Lumia Boot Manager detected
Check status of battery
State of charge 3, charging current 1
Warning: Battery level low. Charge battery to 10 % of max charge.
Protocol version 1.1 Implementation version 1.16
Detecting UEFI responder
HELLO success
Lumia Boot Manager detected
Check status of battery
State of charge 3, charging current 220
Warning: Battery level low. Charge battery to 10 % of max charge.
Protocol version 1.1 Implementation version 1.16
Booting to FlashApp
Reboot to FlashApp command sent successfully.
DetachFrom connection
Verifying that device is online
Device is online
Detecting UEFI responder
HELLO success
Lumia Flash detected
Protocol version 1.15 Implementation version 1.28
Disable timeouts
Get flashing parameters
Lumia Flash detected
Protocol version 1.15 Implementation version 1.28
Size of one transfer is 2363392
Size of buffer is 2359296
Number of eMMC sectors: 15269888
Platform ID of device: Nokia.MSM8227.P6036.1.2
Async protocol version: 01
Security info:
Platform secure boot disabled
Secure FFU disabled
JTAG eFuse blown
RDC not found
Authentication not done
UEFI secure boot enabled
SHK enabled
Device supports FFU protocols: 0019
[THOR2_flash_state] Device programming started
Using secure flash method
CoreProgrammer version 2015.06.10.001.
Start programming signed ffu file C:\ProgramData\Microsoft\Packages\Products\RM-914\RM914_3058.50000.1425.0004_RETAIL_apac_malaysia_307_04_441880_prd_signed.ffu
FfuReader version is 2015061501
Send FlashApp write parameter: 0x4d544f00
Perform handshake with UEFI...
Flash app: Protocol Version 1.15 Implementation Version 1.28
DevicePlatformInfo: Nokia.MSM8227.P6036.1.2
Unknown sub block detected. Skip...
Unknown sub block detected. Skip...
Supported protocol versions bitmap is 19
Secure FFU sync version 1 supported.
Secure FFU async version 1 supported.
Secure FFU async version 3 supported.
Get CID of the device...
Get EMMC size of the device...
Emmc size in sectors: 15269888
CID: Samsung, Size 7456 MB
Start charging...
Requested write param 0x43485247 is not supported by this flash app version.
Start charging... DONE. Status = 0
Unable to send ECHO REQ or ECHO REQ not supported
Get security Status...
Security Status:
Platform secure boot is disabled.
Secure eFUSE is disabled.
JTAG is disabled.
RDC is missing from the device.
Authentication is not done.
UEFI secure boot is enabled.
Secondary HW key exists.
Get ISSW Version...
Get ISSW Version, SKIPPED!
Get system memory size...
Size of system mem: 524288 KB
Read antitheft status...
Requested read param 0x41545250 is not supported by this flash app version.
Send backup to RAM req...
Clearing the backup GPT, startsector = 15269854
UEFI returned error: 4
Clear GPT has failed!
Operation took about 9.00 seconds.
Unknown error code.
THOR2 1.8.2.18 exited with error code 196611 (0x30003)
5) Try to flash FFU with WPInternal
- Doesn't work for flashing FFU (Error shown when trying to flash, Error 0x1106: Security header validation failed)
- Somehow flashing separate partitions (EFIESP, MainOS, Data) works, but I've flash old ROM that I've backup doesn't work
- able to boot to mass storage mode, able to read, able to backup (don't know about write)
Please help me, I've tried all of these above and my phone still bricked :crying:

Did you find the solution and unbrick your phone?

It sounds like the Flash memory in your phone is going bad or at least has some bad blocks. The error states that the phone reported an error while trying to flash over the image

i connect not one, 3-4 pieces to jtag riff box. the problem is emmc/nand memory, this chip have a bug, is not the only one have this problem.
the state of the memory chip is READ ONLY!, so you can't write this.
one box apear and change the state of the memory on other phones with same kind of problem. need to send some special command to emmc to change the state.