yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
Haven't forgotten about this. Been extremely busy with finals but the semester just ended. Going to start working on android-5.0 branch and see what happens
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
Successfully built android-5.0 branch but I have not had an opportunity to flash it yet. I will test it out tonight after work.
[Galaxy Note 10.1 (2014 Edition) Original Android D] valexi:
YES! Good luck. I've been waiting for CM-12 for this device. Stock Samsung is killing me (with only 16gb of internal space!).

Maybe you can ask from Schischu if you encounter any problems that he has already fixed:

http://xdaforums.com/galaxy-note-10-2014/development/rom-aosp-lollipop-note-10-1-2014-lte-t2941699
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
I have already been in contact with him. I maintain this device officially for CyanogenMod. I will not be making an XDA thread for CM because:

There's already one.

I don't feel like managing yet another thread here. I have too many as it it for now.

I'm currently working on finishing merging the Samsung source into the CAF kernel. Ive only done mdss so far and it just isn't working on android-5.0 for omni or cm. I'm not sure if its the kernel or the device configurations, but I will be spending the next few days making sure that the kernel is properly merged.

My progress on the kernel can be tracked here: https://github.com/jakew02/android_kernel_samsung_lt03lte

It will probably take me a few days as there are an obscene amount of changes that Samsung made and I need to compare each changed file individually to ensure a clean merge.

I'm not releasing anything until it is at least stable enough to where all of the main features work enough to be a daily. I hate it when broken stuff is released.

actually, decided to do one final kitkat release, just for the hell of it.

I am nearly done re-merging the Samsung source into the CAF kernel for lollipop, so I should (assuming everything works as expected) have lollipop builds soon..
[Galaxy Note 10.1 (2014 Edition) Original Android D] itsita:
Sounds awesome...!

Will your final kitkat release be cm11 or omni?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
Omni , going away for a few days will do it when I get home
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
Good news.

Finally found time to work on the kernel merge.

This will be the cleanest Samsung merge into Caf of all history. Standby for test builds on LP once I confirm it's at least booting and safely functioning.
[Galaxy Note 10.1 (2014 Edition) Original Android D] itsita:
CAF + P605 = Profit :)

Sent from my Nexus 5
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
also, if anyone is interested, my progress can be followed here, at my personal github:

https://github.com/jakew02/android_kernel_samsung_lt03lte/tree/fresh

i haven't pushed everything i have locally yet, but this has mostly everything except media,net, and video drivers, as well as the entire arch/ directory.

i'm hoping to be finished by the end of the weekend.
[Galaxy Note 10.1 (2014 Edition) Original Android D] jittusm:
Please make one for 601 also..
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
as stated in the OP, this will ONLY work for the QUALCOMM (p605) variants of the note 10 (2014) that are listed there. I WILL NOT be doing ANY work for the exynos variant (i believe there is already support for that anyway) because 1) i don't own that device 2) this was such a PITA i never want to do another kernel bringup again :confused:
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
I need testers for all p605 variants please
[Galaxy Note 10.1 (2014 Edition) Original Android D] itsita:
I wish i could! It's exams time here in my uni. I'll be glad to test in a month or so, if still needed.

Sent from my Nexus 5
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
Kernel is finished. I need to fix some minor merge derps now.

Important thing is that the extraordinarily humongous amount of work is done, just minor things now.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ranger:
I have a stock P605 / Ireland. I'll test if...

The EFS isn't touched [can't risk my IMEI... again]

It's Lollipop not KitKat.
[Galaxy Note 10.1 (2014 Edition) Original Android D] itsita:
In any case back the rom first using TWRP. You can also back up the efs partition separately.

Sent from my Nexus 5
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
Refer to this list to see if you are able to flash this:

Model listed in OP

Using latest version of TWRP

Are able to flash custom ROMs (not restricted by Knox or bootloader)

On that note, I would highly recommend that users do NOT accept any OTA updates, since this is a Samsung device and they are absolutely notorious for locking down bootloaders.
[Galaxy Note 10.1 (2014 Edition) Original Android D] md1008:
I have p607t but essentially 607t and 605 are same. I can test as well
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
Yea, that's what I have :highfive:

