[ROM][WIP] CM9-marvel-UNOFFICIAL [UPDATE: April 25th]

---

This is a project trying to get CyanogenMod 9 working on the HTC Wildfire S.


If you are a developer and you're working on a device with msm7x27 hardware, contact me, we have a dev only IRC channel to work together.


People who helped during development, with their input, knowledge and patches:

alquez (CM7 port and kernel fixes)
Droste (Input, help and patches)
PabloPL (Thanks for the input)
WinSuk We worked together on fixes for Marvel and Liberty


There will be an official marvel (unofficial CM9) release next week (week 18). I need to prepare for that.


TODO:
* Get camera fully working.



The HTC Aria (Liberty) uses the my kernel tree now. Thanks WinSuk for the trust


NOTE: Don't send me private messages asking for a HOWTO. Everything is documented in the CyanogenMod Wiki. You can't help if you're not able to set it up on your own.

SOURCES: http://git.cryptomilk.org/

ChangeLog


ALHPA0

2012-04-25
* KERNEL:
- Fix ICS/HTC ril problems
* ROM:
- Fix USB Mass Storage
- Fix memory leaks and pmem problems with camera (Thanks Droste)

2012-04-24
* KERNEL:
* ROM:
- Fixed camera preview
- Fixed GPS
- Fixed YouTube
- A lot of cleanups

2012-04-22
* KERNEL:
- Fixed usb_function_switch
- Added more cpufreq governors
- Set interactive governor as default
* ROM:
- Added initial camera support (not fully done)
- Fixed RIL (Radio Interface Layer)

2012-04-20
* KERNEL:
- Added support for liberty
- Added support for marvelc and marvelct

Good work.
Think I cant help much, I can only cook roms using dsixda kitchen.

I will make a MIUI theme for CM9, I like themes.

Originally Posted by modpunk

It boots and I can access logcat. At least this is the first success. However it is waiting for SurfaceFlinger. I think I need to start it. That's the next thing to find out how to do it.

If you want a tester i am there for you 24/7 at your service and if you want you can teach me in this stuff as well... good going though keep up the good work and port cm9 fast on our devices

I'm currently stuck with surfaceflinger, but I think it is a kernel problem. We can't access /dev/kgsl

[pid   220] 13:08:58 open("/dev/kgsl", O_RDWR|O_SYNC|O_LARGEFILE) = 12
[pid   220] 13:08:58 ioctl(12, 0xc00c0902, 0x100ffc6c) = 0
[pid   220] 13:08:58 ioctl(12, 0xc00c0902, 0x100ffc74) = 0
[pid   220] 13:08:58 mmap2(NULL, 4096, PROT_READ, MAP_SHARED, 12, 0x2d822) = -1 ENODEV (No such device)

Originally Posted by modpunk

I'm currently stuck with surfaceflinger, but I think it is a kernel problem. We can't access /dev/kgsl

[pid   220] 13:08:58 open("/dev/kgsl", O_RDWR|O_SYNC|O_LARGEFILE) = 12
[pid   220] 13:08:58 ioctl(12, 0xc00c0902, 0x100ffc6c) = 0
[pid   220] 13:08:58 ioctl(12, 0xc00c0902, 0x100ffc74) = 0
[pid   220] 13:08:58 mmap2(NULL, 4096, PROT_READ, MAP_SHARED, 12, 0x2d822) = -1 ENODEV (No such device)

How can i help??

Originally Posted by modpunk

Hello,

the last days I've chatted with alquez. He told me how to build cm7 and we discussed how to proceed with a kernel for marvel, marvelc and marvelct. We decided to work together on a new kernel. During this week I've started to look how cm9 is built and started to work on it. 10 min ago my first cm9 finally build trough.

I've submitted all my patches upstream or to my git repo. I still wonder how to fix webrtc so that it works for all people out there. It tells you it doesn't support several assembler functions but they are available on arm6. So you need to trick it to think your building for armv7.

I still don't have a kernel for it with atmel fix. That's the next step, then rebuilt it and give it a try. I will let you know as soon as I could boot it.

If you're a developer working on a QCOM device let me know. We need an upstream fix for webrtc and a kernel with patches which are accepted upstream (=cyanogenmod).

I'm tired and have to sleep now...

Awesome

Some posts above I wrote that the problem is SurfaceFlinger not starting. The reason is it can't open KGSL device. The only thing you can do is to tell me what's the problem. I have to dig into the code check check what it doing on the device and then try to figure out what's missing from the kernel side.


If you know don't know how Linux on the system level works, understand C/C++ and know how to debug these things there is nothing you can do.

If you know these things I can send you the rom or the instructions how to build it.


Sorry if I'm rude.

We needed gralloc.msm7x27 and copybit.msm7x27. Now it looks like mass storage support isn't working and kills us.

Originally Posted by modpunk

We needed gralloc.msm7x27 and copybit.msm7x27. Now it looks like mass storage support isn't working and kills us.

So what works and what doesn't any ideas yet?

Sent from my HTC Wildfire using xda premium