yashsingh1/xdaforums huggingface dataset:
[Galaxy Note Pro 12.2 Android Development] HuDeeb:
The problem is (yes, there is a problem, just not here) that the "OFFICIAL Nightly" (I mean to be loud, not screaming) at LineageOS download page is still mucked up. It will be bad here... But it's not, just the OFFICIAL version, but one can not simply move back here to the UNOFFICIAL nightly. I hope you got my and others issue?

The reason we are reporting the problems here is because

1. we (I?) Don't know where else to do it (LineageOS who?)

2. Our great (yes he is!!!) Developer here is one of (or THE one) the official maintainers of nightly, I think.

Please don't attack me, I am just trying to help by reporting...

Brotherly Love to all (sisterly too)
[Galaxy Note Pro 12.2 Android Development] Charmandrigo:
Why dont you simply go back to stock with odin and then try the installing process again?
[Galaxy Note Pro 12.2 Android Development] HuDeeb:
What install process?

I've been running this rom for a year or so now, I also installed other custom roms on several devices....

I wiped and moved to the official nightly soon after they become available at the advice of this OP accepting stability over new features.... Now (3 weeks of nightlies) have failed install! Clearly a defective package (as I wrote before in the last couple of weeks) the "system.dat.new" inside the install package is smaller (by 24MB or so!) than all previous version (3 nightlies with the short "system.new.dat)

My reporting here is to simply report my finding to the OP or anyone who needs to know, if you can help, do so, if not why add to this dialog?

I am happily running the August 12th "official nightly"

So again thank you for any help, at any time, you can do for the community of proud owners...
[Galaxy Note Pro 12.2 Android Development] thompatry:
The issue had to deal with kernel being rebased to maintain official build status. I think it is not booting because of SELinux. I will need to look and rewrite a few SELinux rules. This is why it is a smaller build.

Now you my asked, why didn't you test it. I did test it but I am not the only device with this kernel. So we all must play nicely. I apologize again. I will try to get this resolved asap.
[Galaxy Note Pro 12.2 Android Development] thompatry:
Correction, we had some vendor blob issues not merged. I have had the old builds removed and have a requested for a new build to be built. Next build should fix everything.
[Galaxy Note Pro 12.2 Android Development] HuDeeb:
Thompatry, thanks for your hard work on a really great rom and also for your assistance and support!

For future reference, what must we do to alert LineageOS of installation or package issues such as this? Is this forum a proper place to do it and if, not so much, does anyone know how?
[Galaxy Note Pro 12.2 Android Development] thompatry:
Ping me here
[Galaxy Note Pro 12.2 Android Development] antieau:
I've been using this ROM since the day after it was posted, and have been amazed by the responsiveness and battery life. Deathly Adiutor gives us access to a number of features that help on both counts. Great work, what an amazing surprise for Xmas.

The one problem I've been looking for a solution since early CM13 builds is that hangouts crashes every time at the first character typed in response to an SMS message. This is specific to the hangouts dialer add-on to hangouts. Has anyone found a solution to this problem?

By the way, this was a clean fresh install after a complete wipe of everything. Other than the occasional crash of EZpdf and this hangouts issue, this ROM has been amazing. I never expected to see a current Android version on our NotePros from 2014.
[Galaxy Note Pro 12.2 Android Development] Ludespeed:
Care to share your deathly auditor settings?
[Galaxy Note Pro 12.2 Android Development] GuyFromDenmark:
Are there any major errors in the current build? Also, is it stable?
[Galaxy Note Pro 12.2 Android Development] DGT79:
Hi [MENTION=4305688]GuyFromDenmark[/MENTION]

Here are the following issues that are known to us:

1. "OK Google" or also known as Google Voice services, is nto working right now, this is a tricky issues and will require some time to resolve, but it is high on the priority list

2. Google Hangouts SMS services is also not working, causing frequent force closure or locking the tablet up when using it, investigations into this one will kick off soon, as the dev team will work on a top-down order and on one problem at a time to avoid introducing further bugs/issues

3. S-Pen issues are also noted, this is not happening to everyone but it is happening to a fair chunk of people so it is under investigation

4. Audio and Charge settings are not baked into the ROM as of yet, one has to use Deathly Auditor to tweak it, however once there is a clear consensus as to what the settings should be, they will get baked into the ROM, and then Deathly can be used for further tweak if so desired

5. The default Google Camera application may not work if it was not initialised at the first boot correctly, the camera is still there but can only be accessible from the lock screen as the app icon/shortcut is missing from the app draw, this is a rare problem, but there is another solution that I worked on which forced me to stumble on another good camera app, I ended up installing "Open Camera" which prooves to be far better than the default one anyway

NOTE: If you used TWRP to backup your CM13 apps, you should not be restoring it onto this version CM14, you really need to do a full wipe and reinstall from scratch, we will not accept or monitor complaints unless the ROM was from a clean install.

That is about it for now, there are others on the list, but they are more featureset requests and just annoying bugs that will get ironed out once the priority list has shrunken.

This ROM is right now at the minute capable of being a daily driver, it is botu 95% production ready which in a custom ROM world, that is daily driver ready.

Cheers,

David.
[Galaxy Note Pro 12.2 Android Development] antieau:
In Deathly Adiutor, I've only made changes under CPU core control:

Touchkey, touchscreen, and s-pen boosters are all on. The only one I've really tested is the s-pen booster, but it does make the lag go away when writing.

Schedule workqueues on awake CPUs is on, multicore power saving should help too, but I'm not sure that this is being set as it keeps resetting back to disabled.

The last thing I've set is the CPU minimum frequency to 100 MHz.

These are just a starting point, but battery life seems much better than I was seeing with CM13.
[Galaxy Note Pro 12.2 Android Development] bigbot3:
Hi, I have followed your script to switch from the CM root manager to supersu 2.79 SR1 and it works!

After step 5 i didn't find anything "su" like in the bin or xbin directories.

At first i thought it didn't work because the tablet rebooted again after the initial CM Logo display but the second boot was succesful and now everything works as expected.

Thanks!
[Galaxy Note Pro 12.2 Android Development] Don B:
Titanium Backup Missing Setting Menu

Since installing this ROM I have no settings menu in titanium backup, I've been copying my backup file back and forth from the SD Card to internal storage, if your having the same problem and want to restore from you're SD Card here's a work around to see the menu and pick a backup or restore location.

Settings ---> Buttons ---> Home Button ---> Long Press Action ---> (Pick) open/close menu

Now when in Titanium Backup a long press on the home button will open the settings menu.

Note: It seem its possible to restore from any folder but if you want to backup to the SD Card the folder needs to be in

SD Card/Android/data/com.keramidas.TitaniumBackup :)
[Galaxy Note Pro 12.2 Android Development] Yemble:
If you use Google's Documents interface, which is an option in TB, then you can use any folder on the extSD card. The only downside is that the max single file size on this interface is 2Gb.
[Galaxy Note Pro 12.2 Android Development] bigbot3:
I also had no settings menu, but after a while i found it by accident, you have to press the "Problems?" button on the main screen (in the lower right corner) then you find a settings button. :)
[Galaxy Note Pro 12.2 Android Development] Don B:
Thank you very much, I looked around forever yesterday to find the other info, LOL, your way is better :)
[Galaxy Note Pro 12.2 Android Development] Don B:
I decided to try this, before I started I used (Advanced --> File Manager) and like [MENTION=293327]bigbot3[/MENTION] I didn't find "su" files in /system/bin (/system/xbin didn't exist) but I did have supersu directory at the top level so that's what I deleted (Folder and files)

----------- My exact procedure -----------

1) installed SuperSU and SuperSU Pro from Google Play

2) lunched SuperSU and canceled binary update.

3) scroll down to full / permanent unroot (didn't like doing this the warning is scary)

(from TWRP, **mount system first**) <-- didn't have a clue what this meant, I assumed boot to recovery, is that right?

4) When SuperSU closed I booted directly into Recovery (I didn't power off first)

5) In advanced --> File Manager I deleted /supersu directory and files.

6) Installed SR1-SuperSU-v2.79-SR1-20161221223537.zip

7) Wiped dalvik cache and rebooted

It's running great, thank you:)

If the instruction **mount system first** was an important step I missed please let me know.

Note: 1) the message " Kernel is not SEANDROID Enforcing" is now gone when rebooting and the reboot time is amazingly fast, It's nice to have that annoying Privacy Guard message gone, it was popping up constantly, hope I did everything right :confused:
[Galaxy Note Pro 12.2 Android Development] phirestalker:
Does anyone know where to access screen mirroring on this? Or what to install to enable it?
[Galaxy Note Pro 12.2 Android Development] Don B:
Go up and hit cast on the quick launch settings, if you don't see the device you're casting to click (More Settings), when that window opens , right hand corner 3 dots and check the box ( enable wireless display) you're device should be there:)

