yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] lotherius:
Not sure about that particular case, but I've noticed that pressure on certain points of the edge of the device seems to affect the touchscreen. I had tried to use a tablet mount in my car, but when the tablet is in the mount, a portion of the touchscreen stops responding. It has to be due to pressure on the edge of the device because as soon as I unclamp it from the mount it starts working normally again. So I can totally see how a case might be putting pressure on part of the device and affecting the touchscreen.

Honestly, the N7 2013 is just too thin and not rigid enough. I can't even put it in my pocket, as was my goal when I bought it, because it was causing it to warp.
[Nexus 7 (2013) Q&A] indraneelc:
Magnetic Case Issue

What kind of multitouch issue are you referring to ? I have Deb (Nexus 7 LTE) + Poetic Magnetic case and don't see any issue till now.:fingers-crossed:
[Nexus 7 (2013) Q&A] Ignite023:
Constantly missing touch gestures
[Nexus 7 (2013) Q&A] oldsoldier2003:
Not having any issues with multitouch here. I'm running cleanrom and elementalx kernel on 4.4.2. Someone mentioned in the thread that it might be related to pressure points on the device and I'm inclined to agree.

You might also want to take a look at this thread.
[Nexus 7 (2013) Q&A] dkryder:
Screen protectors can be a cause of touch problems. I got a package of the official screen protectors at the time I bought my device. It took me 2 weeks to figure out the protector was the cause , after I began to question it I found out the thing was just too thick.
[Nexus 7 (2013) Q&A] pre4speed:
Now that is not something I disagree with. My multitouch issues actually got better after I applied my official screen protector. Went away completely after upgrade to 4.4.2, even with my magnetic smart case.
[Nexus 7 (2013) Q&A] fqr:
until i got a case, i thought my N7 doesn't suffer from touch problems. but apparently the case degraded grounding and my tochscreen got partly unresponsive. holding the tab in both hands, there weren't any issues at all. so yes, cases can worsen touchscreen issues.

but luckily the ts-10 patch from sfhub's thread solved the tochscreen issues permanently. even with a case everything works flawlessly.
[Nexus 7 (2013) Q&A] dkryder:
Maybe it would be better worded "that is something I disagree with", or, "that is not something I agree with",??because it seems you are of the mindset that the protector does not negatively affect you touchscreen experience. I realize your experience can be the direct opposite of mine, which in my thinking does not negate either's experience.
[Nexus 7 (2013) Q&A] pre4speed:
I realize my grammar mistake. Oops. Yes, in my own personal experiences, I have never had a bad experience with screen protectors negatively affecting my touchscreen. The type I have used, matte, yes that affected the viewing experience. But in my experience, having that very minimal slight drag has helped with typing, drop and drag, selecting items etc. I have since switched to clear protectors (never the orange peel type, yuck) and rather glad I did. I am very much about resale value on all my devices from opening the box. No device ever gets used without a case and protector. Being able to sell as used in mint condition when I upgrade my devices 2-4 times a year is a major way to reclaim that money. Plus I dont like the slippery soap feel of naked screens. I did not mean to come off as negating your experience. I apologize if it did.
[Nexus 7 (2013) Q&A] cobaltleo:
I just love the community here anywhere else that would have been the start of a flame war. But the folks here actually take the time to try to clear things up like adults. Thumbs up to you all.?
[Nexus 7 (2013) Q&A] dakunclear:
Try using ts10 image or the other 2 seems to have fixed all the issues with the screen and you don't need to be rooted to use it
[Nexus 7 (2013) Q&A] mhannigan:
Or "That is something with which I don't not disagree".
[Nexus 7 (2013) Q&A] pre4speed:
Now you're making fun of me. Lol, im a big girl, I can handle it. :thumbup:
[Nexus 7 (2013) Q&A] dakunclear:
Interesting I'll have to test this out now that you mentioned it
[Nexus 7 (2013) Q&A] hakcenter:
You may have an older version. I know moko went through two, one didn't trigger the magnet on or off well but would sometimes trigger screen off from the back.

I've got the same case, v2, no noticeable privileges but I'm using ts20 for this nexus.
[Nexus 7 (2013) Q&A] wednesday13:
I was having ghost screen touches, so decided to remove my poetic slimline case. That solved my touch screen issues.
[Sprint Samsung Galaxy S III] kalico17:
to start. ive had my gs3 since Feb.

the past 3 months I have been experiencing HORRIBLE battery life and my phone flickering/shutting down even with like 30% battery life.. it never happens until it hits 35% or below...

i can open an app like FB, or my camera, or IG and it will flicker a bit while im using the app and then the phone just shuts off

I have tried multiple roms with multiple kernels.. always the same issue..

SLIMKAT with KT or DKP kernel

CM11 w/ BMS kernel

AOKP (when they were building) with BMS kernel

Gummy Rom - BMS or DKP

Carbon Rom - BMS or DKP

MOAR 6.0 with dkp kernel

MOAR 7.1 - DKP kernel

to note. Ive also tried several of these, stock, with same results.

ive tried undervolting, overvolting, changing the gov, etc... nothing works

i get about 6-7hrs MAX and it always dies with a charge still left

and if I turn it back on and it boots and happens to crash again, i have to reflash the rom completely, clean wipe and all just to get the phone to boot again

im not sure what i did or where i went wrong but any suggestions would be great

thanks guys!!
[Sprint Samsung Galaxy S III] dhlee528:
my phone flickers around 20% battery

I'm pretty sure it's battery issue, I don't want to spend money on battery because I'm switching to different carrier soon.
[Sprint Samsung Galaxy S III] kalico17:
Damn
[Sprint Samsung Galaxy S III] kalico17:
anyone else have any input?

attempting a stock flash and see what happens from there :/
[Xoom Android Development] Schischu:
CyanogenMod 11.0 coming to a xoom near you!

This ROM is for wingray, stingray and everest.

Based on:

CyanogenMod "cm-11.0"

Kernel ElementalX-Xoom-2.1 by flar2

Download

cm-11-latest-UNOFFICIAL-wingray.zip (md5sum)

cm-11-latest-UNOFFICIAL-stingray.zip (md5sum)

cm-11-latest-UNOFFICIAL-everest.zip (md5sum)

Download GApps

TBD

Download Root

Already included

Download Deprecated

Browse deprecated

Install

You will need bigPart TWRP and execute the repartitioning as described in

Source

Prerequisites

TWRP 2.6.3.0 R.A.H BigPart Edition Recovery

The ROM you want to flash

Instructions

Your data will be totally wiped!

If you have Nandroids, TitaniumBackups, or anything of any value on your internal storage, copy them to your microsd or computer! They will be gone forever! Your microsd card is the only safe haven on your Xoom during this process.

Put TWRP 2.6.3.0 BigPart version and your desired rom on your microsd card.

Reboot into recovery. Flash TWRP BigPart.

Reboot into recovery. Go into wipe menu. Select "Advanced Wipe". Check

Dalvik Cache

System

Cache

Data

Internal Storage

and wipe them. Don't reboot just yet.

Go into install. Recovery should show your microsd storage by default. If not, using the navigation panel, navigate to root then go into "sdcard". You can now follow the steps below, starting with Flash cm-11-201XXXXX-UNOFFICIAL-wingray.zip.

If updating from older ROM version in this thread, you don't have to wipe anything

If updating from an different rom, wipe

Dalvik Cache

System

Cache

Data

Flash cm-11-201XXXXX-UNOFFICIAL-wingray.zip

Flash gapps-xxxx.zip

Reboot

Issues

TBD

Tips'N'Tricks

Show Developer and Performance settings

Go to the settings menu, and scroll down to "About phone." Tap it.

Scroll down to the bottom again, where you see "Build number."

Tap it seven (7) times, and *poof*, you've got the developer settings back.

Reduces lagging

Overclock to 1.4Ghz (Performance menu)

Decrease animation duration to .5 (Developer options menu)

Source

https://github.com/Schischu

Thanks

dreamcwli

DJNoXD

bubor

michie

flar2

Adler12

realjumy

rchtk

bigrushdog

Special thanks to everybody who donated, You guys rock!!!
[Xoom Android Development] Schischu:
Changelog

The list below may not be up to date.

Check CHANGES for a more current and detailed changelog instead.

cm-11-20140105-UNOFFICIAL-1945+0100-wingray|stingray|everest

- Update CyanogenMod "cm-11.0" from 5nd of January 2014

- Add OTA support

cm-11-20140104-UNOFFICIAL-1537+0100-wingray|stingray|everest

- Update CyanogenMod "cm-11.0" from 4nd of January 2014

- "Unfortunately Messaging has stopped" fix

- Camera fix

- HW VideoDecoding fix

cm-11-20140104-UNOFFICIAL-0939+0100-wingray|stingray|everest

- Add stingray and everest

- Add bigPart check to update.zip. Will assert if not bigPart TWRP

cm-11-20140103-UNOFFICIAL-wingray

- Initial version
[Xoom Android Development] ggrammer:
WOW You've been busy. lol

Thanks for all the effort you have put in.
[Xoom Android Development] -ix-:
As already stated: wow! You're on a roll! :D Thanks a lot for sharing everything with the community.

Can we hope for an Everest version of this as well?

Sent a long time ago from a Galaxy S2 far, far away...
[Xoom Android Development] Y_Yan_C:
cant wait till everest cm comes!
[Xoom Android Development] superbay:
Dude seriously? This is way beyond awesome :victory:

I bet you are having longer new year holiday for this :D Waiting for the Everest as well :)

For the user, what is the difference of KitKat Omni and CM in this device?
[Xoom Android Development] no*boundaries:
Hmm what the !!, I thought CM was dead for Xoom??Big round of applause for you all, especially from us Everesters...
[Xoom Android Development] -ix-:
Everest already?! You're not human! :sly:

Really eager to try this on my Everest. As asked above, difference of user experience between CM and Omni?

Once again, a big round of applause for you Schischu! :thumbup:

Sent a long time ago from a Galaxy S2 far, far away...
[Xoom Android Development] no*boundaries:
sadly, it isn't updating its "FAILING" error executing updater binary, ooops I think it bricked
[Xoom Android Development] Schischu:
Try redownloading the rom.

There was an error on the server which caused all files downloaded earlier today to be invalid.

And the md5sum is also invalid, so dont copy it to your device.
[Xoom Android Development] superbay:
Which gapps do i need to download by the way?
[Xoom Android Development] sk4doosh:
I've managed to successfully install the ROM and have found the following issues -

Not sure what version of gapps to install as there are no links. Tried downloading gapps-kk-20131208.zip from cyanogen but get the following error.

E:Error executing updater binary in zip '/sdcard/gapps-kk-20131208.zip'

Error flashing zip '/sdcard/gapps-kk-20131208.zip

Updating partition details...

Messaging - Unfortunately, Messaging has stopped

Camera - Unfortunately, Camera has stopped

Flash content - no video, audio only

Also, in the developer options the lowest Animation scale duration is .5x (not .25x)

Great to see some fine development, keep up the good work.;)
[Xoom Android Development] Life4Never:
Also like to add to the above that the font inside the folders are cut off.

Font for the battery percentage inside the circle also not centred.

Thanks for your great work. My Xoom feels faster than ever in everyday use.

Edit:

Just installed nova and everything working fine minus camera crashing.
[Xoom Android Development] sammyroot:
CM11 for the xoom is awesome news!!! I just installed todays (wingray) and as mentioned the camera isn't working. Also, where is "mmersive mode?" Any idea why on the omni rom with immersive mode is enabled, homescreen scrolling is completely lag free?

Again, thanks for continuing to take the time and support this device. I just came from stock 4.1.2, tried cm10.1 but it hung up too much. CM11 is ridiculously fast!
[Xoom Android Development] notbrodie:
both PA and banks core gapps work fine

Sent from my Nexus 5
[Xoom Android Development] sk4doosh:
Just installed the latest version (cm-11-20140104-UNOFFICIAL-1537+0100-wingray). Camera and messaging issues now fixed :good: Also installed pa gapps and the apps seem to be running fine (gmail, play store, voice search and youtube).

The only other thing to note is that when scrolling from one home screen to another you are left with a white transparent background. Not sure if this launcher related or something else.

Great ROM for such an early build.:D

Edit:

Forgot to mention that flash content from bbc.co.uk is still audio only.
[Xoom Android Development] murigny64:
Amazing !

Better compatibilty than OMNIROM.

More fluidity, faster boot and now, games from King.com work fine.

Thanks very much.
[Xoom Android Development] Peterpaulmarie:
Thank you for CM11, but no advantages (only double-tap to sleep) to Omni-Rom, but same disadvantages:

- TB has problems with superuser (can't delete sams apps)

- fc with toogles

- start in recovery?

- Omni feels smoother

- no expanded mod
[Xoom Android Development] no*boundaries:
I got the updated rom in, successful, but Gapps =kk-20131119 failed, is there a link for PA or Banks?
[Xoom Android Development] notbrodie:
banks gapps - bit.ly/19VbAlL

Sent from my Nexus 5
[Xoom Android Development] drewski_1:
Are you using the Google Experience Launcher? the disappearing icon is a bug "feature" of that launcher when used on tablets.
[Xoom Android Development] emaxxim:
Yes, I am. But for the fixed lockscreen?
[Xoom Android Development] no*boundaries:
Many thanks, cheers
[Xoom Android Development] wangshin248:
TWRPv2.6.3 ask me password !!! :( if i cancel it, i can not wipe CACHE

-----------

Done, just wipe cache first
[Xoom Android Development] fudsak:
I'm also having this issue.
[Xoom Android Development] notbrodie:
if using s2w or dt2w, turn them off. if not that, try raising your min cpu freq

Sent from my Xoom
[Xoom Android Development] mjc2251:
I'm using nova launcher and have the option to enable transparent status bar but it does not seem to be working. Is this ROM capable of transparent status bars, If so is there something I need to enable?
[Xoom Android Development] drewski_1:
it's not working yet.
[Xoom Android Development] dweezle:
It has been a LONG time since I flashed anything. I have a Stingray Xoom. I am on Team EOS 4 build 197, TWRP ver.2.6.3.0 (NOT big part version).. I am about to try to install CyanogenMod 11.0 and want to do a last minute Nandroid using TWRP. My TWRP backups are being saved to my sd card.

What exactly should I backup?

The options are System, Data, Boot, Recovery, Cache.I want to be able to recover my existing apps in CM11 without having to reinstall each one individually.

I have downloaded;

R.A.H._TWRPv2.6.3_BigPart_selinux.zip

cm-11-20140122-UNOFFICIAL-1943+0100-stingray.zip

pa_gapps-modular-mini-4.4.2-20140123-signed.zip

Am I good to go?
[Xoom Android Development] notbrodie:
system and data. to restore the backup, you'll have to revert bigpart

Sent from my Xoom
[Xoom Android Development] realjumy:
Before doing the nandroid backup update your current TWRP to the last version. There was an old bug that performs corrupted backups...
[Xoom Android Development] dweezle:
Thanks for the tips. All went well and CM11.0 is happily chugging away re-installing all my apps.

I do have a question about the tip by the OP about overclocking to 1.4Ghz. I have set CPU governor to "performance", left the Minimum CPU frequency at 216 MHz, set the Maximum CPU frequency at 1400 MHz and, checked "set on boot". Is that correct?

Thanks again, The install very went well and reading all the posts in this thread made the various hiccups easy to get through.
[Xoom Android Development] superbay:
With governor set at performance, you will have your Xoom run fast since it will lock the clock on maximum frequency. In the other hand, this kind of governor will drain your battery faster as well. I humbly suggest on demand governor which will dinamically set your cpu clock as necessary between minimum and maximum frequency
[Xoom Android Development] rapson2000:
I know several of us are having this problem... I have a Stingray and can not seem to get functional data service with CM11 (or with Omni for that matter). Starting from stock rooted 4.1.2, I flashed to BigPart and then to Omni. I had all kinds of problems with the early Omni builds so I switched to CM11. My Xoom ran better than ever, but... no data. I need the data. I tried flashing every rom available and found I could get 3G with BigPart EOS4 only (I am running that now, and it is really clunky for some reason). I still have no 4G/LTE. My device shows no IMEI number. What I really WANT is to get back to CM11 with my 4G.

Has anyone been able to correct this issue? Those of you who have said you have CM11 and functional data service... am I missing something?
[Xoom Android Development] dweezle:
O
[Xoom Android Development] realjumy:
Sometimes I have that problem with Omni. I turn off and on (not rebooting) and then it works. Try it.
[Xoom Android Development] rapson2000:
I have tried powering the tablet down a few times, but I will try that again a few times throughout the day today and I will let you know if it ever jump starts my data service.
[Xoom Android Development] webeougher:
I think he meant turning your Verizon service on and off, which you can do from the active tiles. That hasn't worked for me at all though.
[Xoom Android Development] armido:
This is a serious problem...

I am responsible for making it possible for sailors everywhere to install an open source marine navigation program on their android devices http://opencpn.org/ocpn/node/193 . The program runs in a chroot linux environment, and most people who follow my instructions are minimally familiar with linux commands. The ability to use an android root file management app to accomplish steps in the installation process is critical. But, a change made in either the Kit Kat OS itself or SuperSu is preventing access to the linux filesystem /data/local/linux/mnt. It appears to be hidden. If a fix for this problem is not released, it will prevent sailors from successfully installing OpenCPN, a full featured marine navigation program and render useless lots of work I devoted to making this happen. Appreciate some help here.

Thanks.
[Xoom Android Development] Schischu:
While installing linux deploy, change the installation path from /storage/emulated/0/linux.img to /storage/emulated/legacy/linux.img.

That is all.

Will probably push this filesystem link also as update over OTA in the coming days, just to stay compatible to the old ways.
[Xoom Android Development] armido:
/storage/emulated/legacy/linux.img makes no difference...

Both paths point to linux.img. Simply changing the path name does not affect Linux Deploy's start. The configuration file updates and the partitions mount on start. However, FX still does not display the linux file system. I may be wrong, but reinstalling linux with /storage/emulated/legacy/linux.img instead of /storage/emulated/0/linux.img will still yield the same result. Because, unless I am a total dufus nothing changes in regard to using FX.

Thanks.
[Xoom Android Development] mr.valacky:
Hey guys!

my old system: cm-10.1-20140112-NIGHTLY-everest

I've been trying to install, but twrp unable to wipe data, cache, dalvik cache

i Put TWRP 2.6.3.0 BigPart version and rom on my microsd card.

Reboot into recovery. Flash TWRP BigPart.

Reboot into recovery. Go into wipe menu. Select "Advanced Wipe". Check

Dalvik Cache

System

Cache

Data

Internal Storage

twrp unable to wipe data, cache, dalvik cache
[Xoom Android Development] kmcrane:
Fomat data... Reboot recovery then try wiping the rest
[Xoom Android Development] tdawgg777:
boot animation

Anyone having a problem using a different boot animation?
[Xoom Android Development] mr.valacky:
thank you!

all done :)
[Xoom Android Development] joshndroid:
found the charger to the old xoom... (currently have a note 10.1 2014).. seen the big part thread gave it a whirl and now running your rom.. ha good stuff rom runs great, just cant kill this ting
[Xoom Android Development] mwie:
Guys,

so far the ROM is running smoothly...

Having two issues:

- I am using GoLauncherEX and resizing of widgets is not working properly.

Might be a GoLE issue, just want to know if anyone else is experiencing it...

- my tablet now rings when a call is coming in and I can accept the call... but I don't hear anything...

Since when is the XOOM supposed to work like a smartphone?

Can I get rid of it by simpy unistalling the phone app??

Thx!

- mwie -
[Xoom Android Development] armido:
Schischu,

Do you still maintain simply changing the path to linux.img from /storage/emulated/0/linux.img to /storage/emulated/legacy/linux.img will resolve /data/local/linux/mnt (/sbin, /usr, /lib, /home, /var, etc.) being hidden from android root file managers? If so, I'll give it a go. But reinstalling everything only to discover the problem still exists is not something I should have to do. Changes from 4.2 to 4.4 should not be so disruptive that users must do these sorts of things. And still, I have not been told precisely what sort of change was made that causes this problem. I am techie enough to understand.

Thanks.
[Xoom Android Development] Schischu:
So you expect me to invest time to reset my device to test if your problem is resolved by my proposed solution, while you won't?

Thank you very much for the conversation.
[Xoom Android Development] armido:
Schischu,

Reset? Install Linux Deploy? Linux Deploy is an android app used to install linux. It is not simply a matter of resetting my device (whatever that means) or installing Linux Deploy. It entails using Linux Deploy to recreate the loop file, download a complete linux operating system and graphical user interface numbering thousands of files, compiling and installing OpenCPN from source and reconfiguring everything. If you know the cause for /data/local/linux/mnt being hidden from android root file managers, please explain. Then maybe I'll understand why your proposed solution makes sense.

Thanks.
[Xoom Android Development] SgtTeabag:
Did it ever occur to you that this is still in testing/experimental stages since this wasn't designed for ANY Xoom in the first place since your a techie? What we do here is try to politely help each other if we take the risk of installing this in the first place. It is in no way Schischu's responsibility that something doesn't work or it nukes something. To demand that Schischu wipes his/her tablet to help you without even asking nicely is rude. Remember everyone 4.4 for our Xoom was a gift and if ya read the op its not anyone's responsibility what you do to your Xoom. So try being a little polite to the person that provided this to us and trying what they say to try first please?
[Xoom Android Development] armido:
"To demand that Schischu wipes his/her tablet to help you without even asking nicely is rude."?

And, to insinuate a 'demand' has been made when NO demand has been made is over the top. I suggest you read and understand my posts before you start declaring I have been rude to anyone in any way.

Armido
[Xoom Android Development] SgtTeabag:
OK just reread everyone of your posts. Where I come from it would be could you please check into this or would you please try to help me get this going and thank you for taking the time to do so. Not once did I see a please or thank you. Where I come from that is rude!!!! ;) Sorry for straying off topic Schischu.
[Xoom Android Development] armido:
SgtTeabag,

You don't read very well. Posts 199, 201, 208 , 210 "thanks"

"please explain" Post 210

And, whether or not my posts meet your standard of acceptibility as measured by how frequently I say please or 'thank you', they are clear and easily understood. If I had the answers I wouldn't be here asking questions. If you don't have the answers and only interjections saying someone is 'rude', I'd say it is you who are out of line - not I.

So, 'please' stay out of my business unless you have an answer to my questions.

"Thank you".