Database Users

Some help with Eclipse and ADB in Linux

Hey, did a search but couldnt find a solution. I'm having problems getting my device to pull up in adb remount on Ubuntu. When I try remount it says no command 'adb' found sometimes or permission denied when it does work, I have root and USB debugging enabled on the devices (a Nexus One and G1). When I try adb devices I just get ?????????????? unknown.
Also, and I don't know if it's related, but in Eclipse, I can't get the SDK location loaded, I have the directory right, but when I hit Apply or OK nothing happens, it just doesnt load. So if I try to start a project I have no Build Targets to select from.
Any help would be appreciated. I have everything running fine in Windows but I'm fairly new to Linux I haven't used it in years. I'm running Ubuntu distro if that matters. Thanks.

i'm with you. i picked up the android sdk tarball, and am a little lost too . i tried getting adb to work in windows 7, but i can't get that going either. dangit. if someone could put up some good reference material, it'd be appreciated

Hello,
The problem with linux having trouble with adb probably lies with a permission issue try adb kill-server && sudo start-server.
The other issue is most likely because you did not download any targets yet. goto windows in eclipse and select android sdk and adv, then at available packages or something like that download your target

i can't even get that far. i switch to my androidSDK/tools and then "adb devices" all i get is 'no command adb found'

I did the first couple times too, then I went to command and did:
su
<enter password>
cd
export PATH=${PATH}:<your_sdk_dir>/tools
then when I adb remount or adb devices it gives me the unknown device thing
but I think the next secret is here
http://forum.xda-developers.com/showthread.php?t=613217
in like the 3rd post. However I think the export PATH is a temp fix because the ~/.bashrc needs to be modified with the path settings and I have no idea how to do that. I just get lots of permission errors or file not found for everything I try, even with root. I'm just using Eclipse in Windows for now, and hopefully someone can help us out cause I'd like to work on roms but I guess I need to brush my Linux up first.

http://forum.xda-developers.com/showthread.php?p=5377103
i found some help elsewhere on the net, and posted it up at the end of this thread. they were having similar issues with the dream, apparently.
i also found this
that link there will probably get you hooked up

adb devices now has a readout!
and, you're right about adding the export PATH=${PATH}:<your_sdk_dir>/tools to
~/.bashrc
i think this command will do it. run in terminal
gksudo gedit ~/.bashrc
i just made a comment line that says
# android sdk export path
and another line underneath it that says
export PATH=${PATH}:/home/timmyd/androidSDK/tools
because that's where i have the extracted sdk
all good, i think. now, let's see what's going on ...
oh yeah, don't forget to enable usb debugging on the device itself.
settings>applications>development
allow usb debugging

screeny works at least
{
"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"
}

Cool, I'll try that out tomorrow.

timothydonohue said:
i'm with you. i picked up the android sdk tarball, and am a little lost too . i tried getting adb to work in windows 7, but i can't get that going either. dangit. if someone could put up some good reference material, it'd be appreciated
Click to expand...
Click to collapse
Hi all!!!!
I have a problem with my HTC Tattoo, can't connect the tatto with adb in ubuntu and eclipse Helios.
/android-sdk-linux_86/platform-tools$ ./adb devices
List of devices attached
???????????? no permissions
Thank you very much.

Hi, I have tha same problem with ????? and can't connect to eclipse my galaxy, so the solution is just use the instructions from the h**p://developer.android.com/guide/developing/device.html
I solve this problem with
1. Log in as root and create this file: /etc/udev/rules.d/51-android.rules.
For Gusty/Hardy, edit the file to read:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
For Dapper, edit the file to read:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666"
2. Now execute:
chmod a+r /etc/udev/rules.d/51-android.rules
Click to expand...
Click to collapse
The USB Vendor IDs foreach manufacturer
Manufacturer USB Vendor ID
Acer 0502
Dell 413c
Foxconn 0489
Garmin-Asus 091E
HTC 0bb4
Huawei 12d1
Kyocera 0482
LG 1004
Motorola 22b8
Nvidia 0955
Pantech 10A9
Samsung 04e8
Sharp 04dd
Sony Ericsson 0fce
ZTE 19D2
Click to expand...
Click to collapse
Hope to help you!

