yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
Thank you for your response. Do I need to worry about what boot loader I have? Is the same used for both Joshndroid and this one?
[Galaxy Note 10.1 (2014 Edition) Original Android D] r4yN:
Made a short recap of known bugs:

Some experience Wi-Fi problems (Check ccode & regrev)

The Microphone is broken (I personally never use it)

Zoom-In during Video Playback (YouTube, Netflix)

The SW / HW Buttons Switch is no longer there

No Lockscreen Rotation (defaults to 0°)

Other than that, I have to say, the latest build runs great (very fast & stable with the darkness CPU governor :good:)

By the way: Is there a reason why the CyanogenMod AudioFX App (Visual Equalizer) is missing?

I know there's a Speaker EQ in Deathly Adiutor, but having a visual representation, sliders & pre-made profiles is so much more appealing imho :angel:

If you were on Josh's CM before, chances are you are already running a KitKat bootloader (which is recommended), otherwise you would have experienced audio & S-Pen bugs.

But just in case: You can also download Kernel Adiutor (ROOT) [deathly adiutor does not have the "device" tab (yet?)] from the Play-Store & check your bootloader-version under the "Device" tab

(Mine says "P600XXUCNJ1" -> a quick google search shows that this is a KitKat firmware)
[Galaxy Note 10.1 (2014 Edition) Original Android D] HotShotAzn:
Anyone getting random reboots? This is from clean install, Open Gapps, Magisk, and phh Super SU.
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
But just in case: You can also download Kernel Adiutor (ROOT) [deathly adiutor does not have the "device" tab (yet?)] from the Play-Store & check your bootloader-version under the "Device" tab

(Mine says "P600XXUCNJ1" -> a quick google search shows that this is a KitKat firmware)[/QUOTE]

Mine says "P600UEUDOK1". Now what?

---------- Post added at 06:55 PM ---------- Previous post was at 06:42 PM ----------

I just did a search and found P600UEUCNK1

Baseband version: P600UEUCNK1

Kernel version: 3.4.39-1462259

Build number: KOT49H.P600UEUCNK1

AP: P600UEUCNK1

CSC: P600XARCNK1

CP: P600UEUCNK1	4.4.2	November 2014

This is KitKat Correct? Not sure why we have different bootloaders.
[Galaxy Note 10.1 (2014 Edition) Original Android D] muhgi:
I tried all the variations of US/5, US/6, ALL/0+US/5, ALL/0+US/6 and could never get wifi to work at the bed and breakfast we stayed at. Wifi Analyzer reported it as: 2462 MHz, CH. 11

WPA2-PSK-CCMP ESS. (It worked fine for iOS and a stock Android phone.)

This suggests a problem other than the 5ghz problem usually assumed.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hey muhgi,

Try reflash rom, gapps and SU2.78sr5 after full wipe.

There must be something going wrong on your side 'cause I know other US users without a single wifi issues like yours.

I'm quite sure there is no wifi issues in this rom.

And do not restore system settings via titanium backup.
[Galaxy Note 10.1 (2014 Edition) Original Android D] muhgi:
Thanks. The problems really depend on your router. My router at home, with the US/5 or 6 fix is fine. (It's a dual band router.) My brother's router hasn't been a problem either. Since getting that fixed, I've only seen the issue at the B&B. ETA: My point here being that from researching this, what I see is that most wifi issues are dependent on the router involved. If you don't have a particular router with particular settings, you won't see the problem. I've seen this even with factory Android.

I did a full wipe (I forget the term, but even the stuff that you usually only wipe when doing an upgrade that changes the partitions) and don't use any sort of backup/restore at all, beyond Google restoring my contacts.

Is the "SU" SuperUser? Why would I need that when su is built in to the ROM?

The first post says "ROM Firmware Required: KK bootloader". Is this the default bootloader? How would I check this or replace it? I don't have the tablet with me, but will TWRP tell me the bootloader version if I boot to recovery? (I wish there was more formal documentation for these projects. I'm a professional software developer and would love to contribute but I start trying to look at issues like this and... :eek::confused::p Even a lot of molecular biology, while weird, is at least documented.)

