69 replies to this topic

[deanesn]

surviven6802, on Mar 22 2010, 23:01, said:

Paul ,I need your help!  Ive tried the alpha 17 no 3g signal i live in the US . I downloaded the alpha 18 still not 3g signal Ive even tried to setting up the APNs still did not work alpha 15 works but i deleted it please help for the people in the US thanks.

"settings > wireless/networks > mobile networks > access point names > Menu key > new apn:

Name: T-Mobile US
apn: epc.tmobile.com

everything else blank." - Quoted from muncheese

and go here http://android.modac...this/page/3380/ between page 160 and 180 you will find what your looking for. And also download a program 'APN backup & restore from the market after you have all your APNs straight and than back them up so next time you flash you can just download the program and restore. That's what I did tonight since i knew I would lose them coming from alpha 16. GL

[Johnston212]

Great work Paul. But how does this affect those of us who might need a clean Desire ROM for when AT&T messes it up?

[falobb]

Thanks a lot to Paul, I just a newbie for nexus as well as for computer knowledge, hope to learning something here, salute to all contributors.
Sorry for my English.

[TecKnight]

commodoor, on Mar 18 2010, 10:49, said:

Support for the pirates lol

I take exception to classifying Paul's work here as piracy in any form.

This is merely an adaptation of the firmware of one HTC device to run on another virtually identical device.

I spoke to several HTC employees at the CTIA convention earlier this week and showed them my HTC rebranded Nexus One.

They were very impressed by the conversion and were actually pleased that I preferred the HTC sense interface to Google's.

Since Google actually allows and has disclaimers when you unlock the Nexus One, installing this on a Nexus One falls under the "I know what I am doing and do so willingly" category.

I, for one, am very appreciative of Paul's work as are a large number of others, based upon the comments here.

[ranblv]

TecKnight, on Mar 28 2010, 15:43, said:

I take exception to classifying Paul's work here as piracy in any form.

This is merely an adaptation of the firmware of one HTC device to run on another virtually identical device.

I spoke to several HTC employees at the CTIA convention earlier this week and showed them my HTC rebranded Nexus One.

They were very impressed by the conversion and were actually pleased that I preferred the HTC sense interface to Google's.

Since Google actually allows and has disclaimers when you unlock the Nexus One, installing this on a Nexus One falls under the "I know what I am doing and do so willingly" category.

I, for one, am very appreciative of Paul's work as are a large number of others, based upon the comments here.

very well said!

[rnmedic1839]

commodoor, on Mar 18 2010, 17:49, said:

Support for the pirates lol

Ran across other issues with the Desire, Sending text pics from the phone will not go thru. T-mobile full android package. The desire is a very nice looking and very funcional ROM on the N1 but like you said there are issues. I would love to have the sense. I will wait happily witn Cyan5.0.5.3 EPE54B STABLE !

Edited by rnmedic1839, 29 March 2010 - 06:37 PM.

[rnmedic1839]

Paul your doing fantastic work. I was having issues with sending and recieving text pics on the Desire ROM. A19 rom.They just would not go thru or recieve. And also sending photo's via texts.The Camera was really nice though.  I also noted that the 3 G bars gone from the phone. I dont know if it was in 3 g or not. I would just love for a stable desire to come out for N1. Great Job Keep it up!.

[jaramillo441]

I got a premium account just to bake a custon desire rom and I have to admit I am very impressed. I had to manually add the apn but was no trouble. I have not ran into the issue of not being apple to send messages or pic messages. However, I cannot seem to send any video messages. On the cyanogen mod my videos were smaller size but when I changed to desire rom all my videos increased in size. I dont know or understand why. Also, I cannot seem to mount my usb card onto pc with this rom. I have to mount through recovery which is fine with me for now. This rom is very nice and I have been using it day to day. Anyway, hope it keeps getting better.

[hk169]

Paul, on Mar 18 2010, 21:39, said:

A status update!

I now have the release candidate of the Desire ROM!

The new ROM, which is MUCH newer than the build I have been using to date is faster and smoother, the Camera app is better synchronised with the flash, the Live Wallpapers selector is in the right place, the base is ERE27 rather than ERD79 and there are numerous little fixes all over the place! Of course, it will take a bit of time for me to do a full quality port over for the next MCR, but i've done a quick hack to flash it on and see what works.

That's the good news - the bad news is BlueTooth, Camera, USB connect popup and FM Radio still don't work correctly out of the box. BUT - I have discovered why.

Basically, it all comes down to the kernel.

