I have it (ADB) installed, but can't get it to install Minuum Keyboard. I'm trying to sideload it via ADB but it keeps saying "can't find minuum keyboard to install".
Joe0113 said:
I have it (ADB) installed, but can't get it to install Minuum Keyboard. I'm trying to sideload it via ADB but it keeps saying "can't find minuum keyboard to install".
Click to expand...
Click to collapse
Are you trying to use the keyboard to write stuff in the google search? If not I don't know what you would use it for..
Anyways are you sure you have the needed permissions? That's the only thing I can think of why it would fail..
spiderflash said:
Are you trying to use the keyboard to write stuff in the google search? If not I don't know what you would use it for..
Anyways are you sure you have the needed permissions? That's the only thing I can think of why it would fail..
Click to expand...
Click to collapse
I figured it out I had the wrong path. It installed fine but it's in beta and has no use as of right now.
Sent from a Galaxy 5 light years away
Related
I modded an app from the market. Well its the facebook app and u can find it with a search for inverted facebook.
Well I can get it to flash and pushed through adb but when I'm trying to get to install like a 3rd party app off the SD card it says installation failed.
Does anyone know why and how to get it to work.
Papa Smurf151 said:
I modded an app from the market. Well its the facebook app and u can find it with a search for inverted facebook.
Well I can get it to flash and pushed through adb but when I'm trying to get to install like a 3rd party app off the SD card it says installation failed.
Does anyone know why and how to get it to work.
Click to expand...
Click to collapse
Install it through "adb install" or look into logcat. We can't know, what it is, if we don't know error message.
Brut.all said:
Install it through "adb install" or look into logcat. We can't know, what it is, if we don't know error message.
Click to expand...
Click to collapse
Gotcha. It installs via adb. It's the original app from the market I just modded it. Would I need to resign or compile the app in eclipse. I dont have the source code to compile . Ill have to log cat the app in a min a ill post.
Any way to get Swype without rooting?
Sideload with the HTC Sync from July (not the one thats available now). Search around and you will find it.
You could also just enable USB debugging mode on the phone and use the "adb install nameofswypefile.apk" command through the android sdk
Sent from my HTC Liberty using XDA App
Rwelch said:
Sideload with the HTC Sync from July (not the one thats available now). Search around and you will find it.
Click to expand...
Click to collapse
What is this?
HTCSync305372exe
http://www.4shared.com/file/v5zvg8G8/HTCSync305372exe.html
the easiest way to install 3rd party apps without rooting is droidexplorer.
http://de.codeplex.com/
i juss use SlideIT from the market i think its better then Swype
I installed swype using the "Android Central Sideload Wonder Machine" and it was a no brainer, and I am a total noob to all of this. Just google the name I typed in quotes. No need to fool with sdk.
so how do u install swype with a rooted aria?
i rooted last night, but have no idea how to install 3rd party apps or delete the at&t crapware.
I will say a couple of things that annoy me that people are saying about the kindle fire.Also some tips.
1.you dont need an external app to install apk files.When the apk is done downloading click the notifications,then the "download complete" notification.
2.you don't need an external app to change the input meathod.go to the kindle browser,click on the url, then hold down on the second bar that pops up and input meathod should be their.(You still need to install it a special way)
3.(for stupid people) you don't need root to install external applications(heard from youtube)
Wow the word "external" is used a lot
4.you can get swype from http://www.swype.com/category/get-swype/
5.It does not suck after you get root.
6.don't mod the framework-res file, or you will die unless you have TWRP or CWM touch.
7.the triangle of doom after installing TWRP is common. Click here for a fix: http://forum.xda-developers.com/showthread.php?t=1543121
Does the fire support swiftkey x tablet?
Also How do I enable swype. I have it installed and everything I just can enable it.
EDIT: Got it all figured out. Its not a hard task but yo make it seems like you can install keyboards the normal android way and you can't. People like you create these misconceptions.
ledd760 said:
Does the fire support swiftkey x tablet?
Also How do I enable swype. I have it installed and everything I just can enable it.
EDIT: Got it all figured out. Its not a hard task but yo make it seems like you can install keyboards the normal android way and you can't. People like you create these misconceptions.
Click to expand...
Click to collapse
Hey, I wasnt trying to say you can install it the normal way, I was trying to say you can switch keyboards the normal way.sorry about the confusion though. We are all family at XDA.
So I grab the ics keyboard app from google play.
https://play.google.com/store/apps/....android.inputmethod.latin.ice_cream_sandwich
Itinstalls fine. Launch it tells me it needs to be set up. Fine. I'd already gotten NookColor Tools since it lets you do this. Trouble is it doesn't see anything other than the 'stock' keyboard. I'm guessing ADB is going to be needed for this?
Edit: Solved. Used RootManager to move the apk over. Went with Jellybean instead. Same process as above except it worked.
You need to convert the keyboard to a system app.
neoman4426 said:
You need to convert the keyboard to a system app.
Click to expand...
Click to collapse
Lemme guess. ADB involved? I'd tried a different filemanager (root Explorer) and gotten the ics apk moved over and still nada.
Could probably do it with ADB, but I usually use Titanium Backup for that. Not sure if you need Pro to do that though. Might just have to reboot after moving the apk.
Got it done with jellybean keyboard. Same process dunno why one worked and the other didn't. Ah well.
Used RootManager to move the files from A to B.
Hi Folks, Hopefully this is the right place for this thread. I don't get over here very often so I'm guessing right now.
I wrote an app for my phone (Sprint Galaxy SIII) in Eclipse to control a IOIO (not terribly important to know for this question). I run the app in the emulator and it fires up just fine, but when I run it on my phone (with supposedly the same settings as the emulator--Android version, AP level, etc) it crashes on startup, saying "Unfortunately, <My App> has stopped".
Since it works in the emulator I can't track LogCat to check for errors, so I have no idea where to start looking for the cause. It only crashes on my actual device. My questions are as follows:
1) What would cause an app to work in the emulator but fail to start up in a device with (supposedly) the same settings?
2) Where can I go to look for errors on my phone (if possible) that might point me to the problem?
Thanks!
Matt
DerStrom8 said:
Hi Folks, Hopefully this is the right place for this thread. I don't get over here very often so I'm guessing right now.
I wrote an app for my phone (Sprint Galaxy SIII) in Eclipse to control a IOIO (not terribly important to know for this question). I run the app in the emulator and it fires up just fine, but when I run it on my phone (with supposedly the same settings as the emulator--Android version, AP level, etc) it crashes on startup, saying "Unfortunately, <My App> has stopped".
Since it works in the emulator I can't track LogCat to check for errors, so I have no idea where to start looking for the cause. It only crashes on my actual device. My questions are as follows:
1) What would cause an app to work in the emulator but fail to start up in a device with (supposedly) the same settings?
2) Where can I go to look for errors on my phone (if possible) that might point me to the problem?
Thanks!
Matt
Click to expand...
Click to collapse
Only log could tell you the possible reasons.
Install catalog and look for the error log
Sent from my A0001 using Tapatalk 2
Vivek_Neel said:
Only log could tell you the possible reasons.
Install catalog and look for the error log
Sent from my A0001 using Tapatalk 2
Click to expand...
Click to collapse
Thanks Vivek_Neel. I tried a couple of log viewer apps but they all require superuser access for use on Android 4.1+. I forgot to add it to my profile, but I currently have a Galaxy SIII running Android 4.4.2.
Any other suggestions? I'd rather not root my phone if I don't have to.
Thanks,
Matt
DerStrom8 said:
Thanks Vivek_Neel. I tried a couple of log viewer apps but they all require superuser access for use on Android 4.1+. I forgot to add it to my profile, but I currently have a Galaxy SIII running Android 4.4.2.
Any other suggestions? I'd rather not root my phone if I don't have to.
Thanks,
Matt
Click to expand...
Click to collapse
Running the app on your phone with it plugged in to a pc and eclipse open should mean that eclipse catches the log, no root access needed, you would need to allow adb debugging though. If it doesn't work with eclipse I know for definite that it works with Android Studio.
Jonny said:
Running the app on your phone with it plugged in to a pc and eclipse open should mean that eclipse catches the log, no root access needed, you would need to allow adb debugging though. If it doesn't work with eclipse I know for definite that it works with Android Studio.
Click to expand...
Click to collapse
Eclipse doesn't seem to recognize my phone. It only brings up the emulator as an available device. Perhaps I should dig more into the cause of that first. You're saying if I load the app on my phone while connected to the PC it'll still show up in the logcat? That would be a huge help if that's the case!
DerStrom8 said:
Eclipse doesn't seem to recognize my phone. It only brings up the emulator as an available device. Perhaps I should dig more into the cause of that first. You're saying if I load the app on my phone while connected to the PC it'll still show up in the logcat? That would be a huge help if that's the case!
Click to expand...
Click to collapse
It should do - worked this way around a year ago when I was using eclipse myself before jumping ship to AS.
You might want to handle uncaught exceptions and either debug, write to a file or what ever is the best way for you.
You can see an implementation example for handling uncaught exceptions here: http://stackoverflow.com/questions/8943288/how-to-implement-uncaughtexception-android.
Please note that some crashes are not caught using this technique so you'll need to use the above mentioned methods to view logcat.
If you have root on your device, install a logcat viewer application. most likely that filtering the display by your package name (or parts of it) we'll lead you to the error cause.
Thanks everyone for the help, I have found the solution. Eclipse wasn't recognizing my phone because apparently the driver was no longer installed (I thought I had installed it a long time ago, but that must have been on my laptop--I'm on my desktop now). I installed it and Eclipse found the phone no problem. I loaded the app while watching LogCat and found the following:
java.lang.SecurityException: Need BLUETOOTH permission: Neither user 10211 nor current process has android.permission.BLUETOOTH.
Click to expand...
Click to collapse
Well that was embarrassing! Added the Bluetooth permissions to the app et voila! The app works just fine.
Thanks for your time!
Matt
DerStrom8 said:
Thanks everyone for the help, I have found the solution. Eclipse wasn't recognizing my phone because apparently the driver was no longer installed (I thought I had installed it a long time ago, but that must have been on my laptop--I'm on my desktop now). I installed it and Eclipse found the phone no problem. I loaded the app while watching LogCat and found the following:
Well that was embarrassing! Added the Bluetooth permissions to the app et voila! The app works just fine.
Thanks for your time!
Matt
Click to expand...
Click to collapse
:laugh::laugh:
Haha glad you got it sorted!