yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 Original Android Development] Mussels84:
Ok so i had a thought as to the black screen 'freeze' and the screeching audio problem - the one thing different users flash differently, and something i have different to my partners phone... Gapps.

To anyone else who has had either of those problems, what Gapps did you use?
[Galaxy Note 4 Original Android Development] agsola:
Alarm tone changed

Today my alarm tone was changed to default.

Did any of you have this problem?
[Galaxy Note 4 Original Android Development] Jenanga:
Gapps

I've used the whole time tk gapps. Now I have installed banks dynamic gapps and now many problems with Google play service I think I need a full wipe knows someone good gapps or recommend gapps to use
[Galaxy Note 4 Original Android Development] Mussels84:
i'm using TK Gapps, and only suffering the occasional 'blackscreen lockup' - after seeing it today and seeing changes in the app store, i started thinking it might be when Gapps updates itself in the background.
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Yes, sorry people. Yesterday I've gotten some horrible personal news and my mind doesnt feel like coding for now. I'll be back though but I need a few days off for sure. Thanks everybody for your support.
[Galaxy Note 4 Original Android Development] agsola:
Of course man, personal life comes first.

I hope everything improves.
[Galaxy Note 4 Original Android Development] speedyjay:
Do what you have to do bud :) 99% of us understand that devs have have a personal life away from developing too :) no rush my friend.
[Galaxy Note 4 Original Android Development] Xokoz:
Okay bro, take your time. We understand that.
[Galaxy Note 4 Original Android Development] fattire:
To make the build finish....

So the kernel doesn't break the build :) One new thing you'll need to change though, gekke, in addition to the other stuff in device/samsung/trlte-common:

diff --git a/mkbootimg.mk b/mkbootimg.mk

index 1fe0e3e..978a4d5 100755

--- a/mkbootimg.mk

+++ b/mkbootimg.mk

@@ -45,7 +45,5 @@ $(INSTALLED_BOOTIMAGE_TARGET): $(MKBOOTIMG) $(INTERNAL_BOOTIMAGE_FILES) $(INSTAL

$(INSTALLED_RECOVERYIMAGE_TARGET): $(MKBOOTIMG) $(INSTALLED_DTIMAGE_TARGET) \

$(recovery_ramdisk) \

$(recovery_kernel)

- [MENTION=279333]ECHO[/MENTION] -e ${CL_CYN}"----- Making recovery image ------"${CL_RST}

+ $(call build-recoveryimage-target, $@)

$(hide) $(MKBOOTIMG) $(INTERNAL_RECOVERYIMAGE_ARGS) $(BOARD_MKBOOTIMG_ARGS) --dt $(INSTALLED_DTIMAGE_TARGET) --output $@

- $(hide) $(call assert-max-image-size,$@,$(BOARD_RECOVERYIMAGE_PARTITION_SIZE),raw)

- [MENTION=279333]ECHO[/MENTION] -e ${CL_CYN}"Made recovery image: $@"${CL_RST}

Actually probably don't need to get rid of those echo statements but anyway, that works fine. Otherwise the build will break like this:

error: could not load ramdisk '/source/out/target/product/trltexx/ramdisk-recovery.img'

device/samsung/trlte-common/mkbootimg.mk:48: recipe for target '/source/out/target/product/trltexx/recovery.img' failed

make: *** [/source/out/target/product/trltexx/recovery.img] Error 1

Instead you get:

Package Complete: /media/test/lollipop/out/target/product/trltexx/cm-13-20151021-UNOFFICIAL-trltexx.zip

:good:

ft
[Galaxy Note 4 Original Android Development] Ogy77:
[MENTION=3041959]fattire[/MENTION] Dude you are not from this planet,thank you for hard work.
[Galaxy Note 4 Original Android Development] SenatorDC:
general fyi: the 21 October nightly has sent my phone into a boot loop (think that is the right term.....cyanmod face sits there looking at me indefinitely)
[Galaxy Note 4 Original Android Development] n3d9ed189:
I was on 21st, now 22nd, both with no problems whatsoever regarding bootloops so something must have went wrong in your set up.
[Galaxy Note 4 Original Android Development] SenatorDC:
Yeah probably..just put it there as an FYI. Had to wipe data in addition to the cache (both cache).
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Hey guys, I'm back after a few days off.

Anyway I've been messing again with CM13, fattire's 5.1.1 kernel boots ! Most problems weren't solved right away though but at least I've now got Audio up. And now I'm working on RIL, I've already found what the problem is ...

*EDIT* BOOM and fixed, RIL is up :) But the to-do list is still quite long. NFC & GPS are up but buggy. Camera and Sensors still down. Video is garbled up. And probably more. So still quite some work, but we'll get there !
[Galaxy Note 4 Original Android Development] Mussels84:
damn, quick progress.
[Galaxy Note 4 Original Android Development] micky387:
Hello. Very nice.I will to help you (if i can) but i have always the same build issue.

