yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] gleng:
still have your now "old" diam500 floating around?? ;)
[Touch Diamond, MDA Compact IV ROM Development] boas:
Data works very well! But despite having the calibration file I'm having difficulties connecting to wlan (worked with previous build).

Very nice release! Dpad did not work on first boot but on second. I have not got the phone to charge once with the w-lan working builds.

And after about 5 min inactivity the phone reboots automatically.

Great job!! You are amazing!
[Touch Diamond, MDA Compact IV ROM Development] beboxed:
[DIAM100]

This build fixes my 3g connection problems! I have removed the ppp.* lines from the startup.txt and could instantly connect on startup, this is briljant!

The only downside is that when 3g is used it draws so much current that the battery monitor bug causes android to complain about low battery.
[Touch Diamond, MDA Compact IV ROM Development] rpgman:
Ok, thanks. The power manager widget stay empty the first time i launch it, i'll have to figure out what does each buttons (the first ones it's ok ^^) i'll search for manual for android phone.

The touch went ok after some time (i can go left and right faster)

For charging battery, i can not tape numbers under terminal, seems that's working before.

A strange thing i never told :p each time i use android my time in winmobile goes one hour back (only once)
[Touch Diamond, MDA Compact IV ROM Development] fcnaben:
just for information, my connection work fine with th new package.

Ty
[Touch Diamond, MDA Compact IV ROM Development] leobaillard:
That's normal, Linux uses a different method for the clock and the timezones may not be the same.
[Touch Diamond, MDA Compact IV ROM Development] beboxed:
[DIAM100]

The image just gave me an issue. When Android just booted into the lock screen (Press the home button to unlock), pressing the home button doesn't work. After a while the screen turns black (not: not off) and can be turned 'on' by pressing the power button however i can't unlock the device.

The home key also doesn't work when i delete the data.img, setup android and lock the device. After that i can't unlock it.
[Touch Diamond, MDA Compact IV ROM Development] demitrixy:
humm it happened with me first time i booted !

on second time it worked. Sometimes its a bit annoying unlock but i think u have to follow the botton the lights and the home

btw anyone can make downloads from market channel ?

im having some trouble.. the application goes to download but stay forever on "Starting download..."

Oh forget it... i discovery that portugal doesn't have access to market channel

hugs
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
Try to reboot, it did the trick for me (download starts automatically at boot). But maybe it's related to your location, don't know.
[Touch Diamond, MDA Compact IV ROM Development] Dunnera:
can comebody help me?

how can i send sms?

what should i do?

thanks
[Touch Diamond, MDA Compact IV ROM Development] demitrixy:
Supposing that u have the last version of everything u should go messaging and send.

but if u have a modern sim card u should take a look HERE
[Touch Diamond, MDA Compact IV ROM Development] chnapsy:
Little report after testing last release on my diam100

Hello,

I tested last release (20091027) on my diamond 100.

It's pretty stable with basics functionnality but I have few very enoying issues:

3G : When I configure a 3g connection and the device tries to connect it result a system freeze and nothing else to do except a soft reset of the device.

SMS: I cannot set the smsc number in the telephone device, after pressing update or refresh, it answers all the time "update failed or refresh failed"

Power management: On my phone, the backlight turns off but the screen is still on, is it "normal" ?

Screen orientation doesnt work : should it work?

For information, for the 3g, I am in France using SFR network with a "illimythic 3g" subscription.

If anyone have some informations related to this issues, thanks for sharing :)

By the way thanks to all the other for their wonderfull job !!! Continue guys !

Chnapsy
[Touch Diamond, MDA Compact IV ROM Development] Dunnera:
does it also work with 20090909 because the ui is nice?!

but thanks for your help
[Touch Diamond, MDA Compact IV ROM Development] H3x:
This is a bug that has been pestering me from early kernel builds. It seems that the DPAD buttons are sometimes not initialized - when this happens, touching/swiping the DPAD does not cause the DPAD to light up and DPAD presses do not register with Linux/Android.

A solution that I found is to MAKE SURE WM initializes the DPAD by USING it (pressing/swiping) before launching Haret.
[Touch Diamond, MDA Compact IV ROM Development] H3x:
BTW, what is the situation with the kernel git? The last commit was more than 2 weeks ago. Is development just slow?
[Touch Diamond, MDA Compact IV ROM Development] c4software:
Git is actually broken.
[Touch Diamond, MDA Compact IV ROM Development] MrVarioII:
Hey Folks,

