Recent content by Bolick

>> screen auto-rotation does not work > Reinstall stock rom your persist is wiped Well that's what I did exactly. I mean right before Bliss I installed latest Chinese stock MIUI (not even MIUI.eu) in a naive hope to recover whatever I could have corrupted with previous ROMs and only then...

Hm... that's funny. If I use some external neodymium magnet (the one I use for pinning notes to a metal whiteboard) then the tablet wakes up. But the one which is built-in my cover doesn't wake the tablet on Bliss while does that on MIUI (as well as its derivative MIUI.eu). So I guess there must...

Just flashed, works quite well so thanks to all the BlissROM devs. One thing that doesn't work though is smart cover that used to work on MIUI ROMS before (like earlier today before flashing Bliss, i.e. all HW and magnet are in place). That's what I get from logcat when turning on "Enable Flip...

After update to the latest weekly (omni-9-20190630-clover-WEEKLY.zip) I can no longer enable Wi-Fi seeing the following in the log: 07-05 09:28:06.807 718 718 E [email protected]: Failed to write driver state control param: Invalid argument 07-05 09:28:06.807 718 718 E...

darkobas is there a chance to enable round corners in system UI? The point is real LCD in the tablet is plain simple rectangular one though screen cover "emulates" round corners. But if you look at any corner at a particular angle you may see those "hidden" corners of the screen which is well...

Interesting finding - even though I own Wi-Fi only tablet I'm seeing "Mobile network standby" consumes 22% of the battery when tablet is idling with screen turned off and nothing being run (like no music player etc). See attached screenshot.

Funny, that seems to be already solved exactly in the same way for all Omni ROMs, see https://gerrit.omnirom.org/#/c/android_vendor_omni/+/33461/

Probably I'm doing something wrong but once I flash Open GApps Nano for ARM64/"Android 9.0" the tablet is stuck in boot animation. Wiped data, system, vendor. I have 3Gb/32Gb non-LTE mi tab4. See logcat here: https://drive.google.com/open?id=1JOCvcJ2w5hRKsgn8GNGQZ-gWuUTA71y9 What looks...

I've just got "bluetooth.default.so" built from latest official sources (android-4.3_r1.1) for Galaxy Nexus with this patch applied https://github.com/CyanogenMod/android_external_bluetooth_bluedroid/commit/e6a380dbe5c269cf4b5ba95935e4e40cfb133032. Resulting file is attached to this post. Just...

From what I see on my phone there's a file "/data/data/com.android.email/files/deviceName" that contains device name. Exactly the one "androidc####". Why don't you try to change its contents manually and then try to connect to your Exchange server? Another question is why are you so sure...

So as of nightly from March 17 the fix is implemented and enabled Bluetooth no longer drains battery. https://jira.cyanogenmod.org/browse/CYAN-51 http://review.cyanogenmod.org/#/c/31201/

Indeed, Matrix kernel has this issue fixed with this commit: https://github.com/mathkid95/linux_samsung_jb/commit/0ca6ad998e09b7278475a3f363e29078253a454b Which is originally in CM kernel for aries (Galaxy S)...

As I promised, did some more study and filed an issue on CM issue tracker - http://code.google.com/p/cyanogenmod/issues/detail?id=7072 Seems like an issue is in kernel guts.

Still see the same issue on CM 10.1 M1 on Nexus S GSM. For me disabled bluetooth solves this issue (battery drain) but as soon as I enable bluetooth once again issue re-appears. Reboot, cache/dalvik-cache clean-up make no difference.

Could be, but the point is I had no Bluetooth enabled device nearby but nevertheless BT kept my phone awake (and BT icon in notification bar was gray saying that there's no active connection). I need to look into dmesg to find out what could be a real problem. I found something similar reported...