yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] zenulator:
why arent you just using the ext2 image? that boots fine for cdma verizon vogues with no existing data.img.
[Touch CDMA Android Development] enatefox:
I needed to change a few things, kind of forget but the ril, had to enable the wifi services (even though it's not working..) and some other stuff. This is meant to be easy for people to test

I've left just the cached dex files, app manifests and some basic files like wifi and apn settings in this data.img and it worked right away. A few people are in the same boat.
[Touch CDMA Android Development] kb7sqi:
The new tattoo dump is uploaded & as long as I don't have to work this evening, I'll be doing my own port. Mostly for fun, but I saw the new kernel/rootfs img w/ better camera/tattoo wifi support so that peaked my interest a great deal. :D
[Touch CDMA Android Development] enatefox:
Seems the camera isn't working on Sprint Hero.. using pmos69's updated rootfs.img and 10-15 kernel. Could be that app, my tweaked system image, the alignment of the stars, whatever. Oh the joy of bugfixing
[Touch CDMA Android Development] zenulator:
is data working with the libhtcgeneric-ril.so with the sprint hero? Also did you put the needed libs in for audio/gps/camera?
[Touch CDMA Android Development] enatefox:
I can't test that but wifi certainly isn't. Could be in the rootfs.img though. Your ext2 image is fine btw, it was the data.img (dexopt I guess) but I did make a couple of changes as I mentioned and it was mainly to be an easy one for people to use/test. Can you tell me if the camera's working for you?

Whatchutalkin bout with the libs? I thought you did-- the image I uploaded was sourced (still mostly) from yours.
[Touch CDMA Android Development] zenulator:
no that ext2 image is a straight port no additions at all except for the apn xml. so /system/lib is untouched. and you might need to add files to /system/bin reference a working hero build. the build.prop was also untouched. i only created the sysinit.rc so the correct bootclasspath was because the regular hero.init.rc doesnt work. thats why there is custom.build and not hero.build
[Touch CDMA Android Development] KERKEDAGAIN:
k..so here's the Sprint user report: 1st boot, no data but calls come thru immaculately. Says it can't read my call settings so i can't switch to roaming or anything..i'm rebooting to see what's what..

*edit* so i've rebooted twice n notice that i get a "no telephony/new data store" message each time...could be reason why i have no data?
[Touch CDMA Android Development] enatefox:
Now that you mention it, I remember you said it was untouched. Ok, shouldn't be too hard. I did edit build.prop for the ril and wifi settings but nothing else. I did a quick pass over things and obviously not thorough enough. I'd say not bad for the second one to come out.
[Touch CDMA Android Development] zenulator:
i wonder if our modem init scripts are conflicting since the sprint hero seems to have its own settings.
[Touch CDMA Android Development] zenulator:
you need to edit sysinit.rc for the ril....point it to /lib/libhtcgeneric-ril.so
[Touch CDMA Android Development] TheKartus:
Not sure what my issue is. I love the look of the build, esp. the green highlights. The two options I see in text settings is "touch input" and "parfield keyboard." The touch input is the silly grey one.
[Touch CDMA Android Development] hudhawk:
Can't boot past the splash screen

So I've been stuck on a build from June because any of the newer builds I try on my Verizon Touch never boots past the splash screen.

Any ideas? I'm trying the latest everything here (Hero build) and having the same issue.

This stuff's gotten horrendously complicated over the last 5 months. A million forked builds with no discernible advantages, multiple install processes with no documentation (I gather flashable installs work now? I downloaded one of the zips and it had a radio.img in it which I had no idea what to do with)... good lord it's confusing.

EDIT: One important detail. I'm running radio version 3.42.50. Is that new enough, or do I need to upgrade the radio? Where can I find the latest radio and flash tools?

EDIT 2: Never mind; the Hero build wouldn't work but the Donut build did. It seems a little off though (odd graphics issues, locked up when I tried to launch the market) but it does work.
[Touch CDMA Android Development] KERKEDAGAIN:
boss..you sure you're using the latest build n did you let it create a new data store? cuz i was running it n it defly had touch input...very sexy lookin too, i might add
[Touch CDMA Android Development] enatefox:
no. This always happens the first time you boot hence the "new data store" message. It's indicating that the telephony.db is being created. I don't know why that's verbose though.

"service ril-daemon /system/bin/rild -l /lib/libhtcgeneric-ril.so -- -d /dev/smd0" is there already.

You said to check bin. Can't believe I forgot that wlan_loader is symlinked and I forgot to add wlan_loader2...

Uno momento. Should have something better if I can get the libs correct. When I post something new I'm going to attach a diff to the post so you can quickly see what's up.

Also, some screenshots would be nice. People are complaining that there's too much goodness which I don't get but maybe some pics would help

hudhawk, all I can suggest with what you wrote is you're failing somewhere. Could be you're trying Hero without setting resolution to 320x480 and you might need the premade data.img I uploaded (for that reason).
[Touch CDMA Android Development] KERKEDAGAIN:
yehh...i know but it shows every time i boot. also when i open the dialer it gives me a message saying "dial *228 for init programming" when i do i get the guy who tells me i've dialed an incorrect code. seems its not recognizing me on my sprint network cuz the roam guard shows up with each call..
[Touch CDMA Android Development] enatefox:
You have Sprint right? Zen's data.img gave me the *228 thing too. The clean one I uploaded doesn't but I'm on ATT. Calls are working though right-- it's just a warning message?
[Touch CDMA Android Development] hudhawk:
Ok... I'm getting closer. I got a different system image to book (Villord's Ion build). Everything works except that I get a message that the process "Media" has stopped unexpectedly. If I open the gallery it gets caught in an endless loop of "Process media closed unexpectedly" errors.

I'm rebuilding my data file again to see if that works.

Isn't that data.img for Sprint vogue's? Will it work w/ my Verizon phone?

EDIT: Rebuilding my data file seemed to work! Looks like I'm all set for now.
[Touch CDMA Android Development] KERKEDAGAIN:
Yes, I'm on sprint and calls come thru perfectly!! (calls do, not sound however) N i wouldn't even call it a warning so much as an alert
[Touch CDMA Android Development] KERKEDAGAIN:
data stores aren't carrier specific, mainly just build specific
[Touch CDMA Android Development] zenulator:
yea vogue-android is for stable. vogue-hero is now the developers test site. the top of this thread has info for tattoo/donut and hero builds. alot of the hero builds and rogers builds are pretty stable if you can stand the slightly squashed resolution. xrom 1.3 and the themed cupcake are also stable. donut/tattoo/motoblur/pulse beta right now so test but dont expect it all to work. and welcome back. well get more organized soon. its hard supporting six phones and 20 different builds.
[Touch CDMA Android Development] enatefox:
If we're not supporting six phones and 20 different builds then we're just not living.
[Touch CDMA Android Development] zenulator:
we could just stop doing this and use winmo
[Touch CDMA Android Development] kb7sqi:
Those are dirty/fightin' words there! LOL :D
[Touch CDMA Android Development] enatefox:
i hurd wm7 is going to be like vista for our phones!
[Touch CDMA Android Development] kb7sqi:
ROFL....I think we need to just work on the Tattoo build. It sure looks nice on my kaiser. :) Initial boot was a success...Testing now.
[Touch CDMA Android Development] zenulator:
get audio working!!!!
[Touch CDMA Android Development] zenulator:
I added Type-XXXX to the google code site. So when you upload a hero image use Type-Image Type-Hero Type-Stable if your uploading a stable hero image. I also put in Type- for cupcake, donut, tattoo, hero, blur, pulse, rogers and stable, beta, alpha, development, misc etc. so that will make things a little more organized for other people just checking out what we're doing. Also there is some stuff on there that i have no clue what it is and some seem to be just for kaiser so that needs to be specifically mentioned.
[Touch CDMA Android Development] enatefox:
Cleaning that up a bit
[Touch CDMA Android Development] zenulator:
also added Type-SenseUI for that up coming Magic/Sapphire SenseUI ROM ;)
[Touch CDMA Android Development] enatefox:
every time I mess with the camera, gps and audio libs I get the power messages endlessly-- no splash screen. Zen?

And what do you know of this new SenseUI ROM?
[Touch CDMA Android Development] loserskater:
You're not alone... had that problem last night.

What's the difference between the audio/camera/gps in the rootfs and the ones in the system?
[Touch CDMA Android Development] enatefox:
They're different.. the ones there now are for the Sprint phone. All I did was change the basic files. There's other "service" libs and such that I didn't touch. Honestly if I have to go through every combination it will take a year.

