The market.rar download contains the 2.1 gApps it looks. This is why the Market is FC'ing. If you look at the dates of those files, they're like 2008. Maybe it's just a glitch or maybe the person who made these has a computer with a bad time (=.. i dunno

these are the 2.1 files I believe. The date/time on them report 2008. That is why the market is crashing. I'm going to grab the 2.2 market from my Samsung Fascinate and try that.

ok, maybe it does exist (data/test)

I finally got adb working and even though 'data' is read only, 'data/test' is available...wierd

Since i got adb working, i just ran the 'apkadd.bat' command script to adb push the files over.
(=

Seems to be working now

I'm a bit confused.... a few questions

8. - type "cd data/test"

What's the purpose of this?? I dont have a 'data/test' directory

9. - "mkdir -p froyo/system/app"

Where is this being created? We dont have write access to root

Thanks!

I still have no devices found, even with USB Debugging on. I also have the 'android_winusb.inf' updated.

There's a few threads with this ADB issue.

Here is one of the more detailed
http://forum.archosfans.com/viewtopic.p ... 7&e=284567

voidunknown wrote:Worked perfectly for me. It's actually pretty easy to do.

Just installed Flash 10.1 from the market, now I'm on my way to complete android bliss.

Did this work on Windows or Linux/iOS, etc?

I've been messing with this in another thread too. ADB DEVICES is coming back blank even though the drivers installed ok (device manager).

Euhm, anyone else who can no longer connect to their wifi network? I have an N network which worked fine with firmware 1.0.84 but now it doesn't even find my home network (router is not even 10 feet away in the same room). The network list is much smaller than before. It seems it only detects G net...

Yeah, rebooting doesnt do it either. ADB works fine for my HTC Incredible and Samsung Fascinate. Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. D:\>adb devices * daemon not running. starting it now on port 5037 * * daemon started successfully * List of devices attach...

Then plug your 70 with ADB debugging enabled into your USB port. When it asks for drivers, point it in the direction of that file. Enjoy your newly ADB enabled A70! Thank you!!! Worked perfectly! Maybe it worked, lol... It's found and installed it as a Android device in Windows, but ADB DEVICES sti...

Harfainx wrote: Then plug your 70 with ADB debugging enabled into your USB port. When it asks for drivers, point it in the direction of that file.

Enjoy your newly ADB enabled A70!

Thank you!!! Worked perfectly!

jackojack wrote:how about app storage?
how about the soft buttons in kindle???

thanks!

Kindle works great now, no cutoffs of the text

Not a bug, but Kindle now works OK. The softkeys don't cover the text.

mpar wrote:The update is available over wifi - go to settings/firmware update.

umm... ehh? We're not talking about the firmware here bud. (=

I called Archos and the 'A70S' ADB device driver isn't publicly available yet. Unless someone had a leaked version, we cannot ADB PUSH anything to the A70 yet.... no access!?? WTF? So now there are new magical things about development... and after I learned to code in java and C++... I can view min...

I called Archos and the 'A70S' ADB device driver isn't publicly available yet. Unless someone had a leaked version, we cannot ADB PUSH anything to the A70 yet.... no access!??

I cant even get ADB started. ADB devices report no devices found. I have USB Debugging enabled, but I have a A70s device drive missing which is probably the reason. Where is the A705 driver? Are we suppose to push the apks into /system/app? {edit} - I called Archos and the A70s adb driver isn't publ...

Please tell me that 2.2 fixes the lag. Archos 101 is close to the point of being useless because of the lag. EVERY action I do on it lags, and it lags like 20-30 seconds. I feel relieved when I grab my nexus one. Also, are we still due for this month's release? Maybe you have a runaway process/app....