Linux Window Manager on Android.

Do any of you think it's possible to run a full blown Window manager on our phones?
Not anything like gnome or kde, but awesome or lxde.
I have grown increasingly tired of all of Android's home applications.
Look forward to seeing comments

Well, I know you can run Debian Linux on our phones... I don't really think there is a point though because our CPU isn't powerful enough to make it very functional. The Droid may have a chance, and the Nexus One or Evo probably could.

Our phones should be powerful enough. Awesome and similar window managers use very little cpu.

wow, I'm no where near able to answer your question but what an interesting idea!! That would be very cool!
Thanks to REGAW helping me learn I used my new gnome bootable usb last night, how cool!!
Only downside is it doesn't save ANYTHING from the session, I'm going to partition some space for it on my hdd

id love to see ubuntu ported to our heros. the tp2 users have it, why not us?

I'd say Ubuntu is a bit too much I think a Debian port would be much more friendly.
Now that I think about it, I wonder if gentoo could be compiled on the phone and used as a phone.</off topic>
This topic is about running a *Window Manager* on the phone, not another operating system. I was reading about Android on the Wikipedia page earlier, and I read that there was no X support, so I dont think it would be very easy to get it working :/
Some of those manager are deathly simple. I guess they could potentionally be ported.

if you were running one of these overclocked roms would this change anything, I found this elsewhere, I didn't write it, you may have read it before:
OK, here's howto get Debian up and running on your HTC Hero running the MoDaCo Custom Rom 2.9:
1. Download this archive:
androidfanatic.com/cms/unofficial-app-repo.html?func=fileinfo&id=21
2. Extract the archive, resulting in a folder 'debian'. Inside this folder
replace 'installer.sh' and 'bootdeb' by the files provided with this howto.
Make sure they are replaced, delete the old ones first!
3. copy the folder 'debian' to the root of your sdcard. The root is the highest level, e.g.
drive E:\ if you are on a windows pc. Unmount sdcard on pc and phone.
4. Download ConnectBot from the market. See included QR-Code for use with Barcode Scanner app.
5. Start ConnectBot and open a local shell. To do so click on the drop down menu on the lower left
that says 'ssh' and select local.
6. As this is your first start of Debian you need to "install" it first. Execute the following
commands (press enter at the end of each line, always allow root access if asked):
su -
cd /sdcard/debian
sh installer.sh
bootdeb
At this point you are changing into the Debian environment. From now on do not restart
your phone or kill ConnectBot without executing 'exit' first. Now continue with commands:
/scripts/onetime.sh
exit
That's it, you are done! Now you can do whatever you want with your Debian installation.
7. To go into Debian from now on you use the following commands in a local shell in ConnectBot:
su -
bootdeb
You can automate that by passing these two commands as 'post-login automation' in ConnectBot,
long click the 'Local' entry in ConnectBot and edit the host.
Remember to leave with 'exit'! Alternatively you can click the trackball once and then press 'd'
on the keyboard. This resembles 'Ctrl+d', which is the logout command for unix shells. Do this
two times more to shut down the local shell in ConnectBot.
8. If you want to access your Debian by ssh execute the following command:
/etc/init.d/ssh start
9. To free some space in your image file execute the following command in the Debian environment:
apt-get clean
Do this also after every usage of 'apt-get upgrade' or 'apt-get install'.
10. For additional information here is howto resize your debian.img (for Linux only):
androidfanatic.com/cms/community-forums.html?func=view&id=1610&catid=9
And see here howto install a graphical desktop enviroment, in this case lxde or icewm:
(Note that i had to resize my debian.img first!)
wiki.lxde.org/en/Android

I'm not going to quote the entire post
@tmachovec: thanks for the info, but I'm looking to see if we can actually run it on the phone. Not connect to a fake X11 server over local ssh. I appresicate the input. But I'd like to run this on the phone

http://www.gentoo.org/main/en/where.xml
Gentoo has an ARM build, so it's possible.