I have confirmed that all of the above (i'm not 100% sure on BT, i'm still investigating that one) use specific features in the Desire kernel that aren't available in the generic kernel. HTC enhancements if you will. The Desire ships with a .29 kernel which, based on what i've seen in the apps and the setup of the config file, is pretty heavily customised. Unfortunately the Desire kernel doesn't boot on the Nexus One, so we're in a bit of a sticky situation until the Desire kernel source gets released, and it's unclear when that will be (HTC's track record in that regard isn't fantastic)!

All is not lost however, as I have started looking at a new approach to fixing the problems, as seen in the camera fix for Alpha 16. I'm basically hunting down the kernel specific hooks and - where possible - i'm rerouting those to an alternate location that I can control. Taking the camera app as an example, the libcamera.so file was checking kernel specific points before deciding whether the flash should fire or not. It was doing things like checking for a phone call, checking for a wimax connection (!), and when these checks didn't work properly, it was preventing the flash firing. By editing this library and rerouting those locations, I was able to make the flash fire - much better than just dropping in the 'wrong' library which was the previous solution. Similarly, the camera application itself was dropping back to 3 Megapixels by default because it was looking for a 'sensor resolution' file produced by the kernel, which didn't exist. By determining this as the cause and reverse engineering the Camera application, I was able to make 5 Megapixels the fallback resolution instead. Problem solved.

Hopefully a similar approach can be used for the other problems (FM radio, USB connection and Bluetooth) and we'll get everything 100% - believe me i'm working on it.

If we CAN get this working fully, the work i'm doing here - if I can get it 100% - will also enable Desire users to have newer kernels and custom kernels with all the goodness that brings, without being dependent on a HTC Kernel source release.

There's lots to do - starting with the RC port to use as a base - but it's been a fun ride and it's gonna get funner. Thanks for all your support!

P

waiting for your good news~

[FLT]

Customers in Belgium will receive their Desire tomorrow. A final build coming?

[McBaul]

Android user in China had got the desire already.
Does Paul have any further progress with the desire rom for nexus one?

[inf]

McBaul, on Apr 7 2010, 18:42, said:

Android user in China had got the desire already.
Does Paul have any further progress with the desire rom for nexus one?

Paul is on vacation until the 20th

[attn1]

Anyone have any idea how exactly bluetooth is broken in this ROM?  Is it more or less functional than the stock N1 Bluetooth, which by many accounts, is also broken?

[xTc is loVe]

I will donate Again when my new Desire arrive and the first custom rom is cooked from paul =)

[kbs24]

Paul, on Mar 18 2010, 09:39, said:

A status update!

I now have the release candidate of the Desire ROM!

The new ROM, which is MUCH newer than the build I have been using to date is faster and smoother, the Camera app is better synchronised with the flash, the Live Wallpapers selector is in the right place, the base is ERE27 rather than ERD79 and there are numerous little fixes all over the place! Of course, it will take a bit of time for me to do a full quality port over for the next MCR, but i've done a quick hack to flash it on and see what works.

That's the good news - the bad news is BlueTooth, Camera, USB connect popup and FM Radio still don't work correctly out of the box. BUT - I have discovered why.

Basically, it all comes down to the kernel.

I have confirmed that all of the above (i'm not 100% sure on BT, i'm still investigating that one) use specific features in the Desire kernel that aren't available in the generic kernel. HTC enhancements if you will. The Desire ships with a .29 kernel which, based on what i've seen in the apps and the setup of the config file, is pretty heavily customised. Unfortunately the Desire kernel doesn't boot on the Nexus One, so we're in a bit of a sticky situation until the Desire kernel source gets released, and it's unclear when that will be (HTC's track record in that regard isn't fantastic)!

All is not lost however, as I have started looking at a new approach to fixing the problems, as seen in the camera fix for Alpha 16. I'm basically hunting down the kernel specific hooks and - where possible - i'm rerouting those to an alternate location that I can control. Taking the camera app as an example, the libcamera.so file was checking kernel specific points before deciding whether the flash should fire or not. It was doing things like checking for a phone call, checking for a wimax connection (!), and when these checks didn't work properly, it was preventing the flash firing. By editing this library and rerouting those locations, I was able to make the flash fire - much better than just dropping in the 'wrong' library which was the previous solution. Similarly, the camera application itself was dropping back to 3 Megapixels by default because it was looking for a 'sensor resolution' file produced by the kernel, which didn't exist. By determining this as the cause and reverse engineering the Camera application, I was able to make 5 Megapixels the fallback resolution instead. Problem solved.

