Search results

Well, there is absolutely no reason why "call quality" would go bad when held with a specific hand. The only reason it would ever happen is if something were to obstruct (or similar) the microphone.

Have you tried another battery?

It was removed. See here: https://github.com/CyanogenMod/android_packages_apps_Settings/commit/51b8cad889ec0989aec92b7cda80079c9af68efc

Only one of the "speakers" on the bottom of the Nexus 5 is actually a speaker and the other is a microphone. If the device is held correctly then it shouldn't be a problem no matter which hand it is held in..

Are there any modules that could provide a second clock in the statusbar using another timezone? The two current ones that I know of ('XMultiZone StatusBar Clock' & 'Xdual Statusclock') are either broken or don't work at all on Lollipop.

I probably won't get a reply so quickly because you were last active a month ago, but any progress on making it work properly on Lollipop?

The OTA update will fail. As of Lollipop, you have to have everything completely stock (including the recovery) to take an OTA update. You're better off just flashing another pre-rooted ROM or custom ROM which has been updated to 5.1.1.

Still looks kinda holo, just with somewhat-material colours.

Probably an Xposed module.

http://forum.xda-developers.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749

It's most likely a driver issue.

No, there hasn't been another preview release since August of last year.

It just won't work. A battery is standard, its just a power source and a circuit. A camera requires hardware/firmware/software/driver support (likely to be closed source) that is usually built specifically for that device. Even if you somehow get it to connect (which is extremely unlikely in...

http://download.chainfire.eu/supersu Download and flash in a custom recovery. Use TWRP if you aren't already.

If you want to dim the navigation bar (why would you need to?) you'll probably have to decompile SystemUI, modify the drawables then recompile, or use Xposed.

You'll likely have to factory reset. What Android version are you on, and what modifications do you have (if applicable)?

https://developers.google.com/android/nexus/images Either should be fine. Everything in the D821 is the same as the D820 with the exception of which radio bands they can access.

No point formatting /system since it does that in the flash script anyways. Report it in the CM bug tracker if you are certain it doesn't work. I recall others having the same issue previously, maybe they just haven't fixed their profiles yet.

The recent apps (now renamed to "overview" in Lollipop) search bar just uses the search bar widget from the Google search app. If it has an issue with loading that widget for whatever reason then it doesn't show up properly. Don't know why a safe mode boot fixes it.

Build the ROM/kernel from CAF repositories or cherry-pick a whole lot of CAF commits from them.

Clean flash. If it still happens then it may be a ROM/kernel issue, or just user error.

What is your Google App version?

bootloader protection is called locking the bootloader. You will have to use encryption (which I don't recommend since it causes issues occasionally) to protect the data partition while in recovery.

You can: - decompile and recompile the SystemUI to change it's resources (there are also apps that do this e.g. SoftKeyz or something like that.. don't know if they work on 5.1) - RRO/Layers theme on a supported custom ROM - CM12 theme on a supported custom ROM - Xposed (but unlikely to work)

The camera2 API can be used for almost any camera sensor. Each sensor has different capabilities (e.g. focus, raw), see here: https://gist.github.com/PkmX/fefff90bab3b6eb2847f It CAN theoretically be used for the front facing camera, but it's capabilities are extremely limited and somewhat...

You can try: - factory reset - putting your SIM in a friend's phone/put your friend's SIM in your phone - flash another radio version - ask your carrier

CyanDelta is unofficial. Maybe try flashing the regular zip, it'll probably work.

Also, see my quote below.

Gestures are done with the kernel, not the ROM. Porting the ROM as a whole is ultimately pointless - just use any custom ROM, which probably has all the features + more anyways.

But seriously: fastboot flash system system.img fastboot flash boot boot.img fastboot flash cache cache.img fastboot flash radio radio.img fastboot flash bootloader bootloader.img boot into custom recovery flash SuperSU/other stuff if desired isn't that hard. Driver issues? If you had driver...

The apps themselves do a bit of post processing too.

First of all, porting firmware from one device to another is extremely unlikely to function properly. If you can even get it to boot (the hardest part), a LOT will be broken as it was not built relevant to the hardware. Porting a custom ROM is even more pointless when it can be built...

See quote below.

- returning to factory images to take an OTA is pointless (you could just flash the new factory images) - returning to factory images to take an OTA to then flash a custom ROM is pointless (you could just flash the custom ROM) Just your desired custom ROM and flash it in recovery. Best to wipe...

download new factory images fastboot flash system system.img fastboot flash boot boot.img fastboot flash cache cache.img fastboot flash radio radio.img fastboot flash bootloader bootloader.img boot into custom recovery then flash SuperSU/other stuff if desired

You're complaining in the wrong place. This is XDA, not the Google/AOSP bug tracker—it has absolutely no relevance here and therefore complaining here is ultimately futile.

A portion of cache seems to be stored in data instead of cache or something. If you're syncing your bookmarks you should be able to wipe data without really losing anything except one or two settings.

Post logs.

Factory reset within Android just boots into recovery and performs a factory reset there. It should work, but if it doesn't then flash factory images using fastboot or LG Flashtool.

Pretty sure people have mentioned this a couple times in every kernel thread that has backlight dimmer. Its just the backlight not being even at the forced lower brightness. Nothing to do with or can fixed with the kernel, it might be different for everyone.

:p

First of all, it depends on how much you already know. There are numerous guides on how to build another existing custom ROM. I'd start with those first to be a little familiar with how a project is handled, but you could always just look for guides for building one from scratch AOSP if you...

First of all, that's hardly any wakelocks. If you have the same setup as before, it does not necessarily mean you'll have the same amount of wakelocks. If an app is granted a wakelock, then you'll have a wakelock. This can depend on the amount of notifications you receive and your usage on that...

The apks are open source. They just don't post them anywhere separately "officially". No particular reason to do so. Their official release is in the form of their custom ROM. Someone else will extract and post them anyways.

They do not upload their sole apks anywhere "officially".

No, EVERYTHING in Google+ is stored in their cloud servers, even your app settings. All you have to do after clearing it's data is open it once so it can sign in.

1. No. 2. Factory reset the Android Wear device. You'll hardly lose anything since almost everything is on the phone or synced to it.

You mentioned that you only ran into issues after a month. During that month a hardware issue could have possibly developed and the device was fine when you initially received it.

https://www.youtube.com/watch?v=7JHcgvb7Cp8

Try dirty flashing your ROM to get rid of anything if you previously flashed the keyboard/installed to system, then install the apk as a user app. No need to reboot after installing a user app. If that doesn't work then its a ROM or some other issue.