[Q&A] [ROM][4.4.4] CyanogenMod 11.0 - Wingray Stingray Everest - bigPart

[the_bartman]

Kernel version?

The ROM description in this thread says, that kernel ElementalX-Xoom-2.1 by flar2 is used.
If i type uname -a the following kernel description appears:
[email protected]:/ # uname -a
Linux localhost 2.6.39.4-ElementalX-Xoom-2.0+ #1 SMP PREEMPT Sun Nov 30 19:34:02 CET 2014 armv7l GNU/Linux

Is this the latest ElementalX-Xoom-2.1 kernel from Dec. 10th 2014?
Is the actual Kernel the GPU overclocking one?
There is no /etc/elementalx.conf configuration file. How is the kernel configured?

Thank you in advance.

Cheers, Bart

 

[the_bartman]

Some USB OTG problems...

Since moving from CM10.1 to CM11 some USB OTG functionality seems to be missing.
With Xoom (MZ601) stock ROM 4.0.4 and CM10.1 (experimental) i could use a RTL2832 USB stick together with some software defined radio apps (like SDRTouch and Wavesink Plus). Works fine so far. Since CM11, the DVB-stick seems to be recognized by the kernel:
<6>[ 5400.965924] whisper_notify: accy=USB host
<6>[ 5400.966622] cpcap-otg cpcap-otg: SUSPEND --> HOST
<6>[ 5400.972103] tegra-ehci tegra-ehci.0: Tegra EHCI Host Controller
<6>[ 5400.972867] tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 2
<6>[ 5401.042359] tegra-ehci tegra-ehci.0: irq 52, io mem 0xc5000000
<6>[ 5401.065351] tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
<6>[ 5401.066043] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 5401.066396] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 5401.066968] usb usb2: Product: Tegra EHCI Host Controller
<6>[ 5401.067508] usb usb2: Manufacturer: Linux 2.6.39.4-ElementalX-Xoom-2.0+ ehci_hcd
<6>[ 5401.067811] usb usb2: SerialNumber: tegra-ehci.0
<6>[ 5401.072954] hub 2-0:1.0: USB hub found
<6>[ 5401.073296] hub 2-0:1.0: 1 port detected
<6>[ 5401.478864] mdm6600_wake_work: Call usb_autopm
<6>[ 5401.592347] usb 2-1: new high speed USB device number 2 using tegra-ehci
<6>[ 5401.674048] usb 2-1: New USB device found, idVendor=0bda, idProduct=2832
<6>[ 5401.674335] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 5401.674609] usb 2-1: Product: RTL2832U
<6>[ 5401.674754] usb 2-1: Manufacturer: Generic
<6>[ 5401.674901] usb 2-1: SerialNumber: 77771111153705700

When i try to start the SDR app, i get the error message, that no device could be detected. The driver (https://play.google.com/store/apps/details?id=marto.rtl_tcp_andro&hl=de) says it loads and starts, but it does't work.

I got another USB OTG problem with USB Midi. I use a Teensy 3.1 as a generic USB Midi device (works great under Win7). The device is recognized too:
<6>[ 5781.251045] whisper_notify: accy=none
<6>[ 5781.251414] cpcap-otg cpcap-otg: HOST --> SUSPEND
<6>[ 5781.251559] tegra-ehci tegra-ehci.0: remove, state 4
<6>[ 5781.251760] usb usb2: USB disconnect, device number 1
<6>[ 5781.305093] tegra-ehci tegra-ehci.0: USB bus 2 deregistered
<6>[ 5789.309328] mdm6600_wake_work: Call usb_autopm
<6>[ 5790.745497] whisper_notify: accy=USB host
<6>[ 5790.746174] cpcap-otg cpcap-otg: SUSPEND --> HOST
<6>[ 5790.750588] tegra-ehci tegra-ehci.0: Tegra EHCI Host Controller
<6>[ 5790.751214] tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 2
<6>[ 5790.825044] tegra-ehci tegra-ehci.0: irq 52, io mem 0xc5000000
<6>[ 5790.845008] tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
<6>[ 5790.845316] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 5790.845665] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 5790.845859] usb usb2: Product: Tegra EHCI Host Controller
<6>[ 5790.846203] usb usb2: Manufacturer: Linux 2.6.39.4-ElementalX-Xoom-2.0+ ehci_hcd
<6>[ 5790.846395] usb usb2: SerialNumber: tegra-ehci.0
<6>[ 5790.848581] hub 2-0:1.0: USB hub found
<6>[ 5790.848811] hub 2-0:1.0: 1 port detected
<6>[ 5791.335168] usb 2-1: new full speed USB device number 2 using tegra-ehci
<6>[ 5791.602907] usb 2-1: New USB device found, idVendor=16c0, idProduct=0485
<6>[ 5791.603469] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 5791.603761] usb 2-1: Product: Teensy MIDI
<6>[ 5791.604258] usb 2-1: Manufacturer: Teensyduino
<6>[ 5791.604536] usb 2-1: SerialNumber: 803180
<6>[ 5791.739959] generic-usb 0003:16C0:0485.0003: hidraw0: USB HID v1.11 Device [Teensyduino Teensy MIDI] on usb-tegra-ehci.0-1/input1

