Recent content by anon768

I don't see the point in booting to twrp. All you need to do is to boot into fastboot and apply the adb commands.

It's in an experimental stage. New builds are probably compiled every time there's some code change. It's not meant to be practical, it's for testing. The ROM right now really isn't quite at a stage where the average user should run it.

The ROM is unfinished. Not everything is working correctly. If you aren't willing or unable to investigate the issues yourself, wait until the ROM is more stable. If, for some reason, you want to use a broken, unfinished ROM, I think the 180222 build has working WiFi.

It's an experimental ROM, it's bound to be buggy. Little you can do about that, apart from working on the development so it's getting stable more quickly. I mean, not even LineageOS is finished for Andorid 8. It just takes some time.

So, the screen on my Note 4X broke, and I wanted to replace it. Long story short, the battery is glued down hard as **** and I managed to damage it, and it burst into flames. I'm fine, I was prepared, nothing but the phone suffered any damage. But now I'm sitting here, with a phone that's...

Taking code from another ROM isn't kanging. Kanging is taking code from other ROMs without giving credit. And really, taking features from others is good. Sure, we need people who develop new stuff, too. But there is zero point in 1000 different implementations of the exact same thing. Why not...

Well, without the right drivers, doing anything with adb is kinda pointless. These help. Still, pretty weird that Google doesn't support the 5X, epsecially because literally no other Nexus device has these issues.

So here's the thing, my Nexus 5X, when loaded into bootloader and connecting to my computer running Windows 10, doesn't work with the official drivers. (https://developer.android.com/studio/run/win-usb.html) It connects fine, and reports itself with the hardware id "USB\VID_18D1&PID_D00D"...

Latest ROM works great, the Slim navbar is much appreciated!

The latest build doesn't have the extensive navbar button customization of the previous builds. Would be great if you could bring that back!

THank you, that worked marvellously!

Anyone?

Hey folks, to avoid doing this manually with every nightly, I wanted to change some build.prop values via a flashable zip, which doesn't seem to work. I used the script from here and modified it for my needs. It doesn't throw an error in recovery, but doesn't change any values, either. Here...

Just curious, what exactly happens when you use a CAF kernel? I use the CAF version of ElementalX with your build and everything seems to work just fine.

I think the performance problems and lower RAM might be related to ro.config-low_ram=false That setting used to be ro.config-low_ram=true up to this build, so maybe setting it to true again might solve these issues. 4.4 is the best android version I've used on the Defy so far. It's a lot...