yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] heidewitzgar:
tattoo = MSM7225

Hi guys, already asked many times, but noone actually ist able to answer:

The Tattoo ist QVGA and runs on an MSM7225. Both, and many other things are 100% identical to the HTC Touch 3G (aka. Jade).

First question: since it's the same basis, is it possible to flash android fully over WinMo, with the right HSPL? Or would the android flasher not recognise the phone?

Second, since it's the same processor: shouldn't I be able to run HaRet and a ROM from the Tattoo on my Jade? Or is this HaRet's problem, not being able to work with a MSM7225?

The Jade community is not big, I know, but since it's pretty much the same device, AND CHEAPER, it would be interesting being able to use Android on it.. right?

Even a short YES/NO answer would be nice :)

Thanks!
[Touch CDMA Android Development] craig0r:
You only need to post a question once.
[Touch CDMA Android Development] scouzer:
Is it just me or is there no onscreen keyboard in this? I'd install some of the mods like Hero but I have no clue how, lol. But anyway, the old version I could pop up the keyboard with the camera button.. but that doesnt seem to work anymore.
[Touch CDMA Android Development] zenulator:
there is an onscreen keyboard that opens up when you push on an input field.
[Touch CDMA Android Development] scouzer:
nothing happens when i do that
[Touch CDMA Android Development] jamezelle:
hold down on text box and it should come up with select input method and then select touch input or whatever it is called
[Touch CDMA Android Development] scouzer:
I get Select Input Method.. but there's no choices there. It's like I don't have any keyboards installed.

Is there a moron guide to getting a Hero ROM installed on this? All of the guides assume you already know what you're doing... and nothing is drag and drop and go like the base files. I don't want to make my own build, I just want a working system image
[Touch CDMA Android Development] zenulator:
maybe you should ask in the hero threads. i'm sure someone will drop you a link to one of my old builds or try some of the custom builds people are making. and it is drag and drop with the base files after you get a system image and edit your default.txt. plus i think i have a tutorial on the top of my sense ui thread.
[Touch CDMA Android Development] scouzer:
I seem to be with a lot of people here: Sound doesn't work. Calling works fine, but ringtones or music do not. Voice dial/search or Shazam are not working either. When I try to voice search, I get an error that simply says "Audio Problem"

I searched for answers and found people suggesting I hard reset my phone. I did, no go, still no sound. I also ensured my WM was not on mute; It's not, it's on max volume. I still have no sound in Android. It's definitely not due to misplaced sound files, they're in SD/media/audio/ringtones

Any ideas? :( I'm really enjoying Android but no sound is a pretty big deal breaker!
[Touch CDMA Android Development] dzo:
I've made quite a few changes to the kernel recently, mostly they are to enable audio in and the camera on kaiser and polaris. I've also made some changes to power management that should help vogue and the distorted audio should be fixed. The power management changes haven't been tested on vogue but they make a big difference on polaris.

Letest kernel is on the google code site.
[Touch CDMA Android Development] scouzer:
Still no joy on audio on my Vogue
[Touch CDMA Android Development] dzo:
Are you sure you are using a recent radio? That's the only thing I can think of that stops audio working.
[Touch CDMA Android Development] scouzer:
I'm using the latest Bell radio.
[Touch CDMA Android Development] ajclai08:
Kernel Testing..Kaiser Camera

Dzo,

When I Launch the camera for the 1st time after bootup..it seems to distort the blur effect on the backgrounds during notifications for the rest of the time in android. Instead of blurring the background..its multicolored grainy distortion, thought it was my panel type but i guess it isnt..thought it was because i see the same effect once I wake the device using panel type 2. THis happens after you launch the camera..im using a ION build. TY

Edit: Haven't tested your latest Kernel. Got these results with your 1st kernel for 09-10-09
[Touch CDMA Android Development] plemen:
I can't boot my Vogue into Android using the latest zimage - I'm using a cyanogenmod (by Zenulator) system and it was working well - tried the new zimage and it's stuck in HaRET at "Booting Linux"...

Same results with Basefiles-20091009 package at vogue-hero.

Replaced with my original zimage and I'm able to boot fine...
[Touch CDMA Android Development] pmos69:
Didn't test that, sorry.

For now, maybe its best you keep the old zImage also, since the new kernels have a lot of new features...
[Touch CDMA Android Development] jamezelle:
tried the latest kernel(9-10-09-1) with one of my hero builds. and im getting random restarts when i try to wake up the device. im almost positive it is kernel related
[Touch CDMA Android Development] tatnai:
I've had one restart with donut when a incoming call started to ring, didn't know if it was donunt related or zImage related. Using dzo's 10/09 zImage, donut 1.6 official from zen.
[Touch CDMA Android Development] zenulator:
Running the latest kernel with no problems on several builds. Audio is a lot better for vogue.
[Touch CDMA Android Development] dzo:
Just to report that I get great battery life from the latest kernel. I haven't charged my phone for 3 nights now and it's down to 40% with light use (and data always connected but with background data off).
[Touch CDMA Android Development] enatefox:
dzo, thanks for the updates. Camera is working, battery seems pretty good so far. Are autofocus and other features able to be worked on or are these limitations with hardware/Android?
[Touch CDMA Android Development] sshark:
MOre or less same results!
[Touch CDMA Android Development] pmos69:
Yup, basicaly the same type of results for me. fantastic work. thanks.

For people still complaining about battery life, don't forget to set the correct panel.type in default.txt (ie: don't set it to 0)
[Touch CDMA Android Development] TheKartus:
What system image? I have had nowhere near that much luck with battery.
[Touch CDMA Android Development] dzo:
Ion 12-09 but that shouldn't matter. If you only have 1X rather than EVDO reception then that could make a big difference, I always have EVDO.

