yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] tatnai:
with a vogue, the boardpaneltype is autodetected and you do not need this in your default.txt (I've had this removed from my default.txt since dzo added this to the kernel a while back, no problems; pretty certain it was pushed to the git repo). also, if you get a white screen on some android versions and not others as was previously posted by another, it is not a boardpaneltype problem.

where in the process do you get a white screen, it sounds like you are booting far enough to get errors from within android, is that correct? boardpanel problems give a white screen right after hitting run on haret, so that is not your issue if you are getting further than that. it's something else.
[Touch CDMA Android Development] kb7sqi:
Hey all...For all the ones having issues w/ the white screen using my zImage/rootfs, can you try again w/ rootfs.kb7sqi.2.img on vogue-hero? In the previous rootfs.img, I had updated the apns-conf.xml file as well the init.rogers.rc scripts for my particular build. But those changes shouldn't have caused the white screen issues. The new rootfs.img is 100% stock besides the new compcache modules.

Sorry I haven't been around today...Been busy w/ work & I'm currently working my g1/mytouch build. lol...Never enough time in the day. :-)
[Touch CDMA Android Development] enatefox:
Ok, so I can't seem to get Phone and framework-res.apk themed without some horrible effects. Phone is okay but the phone stops working... Anyways, I just did basic theming of Rosie which is easy for me. I know it's OT but people here know the answers.. The bottom buttons are glossy and light up blue then amber.

