yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] dunktank11:
Black Screen

Hello,

I was updating from CM12.1

I installed the BL with Odin and the new TWRP you supplied. Odin said everything Passed. I then Wiped Cache/Data/System. Installed the latest CM13 Nightly and Gapps. When I reboot the tablet it now sits at a Black Screen for the past 15-20 minutes. Any ideas?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] mikebetz42:
If you read the first post with the ROM info....

Bootloader Information

You need to make sure you have a Lollipop bootloader installed or else your device won't boot. Here you can go grab the latest bootloader and odin and flash it in download mode. Read all the steps before you do this.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] dunktank11:
I did.. I installed BL_T900XARBOJ1.tar with Odin just like i explained. Is this not correct?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] mikebetz42:
My apologies then. Have you tried to wipe the device then install the rom and gapps?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] dunktank11:
Yes, I installed the BootLoader with Odin and the new TWRP v3 that was supplied. Odin said everything Passed. I then Wiped Cache/Data/System. Installed the latest CM13 Nightly and Gapps everything installed fine. I hit reboot system and I have had nothing but a black screen. I don't understand..

I can make a video if needed to show the process im going through.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] mikebetz42:
Can you boot into the TWRP recovery?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] dunktank11:
Yes, I can.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] mikebetz42:
I had the same problem, but flashing the bootloader solved my issue.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] dunktank11:
Here I attached a picture.. Odin says the BL install Passed.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] dunktank11:
Well I managed to get it running finally but my touch screen does not work at all. Not in CM13 or in TWRP :(

I eventually held down the Power button and volume down to go right into download mode. Then Flashed the Bootloader again instead of loading into download mode through TWRP and it worked.

swear if its not one problem its another... could it be something with the Kernel or is there another Bootloader i can try?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] bam099:
My IR (infrared) blaster is not working with the ROM, is anyone else noticing that? Everything else seems to be working well! Thanks for the hard work.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] midimench:
Be sure to wipe 5 different things when you do the install for the 1st time. Dalvik/ART Cache, Cache, Data, Internal Storage and System leaving the Micro SDCard intact. For updates after the original I wipe just the Dalvik and Cache leaving the rest alone. Prior to that I verified the Lollipop Bootloader using an app called Phone Info before I got busy

Sent from my Samsung Tab Pro
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] vochong:
IR does not work in Oct 19 2016 Build

When using ODIN to flash the bootloader, you must use the Power + Vol Dn combination get into the Download mode. Accessing the Download mode through any other way (e.g. through TWRP or via App reboot to Download mode etc.) and then flashing the bootloader using ODIN will lead to unpredictable results.

Thanks,

Eric

---------- Post added at 04:06 AM ---------- Previous post was at 04:04 AM ----------

I can confirm that IR does not work with this ROM (Oct 19 2016).

Thanks,

Eric
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] dunktank11:
cm13 and Recovery no touch

So iv'e been reading and on Github other people are having my same problem in Both Recovery and CM13. Although its not for this tablet they are having the same problem with the screen becoming unresponsive. A few people said It's definitely a kernel issue as it happens in both system and recovery. So I thank you for your hard work on this project but until someone figures out a fix. I'm stuck with a paper weight as I cant even use TWRP if the touch screen is not working. :(

---------- Post added at 12:11 AM ---------- Previous post was at 12:08 AM ----------

Yeah missed this part.. Just noticed it said Power and Volume Down. :eek:
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] bam099:
Bummer, thanks for confirming. I'm on the same 10.19.16 build. Does anyone know of this is something being worked on? The IR is one of the greatest parts of this device (for me at least).
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] mikebetz42:
You can try flashing the stock rom from Odin and start from scratch.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
It's important to me to use this as a WiFi phone without cell service using Google Voice. I have another WiFi phone without cell service and I use Hangouts Dialer to make and receive calls and I use Hangouts and configure it to send and receive SMS. I'm sure this is no surprise to anyone. However, I have noted that although you can make calls from the Hangouts Dialer on the T900, it force closes when you try to send an SMS. If anybody cares, a work around is to use the good old Google Voice App to send and receive SMS. Really, this was the original way to do it but the slick way that hangouts handles SMS has made the GV App unnecessary. So now I am texting with GV App and calling with Hangouts dialer and again have a fully functional WiFi phone. It is working well this way.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
Viper4Android works with a SELinux Enforcing. Do some Googling and make sure you have the right version. I will not disable Enforcing since it is in your best interest from a security aspect. I am not going to discuss this mod any further since I do not support mods.

I know the IR is currently broken on this latest build, but it will be fixed on the next.

