yashsingh1/xdaforums huggingface dataset:
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] kurt-willems:
You can install custom ROM's over stock ROM 3.14 but you need to use SSPL_Ruu and not HSPL. >>> read more

Android don't have problems with stock ROM 3.14 except NAND, because it need HSPL (the one who isn't compatible with SPL 3.03.0000)

But in this case just install your previous stock ROM 1.66
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] Majidjan:
My previous stock ROM was 1.48. If I install and downgrade to it :

1- No problem would be on HD2 ?

2- Custom ROM or Android would be ok to install ?

Thank you.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] kurt-willems:
1) No, there would be no problems on your HD2

2a) Custom Rom's will work (Don't forget to install HSPL) and Upgrade you're radio; the Radio of stock ROM 1.48 is really old and bad.

2b) Android can only run if you updated your Radio to radio 2.08.50 or newer. (minimum required is Radio 2.08.50. recommended is Radio 2.12.50 ore even Radio 2.15.50)
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] Majidjan:
Hi.

I installed a custom ROM. Everything is ok.

;)

I can't find a good link for Radio 2.12.50 or 2.15.50.

Any Link ?

Thanks.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] kurt-willems:
Here you have the Radio download links sir;

Leo_RADIO_2.15.50.14

Leo_RADIO_2.12.50.02
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] wizroff:
Sir, would be of great help if you can share the link for an official stock rom which I can use to downgrade my phone's spl 3.03. Ive looked eveywhere and cannot locate one. I have an unlocked HTC HD2
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] kurt-willems:
Give me your actual stock Rom version. There are so much stock Rom's. depending of your aria / branded or not / Language.

So with your actual stock Rom, I can know witch one you are looking for.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] wizroff:
Thanks for the reply.

Here are the details:

OS Version: 5.2.21913 (21913.5.0.94)

Manila Version: 2.5.20181527

ROM Version: 3.14.720.3 (04666) WWE

Radio Version: 2.15.50.14

look forward to your reply sir
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] kurt-willems:
Here you have the previous version sir:

RUU_Leo_hTC_Asia_India_1.48.720.2_Radio_15.28.50.07U_2.05.51.05_2_Signed_LEO_Ship.exe
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] wizroff:
Sir, thanks a ton!

I have installed this successfully!

I am now on working on NAND Android installation.

thanks!
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] kurt-willems:
You're welcome.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] kidd78:
Can I ask how you used that information to give him the orignal Rom? I am currently running a Artemis rom and as I remembered I did it using the goldcard method. I just want to remove the SPL install HSPL but it usually reboots. Do you need the serial number part? any help is appreciated

Nevermind found out it was a vodaphone rom needed.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] silverwind:
To know your correct rom, you should go to the HTC website.

Select the country where you bought your Leo.

then go to download section, and put your Serial Number (you can see it if you remove the battery).

If your SN matchs with the Country selected, you can download it.

It means the rom is for you Leo.

Good luck
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] cvpagba:
Sir can i use the the stock rom you suggested on this thread? mine is

OS 5.2.21913 (21913.5.0.94)

Manila Version 2.5.20181527.0

ROM Version 3.14.206.1 (04666) wwe
[Nexus S General] agy1995:
How do i remove clockwork mod recovery?
[Nexus S General] momohammed20:
at the moment the stock recovery images that are floating around wont flash over the clockwork recovery. unfortunately we have to wait a bit until google releases the stock recovery image that is flashable through fastboot
[Nexus S General] rickysquared:
How to remove ClockworkOrange?

I can't seem to install any OTA updates because I can't quite figure out how to remove ClockworkOrange from my Nexus S.

Has anyone been able to go back to the Stock Bootloader?

Thanks,

Ricardo
[Nexus S General] krohnjw:
If you haven't updated via the OTA yet you could flast this: http://xdaforums.com/showthread.php?t=884416

Then flash the OTA via CWM- reboot a few times and let system/etc/install-recovery.sh do it's thing.
[Vibrant Q&A, Help & Troubleshooting] dglowen23:
is this the right camera for the FFC Mod for the Vibrant?

OEM Flex Cable Camera 5.0 MP for Samsung Galaxy S i9000

Picture: http://cgi.ebay.com/ws/eBayISAPI.dll?VISuperSize&item=390271993839

Link: http://cgi.ebay.com/OEM-Flex-Cable-...130006&po=LVI&ps=63&clkid=5834940387970291857
[Vibrant Q&A, Help & Troubleshooting] eweo911:
It appears to be the correct on. Looks like the one I installed.
[Nexus S General] sherifone:
So in my excitement I flubbed and tapped install before capturing the .zip file. Anyone else get the 2.3.1 update yet? It says it just addresses bugs. Yeah don't flame me too bad.

