yashsingh1/xdaforums huggingface dataset:
[HTC Aria General] tilt4life2:
Thanks for the feedback everyone. I tested out Sense without flash and the only site I really go to (a NBA forum) had problems because they usually post youtube videos of dunks or other plays embedded in the threads and they wouldn't show up. That sucks.

But I have seen so many really amazing customizations in the Home Screens thread that I will probably go to CM6. One more final on Monday and then I can get to messing around with my phone.

I just love what people have done with Clockr. And the sense weather animations are cool so I will miss those.
[HTC Aria General] Ki77erB:
I guess you're right "Product F(RED)". It took me awhile to find it and I would like to provide it to anyone who is looking, but I see what you're saying and maybe its not a good idea. On another note, I did a little bit of research and the guys who made the one that was pulled have made a new one (still called Fancy Widget) that is on the market. It looks pretty nice and has a lot of features, but does not have the "flip clock" design that I like so much.
[Gen8 Android Development] guoloong:
Has anyone connect their archos 101 to adb successfully?
[Gen8 Android Development] Harfainx:
As long as you have the SDK already installed, follow this (I originally posted this over at the Archosfans forum). I assume you're requesting this for Windows.

----------------

Go to the usb_driver folder (In your SDK root).

Next navigate to the android_winusb.inf file.

Open that file up, and immediately above the [Google.NTamd64] line, and the [USB_Install] line, add the following:

;Archos 101
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1411
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1411&MI_01

Then plug your Archos in, and if it asks for drivers, point it to that file. If it doesn't ask for drivers, then navigate to your device manager and find the device with a yellow triangle with an exclamation point. Uninstall, and then when it finds it again, point it toward that file.

Done.

----------------

Hopefully that will do it for you.
[Gen8 Android Development] guoloong:
Hi Harfainx,

I followed the steps you mentioned by some how it doesn't work. When calling "adb devices" nothing is showing up.

Deos it matter if my A101 is still in 2.1?
[Gen8 Android Development] Harfainx:
Doesn't matter, I've done that on both 2.1 and 2.2.

Are you ensuring that your system is actually updating the driver to the new file?

If so, do a system restart. That should fix your problem.
[Gen8 Android Development] guoloong:
In device manager, I can see Android Phone -> Anchos G8 Composite ADB Interface. So I guess drivers should be properly updated right?

I have restarted both the PC and tablet both but still can't see the device in adb
[Gen8 Android Development] laptopfreek0:
Linux

Anybody know how to get adb working on a linux box?
[Gen8 Android Development] supagforce:
Dont forget to modifiy the ".android/adb_usb.ini" (found in your user account folder) file in a terminal/command prompt

Code:

echo "0x0e79" >~/.android/adb_usb.ini

or on Windows:

Code:

echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"
[Gen8 Android Development] Harfainx:
Well, my fix is for Windows, which you don't have to add anything to any other folders.

For Linux it's a bit more difficult. For Windows you only have to add those lines into the one folder (at least that worked for many users on the Archosfans forum since about two weeks ago).
[Gen8 Android Development] j.v.fouts:
(Rom)

anyone know if there has been a rom put out yet for this thing, and anyone give me some tweaks i could possibly do.

installed market and thats really it, read alot about the z4root and theres still some issues with it, so i dont really want to try it out yet
[Gen8 Android Development] supagforce:
mmm er ok

http://forum.archosfans.com/viewtopic.php?f=65&t=37386

see bottom post

http://forum.archosfans.com/viewtopic.php?f=63&t=41755&p=284338

From the archos website

First make sure you are running the latest ARCHOS firmware. Connecting by this method will give you user shell privileges. Learn more to know how to use ADB on Windows, Mac or Linux operating system:

* Go to the Android SDK page and download the latest SDK for your operating system. http://developer.android.com/sdk/index.html

