yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] khan_frd2002:
New update is up Colt OS v1.3 Mint [08/11/2017]

Highlights:

1.Switch to official LineageOS source.

2.Add Charging Rate Control

3.Add Boeffla Wakelock blocker driver

4.Few touch ups

Download:

https://goo.gl/vH8Bcs
[ONE Android Development] myshakugan:
Rom isn't booting up for me. Clean flash. All it shows is a black screen after booting.

Edit: Could be something on my end. Another rom is showing the same results for me. Will try a clean flash again.

Edit 2: Yep, was something on my end. Did a fresh install and it worked now.
[ONE Android Development] ggg333:
Worked for me on the first clean flash, but came from a different ROM.

Thank you developer for the ROM
[ONE Android Development] ziepicwaffle:
Just flashed this ROM yesterday. I love it! I'm surprised there aren't more users. There are a lot of features and the ROM still feels lightweight. Battery seems good so far. Thanks!
[ONE Android Development] tamboli007:
Did you find a working kernel with this rom ?
[ONE Android Development] pratikone1:
This is one beautiful ROM. The best. Keep up the good work. Any news about Oreo?
[ONE Android Development] rajatkumar6393:
Best Nougat ROM. Thank you for your hard work. Hope for Oreo real soon.
[ONE Android Development] Sreenath Paramasivam:
When will the Oreo update will arrive?
[ONE Android Development] Mr.Ak:
26th Jan.
[ONE Android Development] Uchiha_It@chi:
TopKek
[ONE Android Development] TriboDoP:
What time (also seconds please) ??
[ONE Android Development] Mr.Ak:
06:09:59 ist
[ONE Android Development] konstantin_sp:
Hi,

Does this rom has Ambient Display (hand wave, pocket)?

Thank you in advance.
[ONE Android Development] pratikone1:
So there won't be sea breeze for bacon? Isn't it?
[ONE Android Development] Pedrogg25:
I flashed the october build and now i am afraid that with that lineage os source might compromise battery, what do you think?
[ONE Android Development] Mr.Ak:
Why would lineage os source compromise battery life? :/
[ONE Android Development] Pedrogg25:
Because that has been the case with almost all the lineage roms
[ONE Android Development] Mr.Ak:
Hasn't been the case with me.Dunno why you think that.
[ONE Android Development] Pedrogg25:
I think that because it happens to me haha. Also I see a type of screen burn when i am on nougat roms. When i switch to 8.0 it goes away. Idk, really weird **** man.
[ONE Android Development] Sreenath Paramasivam:
I am experiencing a display issue in this rom as all underclocked lineage based rom. Did anyone experience the same?
[ONE Android Development] Srinivas D:
This ROM is died for Bacon.
[ONE Android Development] Mr.Ak:
This rom ain't underclocked. 0.o

Bad display,replace it.

---------- Post added at 07:17 PM ---------- Previous post was at 07:16 PM ----------

Maibi the OP is too biji to release update?
[ONE Android Development] Sreenath Paramasivam:
When i change some other the display is fine
[ONE Android Development] Mr.Ak:
Can you elaborate your display "problem" a little?
[ONE Android Development] Sreenath Paramasivam:
display turn little bit white oval shaped one sometimes but not all the times
[ONE Android Development] Pedrogg25:
That happens to me too with nougat roms, now i am in aosp rom and i dont see the issue at all
[ONE Android Development] Mrguojing:
download link missing..
[ONE Android Development] varaprasad1998:
oneplus one

the link has been expired how can i install colt os in my oneplus one ..
[ONE Android Development] Haider**:
The link is expire.

Link is expire.​
[ONE Android Development] Setting.Out:
Never quote the OP... Come back and edit your post please..​
[General Questions and Answers] pozidrivphil:
Hi,