Build number GRH78

Baseband I9020XXJK8

Kernel 2.6.35.7-g7f1638a
[Nexus S General] slowz3r:
Not to be a weeny but take this conversation over to this thread :)

http://xdaforums.com/showthread.php?t=883930
[Touch Pro, Fuze Android Development] arrrghhh:
Awesome... I was hoping this would make its way out into the wild soon!
[Touch Pro, Fuze Android Development] viruscrazy:
Hi,

before release, i wanted to make clocks working without rpc calls, that's why it took longer. Now, the code is "cleaner" and should work for any device (with small adjustments for amss and memories configuration).

Jerome
[Touch Pro, Fuze Android Development] jianC:
Testing on Fuze.

Edit: Does not work, Haret freezes on boot..
[Touch Pro, Fuze Android Development] xUmaRix:
i encounter this when playing around with angry bird.

msm_proc_comm_wince: DEX Code not match! a2m[0x8a], m2a[0x0], a2m_num[0x7b5], m2a_num[0x7b5]
[Touch Pro, Fuze Android Development] vitusdoom:
whooooopieee! trying it out
[Touch Pro, Fuze Android Development] jianC:
Haret does not boot with included kernel... :(
[Touch Pro, Fuze Android Development] vitusdoom:
test diam100:

tried this on a donut version. Camera aint working. hehehe. but it has green crash on it.
[Touch Pro, Fuze Android Development] vitusdoom:
Great one. works great. the bad thing is, hardware buttons wont work after sleep on diam100. I don't know why. can anyone with diam100 comfirm on this?
[Touch Pro, Fuze Android Development] lorikitty:
everything copies successfully except gralloc.msm7k.so. The folder is unwriteable through ssh. Any suggestions for getting it moved?

it says it's a read-only file system. do I need to be in a different mode other than through adb in order to mount the file as rw?
[Touch Pro, Fuze Android Development] tiger2wander:
Great! I hopefully it will work on TP2 also :)
[Touch Pro, Fuze Android Development] pdawg17:
This is GREAT NEWS! Yes I hope once things are ironed out it will be easy to run it on my Rhod400!
[Touch Pro, Fuze Android Development] jianC:
Try sudo command.
[Touch Pro, Fuze Android Development] xUmaRix:
u need to mount -o remount,rw /system to make it writable
[Touch Pro, Fuze Android Development] mister-gwada97one:
Amazing ! ^^ It works fine for me !
[Touch Pro, Fuze Android Development] viruscrazy:
The lib_inst.sh contains a line to enable read/write access to rootfs so that gralloc can be overwritten

Have your tied using this script ?

Package was not designed to run on fuze but should not make your system crash or freeze...

I don't know if it's related to my kernel. Can you send the full dmesg + logcat if you've got the problem again. Also, it might come from the modded libGLES_qcom.so. What device are you using ?

I'm currently modifying blackstone files. I will need someone to test it but he must be patient because it may fail a few times before it runs (memory layout is written in a more "tweakable" way, but it may need some adjustement.

Blackstone sensor is not the mt9t013 as in diamond but mt9p012. Anyway, liboemcamera.so seems to know this sensor and it should work. I'm also looking at the CDMA diamond to make it work with camera (mainly memory configuration to do).

Will try to put a package for theses devices before xmas.
[Touch Pro, Fuze Android Development] xUmaRix:
im on blacstone.maybe i could help.i saw you modified gralloc that have dynamic memory allocation from standard pmem to 3D pmem.im using qcom library for OpenGL ES 1.1-CM GL_RENDERER Q3Dimension MSM7230 01.02.08 0 4.0.0.Im testing 3D library to get better fps
[Touch Pro, Fuze Android Development] viruscrazy:
I've used libGLES_qcom from bzo, just some memory size stuff modded. For camera, right now, I don't care about fps, but I will care when camera will work for almost every devices. Winmo can use more than our 7 & 8 mb of gpu memories, so I think we can make linux to do the same.
[Touch Pro, Fuze Android Development] viruscrazy:
-UPDATE-

Add support for Diamond CDMA, Raphael (all models) and blackstone. Need some (patient) testers.