I'm going to try to make a hybrid while I search for some Magic Sense
[Touch CDMA Android Development] loserskater:
Right... I'm just wondering why they need to be in both places. I'm working with tattoo and tried changing each of the four individually and some combinations, but all of which ended up with power wakes...
[Touch CDMA Android Development] enatefox:
What do you mean both places? /lib and /system? This has got to be the most frustrating part of porting
[Touch CDMA Android Development] zenulator:
don't change the audio files. the camera and gps should be fine. there is one lib in /system/lib that throws a fit if you replace it. use adb to find it..... should be something like "failed to start XXXX.so because xxxx.so could not start because of fubar.so ect.... you'll find which one to take out. and they will stop complaining. basically it's a cascade/domino effect. take one out and they all fall. ideally these libs should be removed and you just use the ones in rootfs since there are conflicts and no point in having the same libs in two different places. the sysinit.rc should point to the lib PATH as /lib:/system/lib so it looks in /lib which is in rootfs first then /system/lib if there are conflicts then you get the crashes. or you can just edit the lib PATH to just /system/lib and keep all libs in /system/lib so there is no confusion. the only problem with this is that when updates come you would have to rebuild the whole system instead of just updating the rootfs.img with the new libs. but it doesn't matter since nobody is working on the libs anyway.
[Touch CDMA Android Development] loserskater:
I mean both in the rootfs /lib and the system /lib. I'm learning so I'm just kinda confused on why we need them in both places.
[Touch CDMA Android Development] enatefox:
So, considering there's 125 files there.. would you happen to know which one that is? It's taking me 15+ minutes to transfer 180MB system.ext2 to my phone while I do this..
[Touch CDMA Android Development] zenulator:
you can push pull while it's trying to boot up. try to pull all the audio related files. then replace with audioflinger.so and audio.so. so files like a2dp.so and libaudioeq.so ect. this is all from memory so.....have fun.
[Touch CDMA Android Development] enatefox:
Just so many dependencies.. I don't think I can just overwrite all the /system/libs with /lib though. Guess I'll try it either way though. Off topic (not really) but anyone have a good way to transfer files from Linux so I don't have to use crappy Activesync in VBox? It's as slow as the overall Windows experience and keeps erroring on me. Still don't have a SD adapter that's not broken.
[Touch CDMA Android Development] zenulator:
you can drop the extracted rootfs.img to a windows folder and open two adb sessions one with logcat running and one to push/pull stop/start. so watch logcat and pull a lib then stop start to restart the android init process and you'll see the results. basically mediaserver can't start because of the audioflinger/audio.so we have that works. so you fix that and all should be good. you also could drop all the sapphire related files in /lib/hw and change the board type to sapphire in the build.prop but you might get copybit errors.....try not to rip out too much hair.
[Touch CDMA Android Development] enatefox:
You're saying that mediaserver is showing the power messages (barrel roll of doom) because of audioflinger/audio? I'll try but do I have to do this while it boots are can I do this at any point and then stop start it?
[Touch CDMA Android Development] zenulator:
yes you can push pull libs while it's powercrapping. do the right thing and it will boot without having to reboot the whole phone. android keeps trying until you reboot or issue the stop command. if your in adb shell you can issue the stop command. make a change. since your already in the android shell you have access to /lib anyway so you can copy the libs from there.....etc.
[Touch CDMA Android Development] zenulator:
the new tattoo is in german or dutch.......
[Touch CDMA Android Development] enatefox:
powercrapping is now a meme
[Touch CDMA Android Development] zenulator:
u need to lay off the b boards for a little bit. or you;ll be trying to run android inside android while you're running android.
[Touch CDMA Android Development] enatefox:
So, we can run Android, use RDP to connect to our PCs running the WM6 emulator running VMWare running Android x86 port running RDP to connect to the main Android OS. Perfect harmonious loop. It's like if you looked down the Grand Canyon and saw yourself staring back at you
[Touch CDMA Android Development] pmos69:
sorta like this: http://www.youtube.com/watch?v=UNo6pn-dnSQ

;)
[Touch CDMA Android Development] zenulator:
wow....ask and i shall recieve. btw is there anyway to move FSCK0000's to their own folder i'm collecting quite a few.
[Touch CDMA Android Development] enatefox:
It always struck me as odd that the partition it fsck's is where the log goes. So, logcat is a catastrophe probably because I'm GSM

