Android 5.0 Lollipop Release Discussion
- Thread starter El Daddy
- Start date
- Status
Anyone else having issues with the "L camera" can't play videos recorded videos
Edit
I can record videos @35 and @65mbps but can't play them.
I can only play @8mbps and it has a green line on the bottom.
Just letting you guys know[emoji2]
How to change resolution as seen image ? I cant find any setting optionin l camera !!
Sent from my Nexus 5 using xda premium
Do you use ElementalX? I think this is a known bug of the kernel you are describingAnyone else having issues with the "L camera" can't play videos recorded videos
Edit
I can record videos @35 and @65mbps but can't play them.
I can only play @8mbps and it has a green line on the bottom.
Just letting you guys know[emoji2]
im having issues with GPS. it never asked me if Agree to stuff like it used to. now im stuck at waiting for location.
I'm using the kernel that comes with Pure White Rom
---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------
Re download it on the Google website I think it's might've been updated
Here's a thought.... I know I tend to go long, but this is worth a reading I think.
In light of all this "delay" I keep going back to the same thing when I try to make sense of it all. Fiirst, a little bit off topic, but its related.. Any of you happen to run Chrome Beta?. I used it until Yosemite came in cos all of the sudden the Google search app within Chrome kept crashing. A super instant crash exactly like when you loose connectivity. My computer only has WiFi....... See where Im getting at?.
I changed to the mainstream release and I get the error but considerably less than in the beta version. This happened in different WiFi's with 100% proof of a working network.
Here's my crazy two cents... Search is now everpresent in the mayority of Google's OS and even in the iOS ecosystem. Google Now, Wear and basically every google app relies on that "OK Google" magic word. So that supposed WiFi intervals of on/off bugg that is supposedly delaying the rollout is related to this
Is far streched and I can probably come up with a lot more "proof" and even get some code to show off but I think its not THAT far out.
Anyways, in the meantime, I keep drooling over the Material Design.
In light of all this "delay" I keep going back to the same thing when I try to make sense of it all. Fiirst, a little bit off topic, but its related.. Any of you happen to run Chrome Beta?. I used it until Yosemite came in cos all of the sudden the Google search app within Chrome kept crashing. A super instant crash exactly like when you loose connectivity. My computer only has WiFi....... See where Im getting at?.
I changed to the mainstream release and I get the error but considerably less than in the beta version. This happened in different WiFi's with 100% proof of a working network.
Here's my crazy two cents... Search is now everpresent in the mayority of Google's OS and even in the iOS ecosystem. Google Now, Wear and basically every google app relies on that "OK Google" magic word. So that supposed WiFi intervals of on/off bugg that is supposedly delaying the rollout is related to this
Is far streched and I can probably come up with a lot more "proof" and even get some code to show off but I think its not THAT far out.
Anyways, in the meantime, I keep drooling over the Material Design.
Here's a thought.... I know I tend to go long, but this is worth a reading I think.
In light of all this "delay" I keep going back to the same thing when I try to make sense of it all. Fiirst, a little bit off topic, but its related.. Any of you happen to run Chrome Beta?. I used it until Yosemite came in cos all of the sudden the Google search app within Chrome kept crashing. A super instant crash exactly like when you loose connectivity. My computer only has WiFi....... See where Im getting at?.
I changed to the mainstream release and I get the error but considerably less than in the beta version. This happened in different WiFi's with 100% proof of a working network.
Here's my crazy two cents... Search is now everpresent in the mayority of Google's OS and even in the iOS ecosystem. Google Now, Wear and basically every google app relies on that "OK Google" magic word. So that supposed WiFi intervals of on/off bugg that is supposedly delaying the rollout is related to this
Is far streched and I can probably come up with a lot more "proof" and even get some code to show off but I think its not THAT far out.
Anyways, in the meantime, I keep drooling over the Material Design.
The bug that you're talking about is already fixed mate.
Take a look about it here.
Last edited:
Wh1t3Rose
Senior Member
Guys App OPs is feature built into Android itself. Since 4.3. It's just hidden by default. You need an app for now to gain access.
https://play.google.com/store/apps/details?id=com.findsdk.apppermission
Moto X 2014 get update sooner than Nexus?? I dont see a point to have Nexus phones in future anymore..
Sent from my Nexus 5 using Tapatalk
If that's true then it would mean Motorola didn't took enough time to do a thorough QA procedure (testing). Quite risky for a fame.
only logical reason I see is because the Nexus 6 is based off the X. but even still....Nexus5 need that ASAP! so gone about the idea they wanna release the images around the same time the N6 starting being sold.
Verde™
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
108Flash SuperSU, then fastboot flash this boot.img, then you have root.
hi click me
http://imgur.com/4tobGiF
EDIT: Gather round guys.
Lots of you are complaining that apps like titanium backup and helium are crashing or just not working. And the popular thing to do is complain that there is no /system write access, buuuut, there is system write access. I'll admit it, at first instinct I thought this was the case too. Upon further inspection, it looks like root app developers are going to need to the new security contexts when they run an elevated command. This will explain why some of your apps can write to system and some cannot. I know Root Explorer has been properly updated, for example. If you'd like to read up more, check this link out. Credit to @Chainfire for the bits n bolts.
Now that that's cleared up, here's a flo boot.img I don't have it, but the method was the same, give it a swing.79Alright guys... we've been watching this thread for quite some time now, and what happens in here is completely unacceptable.
We've been discussing the matter in our mod team, and decided to close this thread for some time.
There were/are posts in this thread breaking several forum rules, which is completely unacceptable. We are a forum for all ages, which means you should watch your language at least a bit. We were allowing this thread simply because it was obvious we'd need one, even though it was kinda a grey area. We in the Sony/Moto/LG section do not allow OT threads, which this one kinda is. All posts in here are either completely off topic, or simply just complaining. But guess what.... this doesn't bring the update any faster either.
And if you happen to have the genious idea of opening up a new thread or start spamming others, please don't do it, or else we have to take further action against you...
If you feel there is a need to discuss the matter, feel free to PM me or @El Daddy about it.61Android 5.0 Lollipop Release Discussion
**Any and all discussion regarding the 5.0 Lollipop Developer Preview will only be allowed in this thread**
Rules of this thread:
- To keep confusion to a minimum, we are asking members to limit their discussion of 5.0 Lollipop to this thread only.
- Limit discussion to talk about the release. Any and all off-topic discussion will not be tolerated.
- Please follow the XDA Forum Rules. Search the thread before posting, be kind to one another, etc.
- If you see a post that is violating Forum Rules, please use the report post tool and move along. There is no need to get involved.
- If you have troubleshooting questions, help to install, etc., please use the dedicated Q&A thread here: Android 5.0 Lollipop Developer Preview Help, Troubleshooting, Q&A
Allowed threads regarding Android L
All threads not listed here will get closed immediately. If you think you have an idea of a thread that should be allowed as well, please report this OP and ask for it to be allowed.
3131For Fluck's Sake!
Rising this morning to find yet more pages of tearful outrage I'm going to skip posting another of my word-salads of mockery and instead stoop to the banality of a 10-point list.
1. To the people complaining so bitterly that some other make, model, or region of phone might possibly get some semi-final build ahead of our Nexii - what were you like in 3rd grade? Are you still in 3rd grade?
2. The Moto-X is only just getting a soak test, not the "official release"!
3. The Moto-X soak test is limited only to the Pure Edition of the phone - a relatively small percentage of the actual number of Moto-Xs on the market.
4. There is an advisory that flashing this build on carrier editions could brick the phone!
5. Not even all Pure Edition owners are included in the soak test; it's limited to selected owners in their special "feedback group". As per point #4 I have no idea how flashing this image might affect the warranty of unauthorized testers. (Play Store Nexus warranties are completely unaffected by any builds, ROMs or kernels you choose to load on your devices.)
6. Motorola is vague on when any build will be pushed to non-Pure Editions. This, as we all know, is because each carrier must run their own "compatibility tests" and futz around with the delightful bloatware they so generously add to the OS. As we also know the carrier stage can take weeks (and weeks, and weeks) to complete! As we also know there is NO carrier stage for the Nexus 5.
7. LG - for God's sake, friggin' LG! is sending out a "final build" to their flagship device in a single country in Europe - and roughly a week from now! A fine & wonderful country Poland is, but it also appears to be a country that has lax restrictions from carriers & has been used in the past as a general soak test territory. While a a relatively large country, I'd wonder just how many G3s are actually in circulation there - this could be a relatively tight control group.
8. LG has made no concrete statements as to when this OS (custom skinned, of course!) will actually make its way to devices outside of wonderful, wonderful Poland. Once again, outside of Play Editions or "Pure Editions" each major carrier will take sweet, sweet time to work their magic before a build is actually released to the great unwashed.
9. HTC, who have taken steps to be completely transparent about updates (I urge you ALL to view http://www.htc.com/us/go/htc-software-updates-process/) report that their current flagship, the One M8 - including Unlocked & Developer Editions have not even begun the process "This device currently has KitKat, and is in the 0 - Evaluation stage of the Android Lollipop Release."
10. To those who think that Google would be forced/extorted/bullied to release a "final build" early to any device manufacturer specifically for wide release before the build is actually consumer-ready... are you 9 year-olds frustrated by 3rd grade?
I guess I can leave it at an even 10.
Bonus point (unnumbered): It is good that other manufacturers are trying shift to new builds as early as possible - good for the entire Android ecosystem, so be happy we're seeing signs of movement out there beyond our ever-special Nexii.
You are welcome.