Note: you need to fully expand the status bar to see the (More Settings) option.
[Galaxy Note Pro 12.2 Android Development] phirestalker:
Thanks, I found it. Unfortunately it tries to connect and then says it has ended. I hit accept on the tv, so it must be something else
[Galaxy Note Pro 12.2 Android Development] Don B:
Your welcome.

Is this a smart tv or a chromecast dongle, if its a chromecast dongle you might try the Google Home app, I use the cast feature on 2 TV's but the one in my shop with the chromecast dongle I needed to use the Google Home app to initiate the first connection, after that I was able to uninstall Google Home app and use the cast.

Good luck :)
[Galaxy Note Pro 12.2 Android Development] phirestalker:
It is a Samsung smart tv. I was able to use screen mirroring on this tablet running stock marshmallow.
[Galaxy Note Pro 12.2 Android Development] Don B:
That's what I'm connecting to is a Samsung smart tv, you've probably done this but the only other thing I can think of is are you switching the TV to the screen mirroring input, I needed to do this for the initial connection, affter that it doesn't seem to matter what the TV input is on.

Good luck, I hope you you figure it out :)

EDIT: maybe an old profile on the TV is screwing things up........?

Don
[Galaxy Note Pro 12.2 Android Development] phirestalker:
No dice. I deleted the tablet from the TV, forgot the TV on the tablet, turned them both off. I went to screen mirroring under setting on the TV and it shows the instructions on how to enable it on your device. I chose the TV in cast on the tablet (under more settings, never shows up directly even after enabling). The TV and the tablet both say connecting. The tablet pops up with an invitation to connect from the TV and I choose accept. Then it times out and it won't even attempt to connect after that
[Galaxy Note Pro 12.2 Android Development] cadilhac:
Hi there;

I hope it's a bad fluke, but my last_kmsg comes out garbled after the most recent crash (freeze). I attach it nonetheless; there's some things towards the end that may indicate that /proc/last_kmsg got overwritten at reboot.
[Galaxy Note Pro 12.2 Android Development] Manya3084:
Anyone having issues playing purchased movies from Google Play Movies?

I just get the spinning circle constantly and the video never loads.

I remember having an issue in the first instances of CM13 but the problem was fixed in later builds
[Galaxy Note Pro 12.2 Android Development] HuDeeb:
You're the man! Thanks
[Galaxy Note Pro 12.2 Android Development] risant:
when will lineage 15.1 be release for samsung P900 ?
[Galaxy Note Pro 12.2 Android Development] DGT79:
When it is stable to be released to the public, it is almost there from the testing I have done so far.

I know that [MENTION=4817899]thompatry[/MENTION] is working his but off to get it completed amongst the stupid hours he is having to do for his real job, for me the wait is absolutely worth it as this is yet another major transformation for this tablet, it will change it yet again and to the point I am investing money in mine to buy a new battery to breath some new life into it.

Sit tight, be patient and you will be satisified with a far better polished product than a rushed one :)

Cheers,

David.
[Galaxy Note Pro 12.2 Android Development] HuDeeb:
All is well now with the Official Nightly.

Thanks thompatry, once again you saved the day!
[Galaxy Note Pro 12.2 Android Development] DaveUK:
Latest build installed and booting as normal.

Thanks for your efforts getting working again.

Dave
[Galaxy Note Pro 12.2 Android Development] HuDeeb:
Thompatry, I noticed on TWRP that you are their maintainer and so I have a Question about it. In most of my devices that use TWRP I have an option to format the partitions "F2FS" but not for the P900, is there a technical reason for the omission? I normaly format my Cache and Data partitions F2FS, leaving the System as EXT4, are there arguments for or against F2FS in general and specifically for the 5420?

Also, Governor and Scheduler settings that are best for our device (with an external 64Gig sdcard)?

Thanks for all your help and great work!
[Galaxy Note Pro 12.2 Android Development] Yemble:
ROM 8th Sep - Failed Boot