many change from cm12-1 of my build but not a problem,always this

Do you have problem about this ?? i have missing someting ( rommservice??)

thanks man and fattire too ;)
[Galaxy Note 4 Original Android Development] Mussels84:
know that gekke is back: some earlier comments from you guys said you're using a kitkat based kernel and not a lollipop one. whats the reasoning behind that?
[Galaxy Note 4 Original Android Development] finallau:
Will the 5.1.1 kernel be ported into CM12.1 before CM13 too? :D
[Galaxy Note 4 Original Android Development] fattire:
kernels and stuff

Guys, we are using the lollipop kernel with a bunch of new shamu 6.0 cherry-picks and our original cm commits. It's here. Read back to my recent posts to check in on progress.

The updates are that Gekke is out of town, so I've been building trltexx for him w/new adreno + the new 5.1.1 kernel, and he's been testing, looking at logs, etc. We had to modify a library to get the RIL to work with a patch he found, though I don't think you can make phone calls yet. From what I remember, the

list of things working

so far looks something like this:

the screen works

bluetooth (sometimes)

audio (and audiofx)

wifi

mobile network

stuff not working yet

sensors

video (probably widevine needs updating)

phone calls

gps can't be turned off

selinux (built in but turned off)

nfc

camera

everything else

Hopefully we can knock some of these out soon... others will take longer. There is a lot to try still.

micky387, what exactly are you trying to do? There are a lot of changes that need to happen to the device tree if you're building cm-13.0-- I can maybe put a tree at github.com/fat-tire at some point soon once we get a few more things stable-er.
[Galaxy Note 4 Original Android Development] 4qman:
Do you expect to have divice encryption working?

Ive rooted the note 4 and running another tom but unable to enable encryption on the device, I was hoping CM would have this working.
[Galaxy Note 4 Original Android Development] micky387:
Thanks for your reply.

I try to build cm-13.0 for note edge (tbltexx -915F) but always same issue with external/ffmpeg and/or external/stagefright-plugins.

I try to change glib2 package and other but always this f... issue.

Same 12.1 build ok but no cm13

exemple of issue

Same files in cm12.1 are ok...
[Galaxy Note 4 Original Android Development] mefflecakes:
Something that I've noticed in recent builds is that when I'm listening to music (in my case using Google play music) and when I tap the power button to turn the screen off, the audio cuts out for half a second. Is this a known issue of am I doing something wrong?

Thanks again for the best rom ever <3
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Fattire and me succeeded today in bringing the sensors up and the camera. I also think I've solved the NFC issue: the CM people didnt include a hack that we made in CM12.1. I'm pretty confident it will work correctly once we merge that again. But cant test it, I'm not at home, so we gotta wait till fattire is back :)

Important issue's that still need fixing:

* Cant call (although RIL is up, I suspect it's an audio issue)

* Video doesnt work correctly, seems a decoder issue, might be a general CM issue.

* GPS seems to have some problems, havent looked into it yet

* Cant install gapps, this seems a general issue with CM

* probably more

Keep in mind that the CM people are working hard on the main code and that it's not finished neither (thats why we cant install gapps for example).

What does work:

* Audio

* Camera

* Bluetooth

* NFC (I think, need to test the patch)

* sdcard

* RIL (mobile internet ? Cant test it right now, not in my home country at the moment)

* WIFI

Anyway, good progress is being made, hoping we can have something release worthy before the end of the month.
[Galaxy Note 4 Original Android Development] fattire:
I'm sure winevine needs to be updated from adreno...

A heads up-- for clarity-- I moved some branches around in my kernel.

branch cm-13.0 is now the "new" 5.1.1 based kernel

The previous kitkat kernel is now at the branch called cm-13.0-oldkernel

Right now cm-13.0-test1 has identical contents to cm-13.0 but as soon as we start making changes to 13.0 they will diverge.. so just use 13.0 from now on I guess...

Maybe tomorrow sometime I'll post an updated 13.0 branch of the device tree as well as a roomservice.xml that should help. Keep in mind this may get a barely booting system, but you need to make other changes around the device to get most stuff working... but if it helps get people to contribute, that's great.

I should warn though that as soon as this stuff goes up, people are likely to build rickety not-very-stable builds. Some people will post these builds. You may try these builds. At that point, you may wish you hadn't. Also looking even furhter ahead there will probably be some half-baked "kangs" that appear in other threads... "Try my super sm00thR0M" which is usually a lightly modified version (themed, overclocked kernels, etc) of the stuff found here. Be aware that we're not supporting any of that crap (not that we promise to support any of THIS crap either).

Some of the new fixes are gonna be simple btw-- it's just old stuff from lollipop that haven't been added to CM yet... or tweaking/adding some blobs or whatnot. But other stuff may take much longer... contributions are welcome.

Anyhoo, like I say I'll try to get a device tree up (but NOT a build-- I don't want to deal with the backlash/support requests) fairly soon along with some basic instructions so people can try building. I don't know if gekke has anything he wants to add to that, caveatwise or whatever. He's been doing the actual booting, so he may have some hands-on suggestions/recommendations.

