yashsingh1/xdaforums huggingface dataset:
[Touch CDMA General] Nick N:
I love this version of Android, very nice. I am currently running it on an regular FAT32 4GB class 6 MicroSD.

My only issues are delay (shows Loading...) when returning to the home screen when holding the camera button down for a few seconds and also a text message delay when it is sleeping. I received text messages at 12:45pm and did not get them until I woke the phone up at 2:45pm. I am using the zImage3 from the 2.01 thread, I have since replaced it with the one from 12/09 from the sourceforge site. We'll see what happens.
[Touch CDMA General] Kiiv:
You can change "cc_disksize" in tattoo.user.conf from 24 to 48 to reduce the reload problem. Trying with 64 may remove it totally.
[Touch CDMA General] DallasW:
I'm having issues trying to flash this to my Touch...

Firstly I've been using WinMo recently so I'm completely new to the flashing to NAND stuff, sorry for the likely simple questions.

Here is what I did:

-Flashed "androidinstall.zip" to my phone. I thought this was the above build at first. It flashed properly and all seemed to work fine, but this was apparently faster.

-Now I am trying to get this on there, so what I did was boot into recovery mode, and placed the following files onto the SD card (empty)

tattoo.user.conf

system.sqsh (tattoo version on SF)

rootfs.img (newest version from today)

systemfsonand

rootfsonand

Now, it seems to copy rootfs fine, but when it tries to copy the sqsh file it take about 1 min and then tells me it's out of space?

I'm not sure what to do from here to flash this to NAND, and also I'm not sure if I'm suppose to flash an empty data.img or what I'm suppose to do with that.

Thanks for the help in advance!
[Touch CDMA General] jamezelle:
yeah...i wouldnt use zimage3 with this build. that zimage was made to force eclair to sleep i would only use it with eclair. it is only a half fix anyways. use the zimage from the basefiles. and you will have notifications when they come in
[Touch CDMA General] drewden123:
I'm running into this issue as well...NAND has always worked for me.

EDIT: Just wait about 30 more seconds when it says "no space available" and it will continue
[Touch CDMA General] DallasW:
It does continue on for me, but never seems to boot into anything. I didn't wait super long though, maybe that's the problem...
[Touch CDMA General] jamezelle:
the system is to big to fit on nand, thats why you get the out of space on device errors. afaik vilord is making a nand version so be a little patient ;)
[Touch CDMA General] drewden123:
Awesome. So...am I doing anything horribly wrong to my phone by running it off nand? Or is that why it seems slower than senseui usually does?
[Touch CDMA General] jamezelle:
how did you get it running from nand? i mean i know how to do it but how did you do it?
[Touch CDMA General] drewden123:
I didn't know this wasn't made for NAND so I just followed standard procedure. i.e. copied system sqsh to sd, copied rootfs to nand, blank data, added ""tonand files. the usual and it just works.
[Touch CDMA General] Reddog80p:
Thats what I did but got the write error..no space on device...did you see this also?

BTW: you have a link to a blank data.img?
[Touch CDMA General] Hakukoru:
I got the out of space error too when trying to flash to nand. So something I tried to do was extracted out the system.sqsh, moved the app & media folders out and added symlinks for them pointing to /data. Then I made a new data.img with app_sys and media_sys (what the symlinks were pointing to).