Well Android booting! So far so good!

Wonder if I could post up for the collective wisdom of the masses....

I'm trying to get the data connection operative. I'm using this build (version 20091027):

http://www.connect-utb.com/index.ph...lder&Itemid=68&id=5:htc-diamond#mce_temp_url#

And as I understand it the settings I need to put into the startup.txt file are these ones:

Orange (UK)

Homepage: http://orange.multimedia/
APN address (Contract): orangewap
APN address (PAYG): paygwap
Gateway (IP) address : 192.168.71.035
Username: Orange
Password: Multimedia
Session type: Continuous / permanent
Authentication: Normal
Port number: 9201

I'm a contract customer.

I was trying to follow these instructions:

http://connect-utb.com/index.php?option=com_content&view=article&id=193

when I tried to boot into android with the data connection functional I hit problems - firstly it booted all the way up but the screen was locked and this time, unlike most, I couldn't unlock it. Used the stylus to reset it.....the next bootup attempt after that (with data enabled) crashed half way through (we got beyond the tux screen and part way throug the loading but it crashed before the android logo screen).

I'm at wits end. I've reverted to the original startup.txt

If someone with the appropriate knowledge could modify the one I've linked here:

http://pastebin.com/f19f3761c

So that I can test one I know has been set up correctly I'd be greatly obliged as I'm still not sure the error isn't incompetance on my part.

Thanks again for your help all and I'll be debugging android and posting back up here as much as I can - it's the most help I can offer as it's about as much as my technological capabilities are up to I'm afraid. :-)

Thanks again all! (btw tested a call when I first booted up - worked like a charm).
[Touch Diamond, MDA Compact IV ROM Development] mchh:
Sorry, I guess I was tired last night :p

I have the DIAM100.

Concerning the GSM and 3G problems, I think that it was network related since I had the same issues in WinMo .. or maybe is it because I turned on and off several times radio signal (in the test menu) and also "played" with the airplane mode to have the 3G connection.

I solved the SMS issues with AT Commander (I set the wrong SMSC, guess I was really tired :p).

I also had many freezes (while connected to 3G) and noticed that the load was heavy (3 to 5), the phone is slower than with the last builds.

I'll give it another try with a fresh install because I've maybe messed up something.
[Touch Diamond, MDA Compact IV ROM Development] H3x:
Hmmm... that can't be good.

Anyway, a few days ago we were making some good progress on maybe getting a Hero/Sense build working on the Diamond.

We ran into a problem regarding the display: Sense builds require a resolution of 320x480 and the current kernel doesn't seem to allow mddi scaling (needed to a scale HVGA to our devices' VGA).

Do any of the people currently working on this project/developers know anything about support for mddi scaling in the current Diam/Raph port? zenulator was of the opinion that the commad line parameters (mddi.*=xxx) were being ignored by the kernel, but that mddi scaling might still be available to the "user space". Is it possible to set mddi scaling anywhere other than as a command-line param? I have adb set up if that might help...
[Touch Diamond, MDA Compact IV ROM Development] Dunnera:
i tried this instruction for sms-fix http://xdaforums.com/showthread.php?t=433433 but it didn´t work... did anybody this work around and does it work?

but maybe i only don´t understand it, is there a better instruction (maybe in german?)?
[Touch Diamond, MDA Compact IV ROM Development] c4software:
Please, why always asking for Sense, it will slow down the device, if one day everythings works with the Classic android, dev will look for adapt kernel/sense on Diamond. I don't think its the acctual priority.
[Touch Diamond, MDA Compact IV ROM Development] H3x:
Well, you have the right to your own opinion, but I do think that quite a few people would like to see Sense on their phones.

There's also no reason why we can't work on things concurrently, not everyone is able/willing to contribute to coding/porting. Some, however would be more than happy to help with getting Sense to work. Like myself. Which is why I'm not simply "asking for" or demanding Sense.

In any case, the issues runs much deeper than Sense. Having an unscalable (mddi) display limited to a VGA resolution does present a problem in terms of application compatibility (and let's face it: apps form a large part of Android's appeal). Sure the Android scene is slowly evolving to support more resolutions, but (to my knowledge) to date there is but a single main stream HVGA Android device - and it's barely been released. Let's face it: for the time being, as well as the foreseeable future, HVGA is the way to go.

