Database Develop

NeoFroyo!! Well testing

hey guys!
Well i was trawling the android forums and found this!
http://www.neopeek.com/viewtopic.php?t=7524
All thanks yo neopeek for the rom.
I decided to test it out on my kovsky. This coupled with I believe duckkly's kernels worked like a charm!! ill post the kernels up here too as I experimented with quite a few to see what worked best!
Battery life: 8 hours on full blast so i rekon around 11 on normal usage
Wifi: never ever ever dropped on me so far! thou it does seem to be weak in some places around my house where i usually should be getting more signals and strong at places where i get little signal :S.confusing
phone: well calls come in and stuff but sometimes ull see a black screen and cant see who's calling! :S
Bluetooth: paired with my mw600s just fine dont know about file transfer
market:works just fine a bit slow though..could be my internet speeds out here in pakistan.
Apart from that using whatsapp like a charm. facebook apps. gaaps everything works!! not a single sod to date been using it for around about 5 days or so.
Sorry for the spelling errors! big thanks goes out to neopeek and duckkly or whoever compiled those kernels !
PS: oh and the keys will freeze up as you hit around 20% battery. I simply reboot. Also terminal doesnt seem to be working. keeps crashing on me but i dont really ever use it in daily use so it seems to be pretty stable apart from these flaws. Also you'll need to reinstall quickpic from market
Also im on radio 1.16 i believe. 1.14 seemed to drop calls randomly.
please read all of neopeek's instructions before flashing ! happy flashing

can't confirm 20% battery being the point where keys stop working. for me 4 hours of uptime seems the be magic point...
i stopped restarting modules via script (how to has been explained many times in here) and simply restart. most of the time it happens when an app is running - now what good is it if you have a shortcut somewhere, but can't get there because back- and home-key isn't working?!
but yeah, neofroyo is a big step forwards. first time using android on x1 is fun!
for terminal to work you have to reinstall it just like quickpic.
i just hope we'll see some kernel-update soon. without it the whole thing is pointless.

lol truee..thanks for the terminal update. oh if u press the camera button it will take you back to your home screen. than i guess u could load the keyboard modules..annoying i never bother with it. try my combination of kernel it gives me decent battery lifee but yea its the kernel with all the problems. tried the new kernels but they dont seem to work properly

hm, which kernel-version is that?
might try if i know which it is. just had to step down from ygge-monster to ygge-turbo. monster made my touchscreen getting unprecise in left half.
thx for the update with cam-button - never bothered to press that, since camera doesn't work anyway.
yeah, new kernels suck for our device, especially since they're missing the specific battery-driver for x1. the only guy still working on x1-kernel has been silent for months, but i can see he's still at it (porting 2.6.35.7).

Just tried pressing cam-button.
Falls back to lockscreen, after unlock shows homescreen. But system is frozen and after some time reboots directly to android. But lots of stuff doesn't work, especially phone-stuff. So i have to reboot winmo anyway.
Sent from my X1i using Tapatalk

i think its the ducckly's keyboard not loaded as modules turbo verison. I believe it should be that because i remember the msm drivers werent really working properly on it
Sent from my Transformer TF101 using Tapatalk

[Q] Does CM10.1 (JB4.2.2) for Bionic have Dock Mode?

