[N910C/H][DEV] AOSP sources

[RaymanFX]

Fixed audio that one was quick.
It still crashes kind of randomly though, which definately needs urgent fixing.
I'll look into it tomorrow, I'm tired of TouchWiz.

 

[Chaffa]

Yes, thank you!

I fixed WiFi on cm11, I want to at least get basic audio playback working before releasing an pre-alpha build in public.
On a positive note, the S-Pen, button lights, notification lights and charging light all work well right now.

So we are so near from our CM ?
Good job man :thumbup:

 

[arbi97]

Fixed audio that one was quick.
It still crashes kind of randomly though, which definately needs urgent fixing.
I'll look into it tomorrow, I'm tired of TouchWiz.

Wait wait wait!!!

 

[gdonanthony]

Fixed audio that one was quick.
It still crashes kind of randomly though, which definately needs urgent fixing.
I'll look into it tomorrow, I'm tired of TouchWiz.

nice.. im so excited about cm for n910c.. i hope it wont be long like 1 or 2 yrs

 

[RaymanFX]

Here's an early pre-pre-pre alpha build for the very brave and impatient (CM11).
https://mega.co.nz/#!bcZFEJ5J!Hv9Gqf6N6GPqhG18H1S2QThV9hi-5MbubQa-VwnOPxY

Please keep in mind it makes no sense sending me logs at this point, I think I'm well aware of every issue present.
What works right now is not much, but here's the list:

• WiFi
• Audio
• Notification lights
• Button lights
• S-Pen (it's usable, no special sammy features though)

What's not working:

• EVERYTHING ELSE (including RIL, sensors, GPS, camera, etc.)

SystemUI also crashes from time to time for me, I definately need to look into that.
The most important part for me is RIL/finally getting the modem to start up next.
I don't know how long this will take, but it sure is a hard task with all these ST-Ericsson blobs and no reference sources/devices.
Anyways, it should only be a matter of time.

A note on the Lollipop kernel sources:
The decon-fb kernel space framebuffer driver got changed around, which makes CM12 builds not even boot to the early animation anymore. I will look into it and see how much changing of our current open source drivers is required to satisfy the kernel needs again, but for now, I'd rather fight the issues on CM11, because any fix I make here probably applies to future CM12 builds as well.

 

[renanterzi]

Good Job man!

 

[jgfernog]

Here's an early pre-pre-pre alpha build for the very brave and impatient (CM11)...,

Working well here, It is very fluir bit the screen answer time is not good. Seems that the screen don't follow tour ginger fastly, smells like a moto G screen.

 

[thiagoribeirorj]

This version is still the CM11. Looking forward to CM12 to volunteer tester.

 

[gekkehenkie11]

@RaymanFX: wonder ful job on booting CM ! I'm interested, what was keeping it from booting ?

Anyway I'm actually facing a similar problem that you are facing now, I want to move our CM12 onto the lollipop blobs but my RIL is dead when I transplant the kernel + blobs, so need to get it going again just like you I just learned something that was VERY helpful, maybe you knew it already but it was new to me. The thing is that most Samsung code has a way to determine the logging level and there are different ways they do that. I was just reverse engineering our lollipop RIL and found out that the way our RIL does it: it reads "ro.debug_level". This can be set to the highest level (4) by adding this to your kernel command line:

androidboot.debug_level=0x4948

and then add to your build prop the setting itself:

ro.debug_level=0x4948

After this it shows me in the radio buffer:

04-07 12:18:38.399 E/RILD ( 332): LoadLogLevel: Log level is 4.

I now have so much more logging output in the radio buffer and it's much easier to see what's actually going on. Anyway very helpful to my own problems and I immediately thought of you, cause I think you're struggling with the same problems (getting RIL up) and I thought this wonderful trick might be of help to you too. But maybe you knew this already Anyway, good luck mate !

*EDIT* BOOM just got my RIL up, with the new logging output it was easy to see where it was going wrong

 

[gdonanthony]

@gekkehenkie11 wow the SD variant is official already.. congratz... i hope u can somehow help @RaymanFX

More power to all note4 devs...

 

[emenny81]

@gekkehenkie11 wow the SD variant is official already.. congratz... i hope u can somehow help @RaymanFX

More power to all note4 devs...

What is SD??

 

[chmuts]

@emenny81 Pretty sure it stands for Snapdragon.

 

[developer_hrishi]

Good luck

 

[RaymanFX]

@RaymanFX: wonder ful job on booting CM ! I'm interested, what was keeping it from booting ?

Anyway I'm actually facing a similar problem that you are facing now, I want to move our CM12 onto the lollipop blobs but my RIL is dead when I transplant the kernel + blobs, so need to get it going again just like you I just learned something that was VERY helpful, maybe you knew it already but it was new to me. The thing is that most Samsung code has a way to determine the logging level and there are different ways they do that. I was just reverse engineering our lollipop RIL and found out that the way our RIL does it: it reads "ro.debug_level". This can be set to the highest level (4) by adding this to your kernel command line:

androidboot.debug_level=0x4948

and then add to your build prop the setting itself:

ro.debug_level=0x4948

After this it shows me in the radio buffer:

04-07 12:18:38.399 E/RILD ( 332): LoadLogLevel: Log level is 4.

I now have so much more logging output in the radio buffer and it's much easier to see what's actually going on. Anyway very helpful to my own problems and I immediately thought of you, cause I think you're struggling with the same problems (getting RIL up) and I thought this wonderful trick might be of help to you too. But maybe you knew this already Anyway, good luck mate !

*EDIT* BOOM just got my RIL up, with the new logging output it was easy to see where it was going wrong

Hey, thanks for the info on RIL debugging
It doesn't help my case unfortunately, as my problem right now is a modem socket not being created (/dev/socket/msockets/AT_*) .. I'm still searching for the blob that creates it, because I cannot track it down and figure out how it needs to be created just by analyzing it.
There was nothing really keeping it from booting, I'm still wondering why CM12 won't boot past the animation actually.
CM11 boots flawlessly though.

 

[miguel-rocha-]

thank you so much, great work I tested your rom cm11 in my note4 n910c and boot without problem I really hope a stable version
again tanks for your work :good:

 

[thiagoribeirorj]

CyanogenMod has released another version of the Note 4. This works in N910C?
http://www.cmxlog.com/12/trltexx/

 

[S.Y.]

CyanogenMod has released another version of the Note 4. This works in N910C?
http://www.cmxlog.com/12/trltexx/

Please do try and learn the model numbers. This one( trltexx) is for the N910F. N910C is trelte.

 

[thiagoribeirorj]

Please do try and learn the model numbers. This one( trltexx) is for the N910F. N910C is trelte.

we are in the same ****.

 

[invisiblesushi]

CyanogenMod has released another version of the Note 4. This works in N910C?
http://www.cmxlog.com/12/trltexx/

please dont SPAM MISLEADING stuff in this thread, this is the secound time, if you really has to post plese posti in Q&A section. And dont be so impatient.
Raymanfx is the ONLY NOTE 4 EXYNOS DEV at the moment.

Here is Q&A section http://forum.xda-developers.com/note-4/help/qa-cyanogenmod-12-sources-t3016341
Please post all your post there! since they are non dev related, and not EXYNOS device related!

we are in the same ****.

It does not matter if the first letters are the same. when the last dont match!

Exyonos is TRELTE
Exynos models: N910C, N910H, N910U

 

[optimuspraim09]

Any idea on when it will be officially released? Thanks