yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Android Development] waterproof125:
so I've tried copying the Mms.apk from the 2.2 /system/app to my computer then into 2.1 but when attempting to copy the file from /sdcard into /system/app it says it cannot copy the file, and the original Mms.apk cannot be deleted. Also when attempting to install from /sdcard it says there is a problem parsing the package. could anyone help me out? would i be able to do this through adb?
[Touch Pro, Fuze Android Development] nickdahat:
The Keyboard that you see may actually be a calendar (Great choice of icons Google *eyeroll*). Pull down the status bar and see what it says as far as reminders or calendar dates. If there's nothing in your calendar, this may be a bug.
[Touch Pro, Fuze Android Development] nickdahat:
The Bluetooth stack in Android isn't the most robust or friendliest stacks around. Google even admits it. They JUST finally opened up the Bluetooth to voice commands in version 2.2. Therefore I can see it being very finicky in a "hacked" environment.

I was trying to program something through the Bluetooth (pandora add on) for quite some time now and its just gotten to be so much of a nightmare I gave up.
[Touch Pro, Fuze Android Development] rkmoray:
Problem was in my startup.txt file. There was an issue with the keybaord line.
[Touch Pro, Fuze Android Development] rkmoray:
screen on

Any way to keep the screen on, when the phone is plugged in?
[Touch Pro, Fuze Android Development] rohith_luffy:
hi ..

i am using xperia x1 (htc kovsky)

where do i download latest version from ?

there is no specific xdandroid section in x1 android dev

thanx :)
[Touch Pro, Fuze Android Development] peterm20:
Settings --> Applications --> Development

check the Stay Awake box, not sure if it works tho
[Touch Pro, Fuze Android Development] arrrghhh:
This thread is NOT for the x1/kovsky. You can try downloading the latest package on the front page, but it may or may not work. Not sure. You may want to post in the correct forum, they would know more about that particular device!
[Touch Pro, Fuze Android Development] ZoneBlaze:
Question...

Does this Android port run on top of Windows Mobile? Like a normal app taking up memory?

Or does it open Android and shut down Windows Mobile?
[Touch Pro, Fuze Android Development] peterm20:
Overwrites winmo in memory and completely takes over memory. To get back to winmo you have to soft reset. And it doesn't touch any of the "Phone" memory
[Touch Pro, Fuze Android Development] drcursor:
Heating

Most of my heating problems (I have a Fuze/Raphael) come from the SD Card. Is there no way to install it to the internal storage, like in the Diamond? Can I just move the files?
[Touch Pro, Fuze Android Development] hamagc:
lol same thing. the internal memory on a diamond is just an sdcard fixed to the board. so in essence you are flashing to the internal memory, we can just remove our internal memory.

as far as nand goes, not at this time.
[Touch Pro, Fuze Android Development] edmarfrazao:
Touch not rum

I instal in HTC Diamont 100

Xand run ok wit button

but touch not run.
[Touch Pro, Fuze Android Development] arrrghhh:
Uh... What? Sober up a little before you post :P
[Touch Pro, Fuze Android Development] adonis89:
Re

I have a htc JADE, can this soft work?
[Touch Pro, Fuze Android Development] TheJokah:
Can't hurt to download and try installing. I would start with 2.1 eclair build and then "upgrade" with newer .ext2 file if it works. ;) Also, you need to now what startup.txt to use. i guess you could try them all :).
[Touch Pro, Fuze Android Development] PicHunter:
Using Diamond100. Works fine! no probs with the touchscreen and so on.

But if i lock the screen (hangup-button) and I want now to unlock the screen (winmo unlock button on the top) the screen is turning on but shown nothing. i have to touch first the screen than it shows the unlock screen.

Okay. I made a soft reset and now in winmo my internal storage is gone!

Well XDAndroid is on my internal storage, I can't start it anymore. But if i connect to my PC (via USB) it is available (only from the PC)

Edit:

omg... situation cleared! another soft-reset fixed it. this 5 minutes (until I had this idea) was an absolutely nightmare xD

Edit 2:

a little slow isn't it? Many, many processes are so slow that the auto-kill window pops up.
[Touch Pro, Fuze Android Development] Kevets:
"Usually" the performance will improve after 5-10 minutes. Not an extreme difference but noticeable.
[Touch Pro, Fuze Android Development] PicHunter:
It seems that every new process need it's time. After few minutes it runs good, but if I start a program, it needs some time again.