Other than that, disable sync, background data, gps and turn the backlight down.
[Touch CDMA Android Development] tatnai:
you shouldn't have to set board panel type now that we have auto-detect. haven't had that setting in mine for a while now.

definitely concur I'm getting much better battery life. thank you dzo, and welcome back.
[Touch CDMA Android Development] enatefox:
I'm happy to report that my phone was on with 12% power instead of dropping from 40% to "instantly die mode" like before. Then, I don't have data, only use wifi when needed and charge only when the battery is low. Awesome stuff.
[Touch CDMA Android Development] pmos69:
I think panel auto-detect is only for vogue atm...
[Touch CDMA Android Development] tatnai:
sorry, almost forgot there were other phones in the android porting world :D

Bug: Since the new zImages with better power saving, I've had problems with phone calls and the phone doing funky stuff. difficult to get a logcat. I rarely get phone calls, but in the three days of use, I've had it reboot the phone twice when an incoming phone call awakens the phone. Also once when hanging up a phone call the phone froze to a grey screen and no buttons would change it and had to soft reset. I had used the previous zImages without this problem for >1 week.

Thanks for the hard work dzo, it's always appreciated.
[Touch CDMA Android Development] BJNK:
I have had problems with the phone hanging after receiving or placing a call and I notice it is always when I have "Notifications" (texts, email etc) in the status bar. The phone call completes fine but after the call is finished the hardware buttons do not work. The screen still responds, and then shortly there after it will completely hang and I have to remove the battery to reset it. Have you noticed that your having problems only with notifications or is it always?
[Touch CDMA Android Development] tatnai:
could not say right now. will keep an eye out. did not mention, but this is using latest basefiles, first power saving zImage released a couple of days ago, and xrom 1.5 that I have used for a while without this problem.

new zImage up moments ago, will try. what's new dzo?
[Touch CDMA Android Development] dzo:
I've put a kernel on the google code site that makes a couple of the changes optional and disabled by default. These shouldn't affect power usage much (and probably not at all). Hope it helps.
[Touch CDMA Android Development] tatnai:
when you say optional, are these turned on/off in the default.txt or some other way? what do I need to know to play around with it? TIA
[Touch CDMA Android Development] dzo:
yes, in default.txt put clock_7x00.slow=1 and/or clock_7x00.voltage=1 or you can change them on the fly with:

echo 1 > /sys/module/clock_7x00/parameters/slow

from a shell.
[Touch CDMA Android Development] JeckyllHavok:
Is it vogue only?
[Touch CDMA Android Development] dzo:
No, kaiser and polaris too, but if you aren't having problems there's no points using it.
[Touch CDMA Android Development] JeckyllHavok:
I love to test new things (even with the risk of crashing everything:o).

So, when i use both arguments in my comandline (clock_7x00.slow=1 clock_7x00.voltage) i got a loop after the bootscreen (the animated one). But when i only use clock_7x00.slow=1 everything worls fine. Have to test it viceversa, too.