Hopefully a similar approach can be used for the other problems (FM radio, USB connection and Bluetooth) and we'll get everything 100% - believe me i'm working on it.

If we CAN get this working fully, the work i'm doing here - if I can get it 100% - will also enable Desire users to have newer kernels and custom kernels with all the goodness that brings, without being dependent on a HTC Kernel source release.

There's lots to do - starting with the RC port to use as a base - but it's been a fun ride and it's gonna get funner. Thanks for all your support!

P

I was wondering if there is a timetable for the fix of the Bluetooth issue on the Desire rom running on Nexus One.  I love everything about it except this bt problem.  Also, please if you have decided not to work up an update please let me know that too since it will affect what rom i eventually stick with.  Thanks very much.

Edited by kbs24, 10 May 2010 - 02:24 AM.

[kbs24]

Paul, on Mar 18 2010, 09:39, said:

A status update!

I now have the release candidate of the Desire ROM!

The new ROM, which is MUCH newer than the build I have been using to date is faster and smoother, the Camera app is better synchronised with the flash, the Live Wallpapers selector is in the right place, the base is ERE27 rather than ERD79 and there are numerous little fixes all over the place! Of course, it will take a bit of time for me to do a full quality port over for the next MCR, but i've done a quick hack to flash it on and see what works.

That's the good news - the bad news is BlueTooth, Camera, USB connect popup and FM Radio still don't work correctly out of the box. BUT - I have discovered why.

Basically, it all comes down to the kernel.

I have confirmed that all of the above (i'm not 100% sure on BT, i'm still investigating that one) use specific features in the Desire kernel that aren't available in the generic kernel. HTC enhancements if you will. The Desire ships with a .29 kernel which, based on what i've seen in the apps and the setup of the config file, is pretty heavily customised. Unfortunately the Desire kernel doesn't boot on the Nexus One, so we're in a bit of a sticky situation until the Desire kernel source gets released, and it's unclear when that will be (HTC's track record in that regard isn't fantastic)!

All is not lost however, as I have started looking at a new approach to fixing the problems, as seen in the camera fix for Alpha 16. I'm basically hunting down the kernel specific hooks and - where possible - i'm rerouting those to an alternate location that I can control. Taking the camera app as an example, the libcamera.so file was checking kernel specific points before deciding whether the flash should fire or not. It was doing things like checking for a phone call, checking for a wimax connection (!), and when these checks didn't work properly, it was preventing the flash firing. By editing this library and rerouting those locations, I was able to make the flash fire - much better than just dropping in the 'wrong' library which was the previous solution. Similarly, the camera application itself was dropping back to 3 Megapixels by default because it was looking for a 'sensor resolution' file produced by the kernel, which didn't exist. By determining this as the cause and reverse engineering the Camera application, I was able to make 5 Megapixels the fallback resolution instead. Problem solved.

Hopefully a similar approach can be used for the other problems (FM radio, USB connection and Bluetooth) and we'll get everything 100% - believe me i'm working on it.

If we CAN get this working fully, the work i'm doing here - if I can get it 100% - will also enable Desire users to have newer kernels and custom kernels with all the goodness that brings, without being dependent on a HTC Kernel source release.

There's lots to do - starting with the RC port to use as a base - but it's been a fun ride and it's gonna get funner. Thanks for all your support!

P

??
If I have already installed one of your Desire roms on my N1, but then I bake another version, do I still have to perform a "wipe" before installing the baked version?

[PaulOBrien]

Generally speaking, try without a wipe and if things break, wipe!

P

[kbs24]

Paul, on May 10 2010, 17:48, said:

Generally speaking, try without a wipe and if things break, wipe!

P

Thanks.   I had to wipe.  Love the r14 rom for Nexus One, still has the Sense Live Wallpaper, and I got my Bluetooth Back.  Now I am working on skinning the Beautiful Widgets Home clock to get it more like the Desire.  But all in all, I like the Nexus One rom better than the Desire.  Really love this stuff, glad I paid my $15.

[sy_enigma]

Paul, on Mar 18 2010, 13:39, said:

A status update!

I now have the release candidate of the Desire ROM!

The new ROM, which is MUCH newer than the build I have been using to date is faster and smoother, the Camera app is better synchronised with the flash, the Live Wallpapers selector is in the right place, the base is ERE27 rather than ERD79 and there are numerous little fixes all over the place! Of course, it will take a bit of time for me to do a full quality port over for the next MCR, but i've done a quick hack to flash it on and see what works.

That's the good news - the bad news is BlueTooth, Camera, USB connect popup and FM Radio still don't work correctly out of the box. BUT - I have discovered why.