Lastly (correct me if I'm wrong), HVGA scaling (whether it's for Sense or not) might actually IMPROVE performance . I know the scaling operation itself requires some resources, but any ape can conjecture that a smaller resolution is less demanding on resources like processing power and less RAM (smaller framebuffer).
[Touch Diamond, MDA Compact IV ROM Development] mchh:
This worked for at least two of us (nobody else reported)

Check you existing SMSC (SMS center) in Settings- Phone - Services -Voice Mail and Text Message.

It should look like +49XXXXXXXXX (49 assuming you're from germany, XXXXXXX is the rest of the SMSC number) (note that number down)

I removed the "+" symbole and replaced it by "00" thanks to AT Commander from that post http://xdaforums.com/showpost.php?p=2002491&postcount=1

In the AT Commander, type :

AT+CSCA="0049XXXXXXXXX" and click on "send".

Soft reset your phone and try it under Android.

Du muss einfach das SMSC Nummer durch AT Commander ändern.

Dein SMSC Nummer sieht so aus : "+49XXXXXXXXXX", du muss das "+" mit "00" auswechseln es soll dann so aussehen: "0049XXXXXXXXX"

In AT Commander, muss du der folgenden Befehl eintippen:

AT+CSCA="0049XXXXXXXXX"

Dann "Send" Einklicken, und dein Gerät neustarten.

Sorry for my german :D
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
But it seems no developer is interested in it. (but zenulator might change this fact)

I'm using daily android donut, without any scaling on my diamond, and no app had any problem with the resolution on my phone. The apps which aren't able to manage VGA as is are "boxed".

Running a text interface as phone would also improve performances.
[Touch Diamond, MDA Compact IV ROM Development] nearlybritish:
Latest Raph110 (Fuze) report

Just a quick update - using the cobaltcode 10-27 build and update, Raph110 now has functional 3g data in 1.6! Marketplace runs like a champ - automatic downloads actually work and no longer hit and miss as it was in 1.5

For those who want to know details - I just used the 10-27 build from the cobaltcode upload site and the 11-02 build update... only change I made was to the density in the startup.txt, but I'm playing with that a bit to get the right fit.

For me, still have problems with SMSC (using AT Commander simply screwed up my existing config in WinMo), the front panel (jittery) and battery consumption... but 1.6 is a lot faster and closer to daily use

Kudos phhusson and leo - not to mention dzo, zen and others for all their hard work!

I'll keep posting my results
[Touch Diamond, MDA Compact IV ROM Development] Dunnera:
thanks for your help

here are exaclty my steps:

AT+CSCA?

+CSCA: "+436640501",145 0

AT+CSCA="00436640501",145

0

after AT+CSCA="00436640501",145 it should be ok and not 0 , isn´t it?

it still doesn´t work!!!

what do i wrong?

(your german isn´t bad as my english ;))
[Touch Diamond, MDA Compact IV ROM Development] mchh:
Actually, you should not type the 145 value (that's why I didnt write it)

If you dont type this value, it will automatically save it as ",129"

I think that AT+CSCA="00436640501", 145 is impossible since the "145" value is for the "+" format

Try just typing AT+CSCA="00436640501"

And 0 is a normal answer (I had the same)
[Touch Diamond, MDA Compact IV ROM Development] rpgman:
I try again today to put the command line "echo 1 > ...." to the file in htc_battery folder but terminal do not want to let me insert numbers.

I try then with android 1.6 sdk, i get in, type the echo command and that doesn't want, i go in first folder then i try to mkdir htc_battery and i see that it's only read-only, like it's mounted in ro mode :p :)

I spent the day with the phone plugged in usb and charging (except going on coffee or to eat ^^), the reactivity seems a lot better than in the beginning (up, down, selecting application were ok but when i wanted to go left and right it was hard, a lots of tries).

For Htc Sense, maybe it could help a lot of us not buying now or soon a new phone or make a little test knowing if we wait for the dragon or taking another phone maker (motorola droid, acer or sony x3/x10/raphael (but not in white :p)). I already hesitate to find a G1 or G2 already used ^^. Or who know jump on htc hd 2 and hopping for so good release of android on it ;)
[Touch Diamond, MDA Compact IV ROM Development] Dunnera:
how can i proof that it is working?
[Touch Diamond, MDA Compact IV ROM Development] mchh:
send yourself a sms or ask someone if he got your sms
[Touch Diamond, MDA Compact IV ROM Development] Dunnera:
yeah i tried it but android says everytimes that it isn´t working :(

any other ideas?
[Touch Diamond, MDA Compact IV ROM Development] jooprzol:
Yup, I have the same results. I've even tried dialing *#*#4636#*#* in android to enter the SMSC info, but every time I pressed the update button, I got an update failed.
[Touch Diamond, MDA Compact IV ROM Development] mchh:
I dont know, try maybe finding an alternative SMSC number on google, or check that it saved the right number with the AT+CSCA? command, you can also check in WM phone's settings.

You could also look in the test menu in android (*#*#4636#*#* on the dial window), it seems to update the SMSC only when I turn off and on the radio signal in the same menu (but I don't really know ..)
[Touch Diamond, MDA Compact IV ROM Development] qumani:
Latest issues...

I obtained all the latest files and ran Android yesterday and lastnight without any issues at all.... 3g, wifi, bt, market... everything worked, and the interface was responsive. I tried to boot it again today and the dpad/ buttons are non responsive. I cleared all files off card and reloaded them fresh and have the same issue. I am not sure what the problem is.

Additionally, I have tried to boot several times (maybe 20) and the problem persists. Is there any known cause for this?
[Touch Diamond, MDA Compact IV ROM Development] H3x:
*sigh* I asked a simple question ("Is mddi scaling possible to set in any manner other than as a kernel parameter?") and the response is a barrage of suggestive, aggressive comments regarding my motivation for asking the question.

Honestly, must every topic in these forums turn into a mindless prattling debate? And, maybe worst of all, is that these "debates" seem to employ virtually no logic - argumentation is based on reductio ad ridiculum and single case-studies are fodder for inference to sweeping statements.
[Touch Diamond, MDA Compact IV ROM Development] H3x:
This was addressed but two pages ago. It may be DPAD drivers which are not initialized in WM.
[Touch Diamond, MDA Compact IV ROM Development] Dunnera:
can you publish screens of atcommand and the test on android?

thank you for your efforts
[Touch Diamond, MDA Compact IV ROM Development] c4software:
Just for information. I have start Anroid this Morning (with lastest phh optimisation) my phone is shutdown right now after works 12hours. I don't have do any 3G connection, no Wifi just two SMS and One Call.
[Touch Diamond, MDA Compact IV ROM Development] qumani:
I realize that, I meant to write if there was a known fix, not just a shot in the dark kinda thing for it. Trust me I have read EVERY post in this thread at least once.... I have been following it for months. I just dont understand why it would initialize just fine the first few times and then all of a sudden crap out on me.

I am flashing my ROM now to exquisite 3.5a (just because there were a few releases since last flash), I am hoping that it will actually eliminate the possibility of there just being instabilities in the WM ROM itself.
[Touch Diamond, MDA Compact IV ROM Development] H3x:
OK, cool. No offence meant. Like I said myself, this bug has been pestering me periodically as well. Particularly with one of earlier builds I had this repeating continously.

I don't seem to have the problem any more. Not sure what I changed, though. It may be the newer kernel image I'm using (zImage pack with addtional drivers from utb-connect). Also I've recently flashed BsB 6.5.1D (base= WM 6.5.1 build 23075).
[Touch Diamond, MDA Compact IV ROM Development] qumani:
No offense taken at all.... I know how it is with the redundant questions of some ppl on here. like....

"android no works, can you fix for me"

Im using the same package that you are, just got done flashing my rom so hopefully that will fix whatever the issue was. My last rom was a little buggy so it might have been the problem. Still cant send SMS no matter what I do though... I have tried all of the different workarounds that I could find and nothing.

It might be an issue with AT&T
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
Use another terminal from the market

You need to mount debugfs in /dbgfs, you can do it by hand, or starting wifi also mount it.

Sorry i haven't seen this question at all.

The problem is not to set it. I can think of 4 different ways with which we can set it, but who cares ?

The problem is to actually get mddi scaling working, and current search i've seen point out that there is no scaling hardware (the mddi client is TC358720XBG, if you see how to get scaling with it, give those informations on #htc-linux @ freenode).
[Touch Diamond, MDA Compact IV ROM Development] H3x:
Ah, thank you so much. I'll scratch around and see what I can find.
[Touch Diamond, MDA Compact IV ROM Development] jaellis:
DIAM400

Did the latest UTB builds take out or change SD card drivers that were there in previous builds? This is the only thing I can think of as to why my DIAM400 doesn't work with latest builds, but I can use everything except replace the new kernel with another one and it works fine.

Anyone else have a DIAM 400?? PM me
[Touch Diamond, MDA Compact IV ROM Development] c4software:
The power management seems working great, when the device enter in sleep mode the dpad is correctly shuting down, Radio awak it (except SMS, but i'm not sure). Its really great but battery drain a little bit fast (my phone stay 12h on android, before stop)
[Touch Diamond, MDA Compact IV ROM Development] nGm@ze:
Hi guys

I recently got the latest Android build running on my RAPH100 for Connect-UTB but i want to try running Sense UI, so i did it and got the file from Vogue-Hero's website and replaced the current system file and try boot with "middi.width=320 middi.height=480 lcd.density=160" (With out the quotes) and it doesn't seem to boot but it loads all the files then i end up on a black screen with a "_" in it. Anyone testing the Zenulator Sense UI build?
[Touch Diamond, MDA Compact IV ROM Development] Roflnova:
May sound a little silly, but are you guys turning this into a ROM when it's done? Would be sweet.
[Touch Diamond, MDA Compact IV ROM Development] ydoucare:
I think that's farrrrr into the future if even possible, because right now we're relying on WinMo to initialize the hardware.
[Touch Diamond, MDA Compact IV ROM Development] Nakebod:
Nice progress lately :)

Currently running the updated Donut build: build-update_donut-1.6_2-11-09.7z on my Diam100, and it is improved a lot :D

The Donut builds itself seems to be a little more buggy, apps "crash" more frequently. (The Force close/Wait dialog pops up.)

- WIFI works perfectly with calibration file. In a very rare occasion WIFI is unable to start, retry and it works.

So far I don't have a very slow responding device like I had with previous WIFI builds.

- 3G/Data is working, and it starts directly :) APN settings are retrieved automatically from my provider, so no manual configuring is needed.

- Bluetooth works, but I'm not using it very often.
[Touch Diamond, MDA Compact IV ROM Development] lucxxx:
Same results for me too. thank you guys for hard work and efforts to port android.
[Touch Diamond, MDA Compact IV ROM Development] kosmodisk:
hi sorry for this question, but how was the problem with disconnecting wifi while obtaining ip adress solved? I still experience this issue..., however i can scan and enter wep key correctly...

thanks
[Touch Diamond, MDA Compact IV ROM Development] roesler90:
I have to say that all works fine, sms work well, wifi is brilliant ;),