If someone can help me with those 2 I can then scale them for Tattoo as well. Can't really show it off until it's done.
[Touch CDMA Android Development] jamezelle:
transparent lockscreen:p, they just didnt put a jpeg in the lockscreen folder, i did it by accedent once
[Touch CDMA Android Development] kb7sqi:
enatefox....Send me the original apk's & the ones w/ the "new" pngs. Let me take a shot at them for you. As far as for the Tattoo builds...You'll notice your icons are 36x36 instead of 48x48 & there's a different folder in the /res dir also.
[Touch CDMA Android Development] silex:
Just tried it with the revised rootfs and same white screen issue :( Could it be something with the zImage?

EDIT: Yup! I stopped using the zImage kb7sqi posted and it booted with just #2 rootfs and it loaded! I'm using the zImage from the 10/9/09 basefiles.
[Touch CDMA Android Development] zenulator:
where does it get the white screen? right after haret? if it does then it's the zImage. because the rootfs hasn't even loaded yet.
[Touch CDMA Android Development] kb7sqi:
silex...The only modification I did to dzo's latest configuration was apply the patch need for swap_free_notification needed for the new compcache & enable lzo as default instead of using modules. If you'd like to try 1 more rootfs.img, hit me up on gtalk. kb7sqi@gmail.com I really don't have many cycles to put towards this until I get my g1/mytouch build fixed, but I'll give it one more try.
[Touch CDMA Android Development] silex:
Correct, right after. I don't want to speak too soon since it's still loading from the htc logo screen, but it's booted so far. I'm testing with system-kb7sqi-magic.mod.themed.img to keep it consistent with the same cook (hehe).

What is the purpose of zImage? Does your version need to truly be paired to your rootfs kernel?
[Touch CDMA Android Development] kb7sqi:
Was my themed magic mod working fine for you w/ the stock basefiles & zImage? To answer your question, yes you need to use my zImage/rootfs.img because the new compcache modules are included in the new rootfs.img. I plan on getting w/ dzo to get all this merged. I just wanted to "share" w/ everyone since I noticed a big difference in performance w/ the new compcache.
[Touch CDMA Android Development] zenulator:
zImage is the kernel.....
[Touch CDMA Android Development] silex:
Yes, it was working albeit pretty slow but I think most Hero builds were prior to your new kernel.

I'm glad to to be the voice for the three of is having issues. I will continue to help testing as necessary. Just whistle three times and I will be there :)
[Touch CDMA Android Development] s0v3r1gn:
Not only does starting the thread make him god over the thread, but that fact that this thread is about HIS build sort of does make him god of it again... 2cents...
[Touch CDMA Android Development] enatefox:
Agreed on sharing links. I don't have a Vogue so I didn't know there was an issue and it's an older build now-- what he's done before and after are really impressive considering. We have about 1-2Mb of RAM free with Hero so for getting it to be as quick as it is at this point in development, let him keep control over his own thing.
[Touch CDMA Android Development] zenulator:
This thread is for zenulator's hero builds. Its in the vogue section. It's great that you managed to get wifi working. But the image is an old build doesn't work on my vogue. BTW thanks for letting me keep control over my own builds. I was concerned for a second. Anyway I'd put your modified build up at the google code site so people that need wifi can have it but i'd rather have the latest image up with wifi support. I'm sure it will be resolved sometime soon. Until then kaiser people use the modified image. I don't mind linking to the kaiser thread. I just don't want direct links to modified images.
[Touch CDMA Android Development] natefish:
Dalvik...for whatever reason, the shorter-named-one is working very well for me now. HTC widgets are crashing much less, if at all, and touchflo itself isn't crashing as much or taking as long to refresh if it does crash. Overall, the build just seems much faster than any other build before this one.
[Touch CDMA Android Development] zenulator:
I'm going to put out a new test build tonight. If you remember the backinblack builds this is along those lines. Black background small and fast with a couple new optimizations.

New build is up.
[Touch CDMA Android Development] mattcoz:
Ok, now I'm confused. I turned GPS on and it shows the weather now. My one problem is that the city doesn't update. It seems to have gotten the city from my GPS location, but it won't change depending on where I am. So yeah, the weather is showing, which is great, but it's not the right weather. :confused:

That said, the new build is working great so far. I definitely notice an improvement over the previous build. Keep up the great work! :D
[Touch CDMA Android Development] enatefox:
You can tell it to use the weather from My Location or a preset city. Are you travelling that far away that it's a big difference? You need it to lock your position or use wireless networks (all in Settings) if you're expecting it to update the location.
[Touch CDMA Android Development] gjbnh:
I see this as more of a quality control issue, not as someone who is stepping on toes . Since it's Zen's builds, he should run the show. I'm sure he would be open to input and submitted code, but he really needs to be the one who post's code, testing or "finished". Just be aware that his time is limited (real life has such a way of getting in the way lol) and it appears he has a path to improve things, so we really need to not make his life any more difficult by useless bickering. NUFF SAID.
[Touch CDMA Android Development] joannerve:
Still vibration-freeze problem when I delete widget or shorcut, so it´s not better to have an option for disable all vibrations? Its not a default.txt problem, no a sd card problem, no rom problem and no a radio problem.
[Touch CDMA Android Development] bangout:
the speed on the new test build is crazy, best build to date. thanks for the wonderful job
[Touch CDMA Android Development] enatefox:
The test one seems okay so far for stability. The load time is negligable except redrawing Rosie. I didn't do all the tests but it's clearly the best yet. I know that ubifs is supported on 2.6.27 kernel and the speed is significantly faster according to some benchmarks I read. Any chance of that happening? There's a script that can disable Rosie like Touchflo in WM6. It can be keymapped so users can toggle between light and full in one build. If I can get it working, I'll post back so you can look at it.
[Touch CDMA Android Development] mattcoz:
Where do I tell it that?
[Touch CDMA Android Development] natefish:
Zen, 8-15 hero build is clearly best yet. I was having a couple touchflo crashes after a while, but nothing that a soft reset didn't fix. Soft resetting is something us WM people are used to doing anyway, right? On former builds, soft-resetting didn't really help anything.

I'm just glad to have something functionally stable and fast that uses exchange. Thanks for the hard work and dedication to this project.
[Touch CDMA Android Development] natefish:
In weather app settings.
[Touch CDMA Android Development] NarSan:
system-081509.img is really fast, but wifi doesn't work, so I back to previously version with wifi (your first test system file)
[Touch CDMA Android Development] natefish:
Is there no one out there working on kaiser or wifi builds? It would be nice if there was. Not to sound mean, but us vogue users in this vogue forum really wish this wasn't a concern. But, I don't want inhibit anyone from sharing the bounty if that is what Z and others want.
[Touch CDMA Android Development] NarSan:
surely someone is working on this, there are already build's running wifi. I also knew if I would be helped, it is only me testing ...
[Touch CDMA Android Development] clockworx:
The issue w/ incoming calls not displaying contact info is an issue across all hero builds, right? Has anyone heard of any progress being made on that?
[Touch CDMA Android Development] zenulator:
which test build? i was being told that wifi wasn't working in previous test builds so i stopped including it.
[Touch CDMA Android Development] zenulator:
have you tried the new test build? i don't really use my phone like a phone if you know what i mean. it's more of a pda to me. sometime today or tomorrow i'll put out a complete hero build that i've had sitting around to test and see if what i've removed is causing it not to display the contact info during calls. the complete build will be slower because it will include everything the regular hero has and no optimizations or anything. for testing purposes i can see if it is caused by me taking parts out and replacing other parts with optimized ones or if it's just related to the fact that we're not running on the real hardware.
[Touch CDMA Android Development] zenulator:
make sure it's named zImage and you removed the .kb7sqi sometimes the extensions get hidden if your using windows or even in windows mobile.....
[Touch CDMA Android Development] silex:
^ Definitely checked to make sure this was the case. It was definitely loading it which is why I got the white screen to begin with.
[Touch CDMA Android Development] kb7sqi:
Silex...First I need an answer to my previous question.. Was my Themed Magic mod running fine for you prior to trying my zImage/rootfs? Was it working w/ the stock zImage/rootfs files? Secondly...Give these a shot these are up on vogue-hero also.

Edit: The Magic mod was working slow? That's news. lol...It's runs great on my kaiser...I had a new record of going over 26 hours before I had to reboot it. With the stock zImage/rootfs.img's I'd have to reboot every 10 or soon sometimes because of hangs. Thanks for trying. I really do want to try to resolve the issue for ya. :-)