I've been at this for some time. I'd like to configure one phone with a lot of tweaks and then make an image from that phone and clone it to over 50 others (all the same type; samsung XCover4 SM-G390F). At first I thought, easy, just install twrp and do nandroid backups/restore, but there wasn't a custom recovery available. Managed to compile TWRP for this phone, but now I see that the backups are created in a folder with the serial number for that specific phone, which requires me to change the folder name for each specific phone :(

I then looked at creating Odin flashable packages, trying to make an Odin package out of the system partition, but I always run into errors in Odin when flashing.

There must be a better way..

Any ideas?
[General Questions and Answers] LilAnt530:
FlashFire, or make one like the same package u make for Odin, name it .zip instead of .tar flash in TWRP, hopefully that helps
[General Questions and Answers] steefzz:
Hello Pozidrivphil,

I am currently looking fo a similar solution with te XCover 4 (SM-G390F). I also tried to compile TWRP for this phone, however i didn't managed to compile it.

For some other phones i also used TWRP backups to make a flashable zip file (it is possible to work around the serial).

Would you like to share your compiled TWRP? Maybe i can help you with creating an flashable image (i have to search for the scripts i used for them)

Ps. Ik zie dat je uit België komt? Je kan eventueel ook een PM sturen, dat maakt de communicatie wat gemakkelijker in het Nederlans ;)
[General Questions and Answers] pozidrivphil:
Haha! Incredible! There's very little love for these phones isn't there...

I successfully compiled TWRP with SElinux disabled, but weirdly enough I can't talk to TWRP through ADB, that's why I haven't shared my build with the TWRP team. It looks like the experts on the compile forum don't really know what's causing it either.

So for now I'm using a SDcard with an image and on every phone I first backup cache, then move my system and data images to that newly created folder and restore from there. Tedious!! So I'm looking forward to your solution, I have already spent way too much time on this :silly:

Sent you a PM with the recovery.

Edit: whatever, this is for the other ten suckers on the planet that own a Samsung XCover4 SM-G390F and are looking for a TWRP 3.1.1-0 (index that google!):

https://www.dropbox.com/s/opppfkdnm4rrkei/recovery.tar?dl=0

*again: adb doesn't work, and I'm not a proper developer; at your own risk*
[General Questions and Answers] palebluedot:
I just tried your TWRP image and it seems to work. Did you figure out how to get ADB to work? I was able to get ADB running with the following (highly experimental!) modifications to the file /init.rc:

on fs
mount pstore pstore /sys/fs/pstore

mkdir /dev/usb-ffs 0770 shell shell
mkdir /dev/usb-ffs/adb 0770 shell shell
mount functionfs adb /dev/usb-ffs/adb uid=2000,gid=2000

[B]write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 04E8
write /sys/class/android_usb/android0/idProduct 6860
write /sys/class/android_usb/android0/f_ffs/aliases adb
write /sys/class/android_usb/android0/functions mtp,adb
write /sys/class/android_usb/android0/iManufacturer ${ro.product.manufacturer}
write /sys/class/android_usb/android0/iProduct ${ro.product.model}
write /sys/class/android_usb/android0/iSerial ${ro.serialno}[/B]

I also added the following at the bottom of /default.prop (but not sure if they are necessary/have any effect):

persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb

One problem is that initially, Windows 10 (which is my development OS) just says "USB device not recognized" when the device first enters TWRP recovery, but if I unplug and replug the cable Windows recognizes the device and ADB starts working.
[General Questions and Answers] steefzz:
Hello Palebluedot,

What is your experience with your experimental code?

Would you mind to share your compiled TWRP?

I'm currently having issues when rooting the XCover 4 with the latest Android 8.1 firmware. Root with Magisk works, however i loose the imei when Magisk has customised the boot.img (when letting Magisk Manager customise the factory boot.img and also when flashing the magisk zip with TWRP).

Thanks in advance.
[General Questions and Answers] TheDarkMadness:
Just make a backup from the phone you want to install the backup on and write down the serial number of this phone then rename the tweaked backup to that serial number it should be flashable
[Remix OS for PC] ahmedamir:
Hi

