(Please feel free to correct me if I am wrong, I am NOT an expert.)

My understanding is that the reason these hurdles are not being dealt with is that we have gone just about as far as developers can go. These problems more or less exist across all Motorola phones running ICS.

There is a light at the end of the tunnel, if Motorola unlocks the bootloader (I wont really pretend to know what that means, just know its the problem) OR if Motorola releases a stock ICS phone, then we may see significant gains. For now, I dont think there is much hope at all.

That said, Hashcode has done a huge amount! Was not that long ago BT and camera didnt work at all, now we just have BT unreliability, and no camcorder. That is impressive progress when you consider he has a JOB and a FAMILY.

There is also the possibility to use kexec to run a 3.+ kernel for a less limited ics build. I do totally agree, amazing what's been done so far in terms of backporting the OS to run on our kernel/phone.

I just want to clarify my last post, I was in no way criticizing Hashcode, or any other developer. I think they have done amazing work and I am hugely appreciative of all their efforts. I was simply trying to get a better idea on where things stand, and what we should expect going forward.
Once again, I would like to extend a big thank you to Hashcode and everyone else who have helped get this to where we are today, and Iook forward to seeing where things go from here.

Originally Posted by The_Joe

(Please feel free to correct me if I am wrong, I am NOT an expert.)

My understanding is that the reason these hurdles are not being dealt with is that we have gone just about as far as developers can go. These problems more or less exist across all Motorola phones running ICS.

There is a light at the end of the tunnel, if Motorola unlocks the bootloader (I wont really pretend to know what that means, just know its the problem) OR if Motorola releases a stock ICS phone, then we may see significant gains. For now, I dont think there is much hope at all.

That said, Hashcode has done a huge amount! Was not that long ago BT and camera didnt work at all, now we just have BT unreliability, and no camcorder. That is impressive progress when you consider he has a JOB and a FAMILY.

There are a couple locked moto phones that have advances. Like the kexec ones and i think its the Droid X or something that is locked and has the video camera working now. 720p recording i believe but dont quote that. I am completely grateful to the developers in all their work. I hope it doesnt seem that im not, i just gave my praise already lol. Not going to in every single post with a question

If it's actually 720, I'd be so happy. The DX/2 only shoots 720, so being able to capture HD at max resolution would be great.

I have some problems with the bilho
for many veses it back to 100% and battery life is gone

I have noticed an old bug reappeared now when I'm running CM9. Once phone have been used in a car dock, it can no longer go into deep sleep. Restart fixes the problem. The bug existed on XT860 as well as XT862 in the initial firmware. It was fixed in the first wave of firmware updates (the only wave for Bell XT860)


Sent from my XT860 using Tapatalk 2

Since now Droid 4 stock ICS has leaked - is there any chance that can be used to improve D3 CM9?

Originally Posted by leobg

Since now Droid 4 stock ICS has leaked - is there any chance that can be used to improve D3 CM9?

Maybe, but most likely not. Remember that the Droid 4 leak includes a new kernel as well which does nothing for the Droid 3.

Sent from my Xoom using Tapatalk 2

FC in Browser

---

in the nighties of May if you open browser and then goes to menu, receive a FC. I test with April 28 and this do not occur.

Also, whenever WiFi automatically switch off to preserver energy, do not come back until manually disable/enable.

very good job in CM9!