yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Just wanted to confirm that I can connect to WPA2 encrypted networks just fine using the package here and the latest kernel image from the auto build service on my RAPH100.

Keep up the great work people!
[Touch Diamond, MDA Compact IV ROM Development] ND4SPD:
Android 2.1 w/ Sense for the Hero has been leaked. Has anyone tried this to see if scaling works? I can't create the .sqsh file because I'm on windows...

http://alldroid.org/viewtopic.php?f=130&t=539
[Touch Diamond, MDA Compact IV ROM Development] vgkeeper:
It works like a charm for me (french sfr), please add this tip in the wiki :)
[Touch Diamond, MDA Compact IV ROM Development] Erik_PLD:
Someone noticed this: DO NOT USE THIS BUILD! THE CLOCK IS BROKEN! (auto-build page)????

:eek:

And Sense UI now is so far from our diam/raphs. I would be happy to have a full 1.6 OS and it's enough for me...
[Touch Diamond, MDA Compact IV ROM Development] fixxxer2008:
does any of the builds work on a diam500/cdma? i mean damn, the vogue users have a flashable android rom now.
[Touch Diamond, MDA Compact IV ROM Development] vgkeeper:
The progresses are impressive on the last build!!!

maybe the camera and the gps not working but everything else is quite good.

I think it's time to cook a beta rom. maybe it will be a good solution to have more free ram, a better stability and maybe it's a part of the solution of the battery over draining!

unfortunately i'm totaly unable to do it...:(

so... pleeaaaaaassssse :o
[Touch Diamond, MDA Compact IV ROM Development] amaher15:
Thanks

Hey guys.

I hadn't been around for a while and I thought development was dead. Came back to the thread after a few months and damn! So much has been done in November alone!

So this is just a thanks for all the hard work, I really appreciate the fact that there are guys and girls out there working on this. This is the best I can do (I wish I had the money to donate or the knowledge to contribute.)

Thanks again!

Andrew
[Touch Diamond, MDA Compact IV ROM Development] deeproot:
Same here.... I have ATT and text still will not send with this updated info.

I tried to remove the + and use 00plus number and then to just remove the + and 00 and just leave the 1312314**** number. No luck.

Deeproot
[Touch Diamond, MDA Compact IV ROM Development] kailashnj:
Hi Guys,

The android is working like a dream for me. Always connected to internet and to friends on google. Faster email access, but the only problem that I see is the fact about the battery drain which is high and does not allow usage more than 3 hrs to me currenlty

I am waiting for someone to make a Android 2.0 rom at the earliests.
[Touch Diamond, MDA Compact IV ROM Development] simonrobinson:
lcd.density

Running latest build, omitting the lcd.density from the startup.txt gives 640x480, but is dreadfully slow. What's the optimal lcd.density?

EDIT: DIAM100
[Touch Diamond, MDA Compact IV ROM Development] Igoran:
Don't work for me too in MTS RUS. SMS don't sends in Android and WinMO too after removing "+" or/and add "00"... :(
[Touch Diamond, MDA Compact IV ROM Development] rattenfanger:
If you change it back to the plus, can you send sms again in WinMo or does it broke it complete?
[Touch Diamond, MDA Compact IV ROM Development] Igoran:
Of course, then i return +, everythings work ok in WinMo
[Touch Diamond, MDA Compact IV ROM Development] pramod_singh01:
the latest phh is not working for me..

I have copied to internal drive of my diamond

then I start running the haret.exe file.

it started but in the middle of that I gets terminated and

get reboot and start loading windows again.

Somebody help me..I also want to be a part of Android world
[Touch Diamond, MDA Compact IV ROM Development] diegoaugustus:
did you make all the steps? did you replace the file startup.txt?

i think maybe this...
[Touch Diamond, MDA Compact IV ROM Development] stefand:
I'm using lcd.density=240 and I'm really happy with it.
[Touch Diamond, MDA Compact IV ROM Development] simonrobinson:
In the words of Roy Walker, "it's good, but it's not quite right".

Lovely and fast and stable, but only 320x240. Are there any other densities that will allow me to use 320x480 or higher?
[Touch Diamond, MDA Compact IV ROM Development] FeliveNdrell:
I'm maybe terribly wrong but i think lsd.density value specifies amount of screen backlight...
[Touch Diamond, MDA Compact IV ROM Development] stefand:
just try some values like 240, 210, 160, 120 and see what works best for you.

I think your terribly wrong ;)
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
?!?

