yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Fankserver:
I can confirm your issue, i tested Apollo (fine) and Google Play Music (broken, will grep logs soon).

Did you installed via dirt flash or clean flash? Because i always used dirt flash since this ROM is released :)

Opened Issue #5 https://github.com/crpalmer/android_device_samsung_mondrianlte/issues/5
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] rnb5500:
Cool, now if I could only find a way to flip KNOX back since I already triggered it installing CM11.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] kurosawa79:
Think Crpalmer posted the following in wrong thread. New build fixes play issues:

New build: http://download.crpalmer.org/downloads/mondrianlte/cm-11-20140728-UNOFFICIAL-mondrianlte.zip

* Updated CM source as of about 18 hours ago

* New interactive governor frequency selection

* New hotplug driver, mpdecision was removed

* Other minor changes

The updated CM source should fix any play music (used it a lot on a phone today and just tested this build right now and it is working for me).
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
Oops!!! Thanks for catching that and reposting it in the right place!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Fankserver:
I can confirm the play issue is fixed
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] fdebef:
Can anyone advice? What is MPL Significant Motion under ANDROID OS processes? Something related to sensors? This seems to eat a fair bit of my battery capacity.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
Sounds like you may be one of the devices affected by a bug in

http://review.cyanogenmod.org/#/c/66657/

I'm not affected by this so I can't say for sure (no proximity sensor on sm-t320). According to what I read for the hammerhead, you can try disabling proximity wakeup in Settings >> Display and then reboot and it may work around the problem.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] fdebef:
I have never enabled this :(

True is, this is not the only one device where I experienced this with CM11, Xperia Z1 Compact or Xperia Z Tablet did that too, this does not seem to be an one device bug. I'll get back, currently I am resetting batterystats.bin, last night I got charged to only 46% ;)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] fdebef:
I've done further research in MPL significant motion process, which spent a lot of my battery.

I have always flashed CM11, Gapps 20140606, Face Unlock and Cerberus. After start I have restored cca 60 apps with TB. With this procedure on different devices (TM325, XPeria Z tablet) I had in Battery Monitor Widget process named MPL significant motion always running and spending cca 30% of battery consumption - even with system monitor I was not able to find, which application uses it.

So I have done clean install (CM11 + GAPPS) + battery monitor widget - everything was OK, normal consumption. After that I have restored all of my applications. And everything is also OK - I even do not see MPL significant motion in battery overview.

From these observations I draw a conclusion, that either Face Unlock or Cerberus was doing this. Inherently it appears to be Cerberus. Definitely nothing to do with crmpalmer's CM11 .
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] slowpoke97:
3G/H+ -> LTE handoff

I also confirm that audio playback using Google Play Music and Appolo works fine. Thanks again for the fix :)

I noticed a problem with 3G/H+ -> LTE handoff taking a long time. After entering an area with LTE coverage, it takes between 5 - 20 minutes until the tablet switches to LTE.

After it starts using LTE, if I switch on Airplane mode and then off again, it will take about 20 seconds until the tablet gets 3G/H+, then another ~5 minutes to switch to LTE. The preferred network type is set to GSM/WCDMA/LTE. If I set it to LTE only, I can't get any signal (waited for about 10 minutes).

The LTE signal strength is about -85 to -95dbm, ~47 asu when the tablet uses it. However, for 3G/H+, the value reported is very large, about +1800dbm, +1000asu. I checked from Settings -> About tablet and from an app called LTE Discovery, both of them reported the same value.

Could this large number be related to the handoff issue?

Handoff from LTE to 3G/H+ is working perfectly.

On stock ROM, the tablet will use LTE in a few seconds after I switch off airplane mode. Handoff from 3G/H+ to LTE also felt much faster, although I didn't measure exactly.

