ROM work for Archos 80 Cobalt?

[bluesmanuk]

I didn't try a restore as I had spent a lot of time getting the set-up just right and didn't want to have to do it again.

Yes I was just looking in the backup folder.

The blobs folder does contain hundreds of entries and was quite large at 317Mb, so seems as if it has probably backed up after all.

Cheers

[bluesmanuk]

I decided to test the restore capabilities of CWM 6, so I took a full first back-up which was the basic ROM without any changes (after taking a belt and braces backup with 5.8).

Then I configured the ROM and added loads of apps etc and ran the backup again.

I then re-applied the ROM to it's basic level so that I could easily see that the restore worked from all the changes that I made.

When I restored using the second back-up, virtually nothing had changed at all.

None of the new apps and configuration were present afterwards.

The only changed thing that was restored was a boot animation that I had been playing with.

The process seemed to have completed without any obvious errors, so not sure what is happening.

When I then restored the 5.8 backup all went smoothly.

Now I understand that with CWM6 using deduplication it should be a more efficient method of backing up but at the moment I'm very hesitant in using it.

Has anybody else tried restoring using the new CWM?

[900supersport]

Re: ROM work for Archos 80 Cobalt?

Thanks sounds as though system has restored by not userdata. I'll look into it myself.

[bluesmanuk]

Thanks.

I trawled the net looking for postings of similar incidents and whilst I did find some instances, there seemed no clear explanation of my it happens, except perhaps where backups are renamed when using DUP, rather than TAR files.

I did find more information about the latest versions of CWM though and new features are the ability to choose between the new and old style of backup and the ability to flash to zip instead of a backup folder, which seem like potentially useful options.

I don't know if you have also seen this site, which purports to be able to be an easy way to build a new up to date recovery from an existing one (I think).

http://builder.clockworkmod.com/

[Gilly10]

Hi 900supersport,

Can you possibly help with creating a 4GB parameter file?

This one here is 3GB, leaves around 2.95 for Apps & 3.17GB for User Data etc.

CMDLINE: console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00002000@0x00002000(misc),0x 00004000@0x00004000(kernel),0x00008000@0x00008000( boot),0x00008000@0x00010000(recovery),0x00100000@0 x00018000(backup),0x0003a000@0x00118000(cache),0x0 0600000@0x00152000(userdata),0x00002000@0x00752000 (kpanic),0x00100000@0x00754000(system),-@0x00854000(user)

I've been doing trial & error and managed to get 3.9GB or so for Apps but I guess some of the entries I put were wrong as the internal SD card corrupted & even after factory reset didn't sort it out so was useless.

I've tried switching extenal SD with internal as well with vold.fstab but that ended up with it sticking at boot, I don't really wanna go that route anyway would rather use the internal memory rather than mess with SD cards.

The 6GB one you kindly provided is good but only if you can get the SD card swap working, I've ran into problems with apps that download extra data due to the low user space (leaves around 180MB) which fills up very fast.

Thanks

[bluesmanuk]

I am using the 6Gb model and this is my vold.fstab. Everything works fine for me and the almost full space which is now the external card is totally redundant. I had it sticking at boot as well until I modified a couple of parameters in the file as recommended earlier on in the thread, at which point it all worked.

## Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##


#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################


## Example of a standard sdcard mount for the emulator / Dream
# Mounts the first usable partition of the specified device
#dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
#dev_mount flash /mnt/external_sd auto /devices/virtual/mtd/mtd9/mtdblock9
dev_mount flash /mnt/sdcard auto /devices/platform/rk29_sdmmc.0/mmc_host/mmc0
#dev_mount sdcard /mnt/external_sd auto /devices/platform/rk29_sdmmc.0/mmc_host/mmc0
dev_mount sdcard /mnt/external_sd auto /devices/virtual/mtd/mtd9/mtdblock9
dev_mount udisk /mnt/usb_storage auto /devices/platform/usb20_otg/usb
## Example of a dual card setup
# dev_mount left_sdcard /sdcard1 auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
# dev_mount right_sdcard /sdcard2 auto /devices/platform/goldfish_mmc.1 /devices/platform/msm_sdcc.3/mmc_host/mmc1


## Example of specifying a specific partition for mounts
# dev_mount sdcard /sdcard 2 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1

[900supersport]

The 0x0600000 corresponds to 3 gig app space

0x0600000@0x00152000(userdata)

