yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 General] gekkehenkie11:
He said he used N910FXXU1ANK4_N910FOXA1ANK4_DBT.zip (which he used on his phone) to extract the blobs. My theory currently is that it's not the version, but missing blobs that the standard script didn't extract. For example in his package were firmware blobs for the cam, those were never extracted with the script. So my theory is that it's in of the files that were in his package, but not extracted with Slayh'ers 910T script. I'd need to look into that though.

Anyway you said you were not going to maintain the TRLTE branch. I think it makes sense, it's just a lot of work and it seems it's pretty much the same as TRLTETMO anyway. The only difference are:

* We need 910F blobs instead of 910T (and libtime_genoff.so)

* 910F Modem needs mhi.ko, 910T doesn't

* mixerpaths were not correct, but then again, maybe we can use a joint version that works for both 910F and 910T. Or just treat it as a 910F blob.

I don't think there's more to it ? And then of course we need a slightly different boardconfig because of the partition sizes (and MHI loading). What would be the best way to proceed then ? If we change our boardconfig, we'll have problems syncing Slayher's branch, is that correct ? (at least I always run into that problem, my repo sync complaining about changed files) Or is there any way to overcome that ? Sorry for my GIT/repo n00bishness ;)
[Galaxy Note 4 General] hav0c:
When CM was being ported to the N9005 there where battery drain issues too. These were mainly caused by the touchscreen driver and solved by http://review.cyanogenmod.org/#/c/56805/
[Galaxy Note 4 General] gekkehenkie11:
I haven't looked into all that (power resume/spending), but I hope [MENTION=2457777]slayher[/MENTION] and/or [MENTION=3041959]fattire[/MENTION] is not going to use the Framebuffer hook. I worked on that for the S4, which had slow resume times and that was because CM11 would resume touchkey first and then the display. Same happens I noticed on our Note 4 Cm12: after a resume, you see the touckeys below your display light up and THEN the display. This adds some slowness but on our Note 4 it's not too bad. However I think about changing that in the future.

Anyway, for the S4 I changed that, resuming display first and then the touchkey. I had to remove the framebuffer hook of resuming touchkey (since that hook runs before before framebuffer call returns, so that will ALWAYS first resume touchkey) and I had to implement the standard Touchwiz power HAL of powering down/up the touchkey. I think I will look into all that later too, but again, for our Note 4 it's not bugging me that much since wakeup isnt that slow anyway ...
[Galaxy Note 4 General] Preaper:
I am planning on using the original N910F kernel source one day. I just dropped it for now as it was holding me back. It's pretty complex, as I had conflicts while cherry picking some of Slayher his fixes. But still important non the less. There are quite some differences between the Samsung N910F/N910T kernel sources. Some CPU scaling stuff and more. So I will continue on this venture and release this one day. Or somebody else will beat me to it as it is usually the case :) (love that btw)

The mixer paths should ultimately be handled via overlays so we won't rely on the trlte-common for this. The starting mdm_helper should also go into one generic init.qcom.rc script with conditions so the mdm_helper is only started on the N910F. That way the common repo truly is common

Regarding the boardconfig - This is trltexx specific. We will separate have a trltexx repo and we will never merge this back into Slayher his trltetmo branch.

edit:

Concerning the blobs: I did a diff and I don't see any extra blobs in 'ano dev' his zip. he doesn't have more blobs than the extract-files script copied for me.
[Galaxy Note 4 General] pbedard:
I was told not to share or post links anywhere its great only two us variants right now working...?
[Galaxy Note 4 General] jdidtht:
Bummer
[Galaxy Note 4 General] gekkehenkie11:
Ok, my note 4 is up and running. I tried the recovery img that I cooked up, that didn't work unfortunately. I figured it might be due to recovery.fstab not being correct, so I changed it to:

/system ext4 /dev/block/mmcblk0p24
/data ext4 /dev/block/mmcblk0p27
/cache ext4 /dev/block/mmcblk0p25
/efs ext4 /dev/block/mmcblk0p13
/boot emmc /dev/block/mmcblk0p17
/recovery emmc /dev/block/mmcblk0p18

After that I figured let's use my own kernel as a source, so I dumped it again and am now rebuilding the recovery imaged based on that kernel ... Going to retry when the image is ready !
[Galaxy Note 4 General] gekkehenkie11:
Damn, the recovery still doen't boot ... Going to research some more ...
[Galaxy Note 4 General] gekkehenkie11:
BTW, just found this tutorial: http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html

It describes pretty much what I did ... not sure what's wrong ..

*EDIT* same thing here: http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device

Yeah that's what I did ... maybe the block_size is not right ... but how to find out the block size ?
[Galaxy Note 4 General] gekkehenkie11:
"If you change the contents of the BoardConfig.mk file, you will have to run ‘make clobber’ or the changes won’t get picked." hmmm just tried that too, no luck neither ...
[Galaxy Note 4 General] gekkehenkie11:
I see that some configs use 4096 ... risking bricking my device going to try that out for you guys :)
[Galaxy Note 4 General] gekkehenkie11:
Nope, no boot neither ... damn ... runninig out of idea's here ...
[Galaxy Note 4 General] F4M0U569:
We all are clueless, you ought ask good devs like [MENTION=2326222]nighthawk626[/MENTION] who successfully ported lollipop to the note 3 and [MENTION=2827150]Moepda[/MENTION] or [MENTION=2849215]manups4e[/MENTION] and [MENTION=4258086]firebird11[/MENTION] who also successfully ported lollipop to the g3. Here is a nice guide he made to build your own cm12

http://xdaforums.com/lg-g3/development/guide-how-to-build-cyanogenmod-12-t2953132
[Galaxy Note 4 General] gekkehenkie11:
Help from everybody is welcome ! But I think I have some new clues, going to try some new things tomorrow ! But for now, off to bed ...
[Galaxy Note 4 General] allenjthomsen:
I been looking at the specs of the note 4 vs nexys 6 they contain the same cpu and gpu if we were to take the nexus 6 stock .img and replace some files i think we can get a booting build.

By the way if anyone can give me a working boot.img zip for cm12 i can probably port factory nexus6 rom
[Galaxy Note 4 General] utopiate:
I see the S4 now has a lollipop port, tis only a matter of time oh yes.... lol
[Galaxy Note 4 General] pbedard:
Sooner then u expect
[Galaxy Note 4 General] utopiate:
ooh your such a tease lol
[Galaxy Note 4 General] gekkehenkie11:
Ok guys, new day new idea's :) Since we have working recovery images from others, like the one from CWM, I figure that's good starting point. So, going to reverse engineer those and hopefully find out by comparing mine and that one, what the problem is ...
[Galaxy Note 4 General] gekkehenkie11:
The issue seems to be preliminary the kernel itself. The main 'program' that is running from the recovery is located in the ramdisk, in the sbin directory (and simply called 'recovery'). So, I figured, let's try the ramdisk first then with a kernel from an image that works. It then at least goes a bit 'further' -> with the cooked up kernel the bootloader immediately throws me into the standard recovery mode, saying it couldnt boot the other one. But when I combine my ramdisk + 'correct' kernel it doesn't do that, it say it's loading and then just 'hangs'.