Do you have any idea about this?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Fankserver:
I supposed this LTE issue on my tablet too
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
Can you send me a radio log of the handoff? Please do so via PM as the radio log likely contains sensitive info.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Fankserver:
PM sended, with logs
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
New build: http://download.crpalmer.org/downloads/mondrianlte/cm-11-20140730-UNOFFICIAL-mondrianlte.zip

* CM source updated as of about 8 hours ago

* More changes to the interactive governor

* Removed mpdecision and replaced it with a new kernel model to handle bringing cores online and taking them offline

(no changes for the LTE, haven't even had a chance to look a the log yet).
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] kurosawa79:
Strange. My LTE lock is immediate after airplane mode.

Haven't checked the handoff yet but will report back when I've observed it.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] kurosawa79:
I have n t noticed any lte issues after a day but Apollo is acting weird. Sound distortion and crashes after playing music for 5 mins. Distortion on n7 player too, no crashes yet.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] slowpoke97:
Apollo is fine for me but I am still on the previous build.

I have been observing LTE handoff for a while and it always happens after 5 minutes except for one time when it switches immediately.

From airplane mode it always takes more than 5 minutes to get LTE.

I wonder if it is related to signal strength. What's the LTE signal strength that you get in dbm? Is your 3G/H+ signal strengh also get reported as >1000 dbm?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
[MENTION=5910245]Fankserver[/MENTION], [MENTION=5966098]slowpoke97[/MENTION]: Thanks for sending me logs. Can you try this version

Test build

and let me know:

* Is the 3g signal strength right (or at least looks believable?)

* Is the LTE signal strength right (or at least looks believable?)

* Does the LTE handoff work better or are you still seeing slow handoffs?

* Any other problems that you may notice.

The last one is important. Ethan Chen is working on cleaning up all the CM Samsung devices and this build is also testing what he's been working on and how I've applying similar cleanups to the mondrianlte. If there are problems, I'd like to know early on.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] slowpoke97:
Thanks for the testing build!

I got no signal after dirty flashing this build. Does dirty/clean flash matter? Sent logs via PM.

Meanwhile I went back to 07/30 build and signal is back. I also tested Apollo to play two songs and didn't notice anything strange.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
At the very least (aka, there may be more problems) I made a stupid mistake when moving my changes over the mondrianlte... Can you either just add this line to your /system/build.prop:

ro.telephony.ril_class=TabproLteRIL

(as I said, oops!) or I pushed up a new build to the same URL which has that fix and also has slightly newer upstream code (I updated the code about 8 hours ago) if you want to download and install that instead.

Thanks for testing. Doing this blind really is a pain for both of us!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Fankserver:
Who the filesystem is in read only mounted?

EDIT: never mind i used the latest build :P
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Fankserver:
For me the LTE issue is fixed, its much better no dbm > 1000 anymore.

But i got huge problems with my GPS.

1. Sometimes i got long "acquire position"

http://1drv.ms/1rXhjOx

http://1drv.ms/1rXhqtv

http://1drv.ms/1rXhp8V

http://1drv.ms/1rXh1HC

2. GPS crashes sometimes. (will collect logs next crash)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] house66:
I have problems with GPS

Copilot does not detect my location

Weather Pro does not detect my location
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Fankserver:
Try GPS Status
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] house66:
thanks, it solved my problem ;)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Fankserver:
GPS logs [MENTION=3857343]crpalmer[/MENTION]:

2014-08-03_13.21

08-03 13:21:48.953 D/AndroidRuntime( 7024): Shutting down VM

GPS Status closed because the GPS driver is unavailable

2014-08-03_16.05

08-03 16:05:24.902 D/AndroidRuntime( 7737): Shutting down VM

GPS Status closed because the GPS driver is unavailable

I also find out that you need to download new A-GPS data very often to make GPS work correctly.

BTW i often see (from 16.05 log):

08-03 16:04:16.882 I/PowerHAL( 696): crpalmer: ignoring interaction

08-03 16:04:16.882 I/PowerHAL( 696): crpalmer: ignoring interaction