noidea` said:
I'm not going to quote the entire post
@tmachovec: thanks for the info, but I'm looking to see if we can actually run it on the phone. Not connect to a fake X11 server over local ssh. I appresicate the input. But I'd like to run this on the phone
Click to expand...
Click to collapse
Gnome, KDE, IceWM or LXDE Desktop on your Android! 1 Year, 2 Months ago Karma: 9
IMPORTANT UPDATE: Many comments on sites that have blogged this post seem to be getting the wrong end of the stick. This is not connecting to a remote desktop on another machine! This is x11 and LXDE Desktop running LOCALLY on the G1 device, the reason I had to connect back to LOCALHOST using VNCViewer (also running LOCALLY on the device) is because there are no drivers available. This circumnavigates the need for any special drivers.
Now back to business!
It's official you can run X-Windows and your choice of GUI (Gnome, KDE, IceWM etc on an Android device!
Screenshots are below!!
androidfanatic.com/community-forums.html?func=view&catid=9&id=1620#1620

wow im lost in all this (NOT linux savy)
what does this mean?

Ok, so I've been trying to do this and I can never manage to get it working. When debian boots, it gives me an array of errors, but its too quick to reboot so I can't read whats wrong. I'm 99% sure it has something to do with the image being read off the sdcard. I read the installer script and manually moved all the necessary files because the script would not do it.
Yes, I ran everything as su
Has any one else had problems with this?
Thanks tmachovec

Any one have info on my problem?

I couldn't get it to load either, same problems with getting Debian to boot. I know a little about linux but not enough solve these issues.
noidea` , I have no idea.

just wondering has any one been able to do this successfully on their Hero's?