See first post
[Touch Pro, Fuze Android Development] xUmaRix:
cool upload the library i can help testing for blac100.Normal qcom library use MSM7500 OpenGL ES 1.0-CM same as in winmo.I could play HomeRun battle 3D smoothly using MSM7230 OpenGL ES 1.1-CM.maybe MSM7500 need opengl patch
[Touch Pro, Fuze Android Development] aviatop:
Any chance to start camera on 2.3 gingerbread? Or it's froyo only? Made everything except copying .conf, because it's for froyo, and there is no such file in gingerbread. Thanks.
[Touch Pro, Fuze Android Development] R^7Z:
Keep in mind this is a testing thread and this is the first time that I am aware of that testing the camera for the XDAndroid project has gone public, much less has been even usable... ;)

Gingerbread isn't even fully developed/ported yet for any of our devices. If anything it's still in alpha phases (at least for the neopeek tree/builds). Give the devs and testers a chance to try to get things worked out, it'll be ready when it's ready... ( how soon, who knows? )

Also, be aware at one point, the froyo file you reference, was called eclair and was included in the earlier build packages... :D
[Touch Pro, Fuze Android Development] fshami:
For guys having DIAM100 & having problem running the camera:

Here is my experience:

First i tried copying user.conf from the first post along with the Kernel & Module provided by Virus in a fresh copy on 2.2 FRX03.

It was not giving me point for screen calibration & hence Touch was not working..

Workaround: i used the default conf file + gd9d77f2 module & successfully created the ts-calibration & data image. After that replaced the user.conf / module / zimage with the ones provided by Virus. It works perfect after it.

The issue i am facing is with Zoom, when i try it the camera App closes..
[Touch Pro, Fuze Android Development] Captain_Throwback:
GSM. AT&T is a GSM Carrier is the US.
[Touch Pro, Fuze Android Development] viruscrazy:
Ok, I didn't knew that...because in dmesg logs, I was seeing NON-CDMA in gpio config and I though your were using CDMA phone...

I'm still looking to the problem for rhodium, I may make a new zImage tonight but I must look at the changes I made before, because it may be useless to make a zImage if modifications are not revelant.
[Touch Pro, Fuze Android Development] dare1234:
im kind a newb in thos one pls explain..i have the froyo conf and now that should i do..i use xdandroid 2.2 newest update froyo
[Touch Pro, Fuze Android Development] arrrghhh:
This is just for testing, so if you're not sure how to do it, might be best to just wait until this code is complete & committed so everyone can enjoy camera.

With that said, you just need to place the files (downloaded in the first post) at the root of your SD card.
[Touch Pro, Fuze Android Development] dare1234:
iv wrote u pm check pls
[Touch Pro, Fuze Android Development] arrrghhh:
I've read your PM, assuming you did what I told you it should work. If you can't get it to work, I'd recommend waiting until it's committed. This is for testing, it's not meant to be ready for prime-time yet. Hell, that pretty much describes this project as a whole currently.
[Touch Pro, Fuze Android Development] dare1234:
i copied on my sdcard roof couse i use droid on my roof not on specific folder froyo.user.conf and from lib pack liboemcamera.so is that so?or i must copy somwhere else?
[Touch Pro, Fuze Android Development] arrrghhh:
Honestly, just wait until it's committed. I've explained it already, and there's something being lost in translation.
[Touch Pro, Fuze Android Development] gmp029:
I tried the new files from 1/3, but the screen still goes blank immediatelly during bootup on my sprint raph800.

Once the boot sequence finished, I was able to accept a call even though I had no screen.
[Touch Pro, Fuze Android Development] djdafreund:
same thin,g is happening with 1/3 update on my raph800 also. Still goes blank after like 1/2 second in a fade.
[Touch Pro, Fuze Android Development] Kate6:
RAPH800 Blank screen

Hi - I'm on a Sprint Touch Pro (aka RAPH800) and with both the 12/31 and 1/3 updates, I also have the screen quickly fading to blank. I click on Haret, the progress bar gets to full, the phone vibrates... For less than a second I see some Linux kernel output, then the screen fades to black.

~30 seconds after that I was able to connect with adb, though, so here's a dump of my dmesg attached... In case it might be helpful.
[Touch Pro, Fuze Android Development] djdafreund:
Hey thanks for posting that log file, i'm sure it will be useful. I didn't think android was still actually running so i never though i would be able to still grab the log, so thanks for doing that. It's LOOKING like for some reason it's manually turning the brightness all the way down by the last part of the log, but it wouldn't make sense WHY. Is there a command to run anyone's aware of to manually flip the screen brightness through the link connection, to further test until this bug is squashed?
[Touch Pro, Fuze Android Development] Kate6:
I figured if people are able to accept calls, it stands to reason something was still running. ;)
[Touch Pro, Fuze Android Development] viruscrazy:
That's true...I think it's just a conflict on GPIOS. I'm currently doing a kernel with some changes for raphael to fix this bug. I will post it in a normal post (not on the first thread) as I can't do the modules with it on this computer. If it works, then I will do the zImage + modules at home tonight.

