yashsingh1/xdaforums huggingface dataset:
[Galaxy Note Pro 12.2 Android Development] DGT79:
Hi [MENTION=4698024]hansonc8[/MENTION]

I am now experiencing this issue, whilst it was prevelant on the stock ROM it was just not as exposed as it is on the custom ROM, probably because I just didnt use it as much on the stock ROM because it was laggy as all hell and overheated a lot.

As it turns out, I just have the same problem as everyone else :crying::crying::crying:

The issue you are experiencing is this:

http://www.androidauthority.com/com...uously-when-the-battery-drops-below-70.18785/

And this one:

http://forums.androidcentral.com/sa...te-pro-12-2-screen-flickering-problems-3.html

And this is from this very thread, but it is quite a few pages back, near the front

http://xdaforums.com/galaxy-note-pr...cyanogenmod-13-0-android-6-0-1-t3366834/page3

I did some temporary soldering to it today, though but it didn't work as intended as I simply don't have the right soldering iron or the right solder either, so I am sending it away to a friend to do.

If you know someone who can solder and is pretty darn good at it and has the right equipment including a bloody good magnifying glass, then you will need to follow this procedure 100%.

Anyway this tablet is going to get retired now to just a lab machine or a hand-me-down to my son, I need something reliable as I am a power user and use my tablet quite heavily every day, so I will get this repair done to it and then I am going to by the Google Pixel C or the new one when it comes out.

Cheers,

David.

[EDIT] I should point out that I am going to continue to do testing of [MENTION=4817899]thompatry[/MENTION] ROM's until such time I cannot, so far as a custom ROM it has been one of the most stable, proactively worked on, and the best outcome custom ROM I have used, I guess all credit to him and the team working on it, I have no doubt it will make many people happy that it has given their tablet a new lease on life...

I hope you enjoy that beer and coffee on me [MENTION=4817899]thompatry[/MENTION] produce another good update and I will donate another beer for you :D
[Galaxy Note Pro 12.2 Android Development] risant:
thompatry

when are u going to release the cm13 for T900?
[Galaxy Note Pro 12.2 Android Development] Yemble:
There seems to be an issue with the WiFi region in the latest release. If I set it to Europe, exit WiFi settings, then go back in, then NO region is shown as selected.

Furthermore, the 2.4GHz radio does not recognise any channel above 11. In Europe, ch12 and ch13 should be available.

This all worked in the previous release.

*** EDIT ***

I did eventually get the European region code to stick, but it did require a reboot. After the reboot, channels 12 & 13 became visible.
[Galaxy Note Pro 12.2 Android Development] thompatry:
Please read the T900 CM-12.1 thread. I have spoke about it twice in the last two post. Also, please donate. I cannot just afford a tablet out of my own pocket. This is going to be the last time I answer this question before reporting you to a Moderator for asking for an ETA. This is a clear violation of the rules.

------------------------------------------------------------

Thank you for all the feedback. I am still diligently working finalizing some things before I release the big news. Let me know if you have big issues.
[Galaxy Note Pro 12.2 Android Development] Logan5:
Hello all !

I contemplate to flash this ROM, coming from Resurection Remix 6.0.1 (MM bootloader). It is not clear wich version of this ROM works with MM bootloader. The first post of this thread still states that this ROM needs Lollipop bootloader. Is is a special branch and repository, or can I download 20160929 version ? Will this version works with Resurrection Remix's MM bootloader, or do I need to flash another MM bootloader?

Thanks for your answers !
[Galaxy Note Pro 12.2 Android Development] DGT79:
[MENTION=1386870]Logan5[/MENTION]

Flashing the 20160929 ROM update will wipe out what you have in place now, and this update operates on the MM kernel if you read what the Dev/OP said in the release/post.

You should not have any problems at all, but if in doubt, use TWRP and do a NAND backup (It is very simple, just make sure you have ample space on your SD Card) and try it out, if it fails make sure you also have the latest RR-ROM at the ready so you can roll back and liven up your backup.

Cheers,