This is my first post on your website knowing that i have been reading and following it for last few years. Also i would like to that all the developers and the supporters here.

I have HP Pavlion dv6 with intel i5 and hybrid graphics (Intel and Radeon HD 6400 M) i tried a lot to activate the Radeon card in Remix OS without success. Can anyone confirm if that is possible and how??.

Unfortunetly HP didn't allow the option to turn off the integrated GPU in the BIOS. I tried GRUB modes, without any success.

I appreciate any comments. Thanks in advancea
[Honor 4x Questions & Answers] lapist:
Duplicate post created by mistake, please remove this thread
[Android Apps and Games] wanderer1479:
If you are crazy about robots and machines, you will definitely like cool game Create Your Robot! You will have the opportunity to make a unique robot, and you will be able to express your creativity. It is perfect for both boys and girls, and there is no age limit for this game!

Get the amazing Create Your Robot here: https://goo.gl/hxapqV
[Nexus 6P Themes and Apps] Deleted member 5303752:
Hello all

viper4android refreshes very rarely and can not keep up with nexus / pixels.

I have seen many guides that suggested deleting the configuration file in /etc/audio_effects.conf.

I think it's a horrible thing! in fact, just insert few strings into another file in /vendor/etc/audio_effects.conf

Under libraries sections:

v4a_fx {

path /system/lib/soundfx/libv4a_fx_ics.so

}

Under effects sections:

v4a_standard_fx {

library v4a_fx

uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b

}

it is very important that selinux is set to permissive mode.

Open a Shell :

$ su

# setenforce 0

P.S. install busybox first
[Nexus 6P Themes and Apps] DEVILOPS 007:
Good guide but that setenforce 0 command doesn't stick after reboot as far as I know. To get it to stick you should use an app that does it or create a .sh file and add the permissive kernel code to it. Can't remember where the file goes though.
[Nexus 6P Themes and Apps] Deleted member 5303752:
In viper's app there is an option "disable selinux".
[Nexus 6P Themes and Apps] coremania:
You only have to go permissive with magisk and there's an module for it.

With SuperSU you can stay enforced.

Delete musicfx or audiofx and you're good.
[Nexus 6P Themes and Apps] mholloway:
Been trying for days to get viper to work,thanks man.works for me
[Nexus 6P Themes and Apps] Deleted member 5303752:
personally I prefer to add two lines of code instead of installing an application that allows another application to work :cool:
[Nexus 6P Themes and Apps] coremania:
Right very good guide, but you have to go and live permissive with it. The question is, what's better. If you root anyway ???
[Nexus 6P Themes and Apps] Deleted member 5303752:
this is a problem to be submitted to the viper developer :rolleyes:
[Nexus 6P Themes and Apps] mholloway:
Dev,you wouldn't happen to know how to get ATMOS working would you?
[Nexus 6P Themes and Apps] Curiousn00b:
I prefer to go permissive as well, besides the fact that I'm always permissive even when I don't have V4A installed.

Also, you don't have to install an app, you just put a permissive script in your init.d(if not using Magisk). For Magisk, you put it in /magisk/.core/service.d/.

I've created my own flashable zips to do this, and since it's Magisk, as long as I don't clean flash, I never have to worry about it. [emoji41]
[Nexus 6P Themes and Apps] Deleted member 5303752:
here we talk about viper. Magisk and company should be treated elsewhere. Just create an init file for selinux.
[Nexus 6P Themes and Apps] Curiousn00b:
Not a Magisk module. If you're using Magisk, you can't stick the init.d script in /system/etc/init.d/ since the system won't being using that location IF you're using Magisk. That's why I included both locations just in case someone that's using Magisk came across the post.