Thanks for the dmesg log, I will have a look at it. I've extracted the camera driver from a sprint rom and I'm working on it.
[Touch Pro, Fuze Android Development] viruscrazy:
Finally, I've updated the first post with a new zImage as It will also be used for rhodium tests...

Thanks for your tests
[Touch Pro, Fuze Android Development] fshami:
Virus: Any changes for DIAM100 in the updated Module / zImage?

If yes then can i use the zImage with ur first Module or i need the 3/1/11 module?
[Touch Pro, Fuze Android Development] viruscrazy:
Only changes for diamond is some gpio configuration (switching from 4mA to 2mA strength), so you don't need to use the last zImage. You can use the last package with zImage + module from 1/3 + libs from the first package (for diamond, you can use all the libs including the libGLES_qcom.so otherwise, the icons will disappear upon screen rotation in camera application).
[Touch Pro, Fuze Android Development] KirisDK:
checkered screen?

I'm using DIAM100...

I followed every instruction on the post but my diam100 keep showing the checkered screen...

I checked the files and tried every zImage on the post, but same result... the checkered screen and square is moving...

I'm using Neopeek's [Barebone] CyanogenMod6.1-Minimum-System 22-11-2010...
[Touch Pro, Fuze Android Development] mymyway:
test rep

touchpro2 rhod210,

tried pack_lib from firstpackage, module from 1/3, and zimage 1/5. got blank screen, then some dialog force close or wait. sorry dunno where is the dmesg log, super nuwbie here. thx
[Touch Pro, Fuze Android Development] viruscrazy:
I will add a line to the first post : the module + zImage are only intended to be used on Xdandroid FRX02 or FRX03 systems. Cyanogen and others systems will need the camera to be activated in the android system. If you've got the checkered screen, it means that the camera is using some hardware stubs, not the real hardware.
[Touch Pro, Fuze Android Development] viruscrazy:
To get the dmesg log, just plug the phone on your computer then type in a shell (cmd.exe for windows, any shell for linux) "adb shell dmesg >dmesg.log". You will need to install android-sdk for that.
[Touch Pro, Fuze Android Development] KirisDK:
oh, I missed the line. thanks!

I'm not good at English... T_T and I missed some lines...

I will try again in another version!
[Touch Pro, Fuze Android Development] pdawg17:
Here is the dmesg for rhod400 (Sprint CDMA)...

I get the same blank screen when starting camera...I don't know much about this stuff but looking in the dmesg log at one point it says:

config_camera_on_gpios NON-CDMA

I have a CDMA phone...not sure if it matters though...

UPDATE: Added logcat for you just in case...
[Touch Pro, Fuze Android Development] Captain_Throwback:
1/5 Kernel Test

Device: RHOD300 (Tilt 2) - GSM

Kernel: zImage-2.6.27.46-01203-g8fc43d4-dirty (1/5)

Modules: modules-2.6.27.46-01202-gb97e666-dirty.tar.gz (from previous test kernel)

System: FRX03

