I was trying to install CM11 on my device but the phone hands on the "hTc quietly brilliant" screen. I can connect to the device using adb while it is in this state. Investigating the output of logcat reveals this troubling section:
I/ServiceManager( 116): service 'sensorservice' died
I/ServiceManager( 116): service 'power' died
I/ServiceManager( 116): service 'usagestats' died
I/ServiceManager( 116): service 'batterystats' died
I/ServiceManager( 116): service 'appops' died
I/ServiceManager( 116): service 'display' died
I/ServiceManager( 116): service 'telephony.registry' died
I/ServiceManager( 116): service 'scheduling_policy' died​
The same thing happens when I try CM10.1 or CM10.2 and it happens with cwm and twrp. Does anybody have any clue what this is about? Googling doesn't turn much up and I can't find anyway to get my phone back into a usable state.
Oof, this was a silly mistake on my part. I was forgetting to extract boot.img and flash it in fastboot in addition to flashing the ROM. After doing this it resolved the issues.
Related
When I dial a call all that happens is it places the call through verizon and not google voice any one else have this issue?, The guy at the store ran the ota before I was even handed the phone...
*Update 1 (4:13 pm): google voice seems to crash when rebooting =\
*Update 2 (4:23 pm): ADB Logcat output with grep on voice
Code:
[email protected]:~/Desktop/****/SDK/android-sdk-linux_86/tools$ cat adb.log | grep voice
W/PackageManager( 74): Unknown permission com.google.android.permission.SEND_DATA_MESSAGE in package com.google.android.apps.googlevoice
W/PackageManager( 74): Unknown permission com.google.android.permission.RECEIVE_DATA_MESSAGE in package com.google.android.apps.googlevoice
W/PackageManager( 74): Unknown permission com.google.android.apps.googlevoice.REMOTE_INTENT in package com.google.android.apps.googlevoice
D/HtcCdmaPhoneApp( 111): voice privacy setting=1
D/HtcCdmaPhoneApp( 111): voice privacy status=-1
I/ActivityManager( 74): Start proc com.android.voicedialer for broadcast com.android.voicedialer/.VoiceDialerReceiver: pid=336 uid=10042 gids={3002}
D/VoiceDialerReceiver( 336): onReceive Intent { action=android.intent.action.BOOT_COMPLETED comp={com.android.voicedialer/com.android.voicedialer.VoiceDialerReceiver} }
D/RecognizerEngine( 336): deleteCachedGrammarFiles /data/data/com.android.voicedialer/files/openentries.txt
D/GooglePartnerSetup( 341): voicesearch client id: ms-android-verizon
I/ActivityManager( 74): Start proc com.google.android.apps.googlevoice for broadcast com.google.android.apps.googlevoice/.BootUpReceiver: pid=348 uid=10049 gids={3003}
E/dalvikvm( 348): Could not find method android.content.Context.getApplicationInfo, referenced from method com.google.android.apps.googlevoice.BootUpReceiver.onReceive
W/dalvikvm( 348): VFY: rejected Lcom/google/android/apps/googlevoice/BootUpReceiver;.onReceive (Landroid/content/Context;Landroid/content/Intent;)V
W/dalvikvm( 348): Verifier rejected class Lcom/google/android/apps/googlevoice/BootUpReceiver;
W/dalvikvm( 348): Class init failed in newInstance call (Lcom/google/android/apps/googlevoice/BootUpReceiver;)
E/AndroidRuntime( 348): java.lang.VerifyError: com.google.android.apps.googlevoice.BootUpReceiver
I/ActivityManager( 74): Process com.google.android.apps.googlevoice (pid 348) has died.
-Chr1831
Yes it started crashing here after the MR2
Snakehn said:
Yes it started crashing here after the MR2
Click to expand...
Click to collapse
I can confirm this on my end as well. After the first OTA update there was no issue, but MR2 screwed with it. I found I can launch the application after the initial boot crash, but haven't confirmed that it is working as it should on my phone.
I get GV FC's on startup but then again I only use it for voicemail and its working pretty good.
I got version 2.5 to work just not 3.0 hopefully the (htc) update on the 22end will address this bug
Still some issues for me. It FCs on boot. All though most functionality is there..
When I call out things are strange, contact pics don't work and the outgoing number is not the dialed number its the GV "bridge" number.
Both of the above issues do not exist on my moto droid.
I wish it was fixed.
1) Grab the 1gb clockwork recovery sd card image
2) boot into CW recovery; mount /system and /sdcard from CW
3) grab a DIFFERENT sd card. unzip the sideload_update.zip, zip up just the /system files
4) unzip system.zip (or whatever you called it) from adb shell onto the nook after moutning it's sdcard (mount sdcard from clockwork, unzip the zip file through adb)
Testing this myself now, but need to step away for about an hour..
EDIT - not having much luck trying new things.. but limited on time for this..
OK - so the above method didn't work. But i'm having partial success going the manual route. Right now, I have a nook 1.1 install with superuser working, and most of the google apps working. What's not working is market installs. market is also working.. (everything that I've tested so far is working )
Here's what I've done - it's complicated and I don't recommend it unless you're comfortable with adb / linux /etc. (wait for a real dev to package this up if you're not..)
http://legacyschool.us.to/nookdev/clockwork/clockwork_1gb-0.4.tar.gz
1) Burn the clockwork SD recovery card - boot from it. http://legacyschool.us.to/nookdev/clockwork/clockwork_1gb-0.4.tar.gz after it boots, adb from the desktop to your nook. (alternatively, bootup nookie froyo and adb to your nook using it. CW would be simpler though for mounting the /system and /data)
2) Restore your system and boot images to stock, using dd directions here - ( http://forum.xda-developers.com/showthread.php?t=919353
3) Upgrade the nook to 1.1 manually using B&N's directions - http://www.barnesandnoble.com/u/nookcolor-support-software-update/379002520/?cds2Pid=35758
4) after an install, your apps will mostly be working, but you won't have the google apps or superuser. Bootup again using the SD card image (either clockwork or froyo) - mount /system and /data from there (using the menus in clockwork if that's what you used.
5) Follow the steps from nookdevs to re-root your device
http://nookdevs.com/NookColor_Installing_su_and_the_Superuser_app
http://nookdevs.com/NookColor_Installing_Busybox
Nook color email if you need it - http://nookdevs.com/NookColor_Email
grab the google apps - http://www.mediafire.com/file/awqekwp5dpbk4e3/nc_gapps.zip - adb push it to your device (adb push nc_gapps.zip /data/local/
copy the /system/framework/framework.jar to a backup file (cp /system/framework/framework.jar /system/framework/framework.jar.bk)
unzip the nc_gapps.zip (cd /system; unzip /data/local/nc_gapps.zip)
copy the framework file back as it's most likely incompatible with the new 1.1 software (haven't tried using it yet) - ( cp /system/framework/framework.jar.bk /system/framework/framework.jar)
(Credit to MrMuffin for getting market working) using the clockwork sd card with /system and /data mounted, run the following commands from adb shell -
Code:
cp /system/build.prop /data/local/build.prop.bk
cp /data/system/packages.xml /data/local/system.xml.bk
sed 's/^.*ro.build.fingerprint.*$/ro\.build\.fingerprint=verizon\/voles\/sholes\/sholes:2\.1-update1\/ESE81\/29593:user\/release-keys/' /data/local/build.prop.bk > /system/build.prop
sed '1,/uid.system/!{ /<perms>/,/uid.system/!d; }' /data/local/packages.xml.bk > /data/system/packages.xml
Then unmount /system and /data in CW, remove the SD card, and reboot.
Reboot your nook.. now you're in 1.1 with su working..
Still working on it.. market installs are failing (because I haven't personally done the steps for enabling market y et.. ) but the rest of the apps are happy.. <-- working now
-m
I'm curious as to how this works out. Do we really need two SD cards, however? Or does that just save time?
Are you sure the ramdisk and kernel don't need upgrading as well?
Fast HTTP Mirror of the 1.1 Update for Nook Color:
http://www.techerrata.com/dl.php?path=14&file=Sideload_update_1-1.zip
Can you mount the necessary partitions via Nookie Froyo on SDcard?
Homer
Seriously hoping that this works. The changelog shows some great improvements, while not necessarily big. Please let us know how its going for you.
first attempt resulted in bootloops.. Most likely permission related as I had just used zip on windows.. after using CW to recovery my old image, I'm trying again with a zip file made under linux (to retain permissions..).
The kernel might be necessary.. not sure.. will report back..
-m
Giving up for now.. even after setting the permissisions based on the updater-script file, I can't get past this error in logcat -
Code:
E/ActivityThread( 1673): Failed to find provider info for settings
I/ActivityThread( 1673): Publishing provider android.server.checkin: com.google.
android.server.checkin.CheckinProvider
I/SystemServer( 1673): Battery Service
I/SystemServer( 1673): Hardware Service
E/ActivityThread( 1673): Failed to find provider info for settings
W/dalvikvm( 1673): threadid=37: thread exiting with uncaught exception (group=0x
4001b170)
E/AndroidRuntime( 1673): Uncaught handler: thread PowerManagerService exiting du
e to uncaught exception
E/AndroidRuntime( 1673): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 1673): java.lang.NullPointerException
E/AndroidRuntime( 1673): at android.content.ContentQueryMap.<init>(Conten
tQueryMap.java:65)
E/AndroidRuntime( 1673): at com.android.server.PowerManagerService.initIn
Thread(PowerManagerService.java:525)
E/AndroidRuntime( 1673): at com.android.server.PowerManagerService$1.onLo
operPrepared(PowerManagerService.java:457)
E/AndroidRuntime( 1673): at android.os.HandlerThread.run(HandlerThread.ja
va:59)
E/AndroidRuntime( 1673): Crash logging skipped, no checkin service
I/Process ( 1673): Sending signal. PID: 1673 SIG: 9
D/BootAnimation( 1684): SurfaceFlinger died, exiting...
I/ServiceManager( 773): service 'telephony.registry' died
I/ServiceManager( 773): service 'batteryinfo' died
I/ServiceManager( 773): service 'SurfaceFlinger' died
I/ServiceManager( 773): service 'power' died
I/ServiceManager( 773): service 'entropy' died
I/ServiceManager( 773): service 'activity' died
I/ServiceManager( 773): service 'usagestats' died
I/ServiceManager( 773): service 'account' died
I/ServiceManager( 773): service 'meminfo' died
I/ServiceManager( 773): service 'cpuinfo' died
I/ServiceManager( 773): service 'activity.broadcasts' died
I/ServiceManager( 773): service 'activity.services' died
I/ServiceManager( 773): service 'activity.senders' died
I/ServiceManager( 773): service 'activity.providers' died
I/ServiceManager( 773): service 'permission' died
I/ServiceManager( 773): service 'package' died
I/ServiceManager( 773): service 'content' died
I/ServiceManager( 773): service 'battery' died
I/ServiceManager( 773): service 'hardware' died
E/installd( 783): eof
Wondering if we need a hacked framework-res.apk file..
Oops, I 'd suggest editing your first post and making it clear NOT to try this just yet..
diomark said:
1) Grab the 1gb clockwork recovery sd card image
2) boot into CW recovery; mount /system and /sdcard from CW
3) grab a DIFFERENT sd card. unzip the sideload_update.zip, zip up just the /system files
4) unzip system.zip (or whatever you called it) from adb shell onto the nook after moutning it's sdcard (mount sdcard from clockwork, unzip the zip file through adb)
Testing this myself now, but need to step away for about an hour..
-m
Click to expand...
Click to collapse
I have a flashable, prerooted update.zip that gets you to 1.1. Will post up tonight. It worked fine for me when trying to update to 1.1.
Decad3nce said:
I have a flashable, prerooted update.zip that gets you to 1.1. Will post up tonight. It worked fine for me when trying to update to 1.1.
Click to expand...
Click to collapse
Not that I understand enough about it, but was thinking that framework had to be updated for google apps to work, is that going to be included with your update.zip? Or was the apps working without modification?
Decad3nce said:
I have a flashable, prerooted update.zip that gets you to 1.1. Will post up tonight. It worked fine for me when trying to update to 1.1.
Click to expand...
Click to collapse
What do u mean prerooted. What would this flashable zip do when installed overautonootered 1.0.1?
cflynt said:
Not that I understand enough about it, but was thinking that framework had to be updated for google apps to work, is that going to be included with your update.zip? Or was the apps working without modification?
Click to expand...
Click to collapse
It's essentially a ROM template created from the sideload update.zip from barnes and noble. It contains the gapps framework, gapps permissions, as well as busybox and the su binary along with the other goodies from the autonooter img.
I didn't want to risk brick on unrooting and updating via official so the created update.zip flashes via clockwork recovery but lacks the uboot stuffs for clockwork overwrite.
Decad3nce said:
It's essentially a ROM template created from the sideload update.zip from barnes and noble. It contains the gapps framework, gapps permissions, as well as busybox and the su binary along with the other goodies from the autonooter img.
I didn't want to risk brick on unrooting and updating via official so the created update.zip flashes via clockwork recovery but lacks the uboot stuffs for clockwork overwrite.
Click to expand...
Click to collapse
SO if we were to flash this we essentially goto a 1.1 nootered?
Will we be able to use the 1.1 ghz OC kernal?
Canadoc said:
SO if we were to flash this we essentially goto a 1.1 nootered?
Will we be able to use the 1.1 ghz OC kernal?
Click to expand...
Click to collapse
Yes. 10char
Well if it works as you say you are gonna make a lot of people happy!!!!!
Decad3nce said:
Yes. 10char
Click to expand...
Click to collapse
Have observed Decad3nce's work on the CDMA hero. This will be the real deal. Thank you sir. Glad you are on board.
Yea I've seen him on the Eris forums too. Thanks again Decad3nce. Much appreciated.
Sounds cool, but will it require CWM to install? Will it require it to run after?
I'm still seeing little weirdness reported with CWM so I'm avoiding it for now, but I could always install it and remove it again..
Decad3nce nice work!
All others, just sit tight, I am sure he's testing and will post a write up later. One thing I have learned from these boards is:
1. Never rush a developer
2. Never rush a developer
3. See #1 then #2.
Rushing leads to bugs leads to hate posts. So....Never rush a developer
Help with this
I/ServiceManager( 1271): Waiting for service media.audio_flinger...
E/SurfaceFlinger( 1190): eglSwapBuffers: EGL error 0x3008 (EGL_BAD_DISP
I/ServiceManager( 1271): Waiting for service media.audio_flinger...
I/ServiceManager( 1271): Waiting for service media.audio_flinger...
I/ServiceManager( 1271): Waiting for service media.audio_flinger...
I/ServiceManager( 1271): Waiting for service media.audio_flinger...
I/Netd ( 1282): Netd 1.0 starting
W/AudioSystem( 1271): AudioFlinger not published, waiting...
I/ServiceManager( 1271): Waiting for service media.audio_flinger...
I/ServiceManager( 1271): Waiting for service media.audio_flinger...
I/ServiceManager( 1271): Waiting for service media.audio_flinger...
I/ServiceManager( 1271): Waiting for service media.audio_flinger...
I/Netd ( 1288): Netd 1.0 starting
if anyone knows how to solve reply imediently
and could this be a kernel problem or ram disk
I search the Internet,and find this:
There should be these erroes:
1,change the file /vendor/sec/smdk6410/init.smdk6410.rc
and put setprop ro.radio.noril yes to setprop ro.radio.noril no
change the file init.rc
and do this:
service media /system/bin/mediaserver
user media
group system audio camera graphics inet net_bt net_bt_admin
2.Sure that ALSA driver is loaded in the system successfully;
3.add ALSA to the init.rc file:
symlink /dev/snd/pcmC0D0c /dev/pcmC0D0c
symlink /dev/snd/pcmC0D0p /dev/pcmC0D0p
symlink /dev/snd/controlC0 /dev/controlC0
symlink /dev/snd/timer /dev/timer
chmod 0777 /dev/pcmC0D0c
chmod 0777 /dev/pcmC0D0p
chmod 0777 /dev/controlC0
chmod 0777 /dev/timer
chown root audio /dev/snd/controlC0
chown root audio /dev/snd/pcmC0D0c
chown root audio /dev/snd/pcmC0D0p
chown root audio /dev/snd/timer
setprop alsa.mixer.playback.master Front
setprop alsa.mixer.capture.master Capture
setprop alsa.mixer.playback.earpiece Master
setprop alsa.mixer.capture.earpiece Capture
setprop alsa.mixer.playback.headset Master
setprop alsa.mixer.playback.speaker Master
Hope this can help u!
yeah bro i fixed that but a new problem apears will post logcat as soon as i can
maybe you can ask in other phone thread bro..
MIUI 5 is totally awesome would be very happy if you could port it
Buda1996 said:
yeah bro i fixed that but a new problem apears will post logcat as soon as i can
Click to expand...
Click to collapse
Whats the problem? I'm curious ^^
i got a problem egl.bad display fixed the one i mentioned but this one kick me hard i dont know what to do wheen i get home i will post logcat
E/SurfaceFlinger( 1190): eglSwapBuffers: EGL error 0x3008 (EGL_BAD_DISP
this is one piece ok and can it be a problem couzed bz kernel i use feras jb kernel latest one
Buda1996 said:
i got a problem egl.bad display fixed the one i mentioned but this one kick me hard i dont know what to do wheen i get home i will post logcat
E/SurfaceFlinger( 1190): eglSwapBuffers: EGL error 0x3008 (EGL_BAD_DISP
this is one piece ok and can it be a problem couzed bz kernel i use feras jb kernel latest one
Click to expand...
Click to collapse
Ok, pm me the whole logcat please
Sent from my LT30p using xda premium
If you need testers i can help you x10 is now my secondary phone so there is no problem if i damage it. poorly i have no idea about android developing so i cant help in another way
Got a MI2 today MIUI5 is awesome
Hello, currently, one of our Galaxy 4.0 Players is stuck in a boot loop. I have been searching this site and a few others for over a month now for solutions and am stumped.
I have tried flashing several different US YP-G1 stock ROMs using both Heimdall and Odin, Terrasilent kernel, Steve's kernel, Icyfusion ROM, factory reset, wiping cache/dalvik.
Over a month ago, the device started randomly rebooting and showing the first time startup screen each time it rebooted like this. When it would have a random reboot however, it would get stuck in a boot loop and have to be restarted by holding the power button or pulling battery. Then after a couple weeks of that, it has since been stuck in a boot loop.
Interesting "dmesg" information that may or may not have anything to do with this are:
7.347889] init: SEC_DEVENC ***[/dev/block/mmcblk0p2][0]
7.352046] init: failed that mount s:'/dev/block/mmcblk0p2', t:'/data', f
7.362574] init: SEC_DEVENC ***[/dev/block/mmcblk0p2][0]
7.368081] init: failed that mount s:'/dev/block/mmcblk0p2', t:'/data', f
8.585066] mmc0: error -110 whilst initialising MMC card
8.655510] mmc1: new high speed SDHC card at address b368
I believe that the internal sdcard has died and have formatted the external one with the vfat and rfs partitions to act as the internal sdcard. But according to dmesg, it appears that perhaps mmcblk0p2 is trying to be mounted in the boot procedure before MMC1 is detected?
Any help is greatly appreciated and I will provide any more information as needed.
-Tony
"FATAL EXCEPTION IN SYSTEM PROCESS: ConnectivityThread"
update
Between flashing the international verions's bootloader, reflashing recovery rom, Terrasilent kernel and restoring a Nandroid backup from our other YP-G1, the mounting problems seem to be gone now.
However, there is still a bootloop problem which I believe has something to do with these logcat entries:
D/NativeDaemonConnector( 246): NativeDaemonConnector ::
D/NetdConnector( 246): run ::
D/NetdConnector( 246): listenToSocket ::
I/SystemServer( 246): Connectivity Service
W/dalvikvm( 246): threadid=17: thread exiting with uncaught exception (group=0x
40015578)
E/ ( 246): Dumpstate > /data/log/dumpstate_sys_error
V/ConnectivityService( 246): ConnectivityService starting up
E/ActivityThread( 246): Failed to find provider info for settings
E/AndroidRuntime( 246): *** FATAL EXCEPTION IN SYSTEM PROCESS: ConnectivityThre
ad
E/AndroidRuntime( 246): java.lang.NullPointerException
E/AndroidRuntime( 246): at android.provider.Settings$NameValueCache.getS
tring(Settings.java:664)
E/AndroidRuntime( 246): at android.provider.Settings$Secure.getString(Se
ttings.java:2209)
E/AndroidRuntime( 246): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:264)
E/AndroidRuntime( 246): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:61)
E/AndroidRuntime( 246): at com.android.server.ConnectivityService$Connec
tivityThread.run(ConnectivityService.java:229)
I/dumpstate( 277): begin
E/dumpstate( 277): Cannot get free space size. So, skip dumpstate.
When the problems first started before all the flashing, logcat also showed this fatal exception in ConnectivityThread
Hello,
recently I get my Teclast X89 tablet, but unfortunately it appeares to have a problem. When the battery charging level comes to 100% (at 99% everything is OK) tablet becomes totally unusable. When the screen is switched off it cannot be waken up and when I use the tablet a window pops up telling that "Process com.android.systemui has stopped", like here:
imgur.com/hjWI1lP
After restart everything is OK, but it really grinds my gears. Maybe someone know how to fix this problem?
Please halp!
Bogusz
Go to developer settings and enable android debugging. Now connect to computer set up adb drivers and post a logcat at the time of crash
MasterAwesome said:
Go to developer settings and enable android debugging. Now connect to computer set up adb drivers and post a logcat at the time of crash
Click to expand...
Click to collapse
Hello again,
I've made logcat, here is an interesting part, I think:
I/SecurityManagerService( 671): SMS received security event: App[START/com.android.keyguard]
I/WindowState( 556): WIN DEATH: Window{26a85ad0 u0 Keyguard}
I/ActivityManager( 556): Process com.android.systemui (pid 622) has died.
W/ActivityManager( 556): Scheduling restart of crashed service com.android.systemui/.SystemUIService in 0ms
W/ActivityManager( 556): Scheduling restart of crashed service com.android.keyguard/.KeyguardService in 0ms
D/InputMethodManagerService( 556): --- calledFromForegroundUserOrSystemProcess ? calling uid = 1000 system uid = 1000 calling userId = 0, foreground user id = 0, calling pid = 556dalvik.system.NativeStart.run(Native Method)
W/ActivityManager( 556): Scheduling restart of crashed service com.android.systemui/.ImageWallpaper in 0ms
I/StatusBarManagerService( 556): binder died for pkg=com.android.keyguard
I/WindowState( 556): WIN DEATH: Window{269b48a8 u0 NavigationBar}
W/InputDispatcher( 556): Attempted to unregister already unregistered input channel '268ba8e8 StatusBar (server)'
D/dalvikvm( 3948): Try to disable coredump for pid 3948
D/dalvikvm( 3948): Process 3948 nice name: com.android.systemui
D/dalvikvm( 3948): Extra Options: not specified
Click to expand...
Click to collapse
I discovered also that when the battery level drops to 99% process starts to work properly.
I include also whole log file compressed to .zip.
Still need help!
I have the same problem, even after a factory reset.
me too having the same issue. Is it hardware failure or just android?
I found a solution in an other tread :
http://forum.xda-developers.com/android/general/review-teclast-x89-baytrail-tablet-dual-t3039961