Look forward to a new build coming soon guys! A lot of changes coming in. Sorry I disappeared. I have been working close to 60 hour weeks so it is a bit hard to get to android. Thank you for all the great feedback.

I have been getting a lot fo questions on when I am going to start on CM-14. I have technically been working on it. The more stable I get CM-13.0, these changes will pass on to CM-14. If not, you would still be seeing the same issues in both versions. So bear with me. I am close to having a stable, fully functioning CM-13.0.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
Hi ThomPatry,

Iam with you :) Would like to have a stable Tablet (with CM13) rather than the newest CM14 with many bugs...

I will wait a a complete stable CM13 and maybe later a stable CM14.

This CM13 is working for me better than the last CM12 - so its fine for me.

Could you please recheck the volume-slider? I got some state with the newest rom and the volume-hardware key did only work after firstly sliding volume via touchscreen (as a other member did write some messages ago....)

Do you got this in mind or should it be already corrected? Or is it on the list for later?

Have a nice weekend :)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
New Build

As promised here is the new build. The list of the changes are below. It captures 99% of the changes but I might have shorten some of it since there has been a lot that changed.

As always feedback please. I can't make a better ROM without your feedback!

Enjoy! Link

Changelog

Changed the lock screen so it no longer says slowly charging

Updated the camera to the MM blobs (Camera is a lot faster and the picture quality is better)

Cleaned up the camera configs

Fix OTG permissions

Enabled multi-window by default

Enabled Samsung Bluetooth

Cleaned up the Bluetooth configs

Enabled multi-threaded decode for the boot animation

Fixed WiFi Display and allow it to display DRM content

Enabled extended file system support at the kernel level (NTFS and EXFAT)

Tuned the CPU/GPU for the interactive kernel (A lot of performance gain here)

Updated the audio to the i9500 hal

Updated the media profiles and codec MM

Fixed the IR blaster (Moved the initialization back to the on parameter in the ramdisk)

A lot of GPU/CPU performance tweaks from the kernel level

Updated various blobs at the vendor level to the MM version (Sound Effect, Sswap, Mobicore, Mfc_bin, libstagefright, scranton_RD)

Updated the rotation driver to MM version

Enable vibration strength control (You can find this in the sound settings)

Modified the Wolfson DAC settings (The sound should be a little bit louder. This is still a work in progress.)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] bam099:
Thank you so much for your hard work and great ROM, it is keeping my old tablet running well! Thank you for fixing IR, it is working perfectly now on the Nov 4 version.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
Many Thanks for the feature-full Update :good:

MM is MarshMallow :confused:!

Vendor Level is Samsung?

MM Version - is that Google MM or Samsung MM?

Was the former vendor Level a Lollipop blob?

I'll test the new ROM this evening ;)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
Yes MM is marshmallow. Technically our device is only supported up to Lollipop from Samsung but we share some common files with other devices that Samsung supports up to Marshmallow. So we are able to use those files.

Vendor level is the files that are already compiled by Samsung that we do not have the code or time to reverse engineer them. We end up copying them from a stock ROM and using them on our device without issue. For example the sensors driver. We do not have the source code for that so we use Samsung's version.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] vochong:
The Nov 4 2016 version is very good.

Thank you very much Tom!

Everything seems to work well so far. The following small bugs that people had previously reported are no longer observed:

- Live wallpaper crash

- Hot camera/LED area

- IR blaster not working

- Hangout SMS crash

- V4A can be made to work in SELinux Enforcing mode.

Not sure of the MM MIDI support that another member requested.

Best regards,

Eric
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] bertoxo:
Still can't use midi on this MM rom. :/

I think its don't even enabled in kernel, don't know why.

https://source.android.com/devices/audio/midi.html

https://source.android.com/devices/audio/midi_test.html
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] bertoxo:
I have another problem too: can't copy files from PC to device on usb, wtv internal or external sd. MTP enabled.

Strange thing is i can copy from device to PC, and create/rename files and folders inside the tablet window. Looks like write locked. :/
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
Thanks for the links. That is very helpful. I will dig into this issue some more.

Have you done a clean flash?

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

In other news, I have two exciting changes coming soon. Be patient and it will come. Not N yet but I am getting close.

As always, keep giving the great feedback.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] bertoxo:
Nop, just installed over. Don't want to install all apps again. Buts its strange either, naver happen to me with any dirty flashed rom.

Wtv i didn't tried this behavior with previous version, i think it was the 2nd release still with permissive selinux. Maybe it don't works too.

I'm using windows 10 now, will try with my old win 7 partition.

Maybe i should flash your fixed recovery, don't know. I'm still using the ordinary twrp 3.2.

__

