yashsingh1/xdaforums huggingface dataset:
[Xoom Android Development] webeougher:
I've used Google Cloud Print with no issues.

---------- Post added at 11:10 AM ---------- Previous post was at 10:56 AM ----------

Which rom were you running prior to this? I'm in the camp with no data. I enabled the testing menu and my IMEI and phone number are both shown as unknown, but by changing the radio to LTE/CDMA/EVDO, I can get it to recognize the IMEI, phone number, and carrier, but I still can't get data and when I reboot, it's back to all zeroes in the IMEI.

If anyone else is having data issues and wants to try the testing menu, with the tablet turned on, hold both volume buttons and press and hold power until the tablet reboots. In your app drawer, an app called Field Utils (red Moto M logo) will appear. The first two options will cause a force close, but the third option is the hidden dialer menu you've probably seen on your phone at one point or another.
[Xoom Android Development] saintanthony:
Hmm, which GAPPS package did you use? Or did you just install it out of the app store?
[Xoom Android Development] SleepyS40:
I started with pa gapps mini modular. It has hangouts in it by it has been updated through the play store once. Hope this helps.
[Xoom Android Development] drewski_1:
They took out Tablet UI code in 4.4 (merging of Nav & Status Bars on the bottom), but the button position can be changed by the ROM.

I have ThunderKat on my N10 and it let's you choose the Nav button position. EOS4 also did this without implementing the full Tablet UI.

You still have the status bar at the top of the screen, though.
[Xoom Android Development] xyrcncp:
I was running the 10/28/13 CM10.1 Stingray nightly.
[Xoom Android Development] webeougher:
Thanks. I'll try flashing that and see if I can get data back when I go back to CM 11.
[Xoom Android Development] armido:
Update #118 and SuperSu..

Update #118 includes an updated SuperSu with no apparent way to change SuperSu settings. This is problematic because my Linux Deploy installation fails to start after the update. Reverting to UPDATE-SuperSu-v1.86.zip doesn't work and the result is loss of root. Only way to restore root and Linux Deploy functionality was to fallback to #115, reinstall gapps and the UPDATE-SuperSu. Each new version of Kit Kat appears to be taking away root functionality. What's going on here?
[Xoom Android Development] drewski_1:
Koush's Superuser is built into the CM11 ROM so there's no need to flash SuperSU. Just ROM & GApps.

Access Superuser settings in System Settings close to the bottom above About Phone.
[Xoom Android Development] notbrodie:
become familiar with gesture controls. I use "GMD gesture controls" from play store. it works great on xoom. multi touch gestures are the future of tablets

Sent from my Nexus 5
[Xoom Android Development] Blondblueyed_girl:
[QUOTE=webeougher

Thanks webougher but I have a network printer connected to the router. Although cloud printing might work (not tested it yet) I wanted to get what I had before with EO3, that is direct printing via wifi. Printing works OK on my nexus 7
[Xoom Android Development] webeougher:
That's how mine is set up. If your HP printer is network connected and less than 18 months old, it's very likely that it's compatible with Google Cloud Print. It's exactly the same thing that you're doing with the HP app, except it's a Google app instead of an HP one, and it works with multiple brands of printers. I have mine currently linked to an HP Deskjet 6600, an Epson Workforce 645, and the monstrosity that I have in my office as well. It's very convenient.
[Xoom Android Development] superbay:
Yep. Combined that one and auto hide soft key still from goodmooddroid and my screen feels larger :)
[Xoom Android Development] webeougher:
Update: Went back to normal partition, installed the 10/28/13 CM10.1 Stingray nightly, but could only get 3G. Whatever, that could be because of where I'm located, even though I had 4G previously running EOS and later after going back to stock (rooted) 4.1.2. Repartitioned to BigPart again, installed the same Stingray nightly with the CM 10.1 BigPart kernel - no data. I'm wondering if that's because the CM 10.1 BigPart kernel is for Wingray, and, if so, if there's one available for Stingray. I'm going to keep experimenting and see if I can figure this out, because I'm fairly confident that I'm not the only one with this problem.