ft
[Galaxy Note 4 Original Android Development] isaacinsoll:
I've made Android and ios apps before but never been involved in this side of things. **** its interesting to see these updates just to get a better idea of whats involved in getting this up and running. Amazing work guys :)
[Galaxy Note 4 Original Android Development] agsola:
Does it use Camera V2?

Is it possible to test if GoogleCamera works? (maybe something related with Marshmallow fix it...)

I guess you are using the latest modem and bootloader.
[Galaxy Note 4 Original Android Development] gekkehenkie11:
V2 capability should be provided by the HAL. So we'll have to wait till samsung releases Android M .. In march ? Will take a while for sure.
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Oh, and this, my dear friends, is why you should think twice before upgrading to the Note 5 (which will never have CM/AOSP) ->

Note 5 recent tab scrolling: https://www.youtube.com/watch?v=33pqdsdEqqc&feature=youtu.be&t=31

Our beloved Note 4 Snapdragon with Android M recent tab scrolling: https://www.youtube.com/watch?v=hMFGahR-Nr8

Who cares about some theoretical benchmark number. It's all about user experience. And there our Note 4 running AOSP easily beats the Note 5 running Touchwiz ;)
[Galaxy Note 4 Original Android Development] mpcjanssen:
It's such a shame there is no proper other phone with stylus.

Samsungs hardware is very nice, but their os sucks. Thankfully we have this rom to make the most of both.
[Galaxy Note 4 Original Android Development] drmoeed:
This is exactly why I downgraded from Note 5 to Note 4 ...

Because of flawless work by CM community ...

Loved it ...

Thanks ...
[Galaxy Note 4 Original Android Development] Narekrocks:
Really is a shame that Samsung is SOOO bad at software. Like it tooke them 4 months to add the recents menu animation. I am really hoping CM13 doesn't have the 4g issue so I can finally use it as a faily driver.
[Galaxy Note 4 Original Android Development] soielbueno:
This is great haceis a great job when the download will be available even if failures ? I am ready to install ...

Enviado desde mi SM-N910F mediante Tapatalk
[Galaxy Note 4 Original Android Development] fattire:
How to build CM-13.0 guide for note 4 on the CyanogenMod wiki (WIP)

Okay guys-- by your request, I spent the day doing some stuff to try to bring everyone who is interested in joining us in building cm-13.0 for the Note 4 up to speed. What I did:

Created two new repos-- android_device_samsung_trltexx and android_device_samsung_trlte-common, both of which have a cm-13.0 branch and contain all my cm-13.0 related changes which you can see in the history for each.

Along with the previously-mentioned trlte kernel, you now have the basics. So...

I wrote up a how-to build cm-13.0 for trlte/Note 4 guide (WIP) on the CyanogenMod wiki. It includes a roomservice.xml you can use, as well as detailed step-by-step instructions for some modifications you need to make to the source to get the build to finish with maximum functionality.

I used the wiki because it's a place people can use to (1) learn more about building via the Learning Center (whoever wrote that stuff is a freaking genius :good: and (2) make their own changes to the instructions with more tips/advice/corrections, so that (3) the instructions will be as clear and as usable as possible for people to go off of.

With the changes and repositories described in the doc, I was able to make a clobber build resulting in this:

Package Complete: /android/system/out/target/product/trltexx/cm-13-20151025-UNOFFICIAL-trltexx.zip

#### make completed successfully (01:40:05 (hh:mm:ss)) ####

It should be bootable, though gekke will let me know very soon. Update: Gekke let me know. It boots, but due to a system-wide issue on the current CM source, you need to manually start the sensor service with:

$ adb shell sensorservice

To do this, in recovery you'll need to first enable adb by editing the file /system/build.prop while in recovery. You just add these lines:

ro.adb.secure=0

ro.secure=0

That's it! Find us on IRC. And one last caveat:

If people are able to get this booting-- again I stress, please don't spam up the various threads with "OMG TRY MY K-K00L RADZ BUILD!!! (some things don't work)!!!!4!!!!" The point of this is not to kick off a bunch of broken spinoffs right now, but to get a base CM that works 100%. Also, don't ASK for a build here. Don't complain about builds not working.

We know they're not working

. There's lots to do still. But if you wanted to learn, we're all for that, and if you want to kick back some fixes, even better.

If you ignore the above advice, you WILL be mocked and ridiculed and your selfish, selfish name will be warbled by the bards generations from today as a legendary fool and scoundrel.

Enjoy, and please change the wiki!

ft
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Good job fattire ! Hopefully some people will join, cause there's still a lot of work to do ...
[Galaxy Note 4 Original Android Development] Mussels84:
i'll just wait til you guys recommend a test build, and then have fun :D

no skills at fixing bugs, but i'm plenty good at finding them.
[Galaxy Note 4 Original Android Development] fattire:
Oh ye of little faith in yourself :P ... True, it is kind of early at this point to be messing with it, but we want to be transparent and open in the development process as much as possible, so that's why it's all opened up and instructions are provided if you happen to want to try it, and I know based on some comments above that other people are definitely trying...

Stay tuned!
[Galaxy Note 4 Original Android Development] Mussels84:
hah, i've got complete faith that within a month you guys will have a CM13 as my primary daily ROM.

i just have a kid and a job, so unfortunately i dont have the neccesary spare time to be very helpful in the alpha stages.
[Galaxy Note 4 Original Android Development] jasopan:
Hey guys, how do I flash this? I've been flashing Samsung stock ROMS for a while but that was easy as I was using ODIN. Can I simply download the room and use Recovery to wipe + install CM12.1? What are the .img recovery files for?
[Galaxy Note 4 Original Android Development] Mussels84:
just flash the recommended recovery via ODIN, then flash the ZIP files for the rom and Gapps of your choice from the phone, in your custom recovery.

its far simpler than touchwiz roms, no need to worry about modems, bootloaders and such.
[Galaxy Note 4 Original Android Development] jasopan:
Fantastic. So flash recovery via Odin, put ROM and gapps (where can i find the appropriate one?) on sdcard and flash via recovery. What is the recovery for? Some sort of fail safe? Finally, how can I root the device afterwards? I had root then after updating it disappeared.

Thank you!
[Galaxy Note 4 Original Android Development] fattire:
On my phone but visit wiki.CyanogenMod.org and go to devices and you'll find install instructions and info...
[Galaxy Note 4 Original Android Development] cloak:
Is it possible to merge or install this new true 5.11 kernel, mentioned in #4645 by Fattire, in the CM 12.1 build?
[Galaxy Note 4 Original Android Development] Mussels84:
sorry was AFK for a while.

recovery is used to flash non-samsung files to the phone, basically. It definitely fills the role of a failsafe since custom recovery can let you backup your phone completely to internal or external SD card, as well as flashing zip files (For custom roms, gapps, Xposed and other mods)

you can use any Gapps you want, the one recommended in the OP is going to be commonly used here so its a safe choice. just make sure its for 5.1.1.

Rom is pre-rooted, you turn it on in developer settings.
[Galaxy Note 4 Original Android Development] StuttgartKiwi:
Hi [MENTION=3296134]gekkehenkie11[/MENTION], just curious, why do you say that the Note 5 will never have CM? Is there a particular reason that the CM team will not ever support it in the future?
[Galaxy Note 4 Original Android Development] Mussels84:
exynos chipset only, no qualcomm. thats been a bad sign in the past for CM.

edit: gekkenhekekekeke (my god i cant spell that name) below filled in the details, looks like exynos dont want to play nice.
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Exynos is not releasing the device code anymore. For the Note 4, people could use a (very) similar chipset code. But for the Note 5 or the S6 that doesnt exist. That's why there's still no AOSP for the S6. And never will.

Instead of the Note 5, I'd recommend getting a Nexus 6p. Or wait till the 820 is out, that's my plan anyway :)
[Galaxy Note 4 Original Android Development] micky387:
[MENTION=3296134]gekkehenkie11[/MENTION] and [MENTION=3041959]fattire[/MENTION]

Thanks for your work but i have always the same issue with my build as i say.