All the apps capable of using USB Midi are saying "no device connected".

The third problem:
If i connect the Teensy Midi device, i get no audio anymore. Seems, that the Xoom thinks it is put into a audio dock and tries to di the audio output via the externa audio connection.
There seems no property in the settings, where i can say to play audio via internal speakers if plugged into a dock (which i will use to connect USB devices over USB OTG).

Any ideas?

Thank you in advance.

Cheers, Bart

 

[Ali3n0id]

Can someone point me to the smallest gapps like micro for this ROM?

 

[pelzi]

CM 11 on encrypted Xoom Everest

Surprisingly, nobody seems to care - but neither the ex-official CM10 nor this CM11 build work with encrypted Xoom devices. More specifically, encrypted devices will show a message that no SIM card is available and will have no mobile network capabilities.

It is possible to resolve the situation by hacking and flashing the boot image - or, of course, building a patched version of CM 11.

The problem has been discussed for CM 10 in this issue: https://jira.cyanogenmod.org/browse/CYAN-3388

The resolutions quoted there, having a ril-daemon in the service class core, will lead to a device that does not boot. Reason is that ril-daemon will have an open file under /data, therefore unmounting of the tmpfs data partition after decryption of the real data partition, will not succeed, the boot process hangs.

On the other hand, restarting ril-daemon - either by killing in init.stingray.rc, or having it in the service class main, keeps the radio devices in a confused state and is the reason why radio doesn't work in CM 11 as published in this thread.

So, this is my recipe to cure:

1. Patch init.rc: search for service ril-daemon and change its class to core
2. Patch init.stingray.rc: in the "on fs" triggered block, add what's called elsewhere the "obsolete symlink hack"
   

       mkdir /data/misc 01771 system misc
       mkdir /cache/ril 0771 radio radio
       rm -rf /data/misc/ril
       symlink /cache/ril /data/misc/ril

 

[solomoninusa]

Screen gos dark with high graphic games

Does anyone have the same problem like me? I can't play racing games eg Asphalt 8 etc cos my screen goes dark.
Is this a bug problem, my device or i should try another rom?

 

[szabeee]

I'm playing need for speed, and that's working

 

[lothian]

Constant Random "Unfortunately.... has stopped" Pop-ups

I get constant random pop-up messages alerting that "Unfortunately... " one of the apps i list below "has stopped":
- Google Play services
- com.google.process.gapps
- Browser services
- Clock services
The pop-up's appear only for these four services, shown in order of frequency.

XOOM LTE (mz600) newly flashed-from-stock to "stingray" cm11-20141130-unofficial-1853+0100, twrp2.8.6 BigPart, only GAPPS (pico) installed, with ART enabled. CPU is set at govener: "interactive", 312min, 1400max.

This tablet is barely useable with the constant interruptions from these pop-up's.

How do I resolve this problem?

 

[slybarman]

Does anyone have the same problem like me? I can't play racing games eg Asphalt 8 etc cos my screen goes dark.
Is this a bug problem, my device or i should try another rom?

I have not been able to get asphalt 8 to run on this tablet/ ROM either.

Sent from my note 4 using Tapatalk.

 

[pelzi]

CM-11 final for encrypted xoom devices

Many thanks to Schischu for providing the final snapshot of CM-11. This still has the problem, that no GSM/UMTS radio will be detected, as written in my earlier post.

I patched boot.img within Schischu's archive.
If you're interested, and already installed shishu's update, you might want to exclusively flash the boot partition with the patched boot image.
If you didn't yet install the update, find the repackaged update zip for installation.

The only differences are, as written in my post, certain changes in init.rc and init.stingray.rc in the initial ramdisk.

 

[ZenMyst]

Crashes on Setting Alarm..... And Text to Speach

I an new to all this custom stuff.... And for the most part is works well..... I updated because I thought it would help me be able to use voice to text, which I used to use a lot as I have a disability.
I am assuming though that this is a google/age of the xoom yes? As it no longer seems to work in either stock rom or the custom open source ones. (yes I read to expect this.)

What if any options/alternatives do I have?

CyanogenMod seems to crash on the setting of the alarm Mon through Fri. option.

I also updated because terraria got messed up after an update. I posted about it here but no replies.
http://forum.xda-developers.com/motorola-xoom/help/terraria-colours-gfx-messed-t2973462
While it does not crash my tablet the GFX are all messed up.

Another family member has a Samsung running stock rom of 4.2.2 and at the time I was running 4.2.1 so I thought that was the issue but no...

I notice cm 12 and 13 are out but see no references to it for xoom only 10 an 11. Are there any? or is 11 the latest for xoom?

Most seem to use other custom roms for the xoom but I liked/prefer this one if it is possible.

I could go buy a newer tablet but I just can't seem to part with my xoom wifi. Other that theses issues it has and still does serve me well.

 

[axell16]

low volume

Hi!
Installed the mod on my mz600 and now the volume is lower than it was before with the jellybean. I have found guides how to alter a text file called to3g in device/etc/sound. But that giude was not for xoom and it was for cm12. I cant find neither file or directory on my xoom. Where is the file I have to edit?

 

[johneflik]

OK