Related
So i have two nexus's one is perfect. However I also have my old one (before htc sent me the new one) it has a major problem were the phone will usually not boot and if it does after a few minutes of use will reboot and vibrate a bunch of times.
So what do you guys think could be the problem??? I'm thinking the logic board?
I'm asking because i am thinking about fixing it myself
Do an ADB logcat.
The phone doesn't have to completely boot to start it. This is the best way to determine at what point the phone stops. I use these when I get a boot loop.
K I will try that and post back
Sent from my Nexus One using XDA App
Search the forum using "vibrations" keyword.
Ok so i plugged her in and it booted up. So i ran adb logcat and started messing around. It crashed while recording this is the last couple lines... I don't know how to copy from cmd???? So have type it out
Code:
E/CameraInput < 59>: Recording is not ready <iPeer 0x1fc94 iState 2 iWriteState
1 iClockState 0>, frame dropped
I/AudioHardwareQSD< 59>: AudioHardware pcm playback is going to standby.
And that's it thats last thing before it crashed and turned off... Any ideas what means in english? something about audio but i don't know if that is realated
EDIT: And yes it is the seven vibrations problem
What radio are you using?
Jack_R1 said:
What radio are you using?
Click to expand...
Click to collapse
5.12 right now but i have tried all of them. Same problem. Almost all the kernels and roms too. from stock to cyanogen to miui.
Non make a difference. The phone clearly has a hardware problem i just want to identify which piece of hardware
"adb bugreport" will help much more.
Also, "cat /proc/kmsg" and "cat /proc/last_kmsg", too.
Clear cache
Sent from my Nexus One using XDA App
I have cleared cache a hundred times...
I am going to try the other adb commands
Tech_Boy said:
Ok so i plugged her in and it booted up. So i ran adb logcat and started messing around.
It crashed while recording this is the last couple lines... I don't know how to copy from cmd???? So have type it out
Click to expand...
Click to collapse
Right click anywhere in the window itself and select: edit, then select all
After everything is highlighted again right click on anywhere on the window and select: edit, then copy
You can then paste this into a notepad to edit it, or whatever.
Also as mentioned, try adb bugreport as well that could help.
Ok this is what i got. I don't understand much of it, so i don't know what i am looking for.
I ran the first two the third gave a file no found error... Also I notice cmd didn't copy the whole thing, like when it reaches a certain amount of lines it cuts off the top stuff
Code:
en=1 layout=34 uiMode=17 seq=4}
mShownFrame=[0,0][480,800] last=[0,0][480,800]
mFrame=[0,0][480,800] last=[0,0][480,800]
mContainingFrame=[0,0][480,800] mDisplayFrame=[0,0][480,800]
mContentFrame=[0,38][480,800] mVisibleFrame=[0,38][480,800]
mContentInsets=[0,38][0,0] last=[0,38][0,0] mVisibleInsets=[0,38][0,0] last=
[0,38][0,0]
mDrawPending=false mCommitDrawPending=false mReadyToShow=false mHasDrawn=tru
e
Window #2 Window{44ac0690 SurfaceView paused=false}:
mSession=Session{44b399c8 uid 10028} [email protected]
mAttrs=WM.LayoutParams{(0,38)(480x762) gr=#33 ty=1000 fl=#24218 fmt=-3}
mAttachedWindow=Window{44b7ce48 com.android.launcher/com.android.launcher2.L
auncher paused=false} mLayoutAttached=true
mBaseLayer=21000 mSubLayer=1 mAnimLayer=21010+0=21010 mLastLayer=21010
mToken=WindowToken{44ac0630 [email protected]}
mRootToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.
launcher/com.android.launcher2.Launcher}}
mAppToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.l
auncher/com.android.launcher2.Launcher}}
mViewVisibility=0x8 mLastHidden=true mHaveFrame=true mObscured=true
mPolicyVisibility=true mPolicyVisibilityAfterAnim=true mAttachedHidden=true
Requested w=480 h=762 mLayoutSeq=316
mGivenContentInsets=[0,0][0,0] mGivenVisibleInsets=[0,0][0,0]
mConfiguration={ scale=1.0 imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=3/1 ori
en=1 layout=34 uiMode=17 seq=4}
mShownFrame=[0,38][480,800] last=[0,38][480,800]
mFrame=[0,38][480,800] last=[0,38][480,800]
mContainingFrame=[0,0][480,800] mDisplayFrame=[-10000,-10000][10000,10000]
mContentFrame=[0,38][480,800] mVisibleFrame=[0,38][480,800]
mContentInsets=[0,0][0,0] last=[0,0][0,0] mVisibleInsets=[0,0][0,0] last=[0,
0][0,0]
mDrawPending=false mCommitDrawPending=false mReadyToShow=false mHasDrawn=tru
e
Window #1 Window{44b7ce48 com.android.launcher/com.android.launcher2.Launcher
paused=false}:
mSession=Session{44b399c8 uid 10028} [email protected]
mAttrs=WM.LayoutParams{(0,0)(fillxfill) sim=#20 ty=1 fl=#110100 fmt=-2 wanim
=0x1030001}
mBaseLayer=21000 mSubLayer=0 mAnimLayer=21005+0=21005 mLastLayer=21005
mToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.laun
cher/com.android.launcher2.Launcher}}
mRootToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.
launcher/com.android.launcher2.Launcher}}
mAppToken=AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.l
auncher/com.android.launcher2.Launcher}}
mViewVisibility=0x8 mLastHidden=true mHaveFrame=true mObscured=true
Requested w=480 h=800 mLayoutSeq=316
mGivenContentInsets=[0,0][0,0] mGivenVisibleInsets=[0,0][0,0]
mConfiguration={ scale=1.0 imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=3/1 ori
en=1 layout=34 uiMode=17 seq=4}
mShownFrame=[0,0][480,800] last=[0,0][480,800]
mFrame=[0,0][480,800] last=[0,0][480,800]
mContainingFrame=[0,0][480,800] mDisplayFrame=[0,0][480,800]
mContentFrame=[0,38][480,800] mVisibleFrame=[0,38][480,800]
mContentInsets=[0,38][0,0] last=[0,38][0,0] mVisibleInsets=[0,38][0,0] last=
[0,38][0,0]
mDrawPending=false mCommitDrawPending=false mReadyToShow=false mHasDrawn=tru
e
mWallpaperX=0.5 mWallpaperY=0.0
mWallpaperXStep=0.25 mWallpaperYStep=0.0
Window #0 Window{44aa38e8 com.android.wallpaper.nexus.NexusWallpaper paused=fa
lse}:
mSession=Session{44a8e370 uid 10029} [email protected]
mAttrs=WM.LayoutParams{(0,0)(fillxfill) gr=#33 ty=2013 fl=#318 fmt=-1 wanim=
0x1030075}
mIsImWindow=false mIsWallpaper=true mIsFloatingLayer=true mWallpaperVisible=
false
mBaseLayer=21000 mSubLayer=0 mAnimLayer=21000+0=21000 mLastLayer=21000
mSurface=Surface(name=com.android.wallpaper.nexus.NexusWallpaper, identity=4
)
Surface: shown=false layer=21000 alpha=1.0 rect=(0,0) 480 x 800
mToken=WindowToken{449909f0 [email protected]}
mRootToken=WindowToken{449909f0 [email protected]}
mViewVisibility=0x0 mLastHidden=true mHaveFrame=true mObscured=true
Requested w=-1 h=-1 mLayoutSeq=318
mGivenContentInsets=[0,0][0,0] mGivenVisibleInsets=[0,0][0,0]
mConfiguration={ scale=1.0 imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=3/1 ori
en=1 layout=34 uiMode=17 seq=4}
mShownFrame=[0,0][480,800] last=[0,0][480,800]
mFrame=[0,0][480,800] last=[0,0][480,800]
mContainingFrame=[0,0][480,800] mDisplayFrame=[-10000,-10000][10000,10000]
mContentFrame=[0,0][480,800] mVisibleFrame=[0,0][480,800]
mContentInsets=[0,0][0,0] last=[0,0][0,0] mVisibleInsets=[0,0][0,0] last=[0,
0][0,0]
mAnimating=false mLocalAnimating=false mAnimationIsEntrance=true mAnimation=
null
mDrawPending=false mCommitDrawPending=false mReadyToShow=false mHasDrawn=tru
e
mWallpaperX=0.5 mWallpaperY=0.0
mWallpaperXStep=0.25 mWallpaperYStep=0.0
All active sessions:
Session Session{44bcab88 uid 1000}:
mNumWindow=3 mClientDead=false [email protected]
4a1cd90
Session Session{44b399c8 uid 10028}:
mNumWindow=2 mClientDead=false [email protected]
49a1ed8
Session Session{44a8e370 uid 10029}:
mNumWindow=1 mClientDead=false [email protected]
4960760
Session Session{44ac1528 uid 10018}:
mNumWindow=0 mClientDead=false [email protected]
49c5ee0
Session Session{44af3498 uid 1000}:
mNumWindow=3 mClientDead=false [email protected]
4af4eb8
All tokens:
Token null:
token=null
windows=[Window{44af4960 StatusBar paused=false}, Window{44b24fa0 TrackingVi
ew paused=false}, Window{44af8488 StatusBarExpanded paused=false}]
windowType=-1 hidden=false hasVisible=true
Token [email protected]:
[email protected]
windows=[]
windowType=2011 hidden=false hasVisible=false
Token HistoryRecord{44b27e28 com.android.launcher/com.android.launcher2.Launch
er}:
token=HistoryRecord{44b27e28 com.android.launcher/com.android.launcher2.Laun
cher}
windows=[Window{44b7ce48 com.android.launcher/com.android.launcher2.Launcher
paused=false}]
windowType=2 hidden=true hasVisible=true
app=true
allAppWindows=[Window{44b7ce48 com.android.launcher/com.android.launcher2.La
uncher paused=false}, Window{44ac0690 SurfaceView paused=false}]
groupId=5 appFullscreen=true requestedOrientation=5
hiddenRequested=true clientHidden=true willBeHidden=false reportedVisible=fa
lse
numInterestingWindows=3 numDrawnWindows=3 inPendingTransaction=false allDraw
n=true
startingData=null removed=false firstWindowDrawn=true
Token [email protected]:
[email protected]
windows=[Window{44aa38e8 com.android.wallpaper.nexus.NexusWallpaper paused=f
alse}]
windowType=2013 hidden=true hasVisible=true
Token HistoryRecord{44ae2d88 com.android.settings/.DevelopmentSettings}:
token=HistoryRecord{44ae2d88 com.android.settings/.DevelopmentSettings}
windows=[Window{44b4d8a0 com.android.settings/com.android.settings.Developme
ntSettings paused=false}]
windowType=2 hidden=false hasVisible=true
app=true
allAppWindows=[Window{44b4d8a0 com.android.settings/com.android.settings.Dev
elopmentSettings paused=false}]
groupId=6 appFullscreen=true requestedOrientation=-1
hiddenRequested=false clientHidden=false willBeHidden=false reportedVisible=
false
numInterestingWindows=2 numDrawnWindows=2 inPendingTransaction=false allDraw
n=true
startingData=null removed=false firstWindowDrawn=true
Token [email protected]:
[email protected]
windows=[Window{44ac0690 SurfaceView paused=false}]
windowType=-1 hidden=false hasVisible=true
Token HistoryRecord{44afab70 com.android.setupwizard/.SetupWizardActivity}:
token=HistoryRecord{44afab70 com.android.setupwizard/.SetupWizardActivity}
windows=[]
windowType=2 hidden=true hasVisible=true
app=true
groupId=2 appFullscreen=true requestedOrientation=-1
hiddenRequested=true clientHidden=true willBeHidden=false reportedVisible=fa
lse
numInterestingWindows=1 numDrawnWindows=1 inPendingTransaction=false allDraw
n=true
Token HistoryRecord{44a9bb18 com.android.settings/.ApplicationSettings}:
token=HistoryRecord{44a9bb18 com.android.settings/.ApplicationSettings}
windows=[Window{44b446f8 com.android.settings/com.android.settings.Applicati
onSettings paused=false}]
windowType=2 hidden=true hasVisible=true
app=true
allAppWindows=[Window{44b446f8 com.android.settings/com.android.settings.App
licationSettings paused=false}]
groupId=6 appFullscreen=true requestedOrientation=-1
hiddenRequested=true clientHidden=true willBeHidden=false reportedVisible=fa
lse
numInterestingWindows=1 numDrawnWindows=1 inPendingTransaction=false allDraw
n=true
startingData=null removed=false firstWindowDrawn=true
Token HistoryRecord{44beca80 com.android.settings/.Settings}:
token=HistoryRecord{44beca80 com.android.settings/.Settings}
windows=[Window{44b2c1d8 com.android.settings/com.android.settings.Settings
paused=false}]
windowType=2 hidden=true hasVisible=true
app=true
allAppWindows=[Window{44b2c1d8 com.android.settings/com.android.settings.Set
tings paused=false}]
groupId=6 appFullscreen=true requestedOrientation=-1
hiddenRequested=true clientHidden=true willBeHidden=false reportedVisible=fa
lse
numInterestingWindows=1 numDrawnWindows=1 inPendingTransaction=false allDraw
n=true
startingData=null removed=false firstWindowDrawn=true
startingWindow=null startingView=null startingDisplayed=true startingMovedfa
lse
Window token list:
#0: WindowToken{44af47b0 token=null}
#1: AppWindowToken{44afc5a8 token=HistoryRecord{44afab70 com.android.setupwiza
rd/.SetupWizardActivity}}
#2: WindowToken{449909f0 [email protected]}
#3: WindowToken{44ae24d0 [email protected]}
#4: AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.launcher/
com.android.launcher2.Launcher}}
#5: WindowToken{44ac0630 [email protected]}
#6: AppWindowToken{44becd60 token=HistoryRecord{44beca80 com.android.settings/
.Settings}}
#7: AppWindowToken{44becb90 token=HistoryRecord{44a9bb18 com.android.settings/
.ApplicationSettings}}
#8: AppWindowToken{44bd6e30 token=HistoryRecord{44ae2d88 com.android.settings/
.DevelopmentSettings}}
Wallpaper tokens:
Wallpaper #0 WindowToken{449909f0 [email protected]}:
[email protected]
windows=[Window{44aa38e8 com.android.wallpaper.nexus.NexusWallpaper paused=f
alse}]
windowType=2013 hidden=true hasVisible=true
Application tokens in Z order:
App #4: AppWindowToken{44bd6e30 token=HistoryRecord{44ae2d88 com.android.setti
ngs/.DevelopmentSettings}}
App #3: AppWindowToken{44becb90 token=HistoryRecord{44a9bb18 com.android.setti
ngs/.ApplicationSettings}}
App #2: AppWindowToken{44becd60 token=HistoryRecord{44beca80 com.android.setti
ngs/.Settings}}
App #1: AppWindowToken{44b8c8a8 token=HistoryRecord{44b27e28 com.android.launc
her/com.android.launcher2.Launcher}}
App #0: AppWindowToken{44afc5a8 token=HistoryRecord{44afab70 com.android.setup
wizard/.SetupWizardActivity}}
mCurrentFocus=Window{44b4d8a0 com.android.settings/com.android.settings.Develo
pmentSettings paused=false}
mLastFocus=Window{44b4d8a0 com.android.settings/com.android.settings.Developme
ntSettings paused=false}
mFocusedApp=AppWindowToken{44bd6e30 token=HistoryRecord{44ae2d88 com.android.s
ettings/.DevelopmentSettings}}
mInputMethodTarget=null
mInputMethodWindow=null
mWallpaperTarget=null
mCurConfiguration={ scale=1.0 imsi=0/0 loc=en_US touch=3 keys=1/1/2 nav=3/1 or
ien=1 layout=34 uiMode=17 seq=4}
mInTouchMode=true mLayoutSeq=345
mSystemBooted=true mDisplayEnabled=true
mLayoutNeeded=false mBlurShown=false
mDimShown=true current=0.0 target=0.0 delta=-0.004 lastAnimTime=0
mInputMethodAnimLayerAdjustment=0 mWallpaperAnimLayerAdjustment=0
mLastWallpaperX=0.5 mLastWallpaperY=0.0
mDisplayFrozen=false mWindowsFreezingScreen=false mAppsFreezingScreen=0 mWaiti
ngForConfig=false
mRotation=0, mForcedAppOrientation=-1, mRequestedRotation=0
mAnimationPending=false mWindowAnimationScale=1.0 mTransitionWindowAnimationSc
ale=1.0
mNextAppTransition=0xffffffff, mAppTransitionReady=false, mAppTransitionRunnin
g=false, mAppTransitionTimeout=false
mStartingIconInTransition=false, mSkipAppTransitionAnimation=false
mLastEnterAnimToken=AppWindowToken{44bd6e30 token=HistoryRecord{44ae2d88 com.a
ndroid.settings/.DevelopmentSettings}}, mLastEnterAnimParams=WM.LayoutParams{(0,
0)(fillxfill) sim=#110 ty=1 fl=#10100 fmt=-1 wanim=0x1030001}
DisplayWidth=480 DisplayHeight=800
KeyWaiter state:
mLastWin=null mLastBinder=null
mFinished=true mGotFirstWindow=true mEventDispatching=true mTimeToSwitch=0
[dumpsys: 3.3s elapsed]
C:\android-sdk-windows\tools>
Code:
<6>[ 5.608520] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 64000000 Hz
<6>[ 5.608764] mmc0: Slot eject status = 1
<6>[ 5.608886] mmc0: Power save feature enable = 1
<6>[ 5.609039] mmc0: DM non-cached buffer at ffa04000, dma_addr 0x279bd000
<6>[ 5.609283] mmc0: DM cmd busaddr 0x279bd000, cmdptr busaddr 0x279bd300
<6>[ 5.610229] mmc1: Qualcomm MSM SDCC at 0x00000000a0400000 irq 26,0 dma 8
<6>[ 5.610443] mmc1: 4 bit data mode enabled
<6>[ 5.610595] mmc1: MMC clock 144000 -> 50000000 Hz, PCLK 64000000 Hz
<6>[ 5.610839] mmc1: Slot eject status = 0
<6>[ 5.610961] mmc1: Power save feature enable = 1
<6>[ 5.611206] mmc1: DM non-cached buffer at ffa05000, dma_addr 0x279be000
<6>[ 5.611328] mmc1: DM cmd busaddr 0x279be000, cmdptr busaddr 0x279be300
<6>[ 5.612396] logger: created 64K log 'log_main'
<6>[ 5.612640] logger: created 256K log 'log_events'
<6>[ 5.612945] logger: created 64K log 'log_radio'
<6>[ 5.613128] logger: created 64K log 'log_system'
<4>[ 5.613586] GACT probability NOT on
<4>[ 5.613800] Mirror/redirect action on
<4>[ 5.613952] u32 classifier
<4>[ 5.614074] Actions configured
<4>[ 5.614318] Netfilter messages via NETLINK v0.30.
<4>[ 5.614501] nf_conntrack version 0.5.0 (6171 buckets, 24684 max)
<4>[ 5.614929] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Plea
se use
<4>[ 5.615081] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack modu
le option or
<4>[ 5.615295] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
<4>[ 5.615570] ctnetlink v0.93: registering with nfnetlink.
<6>[ 5.616058] xt_time: kernel timezone is -0000
<6>[ 5.616394] ip_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 5.616729] arp_tables: (C) 2002 David S. Miller
<6>[ 5.616943] TCP cubic registered
<6>[ 5.617279] NET: Registered protocol family 10
<6>[ 5.617980] lo: Disabled Privacy Extensions
<6>[ 5.618896] Mobile IPv6
<6>[ 5.619049] IPv6 over IPv4 tunneling driver
<6>[ 5.619720] sit0: Disabled Privacy Extensions
<6>[ 5.620330] ip6tnl0: Disabled Privacy Extensions
<6>[ 5.620666] NET: Registered protocol family 17
<6>[ 5.620819] NET: Registered protocol family 15
<6>[ 5.620971] Bluetooth: L2CAP ver 2.14
<6>[ 5.621215] Bluetooth: L2CAP socket layer initialized
<6>[ 5.621337] Bluetooth: SCO (Voice Link) ver 0.6
<6>[ 5.621582] Bluetooth: SCO socket layer initialized
<6>[ 5.621917] Bluetooth: RFCOMM TTY layer initialized
<6>[ 5.622070] Bluetooth: RFCOMM socket layer initialized
<6>[ 5.622314] Bluetooth: RFCOMM ver 1.11
<6>[ 5.622436] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
<6>[ 5.622680] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
<6>[ 5.622894] ThumbEE CPU extension supported.
<6>[ 5.623596] clock_late_init() disabled 18 unused clocks
<4>[ 5.623809] mahimahi_wifi_init: start
<6>[ 5.624206] VFP support v0.3: implementor 51 architecture 0 part 0f varian
t 0 rev 1
<4>[ 5.652435] regulator_init_complete: incomplete constraints, leaving ldo2
on
<4>[ 5.653320] regulator_init_complete: incomplete constraints, leaving ldo1
on
<4>[ 5.654083] regulator_init_complete: incomplete constraints, leaving dcdc3
on
<4>[ 5.654968] regulator_init_complete: incomplete constraints, leaving dcdc2
on
<4>[ 5.655853] regulator_init_complete: incomplete constraints, leaving dcdc1
on
<6>[ 5.657379] rs30000048:00010000 rs30000048:00010000: setting system clock
to 2010-11-23 19:51:55 UTC (1290541915)
<6>[ 5.657714] Freeing init memory: 120K
<4>[ 5.657867] Warning: unable to open an initial console.
<6>[ 5.745422] keychord: using input dev h2w headset for fevent
<6>[ 5.745574] keychord: using input dev mahimahi-keypad for fevent
<6>[ 5.745971] keychord: using input dev mahimahi-nav for fevent
<6>[ 5.748168] yaffs: dev is 32505859 name is "mtdblock3"
<6>[ 5.748443] yaffs: passed flags ""
<4>[ 5.748565] yaffs: Attempting MTD mount on 31.3, "mtdblock3"
<4>[ 5.915313] mmc1: host does not support reading read-only switch. assuming
write-enable.
<6>[ 5.915496] mmc1: new high speed SDHC card at address aaaa
<6>[ 5.916229] mmcblk0: mmc1:aaaa SU04G 3.69 GiB
<6>[ 5.916625] mmcblk0: p1
<4>[ 5.956512] yaffs: restored from checkpoint
<4>[ 5.956970] yaffs_read_super: isCheckpointed 1
<6>[ 5.996093] yaffs: dev is 32505861 name is "mtdblock5"
<6>[ 5.996337] yaffs: passed flags ""
<4>[ 5.996459] yaffs: Attempting MTD mount on 31.5, "mtdblock5"
<6>[ 6.100860] batt: 83%, 4030 mV, -237 mA (0 avg), 27.0 C, 1128 mAh
<6>[ 6.108581] batt: charging OFF
<4>[ 6.298553] block 164 is bad
<4>[ 6.373718] block 410 is bad
<4>[ 6.429870] block 594 is bad
<4>[ 6.436859] block 617 is bad
<4>[ 6.514953] block 873 is bad
<4>[ 6.581939] block 1092 is bad
<4>[ 6.585266] block 1103 is bad
<4>[ 6.612121] block 1191 is bad
<4>[ 6.626129] block 1237 is bad
<4>[ 7.622741] yaffs_read_super: isCheckpointed 0
<6>[ 7.628631] yaffs: dev is 32505860 name is "mtdblock4"
<6>[ 7.628753] yaffs: passed flags ""
<4>[ 7.628997] yaffs: Attempting MTD mount on 31.4, "mtdblock4"
<4>[ 7.773559] block 93 is bad
<4>[ 7.794616] block 162 is bad
<4>[ 7.836578] block 299 is bad
<4>[ 7.836853] block 300 is bad
<4>[ 7.903015] block 519 is bad
<4>[ 7.987426] yaffs_read_super: isCheckpointed 0
<3>[ 8.017700] init: service 'console' requires console
<3>[ 8.062011] init: cannot execve('/system/etc/install-recovery.sh'): Permis
sion denied
<3>[ 8.110382] init: cannot find '/system/bin/dspcrashd', disabling 'dspcrash
d'
<6>[ 8.125823] acpuclk_set_vdd_level got regulator
<6>[ 8.545745] warning: `rild' uses 32-bit capabilities (legacy support in us
e)
<6>[ 8.679840] SMD: ch 0 1 -> 2
<6>[ 8.681640] qmi: smd closed
<6>[ 8.682006] SMD: ch 50 1 -> 2
<6>[ 8.682312] qmi: smd opened
<6>[ 8.683135] qmi: smd closed
<6>[ 8.683471] SMD: ch 51 1 -> 2
<6>[ 8.683807] qmi: smd opened
<6>[ 8.684265] qmi: ctl: wds use client_id 0x01
<6>[ 8.684936] qmi: ctl: wds use client_id 0x01
<6>[ 8.685455] qmi: smd closed
<6>[ 8.685913] SMD: ch 52 1 -> 2
<6>[ 8.686523] qmi: smd opened
<6>[ 8.687438] qmi: ctl: wds use client_id 0x01
<6>[ 9.907592] a1026_bootup_init: starting to load image (863 passes)...
<6>[ 12.805664] a1026_bootup_init: firmware loaded successfully
<6>[ 12.966003] a1026_bootup_init: initialized!
<6>[ 12.968688] htc-acoustic: open
<3>[ 12.969726] smd_alloc_channel() cid 41 does not exist
<3>[ 12.969848] smd_alloc_channel() cid 47 does not exist
<6>[ 12.973327] htc-acoustic: mmap
<6>[ 12.973541] htc-acoustic: ioctl
<6>[ 12.973632] htc-acoustic: ioctl: ACOUSTIC_UPDATE_ADIE called 59.
<6>[ 12.976440] htc-acoustic: ioctl: ONCRPC_UPDATE_ADIE_PROC success.
<6>[ 12.977264] htc-acoustic: release
<6>[ 12.997161] audio: init: codecs
<6>[ 12.997375] SMD: ch 43 1 -> 2
<6>[ 13.109802] dal_attach: status = 0, name = 'DAL_AQ_AUD'
<6>[ 13.109985] audio: init: INIT
<6>[ 13.110290] audio: init: OPEN control
<6>[ 13.495880] audio: init: attach ACDB
<6>[ 13.496215] SMD: ch 48 1 -> 2
<6>[ 13.606018] dal_attach: status = 0, name = 'DAL_AM_AUD'
<6>[ 13.606140] audio: init: attach ADIE
<6>[ 13.606628] dal_attach: status = 0, name = 'DAL_AM_AUD'
<6>[ 17.041503] lcdc_unblank: ()
<6>[ 17.041748] samsung_oled_panel_unblank: +()
<6>[ 17.256103] msm_kgsl: initilized dev=1 mmu=on
<6>[ 17.256561] misc kgsl: firmware: requesting yamato_pm4.fw
<6>[ 17.263732] misc kgsl: firmware: requesting yamato_pfp.fw
<3>[ 17.265991] init: untracked pid 87 exited
<3>[ 17.271881] init: untracked pid 88 exited
<6>[ 17.325988] samsung_oled_panel_unblank: -()
<6>[ 25.646606] capella_cm3602_open
<6>[ 25.647003] capella_cm3602_ioctl cmd 2
<6>[ 25.647918] capella_cm3602_disable
<6>[ 25.648040] capella_cm3602_disable: already disabled
<6>[ 25.648162] capella_cm3602_ioctl cmd 1
<6>[ 25.655303] request_suspend_state: wakeup (3->0) at 21809722976 (2010-11-2
3 19:52:15.497955355 UTC)
<6>[ 25.672088] capella_cm3602_ioctl cmd 1
<6>[ 32.422729] request_suspend_state: sleep (0->3) at 28577117998 (2010-11-23
19:52:22.265350377 UTC)
<6>[ 32.422851] capella_cm3602_ioctl cmd 1
<7>[ 32.423767] flashlight_control: mode 0 -> 0
<6>[ 32.423767] flashlight_control: off
<6>[ 32.426666] capella_cm3602_ioctl cmd 1
<6>[ 32.439849] lcdc_blank: ()
<6>[ 32.439971] samsung_oled_panel_blank: +()
<6>[ 32.645751] samsung_oled_panel_blank: -()
<6>[ 32.647949] mahimahi_ts_power: power 0
<6>[ 32.655822] lcdc_suspend: suspending
<4>[ 32.701049] save exit: isCheckpointed 1
<4>[ 32.706878] save exit: isCheckpointed 1
<4>[ 32.739654] save exit: isCheckpointed 1
<6>[ 32.763153] active wake lock kgsl
<6>[ 32.763275] active wake lock PowerManagerService
<6>[ 32.763366] wake lock mmc_delayed_work, expired
<6>[ 32.763549] wake lock qmi0, expired
<6>[ 32.763671] wake lock qmi1, expired
<6>[ 32.763763] wake lock qmi2, expired
<6>[ 32.763977] wake lock SMD_DS, expired
<6>[ 33.365203] request_suspend_state: wakeup (3->0) at 29519592363 (2010-11-2
3 19:52:23.207824742 UTC)
<6>[ 33.367401] lcdc_resume: resuming
<6>[ 33.367919] mahimahi_ts_power: power 1
<6>[ 33.369537] capella_cm3602_ioctl cmd 2
<6>[ 33.369750] capella_cm3602_disable
<6>[ 33.369842] capella_cm3602_disable: already disabled
<6>[ 33.369964] capella_cm3602_ioctl cmd 1
<6>[ 33.372253] capella_cm3602_ioctl cmd 1
<6>[ 33.415130] lcdc_unblank: ()
<6>[ 33.415252] samsung_oled_panel_unblank: +()
<6>[ 33.697570] samsung_oled_panel_unblank: -()
<6>[ 33.960021] cable_status_update: status=1
<6>[ 33.985809] msm72k_udc: OFFLINE -> ONLINE
<6>[ 33.986114] hsusb: reset controller
<6>[ 34.045654] msm_hsusb_phy_reset: success
<6>[ 34.195678] msm72k_udc: ulpi: write 0x0c to 0x31
<6>[ 34.195861] msm72k_udc: ulpi: write 0x31 to 0x32
<6>[ 34.195983] msm72k_udc: ulpi: write 0x1d to 0x0d
<6>[ 34.196166] msm72k_udc: ulpi: write 0x1d to 0x10
<6>[ 34.196929] msm72k_udc: ept #0 out max:64 head:ffa02000 bit:0
<6>[ 34.197143] msm72k_udc: ept #1 out max:512 head:ffa02080 bit:1
<6>[ 34.197235] msm72k_udc: ept #2 out max:512 head:ffa02100 bit:2
<6>[ 34.197448] msm72k_udc: ept #3 out max:512 head:ffa02180 bit:3
<6>[ 34.197540] msm72k_udc: ept #4 out max:512 head:ffa02200 bit:4
<6>[ 34.197753] msm72k_udc: ept #5 out max:512 head:ffa02280 bit:5
<6>[ 34.197845] msm72k_udc: ept #6 out max:512 head:ffa02300 bit:6
<6>[ 34.198059] msm72k_udc: ept #7 out max:512 head:ffa02380 bit:7
<6>[ 34.198150] msm72k_udc: ept #8 out max:512 head:ffa02400 bit:8
<6>[ 34.198364] msm72k_udc: ept #9 out max:512 head:ffa02480 bit:9
<6>[ 34.198547] msm72k_udc: ept #10 out max:512 head:ffa02500 bit:10
<6>[ 34.198760] msm72k_udc: ept #11 out max:512 head:ffa02580 bit:11
<6>[ 34.198883] msm72k_udc: ept #12 out max:512 head:ffa02600 bit:12
<6>[ 34.200134] msm72k_udc: ept #13 out max:512 head:ffa02680 bit:13
<6>[ 34.200225] msm72k_udc: ept #14 out max:512 head:ffa02700 bit:14
<6>[ 34.200439] msm72k_udc: ept #15 out max:512 head:ffa02780 bit:15
<6>[ 34.200531] msm72k_udc: ept #0 in max:64 head:ffa02040 bit:16
<6>[ 34.200744] msm72k_udc: ept #1 in max:512 head:ffa020c0 bit:17
<6>[ 34.200836] msm72k_udc: ept #2 in max:512 head:ffa02140 bit:18
<6>[ 34.201049] msm72k_udc: ept #3 in max:512 head:ffa021c0 bit:19
<6>[ 34.201141] msm72k_udc: ept #4 in max:512 head:ffa02240 bit:20
<6>[ 34.201354] msm72k_udc: ept #5 in max:512 head:ffa022c0 bit:21
<6>[ 34.201446] msm72k_udc: ept #6 in max:512 head:ffa02340 bit:22
<6>[ 34.201660] msm72k_udc: ept #7 in max:512 head:ffa023c0 bit:23
<6>[ 34.201751] msm72k_udc: ept #8 in max:512 head:ffa02440 bit:24
<6>[ 34.201965] msm72k_udc: ept #9 in max:512 head:ffa024c0 bit:25
<6>[ 34.202148] msm72k_udc: ept #10 in max:512 head:ffa02540 bit:26
<6>[ 34.202270] msm72k_udc: ept #11 in max:512 head:ffa025c0 bit:27
<6>[ 34.202453] msm72k_udc: ept #12 in max:512 head:ffa02640 bit:28
<6>[ 34.202575] msm72k_udc: ept #13 in max:512 head:ffa026c0 bit:29
<6>[ 34.202758] msm72k_udc: ept #14 in max:512 head:ffa02740 bit:30
<6>[ 34.202880] msm72k_udc: ept #15 in max:512 head:ffa027c0 bit:31
<6>[ 34.203094] usb: notify offline
<6>[ 34.203216] msm_hsusb: enable pullup
<6>[ 34.206329] msm72k_udc: msm72k_udc: suspend
<6>[ 34.226043] batt: charging SLOW
<6>[ 34.312683] msm72k_udc: msm72k_udc: reset
<6>[ 34.314941] msm72k_udc: msm72k_udc: portchange USB_SPEED_HIGH
<6>[ 34.473693] msm72k_udc: msm72k_udc: reset
<6>[ 34.475982] msm72k_udc: msm72k_udc: portchange USB_SPEED_HIGH
<4>[ 34.696075] ### notify_usb_connected(1) ###
<6>[ 34.696228] android_usb gadget: high speed config #1: android
<6>[ 34.696716] msm72k_udc: ept #3 in max:512 head:ffa021c0 bit:19
<6>[ 34.696929] msm72k_udc: ept #2 out max:512 head:ffa02100 bit:2
<6>[ 34.985809] binder: release 289:289 transaction 2744 out, still active
<6>[ 35.002349] binder: 79:223 transaction failed 29189, size 4-0
<6>[ 35.002593] binder: send failed reply for transaction 2744, target dead
<6>[ 55.218261] binder: 79:147 transaction failed 29189, size 52-0
<6>[ 59.133666] batt: 83%, 4060 mV, 58 mA (-68 avg), 27.1 C, 1126 mAh
<6>[ 67.028320] enabling adb
<6>[ 67.028472] msm_hsusb: disable pullup
<6>[ 67.045684] msm_hsusb: enable pullup
<6>[ 67.048828] msm72k_udc: msm72k_udc: suspend
<6>[ 67.056182] adb_open
<6>[ 67.206604] msm72k_udc: msm72k_udc: reset
<6>[ 67.206665] usb: notify offline
<6>[ 67.206878] adb_release
<6>[ 67.207946] adb_open
<6>[ 67.208740] msm72k_udc: msm72k_udc: portchange USB_SPEED_HIGH
<3>[ 67.209564] init: sys_prop: permission denied uid:2000 name:adb.connected
<6>[ 67.367462] msm72k_udc: msm72k_udc: reset
<6>[ 67.369750] msm72k_udc: msm72k_udc: portchange USB_SPEED_HIGH
<4>[ 67.581878] ### notify_usb_connected(1) ###
<6>[ 67.581970] android_usb gadget: high speed config #1: android
<6>[ 67.582031] msm72k_udc: ept #4 in max:512 head:ffa02240 bit:20
<6>[ 67.582061] msm72k_udc: ept #3 out max:512 head:ffa02180 bit:3
<6>[ 67.582763] msm72k_udc: ept #3 in max:512 head:ffa021c0 bit:19
<6>[ 67.582824] msm72k_udc: ept #2 out max:512 head:ffa02100 bit:2
<3>[ 68.069061] init: sys_prop: permission denied uid:2000 name:adb.connected
<6>[ 115.879241] batt: 83%, 4089 mV, 251 mA (230 avg), 27.6 C, 1129 mAh
<6>[ 165.942657] batt: 84%, 4094 mV, 250 mA (254 avg), 28.0 C, 1134 mAh
cat<6>[ 216.020111] batt: 84%, 4099 mV, 248 mA (249 avg), 28.2 C, 1137 mAh
<6>[ 266.188140] batt: 84%, 4104 mV, 248 mA (249 avg), 28.5 C, 1140 mAh
<6>[ 316.250946] batt: 84%, 4104 mV, 246 mA (248 avg), 28.7 C, 1145 mAh
What ROM and Kernel are you using? You usually get boot stalls or lockups from an incompatible kernel.
Ok, I'll spell it out:
ROOT. You need it to see system logs.
Then wait until it crashes with reboot.
Then run:
adb shell cat /proc/last_kmsg > c:\last_kmsg.log
adb shell cat /proc/kmsg > c:\kmsg.log
(here you'll need to stop it after 20-30 sec by Ctrl-C)
adb bugreport > c:\bugreport.log
Then you'll have 3 files in C:\, which you need. Upload here, maybe something will be better understandable from them.
ok thanks i will try to do that
GchildT said:
What ROM and Kernel are you using? You usually get boot stalls or lockups from an incompatible kernel.
Click to expand...
Click to collapse
Hi to all
I didn't want to open a new thread because of the sam problem.
So I have Nexus One, and it restarts randomly after a period of use. When the phone restarts it is stuck on the "X" sign, until it reboots again, and again... and I have to remove battery and wait for a while to turn it back on.
Anybody have any idea what this could be, and could it be this conflict.
Android version: 2.3.3
Baseband version: 32.50.00.32U_5.12.00.08
Kernel version: 2.6.35.7-59423-g008607d4
[email protected]#1
Build number: GRI40
HBOOT: 0.35.0017
Radio-5.12.00.00
Current recovery: RA Recovery V2.2.1
I've installed the latest CyanogenMod build on my Galaxy Tab 8.9. When I connect my pl2303 usb serial port adapter to the device and open the "USB Device Info" app I can only see the device under the "Linux" tab, but not under the "Android" tab. Dmesg says:
Code:
<6>[ 241.823933] tegra-ehci tegra-ehci.0: Tegra EHCI Host Controller
<6>[ 241.824139] tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 1
<6>[ 241.832350] [ CONNECTOR_DRIVER (acc_notified,427) ] ACCESSORY=OTG : STATE=online
<6>[ 241.851514] tegra-ehci tegra-ehci.0: irq 52, io mem 0xc5000000
<6>[ 241.871488] tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
<6>[ 241.871702] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 241.871728] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 241.871749] usb usb1: Product: Tegra EHCI Host Controller
<6>[ 241.871767] usb usb1: Manufacturer: Linux 2.6.36.4-cyanogenmod+ ehci_hcd
<6>[ 241.871786] usb usb1: SerialNumber: tegra-ehci.0
<6>[ 241.876842] hub 1-0:1.0: USB hub found
<6>[ 241.876888] hub 1-0:1.0: 1 port detected
<6>[ 241.878664] tegra-otg tegra-otg: tegra_start_host-
<6>[ 241.878687] host_notify: ndev name=usb_otg: from state=2 -> to state=1
<6>[ 242.091586] usb 1-1: new full speed USB device using tegra-ehci and address 2
<6>[ 242.321825] usb 1-1: New USB device found, idVendor=067b, idProduct=2303
<6>[ 242.321881] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
<6>[ 242.321926] usb 1-1: Product: USB-Serial Controller D
<6>[ 242.321962] usb 1-1: Manufacturer: Prolific Technology Inc.
Why isn't the Android API recognizing the usb device?
I think you need insmod pl2303.ko. ask for it from your kernel developer
Sent from my GT-P1000 using xda premium
Touchpad just trying to turn wifi on without any success. I have no idea what happened. touchpad worked well for months and just lost wifi. when I boot to WebOs - wifi is working well. I tried to clean up cm9 and flash cm10 - same result.
output from catlog:
02-18 11:35:07.449 E/WifiStateMachine(350): Failed to reload STA firmware java.lang.IllegalStateException: command '40 softap fwreload wlan0 STA' failed with '400 40 Softap operation failed (No such device)'
02-18 11:35:07.459 E/WifiStateMachine(350): Unable to change interface settings: java.lang.IllegalStateException: command '42 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 42 Failed to set address (No such device)'
02-18 11:35:18.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:19.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:20.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:21.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:22.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:22.479 E/WifiStateMachine(350): Failed to setup control channel, restart supplicant
02-18 11:35:27.499 E/WifiStateMachine(350): Failed to reload STA firmware java.lang.IllegalStateException: command '43 softap fwreload wlan0 STA' failed with '400 43 Softap operation failed (No such device)'
02-18 11:35:27.509 E/WifiStateMachine(350): Unable to change interface settings: java.lang.IllegalStateException: command '45 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 45 Failed to set address (No such device)'
02-18 11:35:27.509 E/WifiHW (350): Unable to open connection to supplicant on "wlan0": No such file or directory
02-18 11:35:28.509 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:29.519 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:30.519 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:31.519 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:32.519 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:32.519 E/WifiStateMachine(350): Failed to setup control channel, restart supplicant
netcfg shows all interfaces down except lo.
wifi country is eu (never checked it before) and I can't change it.
You could try this; maybe it's something similar?
bananagranola said:
You could try this; maybe it's something similar?
Click to expand...
Click to collapse
no link?
Well, that's my first brain fart today. Won't be the last. http://forum.xda-developers.com/showthread.php?t=1813200
Thanks, but not. my wifi just stopped working without any updates etc.
My goodness - wrong device, wrong thread. Like I said, not the last. http://forum.xda-developers.com/showthread.php?t=1937109
No, didn't helped. wifi in webos works without any problems too.
I'm looking at dmesg and found:
board sdio wifi disable
mmc1: card 0001 removed
is it wifi card?
Sorry, then that was the limit of what I can help with. Other than a full wipe and reflash I don't know what else to try. Hopefully someone with more knowledge will show up.
More info from dmesg:
<6>[ 443.108696] CMTP-ATH6KL v4.4
<3>[ 443.108715] board_sdio_wifi_enable
<6>[ 443.114565] wifi_power(1) 1.8V sdio: set load
<6>[ 443.119068] tenderloin_wifi_power: New regulator mode for 8058_s3: 1
<6>[ 443.126264] wifi_power(1) 3.3V
<6>[ 443.126583] wifi_power(1) 8901_l1 3.3V
<6>[ 443.134761] wifi_power(1) 8058_l19 1.8V
<4>[ 443.135074] wifi_power(1) CHIP_PWD
<4>[ 443.498377] mmc1: queuing unknown CIS tuple 0x01 (3 bytes)
<4>[ 443.507770] mmc1: queuing unknown CIS tuple 0x1a (5 bytes)
<4>[ 443.511869] mmc1: queuing unknown CIS tuple 0x1b (8 bytes)
<4>[ 443.518944] mmc1: queuing unknown CIS tuple 0x14 (0 bytes)
<4>[ 443.529203] mmc1: queuing unknown CIS tuple 0x80 (1 bytes)
<4>[ 443.529474] mmc1: queuing unknown CIS tuple 0x81 (1 bytes)
<4>[ 443.541910] mmc1: queuing unknown CIS tuple 0x82 (1 bytes)
<6>[ 443.541961] mmc1: new high speed SDIO card at address 0001
<3>[ 443.598711] ath6kl: bef2fd6c
<3>[ 446.099490] ath6kl: bef2fcfc
<4>[ 446.099507] ath6kl: bef2fcdc
<6>[ 446.114969] ath6kl: bef2fbc4
<6>[ 446.114985] ath6kl: bef2fbc4
<6>[ 446.116982] ath6kl: bef2fbc4
<6>[ 446.119846] ath6kl: bef2fbc4
<6>[ 446.122747] ath6kl: bef2fbc4
<6>[ 446.125644] ath6kl: bef2fbc4
<6>[ 446.128447] ath6kl: bef2fbc4
<6>[ 446.131304] ath6kl: bef2fbc4
<6>[ 446.134207] ath6kl: bef2fbc4
<6>[ 446.137091] ath6kl: bef2fbc4
<6>[ 446.139949] ath6kl: bef2fbc4
<6>[ 446.142802] ath6kl: bef2fbc4
<6>[ 446.145628] ath6kl: bef2fbc4
<6>[ 446.148491] ath6kl: bef2fbc4
<6>[ 446.151356] ath6kl: bef2fbc4
<6>[ 446.154317] ath6kl: bef2fbc4
<6>[ 446.157094] ath6kl: bef2fbc4
<4>[ 446.160235] ath6kl: bef2fc94
<3>[ 446.163154] ath6kl: bef2fe14
<3>[ 446.166015] ath6kl: bef2fe44
<4>[ 446.168669] ath6kl_sdio: probe of mmc1:0001:1 failed with error -5
<6>[ 462.282740] adm_close port_id=0 index 0
<6>[ 478.764935] adm_close port_id=0 index 0
<3>[ 498.557702] board_sdio_wifi_disable
<6>[ 498.564551] tenderloin_wifi_power: New regulator mode for 8058_s3: 1
<6>[ 498.685586] mmc1: card 0001 removed
i dont know what cleanup cm9 + 10 means.. delete things?
uninstall?
nandroid restore and still no-go?
maybe rootzwixi knows..
goodluck
amkaos said:
i dont know what cleanup cm9 + 10 means.. delete things?
uninstall?
nandroid restore and still no-go?
maybe rootzwixi knows..
goodluck
Click to expand...
Click to collapse
format cache, sdcard, config and data from clockworkmod and then acmeuninstall. tried 3 times. Now trying to flash cm9.
this sounds impossible maybe ::
sometimes my router will not broadcast wifi but all things connected thru ethernet work fine.. or one wireless device cannot connect but others do or other connex issues..etc..
if i restart modem + router, everything connex just fine..
you didnt really give any detes about if hptp only fails on your network etc..
if you do uninstall then acme3 correctly, there is no way that HPTP wont connect to your network... unless you share some obscure hardware fubar that i never heard of..
GL
i hope you post what the outcome is and how you resolved prob.
your experience will help out someone in future time
btw, i dont wanna rub it in but when you get things going, make a nandroid backup .. make more as you tweak out your tab and safely delete prior backups... saved me many headaches..
GL
EDIT:: i see that you do connect w/ webos.. still its easy to restart router + modem..
So, new wifi driver in the new cm10 build - still no success. It's only internet browser with webos ;(
Epic 4g same thing
crea7or said:
So, new wifi driver in the new cm10 build - still no success. It's only internet browser with webos ;(
Click to expand...
Click to collapse
CM10 for 4 months no wifi issues. Suddenly the other morning wifi won't turn on. Boot to a stock image it is fine. Did you ever find a solution?
RichMichPA said:
CM10 for 4 months no wifi issues. Suddenly the other morning wifi won't turn on. Boot to a stock image it is fine. Did you ever find a solution?
Click to expand...
Click to collapse
stock image?
Multiboot utility
crea7or said:
stock image?
Click to expand...
Click to collapse
I use multi boot which lets you reboot into fc09 to add MSL etc. I just tried 9.1 ics and wifi is working.
Exactly the same problem
As yet, no fix in sight.
Wifi in WebOS is solid. I have managed to spontaneously connect a couple of times after several hours, sometimes days. I've tried reflashing several roms/updates, reformating, clearing cache and dalvik, resetting permissions. Nothing.
As long as I do not reboot, once connected the wifi is solid. My catlog shows exactly the same problems as OPs.
It may be a coincidence, but my problems seemed to begin after switching to airplane mode on a recent trip. Since then I've only managed to get the wifi up 3 times.
In settings under wifi it just says "connecting to wifi" regardless of whether the wifi button is set to "ON" or "OFF"
What bothers me, is the "not found" errors in logcat.
I'm out of ideas. If anyone can suggest a way to nail down the issue, I'm all ears. Thanks in advance!
Code:
07-24 11:37:27.209 E/WifiStateMachine(242): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
07-24 11:37:27.209 W/CommandListener(156): Failed to retrieve HW addr for wlan0 (No such device)
07-24 11:37:27.209 D/CommandListener(156): Setting iface cfg
07-24 11:37:27.209 D/NetworkManagementService(242): rsp <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
07-24 11:37:27.209 D/NetworkManagementService(242): flags <[down]>
07-24 11:37:27.219 E/WifiStateMachine(242): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg wlan0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
07-24 11:37:27.389 I/wpa_supplicant(6737): rfkill: Cannot open RFKILL control device
07-24 11:37:27.389 E/wpa_supplicant(6737): Could not read interface wlan0 flags: No such device
I'm having the same issue. WiFi works solid on webOs just when I boot into android and try to turn WiFi on, it stays stuck saying “turning on wifi" on cm9 any build and cm10 any build. I uninstalled everything at least 20 times wiped my TP clean on android and webOs(basically factory reset) wiped the cache wiped the delvik cache turned off turn on reinstall android also downloaded WiFi fixer apk and that doesn't help at all either. Everything on webOs works WiFi internet works great. Just when I go into android it stays stuck at turning on WiFi and when I reinstall cm9 or cm10 open up settings this is the only time I can switch the setting to turning on WiFi but everything is in gray with no luck just stuck saying turning on WiFi. Any help would be much appreciated! I hate webOs android is way better!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
[email protected] said:
I'm having the same issue. WiFi works solid on webOs just when I boot into android and try to turn WiFi on, it stays stuck saying “turning on wifi" on cm9 any build and cm10 any build. I uninstalled everything at least 20 times wiped my TP clean on android and webOs(basically factory reset) wiped the cache wiped the delvik cache turned off turn on reinstall android also downloaded WiFi fixer apk and that doesn't help at all either. Everything on webOs works WiFi internet works great. Just when I go into android it stays stuck at turning on WiFi and when I reinstall cm9 or cm10 open up settings this is the only time I can switch the setting to turning on WiFi but everything is in gray with no luck just stuck saying turning on WiFi. Any help would be much appreciated! I hate webOs android is way better!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
[email protected] said:
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
did u try doctore your TP?
I have been successfully port cm12 to XT1085, there is almost no difference between 1095 and 1085, and most work has been done by crpalmer.
Here is the changes I made to XT1085: https://github.com/kghost/android_device_motorola_victara
Newest build:
http://conoha.kghost.info/~kghost/cm-12-20150318-UNOFFICIAL-victara.zip (md5sum e2cdfdf5f0571a38a6887b8cd05a1e99)
Working:
* Adb
* Ambient display
* Audio
* Brightness / Auto-brightness
* Bluetooth
* Camera and camcorder
* GPS
* MTP
* NFC (Android beam)
* Offmode charging
* Radio (GSM Voice/SMS)
* Radio (CDMA Voice/SMS)
* Radio (EV-DO Data)
* Radio (EDGE)
* Radio (LTE)
* Rotator
* Sensors
* USB-OTG (keyboard, mouse)
* Vibrator
* Video playback (youtube)
* WiFi
* SELinux enforcing
Not working:
* USB-OTG (storage)
Not tested:
* DRM / Widevine
Quirks / Improvements needed (by crpalmer):
* Ambient display should use sensors
* DRM is only partially working (V8 not V12)
* Graphic glitches occasionally?
* Hotword detection should use offloaded DSP
* USB-OTG doesn't show storage stats in Settings app
* WiFi: update to a newer version of the wlan driver than what moto ships.
Unknown:
* Everything else
Offmode charhing not working, LTE working
xarcom said:
Offmode charhing not working, LTE working
Click to expand...
Click to collapse
Thank you，I‘m looking on it
off-mode charging is broken because framebuffer driver is not working. I haven't locate the problem yet
zealot0630 said:
off-mode charging is broken because framebuffer driver is not working. I haven't locate the problem yet
Click to expand...
Click to collapse
Actually, I fixed it in the kernel yesterday.
crpalmer said:
Actually, I fixed it in the kernel yesterday.
Click to expand...
Click to collapse
awesome, I'll sync/build asap
sorry, don't notice DEV-ONLY,
DELETE.
crpalmer said:
Actually, I fixed it in the kernel yesterday.
Click to expand...
Click to collapse
Unfortunately, framebuffer still doesn't work in new kernel
I found some fb error in my dmesg
Code:
--
<6>[ 0.512739,1] gpiochip_add: registered GPIOs 444 to 447 on device: pm8841-mpp
<6>[ 0.513691,1] gpiochip_add: registered GPIOs 408 to 443 on device: pm8941-gpio
<6>[ 0.516441,1] gpiochip_add: registered GPIOs 401 to 407 on device: pm8941-mpp
<6>[ 0.517337,1] mdss_mdp_probe: MDP HW Base phy_Address=0xfd900000 virt=0xc5500000
<6>[ 0.517437,1] mdss_mdp_probe: MDSS VBIF HW Base phy_Address=0xfd924000 virt=0xc547c000
<3>[ 0.517581,1] mdss_mdp_parse_dt_prop_len: Error from prop qcom,mdss-clk-levels : spec error in device tree
<6>[ 0.519077,1] mdss_dsi_ctrl_probe: DSI Ctrl name = MDSS DSI CTRL->0
<6>[ 0.519171,1] BL: panel=mipi_mot_cmd_smd_fhd_520, manufacture_id(0xDA)= 0x2 controller_ver(0xDB)= 0x6 controller_drv_ver(0XDC)= 0x1, full=0x0000000000010602, detect status = 0x0
<6>[ 0.519281,1] mdss_dsi_panel_init: Panel Name = mipi_mot_cmd_smd_1080_v1
--
<6>[ 0.541628,1] mdss_register_panel: adding framebuffer device fd922800.qcom,mdss_dsi
<6>[ 0.541840,1] mdss_hw_init: MDP Rev=10020001
<6>[ 0.543735,1] mdss_register_panel: adding framebuffer device qcom,mdss_wb_panel.6
<6>[ 0.544416,1] mdss_fb_parse_dt: split framebuffer left=0 right=0
<6>[ 0.544516,1] mdss_fb_register: FrameBuffer[0] 1080x1920 registered successfully!
<4>[ 0.544660,1] mdss_mdp_pp_resume: Failed to get AD info, err = -112
<7>[ 0.544792,1] Registered led device: lcd-backlight
<6>[ 0.544830,1] mdss_fb_parse_dt: split framebuffer left=0 right=0
<6>[ 0.544962,1] mdss_fb_register: FrameBuffer[1] 1920x1080 registered successfully!
<6>[ 0.545087,1] mdss_dsi_status_init: DSI status check interval:8000
<3>[ 0.559139,1] sps: BAM device 0xf9944000 is not registered yet.
<6>[ 0.559237,1] sps:BAM 0xf9944000 is registered.
--
full dmesg http://pastebin.com/9ifL5aMc
would you please paste dmesg on XT1095 ?
zealot0630 said:
Unfortunately, framebuffer still doesn't work in new kernel
I found some fb error in my dmesg
Code:
--
<6>[ 0.512739,1] gpiochip_add: registered GPIOs 444 to 447 on device: pm8841-mpp
<6>[ 0.513691,1] gpiochip_add: registered GPIOs 408 to 443 on device: pm8941-gpio
<6>[ 0.516441,1] gpiochip_add: registered GPIOs 401 to 407 on device: pm8941-mpp
<6>[ 0.517337,1] mdss_mdp_probe: MDP HW Base phy_Address=0xfd900000 virt=0xc5500000
<6>[ 0.517437,1] mdss_mdp_probe: MDSS VBIF HW Base phy_Address=0xfd924000 virt=0xc547c000
<3>[ 0.517581,1] mdss_mdp_parse_dt_prop_len: Error from prop qcom,mdss-clk-levels : spec error in device tree
<6>[ 0.519077,1] mdss_dsi_ctrl_probe: DSI Ctrl name = MDSS DSI CTRL->0
<6>[ 0.519171,1] BL: panel=mipi_mot_cmd_smd_fhd_520, manufacture_id(0xDA)= 0x2 controller_ver(0xDB)= 0x6 controller_drv_ver(0XDC)= 0x1, full=0x0000000000010602, detect status = 0x0
<6>[ 0.519281,1] mdss_dsi_panel_init: Panel Name = mipi_mot_cmd_smd_1080_v1
--
<6>[ 0.541628,1] mdss_register_panel: adding framebuffer device fd922800.qcom,mdss_dsi
<6>[ 0.541840,1] mdss_hw_init: MDP Rev=10020001
<6>[ 0.543735,1] mdss_register_panel: adding framebuffer device qcom,mdss_wb_panel.6
<6>[ 0.544416,1] mdss_fb_parse_dt: split framebuffer left=0 right=0
<6>[ 0.544516,1] mdss_fb_register: FrameBuffer[0] 1080x1920 registered successfully!
<4>[ 0.544660,1] mdss_mdp_pp_resume: Failed to get AD info, err = -112
<7>[ 0.544792,1] Registered led device: lcd-backlight
<6>[ 0.544830,1] mdss_fb_parse_dt: split framebuffer left=0 right=0
<6>[ 0.544962,1] mdss_fb_register: FrameBuffer[1] 1920x1080 registered successfully!
<6>[ 0.545087,1] mdss_dsi_status_init: DSI status check interval:8000
<3>[ 0.559139,1] sps: BAM device 0xf9944000 is not registered yet.
<6>[ 0.559237,1] sps:BAM 0xf9944000 is registered.
--
full dmesg http://pastebin.com/9ifL5aMc
would you please paste dmesg on XT1095 ?
Click to expand...
Click to collapse
What is that a dmesg of? Just a normal boot? I don't see anything that looks like a real error in your dmesg. The dt errors and the AD error are normal.
Are you having problems with the mdss driver in general or just for the charge_only_mode?
crpalmer said:
What is that a dmesg of? Just a normal boot? I don't see anything that looks like a real error in your dmesg. The dt errors and the AD error are normal.
Are you having problems with the mdss driver in general or just for the charge_only_mode?
Click to expand...
Click to collapse
offmode charging works fine, but framebuffer still don't work in normal boot, I don't know if it is ordinary.
zealot0630 said:
offmode charging works fine, but framebuffer still don't work in normal boot, I don't know if it is ordinary.
Click to expand...
Click to collapse
What exactly doesn't work? I'm not entirely sure what you mean by "framebuffer doesn't work in normal boot". Do you get the boot animation?
crpalmer said:
What exactly doesn't work? I'm not entirely sure what you mean by "framebuffer doesn't work in normal boot". Do you get the boot animation?
Click to expand...
Click to collapse
boot animation works, I can't read/write "/dev/graphics/fb0"
zealot0630 said:
boot animation works, I can't read/write "/dev/graphics/fb0"
Click to expand...
Click to collapse
What isn't working? I am still not understanding what you are trying to fix...
Hi
I was trying to unlock bootloader of my honor 3c (H30-U10) via SP Flash Tools. When I was connecting my phone without battery to PC via USB after clicking "Download" Button, the device kept vibrating and the connection got disconnected and connected every 3 seconds. The Screen was off during all of this process.
Here is my SP Flash Tool log:
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1467879144.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
COM port is open. Trying to sync with the target...
Failed to Connect DA: S_BROM_DOWNLOAD_DA_FAIL
Disconnect!
BROM Exception! ( BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to download DA to baseband chip's internal SRAM!
[HINT]:
1. There's an cable communication problem between FlashTool and BootROM.
2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION]
1. Try again.
2. Proceed H/W checking in download cable and target side com port.
3. Monitor if power-drop occured in target side.)((ConnectDA,../../../flashtool/Conn/Connection.cpp,127))
and this is my dmesg log:
Code:
[ 3440.213018] usb 1-1.2: new high-speed USB device number 55 using ehci-pci
[ 3440.307101] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=2000
[ 3440.307104] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3440.307105] usb 1-1.2: Product: MT65xx Preloader
[ 3440.307106] usb 1-1.2: Manufacturer: MediaTek
[ 3440.369300] cdc_acm 1-1.2:1.1: ttyACM1: USB ACM device
[ 3443.146921] usb 1-1.2: USB disconnect, device number 55
[ 3560.113932] usb 1-1.2: new high-speed USB device number 56 using ehci-pci
[ 3560.209002] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=2000
[ 3560.209005] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3560.209007] usb 1-1.2: Product: MT65xx Preloader
[ 3560.209008] usb 1-1.2: Manufacturer: MediaTek
[ 3560.271453] cdc_acm 1-1.2:1.1: ttyACM0: USB ACM device
[ 3563.563312] usb 1-1.2: USB disconnect, device number 56.
.
.
.
[ 3589.764652] usb 1-1.2: new high-speed USB device number 62 using ehci-pci
[ 3589.859355] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=2000
[ 3589.859359] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3589.859361] usb 1-1.2: Product: MT65xx Preloader
[ 3589.859363] usb 1-1.2: Manufacturer: MediaTek
[ 3589.921646] cdc_acm 1-1.2:1.1: ttyACM0: USB ACM device
[ 3590.138898] usb 1-1.2: USB disconnect, device number 62
I also tried this with windows with all drivers installed, but I got the exact same result.
After a bunch of tries, now my phone doesn't even turns on. When I press power button with battery inserted, It vibrates every 20 seconds and the screen is always off, too. Connecting it to computer makes the same behavior described above.
So… Is there any way to make it fix? Since I can not access to fastboot mode and SP Flash Tools is not working either?
danialbehzadi said:
Hi
I was trying to unlock bootloader of my honor 3c (H30-U10) via SP Flash Tools. When I was connecting my phone without battery to PC via USB after clicking "Download" Button, the device kept vibrating and the connection got disconnected and connected every 3 seconds. The Screen was off during all of this process.
Here is my SP Flash Tool log:
and this is my dmesg log:
I also tried this with windows with all drivers installed, but I got the exact same result.
After a bunch of tries, now my phone doesn't even turns on. When I press power button with battery inserted, It vibrates every 20 seconds and the screen is always off, too. Connecting it to computer makes the same behavior described above.
Soâ?¦ Is there any way to make it fix? Since I can not access to fastboot mode and SP Flash Tools is not working either?
Click to expand...
Click to collapse
Do adb recognize your phone?!
Not at all. I took my device to Huawei center and they told me it's dead. So, I bought a new phone.
DON'T BY FROM HUAWEI!
danialbehzadi said:
Not at all. I took my device to Huawei center and they told me it's dead. So, I bought a new phone.
DON'T BY FROM HUAWEI!
Click to expand...
Click to collapse
Ahhh too bad :/
The same thing happened to my Samsung , i overcharged it via an unstable source, and the power IC was damaged, if i slid the battery in it would just keep vibrating and flash light turned on, it costed me PKR Rs.1200(USD.12$) to repair it......
Try SP Flashtool again, but with your battery in. Flashing recovery might be your best bet
Fixed your device?
hassanjavaid8181 said:
Fixed your device?
Click to expand...
Click to collapse
No. Threw it away!
danialbehzadi said:
No. Threw it away!
Click to expand...
Click to collapse
thats another way to fix issue