zImage-kb7sqi

rootfs.kb7sqi.3.img

If you're curious about what's changed in the rootfs.img. Just in case the the original lzo_modules in the /lib/modules folder has been removed & the sbin/userinit.sh script has been modified to not try to insmod those modules because the zImage(my kernel) has this enabled/built-in instead of using modules. Everything else is the same. Just trying to make sure there's not a conflict w/ the modules & what's built into the kernel. :)
[Touch CDMA Android Development] plemen:
Guys - I've had similar issues in the past when dzo updated the zimage files. My images would work with older zimage and rootfs but not the new ones - I could switch back between old and new files and the results were always the same.

For me the problem was filesystem errors on my card - I plugged my sd card into my reader, did a scandisk in windows, deleted all of the basefiles and reloaded and things started to work perfectly with old and new zimage/rootfs.

If all else fails, reformat your cards and reload files.

my $.02...
[Touch CDMA Android Development] xxbabiboi228xx:
kb7sqi

kb7sqi can you possibly take dzo rootfs and pmos69 rootfs v3 and put them together so we can have wifi on Tattoo builds?

Nevermind just tried it wifi works thanks kb7sqi ok we have that now.ok i was using zImage fixed audio no bluetooth and sound worked on tattoo builds.With your zImage no sound
[Touch CDMA Android Development] kb7sqi:
Hi xxbabiboi228xx,

I'm glad wifi is working w/ Tattoo. I was suprised to hear that it was reported not to work. First off let me say thanks for the vote of confidence. dzo & pmos69 have been working on the vogue/kaiser stuff way longer than me! I'm quick to learn and I have to say zenulator & I have spent quite a few hours on gtalk...ie, him schooling me on the Vogue/Kaiser stuff. ;) I also had a great chat w/ pmos69 earlier this evening. I plan on getting w/ dzo later today & working w/ him on getting the new compcache-0.5.4-test2 patch integrated into his source. We also have a game plan on the rootfs images. Once that is done, things should get back to normal as far as 1 zImage and 1 rootfs.img for all. It works better that way for everyone involved. Trust me... Since I work on g1/mytouch builds, you have lots of different kernel/modules to play with. lol. So it's been nice working on the Kaiser/Vogue stuff. Swap a system.img & you're ready to go again. ;) Once all that is squared away, if pmos69 don't beat me to it, I'm planning on working on the libaudio for donut. I've been enjoying learn more & getting involved w/ this part of the android community. My intention by throwing up my new zImage/rootfs.img wasn't to try to take away from what dzo/pmos69 & everyone else has accomplished. I was just wanting to share the nice improvements that the compcache-0.5.4-test2 has over the older 0.5.3. I think things will only get better. :D I'm looking forward to having a build w/ native QVGA support as well. Take care.
[Touch CDMA Android Development] jamezelle:
im using your latest zimage and rootfs with a hero build just fine, no whitescreen, on a verizon vogue. thanks for your work and welcome to the team;)
[Touch CDMA Android Development] TheKartus:
What's the fastest hero/tatoo build? Any useable on a day to day basis almost like Ion? SMS still broken in all of them?
[Touch CDMA Android Development] jamezelle:
1 i would recomend zens nano or my v12

2 yes

3 yes sms error still exists, sms was never broken it still works
[Touch CDMA Android Development] TheKartus:
Thanks. Yeah, I just hate the error.
[Touch CDMA Android Development] 2girls1cup:
is anybody using kb7sqi's build? I am wondering if it has camera working with his zImage and rootfs.img
[Touch CDMA Android Development] kb7sqi:
Hi 2girls1cup,

I'll be honest...I've never gotten the camera to work on my kaiser w/ the Magic build. It's a bit different compared to your "normal" HTC Magic/Rogers builds in that it has a "little" bit of hero mixed in because of the added flash support. With the newer zImage/rootfs that dzo made, I've tried fxcamera & several other ones from the market, but haven't take a "clean" picture. It show's up green. I'm kinda partial to the Magic build since I use the exact same build on my G1, but I'll have to try w/ some other builds. Hope that helps. Now maybe others have gotten it to work, but I haven't. If you have, I'd love to know the secret! lol Take care.
[Touch CDMA Android Development] plutarcian:
first up THANK YOU. second sorry for the long post in advance but im begining to see a light at the end of the tunnel so here goes

ive been whining about this problem on the Google Android and Linux for KAISER!! thread for a couple of days now. the thing is that hero runs SOOO slow for me that its unable to recieve phone calls. from the time someone rings to the time my phone actually shows SOME notification is soo long that the other party recieves the caller not responding message. @enatefox suggested setting compcache to 100 ( 101 ??) and flashing the stock att rom. and that has helped but not enough to actually recieve calls. the phone SEEMS more responsive but still unable to respond quickly enough to letme recieve calls.

the new rootfs and zimage DO HELP. i just recieved my first phonecall in hero .. YAY .. but still no contact picture/name etc loaded up in time. only a green android, phone number of caller. i think the other stuff was still loading. any thoughts, ideas etc will help. im runnning the official htc rom ( dont have att tilt so ....) and ill admit its a bit slugish even in winmo :). Garmin.DK.10.Naked and witschey's Minimal 6.5 have been suggested in the other thread and i will try them when i get whome. other than that is there anything else that can be done to speed up phone recieveing???

forgive me for sounding noobish ..... cause i AM :). and thnks again.

EDIT:: ok android just kicked me out of network. there looks like im no longer registered with a network. ehhh. o well back to winmo :( :(
[Touch CDMA Android Development] JeckyllHavok:
Hey man, first of all thanks for the new rootfs files. If you want a working camera on your Kaiser, try my Umbrella Corp Rom, it has the working camera and will do nice and working pictures with proPaint Camera.
[Touch CDMA Android Development] plemen:
Stick with xrom, KB7sqi or cynagenmod - very nice non-hero builds with most things working - with the new files from kb7sqi these builds just rock. The delay in phone ringing keeps me away from hero...
[Touch CDMA Android Development] meekell:
Has anyone on the Sprint network been able to send MMS. I've tried a few Ion builds which worked good, but picture mail was unsuccessful. Too bad, I really want to get my wife off of windows mobile.
[Touch CDMA Android Development] TheKartus:
I don't believe that MMS is supported in any of the builds.... It is a feature that has been kind of put off for now with work being done to make wifi and bluetooth work. I could be wrong though, the situation may have changed.
[Touch CDMA Android Development] polyrhythmic:
MMS works excellently for me on ION builds on AT&T GSM network, but I have no idea about Sprint.
[Touch CDMA Android Development] plutarcian:
Dude this works

hey man. i have only used your ROM for abt 15 minutes and I CANT BELIVE it. i dont know if it was

clock-7x00.ahb_div=3 clock_7x00.slow=1 elevator=noop in the startup or something else but this build removes almost all of my problems. still havent used camera or sms but the phone calling works. atleast now i can receive phone calls without missing them :D :). will use it for the day tomorow and see how it goes. AMAZING startup screen by the way. WOW.

P.S. this is the first time i used lcd density 120 and the phone dialer doesnt fit :).

one more thing is that i still cant use my wifi for market. seems to work on the browser but not the market. i will try flashing a couple of roms and see wchich one works

