yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Brettbesa:
Let's get this out of the way first, nobody here is stupid, we know the L Release is never going to come to the Galaxy Nexus officially. So let's talk about the community. I just have one basic question for our talented devs, what are the odds that a port of L will be able to come to the Gnex and if so, what kind of time frame are we looking at here?
[Samsung Galaxy Nexus] unknownbeing:
Does the Cyanogenmod team do developers previews like this one? We might see it from them.
[Samsung Galaxy Nexus] ashclepdia:
I'm sorry, but this post is exactly what I expected to see today.

so lets get it out of the way.

SURE

we COULD see some 5.0 aosp love(via custom development)

MAYBE.

time frame?

when.source drops, give it a few months at most I'd say

source isn't even CLOSE to ready yet though.

SOOO

let's ALSO look at the past.

which nexus devices, after Google officially dropped support, are STILL ABLE AND ARE running LATEST android version?

ALL of them right?

stability and such isn't a factor for this question, it's IF IT CAN/DOES run newest aosp in SOME FORM.

so I'd say YES gnex WILL see 5.0 in SOME usable form. but asking for ANY "time frame"at THIS POINT since SOURCE ISN'T AVAILABLE YET is kinda pointless.

maybe though, just maybe, there are ALREADY some people at work on getting those "preview" things ported. no matter WHAT, patience and not asking for timeframe/eta is key here ;)
[Samsung Galaxy Nexus] cr08:
I don't normally do +1 style posts, but I am also greatly interested in knowing this as well.

I imagine it is largely going to depend on how much of the underlying kernel and driver interaction changes. I remember on my prior phone, a Droid X which has been and is still locked down, it was generally impossible to get past ICS because of the major underlying changes in JB and not being able to get those on the DX. Granted the Nexus doesn't have this limitation but drivers aren't likely to be further updated and if the kernel goes too far forward it is unlikely to see compatible driver versions for GNex hardware.

EDIT: I should probably say modules instead of drivers. I'm primarily a Windows person PC-side.
[Samsung Galaxy Nexus] InsaneNutter:
Put it this way my 4 year old HTC Desire can run Kitkat then i would be amazed if we didn't end up with some pretty good builds of "L".
[Samsung Galaxy Nexus] Brettbesa:
Thanks for replying! I figured since I looked pretty thoroughly and didn't see a thread for it and thought that having at least one place for Gnex owners to talk about the L release for us wouldn't be a bad thing. I in no way meant to be one of those people who constantly bugs the devs about ETA's, I just meant what were could be expecting in the general sense. Thanks for the reassurance about us getting it, I've just been burned before about support with previous devices when they got past official support. But those weren't Nexii so I didn't know what to expect.
[Samsung Galaxy Nexus] ashclepdia:
yea sorry about my tone in that reply mostly too :D

I'm usually not the one to fly off ranting towards other users actions, at least not on xda(i do #AshRants elsewhere lol)

your question was a valid one, and I know where you coming from when it comes to nom nexus devices and their lack of support, I had a droid x2 that was ORIGINALLY SCHEDULED BY MOTOROLA to have ICS update. which for some reason they just didn't follow through on. Their REASON they said was that "android 4.0+ would not improve functionality of this device"...aka "we don't feel like fixing all the bugs we gave you already with shotty gingerbread releases, and we aren't going to allow you to unlock the device or give you usable kernel source so screw off",...back when moto didn't gaf about the dev communities. they have made huge strides towards mending that relationship. just couldn't believe they had the gall to say 4.0 wouldn't improve the first dual core android device running a tegra2 chipset. bah. ramblings now again from ash.

but yea reason I kinda went off in that reply was mostly cuz I hoped all the other people who were already drooling at the chance to post the exact same things would slow down and think instead first :D it wasnt intended as a personal attack towards you or to start any flamewar on the subject. and judging by your reply you didn't take offense to it anyways, so :thumbsup: :good: :D ;) we all on the same page anyways.

personally, I haven't seen much of the IO stuff about L, I saw mostly design changes, and would like to know more details about it's new features so I'll be digging around YouTube today for recaps and such.

but I'm almost certain that if we don't get some kinda official rom like CM, OMNI, SHINY, PA, etc... building L based.roms for us, then some of our awesomely talented devs will at LEAST get us able to look like we have it, along with SOME if not z MOST functionality of L.
[Samsung Galaxy Nexus] criza:
I also think you guys should be patient. Your life won't be (that ;) limited if there won't be a port of the coming up Android L to our Galaxy Nexus. Just relax.
[Samsung Galaxy Nexus] jsage:
As some have already pointed out, we're unlikely to see Android 5 "officially" ported to our GNex, for pretty much the same reason that we don't have an official 4.4 release for our phone. From ArsTechnica:

TI stopped development for the GNex SoC at Android 4.1. Google and others worked hard to support it for 4.2 and 4.3, but the official TI software was broken by 4.4. The reason that we even have 4.4 custom ROMs is because some kind-hearted person, perhaps a TI insider, released beta or engineering sample software for the SoC. But as we've found, it's not the most stable :(

have a great weekend,

john
[Samsung Galaxy Nexus] akash3656:
You could all complain about TI stopping development and blaming them. The Google Glass uses a not to different TI SOC compared to the GNex has a 3.4 kernel and runs 4.4.2

Now please understand that Google simply ditched us for reasons other than TI stopped developing SOC bla bla bla.
[Samsung Galaxy Nexus] DR3W5K1:
Plus if they didn't drop support after two years android would have alot more bugs in general.
[Samsung Galaxy Nexus] akash3656:
I don't get your logic. And its not like 4.3 is flawless. HD video playback on this device (GNex) lags.

+ if Google themselves show a bad example to OEMs on how long to update devices, expect OEMs to not update devices older than a year. And this makes the whole "android doesn't get timely updates" into a new issue where "android doesn't get updates after a year+ at best".
[Samsung Galaxy Nexus] latenightchameleon:
GNex will never die! :D

(3.5 yrs going strong bby, and thanks to vanir+dirtyv f2fs running better than ever)
[Samsung Galaxy Nexus] quickdraw86:
Indeed. There will likely be somebody out there building from the latest source for this device as long as it's possible to do so, and possibly even if it isn't.
[Samsung Galaxy Nexus] jsage:
Out of curiosity, what would those reasons be?
[Samsung Galaxy Nexus] akash3656:
That's up for you to imagine.... :D

Money, profit, greed? You pick which one. Or make your own reasons.
[Samsung Galaxy Nexus] jsage:
Well, I guess when simple facts aren't sufficient then fantasy must be more believable.
[Samsung Galaxy Nexus] gray bishop:
wow

some of these replies were brutal, sheesh
[Samsung Galaxy Nexus] jsage:
Honest perhaps. It's pretty simple really. The new OS (4.4) has a new kernel. The new kernel requires new drivers. Neither TI (OMAP SoC) nor ImgTec (PowerVR GPU) will supply those drivers.

Yes, an engineer at TI "released" a blob last fall. But it was not release-quality, it was beta-quality. Not everything is a conspiracy; we've just reached the end of the official support road.

On the other hand if one is inclined to run on the bleeding edge and stability is not their primary concern, there are any number of KitKat custom ROMs in which one can indulge.

have a great evening,

john
[Samsung Galaxy Nexus] akash3656:
Ah crap I didn't mean to thank you. Anyway, yea sure remember all those OEMs you blame and all have given everything you've said to a certain product. GOOGLE GLASS. And go and check what SOC Google Glass uses.

Now have fun.
[Samsung Galaxy Nexus] thecoolkid:
Oooh I hope it's all true, and we see the L release on our gnex some time in the future ;)
[Samsung Galaxy Nexus] jsage:
I know what SoC that Google Glass uses. But it has little to do with the fact that Google doesn't maintain the driver internals, and it's apparent that you don't understand what that means.

In any case, I'm sure no one's really interested in our ping-pong discussion. You're certainly free to believe in whatever reality you wish.

have a great weekend,

john
[Samsung Galaxy Nexus] cabalio83:
There are a lot of talented developers working on GNex, I feel somebody is going to make it!

For now let's enjoy 4.4.x roms
[Samsung Galaxy Nexus] jsage:
I just read that OmniROM is picking up the toroplus ball, and that they've managed to come up with the most stable radio integration on AOSP. You might want to try following their effort.

OmniROM

XDA thread

have fun,

john
[Samsung Galaxy Nexus] jsage:
I go away for a few weeks and look what happens ... homebrew OMAP driver for GNEX and a matching toroplus ROM!
[Samsung Galaxy Nexus] valkata1212:
hope

i would like to see my gnex running L >< but it will be a long time till then. #belieaveindevs
[Samsung Galaxy Nexus] CoDe LaZaRuS:
There are lots of amazing roms for our phone and the dev work tirelessly to keep them up to date and bug free. Keeping these things in mind I would say it would take about 2 months (after the offical release of android L) for us to get a taste of android lollypop [emoji16]
[Samsung Galaxy Nexus] grandfirestorm:
i believe there will be a lollipop rom for gnex in a few months, with the new gpu drivers and stuff
[Samsung Galaxy Nexus] tsiliha:
I think too that Lollipop will come to Gnex but for a stable unofficial version, we will have to wait a lot.

I think now, the kit kat versions are in their final fuctioning not lagging format.

This is what we want.

A fast not laggy phone and that's why many are going back to official 4.3 rom in order to be stable and quick.
[Samsung Galaxy Nexus] Shadow Death:
http://www.androidpolice.com/2014/1...roid-5-0-lollipop-source-code-aosp-right-now/

Awww Yeah!
[Samsung Galaxy Nexus] DT84:
So, now that source code is out, is anybody willing to try porting it to the Galaxy Nexus?
[Samsung Galaxy Nexus] seriousia:
http://xdaforums.com/showthread.php?p=56518183
[Samsung Galaxy Nexus] DT84:
Oh dear, I wasn't even hoping for such an early semi working build, thanks for informing me!
[Samsung Galaxy Nexus] Airlibik:
on the 16/11 it's been released a new build with mobile data working but youtube and camera are still not working.

anyway Ziyan on the cm11 thread said that he will continue support gnex for cm12 he will start working hard on it when he will take a break from studying next week.

I Can't wait for it :p
[Samsung Galaxy Nexus] RoadToNever:
Viral works until youtube gets sorted.
[Samsung Galaxy Nexus] Syakir Imran:
Now it more better ..... Thanks to [MENTION=3390093]MWisBest[/MENTION] ... our old gnex can run the latest android ... just need abit fix/improvement ...
[Samsung Galaxy Nexus] idrather:
FML 5.0

I can't wait for FML 5.0 to be stable. Been using CYM 11 for about two months. While it was pretty good at first, it has slow down considerably in the last couple of weeks. This has been similar in my experience with other CYM 11 roms.
[Samsung Galaxy Nexus] JST99:
And...

Now it's stable. :) :) :)
[Samsung Galaxy Nexus] :
It seems to be usable but there are still many things to be fixed, ex:

- sending long SMS (MMS?)

- Torch quick settings toggle doesn't work

- broken offline charging

I also got a force close during my Google account setup when trying to restore settings from another device.
[Samsung Galaxy Nexus] mdki1996:
Not at all, developers that are still defibrillating Galaxy Nexus are so big and I thank very much all of you! [emoji3] Of course they are working to fix bugs as for example low performance of multitasking...flash...etc. Long SMS bug is now fixed in cm12 and liquid

LolliGNexus
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] TabGuy:
For whatever reason I can no longer side load apps. Yes, I've got the checkbox for "unknown sources" checked. I've tried rebooting with it unchecked and then rebooting with it checked.

Here's what happens: I can download and run an apk, like Amazon app store. I click on the APK to install it. It then gives me the normal screen with permissions with the "Cancel" and "Accept" buttons at the bottom. I can tap on the "accept" button all I want but nothing happens. The "cancel" button works but not the "accept."

Other than a factory reset, is their any other solution.

BTW, this is stock without root. I don't want to root.
[One (M7) Q&A, Help & Troubleshooting] mydinosaurwife:
I have tried flashing both sense and Aosp Roms and I cannot figure out what the problem is. Sometimes when I get a phone call whether incoming or outgoing people complain about not being able to hear me. Other times it works perfectly fine though. Anyone have any ideas?
[One (M7) Q&A, Help & Troubleshooting] donkeykong1:
It could be noise cancelation bug. I read somwhere that sometimes it cancels all sounds, not just background noise

Can't think of a good sig
[One (M7) Q&A, Help & Troubleshooting] mydinosaurwife:
Thanks for your response. Is there any known way of dealing with said bug?
[One (M7) Q&A, Help & Troubleshooting] donkeykong1:
I think there are some mods that turn noise cancelation mic off, but I'm not sure. You can search for it, I don't have time right now
[One (M7) Q&A, Help & Troubleshooting] mydinosaurwife:
Alright thank you. I'll see what I can find
[8525, TyTN, MDA Vario II, JasJam General] schwaitz:
I was trying to connect my tytn into my wifi network, the phone detect the network, but appears a invalid IP like 169.254..............and I cant make the phone connect with the correct IP provided by my router. What I have to do to make it connect ???
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
WiFi Connection

