yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] enatefox:
It might already be (only) on sale down there.

http://www.htc.com/br/product/htc-magic/overview.html

At some unknown point time the rest of the world should be getting the upgrade
[Touch CDMA Android Development] arleybarros:
last night i downloaded a image "system-tattoo(1.67.1100.7)" and is not there anymore.

is working VERY GOOD.
[Touch CDMA Android Development] enatefox:
It was after midnight here and I missed the download. Care to share?
[Touch CDMA Android Development] hudhawk:
Dear god no. Even booting back into Windows to copy the files to my SD card is painful. I can't imagine ever having to use it again.
[Touch CDMA Android Development] arleybarros:
no audio...

still want?

i'll read some posts back that zen mentioned how to get audio working (with some bugs) and see if i can do something...
[Touch CDMA Android Development] enatefox:
You say it works great so I want to compare it to the raw ROM I got and the one I quickly threw together to compare. I'm working on audio too. If you have the image as an ext2 image you can edit it on the phone. It's the audio libraries in /system/lib that you'll need to swap around. It will probably powercrap instead of showing the splash screen. That's when you ADB in with two windows-- one to view logcat and the other to get to the shell so you can swap around the files. Once you've solved the mystery, it will boot right after.
[Touch CDMA Android Development] aross6:
Anyone care to share system-tattoo(1.67.1100.7)??? I can't seem to find it anywhere and if it's a good working QVGA Tattoo Image I would love to check it out!!!
[Touch CDMA Android Development] arleybarros:
i'll post the link when upload finishes...
[Touch CDMA Android Development] aross6:
Awesome, Thank you! Everything working... Gmail, Market, Phone, etc.???
[Touch CDMA Android Development] arleybarros:
noooooo....

long way to that...

i'll pm enatefox the link because tere's a lot of work on that...
[Touch CDMA Android Development] xxbabiboi228xx:
Just to let the community know you have to use the Zimage from the basefile

9-19-09 v2 fixed audio no bluetooth

to have working audio in Tattoo
[Touch CDMA Android Development] arleybarros:
rootfs-15-10-09v3.img
[Touch CDMA Android Development] xxbabiboi228xx:
rootfs-15-10-09v3.img? Are you asking me if i used that rootfs yes sir i sure did it has working wifi for tattoo.Thats whats been setting me back from using the tattoo build because i dont have the data package with my carrier.
[Touch CDMA Android Development] KERKEDAGAIN:
k...so i finally got the ext2 squashed and i transferred it to my sdcard, renamed it, and i'm getting a failed to mount /system error n no boot..whatd i do wrong?
[Touch CDMA Android Development] enatefox:
system.ext2? It's not squished.. ext2 is uncompressed
[Touch CDMA Android Development] KERKEDAGAIN:
sorry, forgot to mention i mounted it n ran mksquashfs..then transferred THAT .sqsh file to my card
[Touch CDMA Android Development] enatefox:
It's user error but you didn't give enough to figure out what exactly. What version of squashfs-tools did you use? 3.1 or 3.4? If not, there's your problem.

I'm going to release a new rootfs.img in a little bit. There's some bugs I caught. Copying apps to /data is broken and there's some other errors at boot. I'll also upload a new system for it later on that should fix some other things. I'm adding a startup script that will kill the insane amount of apps that start in the background to save you the trouble of immediately opening Task Killer. Once I upload, I'll post here along with a diff log.

I'm liking Tattoo, we just need to get some things addressed before it can really be taken seriously.
[Touch CDMA Android Development] zenulator:
The apps not copying aren't rootfs errors. So don't go changing thing in the rootfs. The error is in /system/bin. Trust me. And the tattoo build I have up is the one you should be looking at to get /system/bin right. These new builds aren't much different than that build just updated a little. You can prob just replace the app and framework dirs and have it all work.
[Touch CDMA Android Development] enatefox:
It's init or or one of the rc's right? I forget atm which but one of them does the copying part-- what do you mean it's in bin?

Also, after irritation regarding scrolling in the terminal, I have found a fix I'll share. I put nano on my image and don't feel like pull/pushing but you can't scroll since the shell history slaughters everything. Here's the fix (Linux/Mac):

adb shell telnetd &
adb forward tcp:9999 tcp:23
telnet localhost 9999

But you have to set PATH to match so do a regular adb shell and copy "echo $PATH" and all will be well.