So, I looked a bit further into the kernel, decompressed the image(s) and a big difference between the 'cooked up' kernel and the one from Samsung (but also I checked Phil's CWM recovery), is that there's a "recovery.img-dtb" file in both the Samsung and Phil's image, which is not present in the 'cooked up' kernel.

I then googled:

"The idea behind device tree is quite simple. When the kernel starts, it needs to initialize the drivers for the devices on the board. But often on embedded systems, devices can't be discover at running time. In this case, the Linux kernel has a c file that initialize the devices for the board. So the kernel must be modified/compiled for each board.

Another way is to provide a small file that describe the board to the Linux kernel. When the kernel start, it reads this file (called dtb for Device Tree Binary) to know the devices on the board, and initialize usefull drivers. "

http://www.armadeus.com/wiki/index.php?title=Kernel-with-device-tree

So the standard CM procedure doesn't yield such a DTB file and it seems we need that to run the kernel.

Anyway, I also figured, let's then use a working recovery img's ramdisk + kernel and just replace /sbin/recovery in the ramdisk. That doesn't work neither... But thinking of it, that might be because of different base address for the ramdisk, I saw that both Samsung's and Phil's ramdisks are loaded to 0x2600000 and while the cooked up one is loaded at 0x01000000 ... Not sure if that has effect on the address in memory of the executable though ...
[Galaxy Note 4 General] gekkehenkie11:
"2) Kernel compile will generate the DTB" from: https://github.com/xiaolu/mkbootimg_tools/blob/master/dtbtool.txt

Hmmm ... maybe then we need to really build the kernel itself instead of using the prebuilt one ...
[Galaxy Note 4 General] gekkehenkie11:
Ok, copied the samsung kernel sources to /kernel/samsung/trlte, let's see if CM is going to build the kernel now ...
[Galaxy Note 4 General] gekkehenkie11:
Ok, the CM building procedure now sees that the kernel source code is present. However it breaks with

build/core/tasks/kernel.mk:91: **********************************************************

build/core/tasks/kernel.mk:92: * Kernel source found, but no configuration was defined *

build/core/tasks/kernel.mk:93: * Please add the TARGET_KERNEL_CONFIG variable to your *

build/core/tasks/kernel.mk:94: * BoardConfig.mk file *

Yeah that makes sense :) But which config file to use ... I think two are used by samsung as standard ... Going to try some things ...
[Galaxy Note 4 General] gekkehenkie11:
Hmmm... I'm unsure how to set kernel defconfig up. In the Kernel readme from samsung it says:

make VARIANT_DEFCONFIG=apq8084_sec_trlte_eur_defconfig apq8084_sec_defconfig SELINUX_DEFCONFIG=selinux_defconfig

And in the CM kernel.mk it says:

# kernel configuration - mandatory

KERNEL_DEFCONFIG := $(TARGET_KERNEL_CONFIG)

VARIANT_DEFCONFIG := $(TARGET_KERNEL_VARIANT_CONFIG)

SELINUX_DEFCONFIG := $(TARGET_KERNEL_SELINUX_CONFIG)

So, those last two are obvious and can be used from that samsung readme. But kernel_defconfig itself ??
[Galaxy Note 4 General] Beukhof1:
Since I upgraded to the most recent gekkehenkies build. Still no battery drain with screen on or off.
[Galaxy Note 4 General] gekkehenkie11:
Yeah we need different kernel sources, that's indeed also another complication ...
[Galaxy Note 4 General] Preaper:
Concerning the blobs: I did a diff and I don't see any extra blobs in 'ano dev' his zip. he doesn't have more blobs than the extract-files script copied for me.
[Galaxy Note 4 General] gekkehenkie11:
Ok I will look into all that right now then :)
[Galaxy Note 4 General] gekkehenkie11:
BTW, wait, you are still using 910T kernel ? Why ? Just replace the kernel with 910F and go :) And of course update the pointers to the config files
[Galaxy Note 4 General] allenjthomsen:
Hey [MENTION=346046]Preaper[/MENTION] pm me
[Galaxy Note 4 General] jaapschaap:
To bad, can't download the BLOB :S

[MENTION=3296134]gekkehenkie11[/MENTION]