noidea` said:
just wondering has any one been able to do this successfully on their Hero's?
Click to expand...
Click to collapse
Have you tried doing some of the stuff from this site
http://android.modaco.com/content/htc-hero-hero-modaco-com/292093/debian-lenny-now-running-on-hero/
Its the gsm htc hero.. Different phone, but some of the stuff might definitely apply.

Heres a post I made after i got it to work
http://forum.xda-developers.com/showthread.php?p=6438126#post6438126
I GOT IT WORKING
here is a screen shot.. Im willing to do any kind of screen shot to prove it
Ill zip up my exact files that I use and the simple command to get it up and running.
Ill open up something and type my name and post a screen shot in a bit.
{
"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"
}

[WORKING] ROOT for all Eris'

Big thanks to tereg for the toolkit and the guys who rooted the EVO with a file write/chmod race condition exploit that gave me the idea for this.
jcase noticed that a race isn't actually necessary to exploit the chmod 777 on the file I've been working with, simplifying the script alot.
I used the files from the adb development pack that Tereg put together. Download them here. You don't need them for this root process as long as you have a working adb install.
THE SCRIPTS HAVE BEEN UPDATED MANY TIMES! Please be sure to re-download the new hack-v4.zip before you start if you a returning root seeker.
You will need adb access. Install the android sdk for your platform (macos, windows, linux) get it for your OS here.
If you don't know how to install the sdk, search xda, there are a ton of howtos for that.
Also, if you want to root and can't get your computer to talk to the phone or have some other weird computer related issue you can now try this method, which doesn't require a computer at all!
Unzip hack-v4.zip to somewhere, copy/move the files into your adb-sdk/tools directory/folder.
*updated files to hack-v4.zip @ 7-14-2010 10:43AM Central*
Files to download:
hack-v4.zip
A ROM file, I suggest EvilEris if you want to flash the whole phone OR EngTools.zip If you just want to be root. (Thanks jcase!)
Android SDK (skip if you have a working adb)
Instructions for linux/OSX. - Alternate instructions specifically for MAC
Have adb in your path, or move the files contained in hack-v4.zip into your sdk/tools directory so your pushes will work properly.
FOR ALL OS's Make sure your phone has Applications->Development->USB Debugging turned on.
Do NOT have your phone in Disk Drive Mode, have it in Charge Only.
Open a terminal window in your /tools/ directory. Type this at the prompt.
Code:
sh runinlinuxfromtools.sh
This will take a few minutes, follow the instructions on your screen.
If you get adb: command not found, try
Code:
sh runinlinuxadb.sh
Some people get a permission denied error. Try
Code:
chmod +x ./runinlinuxfromtools.sh
./runinlinuxfromtools.sh
Instructions for windows (thanks tereg!)
Download the hack.zip file and extract it to the desktop. So, you have a folder on the desktop called hack. I would recommend moving or copying those files (EDIT: that are contained in the hack folder) to the C:\android-sdk-windows\tools folder. Why? Because the script runs "adb ____" commands, and unless you've set up adb to be able to run anywhere within the command prompt, the script won't run. So, it will universally work if the files in the hack folder are placed in C:\android-sdk-windows\tools
So, open a command prompt by pressing WindowsKey+R, or going to Start-Run (in WinXP) and typing
Code:
cmd
in the text box there and press OK
If you are in Windows Vista/Windows 7, go to the Start Menu, then type in
Code:
cmd
in the search bar in the lower right-hand corner of the start menu and press enter, and locate Command Prompt in the search results, or go to Start -> All Programs -> Accessories -> Command Prompt
Type
Code:
cd C:\android-sdk-windows\tools
and press enter
Now, I recommend pushing the ROM you want to flash to the SD card now. So, if you download EvilEris3.0 for instance, make sure you download it to the C:\android-sdk-windows\tools folder, and then execute
Code:
adb push EvilEris3.0.zip /sdcard
Replace EvilEris3.0.zip with the name of the .zip file that you choose to download.
Then, type
Code:
runindos.bat
to execute the script.
You might have to run it 2 or 3 times for it to work. If it fails, just reboot the phone normally, then run
Code:
runindos.bat
again once the phone is booted back up and you're ready.
----------(Thanks again tereg!)
If your device reboots into a new screen with options on it, you now have root in recovery mode. At this point you will be flashing your Eris's brains, so YOUR PHONE WILL BE BLANK AFTER LOADING A NEW ROM! All of your apps/numbers will be gone from the phone.
I suggest a nand backup first.
Download and copy one of these ROM's to your sdcard as update.zip and flash it with flash zip from sdcard by selecting "Install zip from sdcard".
The first boot after loading a new ROM takes quite a while to show any activity to the screen. Give it a good 5 minutes before you start wondering if it's ever going to come back.
Eris ROMS
More things you can now do.
Replace that hateful HBOOT 1.49, and get a rooted STOCK phone.
Donate of you luv me!
-----------------
And some love for tereg! Donate a bit to him too, if you're feeling generous.

Dude, seriously. Put up a donate button. I would donate for your effort. This is absolutely amazing.

I will suck yo thang if this works...brb

If this is confirmed I'm returning my eris with the ****ty trackball and rooting a new one >_>

I love you so much for running with our small shot

when doing
cat > data/local/testfile
I get:
System cannot find the path specified

Oh and btw
This should work on ANY HTC Android 2.1 phone.

{
"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"
}

cptkrush said:
when doing
cat > data/local/testfile
I get:
System cannot find the path specified
Click to expand...
Click to collapse
crap, I'm kinda spaced out from glee right now. should be
/data/local/testfile

wag3slav3 said:
crap, I'm kinda spaced out from glee right now. should be
/data/local/testfile
Click to expand...
Click to collapse
lol, same thing...
do you want us to do a cd command, because the cat command does not exist i believe. It may not help that i have absolutely no idea what to do in the first place

cptkrush said:
when doing
cat > data/local/testfile
I get:
System cannot find the path specified
Click to expand...
Click to collapse
You're missing the first / in /data/local/testfile sir.
Yours cat > data/local/testfile
mine cat > /data/local/testfile

wag3slav3 said:
You're missing the first / in /data/local/testfile sir.
Yours cat > data/local/testfile
mine cat > /data/local/testfile
Click to expand...
Click to collapse
nope, that was just how i typed it out in the post, still not working.

How are we supposed to "run" the following?
/data/local/flash_image recovery /sdcard/recovery.img
reboot recovery
I keep getting "error opening /sdcard/recovery.img: No such file or directory", but I'm also not really sure if I'm missing something. I type it in EXACTLY as you put it, right?

ericFuels999 said:
How are we supposed to "run" the following?
/data/local/flash_image recovery /sdcard/recovery.img
reboot recovery
I keep getting "error opening /sdcard/recovery.img: No such file or directory", but I'm also not really sure if I'm missing something. I type it in EXACTLY as you put it, right?
Click to expand...
Click to collapse
cat is a unix command
we're on dos
dos doesn't have the same command

xnatex21 said:
cat is a unix command
we're on dos
dos doesn't have the same command
Click to expand...
Click to collapse
I understand that, but that wasn't my question. Refer to my previous post.

xnatex21 said:
cat is a unix command
we're on dos
dos doesn't have the same command
Click to expand...
Click to collapse
THIS EXPLAINS EVERYTHING, sorry for caps, but i got excited :3
any way to do this in DOS or am i gonna have to boot up ubuntu?
scratch that, wag3 got me covered.

xnatex21 said:
cat is a unix command
we're on dos
dos doesn't have the same command
Click to expand...
Click to collapse
You skipped the step where you do an adb shell.
You should be at the $ prompt on your phone for this.

ahem... I get permission error when I tree to reboot **epic sadface**
I"M DUMB I HAVE TO LEAVE SHELL FIRST

Put run 'adb shell' in the instructions before 'then do this'. Not everyone is going to pick up on that.

wag3slav3 said:
You skipped the step where you do an adb shell.
You should be at the $ prompt on your phone for this.
Click to expand...
Click to collapse
you should add
"do: adb shell"
to the first post.

[Guide] Android Emulator On Computer

If anyone is interested in running an Android emulator heres a short guide for it.
Step 1: ADB
If you haven't already, you need to install ADB on your computer. See this guide:
ADB Guide
Step 2: Configuration
Now open SDK Setup.exe from wherever your android-sdk-windows folder is and go to the [Virtual Devices] option and press [New]
{
"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"
}
and this window will show up
Heres what to put
Name: Put something simple like "Android_2.2", etc
Target: From the dropdown box, select whichever Android version you want. I want Android 2.2 so I will select "Android 2.2 - API Level 8"
SD Card: Insert a size in MBs. I put 500(MB). The larger the size, the longer it will take to process. Ignore the File option
Skin: I would recommend you skip this option
Hardware: If you press the [New...] Button it will give you a bunch of options. Basically, you can configure if your emulator can support GPS, Dpad, Keyboard, etc. Most of them are enabled by default but you can increase the ram via "Device Ram Size". I set it to 500(MB) for example.
Heres what it should look like when finished
Click [Create AVD]
Step 3: Running The Emulator
Now open up CMD (Start>Run>Cmd) and enter the following commands:
cd c:\android-sdk-windows\tools (or wherever your "android-sdk-windows\tools" is)
emulator -avd "AVD Name" -partition-size 500 (AVD Name is whatever name you used in the beginning and 500 is the size of the emulators internal memory in MBs. You can increase the size if you want)
Now the emulator should show up and when its done booting up you should have something like this.
And you have your emulator
Step 4: Installing APKs
Now you might want to install some apps/games on it. You can either download APKs from the internet or rip them from your phone. First, open up another CMD (Start>Run>CMD) and type:
cd c:\android-sdk-windows\tools (Or whatever command you used in step 3)
To rip APKs from phone, connect phone to computer and put phone in USB Debugging mode Settings>Applications>Development>USB Debugging. Now go:
adb pull /data/app
Now in your android-sdk-windows\tools folder there should be a list of APKs. Now disconnect your phone and to install the APKs to the emulator, go:
adb install ______________.apk (Whatever the name is)
*NOTE* If you downloaded an APK from the internet, put it in the android-sdk-windows\tools folder first.
And there you have it. Enjoy!!!
Gary~~

TIPS
Will add tomorrow

Hi xGary,
i`ve done all the steps but when i type emualtor -avd Android -partition-size 500 tell me `emulator`is not recognized as an internal or esternal command, operable program or batch file.