08-03 16:04:16.892 I/PowerHAL( 696): crpalmer: ignoring interaction

08-03 16:04:16.892 I/PowerHAL( 696): crpalmer: ignoring interaction

08-03 16:04:16.912 I/PowerHAL( 696): crpalmer: ignoring interaction

08-03 16:04:16.912 I/PowerHAL( 696): crpalmer: ignoring interaction

08-03 16:04:16.922 I/PowerHAL( 696): crpalmer: ignoring interaction

08-03 16:04:16.922 I/PowerHAL( 696): crpalmer: ignoring interaction

[MENTION=3857343]crpalmer[/MENTION] could you please explain what this is?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] fdebef:
Is it line with LCD Density missing in 20140802 build in build.prop? When I installed this (both dirty & wipe), my keyboard was very big, I had phone layout,...
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] amjadnezam:
Hi : i use build 02014/07/26 for a six Day On SMT-325 And Install Many apps . It's Work Perfect and i Must Say : I Love It And Thank's For Hard Work.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Zagzagel:
I have the same problem with the 20140802 build. The keyboard expands beyond the edges of the screen making it unusable, and some widgets have unusually large text.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] peshkata:
The Spotify app seems not to be working, it doesn't produce any sound (either with headphones or speakers), can anybody confirm ?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] sir_wesley:
Hi man I am trying to root it with towelroot but there is no chance :) at least not for me. It is saying that my phone is not supported, so tried put that 3 clicks on wellcome to towelrooot v3 and put code for new samsung but nothing happned... can you please explain how U did that
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
I don't see anything obvious in the logs and GPS seems to be working well on both my mondrianwifi and picassolte.

I did get an update to GPS status yesterday which includes a crash on older devices (maybe it is a more general problem?). Can you try updating GPS status and see if it seems to work any better?

The log message with my name in it is just debugging that I accidentally left in there. It isn't anything to worry about and should be gone in the next build.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
Yes, and, that should be fixed now.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] darrenxes:
Hi,

I have limited knowledge.

As attached my phone info

This link shd be helpful.

http://xdaforums.com/showthread.php?t=2786800
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] sir_wesley:
Thanks after instaling proper kernel I could use Tawelroot so Thanks!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
Manually releasing builds is enough of a pain that I broke down and cobbled together some equipment from my basement and built a very second (third? fourth?) rate build server to build nightly releases for you.

There may be some bumps in the next few days that I have to iron out and at some point the build server may go up in flames but, until then, I won't be posting new builds with specific hand crafted (and incomplete and wrong) changelogs.

Instead, you should be able to update as frequently as you want and all upstream CM changes should be included each night along with any device specific changes. Here's the information I posted in the second post to explain the nightlies:

Nightlies:

Download:

SM-T325 (mondrianlte) nightlies folder

Known Issues:

* most of the bugs on JIRA for mondrianwifi.

Changelogs:

* Main CM changes (ignore device_samsung_mondrianwifi): cmxlog for mondrianwifi

* Tabpro common device changes

* Tabpro common vendor blob changes

* Mondrianlte specific device changes

The changelog contains all changes made to that branch. Each nightly will be tagged and looks like:

7cd5c0b (HEAD, tag: nightly-20140808, m/cm-11.0, github/cm-11.0) mondrianwifi: init: Configure minimum GPU speed

The tag(s) that say "nightly-xxxxxxx" indicate that all changes from this commit down are in that nightly. Therefore, you can see what has changed since a specific version by looking for all entries between your current night's tag and the one that you are going to download and install.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] peshkata:
Amazing. Thank you very much !
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] NewshadowNet:
Great work! Thanks a lot!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] sir_wesley:
Thanks man superb :) anyone who tried new nightlies?

---------- Post added at 12:47 AM ---------- Previous post was at 12:12 AM ----------