Either way, I was still talking about Viper.
[Nexus 6P Themes and Apps] snsone:
I've been using latest Magnum opus on 8.1 without any problems or changes needed to the system. And it works perfectly fine with viper+Dolby config
[Nexus 6P Themes and Apps] ultyrunner:
Maybe you can. Have never had ARISE or Viper work without permissive, on either Magisk or SuperSU.
[Nexus 6P Themes and Apps] coremania:
Not maybe, supersu makes it possible to stay enforced with viper and dolby. With magisk Viper might be possible enforced but dolby will run only permissive with magisk.

Tested so many times.
[Nexus 6P Themes and Apps] snsone:
Wrong.
[Nexus 6P Themes and Apps] coremania:
After every reboot I guess ;)
[Nexus 6P Themes and Apps] snsone:
Works after any reboot with enforcing, no need for permissive
[Nexus 6P Themes and Apps] ultyrunner:
Deleted
[Nexus 6P Themes and Apps] modzilla99:
[MENTION=1955721]snsone[/MENTION] are you using android oreo? And if so, how are you doing that?
[Nexus 6P Themes and Apps] snsone:
Simple:

Aicp oreo 8.1 / atock 8.1

Magisk 15.2

Arise with:

- core

- viper v2.5.0.5

- dolby digital

- sony (just to get music player to get correct tags)

- magisk module

- remove deep buffer

Make sure magisk module is on and magisk is working and there you go
[Nexus 6P Themes and Apps] tropical cactus:
If anyone has missed this, they should try it. Uninstall Dolby digital and flash this zip. Specifically for Oreo.

https://xdaforums.com/showpost.php?p=74880570&postcount=31697
[Nexus 6P Themes and Apps] snsone:
Dolby digital works fine on 8.1, you cannot mess it up. The version you linked to makes our loudspeaker sound like a telephone from my youth. I prefer the one included in the MO package.
[Nexus 6P Themes and Apps] tropical cactus:
Lol. Does it? Sounds a lot fuller to me. For more bass, you could also try the latest ainur sauron mod.
[Nexus 6P Themes and Apps] :
viper updates are too slow .....
[Nexus 6P Themes and Apps] snsone:
I guess I found settings that work for me in viper and dolby. The oreo dolby just makes the loudspeaker lose fidelity, while my headphones are happy, but every ear is different.
[Nexus 6P Themes and Apps] bsg411:
can someone give specific instructions on how to install viper on oreo using supersu?? and where to get the files from..

I keep getting either an error installing the driver or it say my busybox is messed up or im not rooted.
[Nexus 6P Themes and Apps] dazeone:
Use this and reflash viper https://play.google.com/store/apps/details?id=com.vatssyx.busybox
[Nexus 6P Themes and Apps] bsg411:
I thought sterison's busybox was the one to use? should i uninstall that first and try this one?
[Nexus 6P Themes and Apps] dazeone:
Yes uninstall first then install that one. I used to run into the same issue
[Nexus 6P Themes and Apps] bsg411:
Didnt work. Can someone post the viper files they used?
[Nexus 6P Themes and Apps] dazeone:
https://androidfilehost.com/?fid=889764386195922231
[Nexus 6P Themes and Apps] bsg411:
thank you....I was looking for viper tho.... your link is arise
[Nexus 6P Themes and Apps] dazeone:
Check the script it has many variants in package. Viper 2.5.0.5 ,Dolby Atmos,Sony something and more. You need to check the script and follow directions to install it

---------- Post added at 07:24 PM ---------- Previous post was at 07:15 PM ----------

https://androidfilehost.com/?fid=889964283620765959 this is similar but installs viperfx instead of viperArise
[Nexus 6P Themes and Apps] bsg411:
This worked...thank you.
[Nexus 6P Themes and Apps] dazeone:
[emoji106] glad it worked
[Nexus 6P Themes and Apps] axelrodmagma:
https://xdaforums.com/android/software/soundmod-sonymusicwithsseviperaudio-t3536196