* For Windows users only: Install the Archos ADB USB Driver for Windows. The driver is available at the ARCHOS support ftp (ftp://support.archos.com). Instructions how to install the driver are available at USB Driver for Windows site on Android Developers.http://developer.android.com/sdk/win-usb.html

* Add Archos vendor ID (0x0e79) to adb_usb.ini in .android folder in your home directory:

o Windows: echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"

o Macos: echo "0x0e79" >> ~/.android/adb_usb.ini

o Linux: echo "0x0e79" >> ~/.android/adb_usb.ini

* For Linux users only: You need to add a udev rule if ADB only works as root:

o Create a file /etc/udev/rules.d/51-android.rules that contains the following lines:

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",

ENV{PRODUCT}=="e79/*", MODE="0666"

SUBSYSTEM=="usb", SYSFS{idVendor}=="e79", MODE="0666"

o Make the rule known to udev with the following command:

udevadm control --reload-rules (or udevcontrol reload_rules on older systems)
[Gen8 Android Development] guoloong:
Thanks! I will try this soon. Looks promising.
[Gen8 Android Development] Harfainx:
It seems like some people need to add the lines to the .android folder, and some people don't. Not really sure why it works for some people by just modifying the .inf in the SDK.

http://forum.archosfans.com/viewtopic.php?f=74&t=42495

With an A101, and an A70 at least that's all I needed on Windows 32-bit and 64-bit versions.

I never edited anything in any .android folder until I put ADB on Ubuntu.

I see that some people needed to add those lines it, but some people haven't had to do that. Obviously it's best to do it if you're having problems, I'm not arguing with you there.

I wonder why some people need that line and some people don't... Maybe it has to do with having the Gen7 (A5IT) ADB drivers installed from before.
[Gen8 Android Development] supagforce:
Im not arguing either, :) i also noticed this too that it works for some. I wonder if it has anything to do with the OS version ie (Windows 7 / XP / linux) ??
[Gen8 Android Development] ggrant3876:
I followed your instructions here and on archos fans, in cmd I enter adb devices, doesn't list it but says devices listed. Using esbdview it shows a driver and a serial number. Any other suggestions, and yes I rebooted. Didn't help.
[Gen8 Android Development] Harfainx:
Did you try editing the file in the .android folder as outlined by Supagforce further up in this thread? Some people are able to have it work without editing that file, but others have to.
[Gen8 Android Development] guoloong:
Finally ADB is working.

I did it with a combination of instruction from Harfainx and some other from archosfans forum.

Here are the steps:

1. Go to the usb_driver folder (In your SDK root).

2. Next navigate to the android_winusb.inf file.

3. Open that file up, and immediately above the [Google.NTamd64] line, and the [USB_Install] line, add the following:

;Archos 101
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1411
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1411&MI_01

4. Then plug your Archos in, and if it asks for drivers, point it to that file. If it doesn't ask for drivers, then navigate to your device manager and find the device with a yellow triangle with an exclamation point. Uninstall, and then when it finds it again, point it toward that file.

5. start run %userprofile%

find folder called .android

Create/Edit adb_usb.ini, add 0x0E79 inside. Save. Restart ADB service.

After the last step, the A101 shows up with the command "adb devices"
[Gen8 Android Development] ggrant3876:
When I attempt to edit the adb_usb.ini all I get is "# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.

# USE 'android update adb' TO GENERATE.

# 1 USB VENDOR ID PER LINE.

0x0e79 ."
[Gen8 Android Development] guoloong:
You should put "0x0e79"

in a new line
[Gen8 Android Development] Kashban:
Anybody tried adb wireless app yet? Probably easier to go with that than medling with the usb drivers for windows.
[Gen8 Android Development] MGUS:
adb wireless with temproot works like a charm
[Gen8 Android Development] Kashban:
With the new firmware temp root is gone, so I have to go back to setting up USB...
[Gen8 Android Development] Kashban:
Not working at all. I did all of this, using the latest android-sdk (r8), device is showing up in the device manager, but adb still doesn't recognize it.

Win7 Professional 64bit, Archos 101it.

Any clues?
[Gen8 Android Development] noname267:
Same here. Have done all those steps, but the device is listed as 'offline' in 'adb devices' command.

I read somewhere in ArchosFans.com that people with 64-bit machines are having trouble connecting their Archos to adb. I'm also running Vista Business x64...

