![]() |
Re: big news regarding Fremantle MCE
Here's a few patterns to try (i used charging here as it was easy for me to test.)
Code:
# change between red green and blue quickly |
Re: big news regarding Fremantle MCE
Unfortunatly I do not currently have a N900 development box (my old one was so close to dead it wasn't worth paying the moving guys to move halfway across the country) so I am unable to investigate any MCE bugs at this time.
|
Re: big news regarding Fremantle MCE
Quote:
I have a (Jiffybox) virtual root server with scratchbox installed. Assuming it's multi-user safe I/we/somebody could setup another box so that developers can just ssh there and compile their stuff. |
Re: big news regarding Fremantle MCE
Quote:
|
Re: big news regarding Fremantle MCE
Just out of curiosity, where was the bug that caused the keyboard not to wake up the device?
|
Re: big news regarding Fremantle MCE
Quote:
https://gitorious.org/community-ssu/...57b0afa6bacb81 |
Re: big news regarding Fremantle MCE
Great! Are you (CSSU team) interested in the changes I made to decouple keyboard LEDs from Lysti engines?
PS. There is a lot of code not related to Fremantle/N900 in MCE, I wonder if we stripped that out, or #ifdef it, how much space we would free up? |
Re: big news regarding Fremantle MCE
Quote:
Quote:
|
Re: big news regarding Fremantle MCE
Quote:
But, isn't the whole point to replace closed MCE with RE'ed open clone? /Estel |
Re: big news regarding Fremantle MCE
Quote:
Quote:
|
| All times are GMT. The time now is 08:38. |
vBulletin® Version 3.8.8