We do only 640x480, nothing else ! (well 800x480 for blackstone but that's another story), there is no 320x240 things or whatever.

Yep, you're totally wrong. backlight is settable from the android own settings.

Please note that using too high values might prevent the market from downloading most applications. I'm not that sure of that, but last time I tried >240, almost no app were shown.
[Touch Diamond, MDA Compact IV ROM Development] FeliveNdrell:
So it's something like false profile for system? why then not 320? Hero have 320x480 resolution and i'm sure there is plenty of apps for him.
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
Hu ? There is nothing false. It just sets pixel density (see http://en.wikipedia.org/wiki/Dots_per_inch if you don't know what this is), and android interprets it as something like available physical size, this is what android apps use most of the time as positioning unit.
[Touch Diamond, MDA Compact IV ROM Development] NewMan82:
no audio after using voice command

Hi,

I have basic functionnalities with almost no problems.

Except this one:

When I try using voice comand / dial, it does not hear anything... and the worst is that the sound stop working afterward.

Is this a known issue?

If not, could you please tell me about a way to track this down (logs etc...)

or at least, disable the void command completely so that I don't loose my sound?

DIAM100

Android-1.6-22-11-09-CUTB.zip
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
Known problem on my build, don't know about connect-utb. I'll try to take a look at that.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
That is basically your build. (which I also mention on the download page), just with a few added goodies, such as a wide collection of startup.txts, etc..
[Touch Diamond, MDA Compact IV ROM Development] fixxxer2008:
can someone give me a link to any working builds for the diam500/cdma? ive looked and can find none.
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
Hu ? More startup.txt s than what i give are necessary ? Until CDMA is fixed there is no need for that as far as I know.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Well, CDMA (not data) is indeed fixed, at least for the RAPH800. Read up here.
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
Copying old working files, breaking any compatiblity with other boards than CDMA, without data working isn't what i call "fixed".
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
As long as it works, I am sure the RAPH800 users are happy to at least being able to make and receive calls and SMS though..
[Touch Diamond, MDA Compact IV ROM Development] pramod_singh01:
I have successfully rum the haret.exe and it is running also,

but when I am calling some body no voice is coming.

Could some body advice what is the problem
[Touch Diamond, MDA Compact IV ROM Development] stefand:
What type of device you have?

Witch build did you install?

Did you follow http://wiki.xda-developers.com/index.php?pagename=RaphaelDonut ?
[Touch Diamond, MDA Compact IV ROM Development] FeliveNdrell:
More correctly would be use "ppi" ( pixels per inch ) because dpi defines actual size of image, like would picture with res. 300px*300px have 5cm*5cm or 10cm*10cm dimensions if printed.

Now if like you saying we have 240 ppi (or dpi, values in that case the same) you must not only force hardware part of phone to draw alien resolution (something like 320*600) but additionaly port graphics from the android. Now i will explain how i get this numbers.

There are formulas for that kind of things for ex. if you want to know dpi/ppi of your screen you use this:

diagRes / diagSize = ppi

diagRes = sqrt(horizRes^2+vertRes^2)

we have 2.8 inches ( this is our screen diagonal ) and our ppi ( dpi ) 240 from that we have our diagRes = 2.8 * 240 = 672px

and most closest resolution i found for this ppi is 320px * 600px ( ofc with given ratio you always can find another satisfying resolutions ). It looks like lsd.density has nothing to do with dpi or ppi for me. Or maybe it defines screen resolution in some other ways, like width of the screen maybe.

Youself said that this port is using 480*640 resolution, that is why i suggested that this value is false profile for system wich tells android apps that system runs on different resolutions from real (480*640).
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
Wikipedia can't see any difference between ppi and dpi, me neither. The only difference is that dpi is more commonly used from screens and ppi for printers.

Which is totally impossible, our board can do only 480x640 and nothing else.

Android is fine. Apps are not.

It *is* dpi or ppi (hint, wikipedia calls ppi, pixel density.). But yes I missaid a bit, we fake the actual physical of the size.
[Touch Diamond, MDA Compact IV ROM Development] FeliveNdrell:
Thx for answer, glad we understand each other.

About dpi and ppi, i've found one article turn's out dpi not actualy defines size of printed image. Anyway i got your point :)

p.s. did some googling found that article, it says that for now there are only three values 120, 160 and 240. And it is not actualy dpi or ppi, it's more like some variable because android uses complicate system of calculating final resolution (it uses independent pixels and device dependent (absolute) pixels))
[Touch Diamond, MDA Compact IV ROM Development] geh:
Hello,

I confirm that it works for me.

I tried with AT commander : adress_type must be 129, because if I use 145, the system will re-add a '+' at the beginning.

Sample, for SFR, french operator :

AT+CSCA="0033609001390",129

This work both on winmo & android

Thank you :)
[Touch Diamond, MDA Compact IV ROM Development] DonsTechnology:
Except I cant. It hangs up just after Haret finishes its progress bar of booting Linux. And just freezes. (like it still shows file explorer but not functional)Whats up, I followed the instructions to a T.

I really would like to get a working copy of android on my CDMA RAPH800
[Touch Diamond, MDA Compact IV ROM Development] boas:
Battery issues in winmo

Today was a curious day!

8 hours after I pulled the charger from the phone (100% charged) I got a warning from the phone about the batteries energy level! This is a new battery that has worked for over 2 days in Winmo with normal usage. But now it seems to have suffered something extraordinary.

I have yet to confirm that this happens regularly but it looks to be so (will report back about it later on)..

So in worst case there is something in Android that makes the battery wear out, or changes something somewhere. Just want you all to know this experience since it could be important.

Looking forward on the next image, with a working clock!! :p:rolleyes:

EDIT: The battery seems to be as normal now! Don't know what caused this past behaviour, so ignore the post ^^)
[Touch Diamond, MDA Compact IV ROM Development] qumani:
Outgoing SMS for Fuze (Raph110)

So I was wondering if there is anyone that has successfully sent an outgoing SMS from a Raph110 on AT&T in the US.

No matter what WM ROM or Android build/kernel I have, I cant send texts.

In the event that you have would you please share that info.

I have went through all the tuts, and walkthroughs I could find.

Thanks
[Touch Diamond, MDA Compact IV ROM Development] chopped:
i have the same issue but am on USA Tmobile. i checked using ATCommander and it showed my sim card already has the smsc information..
[Touch Diamond, MDA Compact IV ROM Development] qumani:
Same with me. I understand that alot of unintelligent or lazy people come in this forum asking ridiculous questions. However, I am a little tired of people offering up ATcommander as the solution to my problem, after I say that I have tried that and it doesnt work for me.
[Touch Diamond, MDA Compact IV ROM Development] mchh:
Don't only check that the smsc is correct but make sure that this number is in the "00xxxxxxx" format and not "+xxxxxxxx". This is what did the trick for some of us, but there could be other reasons ..
[Touch Diamond, MDA Compact IV ROM Development] aatreya:
On the RAPH800, the "u" key on the keyboard doesn't work. Any idea why this might be?
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
CDMA ?