I'm done with Sprint for the time being. Looking at kb7sqi's now
[Touch CDMA Android Development] zenulator:
http://htcpedia.com/forum/showthread.php?t=930 the tattoo rom source.
[Touch CDMA Android Development] mush2699:
i give up no matter what i do on any release i keep getting a black screen with htc logo on it right after hero logo. the screen will go to sleep and i will have to unlock phone, i can even raise and lower volume but i have no desktop but the htc logo. can anyone help thanks. I am using latest build files and i have tried hero, m22 and jacheroski all with same result. Help i am not a newbie just having a brain fart thanks. P.S i did have ion and cupcake working on this phone and sd card already
[Touch CDMA Android Development] enatefox:
mush2699, I uploaded a blank data.img for that very reason. I get that too on many of them. That's the fix.

Zen, you think we could drop English into the Russian one? Seems theirs is always a newer number.
[Touch CDMA Android Development] mush2699:
im sorry i checked google code page where is this blank data file thanks again?
[Touch CDMA Android Development] zenulator:
what phone are you using? sometimes that screen will take 5 mins or so depending on the hero build. I've never had that problem. I'm on a cdma verizon vogue. So people with that problem should report what phone they have so we can find a solution to that.
[Touch CDMA Android Development] enatefox:
This is for the Sprint ROM but it should still work for you. You said you're not a noob so if you can get ADB or the terminal, you can remove the entries for the apps in /dalvik-cache and /data that are Sprint related. I don't think it's a problem to just use it but you will probably get better results if you do. I'll make a new blank data.img for regular ol' Hero once I've finished MoDaCo's 2.6 in a minute.

You would simply do like this:

rm -r /data/data/com.mobitv.sprint.tvwidget/

for example.

I agree about a solution. I am almost positive it's dexopt. I think that the ones that have the problem are ROMs with odexed apps. How can I test that?
[Touch CDMA Android Development] mush2699:
sprint touch sorry thanks for the help
[Touch CDMA Android Development] zenulator:
I posted links to the google code sites at the htcpedia site. Vogue and kaiser have there own threads there as well. we could take it over with android specific stuff or just stay here since it's pretty established.