rendeiro2005 said:
Hi xGary,
i`ve done all the steps but when i type emualtor -avd Android -partition-size 500 tell me `emulator`is not recognized as an internal or esternal command, operable program or batch file.
Click to expand...
Click to collapse
Oh sorry, it was supposed to be emulator not emualtor. Typo

Thanks for the guide but how do you make the emulator landscape?

emulator does not show up
Hi,
I followed all the steps but after starting emulator from cmd no window came. Infact two or three times a black cmd window appeared and dissappeared instantly. was not able to read the text on the window.....
on other forums, somebody suggested to wait for a while....but i waited for about half n hour...nothing happened....
i can see a process "emulator.exe" in taskmanager which is consuming around 50% of cpu usage...and 18 MB ram......
My computer config: Pentium dual core with 4 GB of RAM
kindly guide....thanks in advance...

You may start the emulator by selecting the avd and press "Start" button. I did it today and works fine.
I just saw the guide here but luckily (I'm newbie to this) I did exactly the same steps except the start the emulator through CMD.

Btw if you go to se's dev website you can grab a preconfigured x10 avd.
Sent from my SAMSUNG-SGH-I897 using XDA App
Edit: heres the link
http://developer.sonyericsson.com/wportal/devworld/downloads/download/dw-102216-xperia-x10sdkadd-onr1?cc=gb&lc=en

gavriel18 said:
Btw if you go to se's dev website you can grab a preconfigured x10 avd.
Sent from my SAMSUNG-SGH-I897 using XDA App
Edit: heres the link
http://developer.sonyericsson.com/w...d/dw-102216-xperia-x10sdkadd-onr1?cc=gb&lc=en
Click to expand...
Click to collapse
Thanks. Downloading now.

gavriel18 said:
Btw if you go to se's dev website you can grab a preconfigured x10 avd.
Sent from my SAMSUNG-SGH-I897 using XDA App
Edit: heres the link
http://developer.sonyericsson.com/w...d/dw-102216-xperia-x10sdkadd-onr1?cc=gb&lc=en
Click to expand...
Click to collapse
Take a look at the description:
Dec 16, 2009
Sony Ericsson Xperia™ X10 add-on for the Android SDK
The Sony Ericsson Xperia™ X10 add-on for the Android SDK includes the complete Android system with additions customizing it for the X10 : Sony Ericsson splash screen; X10 colour backgrounds; A "skin" of the X10 which is a simple graphic of the front of the phone; A hardware.ini file to set the operating parameters for screen, camera, audio and so on.
According to date this "complete Android system with additions customizing it for the X10" is for Android 1.6. I didn't dig pretty deep, but search for a new version wasn't successful. It can be a base, but look like requires a lot of customization for current Android version.

@che
But what do you plan on doing with it? And can you not use the hardware profile while using 2.1 apis?
@ freco no prob
Sent from my SAMSUNG-SGH-I897 using XDA App

problem was with android 2.1
Hi,
thnx for the replies..
yesterday i was trying to start the avd for version 2.1 and it was not running....today i downloaded other versions..(almost all from 1.5 to 2.2) and tried to run emulator of them again..
except 2.1 all other went fine...i think there is some problem with Android 2.1....by d way m happy now...and can start some work..

gavriel18 said:
@che
But what do you plan on doing with it? And can you not use the hardware profile while using 2.1 apis?
Click to expand...
Click to collapse
I think to try to program for Android and this profile allows to see how the program will look like at specifically X10 platform.

kashifsiddique said:
Thanks for the guide but how do you make the emulator landscape?
Click to expand...
Click to collapse
turn of Number-Lock and Click the #7 key to swap the screen from portrait - to landscape - and back #-)

[UTILITY][RUU IMITATE]Easy Installer - Install your rom's like an RUU[HTC only]

Easy Installer​
{
"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"
}
What is Easy Installer?
Easy installer is a windows RUU imitate that helps you as user to install your Rom's with only 2 clicks. Fully automated!
For devs Easy installer helps to provide Rom's alternate to the recovery zip archive.
Click to expand...
Click to collapse
How does Easy installer work?
Thats easy. The developer create a system img file of his rom and configure Easy installer easily with one config file. The package can provide like a normal rom.
The user run a little exe-file and the RUU installs the rom fully automated! If something runs false, the RUU gives the user an error and a explanation what he can to do now.
Click to expand...
Click to collapse
What i need for Easy installer
For now, Easy Installer works only with image files, so you need your Rom as a image file. You can create a image file of your rom easily with mkyaffs.arm (find in attachements).
The config file is easy to understand. An example here (found in package too):
Code:
;The config file is neccessary for the RUU. Here you define all file namens.
[functions]
;imgfile specify, if you want to flash a image or a zip file (0=zip-file, 1=img-file). For now, only img files working, sry :(
imgfile=1
;waitbl set the time the RUU wait for the bootloader (fastboot). Some devices take a while to reboot to bootloader. Set the time here, in generally the time 10 is enough
waitbl=10
;the img-name specify the name of the image file without the file extension!
img-name=system
;zip-name is for one of the next versions, when it is possible to flash zip files. If you want, you can delete this
zip-name=HC_MIUI3.2
;boot-name specify the name of the boot.img without extension.
boot-name=boot
;set the name of the clockworkmod recovery file for your device here.
cwm-name=cwm
;rec-name is the original recovery of HTC that must be inserted for img-files. Put the name here without extension
rec-name=recovery
[labels]
;specify the shown rom-name in the RUU
rom-name=.sense
;the device name is the full name of the device the rom is for
device-name=Wildfire S
;some devices has more versions (marvel, marvelc, marvelct e.g.). Specify for what device your rom is.
device-code=marvel
The picture in the RUU is namend "PHONE.bmp" in package, you can replace with your own.
Click to expand...
Click to collapse
How to create the system.img?
Well, thats is easy
1. Install your Rom you want to use in Easy Installer at your phone via the Recovery (don't start the Rom!!!)
2. Go to recovery, connect your phone via USB-Cable to computer
3. Download the mkfs.arm.zip (see attachements)
4. Create a new directory in your SD-Card (example: "build")
5. Copy the extracted file "mkfs" of the downloaded archive into the folder "build"
6. Insert the SD-Card into the phone
7. In recovery go to: "mounts&storage->mound /sdcard" or run following adb-command: adb mound /sdcard
8. run the following commands in adb one after one:
adb shell
cd /sdcard/build
./mkfs /system /sdcard/build/system.img
9. Wait for the "Build OK."-message
10. Exit the adb shell via exit command and turn off the phone
11. Take the SD-Card of the phone and insert it into your PC
12. in the SD-Card's folder /build you will find a "system.img". Use this file for the easy installer
Click to expand...
Click to collapse
Changelog
v0.0.1
- first version, basic install function
Click to expand...
Click to collapse
Download
See the attachements (WSWizard.zip)
Click to expand...
Click to collapse

Will this work for all devices?
Any chances of bricking? Because many of users of Micromax A70 bricked their phone by a chinese flashing tool.
Burned from my laser torch using pencil cells

Sorry, i see now, that i posted this in false section. In genarally it works only for HTC devices which are unlocked or S-OFF, not for others!

How can I use the mkfs.arm?

it works only on ARM-based devices, like the HTC phones.
You must copy the file onto your sd-card e.g.:
adb push mkfs.arm /sdcard/build
After this you install your Rom on the device or copy the /system-files to the sd-card. Now you run following command:
adb shell
cd /sdcard/build
./mkfs.arm /system /sdcard/system.img
ODER
./mkfs.arm /sdcard/build/system /sdcard/system.img
Then the file will build a system.img and copy it onto the sdcard for next use

Would like to know if this would work to ONelll123
Wipe everything
Flash Rom
Make Nandroid
Use Nandroid as ROM's Images
It seems much easier to me than having to go to shell and all Not meant to be an insult, just a recommendation/question

Hmm, it ia qn idea, but idk in what filesystem the backups are saved. If it is yaffs2 it can be that this works.
But you must do shell commands too. Its for secruity reasons and that this method used works.
Sent from my HTC Wildfire S A510e using XDA

ONeill123 said:
it works only on ARM-based devices, like the HTC phones.
You must copy the file onto your sd-card e.g.:
adb push mkfs.arm /sdcard/build
After this you install your Rom on the device or copy the /system-files to the sd-card. Now you run following command:
adb shell
cd /sdcard/build
./mkfs.arm /system /sdcard/system.img
ODER
./mkfs.arm /sdcard/build/system /sdcard/system.img
Then the file will build a system.img and copy it onto the sdcard for next use
Click to expand...
Click to collapse
Thanks I will be try this when htc one x gets adb working recovery