(Essentially I copied jamezelle's instructions from here with a few modifications: http://xdaforums.com/showpost.php?p=5087279&postcount=8 )

It booted fine off SD.... but if I copy them to nand, it won't fully boot. I keep seeing errors of /system being read-only. Not sure what I'm doing wrong, but I would love to have this on nand :S
[Touch CDMA General] drewden123:
Yes, I got that error but just waited about 30 seconds and everything went smoothly :confused: . For blank data img, just open up notepad or something similar, then click "save as" and click the dropdown box and select "all files" rather than "Text files" and save it as "data.img"
[Touch CDMA General] jamezelle:
your lucky it booted. the out of room on device error means everything didnt copy from system.sqsh to your nand. you might have a lot of errors or sluggishness due to missing files :rolleyes:
[Touch CDMA General] drewden123:
I really wish I could help you guys...Idk what to say I just did the usual nand install and got the out of space errors and then they went away after waiting a few seconds. If it helps...

-rootfs 1-06a

-tattoo sqsh (obviously)

-voguimg-240X320-06-01-10

-blank data.img

-datafstonand

-rootfstonand

-systemfstonand
[Touch CDMA General] drewden123:
Yea, it's somewhat sluggish but nothing more dramatic than any other senseui...

I've run into a couple FC's here and there but everything's running pretty smoothly. Actually, just as fast as plemen's donut aosp at times.
[Touch CDMA General] Hakukoru:
Out of curiosity, is the tattoo sqsh and data.img still on your sd card? With vilord's new builds of rootfs, if those are present it will boot from sd, but if they aren't present it will boot from either partitioned-sd or nand.
[Touch CDMA General] drewden123:
Yes, but my sqsh and data have always remained on the card for previous rootfs builds after i install nand. i.e. when I installed donut i did the same procedure, and when I navigated in my SD card the files were still there.
[Touch CDMA General] Reddog80p:
Must be a good karma thing ...lol
[Touch CDMA General] drewden123:
:D guess so lol
[Touch CDMA General] Nick N:
Changed to 64, will test. Thanks!
[Touch CDMA General] drewden123:
64 worked like a charm for me
[Touch CDMA General] Nick N:
Problem solved. Thank you.
[Touch CDMA General] Hakukoru:
Well booting from the sd card is a feature of the new rootfs. Previously the init file would check for the presence of a filesystem in nand, and if it was there boot it. But the new build will choose to boot the images off the sd card before booting from nand, as mostly a testing feature I'm guessing. (That way you don't have to trash your present working nand build in order to test a newly released build)

So it could be that right now you're simply running the images off the sd card instead of nand. You could try renaming the system/data images and see if it still boots. HOWEVER, since it is likely your phone will crash by doing this, don't do it unless you have an alternate way to edit the contents of your sd card to rename them back, as adb won't function if the build is crashed ^^;
[Touch CDMA General] Nick N:
Looking forward to the official NAND release. Will I notice an increase in overall responsiveness vs class 6 sd partitioned/nonpartitioned?
[Touch CDMA General] drewden123:
Well I have a microSD>SD adapter for my netbook. Everything on the sd is exactly the same as it has been before this new rootfs:

-system.sqsh

-rootfs.img

-data.img

Those are the only android related files on my SD (other than the ...tonand files)
[Touch CDMA General] drewden123:
I would imagine. I've been committed to NAND since it was available and I love it.
[Touch CDMA General] jamezelle:
yea like the guy in the op said try renameing system.sqsh to systemtattoo or something to make sure it is booting from nand.
[Touch CDMA General] abc321:
Sorry for all the questions... I noticed that I am not getting missed called notifications in the taskbar at the top of the screen, but the missed called shows up in my call log. Any ideas?
[Touch CDMA General] Reddog80p:
If you are running from NAND the "tonand" blanks should be gone after copying to NAND...I think.
[Touch CDMA General] drewden123:
yup. changed the file name to "systemtatt" and just booted fine!
[Touch CDMA General] jamezelle:
hmm thats strang yea i just noticed i am too.

yea they should NOT be there
[Touch CDMA General] drewden123:
They aren't
[Touch CDMA General] Hakukoru:
Very curious...

Now I don't know the specifics of the nand fs/partitioning... but are the 13mb root, 90mb system, and 128mb data partitions a permanent feature of the nand? Or were those partitions that dzo setup? Perhaps whatever NBH drewden is using has a different setup?

Otherwise the only other thing I can think of, is that Drewden is just extremely lucky, and somehow his system is "magically" functioning, despite ~40mb worth of files being missing from it :P

Oooor... does the systemfstonand installer somehow overflow some of the files to /data? O_o
[Touch CDMA General] drewden123:
Does it make a difference that on my SD card I have a 200 mb partition left over from pre-nand android?
[Touch CDMA General] nabicat:
Mine also reported the out of space error when flashing to NAND. Its worked fine however.

I took the system file and stripped a few apk's out that I never use, but that only saved a couple of mb.

The slimmer system.sqsh also triggered the error on the flash, but again, it works fine.

Missed call notification works fine for me with the files I grabbed from this thread. I see the notification on the lock screen, in the notification bar and in the call logs.
[Touch CDMA General] drewden123:
I'm in the same boat as you my friend. Pretty stable build if you ask me
[Touch CDMA General] Hakukoru:
Most definitely. My guess is that the *fstonand attempted to copy system.sqsh to nand, ran out of space and failed. Then it copied the data.img to nand. Since the *fstonand install doesn't delete the images, then the new rootfs installer would have also seen the system.sqsh/data.img and attempted to install them. And if I remember right, it chooses partition install over nand install if partitions are present. You did say you had to wait a long time for it to boot after it ran out of space, so it's possible some of that wait time was it copying the system to the partition.