Nice to see you back on board, your progress with the kaiser camera is fabolous:D
[Touch CDMA Android Development] sshark:
DZO, thanks for new zImage (11/10), what do these command exactly do?
[Touch CDMA Android Development] pmos69:
DZO's commit to the kernel tree says:

Add parameters for allowing cpu clock to be slowed and change voltage

use clock_7x00.slow=1 and clock_7x00.voltage to enable these. off by default.
[Touch CDMA Android Development] sandro27:
??

what files, exactly, do i need in the root of my storage card to run android hero on vogue (sprint)? any help is appreciated thanks.
[Touch CDMA Android Development] jamezelle:
you are gonna have to start usin the search tool! this question has been answered multiple times go to the code.google.com/p/vogue-android page and download the latest basefiles and extract to the root of sd card then dload a default txt then dload your system of choice

i dont mean to be a jerk im just tired of answering the same ? because ppl dont read
[Touch CDMA Android Development] mrkite38:
usbnet

Alright, fellas, I read a while back that usbnet had been removed (in favor of adb, I think?) from the kernel.

I was wondering if that might be reappearing at some point. I'm cheap and don't have a data plan, which limits what I can do with Android. I checked up on the adb ppp command but I don't have a Linux box to run it on. Will usbnet ever make a comeback? I've got a spare Vogue and am happy to test if it would help.
[Touch CDMA Android Development] enatefox:
I didn't know about usbnet. I had tried to find a way to get internet through USB but found nothing. If someone could add it that would be awesome since I'm cheap and don't have a data plan and wifi is spotty
[Touch CDMA Android Development] bandur:
great battery with newer kernels

I just want to report that I get great battery life with the newer kernels on different builds with my normal use (kaiser), at least 30 % better.

Great work!

On the camera side, it works on some builds, but not on other builds ...

Thanks
[Touch CDMA Android Development] xxbabiboi228xx:
Dzo

Dzo Here is the zImage thats making audio work in tattoo builds but still the music player does this weird thing like it will skip to the next track without hitting the next tab.wont play the audio out of it either.Typing sound works on keyboard so does ringtones.
[Touch CDMA Android Development] pmos69:
This is just a dirty hack reverting bluetooth changes done after the first bluetooth commits.

It is basically commit 31e211aeb873bda2e79d3dde6b7e98e08c1508c8 with added squashfs support.
[Touch CDMA Android Development] mrkite38:
dzo, I've been looking through the commits that made adb work and ether not work. If I don't care about adb, is bringing ether back as simple as reversing those changes or will there be some catastrophic result?
[Touch CDMA Android Development] dzo:
Yes, just change common.c to put ether in htc_usb_functions and change the vendor/product ids. Bear in mind that ether won't work with a windows box.
[Touch CDMA Android Development] mrkite38:
Thanks... I'm hoping I may be able to get it working through RNDIS. Not holding my breath, though. If I get it working I'll share, of course. :)
[Touch CDMA Android Development] dzo:
No, that won't work, ether is only cdc-subset. If you can get the gadget driver working then that will give you RNDIS but it involves porting the usb function driver.
[Touch CDMA Android Development] mrkite38:
Ha - good to know. I'll start looking at that after I get my dev laptop loaded.
[Touch CDMA Android Development] xxbabiboi228xx:
DZO New kernel source

Hey DZO they have a new kernel source on developer.htc.com was released today, just thought id share the info just incase you didnt run across it.

http://developer.htc.com/
[Touch CDMA Android Development] jhelder:
Linux boots untill it stops on:

[ 1900476] set gpio 33 wakeup 40000000

what to do???

I have a polaris (first model)

but now i use the sqsh fileand it boots a little more. But stops at: [1.890353]GPIOn Input Driver: Start gpio inputs..(can not read more).

HELP...!!!

ok changed the MTYPE To 1723, it runs, then stops at: /bin/sh: CAN'T ACCESS tty: job control turned off

/ (cube)_

and then nothing
[Touch CDMA Android Development] bandur:
241009 zImage flips screen wrong way

With the latest kernel (24 10 09 zImage) the screen flips the wrong way when pulling out the keyboard on Kaiser. I use the zen latest donut.

I think this is a reappearance of an old problem ...?

(the problem has been mentioned on other treads, but I think it belongs here)

Another problem, that might not be kernel related:

The screen seems to be misaligned with the touchscreen input when the keyboard is out. Ie, when I touch the screen, it register the touch somewhere else on the screen. When the keyboard is not out, it works fine.

Thanks
[Touch CDMA Android Development] Rhys'Droid:
Just wanted to record that I have this same issue.
[Touch CDMA Android Development] plemen:
dzo - I'm working on a themed Donut build and I noticed something odd with the rootfs.img - if I use the rootfs.img from Oct 16 the GPS

will

work and locate me in Google maps; I can use the GPS until I make a call and then it stops working...

If I use the latest rootfs.img I get no GPS action at all... is there some code in the the Oct 16 rootfs.img that we can re-enable to get GPS without losing the camera?

Thanks.
[Touch CDMA Android Development] enatefox:
dzo, I know you're busy and all. Have you started or plan on working on Eclair? I don't know how well Donut libs will work and we've got new ROMs on the horizon. Thanks for your help
[Touch CDMA Android Development] mrkite38:
Finally

got the kernel built from dzo's source using the arm toolchain from android. used:

make defconfig ARCH=arm

make ARCH=arm CROSS_COMPILE=../../mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/bin/arm-eabi-

- I encountered an error on the CODA network filesystem, so I reran config and disabled it

re-ran make, success!

but my zImage is under a meg. Obviously I'm missing something - any hints?

BTW I have oodles of newfound (additional) respect for you, dzo.

and, as a bonus, mine doesn't boot. lol!
[Touch CDMA Android Development] dzo:
Try:

make vogue_defconfig

instead of make defconfig, that should do the job.
[Touch CDMA Android Development] mrkite38:
I don't have a vogue_defconfig file in my arch/arm/configs directory nor do I see one in the git repo? I hope this is no bother, I a total n00b when it comes to building from source.

Edit:

These instructions still valid?

http://www.androidonhtc.com/get_involved

Edit 2: lol, ok, now I'm back to the wiki. Stupid not to have looked there in the first place.
[Touch CDMA Android Development] enatefox:
Can someone point me to the latest config file and possiby a way to import that into menuconfig? There's so many options I'd like to make sure all the work would carry forward with whatever I mess around with. I saw WLAN is unchecked by default for example.
[Touch CDMA Android Development] vilord:
thats what the make vogue_defconfig is for :)
[Touch CDMA Android Development] enatefox:
That makes sense, but there's a lot of stuff that's not selected like WLAN and a few things I don't recall at the moment. I figured some things get edited but aren't saved as the default when I pull from git.
[Touch CDMA Android Development] pmos69:
That's because that stuff in not compiled from those kernel sources.

Compiling with vogue_defconfig will give you a standard kernel, such as the one in the basefiles.

Stuff like audio, camera, and ril libs is compiled against android.
[Touch CDMA Android Development] polyrhythmic:
I am still having this issue with kernels zImage-24-10-09 and newer, I can also confirm that booting with all new files but with kernel zImage-23-10-09 works as expected with the correct orientation.

I'm not familiar with the kernel sources you guys are using or I would try to diff it myself. Can someone please take a look when they have a chance?

Edit: I've been running it for about an hour with my ext2 install and nothing bad has happened... in fact, my Kaiser camera works BETTER with this zImage on Zen's Donut-Ion-Eclair, the native camera app AND ProPaint camera both work, albeit with crunchy audio on the 'snap' sound.
[Touch CDMA Android Development] bpedman:
Using the same build and ext2 partitions with zImage-24-10-09 (and a kaiser) the native camera app works just fine for me anyway, I dont have to use zImage-23-10-09...although I don't hear a sound when I click using the native camera app...but yes, when I have tried on other build I have heard the obnoxious snap sound...i just wish the shopsavvy app would work and scan a barcode...oh well, im happy
[Touch CDMA Android Development] dzo:
The commit on 28/10/09 should have fixed this. I don't have a compiled kernel from this date and my tree has lots of experimental stuff in it at the moment so best compile it yourself. I think the very latest commit (pprr fix) may break kaiser but everything up until then should be ok.
[Touch CDMA Android Development] Neuromancien:
I everybody