but now i have the problem with my winmob apps i installed on the 4gb-memory of the diamond, i am impossible to start them, also the cab. files I stored on it don ' t work

Is there someone who knows this problem and can help??????

(sorry for my english)
[Touch Diamond, MDA Compact IV ROM Development] H3x:
No offence, mate, but read through the last 10 or so pages. We can't keep on repeating the same info ad nauseam.

Basically, the current status is that Hero/Sense builds require the "display adapter" to fit a resolution of 320x480 (HVGA) on to a 480x640 (VGA) (this is done by setting mddi.width=320 and mddi.height=480) as Hero can only run on HVGA, but our devices are VGA. However, our hardware (mddi client/bridge) does not seem to support this feature and and such the mddi.*=* settings are just being ignored and Hero/Sense refuses to display correctly (it IS running, just not displaying).
[Touch Diamond, MDA Compact IV ROM Development] H3x:
Dude, WM applications are (incl. *.cab archives) are compiled specifically for Windows Mobile - they will not run on Android.

Android is based on Linux which relies on different binaries (file types). Also applications are not really commonly installed by downloading installation archives. The preferred system for installing new applications is package repositories - online file stores where all available packages (applications) are stored. This is why Linux is the ideal "market"-based operating system.

Basically, you need to install applications specifically designed for Android (NOT WM!) either via Market (which is single-handedly responsible for Android's appeal) or by manually downloading the packages (*.apk files) and placing them in the Android file system (place under "AndroidApps" in Internal Storage root).
[Touch Diamond, MDA Compact IV ROM Development] roesler90:
of curse not, the wm apps don't run under wm anymore
[Touch Diamond, MDA Compact IV ROM Development] H3x:
Ah, I see what you mean. My apologies. What error is displayed trying to run the apps?