yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Original Android D] FamAckermans:
I am running this ROM now for a few weeks. Battery live has never been close to the current on time. Stand-by time is even better. The last 2 versions 1107 and 1113 have been extremely stable. I am successfully running Kodi version 16.1 at hd quality. Really great work. :svetius:
[Galaxy Note 10.1 (2014 Edition) Original Android D] Leoxur:
In the next build can you add some tile in the Quick settings (like screenshot, sound to control fastly the volume, power menu to take partial screenshot) and volume keys control media volume
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
We need someone to test out a build for the LP bootloader, any volunteers?

PM me if you want to help out, but you must be on the LP bootloader for this

Edit: I have enough testers now
[Galaxy Note 10.1 (2014 Edition) Original Android D] DeanoD:
So far, this is one of the best builds that I've ever installed. That being said, I still have a few minor issues. The CM install wizard does not compare to the google version, IMO.

And WHAT is with the overly tetchy screens in recovery (3.01 ?) It's like playing whack-a-mole with everything jumping so fast when I go to select my install zips. A REAL PITA with arthritic hands, believe me! :D But everything is running solidly, so this is now my daily driver.

Thanks again for all the great work(and patience). So NOW they're working on fixing the LP bootloader? And will we need ODIN to put it BACK? ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
You will need Odin to put it back, however our plan is to make it so you don't have to put it back, we're just trying to support both boot loaders.
[Galaxy Note 10.1 (2014 Edition) Original Android D] malim20:
I have this installed on a P601 and man the battery drains so fast, how's the battery life for others?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
I would test it, because i am already on latest LP bootloader. I was just waiting for this suggestion. :D

Oh man, next time i will read your post until the end before i reply:silly:
[Galaxy Note 10.1 (2014 Edition) Original Android D] qkdingus:
first of all, thanks ZakooZ for the awesome work.

can you please merge the adopted storage fix for this rom? https://review.cyanogenmod.org/#/c/171068

keep up the good work :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] Leoxur:
How can I see witch bootloader am I using?
[Galaxy Note 10.1 (2014 Edition) Original Android D] etmflde:
Do you run Kodi with the localy installed files or trying to play them using SMB or NFS from a remote server? On my P600, Kodi 16.1 crashes the tablet each time I try to start it (uninstall it and reinstall it several times now). I have installed now a beta 17 version and this one at least starts but the tablet crashes as soon as I start indexing the remote location.

---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------

On my P600 with WiFi off while the tablet is with the screen off the battery life is actually pretty good. With WiFi always on, the battery was draining also quite fast (but that was on the 20161107)
[Galaxy Note 10.1 (2014 Edition) Original Android D] marclais:
Full screen videos have the right and bottom cut off. YouTube specifically. Anyone else have this?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
If you're on the lollipop one you'll see a red "seandroid is not enforcing" message at the top left corner at boot unless if you are on touchwiz. If you don't get that message, then you are on the KitKat bootloader. You can also run this terminal command to find out which one you're on: getprop ro.bootloader
[Galaxy Note 10.1 (2014 Edition) Original Android D] theophile2:
What CPU governors/settings are people using? I'm noticing that many of the options cause the CPU to peg at max when set. Looking at the default tunables for several of them, I see some frequencies that are way outside the range of this CPU (like 2.8 ghz for "nighmare" for example). That makes me think that some of these governors could be better optimized if tuned properly. So what's working for you?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
I use conservative, lionheart also works well
[Galaxy Note 10.1 (2014 Edition) Original Android D] hallucinate:
Since my latest clean flash to 11/07, I've been getting about once a day black screen of death requiring a hard restart. Anyone else seeing this? I tried reflashing 11/07, and dirty flashing 11/13. Still getting it... pretty annoying. Also, the button lights get stuck on if you have them disabled - a settings toggle resets them but they seem to get stuck on again within a matter of minutes to hours.
[Galaxy Note 10.1 (2014 Edition) Original Android D] theophile2:
Tablet won't deep sleep if on conservative. And on lionheart, CPU frequency is pegged at max all the time.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Leoxur:
Yes, mee too... Dev needs a logcat, next time I'll catch
[Galaxy Note 10.1 (2014 Edition) Original Android D] Genebaby:
Sometimes my buttons light up and flash for apparently no reason. They are enabled, I don't use on screen buttons.