Try this one this has everything viper, Dolby,Sony beats
[Nexus 6P Themes and Apps] bsg411:
I can't get Dolby installed. I have magisk 16 installed. What steps did you take to install viper and Dolby?
[Nexus 6P Themes and Apps] bsg411:
You know how to get this to work using magisk? I can get viper to install via magisk but not Dolby.
[Nexus 6P Themes and Apps] dazeone:
I haven't used Dolby so I'm not sure but I'll look around
[Nexus 6P Themes and Apps] bsg411:
I'm still looking myself too. Appreciate it
[Nexus 6P Themes and Apps] sethukrishnan:
I'm using Dolby on lineage os 15.1 and its working flawlessly but o ain't using viper or any other mods
[Nexus 6P Themes and Apps] bsg411:
How did you get it working? Are you using Magisk? If so, which version? What process did you do
[Nexus 6P Themes and Apps] dazeone:
Have you tried this? https://xdaforums.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508
[Nexus 6P Themes and Apps] bsg411:
I tried it...it didnt work for me.I really only wanted it because my in call earpiece volume is extremely ridiculously low by default and dolby is the only thing ive used that makes any kind of real difference in that earpiece volume on my 6p.
[Nexus 6P Themes and Apps] dazeone:
Have you tried custom kernel and raising the volumes up
[Nexus 6P Themes and Apps] bsg411:
Yes....using elemental x under sound mod section and turning the gain up...but it really doesnt do much
[Nexus 6P Themes and Apps] sethukrishnan:
I'm using magisk 15.3

Not using viper only Dolby atmos

I'm not able to attach screenshots...it always gives me network error.

Dolby version DAx2.5.0.15_r1

Axon 7 Oreo Dolby atmos version

And lineage 15.1
[Nexus 6P Themes and Apps] bsg411:
Thanks... Got it working using this procedure from RyperX over at the Dolby for Oreo thread:

Got it working now on my OP3t (my fault used normal twrp zip not magisk)

For me worked the following step. ( i dont think there is a difference installing magisk module through twrp or magisk)

Install v4a with Magisk

Reboot > Checked if working

Install latest Atmos Unify Version with Magisk

Reboot > 2 Apps was here but did FC

Install AML with Magisk

Reboot > Everything works now
[Nexus 6P Themes and Apps] sethukrishnan:
;):svetius:
[Nexus 6P Themes and Apps] brambizimski:
I flashed v4a through magisk, got the zip through magisk also, the app opens but i can't seem to install the driver it just says "Installation failed because of an I/O error. Try rebooting your device and try again", which I did but same error, i'm also sure the app has root permissions.
[Nexus 6P Themes and Apps] bsg411:
The version of v4a I'm using does not need the driver installed...once flashed the driver is operational already. Are you using the right version of v4a? I flashed it inside the magisk app and then immediately rebooted. I'm using the one labeled "Viper4Android FX for Magisk v 15" created by shadySquirrel.
[Xiaomi Mi A1 Themes, Apps, and Mods] n6i5k7h5:
I am planning to root and use api2 for gcam. Will I receive updates after that? Also would those updates install successfully if rooted? If not any idea on how to just get api2. Can I UNROOT the device and will that install updates successfully?
[Xiaomi Mi A1 Themes, Apps, and Mods] gusthy:
No.

The thing you can do is that you install September ROM with MiFlash, then you get update. (You can install September ROM without loosing data.)

At the moment there is no way to keep root after update using current tools.
[Xiaomi Mi A1 Themes, Apps, and Mods] Ex-Hunter:
You will receive updates after root. I was on rooted September patch and I have successfully installed October OTA update. Just follow these steps and you'll be good to go.

Download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.

Enter fastboot mode on your device. I am assuming you know how to unlock your bootloader and you have all the ADB drivers installed.

I suggest you NOT to flash TWRP but boot to it instead. To do so type

fastboot boot recovery.img

In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; While pressing vol down button connect the USB cable. You should now be in fastboot mode. Try typing the cmd again and it should work.