David.
[Galaxy Note Pro 12.2 Android Development] Logan5:
Does not works. I have done a full wipe (including System and internal storage), flashed 20160929 and GApps, reboot => black screen following the Samsung Logo. Restoring NAND backup now.. Thanks anyway for your answer ! Is there an "official" MM bootloader to use with 20160929 ? or should I flash Lollipop bootloader ?
[Galaxy Note Pro 12.2 Android Development] Yemble:
Exactly the same upgrade path as me. Yes, you must upgrade the bootloader before this ROM will boot. AFAIK, the RR MM ROM has an older kernel and bootloader! Use the BL posted by thompatry on his download area, this one works.
[Galaxy Note Pro 12.2 Android Development] Logan5:
The bootloader in download area is dated september 6, and is still Lollipop BL ? I don't understand why others in this thread talks about MM bootloader ? OK anyway, I am now resigned to do a little ODIN, which I wanted to evitate (always stressfull). I realise that this ROM will probably never be compatible with RR bootloader, as I hoped when I saw people talking about MM bootloader for this ROM..
[Galaxy Note Pro 12.2 Android Development] shonkin:
Installed this last night while my dear wife slept and playing with it this morning. A few observations....

Used Sept 29 version.... used Sept 30 version of gapps (the newest at that point). Selected Pico.

I did have to reflash manually Super SU from a zip file before I could get root back. No biggie.

Sound is soft, even after I flashed the dap sound file referenced in this thread somewhere.

I installed AdAway immediately, then wondered to myself if it already existed in this OS and just had needed turning on; I haven't checked yet on that.

Coming from a stripped down (and sped up) version of the standard Lollipop with Samsung's touchwiz stuff, I am quite happy with the apparent speed increase. I'm back to my old desktop favorite, Nova, which further slickifies this OS.

Thank you! (Any further help w/ sounds would be appreciated. Maybe I'm just making some newbie error.)
[Galaxy Note Pro 12.2 Android Development] DGT79:
[MENTION=1386870]Logan5[/MENTION]

I have seen a couple of reports on here of people experiencing the same thing.

This is the procedure that I followed after I got the black screen:

* Did a full wipe everything but the SD card

* Installed the new ROM - once it finished clicked on the wipe dalvik

* Installed GAPPS full (Downloaded from the link that #thompatry provides on the first page)

* Wipe Dalvik again straight after that

I made sure that I used the right GAPPS as the previous one I used caused the black boot up screen, I am also on the LP bootloader, I have not upgraded mine to MM as there was no need to do so.

I have had others also re-flashing the stock ROM, doing the first initial boot, and then going back in and following the above procedure and that worked as well.

That is about as far as I can help on this one sadly, I am sure others will jump in and offer advice as well, but I don't think you were the only one to get the black screen boot, but I know it was resolved (To my knowledge)

Cheers,

David.
[Galaxy Note Pro 12.2 Android Development] thompatry:
I think there is some confusion on the difference between a bootloader and kernel. First let me say there is not Marshmallow bootloader for the SM-P900 (our device). There is only a Lollipop for it. The bootloader just tells device where to go to boot. It is where you see the screen Samsung Galaxy Note Pro 12.2. It is very minimal and basic for the initial device startup.

The kernel is what connects the hardware with the software. Right now the latest kernel is Marshmallow in the nightlies. These two are not really related to each other. The kernel is where all your drivers are located.

Let me know if this helps clear anything up.
[Galaxy Note Pro 12.2 Android Development] DGT79:
Nope im fine with that - though I already knew that :D
[Galaxy Note Pro 12.2 Android Development] Logan5:
Thanks for clarifying. So, RR has also a Lollipop bootloader, but an older one than this ROM ? Will RR boot on the new bootloader ? (in the case I have problem with this ROM, I would want to revert to RR without Odin manipulation, if possible). Thanks for all.
[Galaxy Note Pro 12.2 Android Development] thompatry:
Yes. RR will boot on the Lollipop bootloader.
[Galaxy Note Pro 12.2 Android Development] ElsaReyes:
Um, I clicked the google drive link, and the last one uploaded that I see is from the 15th. Where's the 29th one?
[Galaxy Note Pro 12.2 Android Development] Ausraster:
Yeah, I (and some other guys) had the same problem. Just open the Google Drive folder in an incognito-tab, then you will see the other versions too. :)
[Galaxy Note Pro 12.2 Android Development] ElsaReyes:
Is anyone elses tablet overheating since the update?
[Galaxy Note Pro 12.2 Android Development] thompatry:
Did you do a clean flash? Also there are more governors installed so you can play around with those.
[Galaxy Note Pro 12.2 Android Development] ElsaReyes:
It would work better that way?

Also I have no idea what governors are.
[Galaxy Note Pro 12.2 Android Development] 00bofh:
I'll second the heat /battery issue. I'm seeing the "Android OS" process take 80-90% of overall processor and battery is holding at 48/50 C. All background apps have been cleared /killed, cache has been cleared and tablet has been rebooted.

Still holding at OS consuming the processor and battery "hotter" than usual...

Battery life is down with this build as well - getting maybe 8-9 hours of light (web browsing mainly) use versus prior build at 12+ hours.

Ah, the joys of Beta! :)
[Galaxy Note Pro 12.2 Android Development] DGT79:
Those with heat issues, have you tried a clean install? If not try it, make sure you go into advanced wipe and totally wipe the system (Use TWRP to backup your data first if you want a backup) and then give it about 24 hours for it to settle down, as the Android OS is quite active after a fresh install.

