Related
Hi,
I have found problem for both mentioned ROMs. My phone behaves completely same on both roms which are presumably using Cyan's core and work. This problem can be replicated any time on both.
Here is the description:
1. Go to Contacts
2. in Contacts choose either tab Contacts or Favourites
3. Choose any contact (doesnt matter whether it has one, two or more numbers to its name) to get into Contact details and information
4. Press green hw call button on phone
=
immediately i get "Sorry! The process android.process.acore has stopped unexpectedly. Please try again. Force close"
If i try to call this way:
1. Go to Contacts
2. in Contacts choose either tab Call log or Phone
3. Choose contact
4. Press green hw button on phone and all works fine
also it works fine if you
1. Go to Contacts
2. in Contacts choose either tab Contacts or Favourites
3. Choose any contact (doesnt matter whether it has one, two or more numbers to its name) to get into Contact details and information
4. instead using green hw call button just choose number on screen and touch screen for call number and you will get successful call.
-----------------------------------------------------------------------
This is adb logcat of crash:
Code:
MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.conta
cts/.DialtactsContactsEntryActivity bnds=[83,138][157,217] }
I/ActivityManager( 111): Starting activity: Intent { act=android.intent.action.
VIEW dat=content://com.android.contacts/contacts/lookup/2322i5b23ef238d0dad28/81
cmp=com.android.contacts/.ViewContactActivity }
W/Sources ( 565): Unknown type=com.google, mime=vnd.com.google.cursor.item/cont
act_misc
W/Sources ( 565): Unknown type=com.google, mime=vnd.android.cursor.item/group_m
embership
W/Sources ( 565): Unknown type=com.google, mime=vnd.android.cursor.item/group_m
embership
I/ActivityManager( 111): Displayed activity com.android.contacts/.ViewContactAc
tivity: 449 ms (total 449 ms)
D/dalvikvm( 565): threadid=25 wakeup: interrupted
I/ActivityManager( 111): Starting activity: Intent { act=android.intent.action.
CALL_PRIVILEGED dat=content://com.android.contacts/contacts/81 }
D/AndroidRuntime( 565): Shutting down VM
W/dalvikvm( 565): threadid=3: thread exiting with uncaught exception (group=0x4
001e180)
E/AndroidRuntime( 565): Uncaught handler: thread main exiting due to uncaught e
xception
D/dalvikvm( 565): GC freed 6275 objects / 412856 bytes in 139ms
E/AndroidRuntime( 565): android.content.ActivityNotFoundException: No Activity
found to handle Intent { act=android.intent.action.CALL_PRIVILEGED dat=content:/
/com.android.contacts/contacts/81 }
E/AndroidRuntime( 565): at android.app.Instrumentation.checkStartActivit
yResult(Instrumentation.java:1408)
E/AndroidRuntime( 565): at android.app.Instrumentation.execStartActivity
(Instrumentation.java:1378)
E/AndroidRuntime( 565): at android.app.Activity.startActivityForResult(A
ctivity.java:2749)
E/AndroidRuntime( 565): at android.app.Activity.startActivity(Activity.j
ava:2855)
E/AndroidRuntime( 565): at com.android.contacts.ViewContactActivity.onKe
yDown(ViewContactActivity.java:731)
E/AndroidRuntime( 565): at android.view.KeyEvent.dispatch(KeyEvent.java:
1037)
E/AndroidRuntime( 565): at android.app.Activity.dispatchKeyEvent(Activit
y.java:2043)
E/AndroidRuntime( 565): at com.android.internal.policy.impl.PhoneWindow$
DecorView.dispatchKeyEvent(PhoneWindow.java:1631)
E/AndroidRuntime( 565): at android.view.ViewRoot.deliverKeyEventToViewHi
erarchy(ViewRoot.java:2368)
E/AndroidRuntime( 565): at android.view.ViewRoot.handleFinishedEvent(Vie
wRoot.java:2338)
E/AndroidRuntime( 565): at android.view.ViewRoot.handleMessage(ViewRoot.
java:1641)
E/AndroidRuntime( 565): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 565): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 565): at android.app.ActivityThread.main(ActivityThrea
d.java:4363)
E/AndroidRuntime( 565): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 565): at java.lang.reflect.Method.invoke(Method.java:5
21)
E/AndroidRuntime( 565): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 565): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:618)
E/AndroidRuntime( 565): at dalvik.system.NativeStart.main(Native Method)
I/Process ( 111): Sending signal. PID: 565 SIG: 3
I/dalvikvm( 565): threadid=7: reacting to signal 3
E/dalvikvm( 565): Unable to open stack trace file '/data/anr/traces.txt': Permi
ssion denied
I/DumpStateReceiver( 111): Added state dump to 1 crashes
Also I would like to clarify how to wipe phone before flashing new ROM:
1. fastboot boot recovery.zip
2. go to wipe options
3. wipe data/cache/dalvik cache (options 1,2,3)
Is there anything else I should do for wiping phone for clean installation?
Because I have feeling that action might not be working correctly either, after clean installation of phone I had all my previous packages (.apk) installed so reinstalled and wiped again and then again I did not have any packages but in market application and download I had all previous applications ready for installation. How was this remember? Thru Google Apps login and password from last time?
Please help me with this issue, I love 2.1 so much more than stock 1.6 but really cant get rid of this issue with calls.
Thank you
hi! you should post this issues on their respective thread
good luck
I think this is just a known bug to all of those eclair roms that just hasn't been fixed yet
juangil said:
hi! you should post this issues on their respective thread
good luck
Click to expand...
Click to collapse
I thought of creating own forum post as it relates not to one ROM but probably to series of ROMs using possibly one kernel or some part ?
Should I post it in SuperE or Cyan ROMs forums please lock/close this post and I will copy paste this post to relevant forums.
s0mep00p said:
I think this is just a known bug to all of those eclair roms that just hasn't been fixed yet
Click to expand...
Click to collapse
I havent found simillar issue here or looked at wrong posts. Than you for you information, means should I just use this for time being and wait for corrections?
It's already been fixed for CM-5.0.8 which should be out soon.
cyanogen said:
It's already been fixed for CM-5.0.8 which should be out soon.
Click to expand...
Click to collapse
Excellent work, cant wait! Last issue for me on this great ROM.
please help me my n1 is rebooting continuously after little use and restarts , and hanging up at the rebooting loop .. i tried to repair the phone at some service center but it didnt help me out moreover we dont have official htc service in India iam so worried about it and lost completely , i even tried cyanogen mod 7 with gingerbread but it didnt work it is still the same please help me please
sudhank said:
please help me my n1 is rebooting continuously after little use and restarts , and hanging up at the rebooting loop .. i tried to repair the phone at some service center but it didnt help me out moreover we dont have official htc service in India iam so worried about it and lost completely , i even tried cyanogen mod 7 with gingerbread but it didnt work it is still the same please help me please
Click to expand...
Click to collapse
First and easiest thing to try is to do a factory wipe right now to go back to your current base ROM. Don't install any apps. Does the problem happen? If not, next test..
Flash a STABLE ROM and DON'T install any other apps, does it happen? If no reboots, install your apps (manually from the market). Is it still okay? Next test..
Flash the ROM you were having trouble with again, with no apps, does it happen? Install your apps (manually from the market), does it happen?
You can't start guessing unless you narrow the problem. It's simple to do. Of course each time you flash a ROM, wipe data etc.. Start fresh.
When it reboots, open Command prompt in Windows and write: adb bugreport.
Look for the line containing "ARM9". Something like "ARM9 has crashed".
If you find it - return the phone, it's bad.
tried everything its a hardware issue .. how can i repair it?? help
What's up everyone
My GN1 started having the problem way before I got Gingerbread. My phone is all stock, never rooted.
I tried isolating the problem to an app or an specific thing I did to cause it to reboot.
Then I was able to confirm that the problem happens w/ the phone is charging either wall charger or USB cable . When the phone charges and I use a lot of data (browsing, youtube, IM, FB, etc.) mostly during heavy data connection use the phone will restart. None of this happens when the phone is unplugged.
Also I thought that it could've been an overheating problem but the phone runs cool, a bit warmer when charging but nothing abnormal.
Give this a try and might be the problem that you are having.
I'm having the same problem since some days!!!
And I really don't know what to do, cause I've tried ALL sort of procedure! :'-(
I have an unlocked bootloader so it'll be a problem for the Repair Service? I'm ita.
Thanks!
Sent from my Nexus One using XDA Premium App
rebooting randomly
Hi, i have the same issues here with my nexus one... i had in the past, unlocked, rooted and installed CM6, wasnt having any issues at all... but since i installed CM7, troubles started...
this week, i've done some work on that little phone... re-installed stock image, updated to 2.3.4 from OTA, done nothing else, except installing su for terminal purposes... and then, i tried to replicate troubles, which i did easily...
at first, i thought it was heat... not the case, then i remarked that it kept crashing randomly on 3g network connections, since i never have issues watching youtube on my wifi at home, but when im in the bus going to work, it crashed on youtube... so i tried other network datacomm on the 3g, and i can easily make it crash. i can never make it crash on the wifi tho...
so i started adb shell, did su, then logcat command, which gives me output in realtime of whats happening...
this output shows when i started youtube... the video started to play in portrait, so i swithc my creen landscape to get it full screen and BAM! crash, here is the output
Code:
I/WindowManager( 99): Setting rotation to 1, animFlags=0
I/ActivityManager( 99): Config changed: { scale=1.0 imsi=302/500 loc=fr_FR touch=3 keys=1/1/2 nav=3/1 orien=2 layout=34 uiMode=17 seq=5}
D/dalvikvm( 99): GC_EXPLICIT freed 304K, 44% free 5301K/9415K, external 3125K/3903K, paused 140ms
W/TimedEventQueue( 70): Event 2393 was not found in the queue, already cancelled?
D/MediaPlayer(15126): Couldn't open file on client side, trying server side
I/StagefrightPlayer( 70): setDataSource('http : //v21.lscache2.googlevideo.com/videoplayback?id=09857e993aa523f8&itag=18&uaopt=no-save&ip=0.0.0.0&ipbits=0&expire=1307568226&sparams=id,itag,uaopt,ip,ipbits,expire&signature=E5F3700F4F5B82898EB4D207F05C187045243C55.D9B8BFD850E01766AC708F880046A3333B5E29E1&key=yta1&el=standard&devKey=ATdpM7DMA4JyVrf7elHDrdsO88HsQjpE1a8d1GxQnGDm&app=youtube_gdata')
I/NuHTTPDataSource( 70): connect to v21.lscache2.googlevideo.com:80/videoplayback?id=09857e993aa523f8&itag=18&uaopt=no-save&ip=0.0.0.0&ipbits=0&expire=1307568226&sparams=id,itag,uaopt,ip,ipbits,expire&signature=E5F3700F4F5B82898EB4D207F05C187045243C55.D9B8BFD850E01766AC708F880046A3333B5E29E1&key=yta1&el=standard&devKey=ATdpM7DMA4JyVrf7elHDrdsO88HsQjpE1a8d1GxQnGDm&app=youtube_gdata @0
W/libutils.threads( 70): Thread (this=0x12608): don't call waitForExit() from this Thread object's thread. It's a guaranteed deadlock!
I/OMXCodec( 70): [OMX.qcom.video.decoder.avc] allocating 4 buffers of size 460800 on input port
I/OMXCodec( 70): [OMX.qcom.video.decoder.avc] allocating 8 buffers of size 345600 on output port
D/AudioHardwareQSD( 70): AudioHardware pcm playback is going to standby.
W/YouTube (15126): Avoiding double logging of play start
W/QCvdec ( 70): H264_Utils::check_header
W/QCvdec ( 70): check_header: start code 29
I/NuCachedSource2( 70): new range: offset= 1852430
I/NuHTTPDataSource( 70): connect to v21.lscache2.googlevideo.com:80/videoplayback?id=09857e993aa523f8&itag=18&uaopt=no-save&ip=0.0.0.0&ipbits=0&expire=1307568226&sparams=id,itag,uaopt,ip,ipbits,expire&signature=E5F3700F4F5B82898EB4D207F05C187045243C55.D9B8BFD850E01766AC708F880046A3333B5E29E1&key=yta1&el=standard&devKey=ATdpM7DMA4JyVrf7elHDrdsO88HsQjpE1a8d1GxQnGDm&app=youtube_gdata @1852430
W/AudioFlinger( 70): write blocked for 179 msecs, 2 delayed writes, thread 0xea00
another example, was that i wanted to install rom manager, so i went on the market, downloaded rom manager and BAM! crashed, here is a few last line of the logcat output
Code:
W/System.err( 407): at dalvik.system.NativeStart.main(Native Method)
I/TelephonyRegistry( 99): notifyServiceState: 0 home Videotron 302500 UMTS CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false
I/TelephonyRegistry( 99): notifyDataConnection: state=2 isDataConnectivityPossible=true reason=null interfaceName=rmnet0 networkType=3
I/ActivityManager( 99): Starting: Intent { dat=market://details?id=com.koushikdutta.rommanager cmp=com.android.vending/.AssetInfoActivity } from pid 407
I/ActivityManager( 99): No longer want com.android.mms (pid 385): hidden #16
D/dalvikvm( 256): GC_EXPLICIT freed 424K, 47% free 4239K/7879K, external 3230K/3696K, paused 47ms
I/LicenseChecker( 539): Received response.
I/LicenseChecker( 539): Clearing timeout.
I/dalvikvm( 539): Total arena pages for JIT: 11
I/ActivityManager( 99): Displayed com.android.vending/.AssetInfoActivity: +352ms
I/vending ( 256): [1] PermissionsSection.getPermissionGroupLabels(): Invalid group name: null
I/LicenseChecker( 539): Received response.
I/LicenseChecker( 539): Clearing timeout.
D/dalvikvm( 407): GC_CONCURRENT freed 797K, 49% free 3694K/7239K, external 3261K/3411K, paused 3ms+3ms
I/RomNexus( 407): Using gzip for download.
W/KeyCharacterMap( 256): No keyboard for id 131074
W/KeyCharacterMap( 256): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
I/TelephonyRegistry( 99): notifyServiceState: 0 home Videotron 302500 HSDPA CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false
I/TelephonyRegistry( 99): notifyDataConnection: state=2 isDataConnectivityPossible=true reason=null interfaceName=rmnet0 networkType=8
E/C2DMRegistrar( 201): [C2DMReg] handleRequest caught javax.net.ssl.SSLException: Connection closed by peer
I/C2DMReceiver( 407): SERVICE_NOT_AVAILABLE
W/webcore ( 407): Can't get the viewWidth after the first layout
I/TelephonyRegistry( 99): notifyServiceState: 0 home Videotron 302500 UMTS CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false
I/TelephonyRegistry( 99): notifyDataConnection: state=2 isDataConnectivityPossible=true reason=null interfaceName=rmnet0 networkType=3
D/dalvikvm( 407): GC_EXTERNAL_ALLOC freed 662K, 48% free 3782K/7239K, external 3357K/3411K, paused 38ms
D/dalvikvm( 407): GC_EXTERNAL_ALLOC freed 14K, 48% free 3783K/7239K, external 3849K/3921K, paused 34ms
D/dalvikvm( 407): GC_EXTERNAL_ALLOC freed 128K, 48% free 3812K/7239K, external 4286K/4392K, paused 40ms
now i did executed a adb bugreport, i can see the following, if i search for ARM9
Code:
[ 460.500457] ARM9 has CRASHED
[ 460.500518] smem: DIAG '[WCDMA] 02:18:58 FATAL: WCDMA L2 DL (dsmi.c:00191) (0)
that crash code looks really like a 3G connection issues...
here is the header of the bugreport
Code:
Build: GRJ22
Bootloader: 0.35.0017
Radio: 5.12.00.08
Network: Videotron
Kernel: Linux version 2.6.35.7-59463-g52630a3 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 PREEMPT Tue Mar 29 11:49:12 PDT 2011
Command line: board_mahimahi.disable_uart3=0 board_mahimahi.usb_h2w_sw=0 board_mahimahi.disable_sdcard=0 diag.enabled=0 board_mahimahi.debug_uart=0 smisize=0 androidboot.baseband=5.12.00.08 androidboot.cid=GOOGL001 androidboot.carrier=GOOGLE androidboot.mid=PB9910000 androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=HT08LP803098 androidboot.bootloader=0.35.0017 no_console_suspend=1 wire.search_count=5
well, i havnt fixed the issue, i just got a replacement nexusone...
I have found threads with similar problems than mine, but none of the solutions worked for me (i also tried WiFi Fixer).
I have latest CM10 + Devil's Kernel at the moment, but it was going on for a week now also on Semaphore, CM10 kernels and HellyBean rom, although i don't think it is their fault.
Update: I am updating nightlies regularly lately, have also switched back to Semaphore Kernel
I have excellent Wi-Fi connection, but if i leave the phone for a while, i cannot connect to internet anymore. Wi-Fi is still connected, the Wi-fi icon is gray or blue with moving arrows up and down. I can browse local network and my PC's shared folders.
Temporary solution is to disable and re-enable Wi-Fi. Obviously also if i reset the phone or router, but that doesn't matter.
There is no problem with router or access point. It has been working great for years. DHCP always assigns same IP to my phone's MAC address.
I can ping my computer and router, but cannot ping internet - even IP's. (connect: Network is unreachable)
I read somewhere that it is Samsung's (or even i9000) problem with Wi-Fi sleep - that when it should wake up, it does only partially.
I have flashed my phone several times recently but always in CWM, not with Odin, but the problem stays.
I believe it is something wrong with baseband (radio/modem), but don't know if this get flashed with new versions of ROM. I have I9000XXJVT version (System settings/About phone). Edit: i have flashed another modem XXJVU, but problem remains.
If someone also believes this could be the case and has more knowledge than me, what is the procedure to flash only baseband, can i do it from CWM and which version should i look for?
Logcat
I have switched WIFI channels from 11 to 6, tried to change encryption, but it didn't solve the problem.
This is logcat since turning off the screen (internet was working) until start of the problem.. i hope paste will do - it is a short one.
Code:
08-26 09:47:00.800 D/SurfaceFlinger( 489): About to give-up screen, flinger = 0x419caaf0
08-26 09:47:06.011 I/goggles ( 1726): BaseApplication: Getting userWantsHistory = false
08-26 09:47:06.421 D/dalvikvm( 1726): GC_CONCURRENT freed 1870K, 66% free 2808K/8195K, paused 72ms+3ms, total 231ms
08-26 09:47:06.421 D/dalvikvm( 1726): WAIT_FOR_CONCURRENT_GC blocked 112ms
08-26 09:47:06.507 I/goggles ( 1726): FreshnessHelper: Checking for images newer than 1345938048000
08-26 09:47:15.324 V/LockPatternKeyguardView( 664): Set visibility on [email protected]cb8 to 8388608
08-26 09:47:15.511 V/TransportControlView( 664): Create TCV [email protected]
08-26 09:47:15.824 V/KeyguardViewManager( 664): KGVM: Set visibility on com.an[email protected]40edc000 to 6291456
08-26 09:47:15.839 D/PhoneStatusBar( 945): disable: < expand icons alerts ticker system_info back home RECENT* clock >
08-26 09:47:16.019 D/dalvikvm( 664): GC_CONCURRENT freed 2953K, 41% free 13847K/23175K, paused 13ms+46ms, total 218ms
08-26 09:47:16.019 D/dalvikvm( 664): WAIT_FOR_CONCURRENT_GC blocked 120ms
08-26 09:47:16.050 V/LockPatternKeyguardView( 664): Set visibility on [email protected]cb8 to 8388608
08-26 09:47:16.054 D/PhoneStatusBar( 945): disable: < expand icons alerts ticker system_info BACK* HOME* RECENT CLOCK* >
08-26 09:47:16.144 V/LockPatternKeyguardView( 664): Set visibility on [email protected]cb8 to 8388608
08-26 09:48:07.023 I/goggles ( 1726): BaseApplication: Getting userWantsHistory = false
08-26 09:48:07.281 I/goggles ( 1726): FreshnessHelper: Checking for images newer than 1345938048000
08-26 09:48:19.023 D/ConnectivityService( 664): ConnectivityChange for WIFI: CONNECTED/CONNECTED
08-26 09:48:19.027 D/ConnectivityService( 664): handleConnectivityChange: address are the same reset per doReset linkProperty[1]: resetMask=0
08-26 09:48:19.050 D/ConnectivityService( 664): ConnectivityChange for WIFI: CONNECTED/CONNECTED
08-26 09:48:19.058 D/ConnectivityService( 664): handleConnectivityChange: address are the same reset per doReset linkProperty[1]: resetMask=0
[COLOR="red"]08-26 09:48:20.027 D/ConnectivityService( 664): NetTransition Wakelock for WifiStateMachine released by timeout[/COLOR]
08-26 09:49:02.027 D/Sensors ( 664): Smb380Sensor::~enable(0, 1)
08-26 09:49:02.027 D/Sensors ( 664): Smb380Sensor::~enable(0, 1) open /sys/class/input/event1/device/enable
08-26 09:49:02.027 D/Sensors ( 664): Smb380Sensor::~enable(0, 1) opened /sys/class/input/event1/device/enable
08-26 09:49:02.035 D/Sensors ( 664): Smb380Sensor::~setDelay(0, 200000000)
08-26 09:49:02.035 D/Sensors ( 664): Smb380Sensor::~setDelay(0, 66667000)
08-26 09:49:02.187 I/WindowManager( 664): Lock screen displayed!
08-26 09:49:02.210 D/SurfaceFlinger( 489): Screen about to return, flinger = 0x419caaf0
08-26 09:49:02.472 D/Tethering( 664): MasterInitialState.processMessage what=3
08-26 09:49:02.609 D/Tethering( 664): MasterInitialState.processMessage what=3
08-26 09:49:03.003 [COLOR="Red"]D/ConnectivityService( 664): handleInetConditionHoldEnd: net=1, condition=100, published condition=0[/COLOR]
08-26 09:49:03.214 D/PicasaUploaderSyncManager(24298): active network: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
08-26 09:49:03.214 D/PicasaUploaderSyncManager(24298): background data: true
08-26 09:49:03.496 W/ContextScopeImpl(24312): thread=1 tried to enter the scope of the application context. Ignored.
08-26 09:49:03.503 W/ContextScopeImpl(24312): thread=1 tried to enter the scope of the application context. Ignored.
08-26 09:49:03.519 I/goggles ( 1726): BaseApplication: Getting userWantsHistory = false
08-26 09:49:03.691 I/goggles ( 1726): FreshnessHelper: Checking for images newer than 1345938048000
08-26 09:49:03.917 D/PicasaSyncManager(22933): active network: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
08-26 09:49:03.917 D/PicasaSyncManager(22933): background data: true
08-26 09:49:04.074 W/ContextScopeImpl(24312): thread=1 tried to enter the scope of the application context. Ignored.
08-26 09:49:04.082 W/ContextScopeImpl(24312): thread=1 tried to enter the scope of the application context. Ignored.
08-26 09:49:04.093 I/goggles ( 1726): BaseApplication: Getting userWantsHistory = false
08-26 09:49:04.187 D/PicasaUploaderSyncManager(24298): active network: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
08-26 09:49:04.222 D/PicasaUploaderSyncManager(24298): background data: true
08-26 09:49:04.246 D/PicasaSyncManager(22933): active network: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
08-26 09:49:04.246 D/PicasaSyncManager(22933): background data: true
08-26 09:49:04.464 D/dalvikvm( 1726): GC_CONCURRENT freed 1854K, 66% free 2797K/8195K, paused 81ms+67ms, total 245ms
08-26 09:49:04.464 D/dalvikvm( 1726): WAIT_FOR_CONCURRENT_GC blocked 136ms
08-26 09:49:04.503 I/goggles ( 1726): FreshnessHelper: Checking for images newer than 1345938048000
08-26 09:49:06.394 I/ActivityManager( 664): Process com.tmobile.thememanager (pid 24054) has died.
08-26 09:49:12.039 D/Sensors ( 664): Smb380Sensor::~enable(0, 0)
08-26 09:49:12.050 D/Sensors ( 664): Smb380Sensor::~enable(0, 0) open /sys/class/input/event1/device/enable
08-26 09:49:12.050 D/Sensors ( 664): Smb380Sensor::~enable(0, 0) opened /sys/class/input/event1/device/enable
08-26 09:49:12.066 D/Sensors ( 664): Smb380Sensor::~setDelay(0, 66667000)
08-26 09:49:12.441 D/dalvikvm( 664): GC_CONCURRENT freed 2495K, 39% free 14281K/23175K, paused 18ms+11ms, total 137ms
08-26 09:49:12.441 D/dalvikvm( 664): WAIT_FOR_CONCURRENT_GC blocked 109ms
08-26 09:49:12.445 D/dalvikvm( 664): WAIT_FOR_CONCURRENT_GC blocked 79ms
08-26 09:49:12.457 V/TransportControlView( 664): Create TCV [email protected]
08-26 09:49:12.570 D/SurfaceFlinger( 489): About to give-up screen, flinger = 0x419caaf0
08-26 09:49:12.656 V/LockPatternKeyguardView( 664): Set visibility on [email protected]cb8 to 8388608
08-26 09:49:12.687 V/LockPatternKeyguardView( 664): Set visibility on [email protected]cb8 to 8388608
[COLOR="Red"]08-26 09:49:23.093 W/ThrottleService( 664): unable to find stats for iface pdp0[/COLOR]
08-26 09:50:07.011 I/goggles ( 1726): BaseApplication: Getting userWantsHistory = false
08-26 09:50:07.203 I/goggles ( 1726): FreshnessHelper: Checking for images newer than 1345938048000
08-26 09:50:08.261 D/dalvikvm( 664): WAIT_FOR_CONCURRENT_GC blocked 0ms
08-26 09:50:08.382 D/dalvikvm( 664): GC_EXPLICIT freed 1119K, 38% free 14381K/23175K, paused 8ms+8ms, total 121ms
08-26 09:50:44.695 D/ConnectivityService( 664): ConnectivityChange for WIFI: CONNECTED/CONNECTED
08-26 09:50:44.707 D/ConnectivityService( 664): handleConnectivityChange: address are the same reset per doReset linkProperty[1]: resetMask=0
08-26 09:50:44.718 D/ConnectivityService( 664): ConnectivityChange for WIFI: CONNECTED/CONNECTED
08-26 09:50:44.734 D/ConnectivityService( 664): handleConnectivityChange: address are the same reset per doReset linkProperty[1]: resetMask=0
[COLOR="red"]08-26 09:50:45.699 D/ConnectivityService( 664): NetTransition Wakelock for WifiStateMachine released by timeout[/COLOR]
08-26 09:51:07.242 I/goggles ( 1726): BaseApplication: Getting userWantsHistory = false
08-26 09:51:07.421 I/goggles ( 1726): FreshnessHelper: Checking for images newer than 1345938048000
08-26 09:51:07.425 D/Tethering( 664): MasterInitialState.processMessage what=3
08-26 09:51:07.453 D/Tethering( 664): MasterInitialState.processMessage what=3
08-26 09:51:07.589 W/ContextScopeImpl(24312): thread=1 tried to enter the scope of the application context. Ignored.
08-26 09:51:07.609 W/ContextScopeImpl(24312): thread=1 tried to enter the scope of the application context. Ignored.
08-26 09:51:07.625 I/goggles ( 1726): BaseApplication: Getting userWantsHistory = false
08-26 09:51:07.625 D/PicasaUploaderSyncManager(24298): active network: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
08-26 09:51:07.828 D/PicasaSyncManager(22933): active network: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
08-26 09:51:07.863 D/dalvikvm( 1726): GC_CONCURRENT freed 1840K, 66% free 2800K/8195K, paused 19ms+26ms, total 93ms
08-26 09:51:07.863 D/dalvikvm( 1726): WAIT_FOR_CONCURRENT_GC blocked 21ms
08-26 09:51:07.910 I/goggles ( 1726): FreshnessHelper: Checking for images newer than 1345938048000
08-26 09:51:07.933 D/PicasaUploaderSyncManager(24298): background data: true
08-26 09:51:07.937 D/PicasaSyncManager(22933): background data: true
08-26 09:51:07.964 D/PicasaUploaderSyncManager(24298): active network: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
08-26 09:51:07.964 D/PicasaUploaderSyncManager(24298): background data: true
08-26 09:51:07.980 W/ContextScopeImpl(24312): thread=1 tried to enter the scope of the application context. Ignored.
08-26 09:51:07.984 D/ConnectivityService( 664): handleInetConditionHoldEnd: net=1, condition=100, published condition=0
08-26 09:51:07.992 W/ContextScopeImpl(24312): thread=1 tried to enter the scope of the application context. Ignored.
08-26 09:51:08.003 I/goggles ( 1726): BaseApplication: Getting userWantsHistory = false
08-26 09:51:08.199 I/goggles ( 1726): FreshnessHelper: Checking for images newer than 1345938048000
08-26 09:51:08.218 D/PicasaSyncManager(22933): active network: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
08-26 09:51:08.222 D/PicasaSyncManager(22933): background data: true
08-26 09:51:10.476 D/dalvikvm(24085): GC_CONCURRENT freed 3810K, 60% free 3334K/8195K, paused 13ms+4ms, total 58ms
[COLOR="Red"]08-26 09:51:11.253 W/SocketClient( 487): write error (Broken pipe)
08-26 09:51:13.292 W/SocketClient( 487): write error (Broken pipe)
08-26 09:51:15.332 W/SocketClient( 487): write error (Broken pipe)
08-26 09:51:17.375 W/SocketClient( 487): write error (Broken pipe)
08-26 09:51:21.023 W/SocketClient( 487): write error (Broken pipe)[/COLOR]
08-26 09:51:21.152 I/ActivityManager( 664): Start proc com.google.android.gm for service com.google.android.gm/.provider.MailSyncAdapterService: pid=24550 uid=10047 gids={3003, 1015, 1028}
08-26 09:51:21.171 E/Trace (24550): error opening trace file: No such file or directory (2)
08-26 09:51:21.468 I/ActivityThread(24550): Pub gmail-ls: com.google.android.gm.provider.MailProvider
08-26 09:51:21.503 I/ActivityThread(24550): Pub com.google.android.gmail.SuggestionProvider: com.google.android.gm.SuggestionsProvider
08-26 09:51:21.507 I/ActivityThread(24550): Pub com.google.android.gm: com.google.android.gm.provider.PublicContentProvider
08-26 09:51:21.953 I/Gmail (24550): calculateUnknownSyncRationalesAndPurgeInBackground: queueing
08-26 09:51:21.976 I/Gmail (24550): calculateUnknownSyncRationalesAndPurgeInBackground: queueing
08-26 09:51:22.031 I/Gmail (24550): calculateUnknownSyncRationalesAndPurgeInBackground: running
08-26 09:51:22.031 I/Gmail (24550): calculateUnknownSyncRationalesAndPurgeInBackground: running
08-26 09:51:22.078 I/Gmail (24550): MainSyncRequestProto: lowestBkwdConvoId: 0, highestHandledServerOp: 63483, normalSync: true
08-26 09:51:22.250 W/SocketClient( 487): write error (Broken pipe)
[COLOR="red"]08-26 09:51:22.273 E/Gmail (24550): IOException: Unable to resolve host "android.clients.google.com": [/COLOR]No address associated with hostname
08-26 09:51:22.316 D/SyncManager( 664): failed sync operation [email protected] (com.google), gmail-ls, SERVER, earliestRunTime 22107560, SyncResult: stats [ numIoExceptions: 1]
Solved?
Since last time i had problem i have reflashed radio via odin, but then my IMEI disappeared.
Then i flashed radio via CWM and there are no problems for 15 minutes. :victory:
Edit: I have solved the problem by flashing only modem (=radio=baseband) files from recovery mode (CWM).
I've used modem files found here: http://forum.xda-developers.com/showthread.php?t=1158783
xxjvu and xwjw1 both worked for me.
Hello
I have the same problem as you, my s3 is new and has the factory rom.
I do not quite understand how you solved it. Could you explain it better.
In the link above there are many modem files, which is correct?
I need to root the phone? it's affect the warranty?
Thank you very much
aambro said:
Since last time i had problem i have reflashed radio via odin, but then my IMEI disappeared.
Then i flashed radio via CWM and there are no problems for 15 minutes. :victory:
Edit: I have solved the problem by flashing only modem (=radio=baseband) files from recovery mode (CWM).
I've used modem files found here: http://forum.xda-developers.com/showthread.php?t=1158783
xxjvu and xwjw1 both worked for me.
Click to expand...
Click to collapse
aambro said:
Since last time i had problem i have reflashed radio via odin, but then my IMEI disappeared.
Then i flashed radio via CWM and there are no problems for 15 minutes. :victory:
Edit: I have solved the problem by flashing only modem (=radio=baseband) files from recovery mode (CWM).
I've used modem files found here: http://forum.xda-developers.com/showthread.php?t=1158783
xxjvu and xwjw1 both worked for me.
Click to expand...
Click to collapse
thank you very much this helps me...
EDIT: With the exposed method working well, I think it goes without saying that I will be moving on from this thread. Now on to the ouya store on CM10! lol
If for some reason you come here from google or some other place, the thread your looking for to get the play store working is below.
http://forum.xda-developers.com/showthread.php?t=2350639
Original----------------------------------------------------------------------------
This thread will be for working on getting the Google Play Store to work, aka com.android.vending.
Here is a logcat of the play crash when the vending apk has been sideloaded along with the google login and framework apks to /system/app. This was not from flashing the gapps.zip with CWM, this was sideloading the com.android.vending-4.0.25.apk... and GoogleLoginService.apk and GoogleServicesFramework.apk and setting permissions to 6755...
Process com.android.vending has crashed too many times
: killing!
I/ActivityManager( 310): Killing proc 2860:com.android.vending/u0a61: crash
V/DropBoxReceiver( 2593): Starting service for tag: system_app_crash, time: 1369
507749067
D/CrashReportService( 2593): Writing crash report to: /data/data/tv.ouya/cache/.
reports/1369507749067
W/ActivityManager( 310): Unable to launch app com.android.vending/10061 for ser
vice Intent { cmp=com.android.vending/com.google.android.finsky.services.DailyHy
giene }: process is bad
Click to expand...
Click to collapse
I also tried editing the /system/build.prop to say the device was a galaxy s4... same error on logcat...
adding the crash report files that should be in /data/data/tv.ouya/cache... not sure how to get the report data out of the bin file though.
tried this too... same
http://forum.xda-developers.com/showthread.php?p=40823085
tried the old kindle market. the EULA comes up click except and then dies. different logcat though...
http://forum.xda-developers.com/showthread.php?p=41831758#post41831758
Process com.android.vending (pid 1340) has died.
D/CrashReportService( 563): Writing crash report to: /data/data/tv.ouya/cache/.
reports/1369511460591
W/InputMethodManagerService( 311): Window already focused, ignoring focus gain
of: [email protected] attribute=n
ull
Click to expand...
Click to collapse
professorpoptart said:
tried the old kindle market. the EULA comes up click except and then dies. different logcat though...
http://forum.xda-developers.com/showthread.php?p=41831758#post41831758
Click to expand...
Click to collapse
I'm working with the full gapps install and having no better luck. As long as I don't sign into my google account the rest of the ouya functions fine, but as soon as i log in I start getting "com.google.process.gapps" and play store crash messages, even if I never open the store and sign in through music.
Update: I think we need to meet somewhere in the middle. I may be way off, but heres my reasoning...
I have installed the full gapps on my Ouya, and I can't get the terms to pull up on either market. You have no gapps installed and it is getting a little further but still crashing. I believe I have something on there the ouya doesn't like and that's stopping me, and you are missing something the play store needs. I was able to get my error to stop by uninstalling the talk.apk, but still no play store.
Are you getting the same logcat's?... just got to find the right thing to google! lol
This is with the old kindle apk from qwerty790
I/ActivityThread( 1306): Pub com.android.vending.SuggestionsProvider: com.androi
d.vending.SuggestionsProvider
D/vending ( 1306): [1] VendingApplication.onCreate(): Resetting ServiceLocator f
rom app
D/dalvikvm( 1306): GC_CONCURRENT freed 722K, 7% free 11293K/12103K, paused 5ms+3
ms, total 32ms
D/dalvikvm( 1306): WAIT_FOR_CONCURRENT_GC blocked 17ms
W/ResourceType( 1306): Failure getting entry for 0x7f020052 (t=1 e=82) in packag
e 0 (error -75)
D/AndroidRuntime( 1306): Shutting down VM
W/dalvikvm( 1306): threadid=1: thread exiting with uncaught exception (group=0x4
1022300)
E/AndroidRuntime( 1306): FATAL EXCEPTION: main
E/AndroidRuntime( 1306): java.lang.RuntimeException: Unable to start activity Co
mponentInfo{com.android.vending/com.android.vending.AssetBrowserActivity}: andro
id.view.InflateException: Binary XML file line #54: Error inflating class <unkno
wn>
Click to expand...
Click to collapse
this is from the start of the activity from the top of the error stack.
professorpoptart said:
Are you getting the same logcat's?... just got to find the right thing to google! lol
This is with the old kindle apk from qwerty790
Click to expand...
Click to collapse
Not even close. I'll post mine in a bit.
as much of a "bad" idea it is we could write script to recursive (or do it by hand) chmod 777 everything in /system to make sure it everything has permissions to do what it needs... unless the issue is the perms have to be set specifically... but I would think the gapps would have set them correctly if that was the case...
edit: ...almost beer o'clock!
sonofskywalker3 said:
Not even close. I'll post mine in a bit.
Click to expand...
Click to collapse
After installing the gapps did you clear cache?
looking into "com.android.vending.SuggestionsProvider" seems like its usually a cache issue. I get the same logcat after clearing in recovery but just hoping since you have the whole gapps and different errors this mighht be it.
found the cache idea here...http://forum.xda-developers.com/showthread.php?t=649149
ok so I went back to the 4.1.2 gapps files for vending and framework, set permissions and cleared cache. Still dies but now I get a toast fc message. now I'm getting something about the login service in the cat log.
here is the full logcat, did a logcat -c right before launching play. so the whole stack is the play event...
--------- beginning of /dev/log/main
D/su ( 1540): su invoked.
D/su ( 1541): Allowing root/shell.
D/su ( 1543): 2000 /system/bin/mksh executing 0 /system/bin/sh using shell
/system/bin/sh : sh
D/AndroidRuntime( 1542):
D/AndroidRuntime( 1542): >>>>>> AndroidRuntime START com.android.internal.os.Run
timeInit <<<<<<
D/AndroidRuntime( 1542): CheckJNI is OFF
D/dalvikvm( 1542): Trying to load lib libjavacore.so 0x0
D/dalvikvm( 1542): Added shared lib libjavacore.so 0x0
D/dalvikvm( 1542): Trying to load lib libnativehelper.so 0x0
D/dalvikvm( 1542): Added shared lib libnativehelper.so 0x0
I/ethernet( 1542): Loading ethernet jni class
D/AndroidRuntime( 1542): Calling main entry com.android.commands.am.Am
--------- beginning of /dev/log/system
I/ActivityManager( 309): Start proc com.koushikdutta.superuser for broadcast co
m.koushikdutta.superuser/.SuReceiver: pid=1554 uid=10038 gids={1028}
D/AndroidRuntime( 1542): Shutting down VM
I/AndroidRuntime( 1542): NOTE: attach of thread 'Binder_3' failed
D/dalvikvm( 1542): GC_CONCURRENT freed 100K, 88% free 492K/4096K, paused 1ms+0ms
, total 4ms
I/ActivityManager( 309): No longer want com.google.android.gsf.login (pid 1518)
: hidden #2
I/ActivityManager( 309): START {act=android.intent.action.MAIN cat=[android.int
ent.category.LAUNCHER] flg=0x10200000 cmp=com.android.vending/.AssetBrowserActiv
ity bnds=[960,540][960,540] u=0} from pid 1082
I/ActivityManager( 309): Start proc com.android.vending for activity com.androi
d.vending/.AssetBrowserActivity: pid=1568 uid=10061 gids={3003, 1015, 1023, 1028
}
I/ActivityThread( 1568): Pub com.google.android.finsky.RecentSuggestionsProvider
: com.google.android.finsky.providers.RecentSuggestionsProvider
I/ActivityThread( 1568): Pub com.google.android.finsky.QSBSuggestionsProvider2:
com.google.android.finsky.providers.QSBSuggestionsProvider
I/ActivityThread( 1568): Pub com.google.android.finsky.AppIconProvider: com.goog
le.android.finsky.providers.AppIconProvider
D/Finsky ( 1568): [1] FinskyApp.onCreate: Clearing cache due to crash on previo
us run.
D/Volley ( 1568): [1] DiskBasedCache.clear: Cache cleared.
I/dalvikvm( 1568): DexOpt: access denied from Lcom/google/android/volley/elegant
/ElegantThreadSafeConnManager$ElegantPool; to field Lorg/apache/http/impl/conn/t
sccm/ConnPoolByRoute;.poolLock
W/dalvikvm( 1568): VFY: unable to resolve instance field 10430
D/dalvikvm( 1568): VFY: replacing opcode 0x54 at 0x0000
I/dalvikvm( 1568): DexOpt: access denied from Lcom/google/android/volley/elegant
/ElegantThreadSafeConnManager$ElegantPool; to field Lorg/apache/http/impl/conn/t
sccm/ConnPoolByRoute;.poolLock
W/dalvikvm( 1568): VFY: unable to resolve instance field 10430
D/dalvikvm( 1568): VFY: replacing opcode 0x54 at 0x0000
I/dalvikvm( 1568): DexOpt: access denied from Lcom/google/android/volley/elegant
/ElegantThreadSafeConnManager$ElegantPool; to field Lorg/apache/http/impl/conn/t
sccm/ConnPoolByRoute;.poolLock
W/dalvikvm( 1568): VFY: unable to resolve instance field 10430
D/dalvikvm( 1568): VFY: replacing opcode 0x54 at 0x0020
I/dalvikvm( 1568): DexOpt: access denied from Lcom/google/android/volley/elegant
/ElegantThreadSafeConnManager$ElegantPool; to field Lorg/apache/http/impl/conn/t
sccm/ConnPoolByRoute;.poolLock
I/dalvikvm( 1568): DexOpt: unable to optimize instance field ref 0x28be at 0x42
in Lcom/google/android/volley/elegant/ElegantThreadSafeConnManager$ElegantPool;.
getEntryBlocking
I/dalvikvm( 1568): DexOpt: access denied from Lcom/google/android/volley/elegant
/ElegantThreadSafeConnManager$ElegantPool; to field Lorg/apache/http/impl/conn/t
sccm/ConnPoolByRoute;.poolLock
I/dalvikvm( 1568): DexOpt: unable to optimize instance field ref 0x28be at 0x76
in Lcom/google/android/volley/elegant/ElegantThreadSafeConnManager$ElegantPool;.
getEntryBlocking
I/dalvikvm( 1568): DexOpt: access denied from Lcom/google/android/volley/elegant
/ElegantThreadSafeConnManager$ElegantPool; to field Lorg/apache/http/impl/conn/t
sccm/ConnPoolByRoute;.poolLock
I/dalvikvm( 1568): DexOpt: unable to optimize instance field ref 0x28be at 0xec
in Lcom/google/android/volley/elegant/ElegantThreadSafeConnManager$ElegantPool;.
getEntryBlocking
D/Finsky ( 1568): [1] FinskyApp.onCreate: Initializing network with DFE https:/
/android.clients.google.com/fdfe/
D/Finsky ( 1568): [1] DailyHygiene.goMakeHygieneIfDirty: Dirty, need more hygie
ne.
D/dalvikvm( 1568): GC_CONCURRENT freed 609K, 6% free 11398K/12103K, paused 14ms+
4ms, total 52ms
D/dalvikvm( 1568): WAIT_FOR_CONCURRENT_GC blocked 22ms
E/AndroidHttpClient( 1568): Leak found
E/AndroidHttpClient( 1568): java.lang.IllegalStateException: AndroidHttpClient c
reated and never closed
E/AndroidHttpClient( 1568): at com.google.android.volley.AndroidHttpClient.<
init>(AndroidHttpClient.java:175)
E/AndroidHttpClient( 1568): at com.google.android.volley.AndroidHttpClient.n
ewInstance(AndroidHttpClient.java:161)
E/AndroidHttpClient( 1568): at com.google.android.volley.GoogleHttpClient.<i
nit>(GoogleHttpClient.java:117)
E/AndroidHttpClient( 1568): at com.google.android.finsky.FinskyApp.onCreate(
FinskyApp.java:295)
E/AndroidHttpClient( 1568): at android.app.Instrumentation.callApplicationOn
Create(Instrumentation.java:999)
E/AndroidHttpClient( 1568): at android.app.ActivityThread.handleBindApplicat
ion(ActivityThread.java:4151)
E/AndroidHttpClient( 1568): at android.app.ActivityThread.access$1300(Activi
tyThread.java:130)
E/AndroidHttpClient( 1568): at android.app.ActivityThread$H.handleMessage(Ac
tivityThread.java:1255)
E/AndroidHttpClient( 1568): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidHttpClient( 1568): at android.os.Looper.loop(Looper.java:137)
E/AndroidHttpClient( 1568): at android.app.ActivityThread.main(ActivityThrea
d.java:4745)
E/AndroidHttpClient( 1568): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidHttpClient( 1568): at java.lang.reflect.Method.invoke(Method.java:5
11)
E/AndroidHttpClient( 1568): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:786)
E/AndroidHttpClient( 1568): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:553)
E/AndroidHttpClient( 1568): at dalvik.system.NativeStart.main(Native Method)
I/ActivityManager( 309): Start proc com.google.android.gsf.login for service co
m.google.android.gsf.login/com.google.android.gsf.loginservice.GoogleLoginServic
e: pid=1600 uid=10044 gids={3003, 1007, 2001, 3006, 1028}
D/Finsky ( 1568): [1] 2.run: Loaded library for account: [FljaznBLk4v9VpY6BInpX
qtpvXA]
D/Finsky ( 1568): [1] 2.run: Finished loading 1 libraries.
D/libEGL ( 1568): loaded /system/lib/egl/libEGL_tegra.so
E/ ( 1568): file /data/data/com.nvidia.NvCPLSvc/files/driverlist.txt: not
found!
I/ ( 1568): Attempting to load EGL implementation /system/lib//egl/libEGL
_tegra_impl
I/ ( 1568): Loaded EGL implementation /system/lib//egl/libEGL_tegra_impl
D/libEGL ( 1568): loaded /system/lib/egl/libGLESv1_CM_tegra.so
D/dalvikvm( 309): GC_CONCURRENT freed 1104K, 17% free 15096K/17991K, paused 5ms
+11ms, total 107ms
D/libEGL ( 1568): loaded /system/lib/egl/libGLESv2_tegra.so
I/ ( 1568): Loading GLESv2 implementation /system/lib//egl/libGLESv2_tegr
a_impl
D/OpenGLRenderer( 1568): Enabling debug mode 0
I/ActivityManager( 309): No longer want com.koushikdutta.superuser (pid 1554):
hidden #2
W/dalvikvm( 1568): threadid=13: thread exiting with uncaught exception (group=0x
40bed300)
E/AndroidRuntime( 1568): FATAL EXCEPTION: Thread-139
E/AndroidRuntime( 1568): java.lang.IllegalAccessError: tried to access field com
.google.android.volley.elegant.ElegantThreadSafeConnManager$ElegantPool.poolLock
from class com.google.android.volley.elegant.ElegantThreadSafeConnManager$Elega
ntPool
E/AndroidRuntime( 1568): at com.google.android.volley.elegant.ElegantThre
adSafeConnManager$ElegantPool.getEntryBlocking(ElegantThreadSafeConnManager.java
:140)
E/AndroidRuntime( 1568): at com.google.android.volley.elegant.ElegantThre
adSafeConnManager$ElegantPool$1.getPoolEntry(ElegantThreadSafeConnManager.java:1
22)
E/AndroidRuntime( 1568): at com.google.android.volley.elegant.ElegantThre
adSafeConnManager$1.getConnection(ElegantThreadSafeConnManager.java:64)
E/AndroidRuntime( 1568): at org.apache.http.impl.client.DefaultRequestDir
ector.execute(DefaultRequestDirector.java:456)
E/AndroidRuntime( 1568): at org.apache.http.impl.client.AbstractHttpClien
t.execute(AbstractHttpClient.java:898)
E/AndroidRuntime( 1568): at org.apache.http.impl.client.cache.CachingHttp
Client.callBackend(CachingHttpClient.java:670)
E/AndroidRuntime( 1568): at org.apache.http.impl.client.cache.CachingHttp
Client.handleCacheMiss(CachingHttpClient.java:451)
E/AndroidRuntime( 1568): at org.apache.http.impl.client.cache.CachingHttp
Client.execute(CachingHttpClient.java:377)
E/AndroidRuntime( 1568): at org.apache.http.impl.client.AbstractHttpClien
t.execute(AbstractHttpClient.java:797)
E/AndroidRuntime( 1568): at com.google.android.volley.AndroidHttpClient.e
xecute(AndroidHttpClient.java:308)
E/AndroidRuntime( 1568): at com.google.android.volley.GoogleHttpClient.ex
ecuteWithoutRewriting(GoogleHttpClient.java:217)
E/AndroidRuntime( 1568): at com.google.android.volley.GoogleHttpClient.ex
ecute(GoogleHttpClient.java:259)
E/AndroidRuntime( 1568): at com.google.android.volley.GoogleHttpClient.ex
ecute(GoogleHttpClient.java:316)
E/AndroidRuntime( 1568): at com.android.volley.toolbox.HttpClientStack.pe
rformRequest(HttpClientStack.java:83)
E/AndroidRuntime( 1568): at com.android.volley.toolbox.BasicNetwork.perfo
rmRequest(BasicNetwork.java:93)
E/AndroidRuntime( 1568): at com.android.volley.NetworkDispatcher.run(Netw
orkDispatcher.java:98)
W/ActivityManager( 309): Force finishing activity com.android.vending/.AssetB
rowserActivity
V/DropBoxReceiver( 552): Starting service for tag: system_app_crash, time: 1369
518820421
D/CrashReportService( 552): Writing crash report to: /data/data/tv.ouya/cache/.
reports/1369518820421
I/ActivityManager( 309): Displayed com.android.vending/.AssetBrowserActivity: +
517ms
I/ActivityManager( 309): No longer want com.google.android.gsf.login (pid 1600)
: hidden #2
D/dalvikvm( 110): WAIT_FOR_CONCURRENT_GC blocked 0ms
I/ActivityManager( 309): Start proc com.google.android.gsf.login for service co
m.google.android.gsf.login/com.google.android.gsf.loginservice.GoogleLoginServic
e: pid=1618 uid=10044 gids={3003, 1007, 2001, 3006, 1028}
D/dalvikvm( 110): GC_EXPLICIT freed 39K, 7% free 10748K/11459K, paused 2ms+2ms,
total 27ms
D/dalvikvm( 110): WAIT_FOR_CONCURRENT_GC blocked 0ms
D/dalvikvm( 110): GC_EXPLICIT freed <1K, 7% free 10748K/11459K, paused 2ms+3ms,
total 25ms
D/dalvikvm( 110): WAIT_FOR_CONCURRENT_GC blocked 0ms
D/dalvikvm( 110): GC_EXPLICIT freed <1K, 7% free 10748K/11459K, paused 1ms+3ms,
total 22ms
I/ActivityManager( 309): No longer want com.android.vending (pid 1568): hidden
#2
W/ActivityManager( 309): Scheduling restart of crashed service com.android.vend
ing/com.google.android.finsky.services.DailyHygiene in 5000ms
W/InputMethodManagerService( 309): Got RemoteException sending setActive(false)
notification to pid 1568 uid 10061
Click to expand...
Click to collapse
sonofskywalker3 said:
as soon as i log in I start getting "com.google.process.gapps" and play store crash messages
Click to expand...
Click to collapse
I'm getting the play crash every 10-15 minutes or so now too since clearing the cache, so I bet the update script cleared it for you...
Doing a little research on what play requires I was reading the below link that says phonesky.apk is the new vending.apk, and that like we thought for the store to just open all you need in the /system/app is the framework, loginservice and phonesky apks. It doesnt say anything about permissions so I re pushed each of them with default perms, cleared cache in recovery ...And!... same thing.
http://blog.apkudo.com/2012/08/08/run-google-play-on-an-emulator-and-pretend-to-be-any-device/
next I'm going to look at this from the logcat... looks like this fall apart after that...
E/ ( 1568): file /data/data/com.nvidia.NvCPLSvc/files/driverlist.txt: not found!
looking at:
Lorg/apache/http/impl/conn/tsccm/ConnPoolByRoute;.poolLock
I wonder if this apache client is stopping it? Maybe running something for the ouya store on the same connections as play store uses? I will try and go through the app manager and try to force stop/disable the other ouya store apps and see if there are any changes to the logcat.
Also tried to push the vending-4.1.6 apk... (might have needed to push an updated frame work too)
Clearing cache and data from the app manager and rebooting on every test...
edit:
After killing all of the ouya stuff, it looks like it is getting farther into the launch as now there is some stuff about syncing with my gmail account info in it.
edit:
using titanium backup to freeze the ouya framework and apps to make sure they do not get in the way...
Well I started from scratch again just so I know I'm at a clean start. flashed the OTA zip. I've been working with the old vending logcats, as its a little easier to follow whats "not" working with it...
I'm starting to think I will have to build a port of CM to get play to work, I think the ouya framework is using some resources that normally the play store uses so when play launches it gets access denied when trying to use those parts. I think I will try to remove as much ouya branded files as I can and see what the logcat looks like.
edit:
just thinking, has anyone tried to backup and restore the ouya stuff on another device yet? wonder if it would result in breaking the play store there... nice proof of concept....
professorpoptart said:
Well I started from scratch again just so I know I'm at a clean start. flashed the OTA zip. I've been working with the old vending logcats, as its a little easier to follow whats "not" working with it...
I'm starting to think I will have to build a port of CM to get play to work, I think the ouya framework is using some resources that normally the play store uses so when play launches it gets access denied when trying to use those parts. I think I will try to remove as much ouya branded files as I can and see what the logcat looks like.
edit:
just thinking, has anyone tried to backup and restore the ouya stuff on another device yet? wonder if it would result in breaking the play store there... nice proof of concept....
Click to expand...
Click to collapse
I'm not going to be much help here, like, at all. I do have a OUYA tho, I can follow instructions, have a lot of free time, and have CWM/busybox/wireless ADB/superuser on it already. So if theres anything I can do to help, let me know.
I also got my ouya just today.
I'm having some trouble getting adb to work but Iam also ready to test things.
GizmoTheGreen said:
I also got my ouya just today.
I'm having some trouble getting adb to work but Iam also ready to test things.
Click to expand...
Click to collapse
Sweet, I am in the process of porting a rom from another tegra 3 device so I will have a base aosp to work with. Play market will probably just work then... and the new task may then be how to load the OUYA stuff onto the new rom. I'm having issues getting video output on CWM to test the new rom though.
Do you CWM up and running?
Well I may be able to play with it some tonight. If you've got something you want me to try flashing PM me a link and I'll give it a shot and see what happens.
sonofskywalker3 said:
Well I may be able to play with it some tonight. If you've got something you want me to try flashing PM me a link and I'll give it a shot and see what happens.
Click to expand...
Click to collapse
K, I'm hoping its not too bad as we don't care about camera,gps,radio,screen,ect... we just need it to boot and get wifi which we should be able to pull out of the current /system/etc/permissions/android.hardware.wifi.xml. I will start a new thread to document the rom though I just want to get the CWM recovery working first so I dont have to flash OTA every time it breaks... even if I have to fastboot recovery.img every time thats fine...
I managed to get adb to work, added superuser and sideloaded xbmc, works wonderfully even without logging in to ouya account.
I have not installed cwm just yet, will tomorrow.
GizmoTheGreen said:
I managed to get adb to work, added superuser and sideloaded xbmc, works wonderfully even without logging in to ouya account.
I have not installed cwm just yet, will tomorrow.
Click to expand...
Click to collapse
Be sure to install the hw accelerated xbmc beta, handles 1080p perfectly
Sent from my GT-P1000 using Tapatalk HD
Paulenski said:
Be sure to install the hw accelerated xbmc beta, handles 1080p perfectly
Sent from my GT-P1000 using Tapatalk HD
Click to expand...
Click to collapse
yep, I did, works well, tried 60fps 720p amv
Version for no-BN account devices in post #5
This version of the app is for fully registered devices.
5-14-22: Updated to v1.5. Uninstall any previous version to insure all variables clear.
--removed Google accounts section
--removed Network Location setting (relied on Google accounts).
Over the years a few new "Settings" apps have been cobbled together from the ruins of what B&N left on the device. Starting with the original listing by @Renate NST which revealed the scope of what was hidden on the NST/G, people have rejiggered the app in a number of ways. Each of those attempts relied on actually changing the app or the framework and had limitations as to the type of installation they would run on and things that needed to be added, deleted, disabled, etc.
The Nook Settings app is my effort to create a utility that would encompass all the good ideas and none of the less good. But as I am no Java programmer, that meant Tasker (surprise). The result is a frankenapp, using screens from the B&N Settings app (you can't delete it!) as well as completely original pages I assembled from screen images and many, many invisible overlays to hijack the Back button and the return arrow throughout the app. My goal was to eliminate anything that did not work (USB debugging in the Development section, for example), try to fix what I could (USB debugging, for example!), and add in features that just should be there, mundane things like wallpaper and keyboard changes. I also wanted to re-organize the app in a more traditional way. A few representative screenshots below.
Disclaimers
1. Transitions are sometimes a little scrappy. It all depends on what the device is doing in the background and how difficult the item is to access.
2. Rather than introduce a lot of forking with many permutations, I elected to only separate the NST from the NSTG at first run. As far as accounts go, I included everything from B&N: Shop, Social). There is error trapping, so there should be no issues.
3. My number one goal in herding all these electric sheep was to keep what happens in the Settings app within the Settings app. This proved to be impossible in a few cases (keyboard swap is one) because of the way the native Android system was handling the main window. Those cases are clearly indicated in the app menus as "Exits Settings".
4. This app cannot be totally localized. That is, if you have a different display language (say, German), the parts of the app that are actually parts of the B&N Settings app will be localized, i.e., the phrases will be changed to the language you have selected. However, the custom pages I created are just images with invisible touch overlays so.... If anyone is seriously interested in localizing the app for themselves, they should contact me and we can discuss creating a custom set of images which I will then compile into a custom app.
5. I'm sorry to say that the App Manager was one of most difficult nuts to crack. It is part of the B&N Settings app but has an activity that cannot be opened via shell commands. Somehow ADW Launcher does it, but I was never able to come up with a method. Luckily, Tasker has a generic call to the App Manager and it actually works. Still, it is sluggish on the Back arrow where it must be tested against which screen is being displayed. Just not a happy camper. Be sure not to tap the Back arrow more than once or you'll end up who knows where. Consider it a free lesson in patience
6. This app is only for Portrait orientation. Oh, you can rotate your screen, but all the touch coordinates will be off and images distorted. This is not a priority for me, but I may look at it someday. It requires a redesign and right now, I'm sorta sick of working on this :silly:
Requirements
1. This is a Tasker app and has a dependency on two library files which are part of a GApps installation. If you don't have GApps or one of my other Tasker apps already, you need to copy the two files in the zip as below:
/system/etc/permissions/com.google.android.maps.xml
/system/framework/com.google.android.maps.jar
Set permissions for both files to rw-r--r-- and reboot. Without these files resident, the app will not install.
2. Root/SU. Right off the bat. Many, many shell commands, settings.db, accounts.db, etc. manipulations.
3. Sqlite3 (for the database manipulations), provided in the zip below. If you don't already have it, move the file to /system/bin and set the permissions to rwx r-x r-x.
4. Busybox. If you rooted with NookManager, you already have Busybox installed. A few other special packages probably include it. If you have it, you will find it in /system/xbin. If it's not there, copy the file from the zip to that location and set permissions to rwx-rwx-rwx
5. The original B&N Settings app installed
Edit: 6. I've discovered while working on a no-B&N variant that a kernal enabling multi-touch is needed for some of the "sendevent" sequences to execute. Lacking multi-touch does not mean the app will not function or that you will not be able to access some settings.
Installation
The easy part. This is not a system app, but a user app. Just install as normal. You don't have to disable or remove or change anything. If you don't like it, just uninstall.
On first run the app:
1. determines if you have an NSTG and adjusts the menus accordingly.
2. sets ADB debugging via TCP (for WiFi apps like ADB Konnect); This is the default state for rooting with NookManager. You can change to USB in Developer options.
Just to be clear, in every case in which there is a "return" arrow as part of a Settings screen, its function is identical to the Back button in the status bar (i.e., both have been hijacked).
Problems
If you have some issue and end up crashing the app or exiting unexpectedly (has not happened to me, but.....), there may still be invisible overlays present that will impair the function of your device. The easiest way to deal with these is to repeatedly press the Back button until the main Settings menu appears and then disappears. If there is still an issue, force stopping the app via the App Manager will clear all overlays. A power cycle is the last resort.
Acknowledgement
Wow, this was tough... I'm indebted to the generous folk who hang out at the Google Tasker group. I'm sure they all think I'm daft spending so much time on an Eclair device with an ancient version of Tasker, but they have nonetheless been helpful when I've been stuck.
Wow, @nmyshkin that looks like a bit of work.
On a different theme, I have an Android (Linux) executable for doing settings.
It's handy if you want to set a bunch of devices all the same (and you have root).
Settings are stored in different tables for global, system and secure.
Even worse, individual setting moved among these three categories for different versions of Android.
Even worse, they used to be stored in an SQLite database, then they moved to separate XML files.
Fortunately, if there is a setting "klaatu_barada_nikto" it is unique even though it might be in system or secure depending on Android version.
The executable takes an input file of settings.
Here is an example (just what I had at hand, I'm not saying that these settings are the right one for you (or even me)).
Code:
adb_enabled 1
airplane_mode_on 0
auto_time_zone 0
bluetooth_on 0
development_settings_enabled 1
dim_screen 0
heads_up_notification_enabled 0
immersive_mode_confirmations confirmed
install_non_market_apps 0
lockscreen.disabled 1
mock_location 1
package_verifier_enable 0
screen_auto_brightness_adj -1
screen_brightness 5
screen_brightness_mode 0
screen_off_timeout 1800000
skip_first_use_hints 1
stay_on_while_plugged_in 3
transition_animation_scale 1.0
usb_mass_storage_enabled 0
user_setup_complete 1
verifier_verify_adb_installs 0
window_animation_scale 1.0
wifi_frequency_band 0
If the setting exists, it will be set.
Notice, that you don't have to specify category (global, system, secure) since it can figure that out itself.
(No, I didn't attach the executable. I have to double check it.)
Renate NST said:
Wow, @nmyshkin that looks like a bit of work.
Click to expand...
Click to collapse
Yeah, this is another example of why humans are not allowed to know the future. If they did, they would shy away from attempting many things!
I'd be interested in the executable. From my work on this app I can imagine what it must involve to ferret out the appropriate entries. On the NST, at least, values in settings.db for some things appear to be artifacts only and don't actually seem to have any effect. It just made things more interesting...
nmyshkin said:
I'd be interested in the executable.
Click to expand...
Click to collapse
Well, here it is (in the signature).
Park "setvalues" in an executable directory (like /data or /data/local/tmp), chmod 755 it.
It takes the name of the values file as the only argument.
It's verbose in telling you what was and any changes done.
This also should run on any version of Android and any device.
Custom version for those without B&N account and/or apps
5-11-22: updated to 1.5. Uninstall any previous version to insure all variables clear.
--removed Google Accounts section
--removed Network Location setting (relied on Google Accounts)
This version is only for devices which either bypassed OOBE and then removed all B&N stuff or went through registration and then removed all B&N stuff
I've been playing around with a third (my last one, I swear) device and have finally hit upon the method for removing B&N apps without causing a constant drumbeat of protest in the system. More on that in a future post.
No B&N apps means no B&N account, whether you start with a registered device or skip OOBE, so my Nook Settings app had a lot of fluff in it for such devices. Also, the "About" stuff did not work so there was no information such as serial number, MAC address, etc.
This special version of the app addresses these issues. References to B&N stuff are removed and there is a custom "About" section which includes an editing option for those items the app could not dig up on its own (like your name, if you didn't register). See screenshot below.
Hint: if you skip OOBE, you will need to jot down the serial number, model number, and MAC address for entry into the "About" page. You can find these values on the screen where you elect to skip OOBE. Failing that, they are contained in text files in /rom/devconf
The zip below includes all the stuff from the zip in the OP with an updated custom app. Follow the installation instructions in post #1. If you are updating, you only need to uninstall the previous version and install the new one.
Great job!
The app dosen't install on my rooted NST fw ver.1.2.1 but at least I removed all unnecessary B&N apps. Thanks
kodovoimeji said:
Great job!
The app dosen't install on my rooted NST fw ver.1.2.1 but at least I removed all unnecessary B&N apps. Thanks
Click to expand...
Click to collapse
It should install and run on 1.2.1 without any problems. Did you remember to copy the two maps files? It won't install without those present. Also be sure the permissions for each file are set correctly. If not the installer may register them as MIA and refuse to run.
I'm not sure if the same level of dependency is present at installation for sqlite or busybox, but you do need both (with correct permissions) for some parts of the app to function.
Edit: I can confirm that the app installs and runs with FW 1.2.1, following the directions in the first post.
Hey, I find myself unable to put the com.google.android.maps.jar and com.google.android.maps.xml files in the required locations via ADB push due to the filesystem being readonly, and I'm not sure the safest way to remount readwrite on this device, please could you advise?
alexhorner said:
Hey, I find myself unable to put the com.google.android.maps.jar and com.google.android.maps.xml files in the required locations via ADB push due to the filesystem being readonly, and I'm not sure the safest way to remount readwrite on this device, please could you advise?
Click to expand...
Click to collapse
Did you choose one of the NookManager options with ES File Explorer? If so, you can mount /system as RW from within its Settings and just transfer the files to either your sdcard or /media (the "Nook" drive) and then move them with the file manager from there. You can even set the permissions (long-press on file and select "Properties").
Otherwise...hmm....let me see if I have that bookmarked...
Code:
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
I think that's it. Then for permissions:
Code:
adb shell chmod 644 /system/wherever/whatever.xml
(I'm not suggesting it's 644--you'll have to check that.
ES File Explorer is by far the easier method.
nmyshkin said:
Did you choose one of the NookManager options with ES File Explorer? If so, you can mount /system as RW from within its Settings and just transfer the files to either your sdcard or /media (the "Nook" drive) and then move them with the file manager from there. You can even set the permissions (long-press on file and select "Properties").
Otherwise...hmm....let me see if I have that bookmarked...
Code:
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
I think that's it. The for permissions:
Code:
adb shell chmod 644 /system/wherever/whatever.xml
(I'm not suggesting it's 644--you'll have to check that.
ES File Explorer is by far the easier method.
Click to expand...
Click to collapse
I went for the classic so no ES here! Just ReLaunchX. The mount command worked, and I can confirm 644 is the correct numeric for the required permissions. Busybox already existed from the root, and I installed sqlite3 with correct permissions, 755.
Copied those 2 google files over, set permissions, rebooted then installed the APK fine.
Sorry for being such a noob here, but how do I now run the app as superuser? Running it without just refreshes the screen (I assume that means it crashed after trying to open?)
Opening the Superuser app shows no apps in list.
alexhorner said:
I went for the classic so no ES here! Just ReLaunchX. The mount command worked, and I can confirm 644 is the correct numeric for the required permissions. Busybox already existed from the root, and I installed sqlite3 with correct permissions, 755.
Copied those 2 google files over, set permissions, rebooted then installed the APK fine.
Sorry for being such a noob here, but how do I now run the app as superuser? Running it without just refreshes the screen (I assume that means it crashed after trying to open?)
Opening the Superuser app shows no apps in list.
Click to expand...
Click to collapse
Sometimes SU is slow to respond. I'd reboot and try again.
No luck waiting or rebooting unfortunately. Superuser has no app list and the screen refresh flashes when trying to launch still
alexhorner said:
No luck waiting or rebooting unfortunately. Superuser has no app list and the screen refresh flashes when trying to launch still
Click to expand...
Click to collapse
Grr...
Ok, I've shut down my PC for the day. Let me try a clean install of the app tomorrow and refresh my memory on exactly what happens. SU can really be a pain on this device sometimes.
alexhorner said:
No luck waiting or rebooting unfortunately. Superuser has no app list and the screen refresh flashes when trying to launch still
Click to expand...
Click to collapse
So instead of reading till I get drowsy I have downloaded the zip right on the device! I uninstalled the app and checked Superuser to be sure any entries were gone. Then I extracted the app from the zip and installed it. The moment (or nearly) I tapped the app icon I got the Superuser permission request.
I'm baffled.
nmyshkin said:
So instead of reading till I get drowsy I have downloaded the zip right on the device! I uninstalled the app and checked Superuser to be sure any entries were gone. Then I extracted the app from the zip and installed it. The moment (or nearly) I tapped the app icon I got the Superuser permission request.
I'm baffled.
Click to expand...
Click to collapse
Well...
I opened ADB connect, as I knew that asked for super user too. It did, I accepted and it launched fine. I went back to ReLaunchX and decided to look at Superuser now. It won't open at all.
Okay, fine, I'll reboot the device.
Nope, still won't open.
So I decided to open ADB Connect again. Well now that's broken too! It gives me a black screen, so I decided to tap back. Nope. Okay, I'm stuck now.
After a few seconds I get "Sorry! Activity ReLaunchX (in application ReLaunchX) is not responding. [Wait] [Force Close]
I have since forced closed, uninstalled the settings app and rebooted. Superuser still broken. ADB works once and then subsequent times black screens me.
Edit: Got a logcat of superuser:
Spoiler: Logcat Superuser
Code:
D/AndroidRuntime( 1529): Shutting down VM
W/dalvikvm( 1529): threadid=3: thread exiting with uncaught exception (group=0x4001b210)
E/AndroidRuntime( 1529): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime( 1529): java.lang.NullPointerException
E/AndroidRuntime( 1529): at com.noshufou.android.su.PinnedHeaderListView.configureHeaderView(PinnedHeaderListView.java:153)
E/AndroidRuntime( 1529): at com.noshufou.android.su.AppListActivity$AppListAdapter.onScroll(AppListActivity.java:326)
E/AndroidRuntime( 1529): at android.widget.AbsListView.invokeOnItemScrollListener(AbsListView.java:741)
E/AndroidRuntime( 1529): at android.widget.AbsListView.handleDataChanged(AbsListView.java:3181)
E/AndroidRuntime( 1529): at android.widget.ListView.layoutChildren(ListView.java:1488)
E/AndroidRuntime( 1529): at android.widget.AbsListView.onLayout(AbsListView.java:1314)
E/AndroidRuntime( 1529): at com.noshufou.android.su.PinnedHeaderListView.onLayout(PinnedHeaderListView.java:123)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1119)
E/AndroidRuntime( 1529): at android.widget.LinearLayout.layoutVertical(LinearLayout.java:998)
E/AndroidRuntime( 1529): at android.widget.LinearLayout.onLayout(LinearLayout.java:918)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1119)
E/AndroidRuntime( 1529): at android.widget.LinearLayout.layoutVertical(LinearLayout.java:998)
E/AndroidRuntime( 1529): at android.widget.LinearLayout.onLayout(LinearLayout.java:918)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1529): at android.view.View.layout(View.java:6863)
E/AndroidRuntime( 1529): at android.view.ViewRoot.performTraversals(ViewRoot.java:996)
E/AndroidRuntime( 1529): at android.view.ViewRoot.handleMessage(ViewRoot.java:1633)
E/AndroidRuntime( 1529): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1529): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 1529): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/AndroidRuntime( 1529): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1529): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 1529): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 1529): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime( 1529): at dalvik.system.NativeStart.main(Native Method)
I/ActivityManager( 790): Removing old ANR trace file from /data/anr/traces.txt
W/ActivityManager( 790): Send CRASH intent: true
I/Process ( 790): Sending signal. PID: 1529 SIG: 3
D/EPD#ActivityManager( 790): resetRegion 4
D/NATIVE-EPD( 790): epd_reset_region: 0x10
D/EPD#ActivityManager( 790): resetRegion 5
D/NATIVE-EPD( 790): epd_reset_region: 0x20
D/EPD#ActivityManager( 790): resetRegion 6
D/NATIVE-EPD( 790): epd_reset_region: 0x40
D/EPD#ActivityManager( 790): resetRegion 7
D/NATIVE-EPD( 790): epd_reset_region: 0x80
D/DeviceManagerBroadcastReceiver( 949): action (com.bn.devicemanager.ACTION_HANDLE_CRASH)
I/dalvikvm( 1529): threadid=7: reacting to signal 3
I/dalvikvm( 1529): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 1529): Sending signal. PID: 1529 SIG: 9
I/ActivityManager( 790): Process com.noshufou.android.su (pid 1529) has died.
I/WindowManager( 790): WIN DEATH: Window{4a0ebc98 com.noshufou.android.su/com.noshufou.android.su.Su paused=false}
I/UsageStats( 790): Unexpected resume of com.gacode.relaunchx while already resumed in com.noshufou.android.su
W/InputManagerService( 790): Window already focused, ignoring focus gain of: [email protected]
V/Activity( 1225): performResume()
Most disturbing, as Jeeves would say.
Here's where my lack of depth shows. I can see there is trouble in the logcat. The word "CRASH" being a clue. But as to the rest..not so much.
I would, at this point, uninstall and reinstall SU--you can get the apk from your NookManager card.
I've got a fairly busy day but my aim is to back up one of my devices, revert it to an unrooted, registered state, root with the "classic" package and try to reproduce your situation. That's one step short of converting to UK and going through the entire process. Which I hope not to do.
nmyshkin said:
Most disturbing, as Jeeves would say.
Here's where my lack of depth shows. I can see there is trouble in the logcat. The word "CRASH" being a clue. But as to the rest..not so much.
I would, at this point, uninstall and reinstall SU--you can get the apk from your NookManager card.
I've got a fairly busy day but my aim is to back up one of my devices, revert it to an unrooted, registered state, root with the "classic" package and try to reproduce your situation. That's one step short of converting to UK and going through the entire process. Which I hope not to do.
Click to expand...
Click to collapse
The reinstall has certainly fixed Superuser, however, no luck with NookSettings still even after another reinstall. I feel reverting to UK on your device wouldn't particularly help you, however going from stock to rooted might. I am wondering at this point if that might do me any good.
It clearly shows a lack of resilience of Superuser although the instigation lies elsewhere.
There is absolutely no reason that an app should bomb doing a layout.
Personally, I've never liked su. All I need in life (before the advent of system as root) is a rooted adbd.
alexhorner said:
The reinstall has certainly fixed Superuser, however, no luck with NookSettings still even after another reinstall. I feel reverting to UK on your device wouldn't particularly help you, however going from stock to rooted might. I am wondering at this point if that might do me any good.
Click to expand...
Click to collapse
I have just found a new APK for Superuser, 3.0.7 which I have attached in both the unextracted ZIP form and the extracted APK form. Source is https://forum.xda-developers.com/t/app-superuser-2-3-6-1-now-on-the-market-2010-09-05.682828/page-49
Not sure it will be of much help, but it certainly works with ADB Konnect perfectly fine.
Still no luck with NookSettings. I decided to logcat that too, here it is:
Spoiler: NookSettings Logcat
Code:
I/ActivityManager( 790): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x14000000 cmp=com.home.nmyshkin.settings/net.dinglisch.android.tasker.Kid }
I/ActivityManager( 790): Start proc com.home.nmyshkin.settings for activity com.home.nmyshkin.settings/net.dinglisch.android.tasker.Kid: pid=3357 uid=10019 gids={}
E/TC ( 1023): KPICollector: 1634321461142 platform process_start {"processName":"com.home.nmyshkin.settings"}
I/dalvikvm( 3357): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=38)
E/TC ( 1023): KPICollector: 1634321461231 ActivityManager background {"component":"com.gacode.relaunchx/.AllApplications"}
E/TC ( 1023): KPICollector: 1634321461238 ActivityManager foreground {"component":"com.home.nmyshkin.settings/net.dinglisch.android.tasker.Kid"}
I/dalvikvm( 3357): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=56)
D/dalvikvm( 3357): GC freed 10007 objects / 357744 bytes in 64ms
D/dalvikvm( 3357): GC freed 10130 objects / 380968 bytes in 61ms
D/dalvikvm( 3357): GC freed 11236 objects / 402944 bytes in 41ms
D/dalvikvm( 3357): GC freed 7376 objects / 183336 bytes in 57ms
I/global ( 3357): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
D/dalvikvm( 3357): GC freed 10826 objects / 521112 bytes in 53ms
D/LocationManager( 3357): Constructor: service = [email protected]
D/dalvikvm( 3357): GC freed 1646 objects / 200792 bytes in 44ms
D/dalvikvm( 3357): GC freed 116 objects / 120272 bytes in 44ms
I/global ( 3357): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
E/dalvikvm( 3357): Could not find class 'com.google.android.maps.GeoPoint', referenced from method net.dinglisch.android.tasker.hf.a
W/dalvikvm( 3357): VFY: unable to resolve new-instance 279 (Lcom/google/android/maps/GeoPoint;) in Lnet/dinglisch/android/tasker/hf;
D/dalvikvm( 3357): VFY: replacing opcode 0x22 at 0x0005
D/dalvikvm( 3357): Making a copy of Lnet/dinglisch/android/tasker/hf;.a code (52 bytes)
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lcom/google/android/maps/GeoPoint;)
I/dalvikvm( 3357): Could not find method com.google.android.maps.GeoPoint.getLatitudeE6, referenced from method net.dinglisch.android.tasker.hf.a
W/dalvikvm( 3357): VFY: unable to resolve virtual method 1180: Lcom/google/android/maps/GeoPoint;.getLatitudeE6 ()I
D/dalvikvm( 3357): VFY: replacing opcode 0x6e at 0x000a
D/dalvikvm( 3357): Making a copy of Lnet/dinglisch/android/tasker/hf;.a code (116 bytes)
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lcom/google/android/maps/GeoPoint;)
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lcom/google/android/maps/GeoPoint;)
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lcom/google/android/maps/GeoPoint;)
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lcom/google/android/maps/GeoPoint;)
I/dalvikvm( 3357): Could not find method com.google.android.maps.GeoPoint.getLatitudeE6, referenced from method net.dinglisch.android.tasker.hf.b
W/dalvikvm( 3357): VFY: unable to resolve virtual method 1180: Lcom/google/android/maps/GeoPoint;.getLatitudeE6 ()I
D/dalvikvm( 3357): VFY: replacing opcode 0x6e at 0x0009
D/dalvikvm( 3357): Making a copy of Lnet/dinglisch/android/tasker/hf;.b code (72 bytes)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/ht; (280)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/ht;' failed
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/ht; (280)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/ht;' failed
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lcom/google/android/maps/GeoPoint;)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
E/dalvikvm( 3357): Could not find class 'net.dinglisch.android.tasker.MyMapView', referenced from method net.dinglisch.android.tasker.ql.a
W/dalvikvm( 3357): VFY: unable to resolve check-cast 472 (Lnet/dinglisch/android/tasker/MyMapView;) in Lnet/dinglisch/android/tasker/ql;
D/dalvikvm( 3357): VFY: replacing opcode 0x1f at 0x000b
D/dalvikvm( 3357): Making a copy of Lnet/dinglisch/android/tasker/ql;.a code (264 bytes)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lnet/dinglisch/android/tasker/MyMapView;)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
I/dalvikvm( 3357): Could not find method net.dinglisch.android.tasker.MyMapView.getContext, referenced from method net.dinglisch.android.tasker.ql.a
W/dalvikvm( 3357): VFY: unable to resolve virtual method 3189: Lnet/dinglisch/android/tasker/MyMapView;.getContext ()Landroid/content/Context;
D/dalvikvm( 3357): VFY: replacing opcode 0x6e at 0x0001
D/dalvikvm( 3357): Making a copy of Lnet/dinglisch/android/tasker/ql;.a code (117 bytes)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lnet/dinglisch/android/tasker/MyMapView;)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): VFY: unable to find class referenced in signature (Lnet/dinglisch/android/tasker/MyMapView;)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
E/dalvikvm( 3357): Could not find class 'net.dinglisch.android.tasker.MyMapView', referenced from method net.dinglisch.android.tasker.ql.a
W/dalvikvm( 3357): VFY: unable to resolve new-instance 472 (Lnet/dinglisch/android/tasker/MyMapView;) in Lnet/dinglisch/android/tasker/ql;
D/dalvikvm( 3357): VFY: replacing opcode 0x22 at 0x0013
D/dalvikvm( 3357): Making a copy of Lnet/dinglisch/android/tasker/ql;.a code (96 bytes)
W/dalvikvm( 3357): Unable to resolve superclass of Lnet/dinglisch/android/tasker/MyMapView; (284)
W/dalvikvm( 3357): Link of class 'Lnet/dinglisch/android/tasker/MyMapView;' failed
W/dalvikvm( 3357): VFY: returning Ljava/lang/Object; (cl=0x0), declared Landroid/view/View; (cl=0x0)
W/dalvikvm( 3357): VFY: rejecting opcode 0x11 at 0x001c
W/dalvikvm( 3357): VFY: rejected Lnet/dinglisch/android/tasker/ql;.a (Landroid/content/Context;I)Landroid/view/View;
W/dalvikvm( 3357): Verifier rejected class Lnet/dinglisch/android/tasker/ql;
W/dalvikvm( 3357): Exception Ljava/lang/VerifyError; thrown during Lnet/dinglisch/android/tasker/md;.<clinit>
D/AndroidRuntime( 3357): Shutting down VM
W/dalvikvm( 3357): threadid=3: thread exiting with uncaught exception (group=0x4001b210)
E/Settings( 3357): 13.11.02#MyUEH: error: exception in thread main: java.lang.ExceptionInInitializerError
E/Settings( 3357): 13.11.02#: error: Caused by:
E/Settings( 3357): 13.11.02#: error: net.dinglisch.android.tasker.md.<clinit>(Unknown Source)
E/Settings( 3357): 13.11.02#: error: net.dinglisch.android.tasker.vh.b(Unknown Source)
E/Settings( 3357): 13.11.02#: error: net.dinglisch.android.tasker.vh.a(Unknown Source)
E/Settings( 3357): 13.11.02#: error: net.dinglisch.android.tasker.vh.d(Unknown Source)
E/Settings( 3357): 13.11.02#: error: net.dinglisch.android.tasker.Kid.onCreate(Unknown Source)
E/Settings( 3357): 13.11.02#: error: android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime( 3357): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime( 3357): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 3357): at net.dinglisch.android.tasker.vh.b(Unknown Source)
E/AndroidRuntime( 3357): at net.dinglisch.android.tasker.vh.a(Unknown Source)
E/AndroidRuntime( 3357): at net.dinglisch.android.tasker.vh.d(Unknown Source)
E/AndroidRuntime( 3357): at net.dinglisch.android.tasker.Kid.onCreate(Unknown Source)
E/AndroidRuntime( 3357): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime( 3357): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2459)
E/AndroidRuntime( 3357): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2512)
E/AndroidRuntime( 3357): at android.app.ActivityThread.access$2200(ActivityThread.java:119)
E/AndroidRuntime( 3357): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1863)
E/AndroidRuntime( 3357): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3357): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 3357): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/AndroidRuntime( 3357): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3357): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 3357): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 3357): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime( 3357): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 3357): Caused by: java.lang.VerifyError: net.dinglisch.android.tasker.ql
E/AndroidRuntime( 3357): at net.dinglisch.android.tasker.md.<clinit>(Unknown Source)
E/AndroidRuntime( 3357): ... 17 more
I/ActivityManager( 790): Removing old ANR trace file from /data/anr/traces.txt
W/ActivityManager( 790): Send CRASH intent: true
I/Process ( 790): Sending signal. PID: 3357 SIG: 3
D/EPD#ActivityManager( 790): resetRegion 4
D/NATIVE-EPD( 790): epd_reset_region: 0x10
D/EPD#ActivityManager( 790): resetRegion 5
D/NATIVE-EPD( 790): epd_reset_region: 0x20
D/EPD#ActivityManager( 790): resetRegion 6
D/NATIVE-EPD( 790): epd_reset_region: 0x40
D/EPD#ActivityManager( 790): resetRegion 7
D/NATIVE-EPD( 790): epd_reset_region: 0x80
D/DeviceManagerBroadcastReceiver( 949): action (com.bn.devicemanager.ACTION_HANDLE_CRASH)
I/dalvikvm( 3357): threadid=7: reacting to signal 3
I/dalvikvm( 3357): Wrote stack trace to '/data/anr/traces.txt'
I/Process ( 3357): Sending signal. PID: 3357 SIG: 9
I/ActivityManager( 790): Process com.home.nmyshkin.settings (pid 3357) has died.
V/Activity( 1225): performResume()
D/EPD#ActivityResume( 790): resetRegion 4
D/NATIVE-EPD( 790): epd_reset_region: 0x10
D/EPD#ActivityResume( 790): resetRegion 5
D/NATIVE-EPD( 790): epd_reset_region: 0x20
D/EPD#ActivityResume( 790): resetRegion 6
D/NATIVE-EPD( 790): epd_reset_region: 0x40
D/EPD#ActivityResume( 790): resetRegion 7
D/NATIVE-EPD( 790): epd_reset_region: 0x80
D/EPD#ActivityResume( 790): Disable EPD for 350ms!!!!!!!!
I/UsageStats( 790): Unexpected resume of com.gacode.relaunchx while already resumed in com.home.nmyshkin.settings
D/ReLaunchApp( 1225): --- onResume(AllApps)
W/InputManagerService( 790): Window already focused, ignoring focus gain of: [email protected]
I/DeviceManagerHandler( 949): HandleMessage(): msg.what (1)
I/global ( 949): Default buffer size used in BufferedWriter constructor. It would be better to be explicit if an 8k-char buffer is required.
D/dalvikvm( 949): GC freed 4915 objects / 501464 bytes in 41ms
I/LogcatProcessor( 949): LOG END MARKER - 1634321464060
alexhorner said:
I have just found a new APK for Superuser, 3.0.7 which I have attached in both the unextracted ZIP form and the extracted APK form. Source is https://forum.xda-developers.com/t/app-superuser-2-3-6-1-now-on-the-market-2010-09-05.682828/page-49
Click to expand...
Click to collapse
I have tried other SU apps in the past but they were always complaining about updating binaries (not going to happen). But if you have something that works, good.
That logcat seems to point to the two maps files that are expected by Tasker or any of its kid apps (like Nook Settings). So much stuff about maps, like it can't find what it wants. I've never seen anything like that on my devices (not that I sit around watching logcats scroll by all day). Check that both files are in the proper places. The jar file belongs in /system/framework and is rw-r-r (or 644, as you said). The xml file is in /system/etc/permissions and is also rw-r-r.
In short, if the old SU popped up with ADB Konnect, it's probably not the problem. The Nook Settings app itself is not the problem. I have it running on three devices and the fresh install last night went without a hitch. I've tested it on both FW 1.2.1 and 1.2.2.
Getting one of my Nooks ready for a backup now.