Flash Magisk-v13.4.zip via TWRP and reboot to system.

Download the latest Magisk Manager and install. DO NOT update Magisk.

Use this module to get camera2 api.

Download and install normally when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.

P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
[Xiaomi Mi A1 Themes, Apps, and Mods] Flare_91:
Hi, i have some mistake at this point, if i try to install newer magisk manager i cant because "i have another app with the same name", so what? using magisk 13.3 with the manager 5.1.1 provided by itself to active the cameras module? thanks :)
[Xiaomi Mi A1 Themes, Apps, and Mods] Chazy12:
---------- Post added at 10:22 PM ---------- Previous post was at 10:21 PM ----------

[/COLOR]
[Xiaomi Mi A1 Themes, Apps, and Mods] Kripacharya:
How to enable Camera2api after rooting with magisk? Please inform

I just got a MiA1.I know how to root it with magisk but don't know how to enable camera2api.Will you please help me?
[Xiaomi Mi A1 Themes, Apps, and Mods] Ex-Hunter:
You should use Magisk 13.4 for pixel not Magisk 13.3. Download it from here.

After flashing install this.

If you get any error, uninstall Magisk Manager--just the manager and install the downloaded apk. There shouldn't be any problems.

It should be possible. But I am wary of editing system partition because it might interfere with OTA updates and SafetyNet check.

Take a backup of system partition using TWRP just to be safe and proceed with editing.

Kindly report here if it works. Goodluck!:fingers-crossed:

Sure, just follow the steps I have written above. You'll definitely be able to enable camera2 api and more!
[Xiaomi Mi A1 Themes, Apps, and Mods] Chazy12:
Thanks for the answer.

It's only a line of code.. I hope there'll be not a problem for just one line..

Inviato dal mio Mi A1 utilizzando Tapatalk
[Xiaomi Mi A1 Themes, Apps, and Mods] NITRO_100:
Ok, so I have Magisk 13.4 and manager app 5.4.0, and when I install camera module and restart it doesn't get that line written in build.prop so it doesn't work. In magisk it says that is installed. Is there something additional that has to be done or ?
[Xiaomi Mi A1 Themes, Apps, and Mods] Flare_91:
Yes, my mistake i was already on 13.4 so i have unistalled magisk manager and then i have installed the latest version.

Me too and i have add the lines manually then its ok for me.
[Xiaomi Mi A1 Themes, Apps, and Mods] nikkpap:
So the only difference for now (hope the good guys here will solve this) is that we can use twrp but only in temporary way using " boot" command and not "flash" then use the known progress and install root etc etc etc... Can this guide work in a vanilla out of the box phone with the October patch on it ?

To reboot to bootloader then boot to twrp install root then reboot then all ok ? Or you have to set a partition first

Thanks again for the help
[Xiaomi Mi A1 Themes, Apps, and Mods] Ex-Hunter:
Yes it will work. No need to set a partition.
[Xiaomi Mi A1 Themes, Apps, and Mods] Ex-Hunter:
Do you use any PIN/password? If so, you have to input it when the TWRP boots up.
[Xiaomi Mi A1 Themes, Apps, and Mods] cmk7128:
Hi,

Have you tried using the newer Magisk V14.2 (1420) to root MI A1?

Thanks and best regards!

William
[Xiaomi Mi A1 Themes, Apps, and Mods] Ex-Hunter:
Yes, but unfortunately it doesn't work and the device will be stuck in a bootloop. [MENTION=4470081]topjohnwu[/MENTION] is working towards a fix. I'm sure we'll get the official Magisk on our device pretty soon.
[Xiaomi Mi A1 Themes, Apps, and Mods] cmk7128:
Thanks for the feedback, much appreciated. BTW, do we have to fastboot flash the original/unpatched boot image before we proceed to download and install the new security update patch (eg. Oct to Nov 2017 update)?

Thanks!

William