I would be interested to know how it goes after that, as I had similar heat issues, followed [MENTION=4817899]thompatry[/MENTION] advice as I have stated above and the issues just went away, not to mention the system ran heaps better, I only dirty flash to test things and stability issues, but where possible now I wipe the entire system and start from scratch and then use TWRP to restore the data.

Cheers,

David.
[Galaxy Note Pro 12.2 Android Development] Yemble:
I concur.

Although a dirty flash worked initially for me, it did not resolve my WiFi performance issue. A factory reset sorted it out for me, after which I just needed to restore my user apps (note not system apps) from a Titanium backup.

Absolutely no overheating issues for me and battery consumption seems pretty good.
[Galaxy Note Pro 12.2 Android Development] 00bofh:
Indeed yes.

Wiped it down to it's socks (so to speak). Factory reset, wiped Dalvik, Cache, System and Data. Formatted Data. Rebooted back into TWRP and re-formatted Dalvik, cache, system and data.

Installed from scratch using 09/29 build and OpenGapps Mini.

Installed Chainfire root, ROM Manager and 3C Toolbox.

Charged overnight to 100%

Android system is my #1 consumer - 4860mAh out of 4940mAh overall use in a 4 hour period this morning.

Battery temp running in the high 40's centigrade.

ROM Manager was used to set the CPU Governor to "ondemand" and stats were reset about lunchtime and factory charger with new USB 3.0 cable connected. (Note: with charger connected the system is still "draining" at 1200-1300 mA per hour.)

Consumption has stayed consistent for Android System (3809 mAh out of 3855mAh overall since reset), but temp has at least dropped to the mid 40's.

Activities during the day have been web-browsing (sporadic) and document reading with MuPDF (sporadic).

No gaming, etc.
[Galaxy Note Pro 12.2 Android Development] Yemble:
You really do not require either of these on a CM13 mod !

Perhaps this is your underlying issue.

My temps are typically 28 deg C

Suggest you install ForceDoze to get most services sleeping as soon as the screen turns off.
[Galaxy Note Pro 12.2 Android Development] thompatry:
I agree with this statement. I don't even use force doze
[Galaxy Note Pro 12.2 Android Development] ElsaReyes:
I'm hoping someone can help me with this. But I recently got a otg adapter, and it's not working right on my tablet. And the only thing I can figure is it's the cm13 rom as my phone which has the stock rom it works fine.

Is there anything I can do to get it working? I seriously do not want to go back to stock but I need this thing to work.
[Galaxy Note Pro 12.2 Android Development] Yemble:
I have a USB-3 OTG adapter which I use to tether my Sony A77ii camera to my tablet. I use the RCCDroid app to control the camera functions on the tablet and also to display a live view from the camera sensor.

This is quite a sophisticated two-way data transfer between the two devices over the OTG interface, which proves that there is nothing wrong with this mod with regard to OTG functionality.

Have you enabled USB Debugging in Developer Options?
[Galaxy Note Pro 12.2 Android Development] jmase:
CM13 does handle USB OTG a bit strange. I have a Mi USB stick with combined micro and full USB. When I insert the stick CM13 mounts it and allows me to access the stick from the USB status icon (status bar icon). No other app can see the files on the stick (tries ES and Ghost Commander).

/Martin
[Galaxy Note Pro 12.2 Android Development] Tonv:
I just tried several USB sticks and several OTG cables, including one of those reversible devices that can hold a (micro)SD card and with a full and micro USB connector on each side: my conclusion is that OTG works fine, all NTFS and FAT32 sticks are mounted and viewable from ES File Explorer, exFAT however doesn't seem to work (but as long as the other 2 are working all is well for me :) )