Update 2: Flashed CM 10.1 10/28 nightly, followed by ElementalX-Xoom kernel and Unified GApps. Data worked! (Still only 3G, but progress is progress.) However, after flashing the latest CM 11 build, still no data, even after rebooting and then rebooting again to flash the ElementalX kernel. The search continues...
[Xoom Android Development] matt4321:
Hey, I made the CM10.1 BigPart kernel for wingray, on github CM use the same kernel for wingray, stingray and everest. So I'd have thought it would work.

If people really want a stingray version I could pull in CM10.1 repos for stingray, add the patch and compile. I would need a tester though
[Xoom Android Development] webeougher:
Just updated my post that you quoted - by flashing the ElementalX kernel, I was able to get data on CM 10.1 while BigParted. I really appreciate the offer, though, but since I think I remember reading that you got a Nexus for Christmas, go ahead and enjoy that, my friend. In actually, I'm trying to get data on either CM 11 or Omni but I was trying to reproduce the conditions that some others Stingray users were able to flash from and get data on those particular roms, hence why I tried CM 10.1. In determined enough that I'll come up with something eventually.

If someone could get therealjumy to update the initial BigPart post to include a link to the ElementalX BigPart kernel for Stingray users, though, that might save someone else some aggravation.
[Xoom Android Development] hochoch:
I installed xposed then gravity box for kk. I only played around a little but there are nav bar tweaks you can do such as reducing size and adding buttons. I added a back/kill button all the way the left. Still has the stock ones in the middle but at least it's something. I can upload a screenshot if anyone's interested
[Xoom Android Development] armido:
Tried viewing logs. Couldn't. Did not see any option for changing settings...

I found the SuperUser module in Settings, but could not view the logs and there was not as far as I could tell any way to change SuperSu settings. I'll give it another go.

Thanks.
[Xoom Android Development] armido:
Success, but still not able to view log content...

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.
[Xoom Android Development] ankorez:
thank you...

i have flash "TWRP 2.6.3.0"... but it's ask me a password when enter in recovery????????