Well, I don't know much about android, but it uses a linux kernel inside, right? Is there any swapfile? If not, this could be the problem.
[Touch Pro, Fuze Android Development] deke997:
I have a Sprint Touch Pro (Raph800) and im having some problems. Data doesnt initially work ( i fixed this by adding an apn though). bluetooth headsets will connect but audio is not passed through them. and wifi is "unable to connect". plzz help! ty in advance!

I have updated the zimige, rootfs, and initrd.

my startup.txt is

set ramsize 0x6000000

set ramaddr 0x10000000

set mtype 2039

set KERNEL zImage

set initrd initrd.gz

set cmdline "wifi.mac=00:21:E8:8E:1E:9B lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 acpuclock.oc-freq-khz=600000 force_cdma=1"

boot
[Touch Pro, Fuze Android Development] edefux:
might be true ... i have no heating problems on the diamond ... wifi on win mob gets as warm as on android

to confim everything important runs fine. speed is ok (not overclocked) ,gps, wifi, 3g, market, dialer, sync is good. what really amazed me is that the "touchexperiance" is like on the galaxy ... never thought that would be possible with my phone - THANK YOU

let´s see how long the battery lasts, as written in the first posts you can´t trust the battery indicator. no light sensor (mhh might save some battery in future?), no camera ... no real issues. g-sensor not working completly is a little bit annoying so i switched it off.

i hope xdandroid lasts a day with the regular battery to be the main os for my diamond. since this is my first time with android on winmob i downloaded the .cabed up package ... really user friendly. nice!

one last thing. the hardkeys light up when you touch them (not pressed) - i like that feature ... but i would like to see something when i´m charging the device as well
[Touch Pro, Fuze Android Development] PicHunter:
Huh? Seems there is no Swapfile!

I have now partitioned my internal storage. 3.2GB Fat32 (data) and ~760MB Linux-Swap. Well, I had to hardreset my device, because Winmo had problems to detect the internel storage => Its just windows :D

Now XDAndroid works almost perfect. Need some time anymore, but its very more stable! Only the settings-process freezes sometimes.

Edit: Next problem ^^ my headset does not work. I connected the headset for music, but the music came out of the speakers. Then I pulled out the headset, and it stopped playing. I think the headset were detected, but the sound is not forwarded.
[Touch Pro, Fuze Android Development] arrrghhh:
They don't have this worked out... there are more important things like battery life and perhaps the camera :P
[Touch Pro, Fuze Android Development] PicHunter:
Thats right. It was just a notice for the developers.

Battery life is very more important!
[Touch Pro, Fuze Android Development] politan:
Hello !

Today i install XDANDROID. I have one question. How turn-off flashing "light on the circle" ?

Sorry, for my English.
[Touch Pro, Fuze Android Development] arrrghhh:
I'll cut you some slack since you're from Poland (my mother is 100% ;))

The flashing "light on the circle" as you call it is the "breathe" LED option - basically the same one used in WinMo for when the battery is charging.

Here's how to change/fix it - open up the program LEDEffects. In there, you can set any and all options for this LED indicator. By default, deep sleep is what triggers the breathe LED that you see. This is to let users know that the phone is indeed going into deep sleep properly.
[Touch Pro, Fuze Android Development] SiL3nTKiLL:
hows the battery life on this now compared to the 2.2 version?
[Touch Pro, Fuze Android Development] denis1984:
The device heats up like mad due to wifi running at full power (in comparison with 2.2). And you never know when the device is going to shut down because of the 5% battery readings snafu. But if you don't use wifi and know how to disable 3g occasionally, I guess it's on a par. Kinda. Totally subjective opinion, tho.
[Touch Pro, Fuze Android Development] arrrghhh:
I'd say that my battery life has improved in 2.2. From like 4hrs to 6-8hrs. But that's with what I would call moderate usage.... Heavy usage I get less than 3 hrs from a full charge.