The remaining question then, is if the new rootfs is attempting to boot using the data.img, or the nand /data?

Edit:

And now that I see nabicat is also still mysteriously able to boot, despite the failed nand-install... I'm now wondering if the system.sqsh and data.img are still present on his/her sd card.
[Touch CDMA General] drewden123:
Interesting. Well it really didn't take long at all...30 seconds at the absolute max. When I was using partitions it seemed to take quite a while to copy over but I could be wrong. So..am I almost running a partition/nand hybrid? or what. Sorry I'm really familiar with the whole process, etc. but not what goes on behind the scenes.
[Touch CDMA General] nabicat:
Both files are still there. I'll try renaming them when I get home to see whether they are being used.
[Touch CDMA General] Hakukoru:
Well I typically don't either, lol. I just know what I do about this current rootfs after going through the init with a fine tooth comb.

The previous rootfs I was using was the typical nand-only type, and I added in a small bit of script to the init file to make it prompt me to press VolDn to boot from SD instead. I wanted to know if it was possible to that do with Vilord's new rootfs, but I now know that it isn't necessary :P

Edit: And as for the parition/nand hybrid idea, I'm guessing that's correct. I was thinking it could be either part/nand or part/data.img, but you did say you renamed both the system.sqsh and data.img in an earlier test, so it must be nand.
[Touch CDMA General] drewden123:
Very interesting indeed. Glad I could be at the center of such strange discoveries!
[Touch CDMA General] Hakukoru:
I'm nearly tempted to try this method on my own to see if it works for me. I imagine running the system off of the partition is faster than running it off the compressed sqsh image. And then if I can put the data in nand, then at least I won't need 2 large partitions hogging up my SD card :P. Running strictly 100% from NAND would be nice in terms of conserving all of my sd-card storage for music/media/etc., but I'll take what I can get at this point xP
[Touch CDMA General] drewden123:
Yes. As soon as vilord updates with an official NAND build I will be upgrading to that and hopefully be utilizing nand only.
[Touch CDMA General] bmessina:
I've been running this off nand as well for the last 2 days. Runs like I remember tattoo builds running, not especially great, but it works for certain.

Similar to the other two people who've commented here, my system files are still on the SD card though.
[Touch CDMA General] drewden123:
See, but my system files have always remained on the sd card even after installing nand..? Were they not supposed to be?
[Touch CDMA General] Reddog80p:
The files you started with minus the 3 blanks should be there. How was your microsd card partitioned?
[Touch CDMA General] drewden123:
oh, ok that's what I thought. umm 200mb (maybe 250) ext2 i believe
[Touch CDMA General] abc321:
Just noticed an interesting quirk. When you store your voicemail number, if you put in the area code along with your phone number, then the voicemail answering for Sprint will not work if you don't pick up the call. That is, it will say "You have reached the voicemail box of (123) ..." and then it will repeat your full phone number with area code and prompt you to enter your password. If you leave out the area code in the voicemail settings, this doesn't happen. I didn't see this in the search...
[Touch CDMA General] Reddog80p:
Did you have a CONF folder with the tattoo.user.conf in it?
[Touch CDMA General] Hakukoru:
Blargh, not again. I swear that either this new rootfs hates me, hates my phone, or that my phone hates it. I recently tried formatting my sdcard with 2 ext2 partitions, in order to install this tattoo build on it, ran the installer, it claims it cant find the partitions, so I decide to boot back into my nand setup...... my data has been wiped somehow. Though looking through the init file in rootfs it makes complete sense to me what it's "supposed" to do, it's just every time I've used it so far, it ****s something up. Now to reinstall and reconfigure all of my apps aaaagain 8(
[Touch CDMA General] bangout:
what i did to get this working on nand

I was having problems getting this on nand, but i got it working by doing this. I put all the files in android folder using newest files also newest voguimg. I only used rootfstonand not data or systemfstonand. Also NO pre made data.img, just let it make a new one during boot. And now im up and running, fast and with plenty of system mem. Hope this is helpful.
[Touch CDMA General] Reddog80p:
Those of you who have ran this succesfully via Haret. What files are you using? I've tried using the 11/16 basefiles + 1/6/2010 rootfs and a blank data.img with no success..
[Touch CDMA General] sdawson:
Did you chmod the file?