ETA: I'm using GApps nano with the one app for Google Play added so my Kemco RPGs play. :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] ffoo3d:
Still no widevine working on 20161201 build

Still no widevine working on 20161201 build,

it seems that also other official nightlies missed widevine (ex: 20161206 nigthly of cm14.1 victaria).
[Galaxy Note 10.1 (2014 Edition) Original Android D] Leoxur:
I think it's the First rows's kernel processo that cause drain
[Galaxy Note 10.1 (2014 Edition) Original Android D] r4yN:
P600UEUDOK1 is a Lollipop Firmware (Android 5.1.1), so you will likely end up having sound (crackeling) & S-Pen issues (weird that you didn't experience them on josh's CM13 builds? :confused:)

There is a guide on how to revert to Kitkat Bootloader, but it will completely wipe your internal storage, so back up all your files! (Guide originally posted by [MENTION=4630882]epithetic[/MENTION])

Try using ccode=GB & regrev=6 (or =5, I don't remember which one it was), and don't forget to reboot your device after changing the values ;)

And yes, as discussed earlier, it not only affects the 5GHz Wi-Fi, but also certain 2.4GHz channels (channels 11, 12 & 13 to be precise, since they are not being used in the US)

This ROM already has superuser built-in, so you don't need to flash SuperSU.

To check your current bootloader-version, download the Kernel Adiutor (ROOT) app from the play store, grant it superuser access (root required) & check what it says under "bootloader" (in the "Device"-Tab).

Oh and I posted a link to the kitkat bootloader restoration guide above (just in case you need it) ;)
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
[MENTION=4810273]ZakooZ[/MENTION] : I tested latest CM 7.1 build on latest LP Bootloader 5.1.1 and i can report, that the rom is booting, but sound crackeling issues are still there. Still not possible to use this rom with lp bootloader...
[Galaxy Note 10.1 (2014 Edition) Original Android D] muhgi:
Channel 11 is being used in the US. At least, that's what I was having problems with this last weekend. Neither my stock Android phone nor my wife's Android phone nor her iPad had any problems with the 2.4Ghz channel 11. According to the WLAN link in your URL above, North America does not use 2.4 GHz channels 12, 13, and 14.

Thanks for the other links too! ETA: Just noticed that link was to this thread. I tried searching this thread and either missed it or used the wrong keywords to search. :( I expect I have the correct boot loader, since I haven't seen any of the other issues indicated.
[Galaxy Note 10.1 (2014 Edition) Original Android D] r4yN:
You're absolutely right - it's channel 12, 13 & 14, my bad :silly:

Have you tried ccode=GB & regrev=6 'though? It might help ;)
[Galaxy Note 10.1 (2014 Edition) Original Android D] muhgi:
I'll have to wait until I encounter another problem router. My one at home works fine. My brothers has also been working fine. (Maybe I'll try forcing my one at home to channel 11 on 2.4...)
[Galaxy Note 10.1 (2014 Edition) Original Android D] pnuker:
It's really too bad the microphone is still non-functional, since I need to use it so often. Any progress on that front?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Maybe you could stop acting like you're entitled to anything from us and patiently wait for a fix, or help fix it.
[Galaxy Note 10.1 (2014 Edition) Original Android D] pnuker:
Here's what I said: "any progress on microphone functionality"

Here's the meaning you assigned to what I said: "I demand microphone functionality and I am entitled to it"

I will now proceed to scratch my head in confusion...
[Galaxy Note 10.1 (2014 Edition) Original Android D] Leoxur:
I'm still having this battery drain problem, it starts after a few hours that the tablet is on, and does not go into Deepsleep. I have reason to believe that this is not app-related problem. Both Wakelock detector & BBS give this as a wake locks kernel ... I was thinking about a possible "solution" with QuickBoot, drain could disappear as quickboot leaves alive only the most principal process, and also we should not wait too long to turn it on and turn it off
[Galaxy Note 10.1 (2014 Edition) Original Android D] Pact:
It's actually bad form on XDA to ask for progress of any kind - it'll be made when it's made. Furthermore this is a developmental, in-progress release, using it expecting everything to work for critical usage isn't a good decision.

Anyways, to those experiencing the video problem where it zooms to a quarter of the resolution, just switch to another app then switch back to the video app. It'll reset the resolution back to as expected, at the same time without cancelling the current progress. No need to close YouTube or restart the video.
[Galaxy Note 10.1 (2014 Edition) Original Android D] pnuker:
But...I'm not expecting everything to work. Not in the slightest. I'm baffled how my words are interpreted this way. I was just asking if there's any progress on the microphone. And if I'm to troubleshoot the microphone, how can I know where to start if it's bad form to ask what has been done so far or what the actual problem is with it?

Anyways, I've at least noticed that the microphone does function a little bit while I'm recording audio with the screen recorder. It's a bit faint, but it IS recording.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Then just ask how you can help with the fix, but don't ask for a progress report, it's very rude
[Galaxy Note 10.1 (2014 Edition) Original Android D] pnuker:
How do I go about helping with the fix if I'm unaware of what has been done so far or what the actual problem is? That's the root of my confusion ;)
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
We'll let you know if we need any help, we already have logs, just be patient
[Galaxy Note 10.1 (2014 Edition) Original Android D] pnuker:
There is approximately zero lack of patience on my side :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
If so why asking then, lol?!

https://youtu.be/JmvCpR45LKA

Do not take everything so seriously, you will quickly get used to the forms of treatment here.

If necessary, read the forum rules ...
[Galaxy Note 10.1 (2014 Edition) Original Android D] pnuker:
I asked because I was wondering what has been done so far, in order to properly troubleshoot for myself.

Also, take a look back at the person that replied to me to discover who was indeed taking things too seriously ;)
[Galaxy Note 10.1 (2014 Edition) Original Android D] pn1fon1:
Hi,

Does anyone know where to report a bug for deathly adiutor?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi pn1fon,

in the absence of an own DeathlyKernel thread I would post logs here with a detailed description of the issues so that it's easy to replicate it on other devices.

There are a few apps to create log-files like SysLog or CatLog and realy easy to use.

Try to keep the log as short as possible to make it more developer friendly(reboot, replicate issues, create log):good:
[Galaxy Note 10.1 (2014 Edition) Original Android D] marclais:
I tried this with watchespn. While it does recenter the video momentarily, it quickly reverts to only showing the upper left corner. Can anyone tell me if this is a CM 14 issue, or if it is specific to this device?
[Galaxy Note 10.1 (2014 Edition) Original Android D] tst1212:
Has any else received a "E: unknown command [log]" while installing the ROM?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Yepp,

ignore it or install latest TWRP from ShevT:

http://xdaforums.com/galaxy-note-10...-p601-cm13-unofficial-builds-note-10-t3272812
[Galaxy Note 10.1 (2014 Edition) Original Android D] Genebaby:
I thought I installed the latest TWRP, but I still got out the other day when I clean installed the new version.
[Galaxy Note 10.1 (2014 Edition) Original Android D] pn1fon1:
The problem is I am currently using cm13 with deathly kernel, not this ROM. Anyway it seems that widget does not work when trying to switch profiles. It works only from the app menu.

Thanks for the reply
[Galaxy Note 10.1 (2014 Edition) Original Android D] tst1212:
Me too, I have 3.0.2.4. Also getting a force close when setting up email to an e exchange server.
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Someone achieve to fix charging issues? I am charging in recovery mode but not the best.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
What's the charging issue? Slow charging has been fixed, what are your settings in deathly adiutor?
[Galaxy Note 10.1 (2014 Edition) Original Android D] muhgi:
I figured enotar meant the: unable to charge with the tablet off bug, which actually turns on the screen and drains the battery rather than charging. There are no known bugs listed in the first post, and no bugs entered into Git for the source code, which is one of the reasons people have to ask about the status of bugs in this thread, since we have no idea if the bug is really known or repeatable or whatever.

Enotar, I installed the 1201 ROM, did a clean install, and tried charging with the tablet off last night. It appears to have worked--I'll verify this tonight. I've seen a couple other reports of it working for others as well. (Deathly Adiutor is NOT needed for this.)
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Very slow charging not even complete after one night but my settings are different. let me try yours.

Thanks
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hmmhh..!

But widget works on latest CM14.1...

Remember, you have to press two times on the profile widget to get profiles successfully applied!
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi enotar!

You can go strait up to the limits without fear of damage. Battery's suck the power from the power supply, it will never take more as it is technically possible.

Just make sure that the charger does not overheat!

On screenie below are my settings ...

but charging current never goes up to more as 2100mA while display is off and 1800mA while it is on. Also with more higher settings!
[Galaxy Note 10.1 (2014 Edition) Original Android D] pn1fon1:
---------- Previous post was at 07:18 PM ----------[/SIZE]

[/COLOR]

I know

I press twice and says profile applied.

But really it doesn't. If i enter the main app the settings remain unchanged. If I go to the app profile tab I can activated it from there. From the widget I can not. I get a toast message that profile activated but does nothing. I use apex luncher and latest cm13 orionos.

Thanks for your reply.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Going above 2550 is where it starts to get dangerous/risky, I recommend you change your settings to always be at 2550 or before.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Yepp,

maybe risky for the charger but not for the battery. But thanks for the hint!

The internal circuit of the battery allows only 2-2,2A while display off, even if you set it at 2550mA or more(at least with the stock charger).

You can test this by rising the limits and see what's the maximum the battery will suck.(AccuBattery from digibites is a nice tool)

In charging mode the battery collects the energie from the charger, the charger does not push it into the battery (unless you have a fast charging technology like qualcomms "Quick Charge")

The current is also limited by the micro usb 2.0 connection.

BTW,

I've used/tested a 5v/3A power supply maybe a year ago or so, but charging speed was always the same.

Let me see where he was hiding, when I find him, I'll test him again with the new possibillities we have now.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Fenrig:
stuck on boot splash

Hi I fresh installed the 1201 rom on my sm-p600 and its stuck on the boot splash (the pulsating circle of the CM logo face) - I tried with twrp 2.8.7 and twrp 3.0.2 - Normally I should still be on kitkat bootloader (Started romming back when stock was kitkat). I never had these issues with temasek :/
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hmmhh, not much informations to get a conclusion!

Did you use f2fs filesystem with Temasek?

I ask, because this rom only works with ext4 system partition.

If you are still on ext4 (never changed) you can try to install latest TWRP from ShevT's CM13/RR thread and try start from scratch after reboot into the new recovery.

Wipe everything incl. internal storage and check md5checksums before to avoid bad zips.

Install rom and 7.1gapps pico/nano from sdcard.

Reboot and wait a few minutes, first boot can take a bit longer.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Fenrig:
oh yeah I did use f2fs, I had the understanding that the rom would do reformatting. Is there a guide for reverting :) sorry for the lack of information

---------- Post added at 04:15 PM ---------- Previous post was at 04:09 PM ----------

hahah found it already, doing it with the newest twrp/recovery though :D
[Galaxy Note 10.1 (2014 Edition) Original Android D] Leoxur:
[MENTION=6227169]mosimchah[/MENTION] have you thought about the possibility of adding the quick boot?
[Galaxy Note 10.1 (2014 Edition) Original Android D] marxses:
Thanks for the solid ROM, just a few bugs to mention

I get the same issue but with pretty much every app as far as I can tell.

Related log is spen-keypop.txt but to my admittedly untrained eye it doesn't show anything that helps. I attempted opening the keyboard around 14 times by trying to search in catlog while recording. Using finger it works fine.

Another issue which be can worked around (possibly already reported) but thought I'd mention is that the spen and fingers do different things on the "Recents" capacitive key. Have to change the button options to what the spen does regardless to have finger and spen register the same command.

Related log capkeys.txt.

Getting phenomenal battery life out of this ROM. I put a new battery in recently but can squeeze just over 9hrs of screen on time where I'd be lucky to reach five with TW.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
+1

for Spen not able to open keyboard.

---------- Post added at 08:42 ---------- Previous post was at 08:05 ----------

Lol,

