Separate names with a comma.
Discussion in 'ChevyNo1' started by ChevyNo1, Jun 25, 2010.
Yeah mototorch works, flash beta 3 doesnt
Almost have that one working now also - turns out installing apps from recovery is a little tricky
Run just the command 'top' ... what do you see? Then run:
ls -l `which top`
ls -l `which busybox`
Interesting, the launcher on this is different than Jrummy. This uses the scroll up and down launcher and Jrummy uses one similar to Apple iOS, left and right scroll.
The Flash update should work now - let me know if you find otherwise!
Also note - it may take a minute after bootup for flash to show as installed ...
How do I install MotoTorch? Just rename to <update>? Then install @ recovery?
If you are using SPR, yes rename to update.zip - if using CWR, no need to rename, just install as a ROM update
top shows a normal top... seems to work ok
top -> toolbox
To be more specific, mtop works in adb shell but is not running in Better Terminal. I guess this may be just an issue with Better Terminal?
I've got another issue with a2sd but i'll put that in a separate post.
Yea, if it works in adb - then it sounds like a Better Terminal issue - since the commands also run in DevTools -> Terminal
Did another wipe/install sequence this morning. 15 minutes from start to finish with over 100 apps.
RSTAPPS missed the following apps/components:
GDocs IOExtras 1.0.5
Documents to Go full version key 2.003
Otherwise, seemed to work flawlessly. I didn't try the Flash or MotoTorch install because they weren't working last night and I didn't see they were fixed until I came here.
Even with the missed apps, this is still a spectacular package, Chev. Nice work.
I wanted to give a try to a2sd. I'm not really sure what the benefit is but figured I'd try it out.
I ran a2sd on and then went to applications and tried to move a couple of apps. After moving one application I got an error on the next: "Failed to move application. There is not enough storage left." Where can I find some doc on a2sd to understand it a little better and fix this issue?
a2sd is just a basic script for the most part that 'flips the switch' to allow installs to SD - therefore it really is the apps2sd that is native to Froyo that is giving you the error. Does it happen on all successive apps now? Can you run a logcat?