yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 Original Android Development] :
No friggin way!!!! I installed the n5 port rom but if rayman really does port android 6 I'm flashing back
[Galaxy Note 4 Original Android Development] pgilrene:
Heavy n5 rom haha
[Galaxy Note 4 Original Android Development] RaymanFX:
A wild Marshmallow appears!

https://plus.google.com/112066032679014459110/posts/3Afwdq3FaYW

(screenshot in the G+ post).
[Galaxy Note 4 Original Android Development] :
I love you man

---------- Post added at 05:27 PM ---------- Previous post was at 05:25 PM ----------

so like everything except ril work???? I bet fingerprint won't be supported by google
[Galaxy Note 4 Original Android Development] Ausboy 2011:
lookin good :D getting excited
[Galaxy Note 4 Original Android Development] a13x4nd3r:
woohoo!! Super excited about it.. but with marshmallow in the horizon will you continue your 5.1.1 build until mm get perfected?

Also.. seeing that RIL is not yet working kinda worries me.. Do you know the problem already or we were stuck just like the old day with super early lollipop build?
[Galaxy Note 4 Original Android Development] pgilrene:
Excited! Is this real life? Haha
[Galaxy Note 4 Original Android Development] Stocco:
Omg! I need this, you are the Best <3

Enviado de meu SM-N920C usando Tapatalk
[Galaxy Note 4 Original Android Development] masaichris:
I loving you alot man

Sent via Tapatalk from SM-N910H | TeamEOS AOSP Rom
[Galaxy Note 4 Original Android Development] ogo2012:
Excellent news! As always, great work for our Note 4. Much success to you, RaymanFX.
[Galaxy Note 4 Original Android Development] agentdeep:
Syncing source to follow [MENTION=3463426]RaymanFX[/MENTION] work ;)
[Galaxy Note 4 Original Android Development] mkim055:
So 5.1.1 bootloader, kernel, modem work with Marshmallow?
[Galaxy Note 4 Original Android Development] onbeskarakterli:
Obviously bootloader and 5.1.1 sources in the kernel work. Modem is not working (baseband is unknown).

---------- Post added at 04:00 AM ---------- Previous post was at 03:58 AM ----------

Sixperience N5 port is not heavy at all. Actually it works faster than AOSP ROM and original N4 TW ROM.
[Galaxy Note 4 Original Android Development] pgilrene:
I wont say it unless i havent tried it. its my opinion :)
[Galaxy Note 4 Original Android Development] onbeskarakterli:
I am using it right now and I tried the latest AOSP build a few days ago. AOSP build is laggier than I remember. It was really smooth with Googy kernel but he stopped developing for our phone. Sixperience v2 + Talexop 1.05 AIO Soft combination makes this phone the fastest it has ever been.
[Galaxy Note 4 Original Android Development] hognogger:
I just got a Note 4 early this week, and have been playing with the stock variants. Was fairly disappointed with the sound - harsh, fatiguing. Then I load up this ROM, and all that's gone. Good job!
[Galaxy Note 4 Original Android Development] white7561:
U know u can also use viper4android and using the Best driver. Then if u set it well. It will sound BOOM
[Galaxy Note 4 Original Android Development] CLShortFuse:
Hey [MENTION=3463426]RaymanFX[/MENTION], are you aware that the Galaxy Tab S2 is essentially an oversized N910C? Have you considering making an AOSP rom for that?

If you do, I'd buy that tablet in a heartbeat.

Also, the WiFi only version wouldn't have to deal with that pesky RIL.
[Galaxy Note 4 Original Android Development] RaymanFX:
Hey, I'd love to get my hands on one and create a platform on top of my current Exynos5433 work. Unfortunately, I don't own the Tab S2 and neither do I have the spare money to buy one just for my own development journeys. I also believe blind development is entirely pointless and the source of all evil in this world.

Also, I don't think the RIL would be that much of a problem, given that the N910C has an Ericsson M7450 modem, which wasn't even supported in CM until I started looking into it, so I guess I could work with pretty much any RIL at the moment.

And even if it turned out to be a problem, we could still run it as a wifi-only device (and turn off the RIL parts) as a last resort.

News regarding N910C:

I'm probably going to run a fresh userdebug M build later today (as opposed to the engineering one I screenshotted in the last post) and will start hunting for bugs (RIL and friends). I honestly only need to get the radio going, then I'll probably use it as daily (development) driver for myself so I don't have to flash between Lollipop/Marshmallow all the time.
[Galaxy Note 4 Original Android Development] tiguy99:
This guy's awesome!

Thanks to him and this thread, I've singlehandedly decided to buy a 910c over the Snapdragon version.