GREAT WORK DUDE
[Touch CDMA Android Development] KERKEDAGAIN:
as an update..i've run a chkdsk, replaced the files, flashed a new ROM, n still the white screen on my sprint vogue w/ the latest kb7sqi3 zImage/rootfs combo (panel type parameter removed). verified that it DOES work w/ the previous combo. not complaining, just updating my finds..
[Touch CDMA Android Development] jamezelle:
it looks like its only on sprint vogues, i have no problem with kb7sqi3's zimage and rootfs
[Touch CDMA Android Development] mrkite38:
Could it be something to do with the panel type? I know my vzw vogue has a type 1, but my sprint has a type 3...
[Touch CDMA Android Development] zenulator:
im pretty sure its kernel related and seems isolated to sprint vogues. i havent had any problems with it.
[Touch CDMA Android Development] enatefox:
Which is odd considering you have Verizon CDMA so I doubt it is. There must be other kernels and rootfs.img's that work for Sprint. If people with those problems can post specific details we can help-- can't do much with generalizations. No problems here across kernels
[Touch CDMA Android Development] KERKEDAGAIN:
its just the latest kernel from kb7sqi that does it..if i use the latest from dzo it's all good..
[Touch CDMA Android Development] KERKEDAGAIN:
oops..dbl postage
[Touch CDMA Android Development] clockworx:
My understanding from doing LOTS of reading is that MMS is blocked on the server side of Sprint for WinMo devices (which still applies to us, even though we're not using WinMo)

More info here:

http://www.wmexperts.com/articles/editorials/sprint_mms_and_windows_mobile.html

God, I hate Sprint sometimes. But then again, I hate all the carriers for one reason or another. At least MMS is supported on the Hero if I go that route (and the Moment as well, I would assume)
[Touch CDMA Android Development] zenulator:
http://droiddoes.com/ bye guys.......
[Touch CDMA Android Development] loserskater:
damn... another one bites the dust...

On a brighter note. I remember somebody asking about the MLIGN hero so I went ahead and ported it. Nothing really special but I can post it to GC if anybody would like.
[Touch CDMA Android Development] plemen:
Yes please do.
[Touch CDMA Android Development] zenulator:
I just uploaded the supposed magic sense ui. I've read that it's not the actual build. But it's smooth and stable none the less. This will be my last "hero port".
[Touch CDMA Android Development] bug666:
droid wont be out for another 1-2 weeks zen you got some more porting left in you lol
[Touch CDMA Android Development] enatefox:
I've got a blacked out theme for the Magic ROM if anyone wants it. Still working on it but it's got white notification icons, glass dropdown (still wip) and darker black.

And don't worry about Droid... you'll get it.
[Touch CDMA Android Development] zenulator:
Nah....not unless something very major comes along. The only thing I might do is make a flashable android rom for the vogue since i won't have to rely on it anymore.
[Touch CDMA Android Development] jamezelle:
nice man, looks sharp
[Touch CDMA Android Development] enatefox:
Well, I want to finish the phone, change the green to an amber color and add more glass (must have more glass!) but if anyone wants to play with it, this is my version of the Magic ROM. It's almost identical to Zen's but the two apps I made thrown in there. Nano should be working and I did a couple things here and there. You can just grab Rosie.apk and framework-res.apk and drop it onto Zen's or maybe any Hero build and it should be the same
[Touch CDMA Android Development] loserskater:
Looks good! Good work enate
[Touch CDMA Android Development] jamezelle:
so what resolution for the magic sensui rom?
[Touch CDMA Android Development] enatefox:
It's just-another-hero except this thing is quick. Use zen's but if you want the theme, grab Rosie.apk and framework-res.apk from mine or wait till I update. Resolution's the same: 320x480
[Touch CDMA Android Development] jamezelle:
ewww winmobile, wrong forum lol:p:p

nah just messin, the font actually looks cool
[Touch CDMA Android Development] zenulator:
: ) i actually use this. it's not as bad as before. nfsfan does good work. i like your browser icon though. i might have to change that and take out titanium and use the android fonts.
[Touch CDMA Android Development] enatefox:
▲

▲ ▲

aww... it's windows.
[Touch CDMA Android Development] incubus26jc:
woops, wrong place sorry. i dont know how i did that. im using both android and wm. didnt mean to post here
[Touch CDMA Android Development] zenulator:
it's all good. hey at least it's not that cube thing.
[Touch CDMA Android Development] enatefox:
serious. that cube thing was the worst investment of my time ever. it's no compiz