Edit: ah i have to post 12 times before i can post links there.
[Touch CDMA Android Development] enatefox:
Hmm so seems that after I started to work on MoDaCo's I saw the build.prop is for an older version than Blurry Hero I was copying from... I wonder if that's a made up # because I can't find 2.73.411.17 anywhere else on the internets. (1,000 posts-- where has my free time gone?)
[Touch CDMA Android Development] zenulator:
modaco doesn't make up numbers. might have been an old build prop or that's the correct version. anyway wait until the magic sense ui comes out. that should blow hero away since it's made for a lower spec phone.
[Touch CDMA Android Development] enatefox:
I'm looking into Tattoo. PM'd pmos69 to see where things are at. I'm hoping it's nice and wifi is working until we can get our dirty hands on that Magic ROM. It's hard to find anything on it for sure. So, do you know how I could test that dexopt is causing the boot problem? Found a nice guide by JesusFreke on deodexing that spells it out pretty clear I just don't know if doing that will prove that's the problem.
[Touch CDMA Android Development] bug666:
the tattoo audio issue isnt kernel related is it?
[Touch CDMA Android Development] loserskater:
I have the newer tattoo build booting ( and that's about it) and with the new rootfs, wifi works. I can upload to gc if you'd like
[Touch CDMA Android Development] enatefox:
Please do, it's 1.67.1100.7 you got right? bug666, I really don't think so (I wish I knew kernel dev) but not 100% sure on that.
[Touch CDMA Android Development] loserskater:
yes. And uploading now.
[Touch CDMA Android Development] enatefox:
You're the man. I was commiting another 15 minutes to test out my first try with a guide written for Hero. Saved me the anguish at midnight.. That will free me up to theme it to look like Hero. I really dislike the grey look.
[Touch CDMA Android Development] loserskater:
I was also wondering this but I agree with enate... I'm pretty sure it's not.
[Touch CDMA Android Development] zenulator:
tattoo/donut audio isn't kernel related. it's the libaudioflinger.so and libaudioeq.so you can tell in donut where some files play right and some don't. i never finished getting tatto the same as donut. i have an audioflinger that will play perfect audio but it causes resets when making calls. so i took it out. the libaudioflinger that donut is using now is for the cupcake/ion builds. so it needs to be tweaked a little if anyone wants to check out the source for it and tweak it be my guest.....
[Touch CDMA Android Development] enatefox:
I can only imagine what it took to get Cupcake's audioflinger to work on Donut. You got the source? I can't promise a miracle but maybe I can catch something.

I know that Pulse is kind of a dead subject but I really like the Launcher for it. Has anyone looked into it? T-Mobile renamed it and have done something crazy with the setup so I don't know at this point how to port it over but I'd love to have that on other ROMs. 9 panel zooming desktop... it's as close to my Compiz desktop as I can get for a phone.
[Touch CDMA Android Development] zenulator:
i ported the pulse launcher to xrom............what a mess. it works but a lot of force closes. so i kept adding apks and libs and frameworks until it was more pulse than xrom.

for tattoo/donut audio you need to pull the donut source to get the libaudioflinger source. the one for the g1 works but plays distorted. should be just a few edits here and there. but nobody seems interested in looking at it.
[Touch CDMA Android Development] loserskater:
Info for the new tattoo img

I'm retarded. More work than needed
[Touch CDMA Android Development] enatefox:
o rly? You got source to share? I know you gave up on it and I did to. Remember when Wal Mart was pushing gOS as the economy Ubuntu (oxymoronic term I know) computers? That's what Pulse feels like to me. But the launcher is pretty special.
[Touch CDMA Android Development] zenulator:
what else did you do to the image? cause it boots if you just pack up the system.img after you unyaffs it and put tattoo.build in /system.
[Touch CDMA Android Development] loserskater:
I tried that and it wouldn't boot... I didn't really do much to it, just uploading for other people. Also added taskiller so you can kill the processes bogging down the system without having to setup apn and what not.
[Touch CDMA Android Development] zenulator:
it booted for me fine with no modifications. did you add anything to /system/lib or change the build.prop?
[Touch CDMA Android Development] loserskater:
Nope. I originally changed the audio/camera/gps but realized that was causing problems and replaced it back.

I'm trying just a straight repack again to see if it boots

EDIT: weird.. it boots now.
[Touch CDMA Android Development] arleybarros:
Google Wave will be perfect to this colaborative docs and discussion.

i think that the simultaneous translation will take development to a new level and also speed the things up a lot.

those who heave one hour to know it better, watch this video:

http://wave.google.com/help/wave/about.html#video
[Touch CDMA Android Development] jamezelle:
i know i was thinking about that a little while back..

and YES it will
[Touch CDMA Android Development] zenulator:
yea i was going to ask if anyone got invites?
[Touch CDMA Android Development] ajclai08:
Im trying to find the best files for Tattoo on kaiser. Trying to get wifi, audio, and power savings to work on one build. The latest kernels have no audio but power savings works. Tried a kernel from 09-13 with no bluetooth fixes and audio worked but no power savings.
[Touch CDMA Android Development] loserskater:
Which tattoo build are you using? With the latest one, I just tried the zImage from 9-13 and still have no audio. And according to zen audio isn't kernal related.
[Touch CDMA Android Development] ajclai08:
*double post*
[Touch CDMA Android Development] ajclai08:
Im using the pre-sdk build and the 9-13 kernel for me gets audio...just doesnt go to sleep..trying the sdk version now. I'm pretty sure audio is kernel related,ask dzo. 9-13 kernel has no bluetooth, so audio doesnt get messed up. Not sure what was done in the latest builds but audio works fine in donut, power-savings..just no wifi.
[Touch CDMA Android Development] arleybarros:
OH MAN!!

i was being sutil, that was the second step...
[Touch CDMA Android Development] enatefox:
Careful with Wave invites-- I know most of you aren't running Windows but it's become "the next twitter" of malware and viruses. Don't click the "lolz clikc heer haha 4 ur FREE Vioce Invitez!!11" because apparently a lot of people are.
[Touch CDMA Android Development] arleybarros:
unfortunately I have to use windows because of the ADOBE products...

Today, I finally managed to run unsquashfs in windows, and i'll begin to understand better the things...
[Touch CDMA Android Development] enatefox:
arleybarros, since you're in Brazil you happen to know anyone with the new Magic phone? You would be legendary. Maybe sweet talk a rep into getting a backup? I would learn Portugese if it came down to it
[Touch CDMA Android Development] arleybarros:
This things take a long time to get in south america, but tell me exactly do you need...