Database Develop

Freezing all the Time...

I've been using Incubus26Jc's Froyo v. 12 and My Vogue has been freezing over and over all the time. Seems not to be app specific, and seems to happen when its charging and when its on battery.
Any chance I've got a setting wrong? My guess is that my phone is dieing. Any advice?

I've had this problem on the earlier versions, but now on release 12, I have only had 2 freezes... Sometimes you just have to let the phone sit. I guess it kinda gets overwhelmed and needs a little rest :/

Is my situation the same? I'm running SagaROM Froyo Ultralite [v1.2.1, 7/28/10] and every time the screen goes to sleep and goes into lock mode, it reboots. What can I do to fix this? Please & thank you!

deltagamer said:
I've had this problem on the earlier versions, but now on release 12, I have only had 2 freezes... Sometimes you just have to let the phone sit. I guess it kinda gets overwhelmed and needs a little rest :/
Click to expand...
Click to collapse
i have to agree my phone was doing this all day today, after using gps and apps heavy
rebooted a few times and let it sit for a while working much better now

evilclosetmonkeynate said:
i have to agree my phone was doing this all day today, after using gps and apps heavy
rebooted a few times and let it sit for a while working much better now
Click to expand...
Click to collapse
Try going back to RLS10.5 with the 15-07-2010 version of Zimage. That eliminated the freezes for me. And it seems a lot faster.

evilclosetmonkeynate said:
i have to agree my phone was doing this all day today, after using gps and apps heavy
rebooted a few times and let it sit for a while working much better now
Click to expand...
Click to collapse
Try going back to RLS10.5 with the 15-07-2010 version of Zimage. That eliminated the freezes for me. And it seems a lot faster.

Thanks @richardk3 ... I have the NBH, but I didn't save the 10.5 install file. Anyone have a link?
Update: Searching the forum didn't find it but a Google Search did: http://www.mediafire.com/?ond2tmmzolggtmm

If you search the main Froyo thread, incubus put up a link to the archive of recent releases.
I went back to RLS10.5 and the 7/15 zImage per richardk3's suggestion. At first I did notice less freezing and overall better performance. But then I made a long call (over 5 min) with BT headset and the phone became unresponsive. BT and the call were still working fine, but the phone was unresponsive and had to be reset at the end of the call.
This is pretty consistent across all builds in Eclair and Froyo. I've reached the point where I basically accept that this is always going to happen and I'll need to reboot. It's worth the trade-off, though, since this build is so amazing and Android is so much better than WinMo.

Johndixon, if you're running from nbh then you may need to clear the dalvik cache from the boot screen menu. Worked for me when the freezes came fast and furious.

jstrom23 said:
I went back to RLS10.5 and the 7/15 zImage per richardk3's suggestion. At first I did notice less freezing and overall better performance. But then I made a long call (over 5 min) with BT headset and the phone became unresponsive. BT and the call were still working fine, but the phone was unresponsive and had to be reset at the end of the call.
QUOTE]
I'm having the exact same problem... always becomes unresponsive at the end of the call when using Bluetooth. I've tried combinations of RLS10.5 and RLS12, and a couple of zImages.
Other than this, it's super fast and stable... But it would be great to figure out what is causing the freezing.
Click to expand...
Click to collapse

eugene2007;7515857
I'm having the exact same problem... always becomes unresponsive at the end of the call when using Bluetooth. I've tried combinations of RLS10.5 and RLS12 said:
I'm having the same problem without using Bluetooth.
Can you gather the debugging info that DZO needs, as described here:
http://208.100.42.21/showthread.php?t=712310&page=180
Click to expand...
Click to collapse

[ROM Feedback] CM 6.0.2 (09/05/10)

To my knowledge, there is no thread dedicated to the new numerical releases of CM. Let us start with the newest, CM 6.0.2.
Please post your anecdotal data, including benchmarking scores, bugs, and glowing experiences. Perhaps this will serve as an unofficial repository for issues that prove consistent.
Note: After modifying my WiFi settings, specifically disabling sleep mode while the screen is off, I've encountered no related instability.
Mail FC Fix: http://forum.xda-developers.com/attachment.php?attachmentid=394316&d=1283500340
Systemic issues yet to be addressed:
-LEDs do not work save for charging
-Outgoing calls initially drop before reconnecting
-Lockups or reboots, likely stemming from SetCPU
-OS does not recognize internal storage

