Search results

I've just started working on LA 13.0 for land again. Pushed a bunch of changes to my trees the past few days: https://github.com/zwliew/android_device_xiaomi_land

Hmm, may I know which MIUI release these libraries were taken from?

This is actually in the works :) WIP Gerrit patches: https://review.lineageos.org/#/q/topic:network-traffic An updated Gello based on the latest Chromium release is also planned.

LineageOS Gerrit is up now. What this means is that all the CM to LineageOS rebranding in the code should happen shortly (and LineageOS builds can start churning out soon). On another note, the LineageOS infrastructure is undergoing some restructuring. Once it's settled however, there should be...

Download: https://goo.gl/HNpDyO Changelog: Fix IR blaster (courtesy of frapeti) Fix video recording Implement raise to wake Switch back to Snap camera Ship with OpenGApps Pico (this is somewhat controversial, but is easily removable with OpenGApps scripts if wanted)

Sorry for the lack of builds guys. Ive been pretty busy thus far and haven't had time to release a build. I'll try to release one after a week long holiday I'm taking.

Simple fix for video recording: Append media.camera.ts.monotonic=0 to /system/build.prop Brief explanation: The MSM8937 camera driver is now using the boot-time clock rather than the wall clock for video recording timestamp reference. Setting media.camera.ts.monotonic to 0 forces the framework...

The IR blaster is already fixed in the upcoming build (if you had noticed the changelog). Also, I just fixed video recording as well, this time for reals :). No changes will be pushed to my device tree yet since my workstation laptop is out for repairs, meaning I can't upload anything for now.

Can y'all try this to see whether it fixes the IR blaster: 1. Launch the terminal 2. Enter the following 2 commands: chown system:system /sys/class/leds/infrared/transmit chown system:system /sys/class/leds/infrared/brightness 3. Try using the IR blaster (If this works, you'll have to...

Im not working on cm 14.1 for redmi 3s yet. I just created the branch so that I can fully sync the source code when working on other cm 14.1 projects. I would only work on cm 14.1 after getting my hands on the kernel source.

It already is merged in CM 13.

To those wondering, don't install Xposed on CM. Google's latest Android security patches break Xposed, and I'm not sure whether anyone at CM intends on fixing support for it. Basically what cruplezone said. Although I released the first android 7.0 build for jfltexx back in Aug 27, CM 14.1 is...

I just set up CM 14.1 branches for Zuk Z1. You're welcome to submit bringup patches :) I'll try to see whether getting another maintainer for the device is possible.

Let me re-iterate: Xposed bootlooping is *not* a bug. It is *intentional* breakage by Google themselves in the latest Android security patch. Whether I 'fix' the bootlooping really depends on whether I feel like it at this point.

New build :) Download: https://goo.gl/1N4EUu Changelog: Enable LTE option Add LiveDisplay color profiles and picture adjustment tunables (similar to MIUI) Add Reliance Jio APNs Update firmware on install-time Note: Xposed still doesn't work. I haven't had the motivation to look into it yet...

The internals of the Sony CM 13 ROM looks really similar to mine. What bugs have been fixed in that ROM? Thanks for the tip, that ROM is indeed stolen from me. You're most likely using either the network or fused location provider (the location provider that uses your network rather than...

As a temporary workaround for the video recording issue, use Footej Camera.

I merged Reliance Jio APNs into CM 13.0 just now. They will be in the next build.

Xposed resulting in a bootloop is most probably due to extended security hardening in the Zygote process done during the November Android Security Bulletin update. Whether CM is going to whitelist the Xposed process is yet to be decided. To be sure, does anyone have a logcat of the bootloop...

flo will have an official CM 14.1 build soon, courtesy of Simon Shields (forkbomb) :). He took the rebased trees and brought them up to 7.1.

flo will have an official CM 14.1 build soon, courtesy of forkbomb (Simon Shields). :) He took the rebased trees and brought it up to 7.1.

Can someone with a goodix fingerprint sensor send me a logcat and a kmsg of you touching the fingerprint sensor (attempting to unlock the device)?

Nope. can we not trust AIDA64 on this, and follow what Chifty has said? Attached below is what AIDA64 shows me and my fingerprint sensor works well. It would be helpful to know exactly whether a device is using FPC or Goodix sensors. This is because i need info on why some devices don't have...

Sorry, accidentally fell asleep while the 10th Nov. build was compiling. Anyway, the build is now uploaded to the GDrive. Download: https://goo.gl/RJCwFY Changelog: Fix video recording Update libraries and kernel to MIUI 6.11.3

I don't mind people releasing unofficial builds in this thread. :) Also, to get it to boot, you need this WIP SELinux commit on Gerrit: https://review.cyanogenmod.org/#/c/167358

Chill guys. Steve doesn't really roam around XDA anymore. Either way, Steve (cyanogen), dianlujitao and Grarak are all the main maintainers of CM 13 for OP3. Taker18 compiled from the official source. Now you have official nightlies from the official source itself - the guys who fix the...

We're using a prebuilt kernel so we don't need any of that. Which MIUI ROM version did you come from? Could you try flashing V8.0.3.0.MALMIDG before flashing this ROM, if you weren't on V8.0.3.0.MALMIDG before? Link...

May I know what the command 'getprop ro.product.wt.boardid' prints for you? The fingerprint sensor works fine on my device, but it may be due to differences in model/hardware. Just for the record, my boardid is S88537BA1. Camera was broken because of an accidental change I made last minute :/...

I'm mainly working on the Redmi 3S now, but I'll try to get the rest of the issues on jfltexx ironed out by the end of the week. If all goes well, expect 14.1 nightlies maybe, next week?

Notes Be sure to... Turn location services off to prevent a constant wakelock Known issues GPS (network and fused location work fine) Goodix fingerprint sensor (FPC sensors work fine)

Changelog Upcoming Switch back to the Gello browser Update libraries, kernel and configs from MIUI 6.12.15 No longer ship with OpenGApps 22-12-2016 Fix IR blaster (courtesy of frapeti) Fix video recording Implement pick up to activate Ambient Display Switch back to Snap camera Ship with...

CyanogenMod 13.0 for Redmi 3S (unofficial and alpha) Downloads https://goo.gl/N60xs2 Installation guide * Download cm-13.0-[latest_date_here]-UNOFFICIAL-land.zip * Reboot to recovery mode * Factory reset (for first-time flashers) * Flash the ROM * Flash GApps (for first-time...

I have CM 13 almost daily driver material currently after a couple days of work. I'll update the sources after I get a few minor bugs worked out (probably by the end of the week).

Yeah, I can confirm that camera HAL3 works fine on Redmi 3S.

No worries. I didn't mean to come across as authoritative. Was just meaning to correct the misconception I've been seeing quite a bit around here. Just to reiterate, the behaviour is caused by incorrect reporting of battery current by our battery driver.

Introducing CyanogenMod Recovery for Redmi 3S. It is a no-frills recovery - it may not offer as many features as TWRP, but it's just enough for the simple poweruser. For those who are wondering, this is the recovery that comes with CyanogenMod 13.0. Download: https://goo.gl/N60xs2...

Hi all, I recently compiled CyanogenMod Recovery for my new Redmi 3S, A.K.A. land. It is a no-frills recovery - it may not offer as many features as TWRP, but it's just enough for the simple poweruser. For those who are wondering, this is the recovery that comes with CyanogenMod 13.0...

That's also not the right behaviour. Our device is currently displaying incorrect input currents, resulting in the lockscreen displaying the wrong strings. On AC, I measured that it should be displaying 'Charging quickly'. On USB, 'Charging'. That's what the patch I mentioned earlier is...

The current 7.1 release is exclusive to Pixel. Google won't certify any other devices released on it.

> it displaying "Charging Slowly" is normal behavior This is definitely NOT normal behaviour. I just haven't gotten around to fixing it yet. I do have WIP patches on the CyanogenMod Gerrit to fix it though. (http://review.cyanogenmod.org/#/c/160486/) It's quite unfortunate nobody else has...

You should be able to build and boot fine with just these 2 patches: http://review.cyanogenmod.org/#/c/167358/ and http://review.cyanogenmod.org/#/c/167359/ Yeah. I'm trying out CM 14.1 as we speak. Although Android 7.1.0 is exclusive to the Pixels, nothing is stopping CM from getting a taste...

I'm running exactly that configuration on CM 14. It's quite likely it works fine on CM 13 as well. There are some VoIP patches otw that could fix the VoIP issues. I just haven't fully reviewed the patches and verified them.

The build fix (actually simply a partial revert) has been merged. Resync and rebuild. Do take note that you'll need this SELinux patch in order to boot: http://review.cyanogenmod.org/#/c/158323/

CM 14 has been buildable and workable for a few months now. I just haven't released a build due to some issues like video recording and some WiFi quirks. In fact, much of the N bring up work was really done by B--B and I. Plenty of hours have been put into this.

What app are you using that has that issue? I'll take a look. Overheating is an issue that I've not been able to solve for now, but it has more to do with 'unknown CPU loads' rather than the CPUfreq subsystem (which scales higher since there is more CPU load). Regarding the 'issue' you...

Yes, CM 14 is working pretty well at the moment. The main reasons why I haven't released more builds are 1. lack of time, and 2. I don't want to release half-baked builds lacking in features and having a few bugs (camcorder)

I need an actual test case for me to reliably reproduce the issue. Otherwise, I wouldn't know what the issue is. Since my year-end exams are near, I also don't have the time right now to try out all the different VOIP apps out there to reproduce the issue. Edit: Even simple info like what app...

Thanks for your wonderfully helpful input.

Could you post a test case and the comparison between the current result (from CM) and the expected result (from GPE/TW)? Something like the steps to reproduce the issue.

Generally I've been working on CM 14, but there hasn't been a build that's CyanogenMod-esque enough for me to be satisfied with releasing. There are also some bugs (i.e. camcorder) that need to be fixed, but progress is slow since school and exams have started. The previous bugs from CM 13 also...