Flipboard still has issues, it mostly works, but can crash inside an article, which takes me back to the news feed I was on, but with that crashed article missing.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
The button light issue has been fixed in source, so it should be fine in the next build, can you get a log for the Flipboard issue?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Genebaby:
Thanks, good to know about the buttons. This is my first time logging, I hope it's ok.

11-19 09:12:42.901 E/flipboard(21351): Only a background thread is allowed to do that: ItemCache:readItemsFromDisk

That seems to be the error I just made it crash again, but it's better than the last Rom version for sure.
[Galaxy Note 10.1 (2014 Edition) Original Android D] rehellio:
I'm also having the same problems as these two are having above. What info do we need to provide to help debug some of these problems?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Ruben_vd_Bos:
Thanks for this great rom, it's so smooth!! But I have one problem. I did a clean flash yesterday on the kk bootloader. Everything was fine and the rom was awesome. When I started playing around with multiwindow, the device suddenly started a bootloop. I wil install it again today, but has anyone also got this problem?

Verstuurd vanaf mijn UMI_SUPER met Tapatalk

---------- Post added at 08:06 AM ---------- Previous post was at 08:03 AM ----------

Wait I installed SuperSU yesterday, maybe that is the problem?

Verstuurd vanaf mijn UMI_SUPER met Tapatalk
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi theo,

try darkness governor! :good:

I'm really a heavy user (5-6h daily)and I got the best battery and device performance on darkness governor.

Temps are always in the mid thirties and never seen locked cpu frequencies on this governor. :cool:

I uc/oc'ed the cpu from 150-2000mhz with absolut no issues. (Antutu +56.000)

I think some of these governors are not ready to work on octacore cpu's with big/LITTLE architecture or was simple made for qualcomm devices.

I've seen the "locked at max. freqs" issue many times on CM13 roms (Temasek "and" Orion) and only a reboot solves it for a while.

Later I'd applied some governor tweaks(more or less the same as on interactive governor in this kernel) and it was better for some reason but never was totally gone. And the same behavior is now visible with the cm14 kernel. :confused:

I think the simplest governors are currently the best option to avoid overheating/locked freqs issues (darkness, ondemand, wheatley).

---------- Post added at 09:30 ---------- Previous post was at 09:28 ----------

Hmm!

I've no such issues with build-in superuser!

---------- Post added at 09:39 ---------- Previous post was at 09:30 ----------

Hey Genebaby.

Buttons starts blinking on incomming notifications while screem off.

A small workaround to avoid buttons from blinking is to disable the notifications or set importance at level 1 or 2 for the app which cause it. (In my case gcalender)

BTW,

To grab a log-file install SysLog app from plays

reboot to keep it as short as possible,

replicate the issue,

grab a full log with syslog(or any other logcat) and

post it here.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Genebaby:
Ok, hopefully this is a good log.

http://cloud.tapatalk.com/s/583035c709ca3/2016-11-19_22.15.zip

And I'm trying the darkness governor.
[Galaxy Note 10.1 (2014 Edition) Original Android D] pn1fon1:
Hey guys,

An off topic question,

Which I/O scheduler should I use with this device

Thanks
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
It doesnt really matters...

Take the stock one, should be "bfq"..

If you want to increase storage performance disable fsync!
[Galaxy Note 10.1 (2014 Edition) Original Android D] theophile2:
[MENTION=4810273]ZakooZ[/MENTION], is this the source tree for the kernel that is included in this rom?

https://github.com/exynos5420/android_kernel_samsung_exynos5420/tree/cm-14.1-rebase