I just recently went from CM10 to CM10.1 (JB 4.2.2) on my Bionic and love it but noticed that when I insert it into the standard dock it doesn't sense it and go into a "Dock Mode". I am not sure if it's just my phone or not (I don't think so, it worked with CM10) and I am too new to post in the developers forum to let them know about it and it is still under development. Does anyone have any input how to get this to work and/or if you have access to post in the appropriate forum can you let them know about this?

I believe yes. if you go Setting>Display>Daydream you can get a clock or other options which can be triggered by the docks.

hackthis02 said:
I believe yes. if you go Setting>Display>Daydream you can get a clock or other options which can be triggered by the docks.
Click to expand...
Click to collapse
I found that and adjusted it and it still isn't triggered when docked. I booted back into stock ICS and CM10 (JB 4.1) and it seems to work then so I know it's not my phone. Are there any other settings to check?
I really love CM10.1 and really appreciate the work they do and know that it is still a work in progress but would like to submit it a bug report about it just so the dev's know. I would let them know myself but I can't post in that thread because I am a "noob" to this forum even though I have been using custom ROM's for a couple of years. Can someone help me out?

Dime-Baggins said:
I found that and adjusted it and it still isn't triggered when docked. I booted back into stock ICS and CM10 (JB 4.1) and it seems to work then so I know it's not my phone. Are there any other settings to check?
I really love CM10.1 and really appreciate the work they do and know that it is still a work in progress but would like to submit it a bug report about it just so the dev's know. I would let them know myself but I can't post in that thread because I am a "noob" to this forum even though I have been using custom ROM's for a couple of years. Can someone help me out?
Click to expand...
Click to collapse
I've been struggling with this too. It doesn't seem to work in either the latest Kexec versions of CM10.1 or AOKP. I suspect it has to do with something still needing to be merged into the kernel. I've tried restoring the different dock component apks from ICS, but that doesnt' help either. I sent a tweet to Hashcode yesterday asking if he knows how to get it working, but he hasn't responded yet. I'll let you know when he does.

I would not worry too much about it. CM10.1 is still in the nightly phase so a lot of stuff will not work, and they know this. I am sure it will be working once we hit RC.

I'm pretty sure that Daydream is set up to trigger with the screen timeout. Myself, I have mine set to 2 minutes, and once I'm docked, it seems to be about 2 minutes later that Daydream turns itself on.

irish_711 said:
I'm pretty sure that Daydream is set up to trigger with the screen timeout. Myself, I have mine set to 2 minutes, and once I'm docked, it seems to be about 2 minutes later that Daydream turns itself on.
Click to expand...
Click to collapse
Ya, for the life of me I can't get anything to happen when I dock it. Hopefully they get this fixed on an upcoming nightly. I'd even donate to get this one done because I use it for an alarm clock everyday. The thing I am doing in the mean time is to set the daydream "when to daydream" setting to "while charging" and then manually turn on the app "Dock Clock" when hitting the hay. It's a good work around but was a lot easier when it just triggered when docked. Thanks again to the dev's! They rock!! :good:

This is one the main issues I have with cm10.1. While the daydream setting works OK for my bedside dock, there is no way to differentiate between that dock and my car dock. So I can't launch a custom car launcher when in my car.

linuxgator said:
I've been struggling with this too. It doesn't seem to work in either the latest Kexec versions of CM10.1 or AOKP. I suspect it has to do with something still needing to be merged into the kernel. I've tried restoring the different dock component apks from ICS, but that doesnt' help either. I sent a tweet to Hashcode yesterday asking if he knows how to get it working, but he hasn't responded yet. I'll let you know when he does.
Click to expand...
Click to collapse
Have you heard back from Hashcode yet about the dock thing? I keep flashing nightly's hoping it'll be working but it's still a no-go. Today's nightly looks like it's gonna have a lot of changes/additions so I'll keep my fingers crossed.

FYI - I got a message back from Hashcode on twitter and he said "No dock features yet" :cyclops:

Any idea how the LapDock will respond? That's the sole reason i have stayed stock. I bought this dumb phone for LapDock...

ak110707 said:
Any idea how the LapDock will respond? That's the sole reason i have stayed stock. I bought this dumb phone for LapDock...
Click to expand...
Click to collapse
Same, that's why I haven't installed one of the custom ROMs on mine, because I love the lapdock functionality, which requires HDMI to be working. As far as I know, none of the non-Blur ROMs have working HDMI.

I love this ROM but I sure wish the dock stuff worked. I use my phone as an alarm clock on the dock and I switched over to liquidsmooth jellybean
yesterday to see if it's dock stuff worked (it doesn't). It was awesome but (even though the dock stuff doesn't work) until I got an FC for the clock when my alarm went off this morning so I am back.
On a separate note I installed yesterdays nightly and rebooted and my wifi was broken and i couldn't even turn it on so i reverted to the fixed version of the 3/27 nightly and was back in business. Hoping they get the dock up and going soon. :fingers-crossed:

Dime-Baggins said:
I love this ROM but I sure wish the dock stuff worked. I use my phone as an alarm clock on the dock and I switched over to liquidsmooth jellybean
yesterday to see if it's dock stuff worked (it doesn't). It was awesome but (even though the dock stuff doesn't work) until I got an FC for the clock when my alarm went off this morning so I am back.
On a separate note I installed yesterdays nightly and rebooted and my wifi was broken and i couldn't even turn it on so i reverted to the fixed version of the 3/27 nightly and was back in business. Hoping they get the dock up and going soon. :fingers-crossed:
Click to expand...
Click to collapse
My bad - operator error. I wiped and reflashed 3/27 the 4/4 and updated again and everything is peachy keen again.

So this may be a silly question, but is there any "light at the end of the tunnel" for Car dock mode in any of these JB ROMS?
We all thought that Root was unobtainable on the JB but that was proven wrong. Here's hoping that Car Dock mode is in the near future as its the one thing on my phone that i use consistently every day driving to and from work.

zetachi said:
So this may be a silly question, but is there any "light at the end of the tunnel" for Car dock mode in any of these JB ROMS?
We all thought that Root was unobtainable on the JB but that was proven wrong. Here's hoping that Car Dock mode is in the near future as its the one thing on my phone that i use consistently every day driving to and from work.
Click to expand...
Click to collapse
I was able to get the car dock mode to launch using the app below and the new Blurry ROM. No luck on CM10.1.
https://code.google.com/p/bionic-dock/

zetachi said:
So this may be a silly question, but is there any "light at the end of the tunnel" for Car dock mode in any of these JB ROMS?
We all thought that Root was unobtainable on the JB but that was proven wrong. Here's hoping that Car Dock mode is in the near future as its the one thing on my phone that i use consistently every day driving to and from work.
Click to expand...
Click to collapse
@Hashcode0f said:
I plan on supporting basic dock features and HDMI output (not webtop).
Click to expand...
Click to collapse
Source

Though I'm confused... is there something more "to" webtop/lapdock since the ICS version? AFAIK it's just leveraging the HDMI output for a higher resolution screen and attaching a USB keyboard/mouse. It hasn't been something "Special" since Gingerbread when it was Ubuntu based, right?

cixelsyddyslexic said:
Though I'm confused... is there something more "to" webtop/lapdock since the ICS version? AFAIK it's just leveraging the HDMI output for a higher resolution screen and attaching a USB keyboard/mouse. It hasn't been something "Special" since Gingerbread when it was Ubuntu based, right?
Click to expand...
Click to collapse
That confused me as well. I know there are some things like volume control that might not work (but I'm not sure they work on the stock JB ROM anyway) but people have modded all sorts of things to work with the lapdock (other phones, Raspberry Pi) by simply treating it as an HDMI display and a keybord/mouse. If a mod ROM even had that level of functionality I'd be happy with it, and I certainly don't expect a return of the original Ubuntu based webtop mode.
On a similar note, has anyone tried a mod while using the HD dock? That is supposed to do something similar, except I believe it comes with a remote control.

[Q] Problems with Touchpad CM

Have been using Touchpad CM9 for a long time, and 2 months ago reflashed it due to the '50 apps in sd card' issue. I reflashed it to the most recent CM9 nightly and it was stable with camera working and all. However what I realised was that there was this space at the top of the screen, about 2cm long, that does not detect any touch at all. This give problems as certain apps have tabs at the top and I can't access those tabs (for e.g. Browsers). On landscape the back button can't detect my touch (on landscape and with the "space" on my left). I wasn't really using my Touchpad much during this period but have recently been more active on it, thus its problematic for daily use.
I have just flashed CM10 over CM9 and this problem persists. I have went into developer options and enabled "Show Touches" and when I reach that "space" it stops detecting my touch and disappears. I would really appreciate it if someone could give me some help :/

iamatechnoob said:
Have been using Touchpad CM9 for a long time, and 2 months ago reflashed it due to the '50 apps in sd card' issue. I reflashed it to the most recent CM9 nightly and it was stable with camera working and all. However what I realised was that there was this space at the top of the screen, about 2cm long, that does not detect any touch at all. This give problems as certain apps have tabs at the top and I can't access those tabs (for e.g. Browsers). On landscape the back button can't detect my touch (on landscape and with the "space" on my left). I wasn't really using my Touchpad much during this period but have recently been more active on it, thus its problematic for daily use.
I have just flashed CM10 over CM9 and this problem persists. I have went into developer options and enabled "Show Touches" and when I reach that "space" it stops detecting my touch and disappears. I would really appreciate it if someone could give me some help :/
Click to expand...
Click to collapse
Do you have the same problem in webos? If so, it's probably hardware, if not I'm sure someone will jump in and help.

chicle_11 said:
Do you have the same problem in webos? If so, it's probably hardware, if not I'm sure someone will jump in and help.
Click to expand...
Click to collapse
Wow, you are right, webos has the same problem. I guess I was just in denial that it was a hardware issue and didn't think of checking it in webos. Damn, I don't think HP would want this back right
Sigh guess I should look into the chinapads my friend was recommending just this morning

Just wondering, is it possible to have android ruin the "hardware" aspect of the tablet? I am thinking of removing android and seeing if it exists still on my Touchpad.. Hmm..

iamatechnoob said:
Just wondering, is it possible to have android ruin the "hardware" aspect of the tablet? I am thinking of removing android and seeing if it exists still on my Touchpad.. Hmm..
Click to expand...
Click to collapse
No, android does not cause a hardware problem, AFAIK.
Use acmeuninstaller then follow this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
If after this you still have the problem, then you know that it's hardware.
Read the whole thing, it's very informative.
Edit : use cm10.1, it should give you access to the back button in landscape mode.

chicle_11 said:
No, android does not cause a hardware problem, AFAIK.
Use acmeuninstaller then follow this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
If after this you still have the problem, then you know that it's hardware.
Read the whole thing, it's very informative.
Edit : use cm10.1, it should give you access to the back button in landscape mode.
Click to expand...
Click to collapse
Thanks for the help! Will try this after backing up my stuff via Helium.
I have the impression that 10.1 isn't that stable, but I am likely wrong. Dont seem to see any cm10.1 with low deep sleep drain + working camera & mic + most other functions, or I could be looking at the wrong places.

I use milaq's nightlies, and for my needs, it's more than adequate.

Invisiblek's 4.4 12-30-13 Nightly Impression

I can't post this on the Milaq thread (where most of the invisiblek discussion is) so I thought I would post it here to give anyone else a heads up.
The Good:
It's a fairly stable kernel and all my apps run seemingly just fine. I mean I've only been running it about 5 hours but not a single FC. I did have a weird bootup glitch that locked it up right away after install but after that I loaded all the apps just fine. Super exciting to see it so far!
The Bad:
Screen pixelation/tearing from left to right, especailly on grey backgrounds. Something is up with the video driver/gpu voltage. Certain icons like the Settings sprocket will have a few pixels that will flash and other times you'll see lines all the way across the screen. It might be color specific. I was playing Quadropus Rampage and never noticed it but then went back to the home screen or typing an e-mail and it's very much there.
Pandora plays music fine. If you turn off the screen while playing, horrific things happen like ZZZZZZZZZZZZ and then hard lock. I didn't like that station anyway..
The "OK Google" voice command doesn't seem to work though voice typing does. I'm pretty sure this worked on the Milaq build of the same date.
It's a bit slow and CPU is stuck to 1188. There is a bit of a lag switching apps but I don't notice any core functions slow.
The Different:
The home button doesn't wake up the TP. Only the power button.
Can't say anything about battery life quite yet but I'll keep a gander on it. Battery hasn't been a super concern of mine because I plug it in ever night

The Different:
The typical 15 second reset switch mult-button key is more like 3 seconds now. I like this a lot better.

Positive:
--backup and restore work
--it is getting much better.
Negatives:
--Microphone does not work, so I could not use any vioce search or voice dialer/sound recorder.
--Free game "F.S. Xtreme" has black box issue.
--Youtube still has reboot issue.
--TV streams app "syncbak" has similar reboot issue.

My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.

Switched to milaq's 3.0 kernel.
The CPU is pre-configured to run at much higher 1.5Ghz, yet the 3.0 rom is still able to run very stable.
I am waiting for camera fix to enable video calls.
Since both 3.0/3.4 rom are using the same CWM, it makes 3.0/3.4 rom switch very easy.

Waiting on Flintmans as it is the only non data media rom. Not a big fan of all the repartitioning. For several reasons. Good to see choices still available. God bless the developers for all their time and effort. Wish I could do what they do.

goog888 said:
Switched to milaq's 3.0 kernel.
The CPU is pre-configured to run at much higher 1.5Ghz, yet the 3.0 rom is still able to run very stable.
I am waiting for camera fix to enable video calls.
Since both 3.0/3.4 rom are using the same CWM, it makes 3.0/3.4 rom switch very easy.
Click to expand...
Click to collapse
I flashed 3.4 rom (0103) over 3.0, and tried briefly.
--3.4 rom seems running OK, except it runs relatively slower at 1.1Ghz.
--camera is not working on both 3.0/3.4 rom.
--Free game "F.S. Xtreme" seems not compatible with 3.x kernel. It also cannot run on Samsung S3.

Moody66 said:
My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.
Click to expand...
Click to collapse
Turn off WiFi Optimization in settings.

EbolaCola said:
Turn off WiFi Optimization in settings.
Click to expand...
Click to collapse
Still does it. Did that soon as rom booted as per the Op.

Moody66 said:
My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.
Click to expand...
Click to collapse
Same here. Also double check that the setting took. I swear I unchecked it and it went back or didn't take the first time. Perhaps give it a toggle or two. I also noticed that if wifi turns off, it won't turn back on.

Anyone else having a problem with rebooting from within CM and it just goes to a blank screen?

Dirty flashed to the 1/5 nigthly. Reboot issues seems gone now, or just that a reflash has fixed mine specifically.

Just noticed that there is an official thread over at http://forum.xda-developers.com/showthread.php?t=2592909
Hopefully I can post there too!

sokratz said:
Just noticed that there is an official thread over at http://forum.xda-developers.com/showthread.php?t=2592909
Hopefully I can post there too!
Click to expand...
Click to collapse
Negative on the posting. I'm still seeing the bzzzz when the screen shuts off while playing music. Have disabled the mic (I think). Curious that nobody on that thread has reported that quite yet.

I'm very excited to see all of this development on our old TPs! I'm currently running Milaq's latest 3.0 kernel test build. It is running almost perfectly for me! I cannot wait for 3.4 to finish getting smoothed out. I've tried Invisiblek's builds out, and they currently seem a little laggy compared to Milaq's 3.0 test build. Great work all around though! Thanks to Invisiblek, Flintman, Milaq, JCSullins, Dorregary, and all of the others that I haven't mentioned who have contributed so much of their time and skill toward keeping our Touchpads relevant, even competitive with the current crop of tablets on the market!
Sent from my TouchPad using Tapatalk 4

[CLOSED][DEPRECATED] OmniROM 5.x

OmniROM
Lollipop - Android 5.x
​
A new "unified" Galaxy Tab 2 section was added to our forum because we don't make a difference between p31xx an p51xx specific roms.
Please use the Thread here for Omni 5 related questions and feedback

Reserved
Downloads:
Unofficial Builds by me
ROM Downloads for all supported devices can be found here
SuperSU http://download.chainfire.eu/supersu
GApps:
by @Deltadroid http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
or http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330

Can't wait to try this out. Loved omnirom ROM 4.4.4 on my tab until I tried your recent SlimLP ROM on it
Sent from my Nexus 5 using Tapatalk

New builds late this evening
Send from OnePlus One using Tapatalk

Android-Andi said:
New builds late this evening
Click to expand...
Click to collapse
Will definitely try this out - Omni 4.4.4 was perfect - I expect nothing less here (over time of course). Thanks Andi.

Builds are up
Send from OnePlus One using Tapatalk

FYI... Cant get it to boot! First tried with dirty flash from SlimLP then a clean... But no luck. Get stuck on bootscreen...

cheeseous said:
FYI... Cant get it to boot! First tried with dirty flash from SlimLP then a clean... But no luck. Get stuck on bootscreen...
Click to expand...
Click to collapse
Likewise with a P5113 here, booted first time after clean flash with pico Gapps and supersu 2.40... but after first reboot and 2 force reboots... still hanging on boot screen with a blank faced android blinking and wondering. Black to SlimLP for now. Thanks again Andi.

Lolli!
I installed the latest build and its working great in my P5110
I didn't even had any major bug yet (Only clock app not working)

Android-Andi said:
Builds are up
Click to expand...
Click to collapse
Reporting: Did an update from last years version.
Wiped C + DC
Flashed Rom + SuperSU
Rebooting .... took approx. 7 minutes ... done
Settings done,
Reboot,
Stuck at boot logo ... left for about 15 minutes
Wiped C + DC again,
Rebooted successfully this time.
Used for an hour or two, than reboot again, stucked at boot logo again...
After wiped C + DC again without no apparent reason: Booting successfully.
Restoring SlimLP with TWRP. Will test next build Andy when available.

@Gregzi thx for testing. I'll run new builds tonight...
Send from OnePlus One using Tapatalk

Testing Build 20150107
Testing latest build:
- Clean flash Rom + Gapps + Supersu 2.40
- Boot time reduced to 3 minutes
- Setting everything
- Noticed that SuperSU is this time correctly pushed into the system (in previous builds I had two:
one in Launcher and one in Settings ==> sometimes problems with root - TBackup)
- Shutting down the tablet
- Booting - again stuck at Omni boot animation (left it for about 10 minutes)
- Force reboot to TWRP (with two button combo)
- Reboot into the system from TWRP without cleaning anything
- Booting normally in 1 minute
When OC the frame rate is now 32,8 fps (Nenamark2), so better than previous builds, so certain progress is done.
The tablet feels smoother - especially noticeable when opening app drawer.
BR

installed over omni 4.4.4 without wipe.
first boot took about 40 mins, updating 173 apps.
some bugs:
firefox beta won't run
home button does not work
still collecting experience, but it doesn' t look too bad ?
Cheers and thanks alot, s.
sent over omni

sebastel23 said:
installed over omni 4.4.4 without wipe.
first boot took about 40 mins, updating 173 apps.
some bugs:
firefox beta won't run
home button does not work
still collecting experience, but it doesn' t look too bad
Cheers and thanks alot, s.
sent over omni
Click to expand...
Click to collapse
Home button gets fixed by flashing Gapps!

DarKnighT916 said:
Home button gets fixed by flashing Gapps!
Click to expand...
Click to collapse
thanks, but actually i had flashed Gapps (pico) already just after the ROM.
however, i'll try again later. :fingers-crossed:
in the meantime, i re-flashed gapps, with no change in behaviour.
for the time being, i'm back to 4.4.4.

bt issues
cannot connect bt headset. other features working fine, any toughts

only a question
I have a p5110 and runs pretty well but I've a problem with the minimum brightness it's very dark I can't see anything. any solution?

I loaded the 1/29 build last night on a clean install (with the latest Nano PA Gapps and SuperSU install zip, all on Andi's latest TWRP build). So far so good, here's a few observations:
-The first boot took a pretty long time but from what I've read this is normal. I didn't reboot again until the next day but for the second boot, the bootanimation never loaded, it just went straight from the brand logo to the launcher, long black wait in between. After that, all fine. Later I loaded the stock lollipop bootanimation I had been using previously (I do like the omni one a lot, though), and it used to lag a bit at the end on 4.4.4 but now it runs smooth all the way through, so that's encouraging.
-Turning the screen off (or letting it time out) is usually buggy, the screen flickers on/off for a second instead of any type of animation (I believe Lollipop is supposed to do a monochrome fadeout?) Edit: On closer inspection I see it is doing the monochrome fade, but then the screen flashes at the end of the animation.
-Re-installing apps was painfully slow and seemed to hang if I let the screen turn off (I'd find it sitting on the same install several minutes later). Downloading seemed a lot slower than KitKat ever was, too. I looked at the stats in settings->apps->running at on point in the process and the Play Store was listed as Restarting, perhaps this indicates poor memory management? Running the app in the foreground didn't seem to help at all, though.
-The material updates to the stock browser app are pretty swanky, I'm a fan. (I saw that in the gerrit and got excited. Not done yet but looks great.)
-Cast screen doesn't seem functional, doesn't find my chromecast. I've tested both Netflix and Localcast to connect just fine, LocalCast was a bit finicky the first time I tried but I think that may have been a network issue.
-I was testing a video call in in Hangouts and tried to mute the sound (was testing with my phone in hand and there was audio feedback loops because of that), but couldn't. Using the volume buttons, it wouldn't go all the way down, and if I dragged the bar the rest of the way it just wouldn't stick. Not sure exactly which volume control that was (lollipop's sound settings still confuse me in general), but I think it must be a bug of some sort that it wouldn't go down to mute.
-I had only just got around to trying to use my tablet's IR blaster (P5113) for TV control a few days earlier, and I found that the top several smart remote apps in the store don't work at all. Peel actually forces a soft reboot when it gets to the "push this button to test turning the device on" step, consistently. I did get one app working, which only includes remote IR support as a secondary function, TV Guide by Mini Group. Unfortunately the app isn't quite polished enough to be useful to me, but it was notable that it just worked where the others all get nothing. I didn't re-test all of the apps on lollipop but the ones I did(both of the ones linked here and a couple of the others that didn't work) behaved the same way.
-Visual performance generally seems a bit laggy but overall performance is fine (i.e. animations may freeze or lag but the tasks they're covering up don't suffer). Maybe all the animations in lolipop are just a bit rough on older hardware? I find them a bit overdone now that I've played around with things a bit more, personally (not that this reflects on the ROM). I don't really like stuff like shadows bouncing around as I scroll menus, though some of them are a nice subtle touch.
Overall I was happy with KitKat, but I think I'll let lollipop grow on me, these quirks are all minor. Idle battery life seems a bit worse but it's hard to make that call, I've been fiddling with the tablet more than usual to test things anyway.
Edit: Actually after letting it sit overnight unplugged, the idle battery is better than I was ever getting on KitKat. Granted, I made a point of closing all apps before and I think on KitKat I was having issue with casting apps holding wakelocks overnight and that's yet to be tested, but 1% over 12 hours is a pretty damn good baseline. Not sure what caused that wifi drop towards the end, after holding the connection (it gets a good strong signal) for about 11 hours, though.

Hey together!
Seems like we have some faulty eMMC chips, some reports of broken devices appeared.
I pushed a commit to address the issue and prevent other devices from damage.
I will recompile latest Lollipop roms and recoveries within 1 week.
For more information please read http://forum.xda-developers.com/showthread.php?t=3016879
Follow the instructions please to check your eMMC information.
Best regards and wishes!
Andi
Send from OnePlus One using Tapatalk

Internet sharing (mobile hotspot) doesn't work