[N910C/H][DEV] AOSP sources

[RaymanFX]

We're pretty damn close to getting a full boot, I added a bunch missing radio/modem bringup blobs for the ST-Ericsson modem of the N910C (other variants with Intel modems will be supported later).
It looks like the modem fails to startup because of missing sockets though, here's an excerpt of the log:

I/MMD     ( 2826): [main, 1032] Modem Status is 3
D/DIP     ( 2828): AT socket not available. Retrying (try: 2)

(MMD is the modem daemon (started by cbd) and DIP is STE's debug binary)

I'd appreciate it if another developer (I know some of you are lurking in here ;p) could take a look at a full log.
Maybe I'm missing out on something obvious.
I'll continue to analyse these and try to figure out what kills our modem socket.

 

[invisiblesushi]

We're pretty damn close to getting a full boot, I added a bunch missing radio/modem bringup blobs for the ST-Ericsson modem of the N910C (other variants with Intel modems will be supported later).
It looks like the modem fails to startup because of missing sockets though, here's an excerpt of the log:

I/MMD     ( 2826): [main, 1032] Modem Status is 3
D/DIP     ( 2828): AT socket not available. Retrying (try: 2)

(MMD is the modem daemon (started by cbd) and DIP is STE's debug binary)

I'd appreciate it if another developer (I know some of you are lurking in here ;p) could take a look at a full log.
Maybe I'm missing out on something obvious.
I'll continue to analyse these and try to figure out what kills our modem socket.

You can try to ask someone in this thread: http://forum.xda-developers.com/note-4/development/exynos-543x-android-development-t2949478

 

[gekkehenkie11]

We're pretty damn close to getting a full boot, I added a bunch missing radio/modem bringup blobs for the ST-Ericsson modem of the N910C (other variants with Intel modems will be supported later).
It looks like the modem fails to startup because of missing sockets though, here's an excerpt of the log:

I/MMD     ( 2826): [main, 1032] Modem Status is 3
D/DIP     ( 2828): AT socket not available. Retrying (try: 2)

(MMD is the modem daemon (started by cbd) and DIP is STE's debug binary)

I'd appreciate it if another developer (I know some of you are lurking in here ;p) could take a look at a full log.
Maybe I'm missing out on something obvious.
I'll continue to analyse these and try to figure out what kills our modem socket.

Unfortunately we (snapdragon) have different modems than you guys so can't help you out here. But I had my own problems of getting the modem up. Just keep comparing a log where it boots (TW) to your current log and you will find it. But I'm sure that's exactly what you're doing I'm quite busy myself and also not sure if I could even help you out but if you're still wrestling with this next week, I'll take a look at your logs if you want. Good luck mate !

 

[RaymanFX]

You can try to ask someone in this thread: http://forum.xda-developers.com/note-4/development/exynos-543x-android-development-t2949478

We're lone wolves here, the modem implementation for Exynos models (at least those with the ST-Ericsson modem) are vastly different from anything else (the Galaxy Alpha developer modpunk, who created the thread you linked, also works on Intel modems since the Alpha has one).

Unfortunately we (snapdragon) have different modems than you guys so can't help you out here. But I had my own problems of getting the modem up. Just keep comparing a log where it boots (TW) to your current log and you will find it. But I'm sure that's exactly what you're doing I'm quite busy myself and also not sure if I could even help you out but if you're still wrestling with this next week, I'll take a look at your logs if you want. Good luck mate !

Thanks for the offer, but I'm afraid the modem here is just too special.
I'll let you know if I'm completely out of ideas some day (but it is not today, lol).

On a brighter (well, not really that bright) note, I think I know what might be going on.
My kernel messages indicate that SSP (sensor protocol started by sensor hub) is claiming a certain kernel node (a certain pin ctrl instance to be specific) but does not release it for some reason. The modem then tries to setup its socket and establish a connection to the radio on the same pinctrl node for some reason (Samsung, y u do dis), so early RIL bridges fail to be setup.

Another thing I noticed is that instead of being a good guy OEM and keeping their init scripts tidy, Samsung moved ST-Ericsson specific RIL arguments/restart command sequences to the main android init.rc script, so I might need to import the generic CM 12 init script and slap Samsung's changes on top of it to make the modem fire up properly. This causes all kinds of troubles since init.rc should really be provided by the platform and differs from ROM to ROM. It also makes it a PITA to properly maintain the device (Samsung, y u do dis #2).

Row row row your boat Samsung.

 

[gekkehenkie11]

We're lone wolves here, the modem implementation for Exynos models (at least those with the ST-Ericsson modem) are vastly different from anything else (the Galaxy Alpha developer modpunk, who created the thread you linked, also works on Intel modems since the Alpha has one).



Thanks for the offer, but I'm afraid the modem here is just too special.
I'll let you know if I'm completely out of ideas some day (but it is not today, lol).

On a brighter (well, not really that bright) note, I think I know what might be going on.
My kernel messages indicate that SSP (sensor protocol started by sensor hub) is claiming a certain kernel node (a certain pin ctrl instance to be specific) but does not release it for some reason. The modem then tries to setup its socket and establish a connection to the radio on the same pinctrl node for some reason (Samsung, y u do dis), so early RIL bridges fail to be setup.

Another thing I noticed is that instead of being a good guy OEM and keeping their init scripts tidy, Samsung moved ST-Ericsson specific RIL arguments/restart command sequences to the main android init.rc script, so I might need to import the generic CM 12 init script and slap Samsung's changes on top of it to make the modem fire up properly. This causes all kinds of troubles since init.rc should really be provided by the platform and differs from ROM to ROM. It also makes it a PITA to properly maintain the device (Samsung, y u do dis #2).

Row row row your boat Samsung.

I feel your pain with all the mess Samsung likes to make And you're right, modem is very different than our models so I'm afraid you're on your own. But then again, it sounds like you're onto something there. Good luck mate ! And again, if there's anything you think I could help with, just drop me a message !

 

[calj17]

I read that Android 5.1 update is Rolling out by Google. Will cyanogenmod 12 be updated to Android 5.1 as well?

 

[thiagoribeirorj]

topic died. any updates of information, prior to download, beta ... nothing.

 

[invisiblesushi]

I read that Android 5.1 update is Rolling out by Google. Will cyanogenmod 12 be updated to Android 5.1 as well?

Yes, the newest android version 5.1 will automaticly be merged into cyanogenmod source code.

topic died. any updates of information, prior to download, beta ... nothing.

Relax it takes time, expect 2-4 weeks for an bootable build, and copule of months for an stable one.

Any non dev related questions should be posted in Q&A section.

 

[mkim055]

topic died. any updates of information, prior to download, beta ... nothing.

I dont see you trying to help, zip it.

Sent from my SM-N910U

 

[calj17]

topic died. any updates of information, prior to download, beta ... nothing.

Friend we first created a thread to raise fund to buy 1 note 4 to Raymanfx so that he could work in the port ot cyanogenmod 12 to note 4 exynos and we reached the goal.

Now He is alone to do all the work to port cyanogenmod 12 to our Phone. This Takes time and Hard work so be Nice and patience and try to coperate with the topic

 

[xvital]

We're pretty damn close to getting a full boot, I added a bunch missing radio/modem bringup blobs for the ST-Ericsson modem of the N910C (other variants with Intel modems will be supported later).
It looks like the modem fails to startup because of missing sockets though, here's an excerpt of the log:

I/MMD     ( 2826): [main, 1032] Modem Status is 3
D/DIP     ( 2828): AT socket not available. Retrying (try: 2)

(MMD is the modem daemon (started by cbd) and DIP is STE's debug binary)

I'd appreciate it if another developer (I know some of you are lurking in here ;p) could take a look at a full log.
Maybe I'm missing out on something obvious.
I'll continue to analyse these and try to figure out what kills our modem socket.

maybe i can help you if you can teach me the basics. I can understand fast and i can deal with Linux , so, maybe you can tell me what you did or show me the full log.

 

[jgfernog]

Yeah, I'd like to help u too. I created some works here at xda with i9500 devices. I have no much knowledge with it, but I can learn it very fast too, I just need a good kitchen and some pacient. I have the 910c device and it is available for your tests.

 

[calj17]

Any updates or New progress?


Enviado do meu iPad usando Tapatalk

 

[eydryan]

Awesome! I thought our crowdfunding attempt had died, it's great to see it is actually up and running! Good luck RaymanFX, really looking forward to have an awesome ROM for this awesome device.

 

[calj17]

Guys I talked to Raymanfx in Hangouts and he Still working in the modem problem to try to boot into CM12. We should try to talk to other developers tô help him with this modem stuff, help would be good

 

[arbi97]

Guys I talked to Raymanfx in Hangouts and he Still working in the modem problem to try to boot into CM12. We should try to talk to other developers tô help him with this modem stuff, help would be good

So,a.. How we help him?
And, only this problem he has? Or he has another problems?
All the same, i hope, he fix it, and, soon, we have 50/50 working CM 12! Good luck, Rayman!

 

[calj17]

So,a.. How we help him?
And, only this problem he has? Or he has another problems?
All the same, i hope, he fix it, and, soon, we have 50/50 working CM 12! Good luck, Rayman!

Maybe asking help in CM12 qualcoom note 4 thread

 

[MrAlez]

Maybe asking help in CM12 qualcoom note 4 thread

Maybe this great developers can help @JustArchi, @temasek , @arter97, @Lord Boeffla, @XpLoDWilD all this guys works with exynos and maybe asking them can be nice

 

[arbi97]

Maybe this great developers can help @JustArchi, @temasek , @arter97, @Lord Boeffla, @XpLoDWilD all this guys works with exynos and maybe asking them can be nice

Don't think, that Lord Boeffla do anythink about our phone, coz i asked him about the kernel for our phone, and he said that he doesn't do anythink, and he has many devices.......
. And another developers in your list, i don't know, do they or not... He, now, do CM for Note 3, OPO, SGS3...

 

[invisiblesushi]

Maybe asking help in CM12 qualcoom note 4 thread

Maybe this great developers can help @JustArchi, @temasek , @arter97, @Lord Boeffla, @XpLoDWilD all this guys works with exynos and maybe asking them can be nice

READ THE THREAD, its modem related problem, it can only be solved using the same device N910C, or an with the same or simmilar modem

Unfortunately we (snapdragon) have different modems than you guys so can't help you out here. But I had my own problems of getting the modem up. Just keep comparing a log where it boots (TW) to your current log and you will find it. But I'm sure that's exactly what you're doing I'm quite busy myself and also not sure if I could even help you out but if you're still wrestling with this next week, I'll take a look at your logs if you want. Good luck mate !

Thanks for the offer, but I'm afraid the modem here is just too special.
I'll let you know if I'm completely out of ideas some day (but it is not today, lol)