EDIT: Solved. Bad usb cable. :p
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] mikebetz42:
Clock on my device is not working... it crashes. I had a clean install before this one, I just flashed on top of the last one. So if anyone can confirm if this is an issue or not an issue, I will wipe and re-install. The live wallpaper is still crashing for me as well. Leads me to believe I need to wipe, but want to make sure.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JCordero31:
I'm having issues with charging. I turned off my tablet around 3 am and put it to charge with a Motorola fast charger that's used for the nexus. Usually it charges my battery full in 2 hours tops while it's off and while it's on and being used it still charges it pretty good. Now with the 11-4 build its gets to 80 percent the I turns to slow charging. I tried the original charger for tab and it's even slower! From 80% to 100 it states it will take 2 hours to charge. I tried using ampere but it can't read the voltage even with full root access activated from developer options. This is on t900. Thanks for any advice [MENTION=3203856]thompa[/MENTION]ntry
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] bogus83:
I've been wanting this tablet for a long time and finally snagged one from eBay. I just read through this whole thread and wanted to say thanks for all of the work that's gone into this ROM. Can't wait to check it out when the tablet arrives... and I'm really looking forward to CM14! :)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thanatos74:
The download link for the latest builds seems to be broken...can someone provide a working link?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] mikebetz42:
Works for me.

https://drive.google.com/drive/folders/0BxqoBZiUYroBZHBnNlB4T0tXajQ?usp=sharing
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thanatos74:
Perfect! This one is working - thx for your help
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] bertoxo:
I must say that i'm having LOTS of random reboots, specially viewing movies. Since day one of this new ROM.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] KoningBas:
None of that on.my side. Watch movies with MX Pro daily without issues. All in all super stable and hardly any battery consumption when not used..
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] vochong:
I have the same experience: It's also perfectly stable for me and consumes very low battery consumption in sleep mode. In fact, this CM 13 ROM is MUCH better than its older sibling CM 12.1 ROM, as the CM 12.1 ROM had the high battery consumption problem due to the mediaserver process, even in sleep mode.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] Shveesus:
Hulu has stopped working

I'm not sure what the correlation is, but when I flashed the latest build hulu now will just sit at a black screen with the status bar and the network logo and it will not play video. It worked with the 10/19 build, but after the 11/04 build it's stopped. I tried uninstalling the app and installing it fresh from the playstore to no avail. I tried changing the app settings for quality also and had the same issue. Thanks for any help, hopefully it's not just me being dumb :p
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] bertoxo:
Which version of MX Pro are you using? Are you using in HW+ mode?

I've tried VLC player and no more crashes, MX reboots system always on around 17 minutes.

Now i'm trying BSplayer, same type crash after 17 minutes in HW mode but on SW mode so far so good going 30 minutes and on.

Remembered i've tried MX on SW mode and goes the same crash. Strange too.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] KoningBas:
Pure standard...latest version from the playstore and the codec from XDA. HW+ isn't checked.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
Hey Guys,

Long time no talk. Been busy with the holidays and works. I am working Nougat. So far it is looking good. I am working on getting it bug free before I release it. In other news, the next release will have some battery optimization in it. I have been testing it and it looks very promising. I will release that as soon as I can get something out that is ready for the public. Last item of business, the Exynos5420 Team has been working really hard developing a kernel auditor for the Exynos5420 devices. It going to awesome. It practically can control everything kernelwise. We are looking to release it sometime and December.

Alright that is all I got for right now. Keep giving the feedback and I will keep fixing items.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] KoningBas:
Nougat would be awesome!! But for now a big THANK YOU for your work to keep our device up to date. It's running way better compared to the standard Samsung software.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] citionecent:
thanks for your great work, donation on the way.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
Just a heads up... a bug that a end user discovered is the microphone does not work in some apps such as "Ok Google". Also I am looking into Hangout crashing when doing a video call. I will release a fix in the next built soon.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
I expect you already know this, but, at the risk of being a pest, you can't make a voice call not can you text from Google Voice either. Thanks for the great work, I'm having so much fun with this tablet.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] Masayoshi Tadokoro:
Great work!

I am very much looking forward to it â™ª
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] sincro:
My microphone works fine in all of the apps I've tried, including "Ok Google". The only problem that I have is with MHL output not working. A small price to pay for what is otherwise a fantastic ROM.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] stslimited84:
Is there a way to tether my phone to this tablet via usb? The nougat software no longer allows wifi hotspots via PDANET on 7.0 or later. I'd like to keep nougat on my phone but only if there is a way to tether it to this tablet via USB.

How can I do so?

Thanks for your hard work on this tablet software :D
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] bertoxo:
Thanks for new Kernel Adiutor. :)

Btw, i'm just narrowing my reboots issue to some bad xposed module, no problem so far.