Guide including howto for Windows
[Touch CDMA Android Development] zenulator:
The path on first init looks at /system/bin the right files aren't there. I know I went through it with the last port. Just swap /system/bin with the one from the tattoo build I already had out.
[Touch CDMA Android Development] enatefox:
In progress. What do you mean about framework? 10-03 doesn't have working audio or are you referring to something else?
[Touch CDMA Android Development] zenulator:
Im saying that the update most likely is only updated apps and frameworks so put the apps and frameworks in the 10 03 build.
[Touch CDMA Android Development] enatefox:
I got you, the extra bin stuff is messy. I did the opposite-- put yours over the new one and it killed itself. While I'm transferring your system image with the new stuff dropped on, I thought I'd share the diff. Cleaned up a bit because no one's putting the right wifi files, who cares about the legal notice file, etc.
[Touch CDMA Android Development] plemen:
I'd like to try this myself... where can I get the latest tattoo? Enatefox - can I get a copy of the latest tattoo from you?

Thanks.
[Touch CDMA Android Development] enatefox:
It's on the site:

http://vogue-hero.googlecode.com/files/CLICIMG_Click_HTC_BE_1.67.1100.7_release_signed.zip

Just grab what Zen said and drop onto his 10-03 one.
[Touch CDMA Android Development] plemen:
Ok I have that one already - I thought there was a newer one. I'll give it a go.

Thanks
[Touch CDMA Android Development] GODZSON:
As per request..

http://www.filesavr.com/sprintherosystemfiles

http://www.filesavr.com/sprintherosystemapps (Footprint widget, Stock Widget, and More ... Sprint TV works on 3G networks T-Mobile Tested)

http://www.filesavr.com/ruuherocsprint1296511signedrelease
[Touch CDMA Android Development] enatefox:
I would love to be able to copy the apps, bins and framework over from the new Tattoo to 10/03 and not have a black screen after the logo. Oh to dream... Anyone have luck with that?
[Touch CDMA Android Development] zenulator:
I'll fix the new tattoo later tonight. If no one else does.
[Touch CDMA Android Development] plemen:
Same here - tried framework, bin and apps and just app & framework - boots to black screen.

Gonna check out logcat and see what is going on...
[Touch CDMA Android Development] zenulator:
Did you look at the diffs in the /system/bin between the two tattoo builds. Basically you need to take out those files linked to toolbox and replace them with unlinked binaries. And add the extra files. I'll be home late tomorrow night so I can upload it then.
[Touch CDMA Android Development] plemen:
I'll try this later tonight - I want to get this working just so I know how to do this...
[Touch CDMA Android Development] TheKartus:
Nice. I'm really looking forward to a solid Tatoo build. It just look so nice.
[Touch CDMA Android Development] enatefox:
Zen, yeah I really didn't look through it when I downloaded it but when you said to check it, it was pretty clear most was raw from the dumped image. I put the new apps, bin and framework. I bet bin but know framework is messing things up.

I can still log in just fine while the screen's black. The boot splash process is running so I know at least that's where it's freezing. I don't know what is happening to the boot before the splash process is terminated as I don't know what calls it. That would probably narrow it down. Know where to look? I'm trying again but will be more careful with the framework.
[Touch CDMA Android Development] zenulator:
Did you swap the folders or just drop in the files?

And dzo has the git repo for libaudio if anyone wants to make it work for donut/tattoo.. you'd need to pull the donut source and the sdk and make the correct donuts changes.
[Touch CDMA Android Development] enatefox:
I did both. Your app, bin and framework on the new one and everything but those from the new one onto yours but same result.

I've been trying to figure out what to do if I gitted libaudioflinger and the ril.. any hints?
[Touch CDMA Android Development] zenulator:
Ok two part answer. For tattoo take the /system/bin from the 10 03 build and put it in the new build.

Second for audio you need to look at dzo's git source and apply that to the donut source and recompile. Nothing needs to be done with the ril. The one pmos did works great with donut. Tattoo just has proprietary pieces in it that are incompatible as well as wcdma support that most likely are the causes of the force closes.
[Touch CDMA Android Development] pmos69:
the donut ril isn't in the repo yet. (vilord is still missing and I don't have push rights in that repo)
[Touch CDMA Android Development] plemen:
Cool - I can't work on this until Monday - do u mind posting what u had to do to get it going? Thx
[Touch CDMA Android Development] enatefox:
Updated to 1.67.1100.7, wifi working.