Also, making killer progress on working out the merge derp errors. Hopefully I'll have something for you guys by the end of the weekend!

edit: if you want a good laugh at my expense, and don't mind some bad language, track my commit history on my github for this kernel, branch: fresh :D
[Galaxy Note 10.1 (2014 Edition) Original Android D] ranger:
With respect, that's not what I said. I don't want my EFS touched, at all. Regardless of backing up and restoring

I'm good to go. I have TWRP installed with Stock ROM ready.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
sounds good. i'll let you guys know when i have something (very, very soon)

also, EFS will not be touched as it is not in the updater-script at all :good:

however, i would *highly* recommend backing it up w/ TWRP and moving it somewhere safe (like Google Drive or somewhere you know it won't be inadvertently deleted)

Outstanding news: I just woke up to a completed boot.img. So the kernel is compiling properly now following my massing merging of Samsung source into the CAF kernel :good:

Now, I think I am going to drop some android-4.4 builds initially just to test the initial stability of the kernel itself, since the HALs are very stable on omni's android-4.4 branch.

Update: had a freak incident and somehow soft bricked my tablet. Im not sure how it happened but it was with flashing twrp 2.3.6.0 via flashify and now will bootloop saying recovery is booting with some nasty graphical glitching before rebooting and doing the same thing again. Luckily download mode is still accessible so I just need to Odin back to stock and start fresh. Conveniently thus occurred right before I flashed my omnirom android-4.4 build for testing with the new legitimately merged kernel. I built android-4.4 because the kernel source was closest to kk_3.5 in CAF. Once I confirm it boots and functions I will merge in the LP caf tag we are using and will build android-5.0 branch.

Main point to get from this is that the kernel is completed and compiles a full build successfully. Testing actual functionality has yet to be done. Once I can verify it is safe to run, I will post test builds from android-4.4 for users to run it through the gauntlet while I work on merging in the LP caf tag, which shouldn't take more than an hour.

We're almost there folks :D

update: successfully restored.

omnirom android-5.0 build completed. entering test phase :good:
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
Booting :good:

Update: I'm re-merging the lollipop CAF tag into the kernel, I did it sloppily the first time. Will most likely finish it tomorrow, depending on how much studying I get done for my exam on Monday morning. Once that is compete, the kernel will be done, finally and properly, which should hopefully fix audio as well.

I would recommend other ROM developers who are using CAF in their ROMs to consider rebasing to my kernel. I will be pushing the changes to CM github as well for cm-12.0.

I just need to fix the modem so that cellular service is working again, then we should be seeing some test builds.

Priority list:

Modem

Audio

Video playback

Anything else

Status Update:

I am re-doing all of the blobs using the stock T-Mobile P607TUVUANDA firmwares.

This should hopefully clear up the missing camera issue, as well as possibly correct the audio malfunctrion as well. Sorry it's taking so long, this is quite the daunting task I took up -_-
[Galaxy Note 10.1 (2014 Edition) Original Android D] davitox87:
Is this project dead/abandoned? Haven't heard anything in a few weeks.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
Literally one post above yours ... Come on now

But to answer your question, no, it is not.

Right now I am working on putting out a 100% stable android-4.4 build for use while I work out the bugs with lollipop. I removed the old builds because:

they were using my old, messy, crappy kernel

they had some bugs

The 4.4 build i put up will be completely stable, I'm just trying to work out a stupid issue I had resolved before, but I lost my commit history -_- so I have to basically figure out what I did all over again.
[Galaxy Note 10.1 (2014 Edition) Original Android D] davitox87:
My apologies, I saw that post on the 6th,but i didn't see the part that said status update... If it wasn't an edit then I'm blind..
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
no worries :good:

here's a fully stable 4.4 build for everyone to hold-over until 5.0 is usable:

https://www.androidfilehost.com/?fid=95916177934532242

^ this is in OP as well

Actually, I need to remove audio offloading because DSP manager is force closing.

Audio still works, but there's just an annoying popup about DSP manager force closing , but it doesn't actually impede the listening of music. So pretty much just ignore that FC for now
[Galaxy Note 10.1 (2014 Edition) Original Android D] earthtk:
How are the fixes coming along? :)

Kinda excited

EDITED: Tried out the kitkat version. Awesome so far! Anyway is there any option to turn on the stylus cursor?

EDITED1: Found it :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
Good, I re-did the vendor files.

My time has been sparse lately due to mid-terms, and now upcoming finals (my university is on a weird 10-week quarter system) but my first priority right now is to fix audio.

I think a lot of the display drivers are fixed now, since I manually re-did the vendor files from the T-Mo 4.4.4 release (UANJ or something like that)

Apologies it's taking so long.

But wifi works :p

Also, I'm breaking the builds down to variant builds, so i'll need input for every variant besides the Tmo one, since that's the one I have (p605 only, p600 lt03wifi is actually supported by CM, so someone else can port it to omni quite easily, I'm not getting involved in haxxinos)
[Galaxy Note 10.1 (2014 Edition) Original Android D] earthtk:
Hey.. Thanks for the heads up! Hope you are ready for your finals. I'm using your 4.4.4 one. It is awesome! But there is a weird bug that makes the screen turn black randomly. Shall use it till lollipop is up and running! Just wondering will theme engine from cm12 be included?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
Cm theme engine will never be in omni. Also, layers probably won't be either now due to disagreement by the developers.
[Galaxy Note 10.1 (2014 Edition) Original Android D] earthtk:
Alright. I was just wondering :)..
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
OK, mobile data and camera are working. Just sound left (afaik) to fix for lollipop :good:

I re-merged the kernel (again) into CAF and I must say, it is significantly better. No more audible "whirring" noise when opening and closing apps

I have a research paper due tomorrow and a research presentation due Thursday, and finals next week, so I'll get as much as I can done this weekend
[Galaxy Note 10.1 (2014 Edition) Original Android D] earthtk:
Hope your presentation and paper went well :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
Yea, straight A's so far :good:

I have off classes all this week so I've been working on the kernel; I finally fixed the weird, audible "whirring" noise that comes from the speakers when opening/closing a display-intensive app or process :highfive:
[Galaxy Note 10.1 (2014 Edition) Original Android D] earthtk:
Good to hear that! :laugh: I still got my final year to go through with a report and a presentation too.. Haha..

That's nice, take your time! :)..
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
Of course, as soon as I'm about to test what I thought would be a release for 5.1, I soft bricked and have to reinstall windows to use Odin -_-
[Galaxy Note 10.1 (2014 Edition) Original Android D] windows8k:
Good rom

could not do normal boot..

but omnirom 5.1 build err faild

jakew02 github thanks open source
[Galaxy Note 10.1 (2014 Edition) Original Android D] windows8k:
LoLLIPOP building?? but upload?? wait.. thanks
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
I have building and working android-5.1 branch. Just need to fix camera before posting any public builds :good: finally had time and fixed audio. It will definitely be ready by time Omni starts android-5.1 nightlies
[Galaxy Note 10.1 (2014 Edition) Original Android D] valexi:
Great thing! I have been waiting for this for a long time! [emoji1]
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
I just need to fix ril and camera but otherwise everything else works.

It takes a while to boot on clean flash but I'll fix that later after I get tests up.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Zerreth:
Hi Gandalf, thx for the active work on this device. It's tough to find any developers anymore working on the P605. I'm trying to find a rom that works well and is stable for my parents to use. Other roms usually have broken stuff like the dialer app crashing or chromecast simply refusing to cast the display. I'm looking forward to the 5.1 release. Going to test the 20150324 build now.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
The 4.4 builds should be very much stable. The only issue is that DSP Manager crashes, but it can just be removed from /system/app as a workaround.

I will post a 5.1 build with broken camera and RIL if people are interested in playing around with it. Wifi and everything else works on it.. It's stable enough for me to take notes during class on and listen to music and etc.