Thoughts?
[Gen8 Android Development] Kashban:
For me its not even listed.

The only Computer I have with a 32bit system is my netbook. Going to try that next.
[Gen8 Android Development] jutley:
Has anyone tried editing the build.prop and change the default adb status from 0 to 1 cause i can see with root explorer that it is set to off the build.prop is the one on root not the one in system.I can confirm this status is off on a archos 43 tablet should be the same all round.
[Gen8 Android Development] jutley:
There is a line in build.prop as follows persist.service.adb.enable=0 and the problem is i can't get root acess and change the default value from 0 to 1 which should enable it so will just have to wait for a suatable root option first.
[Gen8 Android Development] divx118:
It took me some time, because I couldn't get sdk manager to update (android sdk tools revision 8), but after I got around that by manual extracting the update in the tools folder it is working with no problems on win7 64 bit.

If you still have problems just ask, maybe I can help.

Maurice :cool:
[Gen8 Android Development] faldiin:
Could you post what steps you took and what Version you are using on the tablet please?

Faldiin
[Gen8 Android Development] divx118:
Just a little warning, this will not be the best guide. I was in a hurry and didn't want to read the basics of adb.

I am using the newest firmware 2.0.71 on the A101

1) I downloaded the adb driver from archos.com and installed it manually with the devicemanager from win7.

2) Then I edited the adb_usb.ini and put in the device code 0x0e79

3) I copied the entire .android folder to my tools directory of the android sdk. If this step is really needed I don't know, but when I downloaded the android sdk it was just a zip file and that needed to be extracted no further installation was involved so I just took a shortcut to try to get it working.

4) Tried updating the sdk manager with android sdk revision 8, but that couldn't be done, because the files wich needs to be updated are offcourse in use because of the update process (stupid windows). I then just looked for the temp folder which is inside the android sdk and there you find the update zip file which was downloaded during the update process.

Extract the files over the tools folder and overwrite if it asks you to.

5) Run the update again to get sdk 9 (2.3)

After that it restarted adb and my A101 got recognized.

I don't think all the steps are needed, but I was a bit in a hurry to get it up and running. So I took some shortcuts. ;)

BTW if you edit the adb_usb.ini be sure to run "android update adb" in the tools folder or if you have r8 in the tools_r08-windows folder , I didn't tried this before, but I noticed it after I done all the steps above. So maybe you don't need r8.

Maurice :cool:
[Gen8 Android Development] vncehar:
Help in Connecting Archos 101 to SDK

I am beginners and need to get my Archos 101 connected to my PC SDK.

I've downloaded SDK for my Windows XP and installed all the available packages.

Then I was told to download Android driver for Windows and add some lines there.

But I don't know how and where to get adb_usb.ini to be modified. Do I need to install anything in my Archos too? Do I need to instal any software in my Archos to enable it connected to SDK?

Everytime I connect my Archos to my PC via USB, Archos will prompt out page to mount Storage, do I need to click "Mount" here?

And everytime I connect my Archos to my PC, PC never prompt out that it found new hardware and ask my for driver. It also automatically recognize my Archos as a usb mass storage. Tried to replace usb mass storage driver with downloaded driver, but can't work.

I also see some instruction page in web that I can go to Device Manager and find Android phone and change the driver with the downloaded and modified one. Again, I can't find any Android phone text in my Device Manager.

Anybody can help?

Many thanks in advance.
[Gen8 Android Development] Kashban:
No, you need not install anything on the Archos to connect via adb, BUT, you have to enable USB debugging in the applications settings.

As for the usb_info file: Use the search function of this forum, it has been posted several times by now where to find and what to change.
[Gen8 Android Development] zeropang:
Hello everyone

Thanks for the previous post about the setting of Archos 101 adb.

I tried many times and failed to recognize the Archos 101 in Eclipse or adb command console.

Finally, I found that there is another usb_driver folder named "google-usb_driver" in the adnroid-sdk-windows" folder. Then I copied those :Archos101......" into the same filename "android_winusb.inf".

I restarted the adb server by command: adb start-server

and list the devices by command: adb devices

Finally, a device name appeared in my adb console and Eclipse environment.