chmod 777 /system/media/bootscreen/boot_animation.xml

You may not have permissions to edit it if you don't, otherwise you could try push/pull with ADB.
[Touch CDMA General] stopthebus:
I feel your pain, I went through a lot too, following is what works, for me at least.

My formated 8GB card.

1. FAT32 ~ 7GB

2. EXT2 ~ 500MB

3. EXT2 ~ 500MB

Everything goes to the FAT32 partition.

I know the rootfs is from 1-06a, not sure about the other files.

In any case, here's the whole thing.

Good Luck.

http://www.mediafire.com/?yyzmymm3mmz
[Touch CDMA General] TheKartus:
Am I better off with compcache or swap to speed this bad boy up?

Its also slightly slow to wake, is that a product of the image and the weight of the build or the rootfs or something?
[Touch CDMA General] Nick N:
I agree with the slow to wake, in fact my alarm did not go off this morning.
[Touch CDMA General] nabicat:
From my personal experience, enabling compcache helped reduce the rosie reloads, but actually made wake-up slower.

Even with rosie , compcache and swap disabled, wake-up can be problematic.
[Touch CDMA General] TheKartus:
So I should take the speed from swap and not risk compcache slowing down wakeup anymore.
[Touch CDMA General] TheKartus:
Android installer is giving me 2 errors.

First: Its telling me that it cannot make the temp directory since it already exists

Second: it tries to install the new system.sqsh and then "ext2fs_check_if_mount: no such file or directory while determinning whether /dev/block/mmcblk0p2 is mounted"

If I wait it says completed but it looks different than the old rootfs.

Is this normal now? There used to be a lot more text.

EDIT: After all that, it went through the rest of the boot and then I got a black screen. I reformatted and am trying again.
[Touch CDMA General] Reddog80p:
Thanks this worked for for me. I just added everything from the .zip except the linux folder. I also made a CONF folder and added the user.conf to it.

The build is pretty decent for me. I'm having the rosie issues tho and cant seem to get rid of it.
[Touch CDMA General] ajclai08:
p1=fat32

p2=ext2-128mb

p3=ext2-128mb

p4=linux swap-32mb
[Touch CDMA General] sassagelink:
Can't get it to boot.PLEASE HELP I'm a newbie and I'm stupid to all this.

When it tries to boot I have a screen with the Linux Penguin up top and then it says:

.....................

Rootfs loaded

SD card already mounted... not running a disk check!

tee: /sdcard/bootlog.txt: Read-only file system

checking for partition...

No sys found on SD. booting Part/NAND

Creating a new Data store

dd: can't open /sdcard/data.img's : Read-only file system

Failed Failed to allocate the storage

I downloaded all the following:

basefiles-xxxx.zip

system-xxxx.img or system-xxxx.sqsh

updated zImage-xxxx

updated rootfs-xxxx.img

I formated my SD card to Fat32 and put the Andriod folder on the SD root along with the System.sqsh.

My SD card is only a 2gb. Is this a problem? Please help i don't know where to go from here.
[Touch CDMA General] TheKartus:
You just don't have room. Reformat the card and only put on the files you need and you'll be fine.
[Touch CDMA General] tatnai:
Actually it is a problem with the new rootfs 2010-01-07. I have an established donut build on sd card, swapped to this rootfs, and got the same error. Switched back to rootfs 2010-01-6a and all is fine again.
[Touch CDMA General] sassagelink:
I tried it using the older Rootfs file and it gets farther but I still get he following:

losetup: /dev/block/loop: no such file or directory

Failed

Failed to find system.img on sd card

Should I be putting the system.img or sqsh in the andriod folder? The instructions say to put it on the root of the SD card.
[Touch CDMA General] tatnai:
either put everything in the root of the sdcard, or everything in the /sdcard/android folder.
[Touch CDMA General] sassagelink:
Buttons and Keyboard??

This worked great andriod started up. I dont know what my back button is? There are only the Answer, End, Center button, Power button, Camera button. The keyboard for typing also does not fit to the bottom f the screen. Do I have some display settings wrong? My phone is a HTC touch from alltel. But I think it is the same as the vogue but I'am probably wrong.
[Touch CDMA General] Hakukoru:
On most Android builds for the Touch/Vogue, the camera button functions as Back, or Home if you hold it down. The power button displays the menu, or if you hold it for about 1 second it opens/closes the keyboard, or hold it much longer and it will rotate the display. The End button powers off the screen, or just locks the phone if you double-tap it. The Call button, VolUp/VolDown, and Arrows/OK buttons all function as they normally would.

