I have a RAZR i with the standard UK 4.1.2 ROM. Sometimes I've had low memory problems or periods where the battery runs down unexpectedly. I recently started experiencing severe memory shortage after running with data disabled and poked around a bit. What I discovered was a large number of app_process instances taking 8M each.
From what I can tell, I should not see these. Android runs this process but it loads Java code into itself and changes personality. So while there's plenty of app_process instances running, they don't show up as such when you do a ps.
I found this out the hard way running killall app_process :/
But I can use this to kill off any of these "zombie" app_process instances: ps | grep app_process | busybox awk '{print $2}' | xargs kill
Running with data disabled seems to make these happen fairly reliably. Made me suspect something was being spawned to look for something on the network but failed due to a lack of data and then... got stuck instead of exiting?
I've disabled a few things on this ROM before. I think ModemStats or similar was a problem once before (chewing up CPU).
Has anyone seen this?
Is there something I can capture that would help diagnose the cause (I've heard of a logcat? maybe ps output?).
a1291762 said:
...Is there something I can capture that would help diagnose the cause (I've heard of a logcat? maybe ps output?).
Click to expand...
Click to collapse
sure, setup ADB and plug your device with a micro-usb cable on pc. Now you can logcat and also grep your favorit process.
Did you try limiting your backgroundprocesses under Developer-Options > backgroundprocess-limit ?
I use all the time a limit of 4 processes and have no memory problems (fyi: it will fall back to standard-setting after reboot)
Use the app Greenify to hibernate the apps you dont use daily
Enviado desde mi XT890 mediante Tapatalk
So... Greenify and limiting background "apps" can't help here because app_process isn't an app, it's a system process.
And it seems logcat isn't very useful when run after-the-fact? Oh it seems you can't run it except as root from Android 4.1 onwards. I've now got catlog recording so maybe next time I'll get something useful - assuming my SD card doesn't fill up first.
And of course now that I'm trying to _look_ at the problem, it's happening less frequently >:|
Amm app process are services, with the greenify app kills the services.....
If you havent root, well, remove the task on recent app list, force detention of the apps manually, and so on
Enviado desde mi XT890 mediante Tapatalk
Please don't spread misinformation. app_process is a system process. It is not even visible at the Android layer. Every app starts as an app_process instance. Greenify cannot even see it, let alone control it.
The good news is I have a logcat. The bad news is it's a 37Mb file and both the system ui and logcat app died due to lack of memory. I have second logcat fr when I noticed but the end of the first one if probably more useful. Having trouble reading the file on my phone. Will investigate more when I get home tonight.
bug2go is evil???
So app_process is AndroidRuntime. I see various AndroidRuntime START messages. Looks like normal starting of apps. Until 16:24 on 03-22.
Code:
03-22 03:30:04.822 D/AndroidRuntime(29699): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 08:35:03.670 D/AndroidRuntime(31593): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 08:35:03.670 D/AndroidRuntime(31592): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 08:38:03.542 D/AndroidRuntime(31650): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 08:38:03.552 D/AndroidRuntime(31651): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 09:23:10.850 D/AndroidRuntime( 1024): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 09:23:10.850 D/AndroidRuntime( 1025): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 09:41:29.170 D/AndroidRuntime( 2245): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 15:27:38.730 D/AndroidRuntime( 4879): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 15:41:39.630 D/AndroidRuntime( 5729): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 15:41:39.630 D/AndroidRuntime( 5730): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:30.350 D/AndroidRuntime( 6042): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:35.710 D/AndroidRuntime( 6064): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:35.910 D/AndroidRuntime( 6074): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.050 D/AndroidRuntime( 6079): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.320 D/AndroidRuntime( 6098): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.340 D/AndroidRuntime( 6087): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.400 D/AndroidRuntime( 6102): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.620 D/AndroidRuntime( 6105): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.690 D/AndroidRuntime( 6111): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.860 D/AndroidRuntime( 6133): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:36.950 D/AndroidRuntime( 6136): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
...
03-22 16:24:48.350 D/AndroidRuntime( 6650): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:48.350 D/AndroidRuntime( 6654): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:48.530 D/AndroidRuntime( 6744): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
03-22 16:24:48.610 D/AndroidRuntime( 6670): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
Something is running com.android.am.Am over and over again.
Code:
2014-03-20-08-45-47.txt|417176| 03-22 16:24:38.060 D/AndroidRuntime( 6111): Calling main entry com.android.commands.am.Am
2014-03-20-08-45-47.txt|417215| 03-22 16:24:38.380 D/AndroidRuntime( 6133): Calling main entry com.android.commands.am.Am
2014-03-20-08-45-47.txt|417216| 03-22 16:24:38.410 D/AndroidRuntime( 6136): Calling main entry com.android.commands.am.Am
2014-03-20-08-45-47.txt|417225| 03-22 16:24:38.620 D/AndroidRuntime( 6140): Calling main entry com.android.commands.am.Am
Am seems to be an android tool to run shell commands. What's being run?
Code:
03-22 16:24:48.440 D/su ( 6756): su invoked.
03-22 16:24:48.440 D/su ( 6756): Allowing shell.
03-22 16:24:48.440 D/su ( 6756): 2000 /system/xbin/su executing 0 showmap using binary showmap : showmap 129
03-22 16:24:48.440 E/su ( 6756): exec failed with 2: No such file or directory
Hm... Running a binary that doesn't exist lots and lots of times? That can't be a coincidence. Looks like app_process doesn't properly clean up in this case.
But what is causing all this in the first place? I found this.
Code:
03-22 16:24:29.600 I/bug2go-bugreport( 6037): bugreport started
03-22 16:24:29.610 I/bug2go-bugreport( 6037): reportId=2014-03-22_16-24-29.000+1000
03-22 16:24:29.610 I/bug2go-bugreport( 6037): Available space in /storage/sdcard0/bug2go is 1227 MB
03-22 16:24:29.610 I/bug2go-bugreport( 6037): Required space is 50
03-22 16:24:29.610 I/bug2go-bugreport( 6037): Storing report to /storage/sdcard0/bug2go/[email protected]_16-24-29.000+1000
...
03-22 16:24:30.690 W/ActivityManager( 384): Unable to start service Intent { act=motorola.intent.action.BUG2GO.BUGREPORT.START typ=text/plain (has extras) }: not found
Now that's odd. The bug2go apk is something I had previously removed. But the 2 bug2go binaries in /system/bin were still there. I can't see what triggered this (unless it's that last line, some kind of period attempt to run the now-missing bug2go app). Scrolling up in the logs I see... nothing but wifi scanning. My phone was suspended at the time so nothing was happening.
I've removed the bug2go binaries from /system/bin. That seems to be the source of the problem so maybe that'll fix things?
I also got a log after I noticed my phone was bad. It shows the last showmap error.
Code:
03-22 16:25:33.300 D/su (8732): su invoked.
03-22 16:25:33.300 D/su (8732): Allowing shell.
03-22 16:25:33.300 D/su (8732): 2000 /system/xbin/su executing 0 showmap using binary showmap : showmap 28103
03-22 16:25:33.300 E/su (8732): exec failed with 2: No such file or directory
And then, bug2go either gives up or finishes.
Code:
03-22 16:26:16.850 I/dumpstate(6054): done
03-22 16:26:16.850 I/bug2go-bugreport(6037): Dropping from root user to log user
So that at least explains why the phone doesn't ground to a permanent halt and why I can kill off these processes and have the phone continue to work.
Aha! It's actually dumpstate that causes the bug. It's run by bug2go but also by 'adb bugreport'. It tries to run showmap on... each running process? But since I don't have that binary, it leaves behind all the app_process instances. I ran 'adb bugreport' just now and it caused my phone to reboot!
So removing the bug2go binaries should stop this from being a problem but I'm kind of stumped as to why I have 'dumpstate' but not 'showmap' on my phone...
Related
sup peeps
im just wondering whats the diffrence between Ext2 and Ext3 and also could 1 or the other cause a coma/hanging issue on a hero rom if you have or dont have the right "Ext" so let me kno thx people
if you have cyanogen's recovery image go into the recovery console and type
Code:
upgrade_fs
reboot
ext3 has journaling which is a good thing. just do it.
wow....you didnt answer my question and i alrdy have ext3 answering my question just might help me with my coma problem so ya
RanT476 said:
wow....you didnt answer my question and i alrdy have ext3 answering my question just might help me with my coma problem so ya
Click to expand...
Click to collapse
i answered half of it. the coma issue, afaik, is related to a kernal panic. the last time i knew of the coma issue being present was in the use of unionfs and AUFS for apps2sd, but that has since been replaced by bind mounts and symlinks.
afaik? and how can i look at my log to see if the kernal is panicing whats the command for adb so i can see what the hell is going on so i can post it or something
RanT476 said:
afaik? and how can i look at my log to see if the kernal is panicing whats the command for adb so i can see what the hell is going on so i can post it or something
Click to expand...
Click to collapse
AFAIK = As Far As I Know
to check your log, #logcat
D/AndroidRuntime( 1911):
D/AndroidRuntime( 1911): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1911): CheckJNI is OFF
W/dalvikvm( 1911): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1911): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1911): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1911): VM cleaning up
D/dalvikvm( 1911): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1911): JNI_CreateJavaVM failed
E/AndroidRuntime( 1911): JNI_CreateJavaVM failed
D/AndroidRuntime( 1912):
D/AndroidRuntime( 1912): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1912): CheckJNI is OFF
W/dalvikvm( 1912): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1912): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1912): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1912): VM cleaning up
D/dalvikvm( 1912): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1912): JNI_CreateJavaVM failed
E/AndroidRuntime( 1912): JNI_CreateJavaVM failed
D/AndroidRuntime( 1913):
D/AndroidRuntime( 1913): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1913): CheckJNI is OFF
W/dalvikvm( 1913): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1913): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1913): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1913): VM cleaning up
D/dalvikvm( 1913): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1913): JNI_CreateJavaVM failed
E/AndroidRuntime( 1913): JNI_CreateJavaVM failed
D/AndroidRuntime( 1914):
D/AndroidRuntime( 1914): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1914): CheckJNI is OFF
W/dalvikvm( 1914): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1914): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1914): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1914): VM cleaning up
D/dalvikvm( 1914): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1914): JNI_CreateJavaVM failed
E/AndroidRuntime( 1914): JNI_CreateJavaVM failed
D/AndroidRuntime( 1915):
D/AndroidRuntime( 1915): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1915): CheckJNI is OFF
W/dalvikvm( 1915): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1915): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1915): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1915): VM cleaning up
D/dalvikvm( 1915): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1915): JNI_CreateJavaVM failed
E/AndroidRuntime( 1915): JNI_CreateJavaVM failed
D/AndroidRuntime( 1916):
D/AndroidRuntime( 1916): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1916): CheckJNI is OFF
W/dalvikvm( 1916): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1916): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1916): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1916): VM cleaning up
D/dalvikvm( 1916): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1916): JNI_CreateJavaVM failed
E/AndroidRuntime( 1916): JNI_CreateJavaVM failed
D/AndroidRuntime( 1917):
D/AndroidRuntime( 1917): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1917): CheckJNI is OFF
W/dalvikvm( 1917): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1917): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1917): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1917): VM cleaning up
D/dalvikvm( 1917): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1917): JNI_CreateJavaVM failed
E/AndroidRuntime( 1917): JNI_CreateJavaVM failed
D/AndroidRuntime( 1918):
D/AndroidRuntime( 1918): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1918): CheckJNI is OFF
W/dalvikvm( 1918): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1918): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1918): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1918): VM cleaning up
D/dalvikvm( 1918): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1918): JNI_CreateJavaVM failed
E/AndroidRuntime( 1918): JNI_CreateJavaVM failed
D/AndroidRuntime( 1919):
D/AndroidRuntime( 1919): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1919): CheckJNI is OFF
W/dalvikvm( 1919): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1919): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1919): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1919): VM cleaning up
D/dalvikvm( 1919): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1919): JNI_CreateJavaVM failed
E/AndroidRuntime( 1919): JNI_CreateJavaVM failed
D/AndroidRuntime( 1920):
D/AndroidRuntime( 1920): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1920): CheckJNI is OFF
W/dalvikvm( 1920): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1920): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1920): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1920): VM cleaning up
D/dalvikvm( 1920): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1920): JNI_CreateJavaVM failed
E/AndroidRuntime( 1920): JNI_CreateJavaVM failed
D/AndroidRuntime( 1921):
D/AndroidRuntime( 1921): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1921): CheckJNI is OFF
W/dalvikvm( 1921): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1921): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1921): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1921): VM cleaning up
D/dalvikvm( 1921): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1921): JNI_CreateJavaVM failed
E/AndroidRuntime( 1921): JNI_CreateJavaVM failed
D/AndroidRuntime( 1922):
D/AndroidRuntime( 1922): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1922): CheckJNI is OFF
W/dalvikvm( 1922): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1922): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1922): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1922): VM cleaning up
D/dalvikvm( 1922): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1922): JNI_CreateJavaVM failed
E/AndroidRuntime( 1922): JNI_CreateJavaVM failed
D/AndroidRuntime( 1923):
D/AndroidRuntime( 1923): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1923): CheckJNI is OFF
W/dalvikvm( 1923): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1923): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1923): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1923): VM cleaning up
D/dalvikvm( 1923): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1923): JNI_CreateJavaVM failed
E/AndroidRuntime( 1923): JNI_CreateJavaVM failed
D/AndroidRuntime( 1926):
D/AndroidRuntime( 1926): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1926): CheckJNI is OFF
W/dalvikvm( 1926): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1926): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1926): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1926): VM cleaning up
D/dalvikvm( 1926): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1926): JNI_CreateJavaVM failed
E/AndroidRuntime( 1926): JNI_CreateJavaVM failed
D/AndroidRuntime( 1927):
D/AndroidRuntime( 1927): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1927): CheckJNI is OFF
W/dalvikvm( 1927): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1927): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1927): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1927): VM cleaning up
D/dalvikvm( 1927): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1927): JNI_CreateJavaVM failed
E/AndroidRuntime( 1927): JNI_CreateJavaVM failed
D/AndroidRuntime( 1928):
D/AndroidRuntime( 1928): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1928): CheckJNI is OFF
W/dalvikvm( 1928): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1928): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1928): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1928): VM cleaning up
D/dalvikvm( 1928): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1928): JNI_CreateJavaVM failed
E/AndroidRuntime( 1928): JNI_CreateJavaVM failed
D/AndroidRuntime( 1929):
D/AndroidRuntime( 1929): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1929): CheckJNI is OFF
W/dalvikvm( 1929): DexOpt: file has zero length and isn't writable
I/dalvikvm( 1929): Unable to open or create cache for /system/framework/ext.jar
D/dalvikvm( 1929): Failed on '/system/framework/ext.jar' (boot=1)
D/dalvikvm( 1929): VM cleaning up
D/dalvikvm( 1929): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 1929): JNI_CreateJavaVM failed
E/AndroidRuntime( 1929): JNI_CreateJavaVM failed
D/AndroidRuntime( 1930):
D/AndroidRuntime( 1930): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
wow...umm yea i gatta look that over but if you see nething odd before me let me kno i kno that fail aint good but im ganna delete java rite now
RanT476 said:
wow...umm yea i gatta look that over but if you see nething odd before me let me kno i kno that fail aint good but im ganna delete java rite now
Click to expand...
Click to collapse
What good is deleting Java going to do? :-S
RanT476 said:
wow....you didnt answer my question and i alrdy have ext3 answering my question just might help me with my coma problem so ya
Click to expand...
Click to collapse
wow....you're giving the guy stick for not answering your *whole* question? This isn't a f*cking call centre...
Anyway, back to your question: ext3 is pretty much the preffered filesystem for all ROMs, it's more efficient than ext2 because as david said, it uses journalling and it's probably more stable than ext4 because it's been out longer. So changing your filesystem won't help with kp's.
i see so i need a dev to look at this log is what your saying and no im not getting at him he was being a **** by bypassing my question like a **** so he deserves the **** comments he got from me(pause) but neway thx for answering my question
RanT476 said:
he was being a **** by bypassing my question like a **** so he deserves the **** comments he got from me(pause) but neway thx for answering my question
Click to expand...
Click to collapse
Maybe he didn't know the answer?! Why do people have to be so damn hostile? He's volenteerting his free time, answeres one of your questions and get's called a ****, nice!
"David1171 - i answered half of it." sounded kinda dickish to me but if u aint mean it that way no harm done misunderstanding is all i guess
RanT476 said:
"David1171 - i answered half of it." sounded kinda dickish to me but if u aint mean it that way no harm done misunderstanding is all i guess
Click to expand...
Click to collapse
always post your code with the code tags.
right now your the one that looks dickish. Someone tried to help you out, someone who is surrounded by noobs who ask stupid questions, yet he still takes time to try and help you out. Your question looked like one of them, as there are a lot of threads with that information around here. If you don't like the information given, don't say anything negative and ask for additional clarification.
As for your logcat, it seems to have the same crash over and over. Reflash your rom. you probably didnt wipe, and it looks like you have corrupted files
RanT476 said:
"David1171 - i answered half of it." sounded kinda dickish to me but if u aint mean it that way no harm done misunderstanding is all i guess
Click to expand...
Click to collapse
look at how many of my posts have helped people and how much time i have helped people root their phones, partition, other things they didn't understand and now do because i took the time to help them understand, i have been trying all night to help Z҉A҉L҉G҉O̚̕̚ to get his theme to fit within the confines of the hard spl so people that are afraid to flash the 1.33.2005 spl can use it with all the extras as well.
i misread your initial question and answer what i knew how to answer. i guess partial answer have never helped anyone reach their goal. maybe in the future we should all decide never to answer a question unless we know every single part of the answer with a clear and thought out thesis on how we reached our answer.
you should post your logcat in the thread for the rom you are using, there is a much bigger chance that the dev will see it in there then they will here where you are asking people who don't have all of the answers.
also thank you adriank.
WOW
Wrecking Crew needs to spend some time here obviously. HOLY SH*T! Adrian cursed TWICE in this thread!!!!!!!!!!! wow RanT, you must have hit one of his buttons real good and btw I would have posted the same thing david did as I don't know the answer to your second question either.
<3 david
sorry Adrian, I'm no pedo
i love how people feel they can attack me but w/e and i did post the "logcat" in the roms thread so no worries there and ill press buttons all i want if i feel im being smart mouthed just cause i asked as you said a "noob question" it cant be that noob if even you dont have the answer to the question so it will be returned back to u im not a bad dude but you can take w/e i say how ever you want go to the corner and cry if u want makes no diffrence to me and yea thx for attempting to help and u can curse all u want dude lol i get to laugh u look like a idiot and if u dont kno answers to questions just say you dont kno instead of making it seem like u dont see it or dont wanna answer it or w/e it may be
and yes i did wipe and redo just to make sure something stupid wasnt causeing this so i partitioned 4 gig transcend class 6 micro sdhc card
wiped my phone
redid my partitions
fat32 0 3400 3.4gigs
ext3(it was ext2 before the upgrade) 3400 3900 500megs
linux-swap 3900 3964 64megs
upgrade_fs
reboot recovery
wipe again
flashed rom
so i dnt see the problem redownloaded the rom did it all over again so i dnt kno
42....42.....424242..
42....42.............42..
424242.....424242..
........42.....42.........
........42.....424242..
try clearing your dalvik cache
whats the command i had it in my gmail but i erased it awhile back by accident....so ya tell me how and ill do it rite now
RanT476 said:
....so ya tell me how and ill do it rite now
Click to expand...
Click to collapse
Good luck. This is a community forum. We don't have anything to gain from helping people like you so most people ask when they need information. Anyways, here's your answer.
http://tinyurl.com/nxl9fr
lol im the bad guy ill just agree with you i dnt care enuff to carry this pointless bs of a insult u just threw at me, "people like you" funny how im the bad guy i ask a question and people cant answer it than i get called a noob lol but ok im the bad guy im wrong ill agree with you and GL to you too dude
Greetings fellow tinkerers, hope you can help.
After flashing AOSP eclair 2.0 I'm now unable to flash anything else, I get the below error (see code) for any mod I try and install.
I can no longer restore nandroid backups. I can only install the default sappimg.nbh.
I've tried to reroot the phone thinking maybe I lost root, but I can SU in terminal so I don't think that's the case.
edit: I've wiped and cleared everything, formatted the SD card, swapped the SD card.
edit: every time I try to do anything from the recovery console, e.g. nandriod resto or "fix package uid matches" it give me and error and tells me to run fix_permissions from adb
Tmobile MT3G (32B board)
HBOOT 1.33.0006
Tried Amon Ra and CM flash recovery
Any ideas?
Thanks.
Code:
D/AndroidRuntime( 2987): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 2987): CheckJNI is OFF
D/dalvikvm( 2987): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 2987): Stale deps in cache file; removing and retrying
W/dalvikvm( 2987): Size mismatch on inflated file (5461131 vs 5455656)
E/dalvikvm( 2987): Unable to extract+optimize DEX from '/system/framework/framework.jar'
D/dalvikvm( 2987): Failed on '/system/framework/framework.jar' (boot=1)
D/dalvikvm( 2987): VM cleaning up
D/dalvikvm( 2987): LinearAlloc 0x0 used 4100 of 4194304 (0%)
W/dalvikvm( 2987): JNI_CreateJavaVM failed
E/AndroidRuntime( 2987): JNI_CreateJavaVM failed
D/AndroidRuntime( 2988):
So you cant get into console?
Did you clear/wipe everything?
Ace42 said:
So you cant get into console?
Click to expand...
Click to collapse
What do you mean by console?
I can fastboot/use cm/amonRa recovery.
PlzHELP! said:
Did you clear/wipe everything?
Click to expand...
Click to collapse
I've cleared and wiped, reformatted my SD card.
Reinstalled sappimg.nbh.
cleared and wiped some more.
I've wiped and cleared with both root access and non-root access
charkosh said:
What do you mean by console?
I can fastboot/use cm/amonRa recovery.
Click to expand...
Click to collapse
Console is a option from recovery mode...
Ace42 said:
Console is a option from recovery mode...
Click to expand...
Click to collapse
I don't see "console" in the recovery mode for any of my recovery flashers, but I have seen the option before; as I have a MT3G there is no physical keyboard so I can't use console anyway.
ra1.2.1G
cm1.4
ra1.5.1G
He is using mt3g so there is no console.
IIRC correctly I can get a console if I use a dream recovery flasher
well have your tried to run fix_permissions from adb like it said? if you dont know how to use adb there are threads on how to set it up. also if you can boot a rom and download a terminal app with an on screen keyboard you can run fix_permissions from terminal
Just boot into recovery and open up the cmd prompt and do
adb shell
then below should be a
#
try pushing this file from another rom using adb
/system/framework/framework.jar
if u dont know how i think its like this:
adb remount
adb push framework.jar /system/framework/
or sthg like this,, u can search around for how to use adb
m_kayali said:
try pushing this file from another rom using adb
/system/framework/framework.jar
if u dont know how i think its like this:
adb remount
adb push framework.jar /system/framework/
or sthg like this, u can search around for how to use adb
Click to expand...
Click to collapse
Definitely worth trying, where can I obtain the correct framework.jar?
am I bricked?
Update:
I did try all the ADB stuff
Code:
D/AndroidRuntime( 201): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 201): CheckJNI is OFF
D/dalvikvm( 201): Precise GC configured ON
W/dalvikvm( 201): ERROR: Unable to find decl for native Lorg/apache/harmony/luni/platform/OSNetworkSystem;.createStreamSocketImpl (Ljava/io/FileDescriptor;Z)V
E/JNIHelp ( 201): RegisterNatives failed for 'org/apache/harmony/luni/platform/OSNetworkSystem'
W/dalvikvm( 201): jniRegisterSystemMethods failed
D/dalvikvm( 201): VM cleaning up
D/dalvikvm( 201): LinearAlloc 0x0 used 115780 of 5242880 (2%)
W/dalvikvm( 201): JNI_CreateJavaVM failed
E/AndroidRuntime( 201): JNI_CreateJavaVM failed
^C
I'm still getting all sorts of errors. Not to mention I apparently am still able to flash the phone, there are apparently only two ways to get my phone to run:
sappimg.nbh or a nandroid restore
I can't flash/upgrade any roms nor get root access (used telnet and unlockr method)
Did I brick my phone?
Any ideas?
I will love you for always
charkosh said:
Update:
I did try all the ADB stuff
Code:
D/AndroidRuntime( 201): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 201): CheckJNI is OFF
D/dalvikvm( 201): Precise GC configured ON
W/dalvikvm( 201): ERROR: Unable to find decl for native Lorg/apache/harmony/luni/platform/OSNetworkSystem;.createStreamSocketImpl (Ljava/io/FileDescriptor;Z)V
E/JNIHelp ( 201): RegisterNatives failed for 'org/apache/harmony/luni/platform/OSNetworkSystem'
W/dalvikvm( 201): jniRegisterSystemMethods failed
D/dalvikvm( 201): VM cleaning up
D/dalvikvm( 201): LinearAlloc 0x0 used 115780 of 5242880 (2%)
W/dalvikvm( 201): JNI_CreateJavaVM failed
E/AndroidRuntime( 201): JNI_CreateJavaVM failed
^C
I'm still getting all sorts of errors. Not to mention I apparently am still able to flash the phone, there are apparently only two ways to get my phone to run:
sappimg.nbh or a nandroid restore
I can't flash/upgrade any roms nor get root access (used telnet and unlockr method)
Did I brick my phone?
Any ideas?
I will love you for always
Click to expand...
Click to collapse
sorry for being late to response
u can get framework.jar from the original donut rom or any other rom i guess
from what i know if u can access the bootloader mode then ur not bricked.
did u get your phone to work by using sappimg.nbh?
i figured out u have perfected spl, i think that there is a 10% chance that it is causing all this stuff
dunno if it helps but plz check this link
http://forum.xda-developers.com/showthread.php?t=548218
!!!!!!!!BUT PLEASE TAKE CAUTION WHILE TRYING THIS OUT, DO SOME READING!!!!!!!!
still no dice
Tried the NON-perfected SPL's and didn't seem to fix the problem,
What do
Code:
D/dalvikvm( 161): DexOpt: incorrect opt magic number (0xff ff ff ff)
and
W/dalvikvm( 161): Size mismatch on inflated file (5540041 vs 5539684)
mean?
Any ideas?
Code spam to follow
Code:
I//system/xbin/busybox( 49): --- Executing firstboot.sh
I//system/xbin/busybox( 49): --- Checking filesystems
I//system/xbin/busybox( 49): e2fsck 1.41.9 (22-Aug-2009)
I//system/xbin/busybox( 49): /dev/block/mmcblk0p2 was not cleanly unmounted, check forced.
I//system/xbin/busybox( 49): Pass 1: Checking inodes, blocks, and sizes
I//system/xbin/busybox( 49): Pass 2: Checking directory structure
I//system/xbin/busybox( 49): Pass 3: Checking directory connectivity
I//system/xbin/busybox( 49): /lost+found not found. Create? yes
I//system/xbin/busybox( 49): Pass 4: Checking reference counts
I//system/xbin/busybox( 49): Pass 5: Checking group summary information
I//system/xbin/busybox( 49): /dev/block/mmcblk0p2: ***** FILE SYSTEM WAS MODIFIED *****
I//system/xbin/busybox( 49): /dev/block/mmcblk0p2: 11/249856 files (0.0non-contiguous), 31384/499300 blocks
I//system/xbin/busybox( 49): cp: cannot stat '/data/app-private/*': No such file or directory
I//system/xbin/busybox( 49): +++ Apps-to-SD successfully enabled
I/logwrapper( 49): /system/xbin/busybox terminated by exit(0)
I/DEBUG ( 138): debuggerd: Dec 2 2009 20:35:30
E/flash_image( 144): error opening /data/recovery.img: No such file or directory
I/vold ( 137): Android Volume Daemon version 2.0
I/vold ( 137): New MMC card 'SU04G' (serial 293776) added @ /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa
I/vold ( 137): Disk (blkdev 179:0), 7744512 secs (3781 MB) 3 partitions
I/vold ( 137): New blkdev 179.0 on media SU04G, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 3
I/vold ( 137): Partition (blkdev 179:1), 6682977 secs (3263 MB) type 0xc
I/vold ( 137): New blkdev 179.1 on media SU04G, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 2
I/vold ( 137): Partition (blkdev 179:2), 998601 secs (487 MB) type 0x83
I/vold ( 137): New blkdev 179.2 on media SU04G, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 1
D/AKMD ( 146): akmd 1.6.6 START
D/AKMD ( 146): library version: 1.2.1.1129
I/vold ( 137): Partition (blkdev 179:3), 62871 secs (30 MB) type 0x82
I/vold ( 137): New blkdev 179.3 on media SU04G, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 0
I/vold ( 137): Evaluating dev '/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa/block/mmcblk0' for mountable filesystems for '/sdcard'
I/vold ( 137): Aborting start of /sdcard (bootstrap = 1)
I/vold ( 137): Volmgr not ready to handle device
D/vold ( 137): Bootstrapping complete
E/RIL Acoustic( 139): Fail to open /system/etc/AudioPara_TMUS.csv -1.
I/RIL Acoustic( 139): open /system/etc/AudioPara4.csv success.
I/RIL Acoustic( 139): acoustic table version: Sapphire_TMU_20090305
I/RIL Acoustic( 139): read_audio_para_from_file success.
D/AndroidRuntime( 140):
D/AndroidRuntime( 140): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 140): CheckJNI is OFF
D/dalvikvm( 140): Precise GC configured ON
I/dalvikvm( 140): DexOpt: source file mod time mismatch (3b77614f vs 3b8c9f51)
D/dalvikvm( 140): Stale deps in cache file; removing and retrying
I/ ( 141): ServiceManager: 0xac38
I/HTC Acoustic( 141): libhtc_acoustic.so version 1.0.1.1.
E/HTC Acoustic( 141): Fail to open /system/etc/AudioPara_TMUS.csv -1.
I/HTC Acoustic( 141): open /system/etc/AudioPara4.csv success.
D/A2dpAudioInterface( 141): A2dpAudioInterface::openOutputStream 1, 0, 0
I/AudioFlinger( 141): AudioFlinger's thread ready to run for output 0
D/A2DP ( 141): a2dp_init rate: 44100 channels: 2
D/A2DP ( 141): a2dp_thread started
D/A2dpAudioInterface( 141): A2dpAudioStreamOut::set 1, 0, 0
D/AudioFlinger( 141): set output to hardware audio
I/AudioHardwareMSM72XX( 141): Routing audio to Speakerphone
D/HTC Acoustic( 141): msm72xx_enable_audpp: 0x0001
D/A2DP ( 141): bluetooth_init
I/AudioFlinger( 141): AudioFlinger's thread ready to run for output 1
I/AudioHardwareMSM72XX( 141): Set master volume to 5.
E/A2DP ( 141): bt_audio_service_open failed
I/CameraService( 141): CameraService started: pid=141
D/dalvikvm( 140): DexOpt: --- BEGIN 'core.jar' (bootstrap=1) ---
D/dalvikvm( 157): Ignoring duplicate verify attempt on Ljava/lang/Object;
D/dalvikvm( 157): Ignoring duplicate verify attempt on Ljava/lang/Class;
D/dalvikvm( 157): DexOpt: load 509ms, verify 5951ms, opt 263ms
D/dalvikvm( 140): DexOpt: --- END 'core.jar' (success) ---
D/dalvikvm( 140): DEX prep '/system/framework/core.jar': unzip in 994ms, rewrite 8551ms
I/dalvikvm( 140): DexOpt: source file mod time mismatch (3b776162 vs 3b8c9f6e)
D/dalvikvm( 140): Stale deps in cache file; removing and retrying
D/dalvikvm( 140): DexOpt: --- BEGIN 'ext.jar' (bootstrap=1) ---
D/dalvikvm( 158): DexOpt: load 136ms, verify 1700ms, opt 47ms
D/dalvikvm( 140): DexOpt: --- END 'ext.jar' (success) ---
D/dalvikvm( 140): DEX prep '/system/framework/ext.jar': unzip in 165ms, rewrite 2357ms
I/dalvikvm( 140): DexOpt: source file mod time mismatch (3b776186 vs 3b8e0583)
D/dalvikvm( 140): Stale deps in cache file; removing and retrying
W/dalvikvm( 140): Size mismatch on inflated file (5540041 vs 5539684)
E/dalvikvm( 140): Unable to extract+optimize DEX from '/system/framework/framework.jar'
D/dalvikvm( 140): Unable to process classpath element '/system/framework/framework.jar'
I/dalvikvm( 140): DexOpt: source file mod time mismatch (3b7761bb vs 3b8ca05a)
D/dalvikvm( 140): Stale deps in cache file; removing and retrying
D/dalvikvm( 140): DexOpt: --- BEGIN 'android.policy.jar' (bootstrap=1) ---
D/dalvikvm( 159): DexOpt: load 27ms, verify 15ms, opt 2ms
D/dalvikvm( 140): DexOpt: --- END 'android.policy.jar' (success) ---
D/dalvikvm( 140): DEX prep '/system/framework/android.policy.jar': unzip in 28ms, rewrite 2731ms
I/dalvikvm( 140): DexOpt: source file mod time mismatch (3b7761d8 vs 3b8ca07b)
D/dalvikvm( 140): Stale deps in cache file; removing and retrying
D/dalvikvm( 140): DexOpt: --- BEGIN 'services.jar' (bootstrap=1) ---
D/dalvikvm( 160): DexOpt: load 77ms, verify 111ms, opt 3ms
D/dalvikvm( 140): DexOpt: --- END 'services.jar' (success) ---
D/dalvikvm( 140): DEX prep '/system/framework/services.jar': unzip in 293ms, rewrite 1945ms
D/AndroidRuntime( 140): --- registering native functions ---
E/JNIHelp ( 140): Native registration unable to find class 'android/debug/JNITest'
E/AndroidRuntime( 140): Unable to register all android natives
D/AndroidRuntime( 161):
D/AndroidRuntime( 161): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 161): CheckJNI is OFF
D/dalvikvm( 161): Precise GC configured ON
D/dalvikvm( 161): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 161): Stale deps in cache file; removing and retrying
W/dalvikvm( 161): Size mismatch on inflated file (5540041 vs 5539684)
E/dalvikvm( 161): Unable to extract+optimize DEX from '/system/framework/framework.jar'
D/dalvikvm( 161): Unable to process classpath element '/system/framework/framework.jar'
D/AndroidRuntime( 161): --- registering native functions ---
E/JNIHelp ( 161): Native registration unable to find class 'android/debug/JNITest'
E/AndroidRuntime( 161): Unable to register all android natives
Update
I got the whole gold card thing working still having the same problem with framework.jar with cyanogen 4.2.8.1.
For some reason the ONLY way to get anything working is through one particular nandroid from cm 4.2.7.1 that I have. Is there anyway to use that to my advantage.
I can't upgrade or install any other ROMs, and I'm pretty much at wits end.
Anyone?
bump,
How do I fix this?
charkosh said:
bump,
How do I fix this?
Click to expand...
Click to collapse
reformat your sd card again, place on it hard spl, htc image for mytouch, and cyans latest rom. then flash hard spl or w/e is similar to it for the mt3g (majority of the time the danger spl is what screws things up for people), then reboot, so it takes you back to recovery, then flash teh htc image, do no reboot yet, and immedaitely flash cyans rom, then reboot. should allow you to start from scratch and have everything work again.
Can you please clarify hard spl and where I can get it?
Thanks.
Hey guys im trying to get this 3D Friend stream widget to work on Honeysense but it needs the matching app it wont work with the standard friend stream app.
When i use the standard Honeysense HD Friendstream app with the 3D Widget, the widget works and the app works BUT, on the widget you can see where the feeds would be but nothing in them and the contact pictures are just blank
When i use both 3D Widget and matching app i get force close on the APP not the widget.
So my question is what am i missing... im guessing there is a link missing between the 3D widget and the stock app which is why its not showing the streams, but i cant find it..
Thanks.
Bellow is the error it throws when entering the APP:
Code:
12:00:14.809 Error AndroidRuntime 5340 FATAL EXCEPTION: main
12:00:14.809 Error AndroidRuntime 5340 java.lang.NoSuchMethodError: com.htc.friendstream.MultipleActivitiesMain.setMainContainer
12:00:14.810 Error AndroidRuntime 5340 at com.htc.friendstream.MultipleActivitiesMain.initMainLayout(MultipleActivitiesMain.java:54)
12:00:14.810 Error AndroidRuntime 5340 at com.htc.friendstream.MultipleActivitiesMain.onCreate(MultipleActivitiesMain.java:29)
12:00:14.810 Error AndroidRuntime 5340 at com.htc.friendstream.SwitchMultipleActivityMain.onCreate(SwitchMultipleActivityMain.java:23)
12:00:14.810 Error AndroidRuntime 5340 at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1093)
12:00:14.810 Error AndroidRuntime 5340 at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1780)
12:00:14.810 Error AndroidRuntime 5340 at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1837)
12:00:14.810 Error AndroidRuntime 5340 at android.app.ActivityThread.access$1500(ActivityThread.java:132)
12:00:14.810 Error AndroidRuntime 5340 at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1033)
12:00:14.810 Error AndroidRuntime 5340 at android.os.Handler.dispatchMessage(Handler.java:99)
12:00:14.810 Error AndroidRuntime 5340 at android.os.Looper.loop(Looper.java:143)
12:00:14.810 Error AndroidRuntime 5340 at android.app.ActivityThread.main(ActivityThread.java:4196)
12:00:14.810 Error AndroidRuntime 5340 at java.lang.reflect.Method.invokeNative(Native Method)
12:00:14.811 Error AndroidRuntime 5340 at java.lang.reflect.Method.invoke(Method.java:507)
12:00:14.811 Error AndroidRuntime 5340 at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
12:00:14.811 Error AndroidRuntime 5340 at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
12:00:14.811 Error AndroidRuntime 5340 at dalvik.system.NativeStart.main(Native Method)
At the start I want to mention I need to have access to some of 4.1 API features, so that I cannot use MiniCM9 or older.
The problem is that when I try to deploy any Eclipse project, or try to install it via
Code:
adb install
IDE throws:
Code:
[2013-02-18 20:41:21 - BasicGLSurfaceView] Installation failed due to invalid APK file!
[2013-02-18 20:41:21 - BasicGLSurfaceView] Please check logcat output for more details.
[2013-02-18 20:41:21 - BasicGLSurfaceView] Launch canceled!
And here is logcat snippet from my phone:
Code:
D/AndroidRuntime( 9226): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
D/AndroidRuntime( 9226): CheckJNI is OFF
D/dalvikvm( 9226): Trying to load lib libjavacore.so 0x0
D/dalvikvm( 9226): Added shared lib libjavacore.so 0x0
D/dalvikvm( 1722): GC_EXPLICIT freed 87K, 34% free 6828K/10247K, paused 4ms+21ms, total 118ms
D/dalvikvm( 9226): Trying to load lib libnativehelper.so 0x0
D/dalvikvm( 9226): Added shared lib libnativehelper.so 0x0
I/ActivityManager( 1653): Process com.android.defcontainer (pid 9093) has died.
D/AndroidRuntime( 9226): Calling main entry com.android.commands.pm.Pm
I/ActivityManager( 1653): Start proc com.android.defcontainer for service com.android.defcontainer/.DefaultContainerService: pid=9236 uid=10027 gids={1015, 2001, 1028}
I/ActivityManager( 1653): Process com.google.android.gsf.login (pid 9156) has died.
E/Trace ( 9236): error opening trace file: No such file or directory (2)
W/zipro ( 9236): Unable to open zip '/data/local/tmp/BasicGLSurfaceView.apk': Permission denied
D/asset ( 9236): failed to open Zip archive '/data/local/tmp/BasicGLSurfaceView.apk'
W/PackageParser( 9236): Unable to read AndroidManifest.xml of /data/local/tmp/BasicGLSurfaceView.apk
W/PackageParser( 9236): java.io.FileNotFoundException: AndroidManifest.xml
W/PackageParser( 9236): at android.content.res.AssetManager.openXmlAssetNative(Native Method)
W/PackageParser( 9236): at android.content.res.AssetManager.openXmlBlockAsset(AssetManager.java:521)
W/PackageParser( 9236): at android.content.res.AssetManager.openXmlResourceParser(AssetManager.java:477)
W/PackageParser( 9236): at android.content.pm.PackageParser.parsePackageLite(PackageParser.java:749)
W/PackageParser( 9236): at com.android.defcontainer.DefaultContainerService$1.getMinimalPackageInfo(DefaultContainerService.java:169)
W/PackageParser( 9236): at com.android.internal.app.IMediaContainerService$Stub.onTransact(IMediaContainerService.java:110)
W/PackageParser( 9236): at android.os.Binder.execTransact(Binder.java:367)
W/PackageParser( 9236): at dalvik.system.NativeStart.run(Native Method)
W/DefContainer( 9236): Failed to parse package
W/ActivityManager( 1653): No content provider found for permission revoke: file:///data/local/tmp/BasicGLSurfaceView.apk
D/dalvikvm( 1653): GC_EXPLICIT freed 149K, 36% free 18567K/28807K, paused 6ms+12ms, total 141ms
D/AndroidRuntime( 9226): Shutting down VM
D/dalvikvm( 9226): GC_CONCURRENT freed 125K, 77% free 478K/2048K, paused 1ms+1ms, total 8ms
D/dalvikvm( 9226): Debugger has detached; object registry had 1 entries
Changing permissions and owners didn't give or changed anything, it further says that there is no permissions to access APK file.
I think it is releated to kernel or ROM, so I want to ask if someone knows a solution or something to change in kernel/ROM sources to fix it up.
I use: MiniCM10-4.0.2-20130210-NIGHTLY-shakira ( on stable MiniCM10, problem also occur ) with kernel 2.6.32.60-nAa-jb-03.
Yes, it is kind a solution, but when I want to test my app many times, it won't be comfortable solution, and I'm searching permament fix for this issue
Go to Settings > Development > Enable Root for Apps and ADB.
And you should be using the latest nightly only. It has fixes for the .32 kernel.
CtrlAltDelIrl said:
Go to Settings > Development > Enable Root for Apps and ADB.
Click to expand...
Click to collapse
It changes nothing at all
There is an on/off switch at the top of the dev settings page. Make sure it's on.
Use latest nightly only with .32
I'm using latest nightly with .32 kernel, I have Root access enabled for Apps and ADB, and I'm sure switch is on, It could be kernel or ROM problem, but I haven't had any knowledge about how to try fix it.
Oh could be SuperSu instead of default Superuser a problem? Because I always changing it when I reinstall ROM.
But I have root access when using adb shell, only adb install fails
Try this..
Code:
adb pm install
Before install use
Adb remount
Sent from my U20i using xda premium
CtrlAltDelIrl said:
Try this..
Code:
adb pm install
Click to expand...
Click to collapse
When I transfer apk manually and try using command you've posted from
Code:
adb shell
it gives me
Code:
pkg: Application.apk
Failure [INSTALL_FAILED_INVALID_APK]
and ADB logs:
Code:
W/zipro ( 7157): Unable to open zip '/data/local/tmp/Application.apk': Permission denied
D/asset ( 7157): failed to open Zip archive '/data/local/tmp/Application.apk'
but,
when I transfer the file to sdcard, and then execute
Code:
pm install
then it result with success and everything is ok
Rempty said:
Before install use
Adb remount
Sent from my U20i using xda premium
Click to expand...
Click to collapse
Doesn't work
mmmm
let's wait patiently for an update I'd say..
Good luck!
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