No sound yet. Any time I touch etc/ or framework/ the system crashes complaining of stale dependencies in random apps' odexes, libraries are missing, etc.

If you don't care about a ringtone, here you go. No sense uploading it to GC-- this is for devs and the curious. Diff file of Zen's 10/03/09 and this version attached.
[Touch CDMA Android Development] scottter:
I haven't been caught up in a while, was there ever a workaround for the hero sms error messages?
[Touch CDMA Android Development] myn:
Is there something special that needs to be done for the nano-hero?

I am using the basefiles (basefiles-20091009.zip)

with my default.txt as follows:

set cmdline "ppp.username=mobile@jamamobile ppp.password=telecom mddi.width=320 mddi.height=240 msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=0 board-htcvogue.panel_type=3 no_console_suspend"

When I boot up it hangs at the HTC screen where the little android guy peaks out and keeps looping through this sequence. I let it sit there for over 15 mins.
[Touch CDMA Android Development] loserskater:
change mddi.height to 480
[Touch CDMA Android Development] kb7sqi:
KB7SQI's new kernel/rootfs.img w/ compcache-0.5.4-test2 uploaded

Hi all,

I had time today after staying up all night w/zenulator on gtalk, lol to compile my own kernel for the Vogue/Kaiser. Now, I'll be honest..I have no problems compiling for my G1. This was my first Vogue/Kaiser kernel, but the good news is it works as expected. I used the exact same config as dzo's latest build & his source w/ the added bonus of adding lzo support directly in the kernel so no modules are needed & I patched the kernel for compcache-0.5.4-test2 swap_free_notify support. The rootfs.img I uploaded along w/ the kernel to vogue-hero must be used w/ each other. The lasted compcache-0.5.4 test2 when used w/ the swap_free_notify patch should really help out on our phones. I'm testing it on my kaiser now after running it for 24 hours on my G1. Feedback/testing would be appreciated. Here's the files needed:

zImage.kb7sqi

rootfs.kb7sqi.img

Next on my list is to attempt to build a new libaudio. ;) Take care.
[Touch CDMA Android Development] tatnai:
so, in lay-man's terms, what will be the difference using these files instead of the base package and latest zimage?
[Touch CDMA Android Development] aven_soulgazer:
I kept up with all the android builds up until the cease and desist put out by google. Now it's gotten all sorts of complicated and can't figure out what to do to get android working again. I just got my vogue replaced. I got a refurb unit and it is already messing up as well. Bah. Need another replacement. I've been through 7 or more of these phones because I've had such bad luck with them messing up on me. I'd go with Touch Pro but not sure how the android project is working on that model.
[Touch CDMA Android Development] GODZSON:
Just a follow up.. is the sprint.sqsh being worked on..? do to the keyboard not working/popping up? Looking forward to footprints/stock being on it.. Impressive work to all of you.
[Touch CDMA Android Development] enatefox:
I can't figure out how to get GSM working on it. Stocks and Footprints are in there but they don't seem to be working. Probably a framework dependency. I haven't been able to get the libraries to work just like Tattoo so sound, camera, GPS, etc. are not working. If I could at least use it I could work on it more. However the apps seem to transfer to other builds pretty nicely. If only I could figure out how to simulate 3G so I could use the SprintTV widget.

aven_soulgazer, this is the latest
[Touch CDMA Android Development] xxbabiboi228xx:
Unable to start wifi on Tattoo builds for us kaiser users
[Touch CDMA Android Development] enatefox:
Not sure what happened here but a heads up if you want to try to fix the rootfs.img. You can do this on the phone since / is read-writable. Push these files from pmos69's v3 rootfs.img and it should work. The parts about compcache won't be affected:

/initetc/apns-conf.xml

/initetc/ppp/ip-up

/initetc/ppp/options.smd1

/lib/libcameraservice.so