Using a fresh data.img (but after rebooting twice, due to system server issues), after system finished booting, I opened Camera. On first attempt, immediate FC (app wouldn't even open). System remained intact. On second attempt, black screen. Got several FC pop-ups, chose "Wait" to keep system alive. Output logcat & dmesg (attached). Every few seconds I would get the FC pop-up and kept choosing "Wait" until after logs were produced. Then, I chose "Force Close", and after 7 seconds or so, device rebooted into Windows.

Rebooted into Android, and produced last kmsg (attached).
[Touch Pro, Fuze Android Development] Thestealth2:
Hi,

thx for this Work.

I Use the Zimage from 01.03 with modified Froyo.user.conf for swap.

Works till 2 Days very stabil and very very fast only camera the picture does not contain red tones.
[Touch Pro, Fuze Android Development] viruscrazy:
Thanks. I think that I will wait for a rhodium phone to come to make more tests...seems really different on this device...thanks again for your tests.

I was not sure that the CDMA detection was working on the rhodium...I will have to find why it doesn't work as rhodiums are not using the same gpios...

The color problem is probably due to the fact that the sensor is used in "flip" mode (the rhodium might have the same problem). When the sensors will be working, then I will try to find how to make either the driver or the camera application to use the sensors settings depending on the sensor configuration.
[Touch Pro, Fuze Android Development] KirisDK:
I installed the FRX03 XDAndroid, but..

It still shows up the checkered screen...
[Touch Pro, Fuze Android Development] viruscrazy:
Did you start with a fresh data.img ?
[Touch Pro, Fuze Android Development] Kate6:
Testing 1/5 zImage on RAPH800 (Sprint Touch Pro)

Alright, I've tested the new zImage from 1/5 (with the modules from 1/3 and the libs from the first diamond package).

Took me a little while to get it to boot -- the kernel was outputting so many debug and error messages that it was obscuring the little + marks for the screen calibration. Once I figured out that was what was going on and clicked five spots blindly, it booted, though.

Unfortunately the Camera application force closed on me as soon as I tried to launch it.

Attached are:

(1) dmesg.txt, the contents of the dmesg log immediately after the phone has finished booting

and

(2) dmesg2.txt, the contents of the dmesg log immediately after I tried to launch the Camera application and it force closed on me. I thought this might be useful as well.
[Touch Pro, Fuze Android Development] KirisDK:
I erased it and run haret again... but...

oh, I just rebooted my device and camera runs!

Korean community doesn't have the information about these kind of great things,

so I have to search in foreign forums... T_T

And this was the best thing which I found at several foreign forums!

I really appreciate your help, viruscrazy. Thanks a lot!
[Touch Pro, Fuze Android Development] bzo:
I just sent some patches to Jerome that should finally get the rhodium camera up and running. It's been a bit frustrating figuring this out since the rhod camera has been working for a week or two now, but not since attempting to integrate with Jerome's tree and getting the code cleaned up.

Hate to disappoint you diam500/raph800 guys, but it may be a little while before the camera is working for those devices. They are very different from the gsm devices with different gpio configurations and a different QDSP+AMSS. I say this from experience because I started mucking with the camera originally on the diam500.
[Touch Pro, Fuze Android Development] viruscrazy:
Thanks you, it's working on the Rhodium I've received. I will cleanup the code and post a new zImage + module for rhodium users. CDMA users will probably have to modify their startup.txt file to make the cdma detection work. It will be done in a better way soon but for beta testing, you will have to make some mod to the startup.txt

Thanks again to bzo for the work on rhodium.
[Touch Pro, Fuze Android Development] viruscrazy:
Thanks a lot for youusefull dmesg.log...I need to make adjustements to the adsp for your devices. I'm going to look at the Sprint ROM I've doanloaded, but can you please tell me which winmo rom are you using (I will compare to the one I have, so that I'm sure not to spend time on a wrong rom...)

Thanks, Jerome
[Touch Pro, Fuze Android Development] viruscrazy:
First post updated with new zImage for rhodium and raph800 users.

Rhodium camera working for GSM users, need some CDMA testers as well.

Thanks
[Touch Pro, Fuze Android Development] welard:
viruscrazy is there anythink up for us blackstone users thanks
[Touch Pro, Fuze Android Development] arrrghhh:
Sounds great, RHOD400 (Sprint CDMA RHOD) testing now!

EDIT: Hey, forgot to add that line to my startup.txt... Realized as I was booting. Figured I would try it anyways...and it worked! So for whatever reason, I didn't need that additional board command to get the camera to work. Thanks!

I set the phone down, and it seems to be in a SoD state. I might be OCing, so I'll reboot and put that command in the startup.txt. Perhaps not having the command caused it to lockup afterwards, not sure at this point... I just about fell out of my chair when I saw the image on the camera preview tho!

EDIT2: Removed the OC, added that board command to my startup for CDMA. We'll see how it goes...

EDIT3: Works great! Not sure why the phone locked up on the last run, especially after taking a picture. I can still see the pic on my gallery app as well... But I added that line to my startup.txt and took a few more pics. Amazing work guys, can't wait to see it committed!
[Touch Pro, Fuze Android Development] viruscrazy:
I'm working on a new library which does have mt9p012 sensor support but it's not yet working (this library need some deep changes in camera support on Android). I will let you know if I can get it to work with mt9t013 (that's the sensors I have), then you will be able to test with mt9p012..;but I must at first make it work...
[Touch Pro, Fuze Android Development] pdawg17:
Jerome-

Camera now works on rhod400! I used the command in startup, booted into Android and just took my first picture! Great work! I will try without the startup command just to see if it will work without it...

Does it still help to get a dmesg or logcat file to check for smaller errors or not needed?

Thanks again!
[Touch Pro, Fuze Android Development] viruscrazy:
If you could make a small dmesg of the startup, that would be great (without starting camera, way too much output that would overwrite the boot dmesg log)...

..and enjoy the camera !