I'm not sure why people ask these subjective questions... if you really want to know, use it yourself friend! Give it a shot! You've got nothing to lose really. I have like 5 different versions of Android on my 8gb SD card.
[Touch Pro, Fuze Android Development] peterm20:
As far as I know the Android OS Doesn't use a swap like linux computers/servers do. At least the android doc (source.android.com) doesn't mention one, and my google android device doesn't have one. I think the Android OS does a better job at actively managing memory and swaps out inactive (sleeping) tasks and saves their status so they can be resumed if need be.
[Touch Pro, Fuze Android Development] NChief:
I tried this on my diamond. I came to the point where I saw a message about that I have no sim card(I dont). Then the screen got black and I was unable to to do anyting.. I have to have a sim card to try this out?
[Touch Pro, Fuze Android Development] AFJAFJ:
installation problem

hello

sry for my bad english but i hope you can understand me :)

i have a installation problem with the actual program 21.6.10

i've got the messages

task rpcrouter: 15 blocked for more then 120 seconds ... and then ...

/proc/sys/kernel/hung_task_timeout_secs disables this message

the installation is in an endless route :confused:

only a softreset can help me

what can i do or why i've got this messages

my hardware -touch diamond p3700 - free ram on storage card 500mb
[Touch Pro, Fuze Android Development] arrrghhh:
Never heard the Diamond called the P3700, but that does look like the same DIAM devices that are supported by this project. Did you copy the startup.txt? If you made it to that point you probably did... Perhaps you copied the wrong one. Under your battery, it should say something like DIAM500 - can you find this? We need to know what device you have.

No, I don't have a SIM and it works just fine. Do you have some PIN authentication turned on in WinMo? I'm not sure what would cause this error message.
[Touch Pro, Fuze Android Development] fogg1:
Where the hell?

Ok so you have told us how to boot android on our phones good, but heres a question. WHERE THE HELL IS THE LINK TO DOWNLOAD ANDROID IN THE FIRST PLACE!!!!!:mad:
[Touch Pro, Fuze Android Development] denis1984:
You want to download it from here [prj][XDANDROID][2.2][AOSP][18.7.10]RC1 RELEASED, and no yellin' please.

Oh, I've forgotten to mention that you're supposed to scroll down to the post #3 on the first page of the thread.

Whew, I've done my part, now it's your turn Anonymous The Lurker.
[Touch Pro, Fuze Android Development] arrrghhh:
Sir, did you READ the first three posts?!? Or did you just skip straight to the end, expecting a download link on every post in the thread... :rolleyes:

Ha, indeed.
[Touch Pro, Fuze Android Development] AFJAFJ:
hello arrrghhh

my phone was a diam200

the startup.txt was from startup config / diamond100

i've found this information on page 828 on this thread