:D
[Gen8 Android Development] Kashban:
There you go :D

I'm going to try this too and come back with the result.
[Gen8 Android Development] zeropang:
Hey,

I recognized my Archos 101 in my office and the problem still exist at my home computer. Therefore, I uninstall the Archos 101 device from mmc console -> devices manager

and repeated the steps today morning BEFORE I plug the Archos again (The first plug is in DEBUG MODE of my Archos 101 after un-installation)

It now work in my office and my home now :D
[Gen8 Android Development] chrulri:
for those who have to use adb while have something plugged into the usb host port, use one of the adb wifi app ;)

no more usb driver hassle...

just type "adb connect IP:PORT" in your computer terminal :)
[Gen8 Android Development] Kashban:
Was about to write the same... :D.

Don't forget to switch it off on the Archos after you're done with the job, otherwise some bad guy on the same network may capture your connection and have adb root access to your device.

I'm using the ADB Wireless widget, which is prominent enough to make sure you don't forget to switch it off. In this case: DO press the red button ;)

EDIT: ADB Wireless widget is not stable, hot restarts the device now and then. Using UrukDroid 0.4.2.

EDIT AGAIN: It is stable if one sets USB Debugging to true. Too bad the widget does not warn about this setting if it's missing but soft reboots instead.
[General Topics] theROMinator:
So about a month ago i dropped my HTC Aria, the screen is now cracked and I am looking for a replacement. I am thinking about buying it from durapowerglobal.com. I've looked into a couple things and the certificate for the site seems to be a bit fishy.. Anybody know about this site? One better? I know this is random but I'd really appreciate some help. Thanks.
[Galaxy Tab General] 3dadd:
I have a AT&T Tab (running a European build) and it's working perfect in all respects (phone, 3G , all excellent)

What is the best version to get it back to AT&T firmware for warranty.

I also read that you need to have AT&T firmware before you use an unlock code from AT&T. I see several of the Cell Unlocker sites offering 4.99 for codes for the Tab.

I do see the firmware on Samfirmware, but need to know what works

ANy advise would be great.
[EVO 4G Q&A, Help & Troubleshooting] whamsandwich:
Tomorrow I am planning on flashing my HTC Evo to MetroPCS.

I have a few questions, as this is my first android phone.

1. What exactly is happening when I "flash" the Evo to MetroPCS?

2. My Evo is running 2.2 right now, when "flashed" to MetroPCS would I be able to update from 2.2 to 2.3 (Gingerbread) later?

3. What exactly are roms and rooting? When I have my phone flashed is someone "rooting" my phone?

Thank you in advanced

P.S. I do understand when I flash my phone to Metro I will lose 3g and 4g functionality.
[EVO 4G Q&A, Help & Troubleshooting] The Local Moron:
Hi there,

I'm a bit of a newbie myself, so to try to answer your questions without being wrong...

1. When you "flash" your phone, it refers to replacing the ROM on your phone. The ROM on your phone is basically a copy of your phone's OS (in this case, Android). Don't be too confused over the ROM part, as even though ROM stands for "Read Only Memory," you can still make changes to it (weird eh?)

2. That will depend on if someone actually makes a MetroPCS 2.3 update. The thing with flashing is that you can put on any ROM you want, by just overwriting the old one. It just requires someone to make the ROM. Most developers package updates for their ROMs so you can sometimes just put on the newer ROM, flash that and be up and running quickly.

3. As I mentioned before, ROMs are basically a copy of your phone's OS that someone might have customized. (Feel free to correct me guys,) In the Android OS way, you flash your ROM onto your phone. An unmodified copy is maintained on the phone, while another copy is made where your phone actually modifies it and changes it as you use the phone and store data. If something goes bad, no problem. Phone takes a copy of the unmodified ROM and copies that over the "put OS to be used here" chunk of your memory.

TL;DR? ROMs are the software on your phone, but can be modified.