I am considering removing the Dialer since it is not in the Stock firmwares (only Messenger is on my P607T T-Mobile variant). I personally have no use for it, but if people do indeed use the dialer to make phone calls on the tablet, I will leave it in. Let me know.
[Galaxy Note 10.1 (2014 Edition) Original Android D] itsita:
I'm following your progress on omnirom's gerrit and it's very, very impressive. Thank you! (BTW - with which app are you taking notes?)

regarding the Dialer - personally i think it's a nice option to have if it's only a matter of leaving it in. not everyone are using skype / viber etc.

But if it's a hassle so obviously it's not worth it.

Looking forward for nightlies!!
[Galaxy Note 10.1 (2014 Edition) Original Android D] Zerreth:
omni-4.4.4-20150220-lt03lte-HOMEMADE works nicely, chromecast screen mirroring works too which is superb. Dialer does crash when attempting to call someone but other than that it's great.

omni-4.4.4-20150324-lt03lte-HOMEMADE is stuck at the omni boot logo.

A working dialer would be nice as my parents use it more than their landline phone. However, it is not a dealbreaker. As long as SMS functionality still works they can get by with using skype.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
I'll be home from campus soon, I'll post a partially working 5.1.1 build for you guys to play with. It will have the following issues:

Completely broken camera

Absolutely broken RIL/Modem