(but it's the release 2.1 => ~13.6.10)

i've tested at once the installation and when i'm looking on my screen

i've found something else

at first - installation runs about 5 minutes then i can read

failed to find system.img on sd card ?

(on my storage card is a system.exe file ? is this the same ?

should i rename it ?)

then there comes the message

task rpcrouter: 15 blocked for more then 120 seconds ... and then ...

/proc/sys/kernel/hung_task_timeout_secs disables this message

and then the endles loop starts task rpc.......
[Touch Pro, Fuze Android Development] arrrghhh:
Hrm... it doesn't say "failed to find rootfs.img"? It actually says "system.img"? Also, you certainly should NOT have a file named system.exe.

Sounds like you should start with a fresh build. Optional, but I would format the SD and start completely fresh. If not, at least download a bundle and start with it. Then you can try updating it. Sounds like you were renaming files that you shouldn't have been renaming ;)

Perhaps good info to know also would be is if you've ever had this working? The startup for the DIAM100 has always worked for you? Honestly if you're getting to the part where txt flies on the screen, the startup.txt is doing its job...
[Touch Pro, Fuze Android Development] AFJAFJ:
Hrm... it doesn't say "failed to find rootfs.img"? It actually says "system.img"?

yes - rootfs.img is on my internal storage =>

sry not storage card = this was my mistake

touch diamond has no sd card -only internal storage

i think - i should test the release dated ~13.6. => see page 828

if it works i will write it here in this thread
[Touch Pro, Fuze Android Development] rkmoray:
Calibrate screen

I need to recalibrate my screen, but I don't see the option anywhere.

Suggestions please?
[Touch Pro, Fuze Android Development] AFJAFJ:
now i've tested the release dated 13.6.

look back at page 828

i don't know why but

yes - it works :D

no problems during installation - very fast

thx for your time "arrrghhh"

i will test it now - great work
[Touch Pro, Fuze Android Development] arrrghhh:
Delete ts-calibration file from where you boot Android from. Boot Android again, it'll take you thru the calibration process on first boot. Be sure to watch the process, if you let it time out you'll end up with a completely uncalibrated system...
[Touch Pro, Fuze Android Development] rkmoray:
Thanks for your help
[Touch Pro, Fuze Android Development] bharris25:
I got that message when I tried to install android without the system.ex2 file. Started over with a complete fresh install and no problems. Android usually doesn't boot up the first time after a fresh install for me but the 2nd or 3rd time good and then I have no more problems with it. I'm just wondering when some video acceleration is going to be happening. You tube doesn't work for me because it flickers but for the most part everything else that's supposed to be working is working. I tried froyo and it worked good but is almost unusable to type with because of the screen double tap and calibration issues.
[Touch Pro, Fuze Android Development] bluezor:
DIAM100

Yeah, I hated the calibration too. Accidently tapped twice on a part and the whole machine was uncalibrated and screwed up and couldn't really be turned off so the battery had to be removed.
[Touch Pro, Fuze Android Development] arrrghhh:
You should've seen the first iteration of the calibration. The text background wasn't wiped originally! :D
[Touch Pro, Fuze Android Development] badboy8813:
does anyone know if infrastructure mode is possible with the wifi tether that currently works???

http://xdaforums.com/showpost.php?p=6780037&postcount=61

i would for my ps3 to be able to connect my TP2
[Touch Pro, Fuze Android Development] florent_lyon:
Hello,

it works great on my Touch HD, thank you for being so active... and so good !

About the last release with 3D drivers: do you have an example of 3D game where it's optimized and works fast now ?
[Touch Pro, Fuze Android Development] tin2001:
I got to trying a build I downloaded a few days ago last night. I'm impressed with the speed... Feels faster than the Windows Mobile ROM I've got on at the moment.

Sadly though, I still get DNS problems (which I think I detailed in the past) on GPRS/HSPA connections. If I run the following, after connecting, it's fine:

setprop net.dns1 <isp dns server 1>
setprop net.dns2 <isp dns server 2>
setprop net.gprs.dns1 <isp dns server 1>
setprop net.gprs.dns2 <isp dns server 2>

I've not tested only doing one pair - I know doing all 4 works. Can anyone (devs or otherwise) tell me how to make this more permanent? I suspect it needs to run after a GPRS connection comes active...
[Touch Pro, Fuze Android Development] Deathcab:
Xdandroid.21.6.10.aosp

I sucessfully installed XDANDROID.21.6.10.AOSP yesterday. I runned it for a while then I turned off my diamond 'cause the battery was empty. This morning, when I turned on my phone, I get into my standard windows mobile ROM instead of xdandroid and I can't get it run as before.

What I should do? Is there any way to have only Xdandroid installed on my HTC Diamond?

Thanks for the help!
[Touch Pro, Fuze Android Development] tin2001:
Check that the "startup.txt" file is still where it's supposed to be, and that it's actually got contents. My phone locked up while starting the first time, and when I tried again, startup.txt was empty - presumably because it never got written to the card.

I don't think there is, though I only pay attention to Touch Pro stuff. Even if there was, I wouldn't do it the way things are at the moment... Hopefully that will change before the clever people working on it get bored and move onto other things :)
[Touch Pro, Fuze Android Development] oliverr871:
Can the capacitive button capability be turned off or something? I absolutely hate its sensitivity and its erratic. Having to keep it clean all the time really reduces its practicality.
[Touch Pro, Fuze Android Development] arrrghhh:
I'd be curious if there is an easy way to disable it... If it could be flipped on/off thru the startup.txt, that would be awesome.
[Touch Pro, Fuze Android Development] denis1984:
I feel you, man. All I can say is that you can re-map the layout of the buttons that you press to something that won't get f*cked up overtime. I mean, for a time being; until after the issue has been resolved.

For example, consider this layout with double-redundancy of 'call' and 'end call' functionality:

# HTC Touch Diamond [DIAM100] by Denis Valeev [denis.valeev@gmail.com]

#WAKE_DROPPED - just wake up if the device is shut down
#WAKE - wake up and perform assigned operation

# code function pre-function # description
###################
key 139 HOME	# home icon

key 102 NOTIFICATION WAKE_DROPPED	# power icon
key 158 BACK	# back icon
key 107 ENDCALL	# end call icon
key 231 CALL	# call icon