Missing: libhtcgeneric-ril-diamond.so (not so important I don't think..)

/lib/libhtcgeneric-ril.so
[Touch CDMA Android Development] xxbabiboi228xx:
Running Tattoo 10-3-09

I cant push nothing through without a terminal and i cant get a terminal installed without a file explorer because for some reason market doesnt have all the apps it used to have like 3 days ago its like they got rid of most of the apps.
[Touch CDMA Android Development] enatefox:
I meant with ADB from your computer. That way you can get the files from the other rootfs.img:

mkdir rootfs && sudo mount -o loop rootfsv3.img rootfs

and push:

adb push rootfs/initetc/apns-conf.xml /initetc/

for example.
[Touch CDMA Android Development] plemen:
Switched over to these - I'm using your rogers build and this seems to make it even faster. I used to notice a 3-4 second lag opening the messaging app - now it opens much quicker... same with everything else - contacts, calender, astrid, gmail - this is a huge improvement... thanks!
[Touch CDMA Android Development] polyrhythmic:
Testing out your new zImage and rootfs on Blurry Hero (and latest 15-Oct basefiles) -- Working GREAT! /proc/swaps reports all compcache with 75MB swap, 33MB free.

It's much snappier now than with the previous settings. Now, upping the swap to 98Mb.....

EDIT: Running great, 98MB total, 53MB free!

This new compcache makes this build responsive enough to use on a daily basis, I believe. Now if I could only get it to support the 528Mhz overclock, like the old ION build...

Thanks for the hard work, dudes!

EDIT2: Why are we limited to 98MB of compcache?
[Touch CDMA Android Development] enatefox:
You're not limited. You have a little over 100MB available after the ROM, radio and drivers are loaded. The setting is the virtual size of the compressed disk. This says you can effectively drop the entire memory footprint into the container which a faster system makes-- any more is counterproductive.
[Touch CDMA Android Development] clockworx:
This boots to a white screen for me (panel type 3 and it is in the config, so I don't think that should be it). Did I miss something? I'm using both the rootfs and zimage.
[Touch CDMA Android Development] enatefox:
What build are you running and if you have the SDK, can you take a screenshot and see the home screen even if the phone's screen is white? That happened to me with the Pulse build until I flashed another ROM
[Touch CDMA Android Development] polyrhythmic:
Does this kernel contain dzo's modifications for settings clock_7x00.slow or clock_7x00.voltage?
[Touch CDMA Android Development] zenulator:
it's all pulled from dzo's latest so everything that he's done so far is in there. it's dzo's kernel with some patches.
[Touch CDMA Android Development] silex:
I thought the latest basefiles was dated 10/9/2009?
[Touch CDMA Android Development] clockworx:
I'm running one of NFSFan 6.5's (v12 or something, haven't gone back to upgrade it in a while because oh god I hate winmo so much). I don't have the SDK, can I do a screenshot via adb or any other way?
[Touch CDMA Android Development] enatefox:
Well, the white screen is a common issue for WM ROMs when users flash the wrong ROM/radio combo or other reasons. It happened to me with Pulse and my ROM so if you can flash from your SD card it would be pretty quick to test. Best I can offer you since we don't have that issue it has to be your setup.
[Touch CDMA Android Development] silex:
I get the white screen error too.
[Touch CDMA Android Development] silex:
I get the white screen too. It only starting happening when I tried out kb7's rootfs and zimage files. It usually happens to me with the wrong panel type and/or resolution. Try adding lcd.density=120 to your default.txt to see if that fixes it. I will report back on my findings.
[Touch CDMA Android Development] zenulator:
you get the white screen on what? doesn't make sense. what builds are you trying to boot. the new zImage and rootfs.img aren't that much different than the others just some modifications mainly compcache related. nothing major.
[Touch CDMA Android Development] silex:
This is preliminary, but I swapped back to the 10/9/09 basefile zimage and rootfs and everything is back to normal.
[Touch CDMA Android Development] enatefox:
The white screen thing is problem I had with Pulse and (I don't know if this ROM was specifically the cause) Solace 3.1. Putting the stock ATT ROM made it work right away. Haven't had the issue since.
[Touch CDMA Android Development] silex:
That's the weird thing. On the blur and pulse builds I would use lcd.density=110 or 120 otherwise I would get a white screen. I don't know it's related, but definitely something up. I don't think it's files, but more like the wrong combination of files and/or options being run. I won't rest until I figure it out so you guys will be hearing back from me soon.
[Touch CDMA Android Development] silex:
Did both you guys just swap out these files with no other additional changes? No deletions, recompiles, nadda? Trying to figure out why myself and other other person is getting a white screen.

What I can say so far is that it doesn't seem lcd.density related. Maybe it's ROM related?
[Touch CDMA Android Development] silex:
Weird....on any build I go back to the 10/09 files and the ROM's work again. I'm stumped unless the guy's who hae gotten it working tell us what, if anything, they did in addition to just copying them over.
[Touch CDMA Android Development] zenulator:
what kind of phones do you guys have and what builds are you trying to boot? and yes i just used the new rootfs and zImage kb7sqi put up nothing more. like i said there just minor changes specifically for compcache. no more module loading. thats it.
[Touch CDMA Android Development] silex:
Sprint Vogue. Tried the same builds that were mentioned being successful (Roger's and Blurry Hero) as well as the new system-motoblurv0.76.sqsh that was just uploaded.

I think I have a larger issue at hand that's all these I/O errors I keep seeing on compile. Do I need to reformat the card or something? I can't even create data.img files anymore. I mean they create, but end up being corrupt and have to reboot. Did all the copying and moving back and forth of files corrupt my partition somehow? How do I fix this?
[Touch CDMA Android Development] pmos69:
Compcache is not magic ;)

Compcaches's compressed swap is created using physical memory.

The larger the "virtual swap" you create, more physical memory will be used.

Problem is, you cannot use all physical memory for compcache because, in the end, compcache provides swap, not memory, and both the kernel and running programs need real memory to run.

Swap, compcaches's or disk swap, is usefull to "swap out" inactive programs, but you still need real memory for other stuff.
[Touch CDMA Android Development] enatefox:
Try to flash another (or maybe the same) ROM again and see if it fixes it. I had to as well. Fixed white screen and data.img issues
[Touch CDMA Android Development] zenulator:
are you saying that every build has a white screen? or just pulse?
[Touch CDMA Android Development] xxbabiboi228xx:
Is there anybody thats working on Tattoo are native resolution rom?
[Touch CDMA Android Development] plemen:
What do u reckon is the "sweet spot" or optimal size for compcache?
[Touch CDMA Android Development] zenulator:
yes eventually.....those updates don't bring much more than whats already up.
[Touch CDMA Android Development] enatefox:
xxbabiboi228xx, Tattoo is Donut. Still working on it but if you don't mind audio it's okay to use. I haven't tested GPS or the camera yet but I guess those are almost done. Follow Donut for the updates as Sense is almost a drop on for it as far as what's being worked on

plemen, I set cc disk size to 101MB (that extra megabyte..) and leave the conf the same from the bundle. Works great for me-- hovers around 40-60MB used.
[Touch CDMA Android Development] silex:
At the moment, all of them. I believe I fixed my I/O errors and data.img woes though by reformatting the flash card as FAT32. I will retest the new files with Hero and see how it goes. Crossing my fingers!

EDIT: Same issue. Is everybody using 'board-htcvogue.panel_type=3' ?? I usually see the white screen with the wrong panel type number is used.
[Touch CDMA Android Development] enatefox:
Silex, if you have HardSPL, just flash the ROM over again or a different one. I've been through this and it sucked but the second I did it was fixed and never happened again
[Touch CDMA Android Development] zenulator:
theres supposed to be auto detection in kernel. but maybe you need to set that in your default.txt. mine is set to 1 for a verizon vogue.
[Touch CDMA Android Development] silex:
3 has always worked for me for a Sprint Vogue. How do I do a HardSPL? I'm running NFSFan WM6.5 ROM.
[Touch CDMA Android Development] jamezelle:
do you have bootloader 2.31.coke

check by holding powe plus camera then poking soft reset while holding both power and camera. the bootloader screen will come up and your bootloader/spl version should be there

if it is 2.31.coke you can flash any rom with gps enabled
[Touch CDMA Android Development] KERKEDAGAIN:
yehh...so i, too, am on a sprint vogue w/ the white screen of doom..flashed to a new ROM and still the problem remains w/ the new zImage & rootfs..

i'll try redownloading the files n see if that changes anything..
[Touch CDMA Android Development] silex:
Yup, 2.31 coke.

Looks like it's not that isolated.
[Touch CDMA Android Development] kdub94:
request for MLIGN-hero porting

I was searching through the threads, and found an interesting hero build at http://xdaforums.com/showthread.php?t=573209.

it would be an amazing port. For example, it has a transparent lock screen. Please port this :)
[Touch CDMA Android Development] 2girls1cup:
it also would be nice to have that jacxheroski 1.8 ported to vogue/kaiser.
[Touch CDMA Android Development] enatefox:
kdub94, I'm looking through it now while I'm working on my own theme. I like the lock screen..

and JacxHeroSki 2.2r4 is out and it's very nice.