[ROM][P605][4.4.4] CyanogenMod 11.0 - Note 10.1 (2014) LTE (27.10.2014)

[INeFFeCTiVE]

What will it take to port to the p600

I have been lurking in this thread for about a month and no one has taken on the task of creating a release for the p600. What exactly do i need to do to get this working on the p600? Is it as simple as removing LTE support, or am I looking at doing a full recompile? If someone with some know how can pm me some instructions, I would be up to the challenge.

 

[INeFFeCTiVE]

I love bringing a thread to a screeching halt with a simple question! :laugh:

 

[StNickZA]

Your question has been addressed in this thread many, MANY times. The P600 is based on a completely different SoC platform and there is very little work here that can translate across. There are no "simple instructions" that anyone can send you to get it to work.

 

[C2Q]

Your question has been addressed in this thread many, MANY times. The P600 is based on a completely different SoC platform and there is very little work here that can translate across. There are no "simple instructions" that anyone can send you to get it to work.

I have been lurking in this thread for about a month and no one has taken on the task of creating a release for the p600. What exactly do i need to do to get this working on the p600? Is it as simple as removing LTE support, or am I looking at doing a full recompile? If someone with some know how can pm me some instructions, I would be up to the challenge.

I posted this over in another thread, but there are already CM11 builds out for other Samsung tablets that came out after the p600 that also use Exynos and have pretty much the same internals (minus the Pen and RAM). For example the TabPro/Tab S have builds for their Exynos versions:

There's a working CM11 port on the tab pro 10.1/12.1 models
https://www.youtube.com/watch?v=Bo1vossH1FM

http://forum.xda-developers.com/gal...pment/cm-11-port-galaxy-tab-pro-10-1-t2850042
@INeFFeCTiVE - I'm not a dev, but if you want to give CM11 a shot on p600, maybe look at porting these over? Might be starting point.

 

[INeFFeCTiVE]

I posted this over in another thread, but there are already CM11 builds out for other Samsung tablets that came out after the p600 that also use Exynos and have pretty much the same internals (minus the Pen and RAM). For example the TabPro/Tab S have builds for their Exynos versions:

There's a working CM11 port on the tab pro 10.1/12.1 models
https://www.youtube.com/watch?v=Bo1vossH1FM

http://forum.xda-developers.com/gal...pment/cm-11-port-galaxy-tab-pro-10-1-t2850042
@INeFFeCTiVE - I'm not a dev, but if you want to give CM11 a shot on p600, maybe look at porting these over? Might be starting point.

I am relatively inexperienced as well, but i have enough knowledge to be dangerous. If i get this ported over I may not have the time to support it. That is the biggest problem, so i can only guarantee a starting point, and can't even really commit to that. If i get something booting, I will post it, and hopefully the community can help out. I will start a new thread to make some grumpy ass happy when I get something.

 

[r4yN]

Exactly, samsung's in-house exynos 5420 is fundamentally different from qualcomm's snapdragon 800... to name just a few key differences:

-8 cores (4x ARM Cortex A15, 4x ARM Cortex A7) vs. 4 cores (4x Qualcomm Krait, a customized ARM Cortex A9/A15)
-ARM Mali T628MP6 GPU vs. Qualcomm Adreno 330 GPU
-? DSP vs. Hexagon DSP
-no modem vs. Qualcomm's own (Gobi?) 3G + LTE modem
-? dual-band ac wifi vs. qualcomm's own dual-band ac wifi

Samsung Exynos uses 3rd party product solutions & chips, whereas qualcomm likes to use its own custom solutions... weirdly enough, Qualcomm products are more developer-friendly (fully open source, fast updates, etc)


You can try porting it, but without any experience I'd say it's pretty much a waste of time (and there's the risk of bricking your device!)... if you choose to try it though, I recommend you check out a few of the following links (+ their source code / repositories):

CyanogenMod on the Exynos SM-T520: Link 1 & Link 2
CyanogenMod on the Exynos SM-T700: Link 1

And from what I've heard halaskz is reportedly working on porting CM to the Exynos Note 3, you can check out his github

They all have pretty similiar hardware (if not exactly the same)


So it's not impossible to bring CM to Exynos devices, but compared to Snapdragon-devices it requires a lot more work...


Edit: ouch, it took me 10 minutes to write this? 2 new posts that I missed? Oops

 

[Gandalf]

@INeFFeCTiVE download the kernel source and create the device trees. Pull the vendor files from the stock ROM and start trying to get it to build. Figure out which CAF tag was used for the samsung source and merge the samsung code into it, you're probably looking at upwards of roughly 90,000(maybe it was 900,000, I don't remember) diffs. If you get it to build then good job. Be careful because it most likely will fail horribly and could potentially damage your device if you mess something up. Device bring ups from scratch are quite difficult and will take time and a lot of trial and error. You probably want to be versed in C and be comfortable moving around the CodeAurora Linux kernel. My sources for the lt03lte kernel are on my github if you want to reference what I've been doing.

Not trying to be sarcastic but that's the process. Its quite daunting. Good luck.


Should have underruns fixed by the weekend. I overlooked a crucial part of the mdp setup in my haste before realizing Samsung either removed or never added several things to their custom dt. Will keep everyone updated.

@Schischu fudge factors and bus implementation need to be moved to the Samsung dt. Its not there so the device is falling back to (bad) bandwidth values causing (from what I can tell) the underruns which are displayed by the blue flashes. FYI.

 

[INeFFeCTiVE]

@INeFFeCTiVE download the kernel source and create the device trees. Pull the vendor files from the stock ROM and start trying to get it to build. Figure out which CAF tag was used for the samsung source and merge the samsung code into it, you're probably looking at upwards of roughly 90,000(maybe it was 900,000, I don't remember) diffs. If you get it to build then good job. Be careful because it most likely will fail horribly and could potentially damage your device if you mess something up. Device bring ups from scratch are quite difficult and will take time and a lot of trial and error. You probably want to be versed in C and be comfortable moving around the CodeAurora Linux kernel. My sources for the lt03lte kernel are on my github if you want to reference what I've been doing.

Not trying to be sarcastic but that's the process. Its quite daunting. Good luck.


Should have underruns fixed by the weekend. I overlooked a crucial part of the mdp setup in my haste before realizing Samsung either removed or never added several things to their custom dt. Will keep everyone updated.

@Schischu fudge factors and bus implementation need to be moved to the Samsung dt. Its not there so the device is falling back to (bad) bandwidth values causing (from what I can tell) the underruns which are displayed by the blue flashes. FYI.

Thanks I genuinely appreciate this.

 

[alvinasnow]

I am relatively inexperienced as well, but i have enough knowledge to be dangerous. If i get this ported over I may not have the time to support it. That is the biggest problem, so i can only guarantee a starting point, and can't even really commit to that. If i get something booting, I will post it, and hopefully the community can help out. I will start a new thread to make some grumpy ass happy when I get something.

Surely i'll be one of those grumpy a**es waiting for that

 

[mcfisch]

hey,

i think i found a "feature": long-pressing a key on the on-display keyboard in landscape mode shows the alternative characters e.g. a > äåã, which is fine. in portrait mode, however, the keyboard just goes dark and doesn't show anything. ..although, releasing the key does input a new character. could you please look into it, should you have the time? it's just a small thing, but it's also a nice feature for all the german speakers (like me) out there, with all their ä and ü and sauerkraut.

thanks a bundle!

I'm using the Google keyboard with the Material design and have no difficulties. Seems the issue appears only with the AOSP keyboard which I usually don't use.

 

[kcrudup]

@Schischu fudge factors and bus implementation need to be moved to the Samsung dt. Its not there so the device is falling back to (bad) bandwidth values causing (from what I can tell) the underruns which are displayed by the blue flashes. FYI.

I'll be looking forward to this, too- I've been building the nightlys (using Schischu's additional repos) and other than the occasional hard hang (which I think is coming from the modem, as it seems to happen a lot when on the train as I traverse thru cell sites at ~80MPH) the "blue flash" is really the only issue I've had lately.

ETA: if you've got patches, please PM me; Thanks

 

[bwilliamspc]

Verizon note 10.1 2014

Any way for bootloader unlock to put CM on here? 605v

 

[r4yN]

Thanks I genuinely appreciate this.

you might want to check out this thread !

Someone over there got CM to boot on the Exynos Note 3 (the "brother" of our P600... xluco's kernel is almost completely based on haslaskz's Exynos Note 3 Kernel)

He also provided a video proof: https://plus.google.com/u/0/+Nitish...6073852881701266370&oid=109020499010364356572

 

[calebcabob]

I have the wifi only version...p600. What would happen if i tried flashing this? Hehe

 

[sgs9]

Congratulation for your new Paperweight

 

[Schischu]

Thx to jakew02 the blue flickering is gone in the latest nightly.

 

[StNickZA]

Thx to jakew02 the blue flickering is gone in the latest nightly.

That is awesome news! Many thanks to you and jakew02!

 

[kuoyu]

Thx to jakew02 the blue flickering is gone in the latest nightly.

Thank you so much for the problems fixed. The rom is perfect now, and the ART mode is running flawlessly.

 

[Edoardo001]

The lag in the first 2 minut use is still here?

Sent from my LG-D802 using XDA Free mobile app

 

[sgs9]

no

---------- Post added at 01:09 PM ---------- Previous post was at 01:07 PM ----------

android.process.media work here on sd and extsd 30 sec.
test self on your device.