Change this to 0x0800000 for 4 gig, don't forget when you do this you need to adjust the following so they all start a gig later

so

0x00002000@0x00752000 (kpanic),0x00100000@0x00754000(system),-@0x00854000(user)

would become

0x00002000@0x00952000 (kpanic),0x00100000@0x00954000(system),-@0x00A54000(user)

[Gilly10]

The 0x0600000 corresponds to 3 gig app space

0x0600000@0x00152000(userdata)

Change this to 0x0800000 for 4 gig, don't forget when you do this you need to adjust the following so they all start a gig later.

Thanks a lot, seems the last entry was the one I kept getting wrong, anyway will try that tomorrow

Also if the tablet were for me personally I'd take a closer look at getting the external SD card working as internal but for now I just want it up and running & 4GB is more than enough right now.

[tomaquet]

6gb plus internal to external sd

I'm thinking of implementing the 6gb rom plus convert internal to external sdcard. Can people that have already done this give some feedback please? I saw that some people mentioned the reduction in battery life. But how is the fluidity/speed in general? And what about apps that have some data on the external sdcard? Do they still run as smooth?

I have a 32gb installed which just has some films and fotos on. The cobalt often has problems with the external sdcard, failing to recognise it (have to physical remove it sometimes as the option to mount it disappears). In the notifications, it keeps asking to mount/unmount it. I'm worried that if I change the internal sdcard to be the external sdcard then it'll create problems.

All comments welcome!

[DudeyGeeza]

I'm thinking of implementing the 6gb rom plus convert internal to external sdcard. Can people that have already done this give some feedback please? I saw that some people mentioned the reduction in battery life. But how is the fluidity/speed in general? And what about apps that have some data on the external sdcard? Do they still run as smooth?

I have a 32gb installed which just has some films and fotos on. The cobalt often has problems with the external sdcard, failing to recognise it (have to physical remove it sometimes as the option to mount it disappears). In the notifications, it keeps asking to mount/unmount it. I'm worried that if I change the internal sdcard to be the external sdcard then it'll create problems.

All comments welcome!

You can still only use the 6gb apps space for apps as any moved to SD with the "move to SD" option (as this will then move them to your micro sd that you mount as internal memory in this configuration) will dissapear after a reboot, but i will keep the 16gb card i have mounted as internal, makes no difference really. Shame the rom has this "move to SD" issue where apps just dissapear after a reboot, but hey... the 6GB apps space seems plenty!

[tomaquet]

Thanks for replies both here and on HUKD!

Yeah, I wont bother moving to sd if I have 6gb of app space, but some apps (typically large games) install part of the app on the internal sd automatically. So I assume, it'll save this part on the external sd. Is there any noticeable slowdown? And do you have problems with mounting your sdcard?

[DudeyGeeza]

Thanks for replies both here and on HUKD!

Yeah, I wont bother moving to sd if I have 6gb of app space, but some apps (typically large games) install part of the app on the internal sd automatically. So I assume, it'll save this part on the external sd. Is there any noticeable slowdown? And do you have problems with mounting your sdcard?

apps that are too big and auto put the rest on your micro sd mounted as internal seem to play fine, and dont moan about the data not being there, it's only the apps that you actually use move to sd on that dissapear..

Im using the new supersport rom and cannot really see any difference in battery usage but i dont use my tablet for more than an hour or so anyway.

[dodemans]

study the post re adb. We then need to pull update.img if this is good then I can make you a ROM.

Could u make a overclock rom :P?
Would be epic

[tomaquet]

otg disabled?

Sorry to drag this thread back from the dead but I have a small problem.

I currently have my Cobalt 80 set up as follows.
Rooted with 900supersport rom (February version).
Changed app space to 6gb.
Swapped internal sd for external sd (vold.fstab)

I’ve recently tried to use a usb memory stick using a USB OTG cable and it’s not recognised. I know the cable works because before implementing the above changes (ie on stock rom, non-rooted) I could use it with a PS3 controller on various games. I’ve tried various apps in the playstore to help mount various usb sticks (and the ps3 controller) but nothing recognises it.

Has something I’ve done disabled the OTG function of the table? How can I check? (it might just be the OTG cable has stopped working).

Cheers, T

[tinazen]

In the information era, people’s life is filled with hustles and bustles. Sometimes we just want a quiet environment to enjoy ourselves. Then you may need this RF Jammer masking for acoustic interference against listening devices.