DSPManager crashes,, but does not affect music playback (i'll fix this after the big ticket items)

Probably other things I haven't experienced yet

Also, cont-splash is mucked up, so it will take a little time to display the boot animation, but it IS booting.

I use Google Docs to take notes for classes that don't provide lecture notes/powerpoint slides. For those I use that OpenOffice or Polaris or whatever office app that allows me to write on the slides themselves and save the overlay.
[Galaxy Note 10.1 (2014 Edition) Original Android D] windows8k:
i am sorry korean model SM-P605L

rom install boot on download mode could not do normal boot..

selinux connection?? boot failed..

NJ1 samsung firmware boot on

SM-P605L kernel Not kernel??

my SM-P605L boot kenel kernel development Should I do?:crying:
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
My internet was wonky last night when I got home from campus, and I didn't have time to fix it before I went out. Here is an android-5.1.1 build to play with.

https://www.androidfilehost.com/?fid=23991606952595910

If you were using a stock-based ROM before you should be able to use odin to flash the stock kernel back and effectively recover your device.

I've managed to restore my device from some pretty nasty bricks, if you're able to get to download mode, you are fine.

So what I'm gathering is, when you flash in recovery and try to boot, it just goes straight to Download Mode?
[Galaxy Note 10.1 (2014 Edition) Original Android D] itsita:
Tested briefly :

very good!!

It takes a while to "settle in" - but after a minute or so the rom is blazing fast.

Home button wake isn't working yet, but i guess you know that.

Thanks!
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
yep, i just got the modem working as well, but it won't connect to data. have to iron out that and then the last major issue will be the broken camera.

edit: oh wait it just booted up and hopped right onto LTE so... RIL is working :good:

edit 2: DSPManager crash fixed.
[Galaxy Note 10.1 (2014 Edition) Original Android D] nickwarn:
Damn, you´re on fire. Been waiting for RIL fix, that was the big one for me. Dont care about camera, never take any photos with the tablet anyways. I understand some use it for skype and such, but hell.... RIL is fixed!!!!!

Thank you for your hard work

By the way, does Omni rom support RRO/Layers theming?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ChrisCh22:
The brightness slider doesn't work on the 0502 version. Also, in the about screen the baseband version is "unknown".

In case anyone needs the info, fermion's gapps work with this.

Additionally, I would suggest to remove the black cursor that appears when using the S-Pen, in order to see more clearly what you're writing/drawing.
[Galaxy Note 10.1 (2014 Edition) Original Android D] davidmueller13:
Yes,and adaptive brightness setting is missing.I used Tasker to deactivate it and then the brightness slider works.

Nice,that the ROM has init.d support and SE Linux is Permissive per default.

Is it possible to add "Expanded Desktop"?

It could work,but I think there are some problems.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
I'm not adding features, I'm just getting the device to work in a stable state for right now. I actually haven't heard any talk regarding expanded desktop, I can't give you a straight answer on that one right now.

I have a solution for the cursor currently under review. Also, touch will be disabled while using the S-Pen (while it is a certain distance from the screen, or touching the screen - not dependent on whether the S_Pen is inserted or not)

RIL is working but data is not connecting, I have another test I have not flashed personally yet that may fix this, I'll see after class.

Entropy512 is working on a new RRO/Layers comparable theming system, more can be found about it here: <insert link later when I have time to find it>

Thanks for the heads up on the brightness slider, I'll get that fixed. So from what I can tell right now:

Camera

RIL (I believe this is because the support for Unified Devices was reverted in android_build, possibly causing the signal to not be fully working, possibly due to missing device/carrier specific properties that would otherwise be applied as a UnifiedDevice during flashing)

Brightness Slider and Adaptive Brightness

Hardware Keys are messed up
[Galaxy Note 10.1 (2014 Edition) Original Android D] valexi:
As we all have to do full wipe, when you get this thing released, should you consider adding F2FS for default filesystem?

I've had good performance boosts with F2FS in Cyanogenmod.

http://en.wikipedia.org/wiki/F2FS
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
I'm not going to add f2fs because in general Omni does not want to support it in the system.

We discussed this regarding Nexus 6 and decided to not include it. If people want f2fs, they should use a custom kernel :good:

The other problem with f2fs is that not all ROMs support it, so while you can flash X and Y ROM while formatted to f2fs, you wouldn't be able to flash A or B ROM.. so in the end it just causes issues.

Also, to my knowledge, CyanogenMod does not have kernel support for f2fs? (The unofficial CM build here is using the kernel I merged)

Update:

I just need to fix sepolicy to get data to work i believe, there are modem/ril denials that once corrected should have ril fully working, ill post abother build then, probably today or tomorrow

I need users with the following to please post the following information from your stock-based ROMs build.prop or default.prop, where ever you can find it:

"ro.build.fingerprint"

"ro.build.description"

"ro.product.model"

"ro.product.device"

from these variants:

P605

P605M

P605S

P605V
[Galaxy Note 10.1 (2014 Edition) Original Android D] earthtk:
Is this information you need?

SM-P605 here

Fingerprint

samsung/lt03ltexx/lt03lte:4.4.2/KOT49H/P605XXUCNJ1:user/release-keys

Description

lt03ltexx-user 4.4.2 KOT49H P605XXUCNJ1 release-keys

Model

SM-p605

Product

Lt03lte
[Galaxy Note 10.1 (2014 Edition) Original Android D] Gandalf:
Update:

I will be ending development for this device effective immediately. I haven't had the time or desire to work on anything android related lately, and I'll be needing to put my focus on school rather than this stuff. I'm nearing completion of my bachelors of science in psychology and will begin applying to graduate school, so I will not have time to properly maintain this device anymore.

90% of the work is already done, and the trees will remain on github @ https://github.com/omnirom for anyone willing to carry on the work.

When a new maintainer takes the reigns, please contact me so I can reopen this thread and have it transferred to you. This will allow one thread to contain all of the discussion of Omni for this device rather than having several.

-- Gandalf
[Vibrant Q&A, Help & Troubleshooting] QA Bot:
Q&A for [ROM][UNOFFICIAL] CM 11.0/Android 4.4.4 Build date 09/28/2014

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [ROM][UNOFFICIAL] CM 11.0/Android 4.4.4 Build date 09/28/2014. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Vibrant Q&A, Help & Troubleshooting] theonewhoroots:
just flashed

I flashed this rom along with the latest minimal gapps i could find and... it runs amazingly!! :victory:
[Vibrant Q&A, Help & Troubleshooting] Babloo1989:
since this is cm11 should i install all cm7 ics passion cm10 to perfectly run cm11 on my phone????

i directly flashed it few days ago it didnt got installed perfectly had lots of errors n always used to struck n restart for every 10-15mins