I follow step by step the "HOW TO" posted by fattire but build failed. Here My pastebin log error

i have past only what you need .

Can you look it and say me what is the problem ??

Thanks again
[Galaxy Note 4 Original Android Development] fattire:
Can you tell me a little more about your build system? Linux? Evertyhing in the bottom part is a warning, so I'll ignore it for now.. the big broken part is in external/stagefright-plugins/utils/codec_utils.cpp

Just to make sure we're working from the same thing, if you go into external/stagefright-plugins and type git log --oneline do you see these as the last few?

ef310a5 stagefright-plugins: Correct mime type

dc2a013 ffmpeg-extractor: Fix deadlock when stopping the reader thread

b384c5f stagefright-plugins: Restructure the code

68d9c45 stagefright-plugins: Remove Vorbis/MP3/H263/H264/HEVC

ce6fc45 stagefright-plugins: Fix adaptive buffer and crop handling

a82d5bd stagefright-plugins: Add special handling of DivX files

and in external/ffmpeg you have:

f032927 avutil: Fix a warning when building with clang

b6817ad ffmpeg: Update configurations for FFMPEG 2.8

24c1325 Update gen-android-configs for new GCC versions

c4f5a10 ffmpeg: Set cpu arch for silvermont config

5e0ebd7 ffmpeg: Readd missing X86 fixups

as the last few?

Just in case, try a repo sync --force-sync just to make sure you have the latest of all the repositories.

ft
[Galaxy Note 4 Original Android Development] fattire:
Update: The symbols you are looking for were apparently defined here in frameworks/av/include/media/stagefright/MetaData.h in this this "Marshmallow for Samsung Galaxy S4 Intl" repository.. but I don't see the same thing in cm's version, and nothing breaks for me. However, those few lines come from this commit which is a CM patch, so now I'm not 100% sure. but apply this same commit and see if it fixes it.

In fact, holy ****.. what is that account all about?! It looks like it's two italians who are doing the Samsung S4 (jflte), and who knows, maybe there's some good stuff to be learned from them...? I see they applied similar kernel patches- not sure which kernel they are using tho. Looks like theirs is a MSM8960 and ours is APQ8084... but anyway. It would definitely be worth comparing their device tree (gekke?!) to see what they've done to see if we missed anything.
[Galaxy Note 4 Original Android Development] micky387:
Ok i try to build with BBQlinux 64bits and now in ubuntu ( HOST_OS_EXTRA=Linux-3.19.0-31-generic-x86_64-with-Ubuntu-14.04-trusty)

All package are updated.

Repo sync are ok for me and i have you commit what you say with git log --oneline

thanks i will try ;)
[Galaxy Note 4 Original Android Development] jizang:
Guys one question right now I'm on miui rom but think about going back to tw or stock Android, can someone post there experience how is the latest build compared to tw in battery life, heat and camera? I know that gekkehenkie11 was working on a patch for camera quality is it on par with tw?
[Galaxy Note 4 Original Android Development] Mussels84:
If it wasnt better than TW, we all wouldn't be here. the camera patch was just for low light conditions, as is included in the stock camera app.
[Galaxy Note 4 Original Android Development] jizang:
Some questions I flashed this rom and wanted to ask is there a way to deactivate fast charging, and to fix the led it already goes by 90 percent to green as in fully charged when its plugged and lastly does exposed and 3minitbattery work ?
[Galaxy Note 4 Original Android Development] domsch1988:
Since some people with serious knowledge in Building, Kernels and Development in General seem to meet here, i have a "fun" question for you:

Would it theoretically be possible to get "older" Android Versions to boot with the Kernels from newer Versions? So could one get a Android 2.x up and running with a 4.x or 5.x kernel? I know that this might be really far off, but i'd really like to try and get a Android 2.x up and running on N4. Not for any specific reason, mainly for curiousness and some throwback retro flash i had recently when getting my G1 out for fun... ;)
[Galaxy Note 4 Original Android Development] gekkehenkie11:
Seems like a lot of work. Why not put your time to better use and help us get CM13 up :)

BTW, mobile internet works !
[Galaxy Note 4 Original Android Development] soielbueno:
That's great , I'm very nervous and excited about teneer CM13 in my note 4 .. If you need a tester rom I'm here thanks

Enviado desde mi SM-N910F mediante Tapatalk
[Galaxy Note 4 Original Android Development] ChemoNL:
Awesome nieuws.

If you need a tester, my note 4 is volunteering
[Galaxy Note 4 Original Android Development] Mussels84:
once you've got wifi and mobile data working, you've got most peoples basic requirements XD