After I installed the way it was described I thought everything is ok, but now I installed phone info *Samsung* and I see my Knox Warranty Void: 0x1 so probably I am done with warranty repair if something happened ... :confused:
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] fdebef:
What I have read about Knox, you can root without triggering it, but installation of custom non-Samsung ROM will trigger it always.

But do not matter - I had several tablets and many phones and never needed warranty repair.

New nightlies are great! Found no bug, in energy saving mode ultra low consumption (less then 1% / hour in standby), average 25mA consumption.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] micmars:
Yes, I concur. I just installed it last night, and I am thoroughly impressed at the speed and stability of this build (August 16).

It boggles the mind that Samsung went so far out of their way to remove features from the device (full screen art on the lock screen). Just insanity.

(I meant to put this in the T-320 thread, my apologies).
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] VeEuzUKY:
Hi guys.

I just buy a Tab Pro 8.4 LTE today and immediately need to get rid of the stock ROM. Its sheer misery. On all my other hardware Ive always used CM so I will not even bother trying other ROMs and want jump straight to this. I only have only question as I am yet to start flashing the Tab.. I see a couple or recovery options available.. can you guys advise my what works and and the build is best to flash this ROM's zip, TWRP or CWM?

Thanks much and cant wait to try CM11 on the Pro 8.4. Thanks for all the hard work on this as always!

Cheers:)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] darrenxes:
Not in my case. I am unsure why too.

See attached pictures. The knoix is not triggered, I am using CyanogenMod.

The method I use is towelroot, flashify, twrp and cyanogen built
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] fdebef:
Hmm, interesting. Does it relate to root method? Maybe

triggered knox already within root process?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] geogetski666:
my knox got triggered after i flashed twrp but when i first rooted it it didnt trigger knox don't know how darrenxes tab pro didnt trigger lucky for him :))
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] sir_wesley:
Actually I think the knox was triggered after I flashed CM because it is showing knox after every restart in left top corner and it showing:

KERNEL IS NOT SEANDROID ENFORCING

SET WARRANTY BIT : KERNEL

So I guess it is because of not original kernel. I think I didnt have knox triggered after all the steps till installing CM but also I am not so sure now .... And I fallowed every single steps from darrenxes even with new original kernel from other country and it was working "well" for me. But I dont care about some knox when it will be something broken on phone and I will have to pay some huge amount for non warranty repair I will just buy something else instead :P It was not cheap device but till now is working so much better than stupid ROM from samsung so definitely WORTHY!!! :good: so BIG THANKS TO CRPALMER again :)

PS: downloading Nightly from 19.08. :victory:

---------- Post added 20th August 2014 at 12:11 AM ---------- Previous post was 19th August 2014 at 11:57 PM ----------

Ok now when I am thinking probably I had maybe newer kernel than what was necessary for using towelroot so I read somewhere that not only non original rom and kernel will trigger knox but also older versions of original flashing trough newer original.... so I have no idea where is truth now :) As I told I didnt check the knox after every single step coz I thought it is without problem when somebody put it here on this page with picture of knox 0x0 but as I said it is not his fault ofc he had probably older device or not updated like I had.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] fdebef:
It is soooo sad, this ROM is so trouble free, we have nothing to discuss.

crmpalmer, we are still here, keep up the good work!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Alex1911:
Kernel-Features

[MENTION=3857343]crpalmer[/MENTION]

Hi,

Is there a possibility to receive Kernel-Features like Undervolt and Overclock ?

Best Regard's

Alex1911
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
Well, I'm working hard lately to try to give you things to talk about! Hopefully in about 2 weeks I'll have a brand spanking new kernel full of new bugs to break up the monotony....
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
CM practices encourage developers to keep within the hardware specs (stability and risk of hardware damage being big considerations). I tend to agree and stick with that for "official" builds.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] sir_wesley:
Noooooooo :laugh: I like monotony where everything is working well and fast and smooth but if the new kernel will have less consumption and maybe also support of touching buttons blinking when U got SMS or missed call I would like to have features like that :good: and big thanks man for your excelent work! Keep up :victory:
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] coljuay:
battery issues