Do you prefer filedropper? I can upload it to one of my webspaces if you want (or give you a ftp login)...
[Galaxy Note 4 General] Preaper:
Yes i am. I never got cyanogenmod to compile for me using the N910F kernel. You did? Or do you compile the kernel separately and just replace the boot.img?
[Galaxy Note 4 General] gekkehenkie11:
Yeah. I don't think I remember I ran into any issue's at all.
[Galaxy Note 4 General] gekkehenkie11:
Maybe someone else can upload it all to megaupload for example ? Several people have downed it, this is their chance to help others out too :) I'm busy checking stuff right now
[Galaxy Note 4 General] indisingh:
Currently experiencing the same issue with the blobs download link. If somebody could create a mirror that'd be great!

Also, (sorry for the noobishness in advance) but what exactly is this "blobs" package for - I have the 910F btw.

Thanks very much.

Also getting the "E:Error executing updater binary in zip "......"" in TWRP, any idea why this is? do i need to download the rom straight to the mobile? I wiped cache, dalvik and data
[Galaxy Note 4 General] lycan_codex:
I used Phils recovery and after wiping the device (boot/data/cache/system partitions), I have flashed the recent build of OP plus blobs plus minimal gapps. After lowering the CPU frequency to 300 Mhz, I havent experienced lag...also, phone getting hot also has reduced so much so that i have decided this to be my daily driver.
[Galaxy Note 4 General] jaapschaap:
Thanks for the reply, it just start working again, but i will make a mirror for you (drive & mega).

Nice work, gonna install it ASAP (making a backup as we speak)!!!

Mirrors:

https://drive.google.com/folderview?id=0BxYSmBZxdWBbMmZnYkRuUlJ3Wm8&usp=sharing

https://mega.co.nz/#F!rZkFlRyA!FM4dwi3nw3UfeFuc-bNkSg

Instructions:

http://xdaforums.com/showpost.php?p=57621692&postcount=934
[Galaxy Note 4 General] Preaper:
Ok, now I'm confused. Either the compilation issues I had weren't kernel related at all, or you have a different sourcefile package from Samsung(mine came from SM-N910F_EUR_KK_Opensource.zip).

I'll try to compile with the original kernel again when this build is finished.

Edit:

This is the issue I ran into: http://xdaforums.com/showpost.php?p=57557513&postcount=791
[Galaxy Note 4 General] gekkehenkie11:
Ah yeah actually I remember running into that too :) Don't remember quite how I solved it though, if it was gone just after syncing again or that I changed some stuff. I can look into that later for you, gotta go now unfortunately. BTW, I was comparing blobs, I saw that in the two "proprietary-files.txt" it puts a '-' in front of a few blob names, one of them is that libtime_genoff.so, not sure what that means, haven't really checked that out, but that might explain why we were missing that lib ? Furthermore it lists this:

lib/hw/camera.apq8084.so:lib/hw/camera.vendor.apq8084.so

While I think it should just list that as this:

lib/hw/camera.vendor.apq8084.so

Apart from that, everything seems to be there indeed. However there are also those blob makefiles, will need to look into that too. If I understand it correctly, the files I just checked are used for extracting and those makefiles are used for putting the blobs back into the output FW.

I understand why we didnt have any sound with RIL, that was just that wrong mixerpath (and maybe those other 3 audio config files). But the camera, maybe something went wrong with that camera vendor so file ? Anyway gotta run now ...
[Galaxy Note 4 General] albireox:
How did you manage to lower the CPU frequency to 300Mhz? Here, it seems to stick to 1700 something Mhz for the lower value.

LE: apparently it works with Trickster after a few tries to stick to 300-2650Mhz.
[Galaxy Note 4 General] boksheng:
Hi,

I'm using 910G tho, where do I get 910G's Phlis recovery?

I tried to flash it with TWRP, all I get is "This package is for device: trltetmo, trltecan; this device is trltedt.

Please help.

Thanks.
[Galaxy Note 4 General] utopiate:
probs partition tables. I would flash origina;l stock rom with odin then whichever recovery you want.
[Galaxy Note 4 General] fattire:
Not sure which line in the makefile you're referring to, but usually a minus (-) sign in front of an import for example means to import if you can, but if the file isn't there, don't break the build.

