yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Q&A, Help & Troubleshooting] Ace42:
The Nexus 9 doesn't seem to be a priority for Google. Even the Nexus 7 2013/2012 have received 5.1 despite being much older than the N9, they should at least give a release window for the 9 even if they are unable to provide immediate updates. Although, I think the user base for the Nexus 9 might be small, so perhaps Google doesn't think it's necessary to cater to N9 users at this time.
[Nexus 9 Q&A, Help & Troubleshooting] petkyrk:
I believe this too, due to the extremely low "nexus market share" this device has. Anyway, eventually it will be released.. Let's hope that it will be a final version. There will always be bugs, this is how software development works. :)
[Nexus 9 Q&A, Help & Troubleshooting] borchgrevink:
The SoC is a catastrophic choice. No other devices use it, I think, and development will be less than nothing from Nvidia.
[Nexus 9 Q&A, Help & Troubleshooting] bobjbain:
Umm, my Nexus 7 (2013 variant) still hasn't got 5.1 either....
[Nexus 9 Q&A, Help & Troubleshooting] doitright:
Reports of "memory leak" from morons who don't even know what a memory leak *is* are meaningless. Your assumption that "they realized that there is a memory leak in 5.1" is without merit.
[Nexus 9 Q&A, Help & Troubleshooting] petkyrk:
I ve had memory leak on my nexus 6 with its latest 5.1 version 3. I ve seen it with my eyes. Also the same problem on my girlfriend's nexus 5. And trust me, I know that I am looking at
[Nexus 9 Q&A, Help & Troubleshooting] doitright:
lol. So does "everybody" who doesn't understand Android memory management.
[Nexus 9 Q&A, Help & Troubleshooting] petkyrk:
Right, u know better... There is memory leak , its there. Whether u like it or not. The only thing that u have been doing is being acting like a smartas* , next time try to explain if u will.
[Nexus 9 Q&A, Help & Troubleshooting] doitright:
Whatever pal. Believe whatever you like.

But the fact that neither you nor anyone else has actually *demonstrated* a memory leak really says a lot about how well (or rather poorly) you understand.

In fact, first thing I would do is challenge you to explain (without looking it up) what a memory leak *ACTUALLY IS*, as well as *prove* that there is one in play.
[Nexus 9 Q&A, Help & Troubleshooting] FrankBullitt:
Before mocking others, did you consider looking on google's bugtracker and checking the fact that someone has demonstrated the memory leak on the 5.1 and that the bug was acknowledged and later marked as "solved" with no timetable for public release of the solution?

Because, you know, doing that would save you from looking really bad around here.

PS: I'll give you a hint: Issue 159738.

So, since I don't understand android's memory management, could you please help me and describe me the reasoning used by google behind their decision of using a more aggressive approach of the garbage collector in 5.1 to increase the free memory (not talking about available) and going against the compacting method introduced in ART (in 5.0) to let the long lived objects persist? Because you obviously know what you're talking about...
[Nexus 9 Q&A, Help & Troubleshooting] doitright:
That bug report is actually bogus, since the "evidence" claimed in it is actually indicative of *correct* behavior. The internal "fix" is to change the way that memory consumption is reported.

I will point out response #33: memory consumption is tied to a bad application running. Kill the application, the memory comes back. Now the system sees all the free (aka WASTED) memory, and reloads the recently used applications that it determines have a high probability of being re-started until the memory is again properly consumed. This behavior is PRE-LOADING of applications in order to launch faster when they are requested.

This is how Android works.

It has ALWAYS done this, since before version 1.0.

People have *ALWAYS* complained about this, because they DON'T UNDERSTAND HOW THE SYSTEM WORKS!

This is what happens when you have some worthless CRAP operating system like windows, that can't properly manage memory. People become familiar with the memory usage monitoring that THAT requires, and assume that everything works that poorly.
[Nexus 9 Q&A, Help & Troubleshooting] FrankBullitt:
wow, you have no idea what you're talking about...
[Nexus 9 Q&A, Help & Troubleshooting] rolldroids:
In the issue tracker people say that they need to reboot so there IS something wrong. And, a large amount of free RAM needs to be reported. It is the RAM that COULD be used for anything, it does not mean that it is not used for anything in that moment.
[Nexus 9 Q&A, Help & Troubleshooting] flippingout:
So... Back on topic. I too, would like to know where 5.1 is for the N9. You have to admit for a recently released device, from Google, it is a bit suspicious there is no 5.1 available.

My hope is Google is hard at work getting it just right for the N9 but I have a sneaking suspicion the K1 may have something to do with it. Time will tell.
[Nexus 9 Q&A, Help & Troubleshooting] Moomoomania:
Same. I have a hunch as well that it could be the K1 have something to do with the delay. Regardless, I'm reading for 5.1.1
[Nexus 9 Q&A, Help & Troubleshooting] jami1:
I think it has something to do with the fact that its a one of the first 64-bit tablets, so most of the software has to be 64 bit. The other tablets do not have this problem. this could be delaying development a little.
[Nexus 9 Q&A, Help & Troubleshooting] NYCHitman1:
LOL @ this thread. All I see is bickering from users with no respect for the process. All good things come to those who wait patiently.
[Nexus 9 Q&A, Help & Troubleshooting] Migamix:
patience works, but when owners of a new device get no information told to them on why there is a delay, people are likely to get pissed. google can also just say. the release will be a month from now. google has this thing about saying too little, which makes me wonder how anything gets done... oh yeah, it doesn't, since we are 3 versions behind with no known future . we may be stuck at stock 501 for the rest of this new tablet's life. we don't know. and that is the part that is pissing even me off.
[Nexus 9 Q&A, Help & Troubleshooting] NYCHitman1:
They don't need to say anything, quite frankly. You will get your update(s). There's no law that says they need to notify you or anyone of anything.
[Nexus 9 Q&A, Help & Troubleshooting] Migamix:
who mentioned law? we are all refering to googles hands off approach to its "beta testers" . a little info from a company after we shell out our cash with the ole promise of first updates is what this thread is all about..
[Nexus 9 Q&A, Help & Troubleshooting] NYCHitman1:
Clearly, my point is not being understood. It makes no difference to me, personally.
[Nexus 9 Q&A, Help & Troubleshooting] doitright:
Like I said, you clearly don't understand Android, and don't know what a memory leak IS. Just because you see a few complaints on a bug tracker from people who, like you, DO NOT understand, does not make it so. Just because somebody tags it as 'solved' does not mean that the solution is actually what you might imagine it to be. Most nonsense bugs are "solved" by altering the data being presented to the end user.

That bug report, by the way, PROVES that the bug is nonsense.
[Nexus 9 Q&A, Help & Troubleshooting] Migamix:
so, you are in this thread to troll? nice.

---------- Post added at 14:53 ---------- Previous post was at 14:42 ----------

to my understanding, its just being called memory leak. it appears to be garbage collection related, which can be viewed as a leak or loss of memory. not everyone can fully understand how the devices lack of knowing its OK to free that orphaned memory, can know its not OK to simply call it "memory leak" around some people. I solve my issue with it by running free ram from 3c toolbox every 2 hours with tasked.. it helps for the most part.
[Nexus 9 Q&A, Help & Troubleshooting] FrankBullitt:
edit: whatever dude, you clearly are smarter than everyone else (at google too)...
[Nexus 9 Q&A, Help & Troubleshooting] wifesabitch:
This there some statement or something anywhere where it says Nexus devices are entitled to fast Android updates?

I really don't care if this tablet is ever updated.
[Nexus 9 Q&A, Help & Troubleshooting] foxmeister:
From http://www.google.co.uk/nexus/9/

There are non-Nexus GPe devices that are already on 5.1, which makes a mockery of that statement.