don(t understand..
[Xoom Android Development] audioblivious:
From what I understand you just cancel out and continue on
[Xoom Android Development] ankorez:
if i do it

i can't do nothing after

all my partitions is 0 mb...
[Xoom Android Development] notbrodie:
after cancelling password, format EVERYTHING except sdcard

Sent from my Xoom
[Xoom Android Development] xyrcncp:
Why don't you try flashing it with a stock kernel? I'm on stock kernel, through EOS (3 and 4) and variations of CM10.1. I'm not saying the kernel is the issue, but starting fresh with no mods may help eliminate posibilities. FWIW the GApps I used were PA Gapps Google Stock Package
[Xoom Android Development] bmecchi:
Hi Guys,

This new CM11 for Xoom is great! My Everest is better then ever.

I still have a minor bug, once some times I can't wakeup the tablet by pressing power button. It doesn't happened at the old ROM. When it happens it may be necessary to robot (power + volume up). But as I said it's minor report for me.

One thing I really want to say is about the dock on the launcher. I have a problem there, it holds apps button plus 8 apps, 4 on each side. The two on the very right always desapear once Xoom is turned on or it reboot. (as attached photos). Any one get same?

Yes, I can change launcher to Nova or other one else but, as we don't have avaite launcher for tablet yet, I'm still trying the launcher who cames with CM11.
[Xoom Android Development] drewski_1:
Is the BigPart'd stock kernel in the main BigPart thread? I don't see it, but I'm interested to try it out to see how it compares, if you have a download link
[Xoom Android Development] webeougher:
The first time I flashed CM 11, I was coming from stock rooted 4.1.2 and I got no data, even though I only flashed the ROM and the PA GApps. So I went back through this whole process and was able to get data on CM 10.1 BigPart, which was the first time I could get data after BigPart. From there, I did a full wipe, installed CM 11 and PA GApps, and rebooted. No data. So then I flashed the ElementalX kernel, which is how I was able to get data on 10.1, but still no luck. I had a funeral today but I plan to get back to experimenting tomorrow.
[Xoom Android Development] ankorez:
i have error on format cache but it's ok i can navigate on sdcard and install

Thank you
[Xoom Android Development] notbrodie:
you are using bigpart twrp, correct?
[Xoom Android Development] ankorez:
absolutely !

i can install CM11 but not boot :( stuck at CM logo

i can't mount partition cache for wipe...

thank you for your help

i continue investigates

EDIT -------------------------------------------------------------------------------------

after reboot i have wipe cache again and it's worked !!

i have Android 4.4.2 on my xoom

thank you guy
[Xoom Android Development] no*boundaries:
latest update issue

Issue resolved, regarding backup to Google! With gapps change. Backup transport .apk wasn't in OK aaps I had.
[Xoom Android Development] no*boundaries:
xoom sleep screen has a very white flash

Last couple of Roms appear to have a graphics issue, when Xoom goes to sleep a horizontal bright white thin line appears along with some very scale bars. Anyone else have this?
[Xoom Android Development] spoooky1:
Go in Settings -> Display & lights -> uncheck screen-off animation ;)
[Xoom Android Development] emaxxim:
Hii everybody, I've some issue with CM11 and KitKat in general. The lockscreen stays in panoramic view, when I rotate the Xoom nothing happens, the screen have the same view. Every time I reboot the Xoom the last icon on the right on the navigation bar disappear, I don't know the mistery. Any suggestion?
[Verizon Samsung Galaxy S 4] A1C_Malone:
i have a galaxy s 4 verizon i have mdk and i have tried unrooting it because my friend tried rooting it while i was gone and messed up the process but im using odin3.07 and im getting this.

<ID:0/007> Removed!!

<ID:0/007> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/007> Odin v.3 engine (ID:7)..

<ID:0/007> File analysis..

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

<ID:0/007> Firmware update start..

<ID:0/007> sbl1.mbn

<ID:0/007> NAND Write Start!!

<ID:0/007> sbl2.mbn

<ID:0/007> sbl3.mbn

<ID:0/007> rpm.mbn

<ID:0/007> aboot.mbn

<ID:0/007> FAIL! (Auth)

<OSM> All threads completed. (succeed 0 / failed 1

my phone says start [224,1440]

sw rev. check fail : fused 5, binary 1

and ive tried 2 other stock files and i still get the same thing i even tried a Me7 to please help
[Verizon Samsung Galaxy S 4] scryan:
Im slightly confused?

You were still on MDK, the original firmware the phone shipped with after this long, but you were not rooted?

Your sure you were still on MDK?

I haven't played with odin a ton, but odin anything but MDK if that is really what your on. That is the ONLY firmware that has a bootloader bypass to allow a full custom recovery. Later base bands cannot, and must use safestap which only allows roms based on the kernel of the phones latest update (no aosp, cm, custom kernels, ect...)

More recent updates blow a fuse in the phone and once that fuse is blown you can only flash the current or newer updates, and there is no current way to go back to the MDK firmware.

How did you friend try and flash? What went wrong?

From the log, I hope I am wrong, but it looks like your friend already updated you phone.

But I believe it failing at aboot and complaining about fuses and binary switches is exactly what that means...

If he flashed Mk2 or MJ7 in an attempt to follow the info on rooting those, then those will be the only one you can currently restore to, in which case look up the guide on how to update to MJ7 and root, and follow the links for the MJ7 odin file, saferoot & safestrap.

Wait for someone else to confirm though. Hopefully I am wrong, and I would hate to lose an MDK device on my advice :P
[Verizon Samsung Galaxy S 4] A1C_Malone:
<ID:0/007> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_u ser_low_ship_MULTI_CERT.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/007> Odin v.3 engine (ID:7)..

<ID:0/007> File analysis..

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

<ID:0/007> Firmware update start..

<ID:0/007> sbl1.mbn

<ID:0/007> NAND Write Start!!

<ID:0/007> sbl2.mbn

<ID:0/007> sbl3.mbn

<ID:0/007> rpm.mbn

<ID:0/007> aboot.mbn

<ID:0/007>

<ID:0/007> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

<ID:0/007> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> VRUAMDK_NoWipe.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/007> Odin v.3 engine (ID:7)..

<ID:0/007> File analysis..

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

<ID:0/007> Firmware update start..

<ID:0/007> NON-HLOS.bin

<ID:0/007> NAND Write Start!!

<ID:0/007> aboot.mbn

<ID:0/007>

<ID:0/007> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

Im using Odin v1.85

this what i get from trying mdk and me7
[Verizon Samsung Galaxy S 4] A1C_Malone:
he said this is the youtube video he followed to do it https://www.youtube.com/watch?v=uii_mYm8IGE
[Verizon Samsung Galaxy S 4] scryan:
Yeah that is the root method for the latest official firmware...If you had MDK you had the oldest firmware avalible (really really good thing)

Do you know if he used odin at all? are you sure you were on MDK originally? This would mean that you got the phone when it first came out and never took an update?

Again, it looks like your phone was updated to MK2 or MJ7, the latest official firmware. If that is true only one of those two restore files will work with odin as you can only odin to what you currently have or newer...

If you don't ever care about custom recovery and only want root, you probably fix it by downloading MJ7, and using odin to flash that. (As I said, the thread on how to update to MJ7 and install safestrap/HD11 will have a link for that file and is on the first page)

IF YOU HAD MDK AND WANT CUSTOM RECOVERY DO NOT FLASH ANYTHING WITH ODIN OTHER THEN MDK. Wait till someone smarter then me can help you figure it out, and make sure your friend hasn't already updated you beyond being able to go back to MDK.
[Verizon Samsung Galaxy S 4] A1C_Malone:
where can i download mj7 or mk2 stock i have a verizon s4
[Verizon Samsung Galaxy S 4] thunderbls:
Sounds like you may want to follow this... If a newer firmware was attempted to be flashed..http://xdaforums.com/showthread.php?t=2579278. IF NO LONGER MDK AVAILABLE FOLLOW THOSE STEPS.
[Verizon Samsung Galaxy S 4] Von Franklin:
use Kies and get a factory clean install
[General Topics] toshibathomas:
We all want good battery life, that is a given. With the large batteries and the optimized operating systems versions most of us are running today, we all should have it. But often times we don't, why not? Apps with services causing wake lock issues are often to blame. So, I wanted to start this thread to post all apps we have found to either avoid or with workarounds to prevent bad battery life from ensuing.
[General Topics] Qas.:
Greenify, Disable Services...Need root though I think
[General Topics] kap19:
The paid version or the free one?
[General Topics] Scripts:
Make sure no apps are running in the background, if you're not gonna be using your phone for a few hours turn your brightness to the lowest possible, make sure your screen shuts off in less settings ect.

Sent from ALCATEL One Touch Fierce
[General Topics] vzsisp:
just dont run apps in background, it will drain your battery drastically
[General Topics] galaxytab2user:
both have the same funcionality. the paid one is just a donation to developer, if you like his app.
[General Topics] Cyboy:
Is it a 'to kill' or 'most wanted' list bro? How many $'s will be paid?LOL.. :P

Ok, as u can search in xda , there are alot of posts ppl complaining about some cpu and battery hunger background processes and apps .

In my case these was built in "download manager " and "audio effect service".

I removed the 2nd one permanently!

So?
[General Topics] droiddekka:
I usually turn auto sync off
[General Topics] robrobbbbb:
facebook...it consumes about 20% of my battery even without opening it once

unistalled it, no actual need of checking it on the phone
[General Topics] fousekis21:
I agree, facebook its battery sucker...
[General Topics] Badbob117:
Wifi, Scrreen brightness, Auto sync, GPS and games in general seem to be the big culkprits for my battery draining. Even simple things like turning auto rotate off can help a tiny bit for performance and battery life. Limiting your amount of active widgets and screens animations on your fancy launcher can cut down as well on battery and performance. Certain IM apps like facebook chat, skype, and a ton of others will kill your device fast. Google + is known to be a bandwidth hog and batttery killer. I noticed when im browsiing youtube simple things like turning off hd will dramatically help improve battery life because your network is not sucking as much bandwidth.

There is all kinds of stuff to do . It is a constant battle. :)
[General Topics] akashtaker001:
Greenify app & use Lean Kernel if possible
[General Topics] Sanchito731:
Like many have said, apps running in the background are the main culprits of a shirt battery life. Unless you feel those apps are truly essential I recommend uninstalling those apps.
[General Topics] maches:
Using greenify like most of you guys. Yesterday I installed lux lite on a new custom ROM and noticed it was responsible for about 25% of my battery usage over about an hour with the screen on. Anyone with experience with this app know if this is normal behavior?
[General Topics] flightwatch:
No issues with lux lite here. I got the paid version and the dusk/night features are great
[General Topics] SpikaDevTeam:
USB Chargers

I don't know if anyone realizes this, but what I have experienced with my phones(from Nexus One - Nexus 4) I have noticed when I charge my phone through a computer the battery seems to go out faster. When I connect it directly to power it lasts much longer.

Has anyone else noticed this"?
[General Topics] vamosfener07:
Only close apps

GT-S5830i cihazımdan Tapatalk 2 ile gönderildi
[General Topics] bliblidi:
yahoo messanger if signed in it's a big eater
[General Topics] timmy5822:
some antivirus and the Android System, some very drain battery, Custom ROM the best!
[General Topics] busote:
install battery calibration
[Sony Xperia Z Ultra] cavallino33:
I just got my Z Ultra GPE. I have the incipio dualshine case for it but the included screen protector is not very good and I ended up with a pretty poor application. I ordered a glass protector from Glass-M but it won't be here for a couple weeks. Do you guys think I can get by without a protector without scratches until the glass comes? I only really put it in my pocket. One edge of the protector I have didn't adhere properly and I'm afraid fuzz/dirt will get under and scratch it. Other option is to just use my S4 until I get the better protector.
[Sony Xperia Z Ultra] LordManhattan:
I've had my Ultra since september and i don't have a single (noticeable) scratch on the front (i'm not using any additional protection). You'll be fine, but accidents happen, so it's not possibble to tell if yours will be scratch free in a few weeks. I do have a couple of scratches on the back though, but i couldn't care less.
[Sony Xperia Z Ultra] blueether:
[MENTION=4642591]hamdogg[/MENTION] mentioned an easy way to apply the protector, use water - added bones is the phone is waterproff :D

you should be able to remove and reapply the protector.
[Sony Xperia Z Ultra] SpyderTracks:
I've used mine since September with no case or added protection. Like [MENTION=655433]LordManhattan[/MENTION] no scratches or wear at all. Dropped it a couple of times without issue.

Worth adding I dont use a stylus or pencil or anything other than fingers, pretty sure that would degrade the film pretty quick.
[Sony Xperia Z Ultra] keithleyson:
I can't see scratches on mine when I am using it. But turn of the screen and swing the phone side to side until the light hits it just right and I see all kinds of fine scratches. How easy is it to scratch? I'd say very easy. And it's not just fine scratches that plague this phone but also the fading of the oleophobic coating. You'll notice the part of the screen where you constantly touch gets rougher compared to the rest of the screen. In the end I'm just waiting for mine to scratch to the point where I will have to remove the ASF.

ಠ_ಠ

On mobile....
[Sony Xperia Z Ultra] cavallino33:
Ok thank you all for the feedback. I decided to just use it. If it's something that will scratch in 2 weeks of light use and no accidents I'd just assume return it.
[Sony Xperia Z Ultra] martin132014:
Can anyone share how zu will look like if you remove the asf.....if the sony logo is not their.... It will be a little weird......
[Sony Xperia Z Ultra] LordManhattan:
You are correct, the Sont logo will be gone on the front, but the Sony and Xperia logos on the back will still be there. Weird? There are several phones out there without any branding on the front (iPhone *cough*), so i can't see why it's weird, but you have your own opinion of course :p
[Sony Xperia Z Ultra] martin132014:
Well it will be look premium if the logo can be seen on the front.....i put a cover on the back so people dont know what my phone model is.....sometimes people mistaken for Chinese model because no model and Chinese manufacturer often make cheap big phone.....my asf got scratch and i eager to take it off...but the remove of the logo and some people said that the screen is not that great to feel is what holding me back.....the aftermarket screen protector is not take full of the screen and their is a cut on the led and sensors..... Even for clear one...so i dont like it a little....i prefer not to use any at all but just the screen but what bad review of the glass....make me scared...... :-/