Related
Just a quick note to everyone who is constantly switching between ROM's with their 'daily driver' phone.
Make sure all of your apps are backed up using Astro or AppControl. They will be backed up to /sdcard/backups/apps.
Once your new ROM is installed, and your phone has been wiped, mount your SD card on your PC.
Open a command prompt and navigate to the \backups\apps folder on your SD card.
(this assumes that your adb.exe is in your PATH)
In the command prompt, type in:
for %%f in (*.apk) do adb install %%f
Watch all of your apps install! This really saves a lot of time over using Astro or AppControl to re-install all of your apps.
Absolutely brilliant!
I've done this dozens of times over the last couple weeks. I felt so dumb finding this little snippet of code after manually installing 100+ apps every time I wanted to try a new ROM.
Huh, how about a script to back up via adb? Or backup/restore app data?
Actually, the latter is far more important =P.
I think easy backup restore is with astro file manager...
SpaceBoy2000 said:
Huh, how about a script to back up via adb? Or backup/restore app data?
Actually, the latter is far more important =P.
Click to expand...
Click to collapse
That's more difficult since the data is stored in a DB inside Android (for most apps, anyway). I noticed there is a sqlite3.exe inside the Android SDK so I assume you can query the DB using that and extract certain data, for example SMS and call history, just need to invest a bit of time reading up I think!
Hey this took me a few hours but its relatively simple. you'll need a little knowledge of DOS or maybe i'll just spell out everything for the noobs being that i'm one. IF YOU HAVE MANUALLY INSTALLED FROYO AND THE OPTION TO MOVE APPS TO SD IS STILL GREYED AND CAN'T BE SELECTED JUST DO THIS.(i'm running windows vista)
1. download and install the android sdk (unzip folder on desktop for easy access)
2. go to my computer then click on C:\ create a new folder here called android
3. go back to the sdk folder on the desktop then open it and go to tools
4. copy the contents of the tools folder to the android folder u just created
5. connect your phone in debug mode if u don't know how to do this go to settings then applications then developement then enable the usb debugging.
6. after doing that you should be prompted to install the drivers 3 will install automatically and one will fail once that one fails select "I DON'T HAVE DISC" then browse for drivers go back to the desktop where u have the android-sdk-windows folder, then go to the usb drivers folder and press ok the adb utility driver should now install. you will also be prompted to reboot the computer in order to access it do so.
7. once rebooted connect ur phone in debug mode again. it should connect smoothly. Now open up a command prompt.
8. From here you'll need to set the path to the android folder to get access to the adb commands do this by typing "path=c:\android" to test it just type adb and you should see all sorts of crap comming up in dos if that happens ur golden.
9. Now all u do is type adb shell you should now see this sign "$" if that happens ur golden now just give the command "pm setInstallLocation 2"
10. you should see the message pm setInstallLocation 2 after which the dollar sign will appear again.
11. exit then reboot you phone and UR GOOOOOD
7
Has anyone else tried this? I assumed that the apps had to support copying to SD in order to work, but Last.FM and a few other apps I have updated to 2.2 support today, and yet I still can't copy them to SD.
xSiraris said:
Has anyone else tried this? I assumed that the apps had to support copying to SD in order to work, but Last.FM and a few other apps I have updated to 2.2 support today, and yet I still can't copy them to SD.
Click to expand...
Click to collapse
i updated to froyo last night and i have been trying to move the apps to sd but it was all greyed and couldn't be selected. i finally figured it out about an hour and a half ago after reading up on adb and stuff i decided to give it a test run cuz what ppl were saying about the apps didn't make any sense. so i tried that and VOILA worked like a charm let me know if it works for u. it did just fine for me
Apps to SD works fine with stock Froyo. The developer just has to support it. One app that does support it that I have found so far is "Armadillo Roll".
After you install, go to manage applications and you will see that the "move to SD" is not grayed out and you can in fact move it over with stock froyo.
thats a way around it man screw the developers
lordvikon said:
thats a way around it man screw the developers
Click to expand...
Click to collapse
have you rebooted your phone yet?
Well, this has been discussed in a couple of threads before, and yeah, it's a working workaround...
pm is the the package manager application which install apks.
installLocation is a parameter which has 3 values...
0 - auto (phone or app decides where to install)
1 - force internal (forces apps to install in the internal memory)
2 - force external (forces apps to install on the sd card)
So, in short, in adb shell or a terminal enumlator, if you type
> pm setInstallLocation 2
all apps will be forcefully installed on the sd card, and you can move them to the phone.
But be careful, if you install widgets and some other aps which run as background processes, they will be killed if you mount ur sd card.
Also, if you have an apk file, u can force install that to the sd card via the adb install command without performing any of the above steps.
> adb install -s AppName.apk
-s forces the app to be installed on the sd card, without that flag, the phone or app will decide where to the app will be installed...
craigacgomez said:
Well, this has been discussed in a couple of threads before, and yeah, it's a working workaround...
pm is the the package manager application which install apks.
installLocation is a parameter which has 3 values...
0 - auto (phone or app decides where to install)
1 - force internal (forces apps to install in the internal memory)
2 - force external (forces apps to install on the sd card)
So, in short, in adb shell or a terminal enumlator, if you type
> pm setInstallLocation 2
all apps will be forcefully installed on the sd card, and you can move them to the phone.
But be careful, if you install widgets and some other aps which run as background processes, they will be killed if you mount ur sd card.
Also, if you have an apk file, u can force install that to the sd card via the adb install command without performing any of the above steps.
> adb install -s AppName.apk
-s forces the app to be installed on the sd card, without that flag, the phone or app will decide where to the app will be installed...
Click to expand...
Click to collapse
so far so good! Thanks for the tip!
Used with adb but I understand you to mean this command will work using terminal emulator app? this would be an easy way to control which apps go to the sd card.
Thanks again for the original post and the clarification. I do love Android and Froyo is rockin' more every day!
help
I downloaded a terminal app and typed
pm setInstallLocation 2
And the dialog gives me an explanation of what the 0 1 2 is and dosen't move the apps. What am I doing wrong?
Ah, this actually works. You have no idea how it feels to move those space hungry navigation apps to the sd card. Perfect!
Thanks!
Awesome! It works, now I can install more games that take up way too much space
Thanks!!
How did you guys do it, I tried with a terminal on the phone but no dice. Did I do something wrong?
glwinkler said:
How did you guys do it, I tried with a terminal on the phone but no dice. Did I do something wrong?
Click to expand...
Click to collapse
Erm, I just followed instructions. I'm on unrooted N1 with Froyo.
Remember to reboot your phone for it to take effect. As Froyo categorizes apps in the application manager, you can tell which apps are installed on sdcard straightaway.
Only downside is once this takes effect, all future apps that you install will immediately be installed to your sdcard. May screw up apps that have background tasks or widgets.
lordvikon said:
thats a way around it man screw the developers
Click to expand...
Click to collapse
disgusting comment.
Without the developers you would have nothing. NOTHING.
Don't do this, you're gonna end up with malfunction applications and then you're gonna get pissed at the developers for your own stupidity.
As i have written on my blog, you need to be aware of a few things:
"Don’t move apps that require a background service running all the time. Things like twitter, widgets, streaming apps (internet radio) and IM apps (you need the notifications even if you use the SD card for something else) should stay on the internal storage because they will break when you’ll use your sd card as a mass storage on your PC.
All the apps you’re going to install from now on will default to the SD card. In case you know for sure that the app uses a background service we advise moving it to the phone’s internal storage."
What you can do is to enable this trick, move all the apps you want to the sd card and reverse the trick so all your future apps will default to whatever setting they have.
lordvikon said:
Hey this took me a few hours but its relatively simple. you'll need a little knowledge of DOS or maybe i'll just spell out everything for the noobs being that i'm one. IF YOU HAVE MANUALLY INSTALLED FROYO AND THE OPTION TO MOVE APPS TO SD IS STILL GREYED AND CAN'T BE SELECTED JUST DO THIS.(i'm running windows vista)
1. download and install the android sdk (unzip folder on desktop for easy access)
2. go to my computer then click on C:\ create a new folder here called android
3. go back to the sdk folder on the desktop then open it and go to tools
4. copy the contents of the tools folder to the android folder u just created
5. connect your phone in debug mode if u don't know how to do this go to settings then applications then developement then enable the usb debugging.
6. after doing that you should be prompted to install the drivers
7
Click to expand...
Click to collapse
Done step 1-5 and when i connect phone i dont get prompt to install drivers???
Please help
This worked like a charm, just gotta remember it when I install new apps (or revert it)
glwinkler said:
How did you guys do it, I tried with a terminal on the phone but no dice. Did I do something wrong?
Click to expand...
Click to collapse
If you want done from terminal, you need root(su). or use ADB save you from trouble.
The only issue with this method is market lost most of downloaded apps link after reboot the phone. Untill you install or upgrade any apps, then the link will refresh.
Use AppBrain check for any update first, then only need install one update. Go back to stock market, everything come back.
BTW: leave phone idle for 1 min after start the phone, otherwise some apps(home screen or app draw) will show default Icon. Phone need time to refresh the apps from SD.Hope next android release can mount SD before phone try to search for Apps(Like the APP2SD on root).
I just want to give props to a program for windows called Android Commander. I am not sure if its been mentioned on the Vibrant forum yet, but it got me out of a major jam today.
Android Commander is basically ADB with an easy to use interface. It lets you pull and push files to and from your pc to your Android device.
Story:
I tried to MM the Androdena theme but it seems the framework was corrupted and caused me to keep me in a forceclose loop not letting mount or boot or really do anything. I did make a nandroid backup but some how deleted the CW update zip from my sd at an earlier date and could only boot up into the stock recovery. I was ok with having to reflash the stock rom using Odin, but needed some important pictures that I took for work. Needless to say I starting freaking out. I have ADB set up but only know a few basic commands and I'm sure what I needed to be done could have been done from there. I started searching for solutions on Google and found this awesome program.
I was first able to move the picture folder from my sd card to my pc, then move and rename the CW update.zip to root of the sd card in turn letting me boot into CW recovery and restoring my nandroid.
The only thing I needed to do was to make sure my device was online through ADB and Android Commander was able to find the device and show me all my files and such. Its a great program, and I highly recommend it if you are not familiar with ADB.
I will need to check this out when I get home. I want an easy way to remove the bloatware on my phone.
it seems like an interesting program, and would be good, but for me it doesn't show that i have root. it tells me "root no" and when i use the console in it and use the su command it tells me no. but still a good program over all, i did some looking around and i believe it will only show you have root access if you have an APP2SD installed. i might be wrong with that, but atleast if anyone else has the same trouble with it please let me know if you figure a work around.
ps, you can view root files and folders just not push or pull anything from them.
Yep, I am seeing the same thing.
I did some research on Google and this is what I came up with:
"adb remount and adb root are protected commands and need either a rooted kernel or a flashed recovery model to run" - Source: Rastaman-FB
ah I see. That's good to know. I guess ill be sticking with just the normal ADB. But I think the program will still be very useful for other stuff considering we don't have to mount the USB so no rescan media after the unmount. That alone is a keeper for me. Thanks again for the information pal.
Sent from my SGH-T959 using XDA App
I must say
I have been using android commander since his 1st beta on all my android rooted phone..
It is the best android tool Out there.
Im usually private about the tools I use but
Android Commander (By PanPiotr) is the best and easiest adb GUI tools out there.
Features
Explore files:
- copy multiple files/dirs between Phone and PC
- copy multiple files/dirs between Phone folders
- delete multiple files/dirs from Phone
- new dir and rename options
- drag&drop multiple files/dirs in to progrm
- drag&drop files/dirs between program tabs
- partitions size info
- bookmarks
Manage apps:
- windows integration
- backup multiple apps to any dir on Phone/PC
- batch/single apps install
- install as private
- update
- batch/single uinstall apps
- uninstall with option to keep data or not
Console:
- type any shell command
- run sh script from PC
and more…
- flashing zip and img files
- options to reboot, reboot to recovery, reboot to bootloader, power off phone
- screenshots (beta)
Stupid question. I accidently deleted my update.zip file and I attempted to reflash another rom. Of course now I'm stuck at the Vibrant Logo and tried to use this app. It says its trying to connect, but never does. I have SDK installed, but I think its the version from when I was tinkering with the G1.
I got into Download mode with the BIG yellow triangle, but my PC never seems to show anything connected via USB unless I try connecting via Recovery.
This app sounded like something would help me since I'm not very good at ADB, but I guess I'm having issues getting over the first hurtle is seems. LOL
Qverse said:
I have been using android commander since his 1st beta on all my android rooted phone..
It is the best android tool Out there.
Im usually private about the tools I use but
Android Commander (By PanPiotr) is the best and easiest adb GUI tools out there.
Features
Explore files:
- copy multiple files/dirs between Phone and PC
- copy multiple files/dirs between Phone folders
- delete multiple files/dirs from Phone
- new dir and rename options
- drag&drop multiple files/dirs in to progrm
- drag&drop files/dirs between program tabs
- partitions size info
- bookmarks
Manage apps:
- windows integration
- backup multiple apps to any dir on Phone/PC
- batch/single apps install
- install as private
- update
- batch/single uinstall apps
- uninstall with option to keep data or not
Console:
- type any shell command
- run sh script from PC
and more…
- flashing zip and img files
- options to reboot, reboot to recovery, reboot to bootloader, power off phone
- screenshots (beta)
Click to expand...
Click to collapse
I'd say it's ok at best. I don't know of any other ADB GUI tools but this one doesn't work well with my Vibrant.
StrayPanda said:
I'd say it's ok at best. I don't know of any other ADB GUI tools but this one doesn't work well with my Vibrant.
Click to expand...
Click to collapse
I'm going to have to agree with this. Is nice to have but doesn't play nice with the vibrant.
Sent from my SGH-T959 using XDA App
It sometimes is very slow in reading internal sd memory on samsung vibrant and it loads up as a blank screen. Disconnecting usb cable and refreshing does the trick for me.
Sent from my SGH-T959 using XDA App
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Background:
It all started with me often finding myself sending small files to my device, and quickly got sick of the constant enabling/disabling of USBMS on my old phone, which is quite slow with re-mounting the SD card(ZTE Blade).
I also quickly got sick of not being able to quickly transfer files from my PC to my tablets internal storage.
There are a few graphical interfaces for adb out there, but none was really what I wanted...
So I decided to attempt to code something myself, and here we are!
Info:
A graphical UI for "adb push" to quickly transfer files from your PC to any location on your Android device.
.... Thats what I planned when i started, and what the first 2 versions did...
Now it hosts a powerful File Explorer thats capable of doing everyday tasks such as copy, paste, rename, create folders, delete files and folders, as well as transfering files on its own.
Features:
The main application is capable of sending and receiving files, and installing APKs.
It also serves as the connection-manager as can connect to devices using either your USB Sync cable, or by using WLAN (req. an app on your device to enable wireless adb).
Finally, it hosts a few other functions such as reboot to recovery, reboot to bootloader and a plain reboot.
The Filebrowser is very similar to any other filebrowser you use everyday on your PC.
It can copy/cut and paste files and folders within the device, rename file and folders, create new folders, delete files and folders.
Highlights would be:
Browse the content of your device like you browse your PC's harddrives
Drag and drop files between your PC and your Android device
Move, copy, delete and rename files and folders
Limitations:
The main program does not detect case sensitive, which can end up with funny results if you push a file to "/removable/" instead of "/Removable/" for example.
ADB is only capable of sending 1 file at a time, but is capable of sending whole directories incl. subdirs.
In a future update, I will add the ability to send multiple files.
Getting started:
Everything should be self explanatory. Most of the buttons have tooltips that tells you what they do.
Basically you make sure USB Debugging is turned ON on your device, plug it into your PC and start Quick ADB Pusher.
If you are connecting using a USB Cable, the application should find it automatically.
If you're connecting through wifi, you will need to type the IP address in the dedicated field. Port only needs to be provided if you are using any other port than the standard 5555. The IP address will be saved, and you can select it from the drop-down list the next time you start the application.
Requirements:
An Android device.
Windows
.NET 3.5
USB Debugging turned ON.
Additional Recommendations:
Root
Busybox
Vulnerable Kernel or Custom ROM
Q&A
Q: My device is rooted, but the program says it cant get root access
A: You are probably on stock rom or kernel. Most shipped roms have root-access from adb blocked.
To check this: Open default.prop located in the root of your device ("/"). If ro.secure is set to 1, thats your issue. Note: Default.prop gets overwritten everytime you restart the device, so changing this file will do nothing.
Theres is an app available that can fix/bypass this: http://forum.xda-developers.com/showthread.php?t=1687590
Q: The cache didnt delete itself when I closed the app!
A: You have two choices here: Either delete the cache/ folder located in the same location as the adb pusher exe, or you can just open and close the program.
If the cache still wont delete itself, report it as a bug.
Q: I cant connect to my device over wifi!
A: Make sure you have an app on your device that enables wireless ADB and that its turned ON. I personally use adbWireless found on the Play Store.
Double-check you are attempting to connect to the correct IP and port.
Q: Whats the "Information" window good for?
A: Its actually a left-over debug window, but can provide you with useful information should a transfer fail. If nothing else, you can use it if and when you report a bug.
Note that the Info window only shows what the main program is doing. ADB Explorer works independently, and will not report anything to the Info window.
Q: Why do I have to click a button to switch between push, pull and install?
A: The program need to knows which adb command to run (adb push or adb pull), and having a button for it was the easiest way for me .
The install option is there because you might not always want to install an .apk, but rather store it on your SD card or something. I know I do.
Q: Why cant I send a whole folder to my device from the main program?
A: Old implementation, use the built-in ADB Explorer instead, which allows you to send whole folders.
Q: Whats the point in the main program, when the Explorer can do everything but better?
A: At the moment it still controls the actual transfers as well as the connections to your device(s).
The main program is, however, more or less untouched since v0.3, while the Explorer is constantly being updated. Therefore, the Explorer hosts more and better features.
I am concidering removing the main form, as its rather obsolete by now.
Q: I Have a question!
A: Feel free to ask in this thread, and I'll answer your question as best I can.
Q: Can I donate?
A: No, I dont feel this program is worth "paying for" and it wouldnt feel right to receive money for it in any form.
Hit 'thanks' and vote the thread 5stars instead
Q: I Found a bug, how do I report it?
A: Report it to me on this forum, either in the thread or through PM, and I'll make sure to look into it.
Just make sure to provide as much info you can.
And remember: I cant fix anything if I dont know about it! So dont hesitate reporting bugs.
Changelog:
v0.5 current version
First of all... v0.4.1 had 6570 views on the attachement alone. Not bad... :victory:
Added an awesome splashscreen! As those who have used this program before should know - the program takes a while to load. The splashscreen is visible during this load, so you know the program is actually starting.
The wifi-field has been redesigned. It now saves your IP adresses so you dont have to retype them every time.
Added an "X" button next to the wifi-field. This button clears the wifi-cache and removes all entries in the list.
Added my name with a link to this thread, Ive seen my program hosted at a few sites with no credit whatsoever. I dont mind anyone hosting it elsewhere, in fact Im happy it gets spread, but PLEASE at least give me credit for it.
Slight redesign
Added tooltips to both the main application and the Filebrowser
Filebrowser:
Renamed "ADB Filebrowser" to "ADB Explorer". It can do so much more than just view the files on the device, so this name is more fitting. I should think of a new name for the entire application as well... "Quick ADB Pusher" isnt even half the truth anymore
Added cache feature! Everytime you enter a directory youve already been in, the cache kicks in rather than asking the device for the content. Each device has its own cache (note: a wifi-connected device will have its own cache based on the IP, so if you connect to the same device using cable or another IP, the cache needs to be rebuilt).
The cache will update as follows:
When entering a new directory not currently present in the cache.
When you hit the refresh button.
When you rename a file/folder.
When you create a new folder.
When you paste a file/folder from the clipboard.
When you delete a file/folder.
When you transfer a file/folder to the device.
The cache will NOT update when you send a file from the device to your PC
The cache will get deleted upon application exit.
You can now cancel the contentlisting and go back by hitting "../", Backspace shortcut-key or the Back button. Added because some directories takes ages to load on various devices, and its not so fun rolling your thumbs when all you want to do is go back to the previous dir
Added "drag-drop" to the filebrowser - you can now dragdrop files and folders directly to the browser to send it(or install, if .apk) to your device. The cache will refresh upon completion. You can also drop files and folders FROM the browser to your PC!*
* this might not sound so special, but it was a ***** to implement. Dragging stuff to the browser - ~50 lines of code. Dragging stuff FROM the browser - a little over 200 lines of code... C# sure has its limitations...
Added "Grab" to the right-click menu. This will send the selected file/folder from your device to your PC.
In short, the filebrowser can do what the main application can, so you dont have to close the browser to send/recieve a file/folder. A loading thingy will appear over the browser while a filetransfer is in progress.
Added "Properties" to the right-click menu. This shows some info such as the size of the file, and even the total size of a folder (incl. sub dirs). If you select a folder with a lot of content/folders, it might take a while to calculate the size. Other things it show is where its mounted and what permissions the file/folder has. NOTE: Requires Busybox, and root for files and folders only accessible by root (duh!)
Added 3 warnings upon opening the browser: One to inform you if your device isnt rooted, one to warn you busybox is missing and one to warn you if your device is rooted, but ADB was unable to acquire it. None of these warnings will show if adb acquires root and busybox is present.
Added a textarea showing the used space on the device, based on the mounted partition (such as /data, /sdcard, etc). So dont be scared if the number jumps around while youre browsing - it just means youve entered a different partition. Click to switch between used and free space. Requires Busybox
The browser now remembers your last location and will not start from "/" everytime you open it. Memory is lost upon main program exit and when you select a different device.
Added "View file" (prev. unfunctional "Open" menu item) to the right-click menu. This allows you to view smaller files (up to 10MB) without permanentally save them on your PC. I have blocked larger files because the time it takes to transfer those files isnt worth it for just "a quick look". My devices transfers a 10MB files between 2 and 5 seconds(depending on device) - which I think is ok, so I set the limit there.
Tweaked and tuned to make the browser act somewhat normal for devices without root/busybox. Devices without root/busybox will miss out on quite a lot though And before anyone asks - No, I do not plan on making this program able to root your devices. There are plenty of tools for that already.
Fixed the shortcutkeys that only worked when they wanted to. In addition, several more shortcuts have been added.
List of currently supported shortcuts:
ctrl+x: Cut file/folder
ctrl+c: Copy file/folder
ctrl+v: Paste file/folder
ctrl+s: Grab the selected file/folder
shift+delete: Delete the seleceted file/folder
shift+n: Create a new folder
F1: View file
F2: Rename file/folder
You can also use the arrowkeys to navigate, similar as in explorer. cut/copy/paste only works within the ADB Explorer.
Added Forward and Back buttons. Works the same way ordinary back/forward buttons do. Also changed icon for Refresh
Added a Toolbar, containing more buttons such as "view file", "download", "upload", "delete"...
Added 2 eastereggs , one is easy to find. The other is well hidden, and actually serves a purpose Well actually, the latter isnt really an easteregg, but it should be hard enough for you mortals to find
Known issues:
You friends might rage and throw their IPhones at you when they see this
------
HTC Sync REALLY doesnt like ADB, so close that crap before starting this app, or better yet - uninstall it!
It seems HTC Sync is trying to start its own adb server, and is very persistant in doing so.
This results in Quick ADB Pusher and HTC Sync having a fight for their life on who is going to start the server.
------
If you install an .apk, then try to send something else, the program will try to install that as well. This is because I was retarded and forgot to add one check.
Solution: Close the filebrowser, untick "install apk". Will be fixed in the next version, I promise! :angel:
Version History:
v0.4.1 - 6570 views on the attachement alone. Not bad...
Fixed filebrowser not working on some devices, I hope. Please test this for me as the browser has always worked fine for me on all my devices.
Changed apk install method to use AndroidLib's method. It now tells you if the installation was successful or not.
... Some minor things I cant remember.
Note, the "Open" option in the filebrowser is just a placeholder for now, its not a bug that it doesnt work, it isnt ment to work.
v0.4
Fixed bug where files and folders containing "_(" threw a syntax error.
Added file browser for device (see Seperate notes).
Added wireless ADB support.
Added Pull-file mode.
Re-designed the UI.
Moved the info-view to 3rd tab. Im moving away from it more and more.
A lot of the text and button-text will now change depending on your current choices. Ex. the Send-button now switches between Send, Pull and Install.
A truckload of code rewriting and optimizations.
Added an additional check for Root remounting, which should fix rare cases where remounting fails (If your device cant be remounted as root, please report it along with your device, rom etc)
Added "Install APK" You can now install APKs directly through the program.
Added reboot options in the Advanced tab
Added device info in the Advanced tab (The temp seems to be reported in C * 10, so I report it as C / 10, let me know if it doesnt look right for your device, and dont forget to tell me what device/rom you're using)
Filebrowser Features:
Browse and select files.
Context menu (right-click menu).
Copy or move(cut) files/folders within the device.
rename files/folders on the device.
delete files/folders on the device. Warning: Deleting the wrong files might brick your device! Double-check that you really want to delete the file before doing so!
create new folders on the device.
icons for certain formats (more to be added).
progressbar for directory loading progress.
'clipboard' icon to remind you what you currently have selected for copy/cut.
Notes:
The filebrowser is in its early stage. I have bugtested it as much as I can and it works flawless with my 3 devices.
The speed of listing directoiess/files greatly differs with device. My TF101 lists the contents about twice as fast as my ZTE Blade, theres not all that much I can do about it, as I dont have the time right now.
When pasting a file in a location where a file with the same name already exists, the program will currently simply overwrite the file. I havnt had time to add a check for it yet (ETA: Next version).
---To be added:
Direct interacting/editing of files, such as text files etc.
cache-feature, to reduce the frequency of grabbing the dir. contents from the device (which will help speed up changing paths).
A "file exists" check when pasting, allowing you to chose to overwrite or rename the old file.
v0.3
Fixed program freeze when no device was connected.
Added device selection, so it should work with multiple devices connected. please test this for me
Rewrote most of the program to make use of AndroidLib.dll
Removed the console(debug) tab, as it served little to no use now
Added an 'Advanced' tab for future use
Cleaned up a lot of garbage code
Fixed system not mounting as R/W
Other minor changes and fixes
v0.2
First public release
v0.1
very first version I wrote, which was buggy and often froze and god knows all...
Trust me, it was terrible. It worked and did what it set out to do but... It was terrible...
The latest Version has been tested and bugfixed on the following devices:
ZTE Blade with Swedish Spring 5, connected through USB Cable
ASUS Transformer TF101 with Team EOS Nightly build 28, connected through WIFI
HTC One S with stock 4.0.3, no root, no busybox. USB Cable
HTC One S with stock 4.0.4, root, no busybox. USB Cable
HTC One S with stock 4.0.4, root, busybox. USB Cable.
-------------------
Suggestions for improvements, feedback etc are more than welcome
Thanks to:
regaw_leinad - for writing the very handy AndroidLib found here
Dont forget to hit 'thanks' if you like my application. Every thanks I get brings a smile to my face
Download:
If the attachment doesnt work, try this mirror (select version and hit ctrl+s, or file -> download)
i think making a batch file was easier
Hey, cool app. There does however seem to be a problem with XDA's attachment feature, and it only downloads about 1k of the zip, then says complete. Also, if you plan on extending this a little more, check out my .NET Android Library named... well AndroidLib. It will help you out a bunch with the coding of the features you want to add.
regaw_leinad said:
Hey, cool app. There does however seem to be a problem with XDA's attachment feature, and it only downloads about 1k of the zip, then says complete. Also, if you plan on extending this a little more, check out my .NET Android Library named... well AndroidLib. It will help you out a bunch with the coding of the features you want to add.
Click to expand...
Click to collapse
Thanks for the heads up.
I placed it on google docs, hopefully it works better
Linky
If it doesnt, perhaps you could give me a tip as to where to upload it. I used to have my own server so never really used any other file-sharing method
regaw_leinad said:
Also, if you plan on extending this a little more, check out my .NET Android Library named... well AndroidLib. It will help you out a bunch with the coding of the features you want to add.
Click to expand...
Click to collapse
O nice, Ill definitely check that out Thanks.
Goatshocker said:
Thanks for the heads up.
I placed it on google docs, hopefully it works better
Linky
If it doesnt, perhaps you could give me a tip as to where to upload it. I used to have my own server so never really used any other file-sharing method
O nice, Ill definitely check that out Thanks.
Click to expand...
Click to collapse
Yup, the new link works great! Unfortunately, when I don't already have an adb server running and hit the 'Check ADB Status' button, the form freezes and the process needs to be killed to close the program. Works fine when adb.exe is already running though.
---------- Post added at 12:26 AM ---------- Previous post was at 12:17 AM ----------
Killing adb.exe while it's frozen fixes the issue I pointed out, probably means there is an error in your
Code:
Process
code
EDIT:
Stalls on process.WaitForExit() when debugging
regaw_leinad said:
Yup, the new link works great! Unfortunately, when I don't already have an adb server running and hit the 'Check ADB Status' button, the form freezes and the process needs to be killed to close the program. Works fine when adb.exe is already running though.
---------- Post added at 12:26 AM ---------- Previous post was at 12:17 AM ----------
Killing adb.exe while it's frozen fixes the issue I pointed out, probably means there is an error in your
Code:
Process
code
EDIT:
Stalls on process.WaitForExit() when debugging
Click to expand...
Click to collapse
Thanks for the report,it seems to happen when theres no device connected. Silly me have only even tried the app with a device connected hehe.
I'll try to fix it later today
Goatshocker said:
Thanks for the report,it seems to happen when theres no device connected. Silly me have only even tried the app with a device connected hehe.
I'll try to fix it later today
Click to expand...
Click to collapse
ah, you're calling
Code:
adb get-state
that gets the state of the device connected.
My .NET Android library handles everything adb wise, it even uses it's own adb binary, so the user doesn't have to have the sdk for it to work. let me know if you're going to reference it with your app, and I'll put your project in AndroidLib's post of "Projects using AndroidLib"
regaw_leinad said:
ah, you're calling
Code:
adb get-state
that gets the state of the device connected.
My .NET Android library handles everything adb wise, it even uses it's own adb binary, so the user doesn't have to have the sdk for it to work. let me know if you're going to reference it with your app, and I'll put your project in AndroidLib's post of "Projects using AndroidLib"
Click to expand...
Click to collapse
Yep, I assumed that would work since it works fine if you do it directly in cmd. But guess not adb start-server didnt work either...
I think I'll leave the bug for now and start looking into your lib instead.
Really nice app
Do you plan to develop a Linux version ?
Great idea, thanks =)
How does it achieve rw access, since device-dependent?
For example, on some devices, in ADB shell, you use
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
But, in some, you use mtdblock3 instead of mtdblock0.
Since there's no setting on which mtdblock to use, how does the program know which one is correct?
Theonewithideas said:
How does it achieve rw access, since device-dependent?
For example, on some devices, in ADB shell, you use
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
But, in some, you use mtdblock3 instead of mtdblock0.
Since there's no setting on which mtdblock to use, how does the program know which one is correct?
Click to expand...
Click to collapse
adb remount does all the job as you are ultimately using adb..
the command which you specified is used to mount on device shell which you enter by adb shell
madman_amit said:
adb remount does all the job as you are ultimately using adb..
the command which you specified is used to mount on device shell which you enter by adb shell
Click to expand...
Click to collapse
Oh, so that's what it does! lol
Thanks.
Actually, when trying it out, it says, after starting daemon "remount failed, action not permitted"
Nevermind, will check the program, it seems easier...
Looks cool! I shall give this a try later and see how it does with my HTC Rezound.
Thank you for your work!
Wow, responses
Thanks for the feedback guys.
Unfortunely Ive kinda killed my sync cable for my TF (tried to convert it to a usb host adapter^^), and currently dont have any other android device to play with.
So development has kinda stalled right now. Ive got rid of the freeze-when-no-device-connected, but developed another issue instead. Not anything major, but very annoying. The app freezes while it checks for a device >_>, its only for a few seconds, but annoying nevertheless.
As for linux version... Im afraid thats way above my coding skills, and I dont have a linux PC to test on anymore (I killed the laptop which was running linux when I tried to build a touchscreen on it. Yes! I break a lot of things)
Awesome, just what I needed!
Could you please add an option to connect the phone using network?, with the "adb connect" command, I can use a bat file before starting the app but because I have several devices connected to the network the phone´s ip change in time, and having it built in the app would be great
Awesome work, just tried it out now and it's pretty awesome.
I think an adb connect option would be awesome, for those who have adb wireless app on there phone then it'll be really easy to transfer files and it'll be pretty sweet.
Anyway keep up the good work
Hey, just an fyi,
Code:
adb remount
will NOT work if the device connected does not have the option ro.secure=0 in the default.prop of the ramdisk. You shouldn't assume it does, because not all "ROM" developers know how to change it. My library does check for this, but in case you don't want to use it, be sure you can mount the filesystem /system as rw that way, or using the mount binary on the phone directly.
regaw_leinad said:
Hey, just an fyi,
Code:
adb remount
will NOT work if the device connected does not have the option ro.secure=0 in the default.prop of the ramdisk. You shouldn't assume it does, because not all "ROM" developers know how to change it. My library does check for this, but in case you don't want to use it, be sure you can mount the filesystem /system as rw that way, or using the mount binary on the phone directly.
Click to expand...
Click to collapse
Hey thanks for the info. I had no idea about that, remount have always worked on all my devices on all roms Ive tried.
I'll keep that in mind when Ive fixed my sync cable
Could you give an example of a device/rom combo remount does not work on?
Goatshocker said:
Hey thanks for the info. I had no idea about that, remount have always worked on all my devices on all roms Ive tried.
I'll keep that in mind when Ive fixed my sync cable
Could you give an example of a device/rom combo remount does not work on?
Click to expand...
Click to collapse
I can't think of a specific example, but if the developer does compile a boot.img with ro.secure=1, adb remount will not work but lots of 'devs' these days just grab the boot.img from people who actually know what they're doing, so you should be ok, just in rare cases, this will not work.
Hi,
Beep'nGo is not supported anymore.
But it's not clear what app could be used instead which would be compatible with preinstalled Beaming Service for Samsung.
Samsung Pay is not available World Wide. App even can't run if installed from apk.
What about other popular Loyalty Card apps? Which apps use Beaming Service?
Thanks.
Beep'nGo still working
I think Beep'nGo was the best loyalty card app. I have a Galaxy Note 3 and even though the app was discontinued earlier this year it still works on my Note 3. I can still add cards locally to the app and the beaming still works. I have been trying to figure out the file structure so that I can preserve the functionality in case something happens to the phone. I have searched the folders and I can't find a mobeam, beepngo or derivative naming file structure. So the question is how does it work. Where are the install files. Any ideas?
the app is still working ,sort of.
if its already installed, it works fine.
But ive just got a Note 8 & unable to use the app so far. Im gutted & I love this app. It works great all the time o my other devices.
I just cant log in at since installing the app.
I get an error 'you are not connected to the internet'. Ive tried all sorts with no luck.
I also tried to find the data file for the app, I found the file for it named COM.MOBEAM.BEEPNGO, then theres a sub folder named CACHE, but thats empy!
Im at a loss how to log in and get this app working on my new phone. Its frustrating as its perfectly fine on my S7 Edge, but I need to give that phone to my partner soon.
someone here must know something on this surely?
Im not in USA so cant use samsung pay or those affiliated apps
pinkbellbird, you can't logon becuse app is discontinued. Nowere to logon. No coud backup.
You can use it by adding new cards every time you reset to factory. Otherwise it's working.
I have Samsung Galaxy Note 3 and love that app, using it all the time. Also I use Titanium Backup for it and restore data every time I play with roms or reset to defaults.
Would like to know if there is alternative for this app that use beaming though.
Samsung Pay is the only other app that I have read of that includes the beaming tech.
As I do not have a Samsung at present, I would be quite interested to know if something is available for phones, at large, that incorporates the beaming tech.
If there was a way to make Samsung Pay work in my country.
Sent from my SM-N910C using Tapatalk
Beep n go on S8
I had the same trouble with my new S8. Just install the app sending it via Bluetooth from old to new phone and then scan the cards directly with new phone from old phone as it was physical card. Then installing widget on new phone you will bypass the logon error.
Still no one found a way to export the cards stored into discontinued Beep n' Go app so they can EASILY be imported into other apps like... Samsung Pay?
We find ourselves in the same position as you. The way I managed to solve the problem, now that I am one step away from making the change to a note 8 (from a note 3), it is to make a copy of the system and user data with the Note root and using the Titanium Backup, and the new phone will reload the Beep'N'Go program. With total reinstallations of Note 3 it has worked, I hope it also does note 8!
Steps to migrate BeepnGo including data from old to new phone
install ADB ( developer.android.com/studio/command-line/adb ) on your PC
Open cmd window in the folder where ADB is located
on old phone: enable USB debug option in developer options
connect old phone to PC ( watch for question popups on phone and answer them)
check if phone is visible to adb : adb devices
commands:
adb backup -apk com.mobeam.beepngo ( watch for question popups on phone and answer them, if your phone is encrypted it will ask for a password (use simple password like the letter 'a' . This command will create a file backup.ab in the current folder)
[the previous command should have backed up the apk as well. However on my phone this did not work so we need some more steps to copy the apk too:]
adb shell
pm list packages -f | grep mobeam
will show the path where the application is stored (in my case:
package:/data/app/com.mobeam.beepngo-2/base.apk=com.mobeam.beepngo )
copy the apk to a folder which is visible on PC:
cp /data/app/com.mobeam.beepngo-2/base.apk /storage/self.primary/Download/beepngo.apk
exit
(you are back at the normal cmd window prompt, don't close the window yet)
Now on PC open windows explorere, navigate to your phone devices Download folder and copy beepngo.apk to a folder on PC
Disconnect old phone
on new phone: enable USB debug option in developer options
Connect new phone (watch for question popups on phone and answer them)
Copy beepngo.apk to the Downloads folder of the new phone
On phone use file manager, navigate to Downloads folder and run the beepngo.apk to install beepngo
On PC go to the command window:
check if new phone is visible to adb : adb devices
adb restore backup.ab (this will restore the beepngo files, watch for popups on your phone and answer quesitons. if you had to enter a password for encryption, please enter the same password again )
Start beepngo and the data from previous phone is visible
:laugh: :victory: :laugh: :victory: :laugh: :victory:
OH MY GOD!!! IT WORKS!!!!!
so I will not have to root the new note 8! Thank you very much! Really !!!!
:laugh: :victory: :laugh: :victory: :laugh: :victory:
MisterKosmos said:
install ADB ( developer.android.com/studio/command-line/adb ) on your PC
Open cmd window in the folder where ADB is located
on old phone: enable USB debug option in developer options
connect old phone to PC ( watch for question popups on phone and answer them)
check if phone is visible to adb : adb devices
commands:
adb backup -apk com.mobeam.beepngo ( watch for question popups on phone and answer them, if your phone is encrypted it will ask for a password (use simple password like the letter 'a' . This command will create a file backup.ab in the current folder)
[the previous command should have backed up the apk as well. However on my phone this did not work so we need some more steps to copy the apk too:]
adb shell
pm list packages -f | grep mobeam
will show the path where the application is stored (in my case:
package:/data/app/com.mobeam.beepngo-2/base.apk=com.mobeam.beepngo )
copy the apk to a folder which is visible on PC:
cp /data/app/com.mobeam.beepngo-2/base.apk /storage/self.primary/Download/beepngo.apk
exit
(you are back at the normal cmd window prompt, don't close the window yet)
Now on PC open windows explorere, navigate to your phone devices Download folder and copy beepngo.apk to a folder on PC
Disconnect old phone
on new phone: enable USB debug option in developer options
Connect new phone (watch for question popups on phone and answer them)
Copy beepngo.apk to the Downloads folder of the new phone
On phone use file manager, navigate to Downloads folder and run the beepngo.apk to install beepngo
On PC go to the command window:
check if new phone is visible to adb : adb devices
adb restore backup.ab (this will restore the beepngo files, watch for popups on your phone and answer quesitons. if you had to enter a password for encryption, please enter the same password again )
Start beepngo and the data from previous phone is visible
Click to expand...
Click to collapse
My backup.ab has 0 Kbytes. Any ideas?
rexator said:
My backup.ab has 0 Kbytes. Any ideas?
Click to expand...
Click to collapse
Are you sure that you have the latest version of MoBeam? I tested it on the latest version.
What does these command give as output?
adb shell
pm list packages -f | grep mobeam
Thank you MisterKosmos! Great help, works perfect. Looked complicated at first, but was really easy thanks to your great tutorial. 5 min work to get beep n go from my S8 to S9.
Do you think it would be possible to export the database to another format so to import into let's say Samsung Pay?