[xaueious]

http://www.archos.com/support/support_tech/updates.html?country=us&lang=en&#firmDoes anyone want to try and flash this onto their device? It might not even boot but it will be at least an interesting experiment. Flash update.img from the SDK toolkit. Or some of you are probably good enough to know how to port this ROM right over. At the very least, frameworks and Launcher.apk should be compatible and should offer a performance boost immediately.

 

[jlove]

Hi xaueios,I did flash the image somedays ago. It does boot to the homescreen but touch doesnt work and some other things. It is not usable in this state. I think someone in this forum is trying to port it (looking into it myself)I did extract all the apks from the image and tryed them on the apad. Most of them work but the videoplayer does not.

 

[xaueious]

[quote author=jlove link=topic=448.msg3772#msg3772 date=1275369812]Hi xaueios,I did flash the image somedays ago. It does boot to the homescreen but touch doesnt work and some other things. It is not usable in this state. I think someone in this forum is trying to port it (looking into it myself)I did extract all the apks from the image and tryed them on the apad. Most of them work but the videoplayer does not.[/quote]If the videoplayer doesn't work, it is probably missing some stuff in system/framework or system/libCheck adb logcatAs for touch not working, flash the kernel only from the firmware update pack and you might get touch back theoretically.

 

[xaueious]

Sorry for the bump, but has this been tried?

 

[rogerbraun]

Any idea how safe the would be? I guess the service-mode like way that you flash the aPad won't be affected by the Android parts of the system, so you could still re-flash a device with a bad kernel. Am I right?

 

[xaueious]

update.img is no more than a repack of the .img files you flash, except you do it on the device itself. It should be no more dangerous than using the SDK tool itself.

 

[rogerbraun]

Yes, but I meant something different. I meant that if you flash your aPad with a bad image, you should always be able to recover using the SDK tool, right?

 

[xaueious]

[quote author=rogerbraun link=topic=448.msg4101#msg4101 date=1275437902]Yes, but I meant something different. I meant that if you flash your aPad with a bad image, you should always be able to recover using the SDK tool, right? [/quote]I was over at archosfan forums and it would seem so. But to be safe, unpack the .img files and flash only what you need

 

[rogerbraun]

Okay, so I tried flashing only the system.img of the Archos. This worked and resulted in the same system that jlove had: A working Archos that won't calibrate, as it will accept all inputs but always give an error in the end, saying it could not save the calibration (or something like that). I looked into the logs and noticed that two files in /lib/hw were missing. I added these (sensors.goldfish.so, sensors.rk28board.so), but this did not help with the touchscreen.Just to clarify, touches are registered, but maybe the position can not be read.The Archos-Rom works fine when used with a mouse.Any ideas how to get the touchscreen running?

 

[jlove]

@xaueiousI did flash the update.img of the Archos 7HT after that i flashed only the kernel of the update file.The Apad is very responsive to Keystrokes (Keyboard)I can start every apk that is on the device.The only problem is the Touchscreen. Touchscreen calibration pops up at the beginning but when I try to calibrate it just says "Failed to calibrate, Try again"Things that dont work:1. Getting into the settings because Touchscreen calibration pops up2. Touchscreen3. SDCard (Videoplayer / Fileexplorer does not recognize the SDCARD)So any help woud be appreciated. I think we can get this to work guys! EDIT: I did get into the settings menü: 1. Open up Fileexplorer2. Press Menu Button3. Choose "Manage Applications"4. Goto "Startup Wizard" 5. Get into the options and click "Force Stop" (I did the same thing for "Wizard")Now the whole system is working wothout saying to calibrate the touchscreenEDIT2: Did push a sample video to the devices through ADB and the video is playing better than on the original firmware (less choppy)I did find out that some of the functions in the settings menu are not present like "3rd party apk install" and some security related stuff like "fake location"

 

[DrunkenMessiah]

But the Archos firmware won't allow Market access will it as Google has blocked Archos from using it...?

 

[jlove]

You are right there is no market on the archos firmware

 

[rogerbraun]

Got the touchscreen to calibrate by replacing the Settings.apk ;DStill some issues, but is looking good.

 

[jlove]

Thats great, will try asap. What kind of issues do you have? Sdcard?

 

[bczeon27]

[quote author=jlove link=topic=448.msg4286#msg4286 date=1275483677]You are right there is no market on the archos firmware[/quote]The archos uses their own Market apk. I heard that it is not too bad.http://appslib.com/applications/index.html

 

[rogerbraun]

Yeah, SDCard does not seem to work, neither does USB. Also, the system will calibrate on every start. I made a hybrid aPad/Archos system.img which you can get here: http://www.multiupload.com/OADPZ2J4ESJust flash it instead of the original system.imgEDIT: sdcard works now, but usb still does not... Strange...

 

[jlove]

how did you get the sddcard working? please tell in detail, thank you

 

[rogerbraun]

Just replace /etc/vold.conf with the one from the original aPad firmware.

 

[jlove]

im such a noooob. i thought that the file has to do with the audio volumen so i didnt look into it :im such a nooooobbbbbb :-[

 

[rogerbraun]

haha, i thought so too at first ;-)I tested the firmware a bit and I rather like it. Calendar does not work for me, I can't get market to run, but Android Comic Viewer and RoboDefense work great, both would not work for me on the original fw.