Schwaitz

I'm sure you'll get other suggestions to solve this but I have found that sometimes the regular WM5 connection settings get corrupted and it loses the network WEP key. Rather than spend time trying to fix it I use the following freeware download which does it all for you - i.e resolves conflicting IP addresses etc. Only thing you need to enter is your network key. Hitchhiker is designed for those that like to wander about looking for Unencrypted hotspots to log into but it's just as good at logging into work/home networks. It does remember settings and can be set to log in automatically.

The first time I used it, it came up with some error or other but I think I just did a soft reset and it worked fine.

Hitchhiker v0.4 beta 1

• "Summary: "Hitchhiker" helps you to connect your Pocket PC to the wireless Internet. Simply click "Connect" and it will try all nearby public access points. Hitchhiker will handle all settings for you and perform complicated tests to ensure you can connect" (Their words not mine)

Available from

http://www.freewarepocketpc.net/ppc-download-hitchhiker-v0-4-beta-1.html

Hitchhiker requires that you have installed:

.NET Compact Framework 2.0 Redistributable

This is obtainable from:

http://www.microsoft.com/downloads/...6b-356b-4a2c-857c-e62f50ae9a55&displaylang=en. I suggest you install this first.

Whether you choose this possible solution or not, I find Hitchhiker a quick way to connect to networks without putting the settings in yourself and just a useful tool to have.

Mike
[General Questions and Answers] zulhadikurniawan:
anybody has a20 tablet rom mainboard: q 11-v1_3 20130618?
[Xperia SP Q&A, Help & Troubleshooting] drkztan:
Hello all! So, I tried to install CM11, the one on this post.

Went into CWM, did Wipe data factory reset and formatted /system. when I tried installing the rom, it said operation aborted and it could not install it. No biggie, the post says to install cm10.2 before doing so.

So i Powered the phone off to copy the file over to the SD. To my surprise, now I can't get into CWM, Philz, TWRP, fastboot or flashmode. Whenever I press the back pin to power the phone off, it turns back on automatically before I have time to press the key and connect the USB cable. Furthermore, when I manage to do it quick enouhg, the green led lights up, but it fades away after 10ish seconds only to display the sony logo again, and a "can't recognize USB device" popup comes up in my PC. I've used flashtool with this same pc in the past, so I don't know what that is about. Also, whenever I try installng flashtool drivers again, just in case 2 things happen:

there is no xperia SP device listed and whatever i select it fails to install.

What can I do now? I had 4.3 with the eXistenZ Ultra ROM before all of this.

Damm, this is the first time this happens to me, I've been swapping roms for ever, and this is not even the first phone i do this in, had a galaxy s2 and a wildfire S before. I feel like such a noob :(

UPDATE!:

So I finally managed to fix it. I posted this after about 8-9 hours of trying to get into fastboot on the 3 different pcs in my household, all had the drivers at some point and i've worked with them and fastboot and this same phone previously, so I figured they'd still work. They didn't, I couldnot even get SUS to work. So i went to a 4th PC, installed SUS and the needed drivers and it only took like 40 minutes worth of tries. I'm in the software download part of the SUS, i'll keep this updated!

UPDATE2!:

So, it finished downloading but it suddenly disconnected, tried again for about 10 minutes and then got it going again. Downloaded the second time and installed it successfully. Leaving this up for future reference!

Bottomline: if you can't get into flashmode, try on as many PCs as you have available for at least 30 minutes each.
[Xperia SP Q&A, Help & Troubleshooting] Th3Duck:
Don't use flash tools just install CM11 with CWM or something, use doomlord kernel to get CWM and install CM11 zip that's it.