btw, I'm on the latest CM build, 29-9 and very pleased with it, no bugs so far, and casting to Chromecast key now works for both audio and video (I had a problem with video in an older version...)
[Galaxy Note Pro 12.2 Android Development] thools60:
Yep, me too. All is well:good:
[Galaxy Note Pro 12.2 Android Development] thompatry:
Hey everyone. Sorry I have been super responsive but here is a new update plus some extra stuff at the end. I still cannot spoil the exciting news yet (Its not N but read further) since it is not ready for release but I promise, well worth the wait. :)

Changes

The usual CM update such as the October Security Patch

Enabled tablet mode for the Trebuchet launcher

Fixed some doze settings. This should help with battery life.

Here is the new nightly :) Link Enjoy

One last thing, here is a teaser for you. Link

No it is not ready for testing or for the public to use yet, a lot of things are still broke. I will not release it till I get to a point I would consider it stable and working.
[Galaxy Note Pro 12.2 Android Development] Mr Creosote:
hi thompatry, I've been following this thread since the start, thanks for all the work you've put into supporting this tablet, I'm thinking I'm going to flash this rom tomorrow.

aside from the issues with some bluetooth keyboards, which I don't use, are there any advantages to sticking with your final CM 12.1 build over this one? is battery life fairly similar?
[Galaxy Note Pro 12.2 Android Development] thompatry:
This ROM has the latest security patches from Google and Cyanogenmod. Also, it has app level permissions, as do all MM ROMs do. I personally think the CM-13.0 ROM is faster. The battery life I think is similar. The one last thing is that I no longer put out builds for CM-13.0.
[Galaxy Note Pro 12.2 Android Development] ReyStunner:
Im having some video playback issues with the 9/29 build on multiple steaming apps where the video stops playback and gives error. Outside of that no major issues to report.
[Galaxy Note Pro 12.2 Android Development] Yemble:
IMHO, the CM13 ROM is much better than the CM12.1 ROM. It is fully functional, stable, supported, up to date and runs smoothly. You really should upgrade!

---------- Post added at 01:28 PM ---------- Previous post was at 12:51 PM ----------

I see that Valera is already off and running with Nougat on his P905 :D

Looks like I'll be pioneering Nougat on my P900 rather than my Moto X Force. I'm really looking forward to a decent implementation of multi-windows :good:
[Galaxy Note Pro 12.2 Android Development] Mr Creosote:
excellent, thanks! downloading it just now :D though it'll probably take me all day sorting out all the unsorted comics in my download folder before I can format and do a clean install :)
[Galaxy Note Pro 12.2 Android Development] Ausraster:
If you just do a factory reset in TWRP, your download folder won't be touched. So don't worry about that.
[Galaxy Note Pro 12.2 Android Development] FileCity:
Thank you very much for this...

I have access to some P900 so if I find something I will report it.

A new life for a great device...
[Galaxy Note Pro 12.2 Android Development] Mr Creosote:
how long should i expect the screen to be black for after the samsung logo, on first boot? it's been black a long time, compared to what i remember from flashing previous roms.

i've redownloaded the rom and gapps in case the previous downloads were corrupt, going to try them now. i have the version of twrp installed that i previously used to flash CM 12.1, so i guess i have the right bootloader?
[Galaxy Note Pro 12.2 Android Development] thompatry:
If it is still black, you need to update your bootloader. You are still probably on the KK bootloader.
[Galaxy Note Pro 12.2 Android Development] Yemble:
Definitely!

Get the bootloader from the same place as you downloaded the ROM.

Incidentally, I upgraded from the previous CM13 ROM version via a dirty flash. This worked without issue and MOST IMPORTANTLY has had no detremental impact upon WiFi performance.
[Galaxy Note Pro 12.2 Android Development] Mr Creosote:
ok, i see what i've done. i was being presumptuous and thinking that because i had lollipop on it, i would've had a lollipop bootloader. evidently not. cheers folks!

---------- Post added at 07:20 PM ---------- Previous post was at 06:41 PM ----------

Yep, updated the bootloader and it's all working now, rom looks good so far, cheers folks!
[Galaxy Note Pro 12.2 Android Development] fsad:
Great news about CM14, thompatry. I'm very excited to try that build when it's ready.