So far, the rom has been great! But I do have some issues with the battery. After a few days, suddenly the charging became very slow. Over 5 hours using the original samsung charger and cable and it's not even 40% charged. I used the tablet for 10mins, low battery and it shuts down automatically.

Subsequently, after every restart, the battery will show 6-10%, again I was able to use for maybe 5-10mins then it shuts down but I was again able to restart and use it again. I am suspecting some sort of battery calibration error.

Any advises and suggestions? I doubt it is cyanogen mod related but just hope you guys can help.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] kurosawa79:
That sounds like a dying or faulty battery to me...
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] sir_wesley:
Exactly this I had on Original rom and I hoped with switching to CM it will fix the problem and it didnt. I bought new charger with new cable and also same result. So what I did was almost completly drain battery like 1% and turn off device than I plug it into the computer USB and let it charge very slowly trought computer and it was working for me it charge to 100% and was working for a while, than it happend one more time that regular charger wasnt able to charged fully so I again charged it turned off with computer USB and again it helped. And now I dont have problem with it anymore it still working well for more than month. And I am almost every day connected to computer usb at work so always very slow and quality charging. But the TAB easilie hold battery with CM trough weekend so from friday till monday no problemo.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Fankserver:
Beware!

I flashed the latest rom via TWRP, and i left TWRP over the night.

Now my tabled is ****ed, if i press the power button i shows me Samsung .... for about 1sec while the monitor is flickering, after the 1 sec it turn off.

I'm unable to boot in in any option (normal, recovery or download).
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
Does twrp charge your battery? Maybe your battery is almost dead? Try leaving it plugged in to a charger for awhile?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Fankserver:
Thanks for the info, yea TWRP completly drained the battery i charged it over the night.

Now everything is working again fine, thanks :)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] rafto:
Call recording

Hi

As we know:

"Starting from CM 11 (any nightly build after August 14) we can enable calls recording".

I tried many ways to enable this in this ROM like:

a) bulid.prop change:

persist.call_recording.enabled=true

persist.call_recording.src=1

b) Dialer.apk patching:

\res\values\bools.xml

<bool name="call_recording_enabled">true</bool>

\res\values-mcc260\bools.xml

<bool name="call_recording_enabled">true</bool>

this way I cannot update Dialer.apk (signature verification failed)

c) I don't want use XPOSED module:EnableCMCallRecording

http://xdaforums.com/xposed/modules/xposed-enablecmcallrecording-t2856248

Question to ROM creator ..there was any build with Call Recording enabled if not there are any plans ?

Please help.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] crpalmer:
Last I heard was that call recording was not a support CM feature yet. It was partially added and then people started talking about it and people figured out how to enable it when it wasn't supposed to be enabled and then the hooks to enable it like that were removed.

When it is officially supported, I'll look into making the audio sub-system support it.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] rafto:
Thank you for answer. Could you post info after this feature will be accessible in your rom?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] sir_wesley:
Hi guys, anybody problem with echo when calling with somebody? Some of my friends told me that they hear echo in the phone. Dunno if it is provider error or some phone bug. If I get it right they are hearing themselfs in our connection....like when phone is sending not only my voice but also their back to them.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] sir_wesley:
i tried nightly 16 but it was not working properly lot of restarts just like that one time it slept so hard I had to hold on/off button for 25s to wake it up, I thought its already lost case. So back to 9 where lot of my friends saying its echo when they speak with me.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Alexey71:
Hi, Can do cm11 for sm-t321?)):fingers-crossed:
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Zakanam:
Does anyone's IR blaster work? I downloaded an IR remote app and it doesn't work?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] arrrghhh:
crpalmer has answered this in another thread.

See here.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] Zakanam:
Sorry ;_; and thanks you
[Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De] cognitior:
Waiting for that much:cyclops: