[SM-P600][4.4.4]CyanogenMod 11 - Note 10.1 (2014) WiFi - Galaxy Note 10.1 (2014 Edition) Android Developmen

Here is my port of CM11 to SM-P600, a.k.a lt03wifi. Source was almost entirely derived from the official source for SM-T520 which has almost the exact same hardware.
What works:
screen
wifi
bluetooth
logcat
usb otg storage
sound
microphone
multitouch
auto brightness
external sdcard
gps
softkeys
softkey backlight
flashlight
accelerometer
gyroscope
magnetometer
light intensity sensor
pen (without fancy Samsung menus of course)
both cameras
What doesn't work:
nothing as far as tested
Issues:
performance cpu governor causes sleep of death
stock cm camera app issue (see post below)
Links and how to install
Download link
ODIN flashable recovery
You won't be able to install it via TWRP for SM-P600, it will be complaining about the device name not being lt03wifiue. This is because they are mixing it up with SM-P601, it should be fixed on their side. I haven't tried but it might be the case for other recoveries as well. If you receive this error, flash the above recovery with ODIN and install from there. As a side note, the above recovery has much less features compared to TWRP but it's much faster, so it's better for quick test iterations.
I would be really glad if you can install, test and see what issues you might get.
Sources:
For those interested, here is the device source: https://github.com/ayberkozgur/android_device_samsung_lt03wifi.
You'll need the modified exynos 5420 kernel source: https://github.com/ayberkozgur/android_kernel_samsung_exynos5420
XDA:DevDB Information
CyanogenMod 11 - Note 10.1 (2014) WiFi, ROM for the Samsung Galaxy Note 10.1 (2014 Edition)
Contributors
equilibriumtr
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2014-11-05
Last Updated 2014-11-05

---

Thanks so much! I really appreciate the work you devs do. I'll install it this weekend and play with it. Thanks again!

---

Camera issue
There is a weird camera issue that I can describe as follows:
cm stock Camera app hangs when launched; after this, if killed, it will crash at its next launch and Torch will start crashing as well. This seems normal as the flashlight is probably using the same driver as the camera.
Torch will work if Camera is not launched at all.
If the Google Camera app is downloaded, installed and launched, the stock Camera app will properly launch and work until the next reboot, even if the Google Camera app is closed.
At this point, within the stock Camera app, if the mode is set to Video instead of Picture (the default), the Camera app will launch successfully even after a reboot. After launched, it can go back into the Picture mode no problem. So in other words, launching the Camera app in the Picture mode will freeze the camera and the flashlight until reboot.
This is very weird and I couldn't pin it down. The dmesg dump of the stock Camera app: http://pastebin.com/xPDYRG4X
dmesg dump of the Android Camera app: http://pastebin.com/WaqxQA5E
As you see, they are nearly exactly the same.
It could be a permission issue, a driver issue, a kernel module that's loaded on-demand, I have no idea at this point. I need help. Do any of you guys have any insight as to why this might be the issue?
Update: I tried the first ~10 camera apps in the market and ALL of them work perfectly fine. I think CM camera app is to blame here. Is anyone aware of such a thing on other devices?

---

I love you, where is your donation button , Sir? I dont use the camera and i can stand the sleep of death(although i know it can be fixed) but you have done something really important, with cm on p600 it is much more possible to be supported as a legacy device on many roms instead of only waiting for samsung and roms based on samsung software. Omnirom, PARom, Aopk are just a compile away with something like p600 working. Congratulations, and i still want to see your donate button.

---

Thank you!
I replaced the camera app with Google Camera, in recovery, and it seems there are no more problems with it.
Is there any way to make the pen work?

---

Make sure you are using CAF-NEW for the audio,media, and display HALs. Also, make sure that you have the proper commits in the kernel to coincide with the caf-new hals.

---

Got the lt03wifiue instead of lt03wifi problem.
I cant flash the recovery that you compiled. It says that md5 does not match on odin 3.07. any suggestions?
installed PhilZ Touch, supposedly based on cwm and still got the lt03wifieu name problem.
Can i change lt03wifieu to lt03wifi flashing a samsung rom from sammobil?

---

Well, I did flash the recovery I uploaded with Odin 3.09 and I didn't try Odin 3.07 so there might be a problem there. I think the device name should be lt03wifixx in one place and lt03wifi in another. I'll check this out along with the HAL issue tomorrow.
Yes, I forgot to test the pen and it doesn't work at all. Adding it to the list.
Thank you for your kindness, but I don't think I really deserve a donation here, all I did was adjust the obvious parameters in a ready-made source

---

equilibriumtr said:
Well, I did flash the recovery I uploaded with Odin 3.09 and I didn't try Odin 3.07 so there might be a problem there. I think the device name should be lt03wifixx in one place and lt03wifi in another. I'll check this out along with the HAL issue tomorrow.
Click to expand...
Click to collapse
META-INF>com>google>android>updater-script
For its to work i deleted the first line that says:
assert(
getprop("ro.product.device") == "lt03wifi" ||
getprop("ro.build.product") == "lt03wifi" ||
abort("This package is for device: lt03wifi; this device is " + getprop("ro.product.device") + "."); );
Click to expand...
Click to collapse
After that and a data wipe on TWRP the installation went smooth. This will let you to flash the rom and also install cwm recovery that comes with CM roms so you can say bye to TWRP; from then, the "lt03wifieu" is not a problem for me on cwm as @equilibriumtr said. I can now flash the zip with the lines that didnt let me before.
I think we could recover the lost security from deleting that line by adding something like this:
assert(
getprop("ro.product.device") == "lt03wifi" ||
getprop("ro.build.product") == "lt03wifi" ||
getprop("ro.product.device") == "lt03wifiue" ||
getprop("ro.build.product") == "lt03wifiue" ||
abort("This package is for device: lt03wifi; this device is " + getprop("ro.product.device") + "."); );
Click to expand...
Click to collapse
Can someone please add the lines instead of deleting them first and try flashing? Since with CWM i dont get the "lt03wifi is not lt03wifiue" error so I dont know if my theory is correct.

---

Will be testing
Thank you for porting cyanogenmod to our tablet. I will be testing it and report anything that goes wrong.

---

Does ART work or Dalvik only? 'cause AFAIK you can't select ART in the official Samsung firmware...
Also the Exynos 3 cm port reportedly has got the S Pen working (without samsung's s pen functionalities of course), so you might want to take a look at their sources / repos?
PS: Keep up the good work, having a fully functional cm rom one day would be amazing :fingers-crossed:

---

r4yN said:
Does ART work or Dalvik only? 'cause AFAIK you can't select ART in the official Samsung firmware...
Also the Exynos 3 cm port reportedly has got the S Pen working (without samsung's s pen functionalities of course), so you might want to take a look at their sources / repos?
PS: Keep up the good work, having a fully functional cm rom one day would be amazing :fingers-crossed:
Click to expand...
Click to collapse
By the way, I always had a working pen in my Note II LTE, even back when only cm 10.2 was available. But I'll look at the pen functionality soon because we will be needing it ourselves.

---

I looked at the device name issue, rebuilt the source and I got exact same build.prop with the original Samsung ROM:
Code:
ro.product.name=lt03wifixx #This changed
ro.product.device=lt03wifi
ro.build.product=lt03wifi
It's basically TWRP's fault for mixing up SM-P601 (lt03wifiue) and SM-P600 (lt03wifi), it should be fixed on their side. I couldn't try philz touch because goo.im was down. For now, try to use my recovery.
I also tried flashing the recovery I provided with Odin 3.07, it works. Something might be wrong on your side.

---

jakew02 said:
Make sure you are using CAF-NEW for the audio,media, and display HALs. Also, make sure that you have the proper commits in the kernel to coincide with the caf-new hals.
Click to expand...
Click to collapse
I don't think Qualcomm hardware applies here, lt03wifi is Exynos-based.

---

Good to see that someone finally directed his attention to CM11 for our P600.
Waiting a long time for a working CM11.
Keep up the good work!!:good:

---

equilibriumtr said:
Well, I did flash the recovery I uploaded with Odin 3.09 and I didn't try Odin 3.07 so there might be a problem there. I think the device name should be lt03wifixx in one place and lt03wifi in another. I'll check this out along with the HAL issue tomorrow.
Yes, I forgot to test the pen and it doesn't work at all. Adding it to the list.
Thank you for your kindness, but I don't think I really deserve a donation here, all I did was adjust the obvious parameters in a ready-made source
Click to expand...
Click to collapse
If I'm not mistaken, the difference between Tab models and Note models is that the Tabs don't have an S-Pen. So it's not surprising the S-Pen doesn't work when using a Tab ROM.

---

Hi ...
equilibriumtr said:
I don't think Qualcomm hardware applies here, lt03wifi is Exynos-based.
Click to expand...
Click to collapse
Dear friend , is this ROM stable for Daily Use ? ( I were porting Ubuntu phone based on TW ROMs but as you made this ... it can have a better base ) ... also , do you know how is the RAM used in this ROM ? ( how much free ? )
With best Wishes
HItman1376​

---

hitman1376 said:
Dear friend , is this ROM stable for Daily Use ? ( I were porting Ubuntu phone based on TW ROMs but as you made this ... it can have a better base ... but , do you know how is the RAM used in this ROM ? ( how much free ? ))
With best Wishes
HItman1376​
Click to expand...
Click to collapse
Slow down there, mate - you can't expect a fully stable "Daily-use ready" Rom after just one day
This is still in early testing...and I doubt you can call it "stable" when there is a sleep of death problem

---

thanks ...
r4yN said:
Slow down there, mate - you can't expect a fully stable "Daily-use ready" Rom after just one day
This is still in early testing...and I doubt you can call it "stable" when there is a sleep of death problem
Click to expand...
Click to collapse
Thanks for the Fast response Dear friend ... Well, if the sleep of dead is all , you can get rid of it by increasing the Min CPU Freq using any CPU manager app ... can you tell me about the RAM ? ( we have RAM management problem in UP so we need some more free RAM comparing with TW ROMs ) ... Thanks in advance
With Best Wishes
Hitman1376​

---

First off thanks for the port. I find stock android roms the best to run Linux on so if you could release a separate kernel with Virtual Terminal enabled (VT_config) it would be great.
As expected the rom only has the barebones on it and seems far more lightweight than even the most debloated rom. Merely not running the Samsung frameworks does wonders me thinks...