was just good guessed! Happy it works now..
[Galaxy Note 10.1 (2014 Edition) Original Android D] Fenrig:
yeah apparently I gave just enough information to fix the problem. I'm really loving this rom!
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
I had this problem when I installed SU. Read about incompatibility with SU and TWRP. Did reinstall without SU and everything is working great.

---------- Post added at 11:04 AM ---------- Previous post was at 10:57 AM ----------

Everything is working great. Thanks for your help. Install went well with a couple of exceptions, could only get nano to work. Standard had error that Google play services had stopped. When I loaded SU it stopped booting, had to reinstall. Everything seems to be working better than new.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
You need latest SuperSU-v.2.78SR5.zip for current CM14.1 roms. Works fine!:good:

For full gapps have you tried gapps aroma? You can also try banks gapps package for 7.1
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
I used arm, 7.1, stock. Not sure why aroma would work better. I will try when next beta Rom comes out. Is SuperSU-v2.78-201609011115.zip the correct su version?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Here it is:

http://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip

Full open gapps packages have caused some issues in the past, don't ask me why.

Honestly no idea!

And remember, the search button is your friend and will help to find everything ever been published here on xda.
[Galaxy Note 10.1 (2014 Edition) Original Android D] r4yN:
Again, CyanogenMod has SuperUser-functionality built-in, so you don't need SuperSU & I strongly recommend sticking to the official su in order to avoid any problems ;)

IIRC most devices have size-limitations on their "system"-partition & with large ROMs, there's just not enough free space for the full GApps-Package (so use Nano or Pico)
[Galaxy Note 10.1 (2014 Edition) Original Android D] Drisanna:
I was having a problem with very choppy video and sound. I followed a suggestion to install AC3 Player, and it works like a charm. However, I've long been a fan of MX Player Pro. Does anybody know WHY it (and the other video players I've tried) behave so badly on the P600 with this ROM installed? It works just fine on my older N8013 with 7.1 installed. I guess I'm wondering if this is a fixable issue, and if so, does it need to be fixed by the wonderful developer of this ROM, or by the MX Player Pro folks? I really love everything else about this ROM. I was sold on Nougat after I installed it on my N8013, and love it just as much here.
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
Reading the thread I was under the impression that SU should be installed also. I understood that rooting was included but some applications needed SU.

Not sure why the GAPPS would install in the system partition that is used by the ROM. I would think that the system partition would be reserved for system only. I guess not knowing about how Android works I was wrong.

Bill
[Galaxy Note 10.1 (2014 Edition) Original Android D] r4yN:
The more variables (in this case: modifications a lá xposed, supersu, etc) there are, the harder it is for developers to troubleshoot (a.k.a. to find & fix the cause of reported problems).

If you flash g-apps, it installs said google apps as system-apps (that's why they can't be uninstalled, only disabled) & system apps are located (you guessed it) on the system partition.

So just flash pico or nano gapps & download the rest of the google apps you need from the play store (those are then installed onto the data partition, in case you're wondering ;)).
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hey r4yN!

You are partielly right

but we have 2,4gb system partition, more than enough for cm+full gapps. Remember, stock sammy builds are between 1.3-1.5gb!

BTW,

SuperSU2.78sr5 "is" the latest "official" from Chainfire and fixes some su issues in 7.1 roms.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi Drisanna,

seems you are on the wrong 5.1 bootloader. You need to revert back to kitkat bootloader to avoid crackling sounds and other issues.

Here's the easiest how-to:

http://xdaforums.com/galaxy-note-10...cial-build-t2980604/post65631142#post65631142

If stock rom download is slow or not available download repair firmware from my mega cloud: https://mega.nz/#!aIFjgRqJ!6qmrEMmspGvrRwnTaWNwyitX3BUiICNUyGJlNFKgcdk
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
Now I am confused again. Do I need to install SuperSU or does the Rom take care of it? Seems to be conflicting answers in the group.

Bill
[Galaxy Note 10.1 (2014 Edition) Original Android D] 0killer:
My Experience also shows dont install SU. I cant see any advantage in doing so. Root is built in the rom.
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
How do you give acces granted without SuperSU?

Dont like the prompt...
[Galaxy Note 10.1 (2014 Edition) Original Android D] wadken1:
Developer options/Manage root accesses