Sorry locked boot loader didn't read it correctly don't use my advice :P.
[Xperia SP Q&A, Help & Troubleshooting] drkztan:
No problem, it kinda sorted itself out by brute force connections :> Dammed sony, locking the bootloaders for real. I even got the sim unlock code from my phone company and it's still not bootloader unlockable at the phone settings, even though i can now get any sim i want in it -.-
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] TonioGela:
Hi to everybody, that's my first post and sadly it's in the troubleshooting section :(

(I'm not even english nor american so don't blame my poor english please!)

Today I was using my S4 mini LTE normally and suddenly without no reason it has rebooted and remained stuck on the CM11 bootlogo.

I had installed the last snapshot of serranoltexx (cm-11-20140609-SNAPSHOT-M7-serranoltexx.zip) with its kernel and I was using CWM v6.0.4.5

I decided to wipe cache partition throught CWM but nothing happened, so I took the occasion to update the phone to the last nightly (the one that was released today).

At first no problem, I've installed it normally and start to reinstall all the apps and my previous stuff. Once the turn of Xposed Framework arrived, after download and activating some modules (I remember GravityBox [KK], DisableSignature..., Turnoff Google Location consent, etc...) and soft rebooting the phone restarted with no custom apps nor gapps. The app where present in /Android/data/app but they didn't seem to be installed.

I've reflashed a lot of times a lot of different versions of CM11 like the M7 I was mounting before but once installing xposed framework the problem was still there.

So i tried an error log under "advanced" into cwm and I've notice that it returned this:

persist.timed.enable=true
persist.fuse_sdcard=true
service.adb.root=1
keyguard.no_require_sim=true
recovery.perf.mode=0
telephony.lteOnGsmDevice=1

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host
I:using /data/media for /sdcard.

I've googled up the 2nd and the 3rd line that start with I: and I've kinda undestood that there might be some problems with the partition table and that I need to reflash via Odin a stock firmware with a .pit file of an original s4miniLTE, right?

BTW I've updated via Odin my CWM to 6.0.4.8 hoping in something but nothing, the error log is the same. I still can use the phone flashing the CM11 but i cannot use xposed framework and the problem remains :(

Can someone try to explain me what to do and if I really need to

like I've read in another post about another phone with similar issues?

Thanks a lot for your attention!

P.S. OBVIOUSLY I've tried a lot of times things like wyping dalvik cache, /data, /cache, /system, and everything that was possible through CWM (apart /sdcard1)

P.P.S. My phone is the LTE European version with 8GB of internal memory (I suppose, as the CM11 says that the total is 5,5), and at the moment I'm downloading an enormous stock rom file (like 650 MB) to flash through ODIN, am I doing well?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] LanderN:
Reflashing a stock TouchWiz rom with odin and starting all over seems like the best option for you! If that doesn't work, I would think you somehow got your internal memory corrupted.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Bolydark:
Is there any possibility to conect this usb wacom http://www.geniusnet.com/wSite/ct?xItem=16830&ctNode=174 with otg

For draw in sketchbook

Sorry for my english
[Galaxy Tab 2 Q&A, Help & Troubleshooting] sharingan:
no bro i dont thinks so it can happen as then device is of much great power according to me
[General Questions and Answers] calanthe:
Google Play Services is continually stopping on ALL of my Android devices. I have searched and done extensive troubleshooting, but have no idea what to try next.

I believe that this issue is somehow related to my Google account. I believe this because:

It happens on all of my devices (unrooted Verizon Galaxy S4, latest 4.4.2 update; 2012 Nexus 7 rooted running latest CM nightly; Android VM in VirtualBox running 4.3)

If I log in to any of my devices with another Google account, the issue does not occur.

I have tried other ROMs, wiping, clearing cache and data, changing my Google account password - honestly, I do not know what is causing this. And to witness it on a VM in VirtualBox with nothing but the OS and GApps was the final straw, causing this post.

The issue is not with the Play Store - it is with Google Play Services. So, anything utilizing Google Play Services (basically, anything Google, and then-some) causes this issue. Hangouts, Maps, Play Store, Music, my RSS reader (D7), etc.

And again, my phone is unrooted, and I've factory reset my phone - it happens as soon as I log in with my Google account, without any apps installed, other than those from the factory ROM. Same can be said for my tablet, and my VM - and my Android VM is as clean as they come.

I am a technical guy, I've been in the IT field professionally for over 15 years, and have been tinkering since I got an Amiga 500 in 1988. I've got some background, and it takes a lot for me to reach out for help because I'm a "fix it myself" type... but I am honestly at my wit's end here.

The only other solution I can see would be to create a new Google account, but that's not really an option, considering I would lose my paid apps, and anything else associated to that account.

Any other ideas or advice is appreciated

PS: I already posted this to the "Assist" forum, but had been asked to repost it here.