CDMA users, please try last GlemSom's build (well it hasn't been built right now, but in 20minutes it will be.), with the usual cdma mtype, it is meant to fix it (but I can't say for sure)

Edit: package built at glemsom's.
[Touch Diamond, MDA Compact IV ROM Development] aatreya:
The one with timestamp Date: Sat Dec 05 13:02:23 2009 +0100 ? Or the one reflecting your latest update: http://gitorious.org/linux-on-qualc...mmit/d9b8955e6aab1b4388f21c94078c03809b544774
[Touch Diamond, MDA Compact IV ROM Development] aatreya:
It keeps stopping at boot right after "mmcblk0: p1", and before "blackstone android". Any ideas?
[Touch Diamond, MDA Compact IV ROM Development] babijoee:
How do we enable Get full power collapse working thanks to hero source code and geh?

I'll add this to your wiki and post my results with battery life :)
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
blackstone android ?!? what's the h*** !

Any snapshot maybe ? (there is no such string like "blackstone android" in kernel sources ...)
[Touch Diamond, MDA Compact IV ROM Development] rayman18:
It said that, here is a snapshot :P

http://img690.imageshack.us/img690/7300/dsc02014m.jpg
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
bugtracker !

pjottrr host a bugtracker for us now !

A big thanks to him as I think it should help a lot, here is the url:

http://pjottrr.no-ip.org:81/redmine/projects/show/androidphh

Please don't report single time bugs, only repeatable bugs, or features requests.

Also please post as much debug infos as possible.

There is also a whole forum for us, instead of this giant thread.

And a wiki if anyone cares fulling it.
[Touch Diamond, MDA Compact IV ROM Development] GlemSom:
This is really great! :D

The bugtracker, is that related to the kernel only - or the whole android package?
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
Whole android package
[Touch Diamond, MDA Compact IV ROM Development] FeliveNdrell:
your link directs to empty page with another link Maybe better would be to use last one?
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
Right, done.
[Touch Diamond, MDA Compact IV ROM Development] Nakebod:
phhusson, in yesterdays commit your comment was: Get full power collapse working thanks to hero source code and geh (:confused:)

In short, does that mean that we are now supposed to have a longer battery life?

Sometimes the comments are a little bit vague to me. (I don't have all the in-dept technical knowledge :p)
[Touch Diamond, MDA Compact IV ROM Development] GlemSom:
autobuildsystem updates

I've added a quick&dirty fix to my autobuildsystem to support RSS feeds.

This is currently ONLY for the htc-msm-android builds.

Enjoy: http://feeds.feedburner.com/glemsom
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
It means that whenever the system goes to true sleep (which normally happens a lot unless there are some bugs... :rolleyes:), the application CPU is totally stopped (not just suspended as before), so the CPU takes during this step something like, mm well, <1mA. I believe ARM9 also goes to some sort of economic mode. So yes, if it goes to sleep (idle sleep is fine as well), it should save (a lot of?) battery life. But it seems to me the system doesn't really sleep anymore /o\. That's something really hard to debug.
[Touch Diamond, MDA Compact IV ROM Development] aatreya:
Perhaps it's from the rootfs.img file?
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
There is nothing like that in my rootfs nor in my initramfs ... I really can't see where this strings comes from /o\

Also this whole thing seems really weird to me, can you even do a video of the boot ?
[Touch Diamond, MDA Compact IV ROM Development] rattenfanger:
I'm seeing the same text at startup using the package from connect-utb.
[Touch Diamond, MDA Compact IV ROM Development] chemical1979:
I've the same string in the boot process. I use your package from the http://wiki.xda-developers.com/index.php?pagename=RaphaelDonut Wiki Page.
[Touch Diamond, MDA Compact IV ROM Development] mchh:
Same here with my DIAM100 :p
[Touch Diamond, MDA Compact IV ROM Development] トロワ:
is the touch pro 2 much diffrent then the tp1. can this code be adapted to the rhodium ? just wondering.
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
Main problem is getting panel working. But basically it's the same thing as TP1, just some minor radio changes.
[Touch Diamond, MDA Compact IV ROM Development] MasterMerlin:
Got My RHOD100 on Friday. Now I have the RAPH120 and RHOD100 to Test.

I read in the Rhodium Forums that someone send his RHOD to cr2 to get the Panel working ... if there is anything I could try or test (on either device) to get this working hust let me know ... I will try as soon as I have the time.
[Touch Diamond, MDA Compact IV ROM Development] dcordes:
I think right now there's not much to test but it's always good to see people are willing to help.
[Touch Diamond, MDA Compact IV ROM Development] karlanal:
just a question

are we going to see a fully working rom soon or no chance

just so i know to keep hoping or to let the hope die

and allso i wanted to thank all the great people who are working on this project

tnx guys

greetings
[Touch Diamond, MDA Compact IV ROM Development] MarcLandis:
All I say is -> read: http://wiki.xda-developers.com/index.php?pagename=RaphaelDonut
[Touch Diamond, MDA Compact IV ROM Development] ruskprick:
That didnt answer his question,did it?

No info on that page is related to the possible "soon to be fixed",and i think alot of people is just waiting for a working version of Android.The Htc Diamond is getting pretty long in theyr teeth by now,and many owners are thinking of upgrading in near future if no working version is released soon.This may sound abit harch and ungreatful,and maybe is,but soo many is clingin on to theyr old diamond just becouse of a possible realease of a great "upgrade" from Winmo.

Still i have the greatest respect for the people involved in the work of this projekt!All kudos for them!!:)
[Touch Diamond, MDA Compact IV ROM Development] MarcLandis:
The wiki does answer the question:
[Touch Diamond, MDA Compact IV ROM Development] karlanal:
marc landis, belive me, i have read evereything there was to read about this, and maybe am one of few guys theat read most if not all of the 600 thread sites here, and tried about 20-30 builds

so im not asking before reading like so many people in this thread period

just was curious because there are few android roms for other devices out but sadly not for the diamond

i just love my diamond as a piece of hardware, it just needs a nice OS as the android is

greetings to all here
[Touch Diamond, MDA Compact IV ROM Development] rattenfanger:
I think that we need to do some more status reporting to keep people up to date. Also the wiki is a little bit outdated on some point. The pm.sleep_mode kernel parameter is not needed anymore for example.

Maybe we can make the new project place (http://pjottrr.no-ip.org:81/redmine/projects/show/androidphh, currently down) a better place :) It already includes known defects / issues (bugtracker) and pending feature request :)

René
[Touch Diamond, MDA Compact IV ROM Development] rattenfanger:
Wrong USB Device ID

I'm trying to connect my RAPH100 to my Ubuntu machine but I noticed a complety wrong Vendor and Device ID.

rene@jewel:~$ sudo lsusb

Bus 001 Device 004: ID 049f:505a Compaq Computer Corp. Linux-USB "CDC Subset" Device, or Itsy (experimental)

I also tried in Windows XP but also Vendor ID 049f and Device ID 505a.

When rebooting to Windows Mobile and running lsusb:

Bus 001 Device 005: ID 0bb4:0303 High Tech Computer Corp.

That seems to be correct.

How is is possible that android sends a completly wrong Device ID? Shall I add this as a bug to the bugtracker?

René
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
Not having the same ID in windows mobile and in linux is totally normal, the modem just asks us what to use as vid/did :p

Anyway, faking dev id is needed for adb to work without having to patch it, and it's maybe the same for usbnet.

If you want adb, add board-htcraphael.adb=1 to kernel cmdline.

Else you'll have to setup usb0 network interface and telnetd by hand.
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
Stop saying always the same ****, what are you really lacking, which precise bugs/features ?

Unless you need GPS or > one full day autonomy, android is already usable for daily use. Actually I use it daily, and when using stable versions (i'm a dev, so it happens only one or two times a week, but that's another story), it really is usable as a standard system (who said more usable than windows mobile ? :rolleyes: )
[Touch Diamond, MDA Compact IV ROM Development] karlanal:
it is usable

but as you said, the battery autonomy is terrible

i can use it for 2-2 1/2 hours an that is you must admit really really weak

greetings
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
I never said that, read better.

You're either using an autobuilt, non-tested, known to be buggy,etc, kernel, or you haven't read carefully the wiki page.

With standard raphael battery you should be able to get ~10hours. (I actually can get 12hours while playing with the phone for 2 hours, but I'm not sure of the capacity of my battery)
[Touch Diamond, MDA Compact IV ROM Development] rattenfanger:
I searched everywhere for this explaination ;)

Restarted android with the new kernel parameter. lsusb now gimes me 0bb4:0c02. The vendor ID is valid but the device id isn't. Don't know if its a problem through..

Still not getting it working on Ubuntu 9.10 (Jaunty). I added the udev rule with correct parameters (SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666") but its still now working. Any hints?
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
The vendorid/deviceid is ok for adb. Try running adb as root (but check it has been killed before otherwise it will still run as user !). I don't know about this udev stuff :p
[Touch Diamond, MDA Compact IV ROM Development] rattenfanger:
Still only the emulator when running adb devices. Maybe I will get back to Windows to test it :P Don't use Windows at home for 2 years now ;)
[Touch Diamond, MDA Compact IV ROM Development] makkonen:
New RAPH800 Build

I've posted up a new build for raph800 (CDMA Touch Pro) over at PPCGeeks. The response to the last cdma build here was 'well, if you call that working'... which is about how I feel about this one. CDMA phone and data are working, as is WiFi. (Regardless of anything else, this is amazing and gratifying to me.) But the microphone isn't, so it's useless as a phone, and there are many other strange issues. It's alpha-quality at best. But for those CDMA users who, like me, just want to see some evidence of progress, it's a nice satisfying step.