--

Edit: just opened adiutor and it says that my kernel is outdated and cannot manage some properties. I've saw that no gpu controls are present too.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
This is my bad. I just got a tad excited on putting the app out.. I will get a new build out tomorrow.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] bertoxo:
The recents apps button doesn't suppose to back right to the last app instead of going to home screen?

Now when in app and go to recents apps view and touch again don't come back to the app but goes to desktop.

I think it is incorrect behavior, please correct it. :)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] Uldiniad:
[MENTION=4817899]thompatry[/MENTION] do you have experimental builds available for cm-14.1 somewhere? or you want to wait and post a link on this thread once you feel it is stable enough for everyone to use?

thank you for cm-13 btw, works like a charm
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
Hey Guys,

Sorry I haven't been around much. I have been working my tail off. 60 hours, 6 days a week. I have not forgotten about you guys. I have been diligently working on the "OK Google" and the hardware keys not working for volume unless you have some kind of media playing. Hopefully I can have a fix soon. Both those items are kind of difficult to wrap your head around why they are acting the way they are.

I know that kernel aduitor is probably complaining about the kernel version is not right so I will release a new CM-13.0 within the next day or so to fix this.

Last but not least, I have a little Christmas present for all of you so stay tuned. As always keep giving great feedback. I may not always reply, but I do read every single one of your posts.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
Hey Everyone,

Just a quick update, I have posted a new build today with usual updates. Nothing really changed on the device or kernel side of things. OK Google is still broken and the default audio levels are still not set. We are getting close to having them finalized.

New CM-13.0 nightly posted. Link

In other exciting news, I have released CM-14.1 for the T900 (v2awifi). Everything is super stable. I hope this is a good Christmas present! Here is the thread. Link

As always, keep giving the great feedback.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] c19932:
thank you.

I am getting stuck on the boot animation after flashing the latest 13.0. anyone else have this problem? had to revert to previous build
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
I just tested this and have not issue. Did you clean the cache after the install? Did you dirty flash? If so, please clean flash.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
didnt had any problems with the laste 13er build....but I got the TWRP from here and cleared - like allways - the cache and dalvik cache...
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] thompatry:
New build is posted. Not much changed since a lot of time went into fixing "OK Google". I will be supporting CM -> Lineage switch over. The new build can be dirty flash. Also the file will start with the words Lineage now. The new builds will be in the same place as the CM builds. Below are the changes.

Changelog

Ok Google audio fixed

General enhancements, improvements, and bug fixed from the Lineage Team

Enjoy! Link
[Galaxy Note 4 Q&A, Help & Troubleshooting] the_rev1995:
To start off i know nothing about repairing phones, i am more a windows pc person so it would be nice if replies could be in layman terms.

I bought a note 4 off ebay a year ago and in the last couple of months ive been getting a mmc read failed error. Yesterday it finally gave out and i think it is hard bricked, it will no longer boot and i cannot get into download mode, recovery mode, safe mode etc, or even any kind of response. I brought a spare battery and external charger to make sure it's not a faulty battery, still nothing with a fully charged new battery. When i plug it into the PC it shows up as Qualcomm HS-USB QDLoader 9008 in the device manager but will not show up in samsung kies or windows file explorer. I have not rooted it my self but i do not know whether it had been rooted before i got it.

I have been doing a bit of searching around and found usb jigs but from what ive found is that they will do nothing to help a hard brick, is this true or should i get one and test it anyway?
[Galaxy Note 4 Q&A, Help & Troubleshooting] vndkmr97:
Guess you need to follow this link
[Galaxy Note 4 Q&A, Help & Troubleshooting] the_rev1995:
Thanks, i'll give it a try and let you know if it worked.
[Wileyfox Swift] sambahb:
Hi,

I am currently running Cyanogen OS 13.0 and I have not managed to update via OTA and TWRP. After TWRP-Update the system just hangs on boot. OTA just does not do the update after reboot. I just keeps downloading the OTA-Update again and again which eats my data plan, unless I notice and stop it. I am looking for a clear instruction on how to flash the newest version directly via cable. I could not find one. Alternatively I would be happy if someone could show me a way to stop the repeating downloads of the latest OTA-version.

Thanks!
[Wileyfox Swift] Dior DNA:
basically you unzip the flashtool zip and do

fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img

if you want to keep data skip userdata (but clear dalvik cache in twrp)

if you want to keep twrp do not flash recovery
[Wileyfox Swift] Dior DNA:
You need to root MM with system less SuperSU ZIP version, I believe v2.65 onwards (v2.76 may be latest, you need to check). And each time you flash kernel (aka boot.img) again you need to root.