Basically, it all comes down to the kernel.

I have confirmed that all of the above (i'm not 100% sure on BT, i'm still investigating that one) use specific features in the Desire kernel that aren't available in the generic kernel. HTC enhancements if you will. The Desire ships with a .29 kernel which, based on what i've seen in the apps and the setup of the config file, is pretty heavily customised. Unfortunately the Desire kernel doesn't boot on the Nexus One, so we're in a bit of a sticky situation until the Desire kernel source gets released, and it's unclear when that will be (HTC's track record in that regard isn't fantastic)!

All is not lost however, as I have started looking at a new approach to fixing the problems, as seen in the camera fix for Alpha 16. I'm basically hunting down the kernel specific hooks and - where possible - i'm rerouting those to an alternate location that I can control. Taking the camera app as an example, the libcamera.so file was checking kernel specific points before deciding whether the flash should fire or not. It was doing things like checking for a phone call, checking for a wimax connection (!), and when these checks didn't work properly, it was preventing the flash firing. By editing this library and rerouting those locations, I was able to make the flash fire - much better than just dropping in the 'wrong' library which was the previous solution. Similarly, the camera application itself was dropping back to 3 Megapixels by default because it was looking for a 'sensor resolution' file produced by the kernel, which didn't exist. By determining this as the cause and reverse engineering the Camera application, I was able to make 5 Megapixels the fallback resolution instead. Problem solved.

Hopefully a similar approach can be used for the other problems (FM radio, USB connection and Bluetooth) and we'll get everything 100% - believe me i'm working on it.

If we CAN get this working fully, the work i'm doing here - if I can get it 100% - will also enable Desire users to have newer kernels and custom kernels with all the goodness that brings, without being dependent on a HTC Kernel source release.

There's lots to do - starting with the RC port to use as a base - but it's been a fun ride and it's gonna get funner. Thanks for all your support!

P

please Paul i can't see the link to the new alpha 22 and can i ask if u can add arabic to the room

[sy_enigma]

Paul, on Mar 18 2010, 13:39, said:

A status update!

I now have the release candidate of the Desire ROM!

The new ROM, which is MUCH newer than the build I have been using to date is faster and smoother, the Camera app is better synchronised with the flash, the Live Wallpapers selector is in the right place, the base is ERE27 rather than ERD79 and there are numerous little fixes all over the place! Of course, it will take a bit of time for me to do a full quality port over for the next MCR, but i've done a quick hack to flash it on and see what works.

That's the good news - the bad news is BlueTooth, Camera, USB connect popup and FM Radio still don't work correctly out of the box. BUT - I have discovered why.

Basically, it all comes down to the kernel.

I have confirmed that all of the above (i'm not 100% sure on BT, i'm still investigating that one) use specific features in the Desire kernel that aren't available in the generic kernel. HTC enhancements if you will. The Desire ships with a .29 kernel which, based on what i've seen in the apps and the setup of the config file, is pretty heavily customised. Unfortunately the Desire kernel doesn't boot on the Nexus One, so we're in a bit of a sticky situation until the Desire kernel source gets released, and it's unclear when that will be (HTC's track record in that regard isn't fantastic)!

All is not lost however, as I have started looking at a new approach to fixing the problems, as seen in the camera fix for Alpha 16. I'm basically hunting down the kernel specific hooks and - where possible - i'm rerouting those to an alternate location that I can control. Taking the camera app as an example, the libcamera.so file was checking kernel specific points before deciding whether the flash should fire or not. It was doing things like checking for a phone call, checking for a wimax connection (!), and when these checks didn't work properly, it was preventing the flash firing. By editing this library and rerouting those locations, I was able to make the flash fire - much better than just dropping in the 'wrong' library which was the previous solution. Similarly, the camera application itself was dropping back to 3 Megapixels by default because it was looking for a 'sensor resolution' file produced by the kernel, which didn't exist. By determining this as the cause and reverse engineering the Camera application, I was able to make 5 Megapixels the fallback resolution instead. Problem solved.

Hopefully a similar approach can be used for the other problems (FM radio, USB connection and Bluetooth) and we'll get everything 100% - believe me i'm working on it.

If we CAN get this working fully, the work i'm doing here - if I can get it 100% - will also enable Desire users to have newer kernels and custom kernels with all the goodness that brings, without being dependent on a HTC Kernel source release.

There's lots to do - starting with the RC port to use as a base - but it's been a fun ride and it's gonna get funner. Thanks for all your support!

P

please Paul i can't see the link to the new alpha 22 and can i ask if u can add arabic to the room