3a. Rooting is different then flashing though, although it's commonly associated with each other. Rooting is when you modify your Android OS so you can have write access to other parts of the OS. All those apps that were stuck on your phone and you never liked? With rooting, you can pull those right out. Rooting allows you to pretty much do more things with your phone that you couldn't do before. It doesn't sound like too much, having write access to everything. But there are plenty of things you can do to your phone with write access. One of those things actually is flashing other ROMs to your phone. You actually need to root your phone as it is, so you can install what's called a custom recovery and a developer bootloader. Anyways, I'm not going to go through too much. Just check out the Evo Development area and there will be plenty to read through.

Hopefully I've explained enough. My apologies for the long post, I have a tendency to be through :D Let me know if you require clarification. Cheers!
[EVO 4G Q&A, Help & Troubleshooting] whamsandwich:
Thank you so much for replying! :D

Although one more question, when I have my phone "flashed" to install another ROM; do I require root access?

P.S. Rooting sounds like a great idea, I wanted to get rid of all those useless sprint apps.

EDIT: Just realized you did answer my question in 3a, so when someone is flashing my phone to MetroPCS tomorrow that means someone is rooting my phone and installing a ROM that is compatible with MetroPCS? Is my phone more than likely going to remain rooted?
[EVO 4G Q&A, Help & Troubleshooting] The Local Moron:
Hmm, I didn't know MetroPCS flashes the Evo now...yay!

Anyhow, I'm going to guess MetroPCS will have their own ROM or will install a custom ROM from somewhere. The key thing really is to have them insert your ESN into their database. Afterwards, you can flash whatever you want on it. I remember it used to be a problem too, for people wanting to switch to MetroPCS. Developers had the software and everything, but the only way to activate it is to convince a service rep to add your ESN into the MetroPCS device database. Now that it's official, it's much easier.

I'm mentioning all of this because if they are officially flashing Evos now, I would think they would have a special in-house ROM that has already been tested and vetted. The issue here is that it's probably a locked (non-rooted) ROM. From the point of view of a service carrier, distributing rooted ROMs might cause higher complaints from users who screw up or from reliability issues. Anyways, good luck getting it flash. Let me know how it goes...
[EVO 4G Q&A, Help & Troubleshooting] whamsandwich:
I'd imagine that to activate a phone with MetroPCS they'd need your ESN, I'll be asking the REP tomorrow. Chances are they are not using an In-House rom, because simply flashing the phone through Houdini gives the phone Talk and Text. But for a little more money under the table they add everything else, not that I can't do it myself. But I'd prefer someone who's done it before do it before I do. Either way I'll be asking quite a bit of questions tomorrow to the REP and I will let you know how it goes.
[EVO 4G Q&A, Help & Troubleshooting] :
I have to give a little clarity here.

1.) "Flashing" your phone is not replacing a rom. Or anything to do with a rom. Flashing your phone is changing the service your phone uses to make phone calls. e.g. Flashing to metro. When you flash your phone you are essentially telling your phone to use MetroPCS's towers instead of sprints.

2.) If you flash your phone you DO lose the data functionality. BUT there is a solution. If you take your flashed evo to the right person they can unlock the data on the phone and it will work just like it would on Sprint. (craigslist is full of ppl who can do it for a price.)

3.) "Rooting". Rooting your phone makes you the "SuperUser". Basically its like "Jailbreaking" if you know what that means. Either way it makes you like an administrator for your phone. Rooting gives you full control over the phones inner workings. Therefore you can install what we call "ROMS". On the flip side this means you can easily BRICK your phone if your not careful. Rooting is only for those who know what they are doing. So do your homework before attempting.

4.) As far as if the phone can receive updates like Gingerbread after you flash it? I don't know. I would like to find out myself. The question is hard to call for me because you still have access to the android marketplace after you flash it. But you are not on Sprints network any longer. So hopefully someone here can answer that for us both.

Glad to be of assistance.

Tony.
[EVO 4G General] NickUcf:
I have an Evo 4g and after updating it and rooting it my camera app is giving me a lot of trouble.

I can't record 720p video anymore. It will record but it is in very choppy blocks. what do you think is the problem? Does it have to do with the custom rom that is flashed to it?
[EVO 4G General] sitlet:
Probably. It would help to tell us what rom you use...
[EVO 4G General] drmacinyasha:
And what hardware version...