The usual form has been current flagship Nexus phones and tablets are updated before older devices.

The problem is that the older devices already have good stable Android builds in KitKat. The N9 doesn't, and given the issues with 5.01 should have been priority.

Regards,

Dave
[Nexus 9 Q&A, Help & Troubleshooting] mghussan:
calm down people , there have reports of bricked nexuses with update. I think nobody will want that just to get 5.1 . Let them fix the things.
[Nexus 9 Q&A, Help & Troubleshooting] taronas:
Lucky you! There are bugs in the 64bit android that the N9 runs, confirmed in the Android bug tracker, with fixes supplied since many weeks. Google just had to release those fixes finally! Me is affected by the issue that affects any app with sqlite data on the SD storage. A couple of payed apps don't work because of this. I want this fixed, asap.

Google s own advertising about benefits of Nexus are already quoted ... I hope they deliver soon on that

If there were a comparable device featuring a 4 by 3 screen ratio running 32bit Android I would switch any second.
[Nexus 9 Q&A, Help & Troubleshooting] wifesabitch:
There you go, kinda thought people just assumed Nexus devices should get updates first but it was never said. Guess not.
[Nexus 9 Q&A, Help & Troubleshooting] Migamix:
The bricking is on 502 if I read it right
[Nexus 9 Q&A, Help & Troubleshooting] petkyrk:
well, it's ok Google, it's only been 5 months with a buggie version on our high-priced nexus 9... You know, memory leak as well as other bugs, but you know what, it's just a nexus device.. no one expects you to support it with the newest version as soon as it is released.... :laugh:

by the way, galaxy s6 edge has just received android 5.1.1 ... And we, with nexus devices still waiting
[Nexus 9 Q&A, Help & Troubleshooting] petkyrk:
hahaha... guys this unbelievable ! Google is trolling nexus 9 users... Just released the 5.0.2 update.....
[Nexus 9 Q&A, Help & Troubleshooting] mihaicristian:
THANK YOU ! At least someone is on the same wavelength as me !

But really now Google, why the F. did you bring 5.0.2 instead of 5.1/5.1.1 ?!
[Nexus 9 Q&A, Help & Troubleshooting] rolldroids:
It is possibly needed for installing 5.1.x
[Nexus 9 Q&A, Help & Troubleshooting] wingdo:
Also possibly an issue with the Tegra K1 and 5.1.
[Nexus 9 Q&A, Help & Troubleshooting] petkyrk:
I just read this guys, let's hope that this is the case with our nexus 9

http://www.androidpolice.com/2015/05/05/aosp-changelog-posted-for-the-nexus-9-update-from-5-0-1_r1-lrx22c-to-5-0-2_r3-lrx22l/
[Nexus 9 Q&A, Help & Troubleshooting] bobjbain:
That's what I thought..

And that pretty much confirms it, to me anyway..
[Nexus 9 Q&A, Help & Troubleshooting] AstroDigital:
Phandroid says 5.1 or is it (5.1.1) has been released. http://phandroid.com/2015/05/07/nexus-9-android-5-1/

No images on Google's site, seems their source is solid (twitter)
[Nexus 9 Q&A, Help & Troubleshooting] zera89:
hi guys,

i received my new nexus 9 today.

I have updated it to 5.0.2.

Anyone received 5.1.1?
[Nexus 9 Q&A, Help & Troubleshooting] AstroDigital:
No .... they say soon
[Nexus 9 Q&A, Help & Troubleshooting] petkyrk:
Actually they said on their official Google+ account that it will roll out today (on may the 7th) . Up until today, may the 9th, I haven't read of any user that has received a 5.1.1 ota. Google is trolling us
[Nexus 9 Q&A, Help & Troubleshooting] Dudmaster:
OTA is receiving in the UK I believe. Honestly, I never OTA anyway so it doesn't matter, I just wait for the image ^_^
[Nexus 9 Q&A, Help & Troubleshooting] petkyrk:
As far as I can remember my friend, IMG are released 1 day after the first ota. Nothing yet. And I haven't seen 1 reported case of an updated nexus 9. I really hope that I am mistaken and that the ota has already begun
[Nexus 9 Q&A, Help & Troubleshooting] Dudmaster:
I don't think google will release on weekends since it is not a business day, and they won't be able to fix anything incase of a problem
[Nexus 9 Q&A, Help & Troubleshooting] petkyrk:
Guys, 5.1.1 img is available.. Finally. Just flashed it, looks really good. Of course I have to use it for around a week to have a full picture
[Nexus 9 Q&A, Help & Troubleshooting] SLZN:
miracast

Is miracast back at 5.1.1 ?
[Galaxy S6 Edge Q&A, Help & Troubleshooting] jpbl1976:
Does anyone know what materials the home button on the S6/S6 Edge are made of? Is it metal and plastic or metal and glass? I haven't encountered an article that has mentioned this. I have the option of trading in my Note 4 for an S6 Edge and one of my pet peeves with the Note 4/S5 before it is that the home button gets all these hairline scratches after a little bit of use (I've had my Note 4 since mid-October). Naturally, having a better home button would be one small thing tilting the S6 Edge as my Note 4 replacement.

Apple used to have this problem with its home button before they introduced the TouchID sensor which has a sapphire-polymer coating. Since the sensor on the S6 Edge/S6 are supposedly similar to the TouchID sensor, I wonder if Samsung extended the improved build quality of its flagships to the home button. Thanks!
[Galaxy S6 Edge Q&A, Help & Troubleshooting] miantiaoliang:
home button on the s6/s6

i have the question 2
[Galaxy S6 Edge Q&A, Help & Troubleshooting] iunlock:
Yes the home button on the S6 is a different material. I've spent a lot of time with the S6 and as a Note 4 owner, the home button (hairline scratch) issue is one of the main things I was curious about as well. The home button on the S6 feels more like a hard acrylic glass....not quite sure what material it is exactly, but it is noticeably different than the Note 4.
[Galaxy S6 Edge Q&A, Help & Troubleshooting] jpbl1976:
That's great! I guess the only way I'll really be satisfied is to play with it at the shop before I claim my pre-order.
[Galaxy S6 Edge Q&A, Help & Troubleshooting] Goronok:
Just wanted to report that the home button is definitely still fragile. My 6mo old Note 4 has a mint home button, but somehow in 3 days i've managed to scratch my S6e button =/
[Galaxy S6 Edge Q&A, Help & Troubleshooting] ingenious247:
Same here. Had the Note Edge for months, and you have to SWIPE the home button for the fingerprint reader, no real scratches of any consequence. S6, barely a few weeks old, only lightly TOUCH the home button for fingerprint reader, and scratched already. Nice big one, too.
[Galaxy S6 Edge Q&A, Help & Troubleshooting] verngator:
Love my Edge - it was just delivered two days ago - but there was a mark on the button that looked like a scrape. Very small - at first it looked like adhesive that just didn't come off the packaging. I rubbed the spot gently with a soft cloth but the mark remained.

If the phone were a car, I'd describe the mark as something in the clear coat but not deeply in the paint.

Anyway I called T-Mobile the next morning - they shipped a new phone that arrives today.
[G 2014 General] shashi1313:
press the volume key down until you feel vibration, then below the volume bar u can see options like "ALL" "Priority" "None". Select None and indefinitely, now your phone doesn't ring or vibrate.
[G 2014 General] juliopw:
Ok, but you still miss alarms and notification led.
[G 2014 General] aditya.upadhyaya:
Or if you have Xposed, you can use true silent mode module. If you don't, well, I'm sorry, not much out there.
[G 2014 General] akay193:
One more meaningless thread...
[G 2014 General] raju sesharaj:
Thread Reported

Kindly read FAQ Guys or search the forum stop creating useless threads
[G 2014 General] fillipina:
Personally found this information very useful. Can't understand why this is a 'useless thread'!
[G 2014 General] raju sesharaj:
Because Most tech sites have already reported this issue and i think even xda has made mention about and this being a common issue for lollipop has been addressed many times in many threads and people should search for answers before asking a question so only i think it is useless
[G 2014 General] shad876:
You seriously created a thread to tell us what 99% of us already know? Do your research before posting please and thanks!
[G 2014 General] Wolfcity:
https://play.google.com/store/apps/details?id=it.merkcoolapp.silentmodelollipopfree
[Kindle Fire Q&A, Help & Troubleshooting] ingoc:
I have a kindle fire which wasn't doesn't connect to the computer. I get an error message such as "USB device not recognized". I had rooted the kindle fire and I thought that this problem could have been because of the rom or some kind of kernal error so I installed the stock rom thinking that I will just re-root if however the connection problem still was still there. So now I have kindle fire which is not rooted so doesn't have google market and I want to root it however cannot find a way to get it connected. I have tried 3 different computers and many different cables however still no success. I have also tried reinstalling the drivers, turning off and on the kindle fire with the cable plugged in. Could the port on the kindle fire be broken even though it charges fine. Also, would a factory cable help because I don't want to order it if it doesn't work. What other options do I have? I live in UK and this kindle fire is the 1st gen which was only available in US so cannot send it to amazon for checking.

And wireless is can not switch from off to on.

Your help will be appreciated
[Off-topic] Asth:
Hey people. I have discover an awesome game! It it x war clash of zombies or known as COZ:good: you can get it on android or ios. Get it now!

COZ fb pagehttps://m.facebook.com/clashofzombies.

This game is very interesting <3
[Off-topic] cheeze.keyk:
im also playing this game. :o
[Samsung Galaxy Core.] pritesh2209:
Hey guys my device is Samsung Core GT-i8262. I recently rooted my phone and installed CWM v6.0.3.6 via Odin. After that i backed up my stock rom using cwm to both internal and external sd. After finishing backup i rebooted the device and it booted directly into cwm! No matter what i did it refused to load the os. It booted into cwm every single time! I tried to fix it by doing factory reset, wiping cache, and dalvik cache. I also tried exitrecovery.zip, but it didnt work. Then i installed cutom kitcat rom (build 4) but the problem persists. Someone please help me!
[Samsung Galaxy Core.] gody420:
dont use cwm use TWRP in future... now install twrp recovery via odin and reboot it wil b solved if not then flash stock rom....
[Samsung Galaxy Core.] pritesh2209:
I tried with odin. But odin is not detecting my phone. I installed proper drivers and used factory supplied cable.
[Samsung Galaxy Core.] pritesh2209:
Problem fixed!

The problem with odin was fixed. i dont how exactly but i just connected my phone with the computer which i had used to flash the cwm! I think it was either, that the computer has already detected my device one before or simply the updated drivers were properly installed. Anyway it worked and now i am using TWRP and KitCat [build 5] rom by VaibhaV. Works like a charm. Thank you!
[Samsung Galaxy Core.] oppala07:
I am passing through the very same situation, and odin don't recognize my phone to install TWRP
[JASJAR, XDA Exec, MDA Pro Software Upgrading] ultravox:
Hi.

I'm looking forward to update my universal, but as backup I want to have a full original rom just in case I get problems.

I had it, but strange enough, I can't find it anymore. I must have deleted it by mistake.

I can't register to get it because my imei doesn't allow it!!!!!

Could please someone be so kind to uplaod it ?

Thx in advance
[JASJAR, XDA Exec, MDA Pro Software Upgrading] cktlcmd:
Here my friend: ftp://xdaupload:xda@ftp.xda-develop...-uni_qtek_wwe_13077_130176_10900_wwe_ship.exe

---
[JASJAR, XDA Exec, MDA Pro Software Upgrading] ultravox:
As usual very helpful to the community: Thank You!!!!

Note: Yesterday I made a search on the forum by 130177, but i didn't get any good link.

When I saw your post today i remebered the other post you made last week about the same subject. I checked the post and the link was there and also on other post that was connected to the first one.

The search didn't work because I tried 13077 and it should have been 1.30.177!!!
[JASJAR, XDA Exec, MDA Pro Software Upgrading] erasec:
hi at all

thanks thanks a lot...

i have had the same problem, because i have a preowned device...

thank you very very:)

bye
[JASJAR, XDA Exec, MDA Pro Software Upgrading] erasec:
hi

i have a question...

so can i install this rom qtek 9000 also for my imate jjs?

thank you
[JASJAR, XDA Exec, MDA Pro Software Upgrading] vivek_suri_bba:
i am updating the 2.60 rom in o2 exec but its showing error 120 and i am not even able to find out the exe file to correct the problem . so any one here u can help me out in finding the no error upgrading exe file for error 120 :mad:
[JASJAR, XDA Exec, MDA Pro Software Upgrading] CWKJ:
sigh . . .
[JASJAR, XDA Exec, MDA Pro Software Upgrading] arvind09:
Try the new RUU by Olipro,its in the first post in the Universal forum .
[Android General] Ok_Kaleidoscope5109:
Since Version 7.x, it appears that the SystemUpdateService wakelock is being triggered by any custom ROM with that service disabled.

Does anyone seem to be encountering this? And how are you dealing with it?

Recommended Fix:

I personally recommend this band-aid fix for those who are running into it. The pre-requisite is Xposed and Root. Use Wakelock Terminator to terminate the SystemUpdateService wakelock for Google Play Services. This kills the wakelock and gives me the battery drain that I had before the 7.x update.

I see others recommending more drastic approaches like denying the Keep Awake permission for Play Services, but that could have other adverse effects. Furthermore, Play Services needs keep awake permission for other activities BESIDES the SystemUpdateService wakelock. My fix addresses the problem directly, whereas killing Play Services entirely is doing more than it needs to. I find this similar to the analogy that I make with dealing with a faucet leak. Killing Play Services is like shutting off the water main to deal with a faucet leak. If you want to deal with not being able to flush the toilet or shower, then maybe that's an acceptable solution.

Edit 25-MAR-2015: This bug seems to be affecting custom ROMs, but CM has already patched this For CM11, see commits http://review.cyanogenmod.org/#/c/91881/ and http://review.cyanogenmod.org/#/c/91882/. For CM12, see commits http://review.cyanogenmod.org/#/c/91021/ and http://review.cyanogenmod.org/#/c/91579/.

The best fix if you're on CM is to use a later build of CM.
[Android General] esklarski:
This seems to be a widespread problem for those of us with rooted handsets. I have yet to find a decent solution myself. I'm running Cataclysm ROM on my Nexus 5.

What I've been doing is using a task killer to force close Play Services every time I reboot. Play Services automatically restarts, and then seems to be fine.

I get three indefinite wakelocs on each boot:

SystenUpdateService

EventLogHandoff

CheckinService

No matter what I enable/disable these come right back on tbe next boot. I hope this isn't something Google planned to discourage rooting. Would be a ****ty Apple'esque move if so.. Fingers crossed it's just a bug.

This topiic is clogging up a lot of other threads so lets try and move the discussion here.
[Android General] mdsenn:
Posting in an attempt to raise awareness of this issue. Looks like it was widespread in past versions of Google Play Services (internet is full of discussions from a few years ago).

Experiencing same issue with Cyanogenmod 12 on Galaxy S5- systemupdateservice is the only "inappropriate" wakelock I'm dealing with.

Note: I tried to run autorun manager and "uncheck" the individual services related to this, but it won't let me uncheck- even with the modify system level services option enabled.