The only time this was different was on some of the very first builds of the kernel.

Edit: Forgot to mention, the power button also unlocks the phone.
[Touch CDMA General] stopthebus:
Strange, I don't have a problem with the reload except when it first boot up or after a reset.

So far, the only problem I have is with the caller id. It does not recognize any of my contacts.

It just shows the number, which is exactly the same as stored in contact, and not the name and then ask to save the number when the call end.
[Touch CDMA General] Hakukoru:
Has it done this with previous Android builds, or is this the first Android build you've used? It might just be that your contact list is missing the area code? I don't exactly know how precisely the numbers must match in order for it to associate the stored contact to the incoming call.
[Touch CDMA General] stopthebus:
I've tried:

Zen's Eclair 2.0.1 in various releases

Zen's Donut in various releases

Plemen's Donut in various releases - like this the most, so far (installing maps is a pain though)

They all work fine.

The only different this time is the HTC caller id instead of the default Android from all the other releases I've used.

All my contacts are from google, so it's the same sync no matter what release I use.

How do you setup your contacts? I used the (xxx) xxx-xxxx format.

Any help would be greatly appreciated.
[Touch CDMA General] loserskater:
Quick answer: This is a common problem in Hero builds, and there is not a fix.

Long answer: I'm not 100% sure about all of this but I believe this is right... The ril (how our phones talk to the network) we use is a community built one (mainly, if not entirely, built by vilord) and Hero builds use a closed source ril so we can't exactly just tweak it to work. There's a lot of logging and debugging that has to be done in order to get the Hero builds to work perfectly with the ril we use. I'm sure it's something that will be fixed in the future but right now it just doesn't work.
[Touch CDMA General] BigBadBuu:
Great build--easily the smoothest Hero UI i've used on Vogue.

Only problems are:

- lagged incoming phone calls

- super slow home screen reload

- home screen refreshes info that should already be cached

Are these problems fixed by installing to NAND? To me, it seems there's some sort of cache missing that's causing #2 & 3. Any thoughts on this?
[Touch CDMA General] TheKartus:
Try SenseHero, its fast also... Unless you like QVGA which is what draws me to the Tattoo build. It just looks so pretty.
[Touch CDMA General] bandur:
data (re-)connection problem solved

Hi Vilord, since this thread is called "Tattoo and new rootfs" I want to report that since I changed to 7/1 the rootfs I no longer have the problem of the modem disconnecting without reconnecting again. That has been a problem for a while, but now it seems to have been solved. Thanks, -- sorry if it posted in the wrong thread.

I am kaiser user, currently on plenems donut sys. image.
[Touch CDMA General] Reddog80p:
Tried to run Pandora today and I got a message saying it was not currently available model: Bahamas

Anyone else experienced this...Is there a fix?
[Touch CDMA General] enatefox:
stopthebus, I believe that you need them in 1-(xxx)... format. Someone (forget now) from Europe had that issue with an ION version and his carrier needed the international format. I forget what he did, you'll have to search, but it apparently fixed that. It's worth a shot maybe even if I'm being as vague as possible.

BigBadBuu, about the SenseHero, if you grab the ril (/system/lib/libril.so) from it you can get faster incoming calls. The delay is specifically caused by HTC's ril.
[Touch CDMA General] BigBadBuu:
Oh, definitely. But it's also about hand usability--SenseHero just doesn't seem to behave as nicely when dragging and selecting items.

@ enatefox

I can't, for the life of me, get ADB to work. I had a Hero setup on this PC before and that all worked perfectly. I then downloaded ADB2 package from sourceforge, but I keep getting either a) "phone not found" or b) driver install problems--any ideas?
[Touch CDMA General] SuperJMN:
I've been using this build for a few days and I think it's slower than Eclair, but it's more stable. Do you know whether a new Tattoo build will be released or not? I really like the integration with social networks, like Albums and Contacts.
[Touch CDMA General] sassagelink:
Keyboard

Why is the keyboard so small? I think I am using the hero build but I'm new to all of this and can't be to sure. Is there any way to make the keyboard span across the entire screen?
[Touch CDMA General] ajclai08:
You need to set lcd.density=120. I'm guessing yours is set to 110..from previous donut/enclair builds. No need for that since this build is optimized for qvga.