gekke-- if you come to irc when you're ready I'm sure there's a way to harmonize your build with slayher's so that your device tree can build seamlessly with tmo and spr etc..

The IRC channel we're all using in the other thread is #cm-note4 on freenode and you can get to it quickly here.
[Galaxy Note 4 General] Preaper:
Yes, libtime_genoff.so shouldn't be excluded. But that is something Slayher did on 22-oct. camera.vendor.apq8084.so was a part of proprietary-files.txt since 22-oct as well. I have them and all i ever did was use extract-files.sh

(see: https://github.com/jaapp/android_device_samsung_trlte-common/blame/cm-12.0/proprietary-files.txt )

BTW - 'Ano dev' is using the slayher kernel (N910T kernel) as well! Since you aren't THAT seems to be the most likely reason for the lag and batterydrain.
[Galaxy Note 4 General] lycan_codex:
Hi< Even i have N910G, I flashed phil recovery for N910F , that works for N910G as well. After flashing a stock touchwhiz ROM, flash Phils recovery for N910F.
[Galaxy Note 4 General] gekkehenkie11:
Thanks fattire, will check it out when at home.
[Galaxy Note 4 General] albireox:
Happens here too, after playing a little with Neutron Player configuration, getting back into launcher it lagged a lot. After locking/unlocking the screen all was snappy again. Strange.
[Galaxy Note 4 General] Preaper:
Ok, my build succeeded. Time to test it

In the meanwhile. The N910F kernel repo i've been creating is looking pretty good at the moment. I think I can release this soon.
[Galaxy Note 4 General] Er. Aditya:
probably the best news for the day....thanks bro:good::good:
[Galaxy Note 4 General] Preaper:
Unfortunately I have to leave for some hours now.
[Galaxy Note 4 General] lycan_codex:
Please post your builds as well when you have time.
[Galaxy Note 4 General] utopiate:
Ok, so I've been using this new build from gekkehenkie11 since it was uploaded. Would like to nominate this build as the build that opens the dedicated rom thread :)

Some quick initial feedback;

I haven't noticed any lag nor noticeable heat issues.

No FC's

All call text data functions working

Seems stable and smooth enough for me to at least keep it on as a daily for a few days to give it a good test.

Ok and here are a couple of bugs etc

Device reports as the tmob variant 'SM-N910T'

Data icon reporting 'LTE' whereas it should be '4G' here in the UK (localisation issue/N910T related?)

Min CPU set to 1.7ghz

Kernel info showing at bootup

I disabled the 2 services suggested by gekkehenkie11

Set min cpu to 300mhz via antutu cpu master

set animation scaling to .5 (dev options. certainly just a personal preference)

Big congrats to all who have contributed thus far
[Galaxy Note 4 General] albireox:
What are those services?
[Galaxy Note 4 General] utopiate:
http://xdaforums.com/showpost.php?p=57622200&postcount=941
[Galaxy Note 4 General] Planet X:
Does vibration feedback is working on this build? On the other build from the unknown dev vibration wasn't working at all. Camera did work well for me. And lots of unexpected reboots.
[Galaxy Note 4 General] utopiate:
... er wut? lol sry dude I don't know what 'trilling' is? although according to the urban dictionary it refers to sitting around gettin high with your friends lols
[Galaxy Note 4 General] Planet X:
Sorry, trilling means vibration. I totally forgot about the real english word.
[Galaxy Note 4 General] utopiate:
lol no worries, just checked and can confirm 'not working' although I haven't dug around in the settings yet
[Galaxy Note 4 General] Er. Aditya:
guys does first boot takes like 15 mins ....its still havnt booted
[Galaxy Note 4 General] albireox:
I don't remember taking that long here...
[Galaxy Note 4 General] Er. Aditya:
its quite hot as well
[Galaxy Note 4 General] albireox:
Well, it gets a little hot at first, until all the sync and media scan takes place. But after that seems ok.
[Galaxy Note 4 General] utopiate:
nope installs very quickly for me and even 1st boot was quick

---------- Post added at 11:39 PM ---------- Previous post was at 11:37 PM ----------

ok so after some investigation the vibration does seem to be working. Haptic feedback works, call vibration is set to 'off' as default but works when switched on.
[Galaxy Note 4 General] Er. Aditya:
the version i got yesterday worked nicely but this latest build dsnt wants to boot at all, what possibly could i be doing wrong guys ??

i just reflashed and still no signs of booting up
[Galaxy Note 4 General] utopiate:
This is the build im using http://xdaforums.com/showpost.php?p=57621692&postcount=934
[Galaxy Note 4 General] albireox:
Have you flashed the blobs too?
[Galaxy Note 4 General] utopiate:
derp post deleted
[Galaxy Note 4 General] Er. Aditya:
yes bro still it dint boot am gonna try again

http://xdaforums.com/showpost.php?p=57595235&postcount=852

this was the build i tried yesterday that worked
[Galaxy Note 4 General] albireox:
Haven't tried that one. You should probably try without gapps at first, see if this way it boots.
[Galaxy Note 4 General] gekkehenkie11:
[MENTION=346046]Preaper[/MENTION]: so I just finished analysing the blob files. Like said, in the 'proprietary-files.txt' there are a few lines starting with a '-', Fattire mentioned that this signifies that those files shouldnt break the process. In the vendor-blobs makefiles however these filese aren't referenced, so they're not appearing in our final package, yet ano dev included them.

Files that ano dev included but weren't in the blob files:

app/com.qualcomm.location.apk (this is referenced in another makefile though)

app/TimeService.apk (this is referenced in another makefile though)

lib/libtime_genoff.so

vendor/lib/libmm-abl.so

And then there's that camera so file being renamed, which shouldnt happen.

Anyway, libtime_genoff.so we need for sure, that other one I'm not certain, it might be cam related or they might not be (judging by the function names it seems not). But it would explain why after using ano dev's blobs, cam worked ...
[Galaxy Note 4 General] gekkehenkie11:
And I also finished analysing 'ano dev's changes to other files, there are actually only a few:

changed in trlte-common:

*mixerpath, this one of course is the most important, he fixed call audio by correcting this (big thanks for that !!)

* An overlay: Should "4G" be shown instead of "LTE" when the network is NETWORK_TYPE_LTE? --> <bool name="config_show4GForLTE">true</bool>

(self explantory, I dont care too much about this, but we could use this)

* Other overlay, he disabled VoLTE: <!-- Flag specifying whether VoLTE & VT is available on device -->

<bool name="config_device_volte_vt_available">false</bool>

I'm not sure about this one !?! Why would we want to disable Voice over LTE ? I don't think we should do that. Or is this not available in 910F (countries) anyway ?

changed in trltexx:

* in system.prop he disabled strict mode. I don't think we should disable strict mode. Strict mode should be available to developers.

* in init_trlte.c:

He changed 910T into 910F (I dont care myself but some people here complain so let's change that too)

He commented out:

// property_set("telephony.lteOnGsmDevice", "1");

// property_set("ro.telephony.default_network", "9");

That last change I disagree with: on stock it also defaults to 9 and when it does not, I run into problems. What that other property does, I'm not sure but I don't think we should comment it out.

Anyway, mixerpaths was obviously the most important. About what exactly made cam function: it might be that missing lib or it might be that renaming of camera vendor file (I think that's it).

And agree, none of this could cause the issue's we saw with his firmware. Hearing that he used 910T kernel explains it !
[Galaxy Note 4 General] Preaper:
Nice writeup. Made me tune some things in my config. Though,

official-rom/system# grep default build.prop
#ro.telephony.default_network=9

ro.telephony.default_network is not set to 9 on stock, since it is commented out.