Search results

So now safety net passes without installing magisk? What about SELinux, it's still permissive?

Clean install,Wi-fi is not turning on. Will update this post with logs in a minute.

Oh well,I guess we are back in the game..right?! :P

I use nano. But that has nothing to do. I was using nano on nightlies and gcam was working perfectly EDIT ------- Mindthegapps fixed the problem. Time to fix safetynet without magisk! :D

I build with opengapps built-in...maybe i'll try with mindthegapps. It's normal for gcam to use only the wide-lens. Snap can use both cameras..at least in my build.

I'm a home builder too. Does gcam work for you? Tried latest arnova version and it always throws an FC.

Sorry for the delay... Telephony crashes because i build with Jack server disabled. If you build normally there won't be any problems! :) galaxyfreak was right,there aren't many things to release. Actually you can cherry pick most changes from the link he mentioned. BTW latest manifest I...

That's because you never flashed the updated bootloader...Instead of googling around please follow the instructions written in the OP

Latest changes are not on my github...I'll update it next week

About 3000 days

And here we go. https://review.lineageos.org/#/c/LineageOS/hudson/+/214926/ got merged! We got official support!

Well well... https://github.com/LineageOS/android_device_xiaomi_tissot

I know what treble is. That's why I said "official treble would be actually helpfull". For example,if our camera HAL needs shimming,getting treble with our existing blobs will do nothing...every next android version will need that shim as our vendor files are still based on an older HAL. Real...

Why do you think porting would be so much easier? Custom ROMs already include a /vendor folder,so instead of that folder there will be a vendor partition,so what? We'll just make the download smaller,cause all those blobs will be preinstalled on the device. One mkfile less :P Don't get me...

BETA 1 - Latest Android/LineageOS changes. - April security patch. - Fixed leds. - Fixed Time resetting after reboot. - Fixed native camera recording (still buggy,green line on back camera and no front camera recording!). - Enabled Android Go configuration. - We now build GPS HAL without any...

I'm not a fan of telegram...but we could use an IRC channel! I'll update this post with more info. for the testers. No,we use nothing from kitkat. Blobs are stock 5.1.1 or from SXD zip. Strange thing is in some older N builds you reported lags etc after some kernel changes,I reverted those...

Update: Sorry for the delay,you know...life happened :D About the build: Green line is presented on both 1080p and 720p recording. Lower resolutions do not even work. That means front camera cannot record videos. Leds - galaxyfreak will investigate on them. Timekeep - I got a hint on what it...

Video recording fixed! But: There is a thin green vertical line on right side of the recording. Definitely present on 1080p, but may be fine with 720p. Also we enabled Android Go configuration for the next build. We will look into the remaining bugs and try to figure some out. Next build maybe...

I won't build it...I have no time. :)

I'm out of ideas...it worked like a charm for me! Some people say that stock nougat works better...you can try that..steps are the same (Don't forget to boot stock ROM after flashing it!) Or maybe "adb push" f*cks with you....pf,strange!

Someone who actually developed for a device. With his own sources. :) Check my gh and forum history! I love how someone took the time to commit the needed changes to fix the official twrp but the "maintainer" never accepted them! https://gerrit.twrp.me/q/project:android_device_xiaomi_tissot

I love how you added tissot on "official" RR devices. Without sources... And you call yourself a "dev"...lol

You just ran it? You have to boot stock oreo too! Just boot it once and after that follow the steps.

Interesting. Did you tried any other recovery before? Start fresh by flashing stock ROM, boot it once and after that follow my steps.

Now that's a first... What was your base ROM?

Ignore those errors and continue. You need to hear it from him? Just have some patience! He released kernel sources...it's something.

Yes,it's normal. Our recovery is built in boot.img, we don't use a separate partition for it. LOS uses it's own recovery.

Yes,use this one.

Same posts over and over...for the last time I flashed this rom over a locked,pure stock 8.1.10 ROM,steps are simple 1. Unlock your bootloader. 2. fastboot boot deadman_twrp.img 3. Wipe system/data/cache 4. Reboot into bootloader 5. fastboot boot deadman_twrp.img 6. Flash ROM only 7. Reboot...

Pronto was already enabled here. "=y" means that the driver is included in-kernel, "=m" means it's a module...(I prefer in-kernel drivers but that's your choice :) ) https://github.com/kunalshah912/kernel_xiaomi_tissot/commit/f6110f2276ee8fa2eb93814d0b1136ebcbc45824 Why remove wificond? 8.1.10...

Most of the needed commits are binder related Plus you need some extra defconfig flags..you can extract defconfig from stock boot.img....

Bootloop. log - https://gist.github.com/kj77/8fe579ecb99d15ba9d03518ce7c5bd04 Also may I ask why we need HAL1 recording hacks while we have official Nougat blobs?! https://github.com/ghpranav/android_device_xiaomi_tissot/blob/cm-14.1/BoardConfig.mk#L108 EDIT: Sensors are dying...

ALPHA 4 Changelog - Latest LineageOS/Android sources - Include Snap camera app - Many of the cm-14.1 features - Dark mode - Colour engine - New power menu - New LineageOS adaptable icons Download

Add this in your local manifest and include it in your next build. It will fix pic-taking :)

https://pastebin.com/9MjNYp5T BTW my "base" is latest oreo (8.1.10)

So they actually took LA.UM.5.3-06310-89xx.0 and squashed LA.UM.5.6.r1-04600-89xx.0 on top of it. LOL! Nice work btw, will make porting easier... Guys please,do not spam this thread asking basic dev stuff (How to setup build env. etc..) Google is your friend.

No, it's not dead.

Are you still on this? I managed to decompile dtb from latest fastboot image (7.12.29 - Android O) Also extracted stock config. BTW it would be better if we start with clean 3.18 tree and port the needed drivers there instead of hacking mido kernel Forked an upstreamed version of 3.18 here...

They are actually using another partition as /vendor. https://github.com/sirmordred/platform_device_xiaomi_gemini/commit/ca4c76d62a9186e06515a948ae22e0b14928facc#diff-ada958ac3a6662f731884325169992e4R13 Still is not that simple for us. We don't got a spare partition to mark as /vendor...

So mi5 devs are gonna create a new odm/vendor partition and push every hidl hal there?! Interesting,can you share a link about that?

Useful logs? Our device does not support treble This ROM will never boot,I bet it doesn't even include any device related HAL. Do you even know what treble is?

Any news regarding this PR? :)

There is no "clean" version of android. only pure AOSP is "clean". Everything else is "stock". Mi A1 is "stock". Not as "google-stock" but as "kinda-google-stock"! Even on android one site screenshots you can see that there is a "partner" folder on the homescreen! I agree about fanboism 100%...

Yeah we only have 1636372 threads about it. Someone please call a mod.

So, OP wants pure android? Cool! Gapps are not pure android! They are proprietary software and have nothing to do with android. We should remove them too! The real pure android is here . Sync and build it if you want.

Yeah I remember those problems,althought we kinda fixed them in last CM13. Anyway I agree,that's why we QCOM solution for so long. ;)

It's probably due to RAM refresh. It's a crazy idea/test. Let's see if it brings any changes. About heating, 3G/4G uses more power than WiFi..it's normal for the device to heat up more. For Nougat and Oreo we switched from thermanager to a kinda "closed-source" solution. We can always revert...

No Idea why this happens. It only happens on devices with alternative sensors.

Hey guys, Please, replace /system/etc/sec_config with this and report back.

Not gonna happen