Does this version fix the wifi not staying on?

Did you change your settings to Never sleep for wifi and just left the wifi on? Thanks...I want to try different settings and see if I can eliminate reboots/shut downs.

are we waiting for the nightly for the newest fixes like LEDs or is there gonna be a new release like .3?

OP you are a month behind (it's 9/3 not 8/3)
After fixing the mail fc, this rom is very stable except for one lingering issue. I guess it might be wifi related. I went all day without any issues with wifi on constantly (and bt) but when I left work (and seemingly as soon as I got out of wifi range) the phone was locked up with nothing on the screen, unresponsive. I had to pull the battery. This has happened since RC3 for me. I am going to try it without wifi over the weekend. Otherwise, BT streaming adio now works perfect, and the internal memory gets scanned for pics/images. I'm going to keep running it though as this wifi bug should be fixed soon.

not to mention we're commenting on it in the more official thread posted up by the author of the rom .
http://forum.xda-developers.com/showthread.php?t=755690&page=111
however just to say it.. so far its running quite well, I found a correlation between wifi and BT causing issues with each other... commented on it in the other main thread after some extensive testing today.

seanmcd72 said:
OP you are a month behind (it's 9/3 not 8/3)
After fixing the mail fc, this rom is very stable except for one lingering issue. I guess it might be wifi related. I went all day without any issues with wifi on constantly (and bt) but when I left work (and seemingly as soon as I got out of wifi range) the phone was locked up with nothing on the screen, unresponsive. I had to pull the battery. This has happened since RC3 for me. I am going to try it without wifi over the weekend. Otherwise, BT streaming adio now works perfect, and the internal memory gets scanned for pics/images. I'm going to keep running it though as this wifi bug should be fixed soon.
Click to expand...
Click to collapse
Yes, there definitely is still issues with wifi. The issue seems to be exacerbated when running SetCPU with a profile that underclocks when the screen is turned off. Since I've stopped using SetCPU I havent had a single freeze, although I might have just gotten lucky so far.
SetCPU will not run at startup for me, even with the option checked to start at boot. I had to set Tasker to run it at boot as a workaround.
When phone is in Airplane mode I still am able to recieve text messages.

Fuzzy_Dunlop said:
Yes, there definitely is still issues with wifi. The issue seems to be exacerbated when running SetCPU with a profile that underclocks when the screen is turned off. Since I've stopped using SetCPU I havent had a single freeze, although I might have just gotten lucky so far.
SetCPU will not run at startup for me, even with the option checked to start at boot. I had to set Tasker to run it at boot as a workaround.
When phone is in Airplane mode I still am able to recieve text messages.
Click to expand...
Click to collapse
I would have to second the issue with SetCPU. As soon as I overclocked it and began using the rom I noticed the phone would get hot abnormally fast and would reboot a few times within the first few hours. Not sure what is going on here as it worked fine on the RC.

Fuzzy_Dunlop said:
Yes, there definitely is still issues with wifi. The issue seems to be exacerbated when running SetCPU with a profile that underclocks when the screen is turned off. Since I've stopped using SetCPU I havent had a single freeze, although I might have just gotten lucky so far.
SetCPU will not run at startup for me, even with the option checked to start at boot. I had to set Tasker to run it at boot as a workaround.
When phone is in Airplane mode I still am able to recieve text messages.
Click to expand...
Click to collapse
I didn't even notice setcpu till you said that. Phone was back to 998mhz
Sent from my INCREDIBLE using XDA app

My phone doesn't vibrate when I receive an incoming call when the phone is set to vibrate.

Has anyone else noticed the keyboard lag when using the Messaging app? Browser and this xda app seem to work fine with no lag..
Other than that, smooth.

dnoyeb said:
not to mention we're commenting on it in the more official thread posted up by the author of the rom .
http://forum.xda-developers.com/showthread.php?t=755690&page=111
however just to say it.. so far its running quite well, I found a correlation between wifi and BT causing issues with each other... commented on it in the other main thread after some extensive testing today.
Click to expand...
Click to collapse
I believe the thread referenced by you refers to RC3, whereas I am specifically looking for feedback on the newest numerical releases of CM 6 for the incredible.

Update: leaving battery percentage at 91 before bed with system panel running, will see whats eating up the most juice. So far stable n fast with no issues (except LCDs).

I get random reboots and freezes every thirty minutes if so on a fresh wipe of 6.0.3 I tried with setcpu and without but always with the built in hotspot running. Same issue since RC3

LED notifications dont work. LauncherPro Plus FCs on every reboot, other then those things im good with it, great wallpapers , great rom

Battery life is terrible compared to sky raider with king kernel. Once we get some real kernels for this rom it should be better...

Panda Fuzz said:
Battery life is terrible compared to sky raider with king kernel. Once we get some real kernels for this rom it should be better...
Click to expand...
Click to collapse
And you know the issue is the kernel because...?

mp3sum said:
I believe the thread referenced by you refers to RC3, whereas I am specifically looking for feedback on the newest numerical releases of CM 6 for the incredible.
Click to expand...
Click to collapse
actually if you read the thread, you'll see koush himself is in there dealing with 6.0.2, offering up kernels and fixes...
he just hasn't updated the topic title.

Okay this may be a stupid question but how do I apply the mail fix?

mp3sum said:
Update: leaving battery percentage at 91 before bed with system panel running, will see whats eating up the most juice. So far stable n fast with no issues (except LCDs).
Click to expand...
Click to collapse
Battery life was down to 81% 11 hours later, and the phone had been placed in Airplane mode while running Gentle Alarm and a few widgets (no auto task killer).
Breakdown:
System 0.6%
System Processes 0.3%
System Panel 0.3%
android.process.acore 0.1%
Plus several honorable mentions with 0.0%. I have yet to perform this experiment with Ruby or ID.

[Q] Erratic Touchscreen Issues

No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.

have you tried a screen protector? my screen wasnt the best for precise touches but since i put a screen protector on and clean the screen regularly it has since changed my problems to almost non existant.
Sent from my NookColor using Tapatalk

Others may be able to help you more than I can with exactly when the CM7 may be doing this, but returning to stock to find out is actually not hard at all.
In the development thread there is a post that has the 1.2 stock zips (one keeps CW in place, the other returns it completely to stock). Which ever one you pick it's still just as easy to return to stock as to reflash CM7 again. This is especially true if you used a SD card with CW to flash (which is what I do), since when you want to go back to CM7 you won't have to worry about flashing CW to emmc again.

angelic.pariah said:
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
Click to expand...
Click to collapse
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?

dalingrin said:
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
Click to expand...
Click to collapse
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it. At one point I almost purchased an app from the market before I had to power down.
I will return it to 1.2 stock and report back. I was mainly wanting to know if these was a commonly reported issue or not. I guess it's not. Thanks for the help everyone!

angelic.pariah said:
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it.
Click to expand...
Click to collapse
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.

bucketheadmn said:
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
Click to expand...
Click to collapse
So now I have installed nook stock 1.2 and NO PROBLEMS. I have run everything trying to get something to happen, and nothing.
Is it possible that I installed something the wrong way with cm7? Could I have used the wrong CWM version (3.0.0.6)?
Should I try cm7 7.0.2 or something else again?
I would try and return it, but I can't recreate the problem... if I could, I would be in their face right now.
Thanks for the help so far.

I think I solved it!
The newest nooks (in the last week or so) have 1.1.0 factory stock. Apparently there is a glitch that has been reported a lot recently about handling the touchscreen AND the SD card. These were fixed in the 1.2 upgrade. SO...
1. I flashed factory stock back on (in this case I went back to 1.0.1)
2. Then turned it off and "restored factory" settings using "Power+N" to turn it on. Repeated that a second time to get B&N's factory reset screen to come up.
3. Pressed N twice to accept restore prompts.
4. Upgraded to 1.2 (no glitches already by this point with touch or SD)
5. Booted CWM 3.0.0.6+
6. Formatted /system & /data
7. Flashed phiremod 6.1
8. OC'd to 1.1Ghz
...and DONE. No problems so far. I still see the "Read Forever" opening screen, but it still works wonders. WAY better than before.
I am still having issues with Wifi, but I can deal with that.
Now to attempt dalingrin's OC to 1.3!
Thanks guys... hope this helps others.

I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.

I had weird touchscreen issues when using the interactive cpu governor. I later found only performance is supported. Using performance setting, everything works much better.

queseyo said:
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
Click to expand...
Click to collapse
I had the same issue. I exchanged it the other night and now my new one does not have the problem. It probably a hardware issue...i hope you are still under warranty!

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

[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