key 232 MENU WAKE_DROPPED	# central navigation button

key 108 DPAD_DOWN	# bottom navigation button
key 103 DPAD_UP	# top navigation button
key 105 DPAD_LEFT	# left navigation button
key 106 DPAD_RIGHT	# right navigation button

#key 115 VOLUME_UP	# volume up button
#key 114 VOLUME_DOWN	# volume down button
key 115 CALL	# volume up button
key 114 ENDCALL	# volume down button

As you can see from the provided key map, pressing the volume up key would fire up a dialer and pressing the volume down key would end a call or turn off your phone. Pretty neat, eh? :D

Besides, you can map something on those up and down keys on the navigation pad, as they certainly have separate physical buttons and don't go crazy because of this capacitive malfunction.
[Touch Pro, Fuze Android Development] nkrick:
I don't know for sure about the directional buttons, but a lot of user experience and reports seem to indicate that there are not actually different hardware buttons under the capacitive pad, but only a couple of buttons (1 for the right, 1 for the left, and I am not sure about the center area) and the "virtual button" that is "pressed" is determined by where the capacitive touch panel detects your finger when the button is pressed. I guess it is easy to perform some testing by using the stylus to press the buttons in the capacitive panel and see what happens...

*****************************************

edit - I just performed that test and in WM, all the buttons work when being depressed by the stylus (back goes back, off hook opened the dialer, the directional arrows moved the selected item, etc). In Android it worked the same way. So perhaps all we need to do is completely disable the capacitive panel and we would be good...
[Touch Pro, Fuze Android Development] arrrghhh:
I'd rather leave the hard keys alone and just disable the capacitive features of the buttons, if that's possible.
[Touch Pro, Fuze Android Development] denis1984:
Try to depress the lower-left corner and while keeping it depressed, try to depress the adjacent corner... that's right, when you depress it it won't produce a click. What would be the logical conclusion of this simple test is left for the reader as an exercise. :D Nah, I'm kidding. I think that there's only one physical button under both the 'call' icon and the home icon.

Update: Here is the HTC Touch Diamond disassembly. Scroll down to the last image to see that there's only 4 (four) hardware buttons underneath this capacitive panel. Well, there's clearly 5 physical buttons, one is for the center button on the navipad. :D
[Touch Pro, Fuze Android Development] nkrick:
Very interesting... With only 1 button on each side, there is no way to know what is being depressed by the stylus if it is truly a capacitive touch panel... I can't figure out how my test worked...
[Touch Pro, Fuze Android Development] oliverr871:
Yea, the capacitive capability needs to go, but leave the hard-buttons functional.
[Touch Pro, Fuze Android Development] denis1984:
I couldn't disagree more. :D Everything should work and work properly. We don't need less features, we need more. :cool:
[Touch Pro, Fuze Android Development] sunyushi:
Have you stopped refreshing now?

I really like the great work you've done.Hope you can get it more perfect
[Touch Pro, Fuze Android Development] denis1984:
No, the project is very much in the works, just in another thread.
[Touch Pro, Fuze Android Development] nkrick:
I agree that everything should work, and in general the capacitive panel does what it is "supposed" to do. Based upon testing in WM, I think the root cause is a hardware problem since using the HTC NavDbgTool.exe I can reproduce the same problems with the capacitive panel as I see in xdandroid. Also, not everyone is seeing these problems. If it was a problem with xdandroid, everyone would see the same problems, but instead, only a few people have reported this issue. For those of us who have the problem, just having the ability to disable the scroll wheel would help tremendously in reducing the affects of the problem. The ability to choose to disable the scroll wheel is what has been requested, though I don't know that any developer who has the ability to do this has seen the request.

The thing that annoys me about the situation is that not one person who has been complaining about the capacitive touch panel not working is willing to download the HTC NavDbgTool.exe to test to see if the problems occur in WM (or if someone has tested, they have not posted their results). Instead they b*tch and moan about some problem in xdandroid that makes their buttons "go crazy." Several people have outright denied that it could be a WM problem (since they don't see the problem in WM) without doing any testing with the HTC NavDbgTool.exe first. The effects of the problem are not nearly as noticeable in WM, but anytime I fire up the NavDbgTool.exe, I can easily reproduce the problem and see "phantom touches" occurring on my capacitive panel.