Been following this thread closely, though I stopped flashing ROMs after I experienced those stylus-related reboots with some of the builds last month; restored the 20160817 build and things have been stable. For those on the newer builds, were those problems fixed?

One thing I thought I'd mention for those experiencing temperature problems: in my case, I noticed that was because of /system/bin/mediaserver, which indexes media files and is presumably getting stuck somewhere, keeping the processor frequencies high. When it happens, you can kill that process with "Simple System Monitor" (or another app) to get the CPU usage back down.

I looked into issues with that process, and it was recommended to temporarily move media files off the system (trial and error) to figure out which files would be corrupt, but in my case, I've got a lot of files I need for courses so I can't easily do that. I wondered if there was a way to access a log or find some other way to figure out which file(s) the mediaserver process is struggling with. Any ideas?
[Galaxy Note Pro 12.2 Android Development] ElsaReyes:
I bring a gift to you all!

As I'm sure some of you know, I've been looking for a way to access files connected by OTG in any program, not just the cm file manager.

And I've found the solution on another forum site, and it works! I can now access things connected via OTG in any program. As long as it's formatted Fat32. Or Fat(Default).

Here's the process.

1: Enable Developer options

2: Enable root access and local Terminal

3: Open local Terminal

Type

su

and press enter

4: Type

sm set-force-adoptable true

Gotta ask, but should I make a thread for this?
[Galaxy Note Pro 12.2 Android Development] Yemble:
Actually, I am now going to retract that statement.

Although initially things looked fine after the dirty flash, the tablet locked up sometime afterwards during a PlayStore update session. I had to power cycle the device, but when it came back up, the WiFi performance was shafted (again). This is the third time that this scenario has played out with this ROM, following a dirty flash.

So I would now NOT recommend performing a dirty flash on a CM13 based ROM on the P900. This combination seems to introduce some level of corruption. :eek: Note that I have never experienced the same problem performing dirty flashes of CM13 on a Galaxy S5 phone.

A factory wipe, followed by a restore of the user apps from a Titanium backup fixes the issue.
[Galaxy Note Pro 12.2 Android Development] thompatry:
I find this interesting. I don't understand why this occurs. Did you clear your cache/dalvik caches between flashes?
[Galaxy Note Pro 12.2 Android Development] thompatry:
New nightly. Nothing major changed.

Changelog

Removed the AudioFX app since it causes more trouble than help

Added custom options for the home button and app switch button. You can find these settings under Buttons in the Settings menu.

Enjoy! Link
[Galaxy Note Pro 12.2 Android Development] Yemble:
By dirty flash, I mean just performing a standard install from TWRP without any cache wipes. This is the standard method for applying CM nightlies which I have been doing for many years now. This is the only CM based ROM that I have ever used (across a variety of devices) that develops issues following a dirty flash (minor/nightly) update. The fact that it has occurred three times on the trot now, convinces me that the only safe way to update this particular ROM involves a factory wipe.

Not really a problem, but still a bit of a PITA.
[Galaxy Note Pro 12.2 Android Development] thools60:
A Dirty flash includes wiping cache and dalvik.
[Galaxy Note Pro 12.2 Android Development] Yemble:
Before or after the ROM flash?

Can't say that I've ever noticed that step during a standard CM Updater (scripted) flash.
[Galaxy Note Pro 12.2 Android Development] thools60:
There's an old golden rule that says that you should wipe dalvik/cache three times, before and after a dirty flash. Whether that is useful or superstition, I don't know, but I've always done it. No problem on this ROM at least....I don't know... anyone else?
[Galaxy Note Pro 12.2 Android Development] Yemble:
Now you have just made me more sceptical :eek:
[Galaxy Note Pro 12.2 Android Development] thools60:
Well...what do you say [MENTION=4817899]thompatry[/MENTION] ?
[Galaxy Note Pro 12.2 Android Development] thompatry:
Since there are a lot of devices changes still occurring to help settle down some of the smaller issues, you will see issues like this. That is why I always recommend clean flash.
[Galaxy Note Pro 12.2 Android Development] thools60:
Yes. Well I ALWAYS flash clean when I update a ROM. But I was referring to the discussion we had. If you absolutely want to flash dirty, isn't it common procedure to always clean cache and dalvik before and after a flash? And three times too. When I first started to use custom ROM's many years ago, everybody was nagging about this three times wash. I just wondered if you know anything about this?

Oh! And thanks a million for your work. Rock solid if you ask me! :good: