yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] Schischu:
Well I for once did find your last posts rude. And that should be important to you as you expect help from me.
[Xoom Android Development] armido:
Another go at trying to get an explanation.

Schischu,

Since I am being accused of being rude and thankless, here's my post #165 for yours and SgtTeabags review.

"Enabling "Multi User Policy" fixed the no start with Linux Deploy, but the log content is still not viewable. Would be nice if it was.

Also, is it likely SuperSu is responsible for not being able to view the linux filesystem when mounted at /data/local/linux/mnt? If so, a fix will be appreciated.

Thanks to the devs for first making new ROMS useable with the Xoom and second keeping with the spirit behind full user control."

Back to the question.

What is the reason android root file managers cannot display /data/local/linux/mnt, that simply changing path names in Linux Deploy will resolve?

All the path name in Linux deploy does is define where the loop file, linux.img is installed; (/storage/sdcard0/linux.img, /storage/emulated/0/linux.img or /storage/emulated/legacy/linux.img. I have changed the path name in Linux Deploy to each of the paths listed here. Predictably, Linux Deploy functions normally.

Linux Deploy defines the 'mount point' as /data/local/linux/mnt. Proof the system mounts properly at /data/local/linux/mnt is two fold. The system can be accessed and linux commands executed in a terminal. The Linux desktop can be viewed using a vncviewer. But, the linux system is hidden from android file managers. This suggests an android system configuration and or permissions issue may be the problem - having nothing to do with Linux Deploy or android root file managers, except in the case of file managers being blocked from reading /data/local/linux/mnt/. There is nothing to suggest a problem with permissions related to /data/local/linux/mnt. There is some interesting content in init.rc regarding security. Didn't look at the other .rc files, but could one of these files be the source of this problem?

Your appraisal please.

Again, "Thanks to the devs for first making new ROMS useable with the Xoom and second keeping with the spirit behind full user control."

Armido
[Xoom Android Development] drewski_1:
I know Titanium Backup had issues where changing to the /legacy/ folder allowed Read/Write to the backup folder.

I don't know the underlying reason or fix, but this proposed solution worked there.

This was not from a Root File Manager, but a Rooted app that was trying to access certain directories.

Maybe this is a similar issue; i'm not familiar with Linux Deploy and how you/it are/is accessing the files in question.
[Xoom Android Development] armido:
File permissions...

Drewski,

Thanks for your attempt to help. The problem is dissimilar in that there is no app dysfunction or failure to access necessary files/folders. The problem is simply that while root file managers are able to read, copy, rename, delete, change file permissions (with some exceptions) anything and everything in the android file system, they can't read the linux filesystem at /data/local/linux/mnt. This means nothing that can be done with the android side can be accomplished with the linux filesystem. Really wierd.

Thanks again.

Armido
[Xoom Android Development] realjumy:
In this context maybe I can be seen as rude, but don't understand it, please.

[MENTION=4674742]armido[/MENTION], can you open a new thread with all this? I think that it looks like a new and big project that deserves an own thread with all the documentation, problems and research done. There people can help and this thread keeps reserved for Cyanogenmod 11.

Thanks.
[Xoom Android Development] webeougher:
This. And, as an added bonus, if you're reading this thread and are about to ask for help on the BigPart process, go post it in that thread.
[Xoom Android Development] armido:
CyanogenMod...

I have a Xoom MZ 601 running CM11 version 126. This issue is related to the operating system and not the hardware. Why does it look like a big project deserving it's own thread? Please explain if you know the answer why the Linux file system at /data/local/linux/mnt is hidden from root file managers. It has been suggested I reinstall Linux using Linux Deploy using a different file path. Considering the amount of work and time involved I'd like to understand why this is supposed to solve my problem before doing it. If you and Schischu don't know the answer, please say so.

Thank you.

Armido
[Xoom Android Development] realjumy:
I don't know the answer. And I don't know the answer to why I can't use my ES File Manager as root explorer but, to be honest, I'm still doing exams and I will not make any research until I finish with them. In December I failed many of my exams because I give too much time looking for a method to change the partition structure (even if I didn't success), and I can't do the same again.

Let me give the example of the BigPartition. I didn't found the final solution, but I think that at least I contributed with ideas and finding things that didn't work. I think that, as far this is a collaborative forum we should search the answer helping each others. And we should release all the steps we do to help other people. However, I can't find what you did.

And about why your project deserves a new thread... Yes, it's related to this ROM but your intention is to do a final thing different to this ROM, and maybe can be applicable to different ones with the same structure, method or whatever have in common with this one. In addition, you said that it took a lot of your time. That means that it's a big project.

As I previously said, I can't contribute with more research, but maybe you can try searching how to mount or symlink using command line. Maybe that can help.

Good luck.
[Xoom Android Development] rhcreed:
gapps error

got the system partitioned and the rom installed, but twrp won't install gapps for me. keep getting the "error executing updater binary in zip" error. have tried a couple different packages and no luck..

any ideas?

Can someone link a package that works or tell me how to get past this?

Thanks!
[Xoom Android Development] realjumy:
Seems like you have a corrupt download. Try downloading it again and if you are no lucky with the new download, I will upload the version that I have in my Xoom's SD.
[Xoom Android Development] sammyroot:
I love this rom!! Not sure if this has been discussed, but my back softkey is dimmer than my home and recent apps keys. Anyone else have that? Fix? Thanks.

Joey
[Xoom Android Development] drewski_1:
I have that intermittently.
[Xoom Android Development] rhcreed:
cwm?

after everything is set up and rom is installed, can I go back to to cwm or do I have to stay on twrp?
[Xoom Android Development] webeougher:
If you plan to update the rom at all, or switch to any other BigPart roms, you have to stay with TWRP. Give it a shot - it's a better recovery than CWM in pretty much every way - faster backups and restores, easier wiping when going between roms, and a built-in file manager.
[Xoom Android Development] Alxoom33:
Love this Rom with new life for my Xoom! Imagine, running KitKat flawlessly, well almost, on an eol device like this sweet wingray:)

---------- Post added at 09:18 AM ---------- Previous post was at 09:15 AM ----------

One issue that I get with CM 11 and not with the Omni counterpart is SOD. In the evening I leave the Xoom on the charger overnight it SOD's and I typically need to reboot, alarm never sounds.
[Xoom Android Development] rhcreed:
hosed?

here's where I'm at..

flashed the twrp bigpart, flashed the rom, can boot into the rom..

twrp cannot flash any gapps package I try (either from sdcard or internal storage) (have tried a variety of them, known good)

tried flashing cwm, able to boot into it as recovery, but it cannot mount any storage points, so it can't flash gapps..

system will not boot to fastboot, so adb and fastboot off pc are useless..

did I screw something up? any way to flash gapps from within a booted system?

Thanks for any help..
[Xoom Android Development] realjumy:
How do you flashed Gapp? Did you wiped data and caches and then flashed ROM, gapps and Su without booting? Any space or special character in the filename or folder? Can you send photos of the error? What Gapps version have been tested?
[Xoom Android Development] rhcreed:
I was flashing gapps in twrp install->choose file swipe to flash...

getting the "error executing updater binary in zip" error

I've used the last 3 kk gapps packages, tested and known good on my N7..

I followed the wipe instructions in the OP, so yes..

adb can see the device, but won't issue any commands "error : closed" is what I get trying to push or install anything..

any suggestions would be great, thanks!
[Xoom Android Development] drewski_1:
error executing Updater Binary is something I've seen when the Recovery is not current, but BigPart TWRP is 2.6.3.0

"the last 3 kk gapps packages"

anyway, this is not enough info as there are many different KK GApps.

i'm using PA GApps and it's flashing fine. if yours are different, maybe try those?
[Xoom Android Development] Schischu:
Linux Deploy works fine for me if you do what I previously described.

Or install the latest OTA as I added a link so emulated/0 points to emulated/legacy.
[Xoom Android Development] SgtTeabag:
I got deploy working also as you described just testing to try to help out. Seems to work well too.
[Xoom Android Development] rapson2000:
Sorry not to get back to this for a few days. Busy week at work... I tried both complete power downs of my tablet and just switching my mobile data on/off from settings, and I have never so much as gotten a blip of data service. I was reading back through some of the forums and noticed that a few of us that are having to loss of data mentioned that we started this whole thing with a stock rooted 4.1.2, is there any chance that could be what we have in common that has some of us with no data and other CM11 BigPart users with perfectly functional data? Or does anyone here have data after flashing from the stock rooted 4.1.2? I could be way off base here, but at this point I am willing to check out anything.
[Xoom Android Development] webeougher:
I'm going to de-BigPart my Xoom today, go back to Honeycomb, and then try re-BigPart-ing and see if I have any luck. I'll let you know what I find out, and thanks for the idea.
[Xoom Android Development] armido:
Now that you've installed Linux Deploy...

Schischu,

Thank you for testing Linux Deploy, but Linux Deploy is not the problem. Now that you have linux installed, please use your favourite root file manager after starting Linux Deploy and navigate to /data/local/linux/mnt. With EOS version 4.2.2 you would see the linux file system /home, /sbin, /lib, /usr, /var, /boot, /tmp, and /opt. You could copy, move, rename, create folders - everything FX offers in the way of file operations. In android version 4.4.x, after Linux Deploy is started you do not even see the linux file system when using your root file manager. This is the problem I've been describing. Jrummy suggested creating a link to the android system, an option in settings provided by Linux Deploy and enabled in my Linux Deploy setup. I'm at a loss as to why the linux system is invisible to FX. Hoping your knowledge of the differences between 4.2.x and 4.4.x will lead to a solution. This problem persists after updating to the most recent version 131.

Thanks!
[Xoom Android Development] ankorez:
i've used this rom since 1 Week and sometimes black screen no another bugs founds

great job

Thank you!
[Xoom Android Development] drewski_1:
Isn't that his second picture?

Sent from my 4.4.2 Razr Maxx
[Xoom Android Development] webeougher:
Dude, you're a genius! I went back to Honeycomb, couldn't get data at all (in spite of trying to activate my device multiple times), took the factory updates through ICS, which is where I got 4G back, re-rooted, re-BigParted, installed CM 11, and boom - data. I had the android.phone.com force close when I first booted, so I pulled my SIM, rebooted, finished setup, re-installed SIM, rebooted, and I'm good to go! I'll write up a full guide in the morning, but if you're savvy, you should be able to get it working tonight.
[Xoom Android Development] rapson2000:
Awesome! That is great news! I'm not going to get a chance to try it myself today, but I'll post back here and let you know if it was successful for me as well. Too cool.
[Xoom Android Development] Schischu:
Hm, if you look at the second screenshot I attached in my previous post you can see that all the folder you listed are displayed.

I'm confused.
[Xoom Android Development] webeougher:
For anyone with a Stingray who hasn't been able to get data working with this rom, I typed up a walkthrough in the Q&A forum with the steps that I used to get data back. I am currently enjoying full 4G on my Xoom running the latest nightly. You can find my write-up here.
[Xoom Android Development] armido:
Full ROM reinstall, SuperSu broken...

Started from scratch installing ROM. I think installing whichever ROM included SuperSu should have included steps 'coming from a different ROM', wiping cache, System and etc. Somehow the old SuperSu was interfering. Indications that permissions were being given was bogus, because in fact they were not. Your screenshot convinced me that something having to do with SuperSu was the problem because none of the root file managers except FX could access /data. But, FX also has a root extension. Reinstalling Linux now and have already confirmed the filesystem at /data/local/linux/mnt is viewable. The SuperSu prompts are very different than before reinstalling the ROM as if coming from a different flavour. Unless users rely on root access as much as I do, they may not be aware they have a dysfunctional SuperSu.

Thanks for your help.
[Xoom Android Development] webeougher:
I don't mean to come across as rude, but most people using this rom have used CM on another device, and Superuser has been built in for almost two years now, since Koush first released the app.
[Xoom Android Development] armido:
Most people?

I came to CM via EOS then OmniRom. If you look at the installation instructions installing the SuperSu update is part of the process.

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 omni-4.4.2-201XXXXX-everest-HOMEMADE_XXXX.zip

Flash gapps-xxxx.zip

Flash UPDATE-SuperSU-v1.86.zip

Reboot

Having never used CM before my error was believing the update was necessary for CM too. What I find remarkable is how posters here need to use the word rude. The same message can be delivered without using the word and nothing is lost...
[Xoom Android Development] armido:
Clarification...

My experience is that SuperSu has always performed its job reliably and without error. However, if a person follows the path I did from pre-BigPart partition EOS, to OmniRom and then CyanogenMod it is possible after having followed instructions at http://xdaforums.com/showthread.php?t=2593414 they'll make my mistake. I followed the instructions here: http://xdaforums.com/showthread.php?t=2596566, and experienced no problem until I tried to install linux using Linux Deploy. The message I received from Linux Deploy was it needed root. Relying on my experience with EOS and OmniRom I looked for what I discovered was a missing SuperSu icon. Concluded that like OmniRom, the SuperSu-update needed to be flashed. Once SuperSu was flashed, and SuperSu Pro enabled, I was able to install linux. Because I use FX File Explorer with a root extension, everything seemed fine except for the fact I could not access the linux filesystem with FX. I posted questions about this problem and until recently received no reply. Went through updates until CM-11 V131 at which point the SuperSu icon disappeared and Linux Deploy complained it required root once again. How to enable SuperSu Pro without that icon? I posed the question and for the first time I learned from Schischu SuperSu was included with the ROM. I believed this was a new feature beginning with 131. But still, because the old SuperSu was installed in system - and surviving updates - it was the controlling SuperSu presenting the familiar grey prompt when an application requested root permission. It was not until I reinstalled CM11 from scratch, wiping system, cache, and dalvik cache that the new SuperSu included with CM began to function. This was evidenced by the appearance of the larger, red coloured popup window.

How could this experience have been avoided? In hindsight I know now what "Download Root,

Already included" means. But it didn't register with me that this was referring to SuperSu. Editing the instructions to explicity state, "Do not flash or install SuperSu from Google Play, it is included with the CM ROM - accessed in Settings" - will help others to avoid the problems I've experienced. SuperSu was 'dysfunctional' only due to my mistakes, but nonetheless dysfunctional until I took the necessary steps to resolve the issue. One more point. Because Schischu made a change to the ROM that enables one to install Linux Deploy the 'old way', I cannot be sure the problem I had accessing the linux filesystem was not due to a change implemented between 4.2 and 4.4 that rendered the filesystem inaccesible. In any case, I am happy to report all issues are, thanks to Schischu, resolved. Thanks Schischu!
[Xoom Android Development] sk4doosh:
Anyone interested in getting Adobe Flash working on this rom or in fact any other Android 4.4 device use the latest version of flash player available for Android (http://download.macromedia.com/pub/...roid/11.1.115.81/install_flash_player_ics.apk) and install the latest version of Firefox from the Play Store.
[Xoom Android Development] michie:
No need for firefox, look for the hacked flash player for kitkat. All flash movies run fine on every browser ;)

https://drive.google.com/file/d/0B1qjrD8ZER9ITmlVNW1EVWM5YlE/preview?pli=1
[Xoom Android Development] lasportsfan:
Anyone having problems adding more than 2 user profiles?
[Xoom Android Development] bigfootnmd:
Netflix issues with wingray OMNI Rom

UPDATE: CM 11.0 Is installed and there are no ISsues with NETFILX

Back in January when i learned that GOOGLE had announced that there would be no new updates for the Motorola Xoom, I found this Page and I posted seeking advice. I took the path lead me install the Omni Rom. I do have the latest wingray Omni Rom. Since I wiped the last version of Android from Google following the instrcutions on this page I also had not loaded every app that I had on my WIFI only XOOM.

So, earlier in this week I noticed that I didn't have the Netflix app. So, I loaded it and I ran into issues. I posted on this Page on Friday and a reply suggested that the Cyanogen MOD 11.0 would be worth trying. The issue with the Netflix APP (yes it is the latest) is since I sometimes use captions while watching Netflix Streaming content on my Sony Bluray that if captions are available they are usually on by default.

On a 10" screen captions are not all that helpful. So, now if I start a streaming program on Netflix the captions are usually on. If I tap on the right corner of the screen and I turn off the captions then the audio also ceases to play on my XOOM.

Please understand that i have only Rooted and loaded a new ROM once back in January. After I did that successuflly I wiped all the files off of my SDCARD. I assume that since I already BIGPARTED my Xoom that all I need is the current version of the CM ROM. But, the instructions in this thread do indicate that you need to flash the Google Apps after you flash the CM but there is no link to the download. So do I need to flash GAPPS? Where are they?

Except for this issue above (described in two other posts on this site) with Netflix I have found the Omni ROM to be workable.

So, before I try to move from OMNI to CM, I will appreciate any help.

Thanks
[Xoom Android Development] webeougher:
You can use the same GApps you used with Omni, but it sounds like the problem is with Netflix. If you'd like, I'll try to replicate your issue on my Stingray running CM 11 before you flash. Also, you didn't need to wipe your SDCard to BigPart. Just FYI.
[Xoom Android Development] xyrcncp:
I'm running CM11 and Netflix (version 3.1.2) and have no problems toggling captions on and off with no problems.
[Xoom Android Development] crisjogos:
Thanks for the amazing ROM! New life for our old Xoom!

Enviado de meu Xoom 3G usando Tapatalk
[Xoom Android Development] tracker01:
anyone experiencing FC play store and random boot?
[Xoom Android Development] bigfootnmd:
Thank you

CM 11 is installed and all is well. I loaded Netflix and I played a movie that i had never played before. Captions were enabled when playback began but now I can turn the captions off without loosing the audio.

Thank you to all who helped.
[Xoom Android Development] rlmesq:
It's there a way to mark all email messages read with the stock email app? There's a "select all" option on the menu in my Droid Maxx, but that doesn't exist in the version in the gapps package on my Xoom.
[Xoom Android Development] bigfootnmd:
CM11 and the Yahoo weather Widget

After my now CM-11 Xoom tablet starts up the screen is locked and it displays a little Weather Widget from Yahoo. The Widget does have my correct location. But, there is one small issue (which I can live with if necessary). The Widget displays the temperature in Celcius. I live in the USA and we never adopted the Metric system. I do know that OC is Freezing and 35C is very hot. I have looked and have not found any

app or settings option in Settings for this WIdget. is there is anyway to switch from Celcius to Farenheight?
[Xoom Android Development] webeougher:
Put the CLock widget (it's built into CM) on one of your home pages. It will give you setup options, under Weather Settings, uncheck the box that says "Use Metric" and you should be good, even if you remove the widget from your homescreen.
[Xoom Android Development] burgi400:
FCs using 3g

Yes, since the last 3 versions. I think it is 3g, very unstable, especially in the last version. Permanent switching from umts to 3g or loosing signal. To clarify: my handy (same provider) does not have any problems.

Most FCs by using browser (Opera, Chrome, Stock) or Feedly.
[Xoom Android Development] webeougher:
http://xdaforums.com/showthread.php?t=2635282

Read the pre-requisites at the beginning, leave out all the stuff that doesn't apply to BigPart, and then skip to Stage 4.

Oh, and I'd recommend using Helium instead of/along with Titanium. Backup to your external SDCard. Because you're going from one major release of Android (JB) to another (KK), using Titanium may give you FCs.
[Xoom Android Development] pots22:
Try the Omni Rom Everest from the 07/02/2014 the 3g is very stable now
[Xoom Android Development] slapheady:
under settings > lock screen > Clock Widget > Weather Panel there's a tickbox option for "use metric".
[Xoom Android Development] new-noob:
hey, where is link to gapps ?

thanks :)
[Xoom Android Development] pots22:
Here: http://xdaforums.com/showthread.php?t=2397942
[Xoom Android Development] bigfootnmd:
Thanks!

I no longer have to do the math to convert Celcius to Farenheight.
[Xoom Android Development] HuckFinn:
Thanks for the link. Since I have a Wingray I have not read any of the Stingray threads, your step-by-step was exactly what I was looking for. Installation went flawless and was a lot faster than I expected.

Also thanks for the hint on using Helium, it is restoring most of my apps right now.
[Xoom Android Development] tracker01:
i don't have 3g Xoom i only have wifi version.
[Xoom Android Development] HuckFinn:
That is what I have and is referred to as "Wingray". This ROM works perfectly on the WiFi only Xooms. I just went through the process of updating to this ROM, if you go back one page you will see the step by step instructions.
[Xoom Android Development] parkentosh:
This ROM just keeps getting better with every update. Perfect!