I tried compiling it myself using the cyanogenmod_deathly_n1awifi_defconfig, without any modifications or changes. It build fine with stock GCC 4.8, and I packaged the zImage into a flashable zip using the AnyKernel2 script (same process I've used for building kernels for stock 5.1.1), but after flashing, I get a bootloop early on--never gets to the CM boot animation, just loops the Galaxy Note 10.1 splash screen over and over.

I read elsewhere in this thread where you were saying that the CM13 kernels won't work on CM14.1 due to some changes in the graphics drivers so I just wanted to make sure I'm working from the right source for this rom. Also, I'm not sure whether kernel flashing works the same way on CM as it does on stock.

Any pointers appreciated! Thanks for a great rom!
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
That kernel is a work in progress and doesn't boot

I recommend https://github.com/zakooz/android_kernel_samsung_exynos5420 right now
[Galaxy Note 10.1 (2014 Edition) Original Android D] Ptyrss:
I`m install for P601. Work fine (missing some text in rus locale), but what can I do (install any soft or using part of another ROM) for make calls?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hey ptyrss!

Maybe if you add modem files and all the needed stuff but I dont think it's so easy!

But if you have the skills it is surely usefull for other P601 users.

You should talk with ShefT, he own a P601 and have an own CM13/RR thread.

http://xdaforums.com/galaxy-note-10...-p601-cm13-unofficial-builds-note-10-t3272812
[Galaxy Note 10.1 (2014 Edition) Original Android D] stapler85:
i had been using p601 LL rom on my p600, no problem except the battery life reports oddly due to the modem not actually present and seems it constantly tries to look for mobile signal?
[Galaxy Note 10.1 (2014 Edition) Original Android D] DirkStorck:
Since you can't use mobile maybe activating "flight plan mode" helps :confused:
[Galaxy Note 10.1 (2014 Edition) Original Android D] stapler85:
that would also disable wifi?
[Galaxy Note 10.1 (2014 Edition) Original Android D] DirkStorck:
Not if you enable it afterwards again...just try it. :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] dronarg:
Thank you so much for this great rom

I just flashed it on top of orion rom with wipe of sytem and cache and everything works fine.
[Galaxy Note 10.1 (2014 Edition) Original Android D] theophile2:
Thanks [MENTION=4810273]ZakooZ[/MENTION]! I'm not a dev, just a tinkerer. But if you're interested, I've got a patch to fix the Smartmax and Smartmax EPS governors.
[Galaxy Note 10.1 (2014 Edition) Original Android D] DeanoD:
Odd Stuph

Now that I've had a chance to test this ROM as my daily driver, I'm noticing a few odd things here and there. Some can be tinkered back into place, others not so much. In settings, under time/date, I can no longer see my local time zone -every thing else but that one. And when I try tofix it, I get multple time displays on top of each other in my status bar. And, in fonts, no matter what I try, or install, I can't see any fonts past "r"'s. Last one, I think is related to incompatibility with Android 7--my CNN app refuses to launch. Also, I'm having probs now with Play store not installing downloaded apps, or running too slow to function.

I'm not sure if log files would be much help with multiple glitches like this. Anyhoo, I'm just reporting what I am dealing with. Still a good solid ROM with MUCH better charge & run times!! ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Original Android D] stamina11:
Hey guys, i am still on KK 4.4.2. Just went back to stock using TWRP. How do i get from 4.4.2 to 7.1? Can i download Nougat and flash it with Odin?
[Galaxy Note 10.1 (2014 Edition) Original Android D] wadken1:
As you have TWRP installed already you can just follow the installation instructions on the OP. I would recommend that you do a full backup in TWRP before the Factory Reset though so you can always get back easily to your current set-up.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hmmhh, strange!

I've no such issues with playstore. Works fast and downloads and installations are much faster as earlier. I've also no issues with my time and location, all was applied automacticly, but I clould imagine that your fonts and modifications are the culprit.

I would remove all these modifications, then wipe cache and dalvik and reboot.

Theming is currently not supported and I would not try it in such early rom state!
[Galaxy Note 10.1 (2014 Edition) Original Android D] stamina11:
thanks for the reply, i always thought that i had to update to that OS version in order to install.

one more question: as i tried to install it, i got a message that my device is v1awifi and this is only for lt03wifi, lt033g, lt03wifiue, n1awifi.

What is it referring to?
[Galaxy Note 10.1 (2014 Edition) Original Android D] wadken1:
.

These are the real Samsung device model references. According to Google yours, v1awifi, is a Note Pro 12.2 !! whereas all the others are variants of the Note 10.1 which is what this rom is compiled for. (The Note 10.1 2014 wifi is designated "n1awifi")

If you really have a Note Pro 12.2 then you're going to have to find a suitable rom from the appropriate forum.

If you do have a 10.1 then I guess that somewhere along the line the model data in your device has been overwritten with the wrong information. I don't know enough about these details to be sure or to advise on how to fix it so hopefully others here can help you.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
It means that either Zakooz messed something up in source, or you are in the wrong forum, v1awifi is a completely different device, are you sure that you have the Galaxy note 10.1 2014 edition? v1awifi is one of the other note devices

Edit: double post
[Galaxy Note 10.1 (2014 Edition) Original Android D] stamina11:
My mistake. After upgrading TWRP from 2.7 to 3. I was able to successfully install the ROM. Thanks mosimchah for your help.
[Galaxy Note 10.1 (2014 Edition) Original Android D] stamina11:
i do have a question, is it by design that my tablet now cannot see dual bands? it sees 2ghz but doesn't see my 5ghz one?
[Galaxy Note 10.1 (2014 Edition) Original Android D] movieifx:
I'm seeing both WiFi bands from my router so nothing is blocked by ROM.
[Galaxy Note 10.1 (2014 Edition) Original Android D] stamina11:
Wiped everything, including the data. Reinstalled CM still not 5ghz. Did another wipe and installed Orion to compare - same result. Darn what am i missing? i remember with HyperDrive i had to install some wifi fix after installing the rom.
[Galaxy Note 10.1 (2014 Edition) Original Android D] movieifx:
Just checking have you got other devices seeing 5ghz OK ? Only asking because I had something similar and it was router that had decided to switch off its 5ghz band.
[Galaxy Note 10.1 (2014 Edition) Original Android D] stamina11:
All of the devices are still connected to 5, including this Mac. I am doing a restore right now to see if stock 4.4.2 will see it. Maybe it's 7.1 that my tablet doesn't like.
[Galaxy Note 10.1 (2014 Edition) Original Android D] stamina11:
Rolled back to stock 4.4.2 and able to see both 2 and 5 bands. Did a Factory reset wipe and then installed CM14.1 - can't see it. :crying:

Thought i would try with CM12 (Marshmallow) same story, no 5ghz. That's interesting that i am on the only with this issue.

Maybe i will post in questions/issues to see if anyone had this issue before, i just figured you guys deal with ROM development and might know. But i don't want to spam your thread with general issues since it's not really related to CM.
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Not sure that works but you can try:

In /system/etc/wifi there are one file:

nvram_net.txt

The installed one is for Great Britain,

Change "ccode=GB" to "ccode=US" and adds "regrev=5".

or go there: http://xdaforums.com/showthread.php?t=2273571
[Galaxy Note 10.1 (2014 Edition) Original Android D] stamina11:
Took me a second to figure out how to enable root.

Oh man, thank you so much that was the fix. Now I am in a holiday mood. :laugh: :good:
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hey Enotar!

Where to add these "regrev=5" entry? Right behind the changed ccode or in an own row? I already have a regrev= entry but with a 6.

Thanks.

BTW

I'm able to use invisible 5ghz wifi by only deactivating 2,4ghz band completely in router settings.
[Galaxy Note 10.1 (2014 Edition) Original Android D] DeanoD:
Odd Stuph Again

After three new flashes, two full and one dirty, I had to go back to CM 13 ResRemix. I was getting error messages at the start of install "E: Unknown command", and then some trash saying my dialer had crash. (funny I got that on an install for a 600, but no probs with installing the 601 ResRemix on my 600). So, for the present, I will keep flashing and bashing but hopefully not trashing several different ROMS. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Original Android D] Whistler1813:
Just an observation of mine that may help with the 5GHz problems.

Yes, the country code and regrev have an impact on which bands are visible to your device.

The high 5GHz band (channels 149-161) appear to be the problem for most people and that band is not enabled in every ccode. I'm guessing that ccode=US and regrev=5 enables the high band on the tablet since that is one of the "legal" WiFi bands in the US.

To keep from having to change the ccode and regrev after every flash I manually set my router to use the low 5GHz band (channels 36-48) which seems to work no matter the ccode or regrev.

I've found that ccode=ALL does not necessarily enable the high 5GHz band. A lot of custom ROMs use ccode=ALL. You'd think "ALL" would mean it includes everything...it doesn't.
[Galaxy Note 10.1 (2014 Edition) Original Android D] rayik:
Thank you. That worked great. Nice to have 5ghz back
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Glad that worked
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
I'll try to include that 5ghz wifi fix in the future (hopefully it doesn't break EU-region wifi)
[Galaxy Note 10.1 (2014 Edition) Original Android D] Whistler1813:
I don't think it will break it. From the tables shown on Wiki it appears that the US and New Zealand have the most open bands which also encompasses the EU region channels.

I'm hardly an expert but I hope this was helpful.

BTW Thank you for this ROM! I haven't seen speed, battery life, and stability like this since KitKat. :good:
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Here's an updated kernel zip with improved deep sleep/ battery life https://www.androidfilehost.com/?fid=385035244224401303
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hey Mosimchah, and thanks for the new kernel.

He's booting but when on lockscreen and swipe up to unlock I get only a message "android is starting" but nothing else.

I've checked md5checksum and tried installing it with and without cache wipes, but no luck.

Is it working for others? Clean flash required?

---------- Post added at 09:47 ---------- Previous post was at 09:35 ----------

Hi DD,

You need to flash latest recovery in order to remove this "E. unknown command" error. I'm with ShefT's latest from here:

http://xdaforums.com/galaxy-note-10...-p601-cm13-unofficial-builds-note-10-t3272812

Download latest twrp.img file,

reboot in recovery,

choose install page,

choose install .img,

choose latest twrp.img

install and reboot into new recovery

Now you are able to flash 7.1 without error message:good:
[Galaxy Note 10.1 (2014 Edition) Original Android D] etmflde:
Any indication when the next drop will be released and some hints about what will be fixing?

For the moment, I have been forced to go back to CM13.0 - I could not get Kodi running properly on my P600 and I was getting too many out of the blue errors (e.g. Facebook, Flipboard and some other apps were suddenly not working any longer and I was getting those annoying pop-up windows telling I should mute the warnings until the next restart).
[Galaxy Note 10.1 (2014 Edition) Original Android D] Genebaby:
My Facebook works fine, only Flipboard gives me that error.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Hulm:
Get some errors with some apps and can't get access to the explorer.

Did a dirty flash.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Nameless One:
When I had that message I got to the home screen by going to recents and then to the home screen.

Things were very sluggish, many things, such as the play store, hanging until I went to something else and then back. Some things just giving a white screen between status and nav bars and no more.

The single best thing I've ever done on this tablet was getting this kernel off and returning to the CM 14.1 kernel.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
I tested the kernel thoroughly, I'm not sure why it's not working well for you guys.

Edit: I think I forgot to include some commits for cm, oh well
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Not a big thing, Lol!

**** happens!;)

Will the changes in your kernel be integrated in the next rom update?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
They've already been merged, so yes, and it's not just my kernel, it's the kernel of the exynos5420 team. There are quite a few different devs working on it.