8th Sep ROM (unofficial) failed to boot after successful flash. Just got the Lineage logo of infinite death!

Immediately flashed back to 1st Sep ROM without any issues.
[Galaxy Note Pro 12.2 Android Development] thompatry:
I will look into why f2fs is not working.

Interesting. I will take a look into this. We have been working on bringing the latest cve's up to date for the kernel.
[Galaxy Note Pro 12.2 Android Development] thompatry:
Latest builds have been pulled since it doesn't boot. We will try to get it fixed and have them rebuilt.
[Galaxy Note Pro 12.2 Android Development] DaveUK:
Hi everyone,

Today's 09/09 build has installed correctly.

Dave
[Galaxy Note Pro 12.2 Android Development] thompatry:
I was going to say that new builds are up. You beat me to it.
[Galaxy Note Pro 12.2 Android Development] DaveUK:
Hehe it popped up in my downloader.

Usually do once a month install after the security patche.

go in. Thought I'd give this one a go

Thanks for your hard work.

Dave
[Galaxy Note Pro 12.2 Android Development] Yemble:
Confirmed :good:
[Galaxy Note Pro 12.2 Android Development] risant:
been waiting for the release of lineage 15.1 for samsung p900
[Galaxy Note Pro 12.2 Android Development] thompatry:
You can keep waiting.
[Galaxy Note Pro 12.2 Android Development] HuDeeb:
Risant, I hear lineage(Oass) 16 is coming 1st (really, real soon, b4 u know it) LoL:(:highfive::(
[Galaxy Note Pro 12.2 Android Development] oldseddie:
Update scripts not running

For some reason my tablet won't rrun the scripts in TWRP. I'm running the latest version of TWRP and when I tell it to update it reboots to TWRP it stays on the menu. Update works fine on my nexus 9. Also where are the update files downloaded to so I can do it manually.Thanks for your work on this ROM.
[Galaxy Note Pro 12.2 Android Development] thompatry:
Are you on the correct version of the bootloader?
[Galaxy Note Pro 12.2 Android Development] oldseddie:
.Thanks for the quick reply. I will check this. I figured it was something simple!
[Galaxy Note Pro 12.2 Android Development] oldseddie:
I odin'ed the bootloader linked from the OP and ran update with no joy. I did notice an 08 vender date. Could this be the problem?
[Galaxy Note Pro 12.2 Android Development] HuDeeb:
Mine have always had the same issue on the 'official nightly', the reboot ends at TWRPs main menu and I go to data/lineageos update/ via the 'install' menu manually... I thought that was the norm :cyclops:
[Galaxy Note Pro 12.2 Android Development] oldseddie:
My nexus 9 reboots to the recovery and runs an update script but now that I know where the updates are stored I just dirty flashed it. Thanks
[Galaxy Note Pro 12.2 Android Development] Yemble:
Two questions spring to mind...

What version of TWRP are you using (read this: https://xdaforums.com/galaxy-note-p...yanogenmod-t3524788/post76085654#post76085654)?

Are you rooted with Magisk and if so, which version?

The upgrade procedure has always worked for me with the

unofficial

ROM, for as many years as I can remember. If there are going to be any issues, it is normally on the post flash reboot. I currently use Magisk 17.1 for root.
[Galaxy Note Pro 12.2 Android Development] Mr Creosote:
I've had problems running update scripts in twrp before, both with unofficial lineage on my note pro, and official lineage on my note 3. then i realised it was because I'd left zip signature verification enabled from when i installed opengapps aroma package. when i unticked that, it worked fine again.
[Galaxy Note Pro 12.2 Android Development] oldseddie:
I don't have an update to run now but I when I checked TWRP verification was unchecked. Never mind the comment about the vender as I don't know where I saw that. Late night.......
[Galaxy Note Pro 12.2 Android Development] risant:
I was wondering when will lineage 15.1 be release for samsung p900?or lineage 16.1?
[Galaxy Note Pro 12.2 Android Development] DarkManX4lf:
Any idea why YouTube videos cannot play at 1440p? The option doesn't even show up. Max resolution is 1080p.
[Galaxy Note Pro 12.2 Android Development] thompatry:
The resolution is set to 1080p. The reasoning is because anything higher causes huge battery drain. At 4K and Max charging, the tablet will die in less than 30 mins.
[Galaxy Note Pro 12.2 Android Development] HuDeeb:
Thompatry, have you verified the lack of F2FS in TWRP recovery? If not, is there a reason for it, or this hardware is not suitable or incapable of implementing it? also, is there a reason the update script always fail to execute on the OFFICIAL Nightly?

thanks for your help!
[Galaxy Note Pro 12.2 Android Development] thompatry:
I thought I had f2fs enabled for 14.1. Let me dig around and I will let you know.
[Galaxy Note Pro 12.2 Android Development] leonelsr:
How did you guys manage to make S-Pen Power Saver work on LineageOS?

I desperately need this on Note 8.0 (N5100) but I don't even know where to look on the code. Can someone point me some directions? Then I could clone the repositories and try to port it on my spare time.

Or else, at least some way to just disable S-Pen layer "permanently" by changing some configuration file or hard coding something on the source. Where should I look for the S-Pen detection feature on the source code?

Thank you!
[Galaxy Note Pro 12.2 Android Development] mintsoft:
Hiya,

Do the currently 14.1 nightly builds work for anyone (right now those are: 2018-10-14, 2018-10-07, 2018-09-30, 2018-09-23, 2018-09-16)?

I've tried back to 2018-09-30 and they all install, however result in a black screen on boot. I'm about to try 2018-09-16 to see if that's any better, but I'd like to know if it's just me!

Thanks in advance

Rob
[Galaxy Note Pro 12.2 Android Development] thompatry:
Please see the first post about the bootloader. It is very important you have the right bootloader installed.
[Galaxy Note Pro 12.2 Android Development] thompatry:
Please PM me I can help. If you would like to Port it, here is a good starting point. https://github.com/exynos5420/android_kernel_samsung_exynos5420/commits/cm-14.1/drivers/input/wacom
[Galaxy Note Pro 12.2 Android Development] rhricik447:
I just loaded the 20181013 ROM and it is working just fine (as usual!). As stated, make sure your bootloader is correct, otherwise you *will* see just a black screen on boot.
[Galaxy Note Pro 12.2 Android Development] sonicshaman:
Issues with 'Cast' to Samsung Smart TV. This used to work for me a while ago, it won't connect now. Looks like it's trying, but doesn't. It seemed like someone earlier had issues, but I saw no resolution?
[Galaxy Note Pro 12.2 Android Development] thompatry:
It is resolved. Are coming from a clean flash or dirty flash? Also, you got to get me some logs from a clean flash. Simply said, it works unless you have logs showing it doesn't.
[Galaxy Note Pro 12.2 Android Development] J Free:
I've been on your ROM for quite a while, I've been dirty flashing weeklies. I'm assuming I should then try a clean flash first?
[Galaxy Note Pro 12.2 Android Development] J Free:
Answered my own question, did a clean flash and all is well. Thanks, and sorry about that.
[Galaxy Note Pro 12.2 Android Development] mintsoft:
Doh! You're absolutely right, that's fixed it thanks!
[Galaxy Note Pro 12.2 Android Development] thompatry:
Any time!
[Galaxy Note Pro 12.2 Android Development] DGT79:
Ahhh you fluked it :D
[Galaxy Note Pro 12.2 Android Development] Charmandrigo:
I can see the freezes happened to many, including me.

As many described, it happens while the S-Pen is being used, however with me it happened while:

Scrolled on apps using the pen (Facebook, youtube, Puffin Browser, etc.)

Using drawing apps that take a lot of memory (Infinite Painter and Medibang)

The freeze is more probable to happen while using the pen on apps that show a decrease of speed on the scrolling. Has it already know what keeps causing this or what's the possible hotfix?
[Galaxy Note Pro 12.2 Android Development] thompatry:
When was your last clean flash?
[Galaxy Note Pro 12.2 Android Development] Charmandrigo:
I just did a clean flash yesterday, it was working perfectly until I had to do a force restart (10 second lock screen button press), after that restart, the issue returned
[Galaxy Note Pro 12.2 Android Development] HuDeeb:
Thompatry, what happened with our F2FS investigation, do we have it or don't we? I thought you said that you will verify it's inclusion in the recovery and/or kernel...

thanks for all your work and help.
[Galaxy Note Pro 12.2 Android Development] thompatry:
I haven't had time yet. I have been traveling every day for work on top of working 12 hour days.