Hey gang,
I am trying to create a script (using GScript Lite) that will preview the boot animation currently loaded. I am running 2.1 leak v3 and don't have root yet. I made a script with only one line like this: "adb shell bootanimation" and saved it. When I try to run the script I get the "permission denied" error. I guess I need root to run the command locally on the phone. Odd though.... because I can run the command from my computer connected via USB and it works just fine. Can anyone explain why its not working locally when I run the script? Surely it does not trigger root access when running this command from a computer.... does it?
Curious....
Also, is there another way around this so I can accomplish previewing the boot animation on my phone without external input? I searched the market and installed the app called "Boot Animation Preview Lite". It required AndExplorer to be installed to work.... but it never did actually work. Only Force Closes on every attempt.
synaptyc said:
Hey gang,
I am trying to create a script (using GScript Lite) that will preview the boot animation currently loaded. I am running 2.1 leak v3 and don't have root yet. I made a script with only one line like this: "adb shell bootanimation" and saved it. When I try to run the script I get the "permission denied" error. I guess I need root to run the command locally on the phone. Odd though.... because I can run the command from my computer connected via USB and it works just fine. Can anyone explain why its not working locally when I run the script? Surely it does not trigger root access when running this command from a computer.... does it?
Curious....
Also, is there another way around this so I can accomplish previewing the boot animation on my phone without external input? I searched the market and installed the app called "Boot Animation Preview Lite". It required AndExplorer to be installed to work.... but it never did actually work. Only Force Closes on every attempt.
Click to expand...
Click to collapse
Have you tried
Code:
adb shell bootanimation
I doubt it needs root to be run but that will show you the boot animation and it will keep looping until you stop the command which on windows is control C
lol.... did you even read my post?
rofl
synaptyc said:
lol.... did you even read my post?
rofl
Click to expand...
Click to collapse
Lol probably not...
when running it from the phone where is it running from?
also if you are running it from phone it doesn't need the adb shell part
it should be
Code:
bootanimation
^^ I tried this from a terminal but it doesn't work unless I give the terminal su privilages.
so there might not be a way to do this on the phone without root privilages.
Sorry I couldn't be any help.
Its all good t2noob. Thnx for the info... food for thought.
Time to write an app for that =)
results so far:
I created a GScript called "bootscreen" (because I am using a bootscreen with sound and not a "bootanimation.zip"
I checked 'Needs SU?' because I now have root
Then I added the line: bootanimation
All goes well, and I can see/hear my bootscreen BUT I can't end it.
It continually loops like it is supposed to.
Can anyone tell me how to kill the bootanimation once it has been called via GScript Lite?
Things I have tried:
hitting the BACK, HOME, MENU, END/OFF buttons. really every button on the phone.
tapping the place on the screen where I have a "QuitIt" widget that will kill all running apps
The phone will accept screen input because I can tap where certain apps are and tell that they are launching. IE: phone, music player, etc.
I was even able to reboot the phone using Quick Boot just because I knew where the on-screen buttons were to make it reboot.
There seems to be no way to kill the bootanimation except to pull the battery.
Maybe I could create a GScrpit that will kill it, then just know where it is on the screen behind the animation?
Any tips?
EDIT: I created a script like this but it still didn't kill the bootanimation (it did run correctly with the sleep thing though)
Code:
bootanimation
sleep 10
pkill bootanimation
pkill boot1.gif
pkill boot2.gif
This is how I've done it through gscrip:
Code:
TIMEOUT=20
( bootanimation & sleep
$TIMEOUT; kill $! 2>/dev/null )
you can change the timeout duration to suit your liking (it's in seconds).
Regards,
Yahya
running vegan and i keep getting this message. I think my wife was using it and maybe the battery died? not sure. any thoughts?
thanks
I get this about every 2 weeks. I boot into clockwork, reset to defaults, then restore from backup.
sent from my g-tablet using tapatalk
i got it. found the answer in the android general forums. You have to delete a database and it clears it up.
Steps
Posting the steps you took might be a little more helpful to anyone reading your thread.....
gpzjack said:
i got it. found the answer in the android general forums. You have to delete a database and it clears it up.
Click to expand...
Click to collapse
Which data base?
Do you mean perform a clear cache/data?
or are you mentioning the contact database sync from gmail?
from another post:
I noticed at least two people in this thread have had this problem. The following worked for me... At one point I started getting this error also. Driving me crazy! Could not bring up the keyboard, and the message would pop like every 5 seconds. I searched and found this post (thanks and credit to KinkyMunkey):
process com.android.acore FC and how i fixed it
I didn't want to wipe data, so I tried it. I couldn't use ES File Explorer for this, but Root Explorer worked great!
The problem is a corrupt contacts sqlite database. As the referenced post says, you'll be able to tell if thats the problem when there is a .db-journal file in the folder. The folder is /data/data/com.android.providers.contacts/databases/ *Note* this is not the data folder in sdcard, but the data folder in root (/).
Just delete the databases folder in /data/data/com.android.providers.contacts and restart. The contacts database will be rebuilt and re-synced.
This has worked for me twice (thank goodness). I don't know what causes the contacts DB to get messed up... it wasn't a drained battery for me.
Thank you so much, this worked for me!
gpzjack said:
from another post:
I noticed at least two people in this thread have had this problem. The following worked for me... At one point I started getting this error also. Driving me crazy! Could not bring up the keyboard, and the message would pop like every 5 seconds. I searched and found this post (thanks and credit to KinkyMunkey):
process com.android.acore FC and how i fixed it
I didn't want to wipe data, so I tried it. I couldn't use ES File Explorer for this, but Root Explorer worked great!
The problem is a corrupt contacts sqlite database. As the referenced post says, you'll be able to tell if thats the problem when there is a .db-journal file in the folder. The folder is /data/data/com.android.providers.contacts/databases/ *Note* this is not the data folder in sdcard, but the data folder in root (/).
Just delete the databases folder in /data/data/com.android.providers.contacts and restart. The contacts database will be rebuilt and re-synced.
This has worked for me twice (thank goodness). I don't know what causes the contacts DB to get messed up... it wasn't a drained battery for me.
Click to expand...
Click to collapse
I also had the "android.process.acore process has stopped" problem. I seem to have fixed it by going to "Manage Apps", "Running", "Contacts Storage", "Clear Data", then same process for Contacts Sync Adapter. Seems to have resolved problem...so far.
yup the contacts storage got corrupted -> most likely you created an empty contact in the contacts app by mistake. Someone should sticky this - i see one of these threads daily haha. Its a pretty common problem.
many time that error (fc) is due to a contact with blank first and last name as the contact database uses them as index. if you have blanks the probem will keep returning.
thanks for the tip - seems to have helped me out of the
...acore... problem
Mind you, I **Never** touched the contacts app in any
way whatsoever.
The corruption happened "spontaneously"
After playing (it is *only* suitable for play) with android
for a few weeks now, you know what, android is CRAP
Cant get to Manage Apps
Everytime I go to settings the damn thing pops up. Cant get to anything to clear the data base. Dont have root explorer and cant find that in the file manager I do have.
Any help?
cassycan said:
Everytime I go to settings the damn thing pops up. Cant get to anything to clear the data base. Dont have root explorer and cant find that in the file manager I do have.
Any help?
Click to expand...
Click to collapse
I had this problem just tonight. Thanks to GPZJack for posting the file to delete. For those of you who can't launch programs because of the "force close" dialog, here is how to do it without that.
1) Install the android developer kit on your PC. You will need the program adb (short for android debugger). I tried to post a link to the instructions, but am too noobish for the forum to allow me to post links. Just google android sdk install
2) Attach gtablet to computer using usb cable
3) [Assuming windows] Launch a command window. cd to tools directory under the android sdk install directory.
4) type the command "adb devices" (without quotes) to verify that adb sees your tablet. If not, you need to install the correct usb drivers. Find help with google gtablet usb driver install
5) type the command "adb shell" (without quotes) This will connect you to the tablet and provide you with a unix shell prompt #
!! Careful with this next command. It will delete the databases directory. Make sure you type the line correctly so that you don't accidentally delete something else.
6) #rm -r /data/data/com.android.providers.contacts/databases
7) #reboot
And your tablet should reboot and work.
Hope that helps!
Norm Minske said:
I also had the "android.process.acore process has stopped" problem. I seem to have fixed it by going to "Manage Apps", "Running", "Contacts Storage", "Clear Data", then same process for Contacts Sync Adapter. Seems to have resolved problem...so far.
Click to expand...
Click to collapse
I was unable to see the folder described in other peoples solutions, your solution of clearing data through the settings application worked great for me on brilliant corners 1.3.1. Thanks.
simuloid said:
I had this problem just tonight. Thanks to GPZJack for posting the file to delete. For those of you who can't launch programs because of the "force close" dialog, here is how to do it without that.
1) Install the android developer kit on your PC. You will need the program adb (short for android debugger). I tried to post a link to the instructions, but am too noobish for the forum to allow me to post links. Just google android sdk install
2) Attach gtablet to computer using usb cable
3) [Assuming windows] Launch a command window. cd to tools directory under the android sdk install directory.
4) type the command "adb devices" (without quotes) to verify that adb sees your tablet. If not, you need to install the correct usb drivers. Find help with google gtablet usb driver install
5) type the command "adb shell" (without quotes) This will connect you to the tablet and provide you with a unix shell prompt #
!! Careful with this next command. It will delete the databases directory. Make sure you type the line correctly so that you don't accidentally delete something else.
6) #rm -r /data/data/com.android.providers.contacts/databases
7) #reboot
And your tablet should reboot and work.
Hope that helps!
Click to expand...
Click to collapse
i manage to get tru the issue on adb shell by installing usb deview, n my command bar alrdy shown my device no. after typing adb devices but aft adb shell, came $ and not #, is there any different?
okay i had mine miracle- ly and not realising it done, my force stop no longer appear after downloading the latest busybox apps.=)
Hi - I was getting the acore error too. but I went ahead & did an nvflash. The error is still popping up. Any ideas?
So here's the deal. I'm getting in to some dirty work with Ninjamorph, but after finishing a project, I know it does not resign an .apk. When I try to put the .apk I've modded through Signapktic it spits out the error: "which: applet not found".
Typing which into the terminal emulator yields the same result. Apparently I'm a serious noob when it come to androids, because Busybox is installed and I thought which would have been added to the commands at that point. How do I get which to work? Because being able to do all this modding on the phone is ridiculously convenient.
So, I failed, and didn't realize there was a new busybox version available. which is now working on my phone.
Signapktic, however, does nothing. I click start, it says it's been given su permissions, and then says finished (the terminal log is empty).
Hi.
I tried to use the Emacs app from Google play store to see if I could see and edit various settings (as I sometimes do in classical unix when nothing else helps), but apparently the "dired" command is not working. I get the message "Listing directory failed, but 'access file ' worked". Is this due to the fact that I do not have superuser rights? Is it possible to give the emacs app su rights?
(As you can see, I do not know much about Android.)
Olof47 said:
Hi.
I tried to use the Emacs app from Google play store to see if I could see and edit various settings (as I sometimes do in classical unix when nothing else helps), but apparently the "dired" command is not working. I get the message "Listing directory failed, but 'access file ' worked". Is this due to the fact that I do not have superuser rights? Is it possible to give the emacs app su rights?
Click to expand...
Click to collapse
The original question still remains unanswered, but I just realized that for me there is a very simple workaround (which I should have realized much earlier):
Since I use NativeSD the whole system is on the SD-card, and nothing prevents me from putting the SD-card into a card reader, and mounting it on a unix computer (in my case Kubuntu). This way I can mount both the FAT-partition and the Ext4-partition, and modify whatever I want.
This is one of the reasons why I like NativeSD: I have the original boot loader and the original Windows Mobile 6.5 in DRAM in my HD2, and no matter how many errors I do when I try to install NaviteSD roms on the SD card I do not brick the phone, as long as I do not touch DRAM. And I find the NativeSD roms surpisingly fast.
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
duuude im baked said:
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
Click to expand...
Click to collapse
Thought I would share some info I found when I ran into the wifi problem on my daughter's nabi. I did some searches on the internet and the typical answer I found for solving the wifi issue was "reset the device" or "unroot and return to stock rom - flash all updates and reroot". Being a glutton for punishment, and the fact I didn't want to reset the device, I searched and searched and was able to fix my daughter's wifi without doing a reset or unroot/reroot. Before I get into it I wanted to mention that wifi failures can happen for a number of reasons so while this worked for myself, it may not work for you.
Some prerequisites:
Most importantly; you need a rooted device. If you do not have root access you will not be able to write files or access the commands to fix the issue I am about to outline.
Some knowledge of linux would be helpful, but not necessarily required.
Lets get started:
Warning! It goes without saying but I will say it anyways - you can mess up your nabi by rooting it. Some of the commands below could mess up your nabi bad. If this scares you then you probably should not proceed any further. I am not responsible for any damage you do to your nabi.
Commands are listed between ' and ' - do not use the ' when inputing the commands.
Note: The first two/three steps are not necessary but they do give you insight as to how I was able to determine my problem. If following this doesn't fix the problem for you the logcat output may give you some important info that you can google that may help you fix your particular problem.
Note: Steps 5 and on can be skipped if you have a text editor (vi or nano) on your device. If you have a text editor loaded simply edit the conf file directly.
1. You will need to run the command 'adb logcat' in a command-line window and in your appropriate directory. Adb is available as part of the android sdk but can also be found stand alone since most people do not need the sdk.
2. Try to turn on the wifi. You should see the output of your adb logcat window scroll some data. If the wifi is not attempting to turn on at all sometimes you can move between the settings options then go back to the wifi settings and move the slider. If you cannot get your wifi to turn on you can scroll the window up and attmept to find the data from when the device started up. In the output you should see lines that talk about wlan0 and probably something that says "failed" somewhere. In my case I could see where the wlan0 enabled but then a few lines down it said something about "Line: 25 failed" and "failed to parse file".
3. The file is actually a configuration file used by the wifi kernal module/driver. In my case this file had become corrupted.
4. Set adb in root mode (won't work if the device does not have root access) by running 'adb root' at the command-line. You may need to click on an "allow root permission" window on the actual device after running this command.
5. Run 'adb pull /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb shell' from command line.
b. 'su'
c. 'cat /data/misc/wifi/wpa_supplicant.conf' - copy the output from the command and paste into a text editor (see note in step 6 on why NOT to use notepad).
d. Save the file as wpa_supplicant.conf, preferrably in the same diretory as adb.
e. 'exit' twice should exit you from the adb shell and return you to your command-line. If all else failes a "ctrl-c" should drop you out of adb.
6. Use a text editor to open wpa_supplicant.conf. The file should be located int he same directory as adb. If you are using Windows I would strongly suggest you NOT use notepad. Notepad will typically change all the EOLs (End Of Line) from \n to \r\n which will really mess things up worse.
7. In the file you should see "network={" entries. There maybe one entry, there maybe many entries. You can remove all lines between "network={" and "}" including the latter themselves. If you see your 'home' network listed you can leave it as the only entry and make sure its priority is set to 1 but it maybe better to remove it as well just in case it contains part of the corrupted data.
8. Save the file.
9. Do 'adb push wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb push wpa_supplicant.conf /sdcard/wpa_supplicant.conf' from command-line.
b. Run 'adb shell'
c. 'su'
d. 'dd if=/sdcard/wpa_supplicant.conf of=/data/misc/wifi/wpa_supplicant.conf'
e. Do 'exit' twice to exit the adb shell. If all else fails then a "ctrl-c" should drop you ot of adb.
10. If the wpa_supplicant file was corrupted then the wifi should now be able to enable and you should now be able to connect to a network.
I hope this is helpful to at least a few people.