( to start, sorry for my bad english, but I'm french,... :rolleyes: )

I try to create a fully working android rom for my nike ( yes I know, here is a Vogue topic... ), but the development on the nike topic was stopped...

So, when I use the vogue kernel on my nike, there is some feature that don't work :

-Sometimes, the calls ingoing go directly to my Answering machine ( I'm not sure of this ****ing google translation :D ), but I found a kernel wich was this problem isn't here...

-The Data ( over HSDPA or EDGE ) dosen't work, I set the corrects APNs ( for DATA and mms ) on default, I started Opera before start Haret, I have modified the apns-conf.xml to add my Orange French conviguration...

I was using the vogue kernel ( and build, rootfs, initrd... ) because the hardware of the nike are close to the hardware of the vogue, but Isn't exactly the same :

On the vogue and the nike, there is a MSM7x00 processor, on the nike is a 7200 and on the vogue a 7500... Addtitionaly, on the nike there is an 274MHz ARM9 coprocessor (it's used by default on vogue kernel for android ? ) and a QDSP5000 DSP, like to the vogue...

So, do you think a recompil of the kernel on the git repository can resolve my problems ? Do you have a solution ?

Additionnaly, I discover 10 minutes ago that I can use a rom radio comming from the Kaiser and working fully on my nike ( RUU Nike Radio 1.71.09.01K ), if I use this on my device, they can work with Kaiser kernel fully ( with dataaaaaaaa !!!! :D:D:D )

Thank to read my ( very ) long post, and, please, if you have any answer, say it to me ;)
[Touch CDMA Android Development] polyrhythmic:
Hmm ok, I'll have to start pulling the sources, haven't compiled for Android yet. Since I'll be compiling, is it possible to change the scroll-wheel-press to 'select' (same as center button of dpad) and also change the side-ok-button to 'back' (same as the front OK button) so that the Android keymap works more like WM?

Is it also possible to map the camera button to the camera app (and also use it to take picture inside the app)?

Last, I still boot with clock.slow and clock.voltage . I swap builds too often to notice any battery difference, but is there a way I can check that those are working from Terminal?

Thanks again for all your hard work!

It sounds like your device is much closer to the Kaiser. I use Radio 1.71 on my Kaiser and Android works beautifully, especially with the latest files. I suggest you flash the 1.71 Kaiser Radio and try the most recent Donut and Ion builds. Hero builds are heavy and take longer to test. Come visit us over in the Kaiser forum, we love Android too :)
[Touch CDMA Android Development] Neuromancien:
Data work on the kaiser ?
[Touch CDMA Android Development] vilord:
i don't think that switching to the kaiser radio is really your fix... there are others out there who are using this on nike and it is working... maybe head over to the polaris forum, as those two devices are *very* similar, and see if one of the folks over there can help?

There is a specific MTYPE that you need to use for nike... but I can't remember what it is. http://xdaforums.com/showthread.php?t=452108&page=293
[Touch CDMA Android Development] deosvx:
Ive had android installed for awhile so its probably an old build. Is there any way to get Android working as actual firmware, taking over WM6.1? If not how can I force my phone to boot into android after WM6 starts up? I really like Android, the big thing holding me back though is the button sizes and placements esp. the dialer. Is there a way to skin or make themes more porportionate to the touch's portrait view or is there a way to force into landscape view like you can on WM6.1? Sorry lotta questions, looked but no solid answers.
[Touch CDMA Android Development] JeckyllHavok:
Use the search button it's a very usefull invention...
[Touch CDMA Android Development] jamezelle:
:eek: ya dont say!!!!!!!!!!!!!!!!!!!!!!!!!:p

here is the answer!
[Touch CDMA Android Development] enatefox:
I realize this is probably preaching to the choir but I just learned the current kernel's .config file can be obtained from /proc/config.gz which helps me a lot. I'm trying to patch the keyboard now so that I can send input through VNC as the default setup rejects remote requests. Not for long..
[Touch CDMA Android Development] pmos69:
current kernel config is vogue_defconfig (/arch/arm/configs)
[Touch CDMA Android Development] chunnell:
Newbie needs some hand holding

Very confused about this. Much of the description of the necessary things to do require an understanding a bit beyond my abilities at the moment. That being said, I have a Verizon VX6900 running NSFAN's 6.5 Windows Mobile ROM with 3.42.50 Radio.

I'll start from scratch here, I've been to your other links and you require something called resources.zip. But nowhere in your links or downloads, have I found any such thing.

Second question, you say to copy everything to the root of your Mini SD card. What exactly is the root? Does that just mean to copy everything to the card but not in a directory? If so, there were files that when extracted are still in directories, such as conf and media. Do I extract the files inside those directories into the the main part of the SD card?