The links work fine on my tablet in gello. I am on the May 13 build. My Gello app was disabled before I opened the links so try disabling and enabling Gello if you haven't already.
[6.0.x] [SM-T320] CyanogenMod 13.0 Nightlies for the Tab Pro 8.4 Wifi (mondrianwifi)
- Thread starter crpalmer
- Start date
AlMunt, thanks for your reply! I'm on the May 13th build too. I tried disabling and enabling Gello, but it did not work for me.
Anyway, at least now I know the problem is definitely not related to the build.
I'm hoping there is an alternative to a factory default to fix this... Suggestions are welcome
On a wifi-only tablet, how would wifi tethering even work?
You don't have a cell network data connection to tether.
Anyway the solution is on page https://forum.xda-develope...6&postcount=53
Another one is that the screen mirroring does not work...
Any solution on that?
Screen mirroring works fine for me when I mirror to the windows 10 connect app.
Sent from my Galaxy Tab Pro 8.4 using XDA Labs
Tried to revitalize my old tablet by flashing Lineage OS 13.
But since this flash on my tab pro 8.4 wifi I'm having some crashes in games. games which used to work without issues on the (rooted) stock Samsung rom before.
I play mainly infinitode and plants vs zombies 2, both crash sometimes after a few minutes, sometimes after playing a few hours.
Things I've tried the last (3) weeks:
- Coming from stock rooted samsung rom, wiped all partitions in twrp then flashed the latest available lineage os nightly, twrp 3.1.1.0, gapps (stock) and su addon.
- Fully flashed last/newest available samsung stock rom for region NLD using ODIN, wiped all partitions in twrp then reflashed the latest available lineage os nightly, twrp 3.1.1.0, gapps (stock) and su addon.
- Re-seated old battery
- Bought new battery and installed it
- Flashed the newest adreno drivers zip posted in this thread: Adreno_Drivers(28.06.16)
- Always updated to the last available ota of lineage os
Issue remained after each step.
the logcat from a crash yesterday
Any help or tips? or am I doomed to go back to a samsung stock rom?
But since this flash on my tab pro 8.4 wifi I'm having some crashes in games. games which used to work without issues on the (rooted) stock Samsung rom before.
I play mainly infinitode and plants vs zombies 2, both crash sometimes after a few minutes, sometimes after playing a few hours.
Things I've tried the last (3) weeks:
- Coming from stock rooted samsung rom, wiped all partitions in twrp then flashed the latest available lineage os nightly, twrp 3.1.1.0, gapps (stock) and su addon.
- Fully flashed last/newest available samsung stock rom for region NLD using ODIN, wiped all partitions in twrp then reflashed the latest available lineage os nightly, twrp 3.1.1.0, gapps (stock) and su addon.
- Re-seated old battery
- Bought new battery and installed it
- Flashed the newest adreno drivers zip posted in this thread: Adreno_Drivers(28.06.16)
- Always updated to the last available ota of lineage os
Issue remained after each step.
the logcat from a crash yesterday
07-03 21:47:00.139 256 774 D AudioFlinger: mixer(0xb2cc0000) throttle end: throttle time(6)
07-03 21:47:02.042 1586 2064 I chatty : uid=10024(com.google.android.gms) lowpool[3] expire 6 lines
07-03 21:47:02.117 720 1610 D WifiService: releaseWifiLockLocked: WifiLock{NlpWifiLock type=2 binder=android.os.BinderProxy@f6a5c1d}
07-03 21:47:02.139 720 744 I chatty : uid=1000(system) android.bg expire 4 lines
07-03 21:47:02.140 720 1358 I chatty : uid=1000(system) Loc_hal_worker expire 6 lines
07-03 21:47:02.141 1826 18604 I chatty : uid=10024 com.google.android.gms.persistent expire 1 line
07-03 21:47:02.146 720 2030 I chatty : uid=1000(system) Loc_hal_worker expire 1 line
07-03 21:47:02.300 18369 18417 W Adreno-GSL: <gsl_ldd_control:477>: ioctl fd 19 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 34 Math result not representable
07-03 21:47:02.300 18369 18417 E Adreno-GSL: <gsl_umd_context_server_thread:745>: (0xaebabd00, 9) node 0x9616a618 ts: 11202 numibs: 2 returned -2
07-03 21:47:02.300 18369 18417 W Adreno-GSL: <gsl_ldd_control:477>: ioctl fd 19 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 34 Math result not representable
07-03 21:47:02.300 18369 18417 E Adreno-GSL: <gsl_umd_context_server_thread:745>: (0xaebabd00, 9) node 0x9616a618 ts: 11202 numibs: 2 returned -2
07-03 21:47:02.302 18369 18417 W Adreno-GSL: <gsl_ldd_control:477>: ioctl fd 19 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 34 Math result not representable
07-03 21:47:02.302 18369 18417 E Adreno-GSL: <gsl_umd_context_server_thread:745>: (0xaebabd00, 9) node 0x9616a618 ts: 11202 numibs: 2 returned -2
07-03 21:47:02.303 18369 18417 W Adreno-GSL: <gsl_ldd_control:477>: ioctl fd 19 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 34 Math result not representable
07-03 21:47:02.303 18369 18417 E Adreno-GSL: <gsl_umd_context_server_thread:745>: (0xaebabd00, 9) node 0x9616a618 ts: 11202 numibs: 2 returned -2
07-03 21:47:02.303 18369 18417 W Adreno-GSL: <gsl_ldd_control:477>: ioctl fd 19 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 34 Math result not representable
07-03 21:47:02.303 18369 18417 E Adreno-GSL: <gsl_umd_context_server_thread:745>: (0xaebabd00, 9) node 0x9616a618 ts: 11202 numibs: 2 returned -2
07-03 21:47:02.304 18369 18417 W Adreno-GSL: <gsl_ldd_control:477>: ioctl fd 19 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 34 Math result not representable
07-03 21:47:02.304 18369 18417 E Adreno-GSL: <gsl_umd_context_server_thread:745>: (0xaebabd00, 9) node 0x9616a618 ts: 11202 numibs: 2 returned -2
07-03 21:47:02.304 18369 18417 W Adreno-GSL: <gsl_ldd_control:477>: ioctl fd 19 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 34 Math result not representable
07-03 21:47:02.305 18369 18417 E Adreno-GSL: <gsl_umd_context_server_thread:745>: (0xaebabd00, 9) node 0x9616a618 ts: 11202 numibs: 2 returned -2
07-03 21:47:02.305 18369 18417 W Adreno-GSL: <gsl_ldd_control:477>: ioctl fd 19 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 34 Math result not representable
07-03 21:47:02.305 18369 18417 E Adreno-GSL: <gsl_umd_context_server_thread:745>: (0xaebabd00, 9) node 0x9616a618 ts: 11202 numibs: 2 returned -2
07-03 21:47:02.306 18369 18417 W Adreno-GSL: <gsl_ldd_control:477>: ioctl fd 19 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 34 Math result not representable
07-03 21:47:02.306 18369 18417 E Adreno-GSL: <gsl_umd_context_server_thread:745>: (0xaebabd00, 9) node 0x9616a618 ts: 11202 numibs: 2 returned -2
07-03 21:47:02.307 18369 18417 W Adreno-GSL: <gsl_ldd_control:477>: ioctl fd 19 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 34 Math result not representable
07-03 21:47:02.307 18369 18417 E Adreno-GSL: <gsl_umd_context_server_thread:745>: (0xaebabd00, 9) node 0x9616a618 ts: 11202 numibs: 2 returned -2
07-03 21:47:02.308 18369 18417 W Adreno-GSL: <gsl_ldd_control:477>: ioctl fd 19 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 34 Math result not representable
07-03 21:47:02.308 18369 18417 E Adreno-GSL: <gsl_umd_context_server_thread:745>: (0xaebabd00, 9) node 0x9616a618 ts: 11209 numibs: 2 returned -2
07-03 21:47:02.309 18369 18417 W Adreno-GSL: <gsl_ldd_control:477>: ioctl fd 19 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 34 Math result not representable
07-03 21:47:02.309 18369 18417 E Adreno-GSL: <gsl_umd_context_server_thread:745>: (0xaebabd00, 9) node 0x9616a618 ts: 0 numibs: 1636 returned -2
--------- beginning of crash
07-03 21:47:02.310 18369 18417 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 18417 (GLThread 604)
07-03 21:47:02.320 253 253 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
07-03 21:47:02.320 253 253 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
07-03 21:47:02.320 253 253 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
07-03 21:47:02.429 253 253 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-03 21:47:02.430 253 253 F DEBUG : LineageOS Version: '13.0-20170701-NIGHTLY-mondrianwifi'
07-03 21:47:02.430 253 253 F DEBUG : Build fingerprint: 'samsung/lineage_mondrianwifi/mondrianwifi:6.0.1/MOB31T/21f9339ec8:userdebug/release-keys'
07-03 21:47:02.430 253 253 F DEBUG : Revision: '0'
07-03 21:47:02.430 253 253 F DEBUG : ABI: 'arm'
07-03 21:47:02.431 253 253 F DEBUG : pid: 18369, tid: 18417, name: GLThread 604 >>> com.prineside.tdi <<<
07-03 21:47:02.431 253 253 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
07-03 21:47:02.471 253 253 F DEBUG : r0 00000000 r1 00000000 r2 00000000 r3 0000008b
07-03 21:47:02.471 253 253 F DEBUG : r4 9616a618 r5 9616a618 r6 00000001 r7 ab374828
07-03 21:47:02.471 253 253 F DEBUG : r8 ab371aee r9 ab364c78 sl ab374828 fp ab371b89
07-03 21:47:02.471 253 253 F DEBUG : ip 9d4c9018 sp 9c7bc8a0 lr ab356b2f pc ab356b3e cpsr 000f0030
07-03 21:47:02.489 253 253 F DEBUG :
07-03 21:47:02.489 253 253 F DEBUG : backtrace:
07-03 21:47:02.489 253 253 F DEBUG : #00 pc 0001db3e /system/vendor/lib/libgsl.so
07-03 21:47:02.490 253 253 F DEBUG : #01 pc 0001e14d /system/vendor/lib/libgsl.so
07-03 21:47:02.490 253 253 F DEBUG : #02 pc 0002226d /system/vendor/lib/libgsl.so (os_thread_launcher+20)
07-03 21:47:02.490 253 253 F DEBUG : #03 pc 0003febf /system/lib/libc.so (_ZL15__pthread_startPv+30)
07-03 21:47:02.490 253 253 F DEBUG : #04 pc 00019cdb /system/lib/libc.so (__start_thread+6)
07-03 21:47:03.049 253 253 W debuggerd: type=1400 audit(0.0:118940): avc: denied { read } for name="kgsl-3d0" dev="tmpfs" ino=7208 scontext=u:r:debuggerd:s0 tcontext=u
07-03 21:47:03.083 253 253 F DEBUG :
07-03 21:47:03.083 253 253 F DEBUG : Tombstone written to: /data/tombstones/tombstone_00
07-03 21:47:03.083 253 253 E DEBUG : AM write failed: Broken pipe
07-03 21:47:03.085 720 748 I BootReceiver: Copying /data/tombstones/tombstone_00 to DropBox (SYSTEM_TOMBSTONE)
07-03 21:47:03.087 720 18810 W ActivityManager: Force finishing activity com.prineside.tdi/.AndroidLauncher
07-03 21:47:03.130 720 811 I chatty : uid=1000(system) InputDispatcher expire 2 lines
07-03 21:47:03.138 720 743 I chatty : uid=1000(system) Binder_2 expire 1 line
07-03 21:47:03.138 720 1610 I WindowState: WIN DEATH: Window{819f1d5 u0 SurfaceView}
07-03 21:47:03.141 720 956 I WindowState: WIN DEATH: Window{6dbc30d u0 com.prineside.tdi/com.prineside.tdi.AndroidLauncher}
07-03 21:47:03.141 720 956 I chatty : uid=1000(system) Binder_4 expire 1 line
07-03 21:47:03.152 720 18810 W ActivityManager: Exception thrown during pause
07-03 21:47:03.152 720 18810 W ActivityManager: android.os.DeadObjectException
07-03 21:47:03.152 720 18810 W ActivityManager: at android.os.BinderProxy.transactNative(Native Method)
07-03 21:47:03.152 720 18810 W ActivityManager: at android.os.BinderProxy.transact(Binder.java:503)
07-03 21:47:03.152 720 18810 W ActivityManager: at android.app.ApplicationThreadProxy.schedulePauseActivity(ApplicationThreadNative.java:727)
07-03 21:47:03.152 720 18810 W ActivityManager: at com.android.server.am.ActivityStack.startPausingLocked(ActivityStack.java:879)
07-03 21:47:03.152 720 18810 W ActivityManager: at com.android.server.am.ActivityStack.finishActivityLocked(ActivityStack.java:2992)
07-03 21:47:03.152 720 18810 W ActivityManager: at com.android.server.am.ActivityStack.finishTopRunningActivityLocked(ActivityStack.java:2848)
07-03 21:47:03.152 720 18810 W ActivityManager: at com.android.server.am.ActivityStackSupervisor.finishTopRunningActivityLocked(ActivityStackSupervisor.java:2828)
07-03 21:47:03.152 720 18810 W ActivityManager: at com.android.server.am.ActivityManagerService.handleAppCrashLocked(ActivityManagerService.java:12494)
07-03 21:47:03.152 720 18810 W ActivityManager: at com.android.server.am.ActivityManagerService.makeAppCrashingLocked(ActivityManagerService.java:12365)
07-03 21:47:03.152 720 18810 W ActivityManager: at com.android.server.am.ActivityManagerService.crashApplication(ActivityManagerService.java:13081)
07-03 21:47:03.152 720 18810 W ActivityManager: at com.android.server.am.ActivityManagerService.handleApplicationCrashInner(ActivityManagerService.java:12586)
07-03 21:47:03.152 720 18810 W ActivityManager: at com.android.server.am.NativeCrashListener$NativeCrashReporter.run(NativeCrashListener.java:86)
07-03 21:47:03.158 265 265 I Zygote : Process 18369 exited due to signal (11)
07-03 21:47:03.188 720 1633 I ActivityManager: Process com.prineside.tdi (pid 18369) has died
07-03 21:47:03.188 720 1633 D ActivityManager: cleanUpApplicationRecord -- 18369
07-03 21:47:03.228 720 731 I chatty : uid=1000(system) HeapTaskDaemon expire 1 line
07-03 21:47:03.285 720 818 I chatty : uid=1000(system) RenderThread expire 2 lines
07-03 21:47:03.636 1586 2064 I chatty : uid=10024(com.google.android.gms) lowpool[3] expire 7 lines
07-03 21:47:04.039 18847 18847 I chatty : uid=10072(com.dolphin.browser.engine) toolbox expire 39 lines
07-03 21:47:04.998 720 2182 I chatty : uid=1000(system) Thread-258 expire 2 lines
07-03 21:47:05.232 720 743 W InputMethodManagerService: Got RemoteException sending setActive(false) notification to pid 18369 uid 10073
Any help or tips? or am I doomed to go back to a samsung stock rom?
Last edited:
Try Resurrection remix version 5.7.4. Wipe system, cache , data and format data. Be sure to format data. Works great on my Smt320.
Sent from my SM-T320 using XDA Free mobile app
Sent from my SM-T320 using XDA Free mobile app
End of support?
No more builds for mondrianwifi: https://review.lineageos.org/#/c/179626/
Missing CVE patches are the reason. It's a pity. A nice and powerful device (snapdragon 800).
No more builds for mondrianwifi: https://review.lineageos.org/#/c/179626/
Missing CVE patches are the reason. It's a pity. A nice and powerful device (snapdragon 800).
Don't flash the adreno driver zip? I didn't post it so I don't support it...
Thanks for the reply
I did not take all steps in one go, but took them in the course of the last 3 weeks with multiple days between every step to verify if it fixed the crashing issue.
The crashing issue remained every time. That's why I tried to solve it by trying something else or even flashing the rom fresh from the start.
The flash of the adreno drivers was a last resort a few days ago, but it did not fix or solve anything.
I have 2 problems with all lineage roms for this tablet, I couldn't solve so far:
1) Memory management: I can't do any proper multi tasking. When I switch to another app and then back to the first app, it always reloads the app. Spotify gets closed regularly when I listen to music and it's in the background. Even SwiftKey gets forced closed every now and then, so it takes longer until the keyboard appears. This makes the tablet almost unusable and I have the problem with 6.0 and 7.1 also with a clean install. Am I the only one with that problem?
2) Playing Youtube videos in 60fps doesn't work. If videos are uploaded in 720 or 1080 with 60fps the max resolution I can chose is 480. (edit: fixed that by changing the model number to SM-T715 in the build.props)
1) Memory management: I can't do any proper multi tasking. When I switch to another app and then back to the first app, it always reloads the app. Spotify gets closed regularly when I listen to music and it's in the background. Even SwiftKey gets forced closed every now and then, so it takes longer until the keyboard appears. This makes the tablet almost unusable and I have the problem with 6.0 and 7.1 also with a clean install. Am I the only one with that problem?
2) Playing Youtube videos in 60fps doesn't work. If videos are uploaded in 720 or 1080 with 60fps the max resolution I can chose is 480. (edit: fixed that by changing the model number to SM-T715 in the build.props)
Last edited:
.
I've got two mondrianwifis (temporarily
). For me, they are working fine. They are running with different Versions LineageOS 13.0 from 2017-12-24 and 2017-10-28 (clean installs). I've got no problems switching apps, they don't restart if i go back to them. But I didn't test playing music in the background.I have an 8.4 Pro running a debloated stock rom and am thinking of getting two more for the kids. I'd plan on running lineage but have a few questions if anyone can help as I can't find definitive answers here:
1) is exfat supported now?
2) is adoptable storage working?
3) any other major issues (camera, rotation, battery, etc)?
Thanks!
1) is exfat supported now?
2) is adoptable storage working?
3) any other major issues (camera, rotation, battery, etc)?
Thanks!
I can answer #3. Lineage seems to work great. The ONLY issue is the battery when connected to wifi--it drains much faster than I would expect otherwise.
With stock, I could stay connected to wifi all the time and drainage would be minimal, tablet would last a week or so.
With Lineage, I can only last that long if wifi is turned off when the device is in standby. It'll last maybe 3 days in standby if wifi remains connected.
With stock, I could stay connected to wifi all the time and drainage would be minimal, tablet would last a week or so.
With Lineage, I can only last that long if wifi is turned off when the device is in standby. It'll last maybe 3 days in standby if wifi remains connected.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
47CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:#include <std_disclaimer.h> /* * Your warranty is now void. * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at us for messing up your device, we will laugh at you. * */
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 13.0 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Known Issues
* Exfat support is done at a CM level (not device related) and last I checked has not been added yet. It should get added eventually.
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Experience issues?
* Nightlies: bug reports are not accepted. You are relying on yourself and your peers in this thread for support!
* Stable: file a bug in Jira.
Download Links
CyanogenMod: download.cyanogenmod.org
Google apps addon:
* Too soon to know what's best, I'm currently using the Slim pico package myself.
Useful Links
Unofficial changelog
Mondrianwifi wiki
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
CyanogenMod 13.0 for MondrianWiFi, ROM for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
crpalmer
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Created 2015-11-24
Last Updated 2015-11-2416The next build will have a completely different kernel in it.
For those that have been here for a long time, you might remember eons ago I started working on a clean bringup of our device on the latest CAF kernel. Several versions of Android later, I've finally managed to work through the major bugs.
This kernel is a very important step for preserving support for this device. The patched up, cobbled together kernel source that was based on Samsung's hacked up crappy kernel and then patched across 3 major versions of android has problems and they are very hard to fix because there is so much crap in there.
The new kernel on the other hand makes only the minimal changes to the latest CAF kernel needed for our device to work.
What this means is that our kernel source is now based on what would be used if a device manufacturer were to start a new msm8974 based device with a new kernel. Aka, the latest and best kernel source that exists for msm8974.
Until caf drops support for msm8974 devices, our kernel should be able to track their work and continue to be as close as possible to the latest and greatest.
However, this is a very large change and god only knows what I may have broken... The only issues I have right now are:
* audiofx doesn't work
* using usb-otg and then disconnecting it causes adb/mtp/etc to no longer work until you reboot
Let me know what problems you have going forward and please provides detailed steps for me to reproduce the problem, the data needed to do so and logs.11
Yes, it is working well right now but camera and OMX is pretty much broken across all devices without N vendor blobs. We'll have to wait and see how hard it is to get that working.10
Yes. I have no idea what frequency builds will be from official servers yet but I'll make sure you guys get builds (although I doubt that there will be much happening with 13 as most work has long since moved to 14.1...).