Thanks man.
[Galaxy Note 4 Original Android Development] andrew.mackew:
Thanks for your excellent work!

I wonder if we still should expect any lollipop update..

Because now that it's already stable maybe should worth to keep both LP and MM.. please, share your thoughts..
[Galaxy Note 4 Original Android Development] agentdeep:
Build error :(

external/openssl/crypto/bn/asm/armv4-gf2m.S:99:17: error: invalid operand for instruction
vmov.32 d26, r2, r1
^
external/openssl/crypto/bn/asm/armv4-gf2m.S:100:18: error: invalid operand for instruction
vmov.32 d27, r12, r3
[Galaxy Note 4 Original Android Development] andrew.mackew:
Are you trying to compile LP or MM?

BTW MM is already merged in Git for those who wish to follow [MENTION=3463426]RaymanFX[/MENTION] work.
[Galaxy Note 4 Original Android Development] agentdeep:
I was trying to build MM but got error as I mentioned..
[Galaxy Note 4 Original Android Development] agentdeep:
Still having the same error building MM..

Maybe there is problem with the source.
[Galaxy Note 4 Original Android Development] xbellox:
Is there any chance that we have fingerprint scanner working with Android 6.0 (native API)?

Thank you for the hard work!
[Galaxy Note 4 Original Android Development] :
no chance
[Galaxy Note 4 Original Android Development] masaichris:
Quick question guys, in the 20150930 build, is the IR Blaster working?? I can't seem to get mine to work...

About Kernel, is there any other AOSP kernel for SM-N910C/H that fixes the overheating while charging without breaking other thins like:

1. GooglyMax - Breaks proximity sensor

2. Ultimate Kernel - breaks USB MTP

Sent via Tapatalk from SM-N910H | TeamEOS AOSP Rom
[Galaxy Note 4 Original Android Development] pgilrene:
Working on me
[Galaxy Note 4 Original Android Development] masaichris:
What App are you using???

Sent via Tapatalk from SM-N910H | TeamEOS AOSP Rom
[Galaxy Note 4 Original Android Development] pgilrene:
Peel smart remote (watch on)
[Galaxy Note 4 Original Android Development] renanterzi:
Where's mm rom?
[Galaxy Note 4 Original Android Development] 557953:
Ready and waiting for you, just build it yourself and you don't have to wait!!!
[Galaxy Note 4 Original Android Development] agentdeep:
For those who want new build

https://mega.nz/#!IRQWSJzB!g6LIKHckjbIL4yT8epH_hf4xCAWXIdJqYz5XzbVw1_4
[Galaxy Note 4 Original Android Development] renanterzi:
I'm not too smart my man!

---------- Post added at 05:43 PM ---------- Previous post was at 05:42 PM ----------

@agentdeep...you try this one? It works?
[Galaxy Note 4 Original Android Development] agentdeep:
I built it from source and running in my phone right now..

This is 5.1 btw..
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Yeah I used that before having discovered android image kitchen. That tool is way more versatile and easier to use, try it, I'm sure you'll love it. Drag the boot image onto the 'unpackimg.bat' and it unpacks everything into two directories. Edit whatever you want and click 'repackimg.bat' and you're done ! Really couldnt be easier than that.
[Galaxy Note 4 Original Android Development] gekkehenkie11:
So, anything yet [MENTION=3463426]RaymanFX[/MENTION] ? Did you succeed at getting that extra logging info ? If so, could you post the logs ?
[Galaxy Note 4 Original Android Development] RaymanFX:
Hey, I'll grab logs from stock later, meanwhile here are those from my cm-12.1 build of today.

radiolog6: logcat -b radio (with debug level set to 4)

dmesg1: dmesg (look for the lines starting with "mif: ")
[Galaxy Note 4 Original Android Development] gekkehenkie11:
"LoadLogLevel: Log level is 4."

Great to see that it worked ;) This extra log info is what we need. Awesome. Really looking forward to the stock one. Ah, one thing, could you maybe add the option -v time to the logcat command ? Thanks mate !!

---------- Post added at 11:17 PM ---------- Previous post was at 11:12 PM ----------

Ah, rayman, something else, could you make the dmesg buffer a bit bigger ? The first 2 seconds are missing and usually there's interesting stuff there. Just change in your defconfig:

CONFIG_LOG_BUF_SHIFT=18

to:

CONFIG_LOG_BUF_SHIFT=20

Which should get you a 4x bigger kernel log buffer (don't set it above 21 though, buffer will be minimal size again). Thanks mate !!

---------- Post added at 11:38 PM ---------- Previous post was at 11:17 PM ----------

Just took a look at your log, right now, without having seen your factory log, it seems to me that your problem is the interface not being brought up. To me this looks very weird:

E/RILD ( 2863): Modem config #0: index[0], iftype[3], ifname[/dev/umts_ipc0], mtype[4], proto[1], protover[2], dbg-ifname[IPCDEBUG_UNIX_SOCKET]
E/RILD ( 2863): Modem config #0: rfsIfName[/dev/umts_rfs0], nvHeader[nv], modemDev[/dev/block/mmcblk0p13], nvSize[1048576], nvDir[/efs] nvOffSet[10485760]
E/RILD ( 2863): Modem config #1: index[1], iftype[4], ifname[imsd], mtype[8], proto[1], protover[8], dbg-ifname[]

I find a few things very weird, like it's saying two times config #0, there are different interface names in line the first 2 lines and the interface name itself doesnt correspond with the interfaces it's checking later on. Needless to say, there's no succesful bringing up of the modem interface in the log at all. Would love to see a new dmesg, but with bigger log size like I just described, to catch the first 2 seconds too ! And of course the stock output, to compare those 3 lines to !!

*EDIT* actually, that 2x config 0 is probably cause the RIL code is slightly different than mine and just giving some extra info in that second line. I'd say, the modem is configured for the wrong interface or the driver doesn't load correctly, but would have to see the stock log.

BTW, this is how it looks like in my Cm12 910F log:

04-18 17:23:07.923 E/RILD ( 329): Modem config #0: index[0], iftype[10], ifname[rmnet_mhi0], mtype[4], proto[10], protover[10], dbg-ifname[]
04-18 17:23:07.923 E/RILD ( 329): Modem config #1: index[1], iftype[10], ifname[rmnet_mhi0], mtype[32], proto[1], protover[1], dbg-ifname[IPCDEBUG_UNIX_SOCKET]
04-18 17:23:07.923 E/RILD ( 329): Modem config #2: index[2], iftype[4], ifname[imsd], mtype[8], proto[1], protover[8], dbg-ifname[]

Followed quickly by the success words:

04-18 17:23:07.925 E/RILD ( 329): [NIF] Interface(rmnet_mhi0) is up.

That's what we want to see in your logs too ;)

I'm confident we can get this working mate !
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Hey Raymann, not sure if you tried it, but make sure that you're on the same bootloader, modem, efs etc as your kernel version. So, flash the exact same samsung ROM as you've downloaded the kernel code for and then flash your CM12. This might be causing all your problems.

I was just reverse engineering the RIL you're using and the modem config is hardcoded, so there's no selection going on (which probably is the case for all samsung RIL's, never really looked into it). The interface it's using really is that "/dev/umts_ipc0" and that rfs0. It's ALWAYS using those (btw do you see that /dev/umts_ipc0 and rfs0 if you ls the /dev/ dir from within adb shell on your CM12 ?). Anyway since I see references to the /efs partition I figured, maybe he's hasn't matched the kernel to those partitions. So if not, try that first please :)
[Galaxy Note 4 Original Android Development] gdonanthony:
i think OP is too bz for this development...

but still thank you
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Nah, he's from Germany, it's 03:45 AM there ;) But just posting stuff for him to look at tomorrow. I'm sure we can get this going !
[Galaxy Note 4 Original Android Development] arbi97:
Man, good luck. Hope, you with Rayman do the normally CM for our device!!!
[Galaxy Note 4 Original Android Development] RaymanFX:
Hey, I flashed the official 5.0 release before anything else, so I'm pretty sure I'm on the latest baseband et all.

I objdump'd the ril libs a while ago already and checked for the dev interfaces.

"dev/umts_ipc0" exists with the same permissions as on stock.

"dev/rfs0" does exist neither on stock nor on my cm-12 builds.

Btw, I confirmed my /efs partition is mounted on my cm-12 builds, and it obviously contains the same files like stock.

Attached are 4 new logs:

dmesg.txt - dmesg from my latest cm-12 build with increased log buffer (set to 20)

dmesg_stock.txt - dmesg from Samsung stock

radiolog.txt - logcat from my latest cm-12 build with -b radio and -v time

radiolog_stock.txt - logcat from stock with -b radio and -v time

There's one issue though: while the debug property (ro.debug) set to 4 works perfectly fine on cm-12 (as you noticed), it does not seem to work with Samsung stock. It gets overridden by the kernel command line each time.

I cannot edit the command line because there is none. All the unpack tools show an empty cmd line, which basically means what I said earlier, it reads the command line from the bootloader each time.

So what I did instead was unpacking and repacking the ramdisk with the debug prop added to default.prop. This works on cm-12, but for some reason it doesn't on stock. I'll keep digging for the issue..

EDIT:

I should probably note that I'm doing all this debugging with no SIM inserted, neither with CM nor with stock.

However, stock obviously still shows a valid baseband and emergency calls are available, whereas on CM, none of these functions work.
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Thanks for you info Rayman ! Just one quick question though. You said you flashed official 5.0 before anything else. But are you 100% sure the ROM version matches the kernel version ? Not sure if I'm expressing myself clearly here, what I mean is, that if you look here at the column version: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=910C that that version, like "N910CXXU1ANJ4" matches exactly the version of the official samsung ROM you've flashed BEFORE installing Cm12. If not, I really think that might be your problem (cause you then might be on different EFS/bootloader/modem partition for example than the kernel version, seeing you guys have source code form 6 different samsung kernels already, that might be the case here.)

*EDIT* you probably could simply check it by comparing the BASEBAND version in your phone's Cm12 info screen to the kernel version you've downloaded, they should match. My yesterday's conclusion was that it almost HAS to be this problem, but I haven't looked at your new logs, going to do that now :)

The SIM should not matter indeed, since the modem doesnt even get up. Thanks mate, we're going to break this one together :)

---------- Post added at 06:12 PM ---------- Previous post was at 05:21 PM ----------

@RaymanFX I just looked at your log, it seems you didnt set the loglevel to 4 for the factory ROM.

*EDIT* ah I see you commented about it, going to look into that ...

*EDIT1* ah damn you're right, there isn't even a commandline for the stock kernel ... that's odd ... Going to find a way to solve this ...

*EDIT2* I just checked, all my 910F ROM's have that commandline. Not sure what's going on but I have an alternative way :) I'm going to crack and patch that RIL you've sent me, to always use loglevel 4. You can then paste it back onto the ROM image you've extracted it from and then run it.

Gimme an hour or so ... :)

*EDIT3* actually this is an easy hack, ready in 5 minutes ;)
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Ok done ! Attached is the hacked version of the RIL you've used in your repo. It won't mind the kernel command line. You still need to set that debug property to 4 though, like you previously did. But this time it should work for stock too :)

So, install the stock ROM you pulled this RIL from, overwrite the RIL with this patched version, set that debug property to 4 and you should have log level 4, regardless of kernel command line :)
[Galaxy Note 4 Original Android Development] Danmann:
Whatever it means. Sounds good. Thanks a lot. ;)

SM-N910U
[Galaxy Note 4 Original Android Development] gekkehenkie11:
The "log level" determines the amount of information in the log file. Simply said, the more information, the easier it is to understand what's going wrong. So with this hacked RIL, Rayman can now get the maximum amount of logging info from the stock version. We can then compare it to the CM12 version and that hopefully will be enough to find the problem and fix it.

No reaction from Rayman yet though, hoping he'll have time today to try it !
[Galaxy Note 4 Original Android Development] RaymanFX:
Hey, sorry for the late reply, silly real life gets between me and Android sometimes.. :angel:

Here is a new radiolog from stock, this time with debug level 4 (thanks for the blob).

The log was too large to upload it here this time.

I think the issue is this (from my cm-12 logs):

04-19 13:09:09.272 E/RILD ( 2861): SetSimOperator: invalid operator

At this point in the stock log, it successfully lists all the valid Sim Operators.

I dug into CM's telephony framework, but couldn't find the culprit yet.
[Galaxy Note 4 Original Android Development] gekkehenkie11:
No worries mate, busy with some stuff in real life today too, so won't have a lot time today neither, but will surely look into it too ! And great to see it worked with the logging level this time ;)
[Galaxy Note 4 Original Android Development] gdonanthony:
oh yesss!! my CM source is sooo ready for building :)
[Galaxy Note 4 Original Android Development] RaymanFX:
Hey :)

Good research there, but unfortunately SeLinux is not the issue here (almost sure).

Fixing the AVC denials was my first idea when I stumbled across this problem, so what I did was setting it to permissive via ramdisk (remember, I cannot edit the kernel command line, it always gets ro.selinux=enforcing from the bootloader), the code is here:

https://github.com/RaymanFX/device_samsung_trelte/blob/cm-12.0/device_trelte.mk#L259.

A quick getprop on my latest cm-12 builds confirms that this works, as I'm clearly getting this:

[ril.cbd.boot_done]: [1]

which means the prop got set. Setting SeLinux to permissive only logs the potential denials, so that's why these still end up showing in the logs.

Good idea though, you're definately helping here!
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Hmmm... But why are we not seeing anything related to cbd at all in the radio log then ? Something must be wrong here, Rayman ... I still think it must be some permissioning problem keeping cbd from communicating with RILD. If not Selinux, then maybe chown/rwx issue's ?

Cause:

1) We do know cbd boots the modem correctly

2) We do know that RILD never sees the modem getting up.

3) We don't see ANYTHING related to cbd in the RILD log.

But yeah I think you're right about those *potential* denials ... Hm.....

---------- Post added at 06:59 PM ---------- Previous post was at 06:36 PM ----------

Ok I did some reverse engineering of cbd. We see this in the dmesg log, right:

mif: cbd: check_debug_level: debug level=0, cp_debug=0

However we do NOT see this in the RILD buffer log for CM12 (only in stock) :

cbd: check_debug_level: debug level=0, cp_debug=0

I just checked the cbd code. The routine that prints this message to the kernel log, ALSO prints to the radio log !! In fact, there's no condition between it, no branch. So it 100% DOES try to print it to the radio log too !! It just doesn't arrive in that log ... Going to see if I can find out why that is, but I think this is our problem: the communication between cbd and the RILD. I think the same reason why we're not seeing anything at all in the radio log, is the same reason why the RILD never knows about the modem getting up.
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Hmmm ... not sure yet why we don't see anything in the radio log related to cbd. But I do now understand that this probably isn't related. What I did is check out how RILD determines that the modem is online. It works like this: the RIL issue's an ioctl with flag "IOCTL_MODEM_STATUS". It then checks if the return value is 4. If it's 4, it prints that the modem is online and continues doing its normal startup process. If not, it prints the modem status together with its return value, sleeps 0.5 seconds and loops like that. That's indeed what we see in the output.

So, question is, why doesn't that return value never get '4' in CM12, when it does get that in stock. Going to look into that next ....

---------- Post added at 09:36 PM ---------- Previous post was at 09:26 PM ----------

Hmmm here you can see modem states in the kernel code, they are:

enum modem_state {
STATE_OFFLINE,
STATE_CRASH_RESET, /* silent reset */
STATE_CRASH_EXIT, /* cp ramdump */
STATE_BOOTING,
STATE_ONLINE,
STATE_NV_REBUILDING, /* <= rebuilding start */
STATE_LOADER_DONE,
STATE_SIM_ATTACH,
STATE_SIM_DETACH,
STATE_CRASH_WATCHDOG,	/* cp watchdog crash */
};

So, state 3 is STATE_BOOTING, state 4 is STATE_ONLINE, but state 2 (which we get to instead of state 4) is STATE_CRASH_EXIT .... So it seems the modem just crashes !?!? Although it seems to coincide with the time_out so it also could be that the RILD sets it simply to 2 after the time out. Going to look into it some more ...

---------- Post added at 09:50 PM ---------- Previous post was at 09:36 PM ----------

LOL I can see now why you've been working so long on this Rayman, it isn't the easy fix I had hoped ;) It indeed seems the modem is crashing for some reason (state 2). In the log it sets it to that state here:

So that's where it must be crashing ... Going to look into it some more :)

---------- Post added at 10:17 PM ---------- Previous post was at 09:50 PM ----------

Ok Rayman, so we need to find out why the modem crashes insteads of coming online ... I just made a new discovery. In stock ROM, just before it comes online, it detects the modem as an USB device, like:

That's our modem. This never happens in CM12. Then shortly after this it sets the modem state to 4:

So, I think this is our lead now. going to look into it again...
[Galaxy Note 4 Original Android Development] pgilrene:
Changelog? Thank you very much!
[Galaxy Note 4 Original Android Development] Fikret488:
I'm on DN5 V3 Custom rom. And I'm interested in right goes another precedure, or full wipe everything and has a flash or something else? Thanks for your reply.
[Galaxy Note 4 Original Android Development] muratbaizhanov:
please try to clarify your question. it is really hard to understand.
[Galaxy Note 4 Original Android Development] Bishal 00:
Guys just being curious :D... If i flash this rom in SM-N910U and flash 5.1.1 bootloader and sumax kernel will it show simcard....i have done this in other SM-N910C rom and got sim card working...... ;)
[Galaxy Note 4 Original Android Development] jayyysss:
I think...

He said that He wants to install this Rom. And if He need to do the same procedure that He did in installing DN V.03 Rom.
[Galaxy Note 4 Original Android Development] agentdeep:
I don't think so because Suemax kernel is for TW, and this ROM is AOSP...

But you could try.
[Galaxy Note 4 Original Android Development] ogo2012:
If understood correctly , you sink firmware you want to change to AOSP, then full wipe.

In the meantime, new build available 20151013

Changelog is not known.