Database Info

[ROM] CARBON-KK-UNOFFICIAL_f2fs-20150526-moto_msm8960

Hi guys,
for those of us who are waiting for at least the M1 of CM12 before switching lanes, I did a build of Carbon (and a few of CM11, previously) for our Photons.
This is an odexed ("user", not "userdbg") build, running on the cm-12.1 kernel branch and using the latest available f2fs_tools. It also features a modified init which can use either f2fs or ext4 for /cache and /data - so switching to f2fs is highly recommended, but not mandatory. Superuser is included.
This is esentially for those who switched to CM12 just for f2fs; it's miles faster than cm12, and a bit more responsive that the old official cm11 nightlies.
A word of warning. TWRP's "change filesystem" function formats the partition (PhilZ does too, but at least it makes that explicit).
So what you want to do when switching from an ext4 ROM is,
before you begin: copy everything in the internal sdcard somewhere on the external sdcard; this is needed, since the "internal sdcard" is actually a folder in /data;
in TWRP, begin by creating a backup of /data (that saves everything except the "internal sdcard" and /cache - that's why you need step #1);
do the FS change for both /data and /cache
restore the /data backup, on the freshly formatted /data partition; ignore the "different filesystem" warning, it's inconsequential;
install the ROM;
once you booted the phone, copy back the old contents of the internal sdcard
You only need to do this when you change filesystems, which will be exactly once if you like my ROMs And obviously, if you don't, you have to use the exact same procedure before flashing an ext4 ROM, if you don't want to lose data.
Though, in all fairness, I'd recommend flashing this cleanly - unless you're upgrading from an ext4 Carbon build.
A note on the radio
I have included a tool called radio-tool (of my own design) that allows people to enable/disable the US GSM lock and individual network bands;
if you're having the SIM mod, and are from, or have business in, the US, you can use it to kill the CDMA and Sprint LTE bands altogether, as well as to enable US GSM bands and disable the US GSM lock;
the source code is here
Use (as superuser)
Code:
radio-tool [dbg] [{+|-}opt [...]]
where opt is one of
uslock - US GSM lockout
cdma - CDMA bands (CDMA800 / CDMA1800 / CDMA2000 1xEV-DO)
usgsm - US GSM/HSPA bands (GSM850, GSM1900, WCDMA850, WCDMA1900)
eugsm - EU GSM/HSPA bands (GSM900, GSM1800, WCDMA900, WCDMA2100)
sprlte - Sprint LTE (LTE25, 1900)
vzwlte - Verizon LTE (LTE13, 700)
Download:
ROM: CARBON-KK-UNOFFICIAL_f2fs-20150526-moto_msm8960.zip
Recoveries: TWRP-2.8.6.0-20150526-f2fs-moto_msm8960_jbbl-xt897.img, PhilZ-6.59.0-20150520-crkk_f2fs-moto_msm8960_jbbl-xt897.
You do not need to use a su app with this; but if you want to, please use the latest SuperSU. Attempting to use a different, or older, su app could result in no radio.
Changes from stock Carbon:
alternative mount points support - this enables the ROM to work with either f2fs or ext4 for /data and /cache
tuned mount settings - kickass speed with both ext4 and f2fs
256MB of lz4-compressed swap space (zram0)
built on gcc-4.8-sabermod
build.prop tweaks - this defaults to GSM/WCDMA - plus a few radio and network tweaks;
added a few goodies that are present in CM builds (Term, Apollo, Calendar, CMWallpapers, VideoEditor, plus the cmdline utils);
removed the stats and the update apps (for obvious reasons)
added Romanian (programmers) keyboard support in Asanti Keypad
built with: twrp 2.8.6.0, cm12.1 kernel, cm12.1 f2fs-tools, cm12.1 e2fsprogs, cm12.1 exfat, cm12.1 fuse.
(this will allow me to pick up any improvements in kernel, file systems, and recovery, with great ease )
Quirks:
MTP doesn't start by default in TWRP, despite the fact that it claims to be enabled; disable and re-enable MTP, and it will work
in PhilZ' mount menu, entries for cache and data are duplicated; this is cosmetic - mounting and umounting works just fine, regarless which of the two entries for each partition you choose
.
Older, CM11 vanilla builds:
Download:
cm-11-20150427-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip - repo syncs, builds with TWRP, uses branch cm-12.1 of the kernel, uses latest available f2fs-tools
Use latest SuperSU with any of the CM ROMs - older, or different, su apps might make the radio not work.
NOTE. These ROMs are actually moto_msm8960_jbbl, so they should work on all devices for which official moto_msm8960_jbbl builds did, as long as they're still on the JB bootloader (jbbl) and you have a device-specific recovery that supports f2fs. A suitable PhilZ touch for non-xt897's can be found on the AtrixHD thread, courtesy of @palmbeach05, or you could use PhilZ-6.59.0-20150506-crkk_f2fs-moto_msm8960_jbbl-mb866 (note, despite the -mb866 suffix, it should work on any moto_msm8960_jbbl device except xt897).
The current repo is available here. To use,
repo init -u https://github.com/mionica/android.git -b cr_kk_gcc-4.8
repo sync
. build/envsetup.sh
breakfast carbon_moto_msm8960_jbbl
edit the .repo/local_manifests/roomservice.xml, changing the device project for android_device_motorola_moto_msm8960_jbbl to
Code:
<project path="android" name="mionica/android_device_motorola_moto_msm8960_jbbl" remote="mionica" revision="cr_kk_xt897" />
repo sync again
finally, (cd vendor/carbon && ./get-prebuilts).
After you do that, you're good to go - (optional) configure ccache (if it's your first build), (optional) enable ccache, choosecombo, then mka carbon 2>&1 | tee BUILD.LOG.
If you're not sure how to do any of these, either just use the provided ROM, or search on youtube for "building CyanogenMod" - that should help, I know it helped me Anyway, this thread is not the right place for learning how to build Android.

Mirrored for archival purposes.
This server WILL BE SLOW. You've been warned.
http://lionspaws.net/cm-11-20150401-UNOFFICIAL_f2fs-moto_msm8960_jbbl/
98e652a97965ba5d88cb9068fe7d4dbe *cm-11-20150401-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip

Using it for the last few days, seems good so far. Thanks

taking a break
Quick one. I'll take a break from this for now - my little sister's phone broke down, so she got my Photon. I just ordered one from the States today, but between that arriving and cornholiogsm doing the SIM mod, it might take a while (US to Ireland to Czech Republic to Ireland - and Tomas is pretty busy in my experience).

Thanks much for building this!
Forgive my ignorance, I've been using CM11 a while but other than the initial installation in which I followed wiki instructions, have only ever updated thru the phone. But since there hasn't been an update in a couple months, I'm considering installing this, particularly to solve the google service problems. If it makes the phone faster with better file system and ram stuff, that's a bonus, although concerned that might cause problems in the future. I don't fully understand what you mean by messed up build and odexed user stuff means. Basically I wonder can I just install this on top of the latest CM11 nightly without issues ("dirty flash")? My "recovery" is recovery-clockwork-6.0.4.4-xt926 clock but I only used that cuz that was what the wiki said, I've never used it since the initial install.
If the answer is yes, and I understand your post right, these are the install steps:
1. Download cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip
2. Download & install TWRP-2.8.6.0-20150408-cm11_f2fs-moto_msm8960_jbbl.img
3. Change filesystem of /cache and /data to f2fs using TWRP
4. Install cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip using TWRP
You said something about flash SuperSU alongside this. I don't recall having to do that before, can you provide a little more info?
Do I need to reinstall gapps, and if so, is it the same as I used before, gapps-kk-20140606-signed.zip?
And a couple more easy questions I could probably find by searching... how do I install that twrp....img file, can I do that thru clockwork... and how do I get into clockwork anyway, I remember it was holding some volume key during power or something but last time I tried to guess weird things happened with robots getting operations and such so if you happen to know the right keys/etc that would be convenient... will twrp replace clockwork and have the same keys to get boot to it, if not, what keys?
And last but not least... when CM11 M13 finally comes out, will I be able to upgrade to that from this, or perhaps because of the stuff you've taken from CM12 (f2fs/zram/etc) maybe I can't, or maybe I can if I set the filesystem back to default with TWRP first? How bout if one day I decide to use Lollipop (which I may never do anyway as I understand it's only recommended for phones with more than 1GB memory), will I be able to upgrade to CM12 the same way as regular CM11 user? I'd always used official stuff so this unofficial is making me nervous, but I really want my google stuff working right again and my battery to last all day like it used to...

Wait what wiki told you to use CWM for xt926!? CM's wiki?

enigma9o7 said:
Thanks much for building this!
Forgive my ignorance, I've been using CM11 a while but other than the initial installation in which I followed wiki instructions, have only ever updated thru the phone. But since there hasn't been an update in a couple months, I'm considering installing this, particularly to solve the google service problems. If it makes the phone faster with better file system and ram stuff, that's a bonus, although concerned that might cause problems in the future. I don't fully understand what you mean by messed up build and odexed user stuff means. Basically I wonder can I just install this on top of the latest CM11 nightly without issues ("dirty flash")? My "recovery" is recovery-clockwork-6.0.4.4-xt926 clock but I only used that cuz that was what the wiki said, I've never used it since the initial install.
If the answer is yes, and I understand your post right, these are the install steps:
1. Download cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip
2. Download & install TWRP-2.8.6.0-20150408-cm11_f2fs-moto_msm8960_jbbl.img
3. Change filesystem of /cache and /data to f2fs using TWRP
4. Install cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip using TWRP
You said something about flash SuperSU alongside this. I don't recall having to do that before, can you provide a little more info?
Do I need to reinstall gapps, and if so, is it the same as I used before, gapps-kk-20140606-signed.zip?
And a couple more easy questions I could probably find by searching... how do I install that twrp....img file, can I do that thru clockwork... and how do I get into clockwork anyway, I remember it was holding some volume key during power or something but last time I tried to guess weird things happened with robots getting operations and such so if you happen to know the right keys/etc that would be convenient... will twrp replace clockwork and have the same keys to get boot to it, if not, what keys?
And last but not least... when CM11 M13 finally comes out, will I be able to upgrade to that from this, or perhaps because of the stuff you've taken from CM12 (f2fs/zram/etc) maybe I can't, or maybe I can if I set the filesystem back to default with TWRP first? How bout if one day I decide to use Lollipop (which I may never do anyway as I understand it's only recommended for phones with more than 1GB memory), will I be able to upgrade to CM12 the same way as regular CM11 user? I'd always used official stuff so this unofficial is making me nervous, but I really want my google stuff working right again and my battery to last all day like it used to...
Click to expand...
Click to collapse
I agree with @arrrghhh you should use what your device maintainers recommend you use. I would also recommend you looking at what bootloader you have before trying this as there are KKBL builds in a different thread on I believe the RHD section. Odexed is like what you get from the manufacturer. It has .apk and odex files in it. odex assist the apk files. 6.0.4.4 is outdated, as 6.0.5.1 is the most recent. The install method you just recited is exactly what the OP just said. Per the OP, SU was not built into the 4/8 ROM, so you need to flash it as well. Yes you should be able to flash that Gapps, you just have to update your Gapps after finishing setup via playstore. Lollipop is able to be used on your device, as it currently has official builds. 5.0 had issues, 5.1 just got its official release yesterday. As far as unofficial builds go, I refer you to epinter and krystianp who both took an older device and provided unofficial updates that were very stable, despite the neverending work on a custom kernel. Furthermore, you can go talk to Quarx about unofficial builds, since his builds has been running the Defy for years. So being nervous about an unofficial build is like saying you're nervous about using a generic brand of something vs the more publicized item. Battery life will always be an issue if you have a bad setup (wifi and bt on all the time, max bright screen, hrs of listening to music or streaming, etc.)

@enigma9o7 Personally, I can't wait to do an unofficial cm11 build based on the cm11 m13 code base - with f2fs, and I expect, by then, zram (if it proves useful on cm11 at all - this thing works unreasonably well to begin with ). So I wouldn't worry about m13, as I'm pretty sure to release a parallel build on its side.
Now, I'm a bit impaired re. testing equipment atm but I have a mind to keep building this weekly or so anyway, while I judge the commits to be low-risk, and resume the riskier stuff once I get the new toy. Was away from Dublin this week, hence from my home PC , but that gets fixed tonight...

mionica said:
@enigma9o7 Personally, I can't wait to do an unofficial cm11 build based on the cm11 m13 code base - with f2fs, and I expect, by then, zram (if it proves useful on cm11 at all - this thing works unreasonably well to begin with ). So I wouldn't worry about m13, as I'm pretty sure to release a parallel build on its side.
Now, I'm a bit impaired re. testing equipment atm but I have a mind to keep building this weekly or so anyway, while I judge the commits to be low-risk, and resume the riskier stuff once I get the new toy. Was away from Dublin this week, hence from my home PC , but that gets fixed tonight...
Click to expand...
Click to collapse
One question i did have that i was wondering, when you built the kernel, did you set it up for GSM, CDMA, or both? I know we've talked via pm about things, but i've gotten it to boot up with your kernel, but no signal and baseband unknown
Sent from my ATRIX HD using XDA Free mobile app

palmbeach05 said:
One question i did have that i was wondering, when you built the kernel, did you set it up for GSM, CDMA, or both? I know we've talked via pm about things, but i've gotten it to boot up with your kernel, but no signal and baseband unknown
Click to expand...
Click to collapse
Mmm will have to check. For me it's working in the EU using GSM/HSPA on the xt897 with the SIM mod.
I used the stock config from the cm12.1 xt897 kernel - I'll have to diff that with the cm11 one.
Another possibility is that it wouldn't work because of SElinux mismatches between kernel and userland. The following has to be in the fstab:
Code:
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,nosuid,nodev,noatime,nodiratime,barrier=1,[b]context=u:object_r:radio_efs_file:s0[/b] wait,check
If it doesn't, on the xt897 you get no WiFi, but I expect results might vary by device
All I'm saying is, it might or might not be a kernel config, would have to check when I get to my PC.

mionica said:
I used the stock config from the cm12.1 xt897 kernel - I'll have to diff that with the cm11 one.
Click to expand...
Click to collapse
I reviewed the entire changelog from cm-11.0 to HEAD, and couldn't find anything that looked even remotely radio-related, so I reckon it's most likely the SElinux thing. And now that I built a TWRP that has a chance of running on AHD, I guess you could tell me whether that's the case

arrrghhh said:
Wait what wiki told you to use CWM for xt926!? CM's wiki?
Click to expand...
Click to collapse
Yep, pretty sure. All started a year ago when I was looking for an android smartphone with a keyboard, this one was rated best, wikipedia itself said CM was required for kitkat, so looked into CM, found their installation wiki http://wiki.cyanogenmod.org/w/Install_CM_for_xt897 which step #2 is install clockworkmod recovery. Right now if I follow the link it leads to recovery-clockwork-6.0.1.3-asanti.img, but I'm pretty sure at the time I originally installed it lead to that version I used, which did work fine for installing CM as I do have it installed. But it's possible something else lead me to that version, I can't really remember for 100% sure, but I definitely started from CMs wiki.
---------- Post added at 10:17 AM ---------- Previous post was at 10:04 AM ----------
palmbeach05 said:
I would also recommend you looking at what bootloader you have before trying this as there are KKBL builds in a different thread on I believe the RHD section
....
The install method you just recited is exactly what the OP just said. Per the OP, SU was not built into the 4/8 ROM, so you need to flash it as well.
...
Yes you should be able to flash that Gapps, you just have to update your Gapps after finishing setup via playstore.
...
So being nervous about an unofficial build is like saying you're nervous about using a generic brand of something vs the more publicized item.
Click to expand...
Click to collapse
Thanks. My understanding is there is no KKBL for Photon Q anyway, but anyways I've always used the msm...jbbl roms.
Okay, will add installing SU to install steps.
Since I already have that version of gapps, my question is do I need to reinstall it then update everything. Shouldn't it already be good? I didn't have to reinstall gapps with the official nightlies, so want to know if I really need to for this.
My concern with unofficial is not that I dont trust it or think it's less stable, just that it may make it more difficult in future to upgrade or get back onto official path as I may not be able to follow the same steps as everyone else.
I'm still unsure if it's okay to dirty flash over CM11 nightly. I do actually use my phone for work so don't want to mess it up... but really want google stuff working again and can't keep waiting forever for official cm11.

enigma9o7 said:
Yep, pretty sure. All started a year ago when I was looking for an android smartphone with a keyboard, this one was rated best, wikipedia itself said CM was required for kitkat, so looked into CM, found their installation wiki http://wiki.cyanogenmod.org/w/Install_CM_for_xt897 which step #2 is install clockworkmod recovery. Right now if I follow the link it leads to recovery-clockwork-6.0.1.3-asanti.img, but I'm pretty sure at the time I originally installed it lead to that version I used, which did work fine for installing CM as I do have it installed. But it's possible something else lead me to that version, I can't really remember for 100% sure, but I definitely started from CMs wiki.
---------- Post added at 10:17 AM ---------- Previous post was at 10:04 AM ----------
Thanks. My understanding is there is no KKBL for Photon Q anyway, but anyways I've always used the msm...jbbl roms.
Okay, will add installing SU to install steps.
Since I already have that version of gapps, my question is do I need to reinstall it then update everything. Shouldn't it already be good? I didn't have to reinstall gapps with the official nightlies, so want to know if I really need to for this.
My concern with unofficial is not that I dont trust it or think it's less stable, just that it may make it more difficult in future to upgrade or get back onto official path as I may not be able to follow the same steps as everyone else.
I'm still unsure if it's okay to dirty flash over CM11 nightly. I do actually use my phone for work so don't want to mess it up... but really want google stuff working again and can't keep waiting forever for official cm11.
Click to expand...
Click to collapse
Yes, you can dirty flash this ontop of an existing CM11 after switching /data and /cache from ext4 to f2fs. Gapps will be fine since they install on the /system partition.
Sent from my ATRIX HD using XDA Free mobile app

Switched to Carbon, but preserved most of the goodies from CM; links in the first post.
Also added a note on how to hack your radio to disable CDMA/LTE - so you could go with this phone in the US and never register on Sprint's network (unless they have a GSM/WCDMA network in place too, which should be fine).

I decided to give it a try with your latest CM11. I installed the TWRP from your first post, was able to backup fine, but don't see how to reformat as f2fs....

enigma9o7 said:
I decided to give it a try with your latest CM11. I installed the TWRP from your first post, was able to backup fine, but don't see how to reformat as f2fs....
Click to expand...
Click to collapse
There should be an option to wipe things, go there
Sent from my ATRIX HD using XDA Free mobile app

palmbeach05 said:
There should be an option to wipe things, go there
Click to expand...
Click to collapse
Thanks, found it.
And now I'm stuck. But I bet it's an easy solution.
I changed filesystems, restored data & cache, installed cm (04/27), installed superuser (wasnt sure if needed, but figured it couldnt hurt), and I booted.
No wifi or phone service but I'm hoping the last step will fix that, restoring sdcard0. However, I can't figure out how to copy that back. I used ES File Explorer to copy it to a folder in sdcard1 before I started. But now I can't paste it back to /storage, always told copy fails. There is a 0 byte file called sdcard0 there, if I delete it, it comes back. Since it's not a directory I can't change to it and copy the contents of my previous save into it... I tried deleting it and making a folder called sdcard0 before it recreated the 0 byte file but that failed too.
I thought maybe I'd try command line, but I'm no expert there... I su'd and tried similar things as in EX but similar results.
I thought I'd try to copy it back with TWRPs file manager, but I couldn't figure out where to put it, there was no /storage directory, so I tried putting it in / and that started copying for a while but before it was done it rebooted and just hung at the TeamWin screen until I powered off...
So yeah. Dunno how to restore sdcard0. Help please....
edit: maybe superuser doesn't work? I tried to use default "file manager" and it wont let me switch to root mode. Then I noticed that while trying ES File Manager again I didnt see the popup about "root granted" or something like that that I normally see. But superuser is installed, its in the apps menu and runs and a quick look thru the settings seems okay to me, but I don't recall ever setting anything before.
edit2: I'm giving up and going to try to go back to last cm11 nightly and hope my phone starts working again. I tried reflashing multiple times, eventually tried supersu instead of superuser and that worked to get root explorer working, but I still couldn't copy over sdcard0 using ES anyway, but using default filemanager I could start (although I hate that filemanager cuz I dont know how to change directories, usually have to tap about 15 times before it opens a folder), but it would always start then reboot before it finished. So I still dunno how to copy that back.

enigma9o7 said:
No wifi or phone service but I'm hoping the last step will fix that, restoring sdcard0. However, I can't figure out how to copy that back. I used ES File Explorer to copy it to a folder in sdcard1 before I started. But now I can't paste it back to /storage, always told copy fails. There is a 0 byte file called sdcard0 there, if I delete it, it comes back. Since it's not a directory I can't change to it and copy the contents of my previous save into it... I tried deleting it and making a folder called sdcard0 before it recreated the 0 byte file but that failed too.
Click to expand...
Click to collapse
Superuser is probably not a smart choice on KK. Use SuperSU instead.
The very first boot is somehow handled differently - I discovered this when I worked on integrating SuperSU into a catch-all zip of mine (alongside Windows Mobile ringtones, Midnight Commander, patched hosts, and a few other goodies). I got no radio with my package, but if I flased SuperSU instead, it worked.
It took me a coupe of tries to find the culprit - a flag file in /etc that SuperSU created after the first boot (and I attempted to create that from my zip). Made my zip not create that, and bang! everything worked just fine. Btw, removing that file after the first boot had no effect, the phone'd be screwed until you wiped /data.
Now, the fact that SuperSU handles the first boot differently kinda makes me think that older su's might very well not work (properly) on KK - and what you're reporting seems to confirm that.
I would strongly suggest going Carbon instead; that includes a working su. It's essentially CM with a different boot logo and a good few extra customization options (which you can safely ignore if you're not into that sort of thing).
So if you didn't go back yet, try either
flashing carbon and being done with it, everything will work;
flash the cm rom alongside supersu, not any other root app,
Either way, root will work, phone will work, and you'll be able to copy stuff around to your heart's desire.
As for a FM, I strongly suggest an app called Total Commander. The UI is atrocious as of late (the author is obviously better at coding than designing icons ), but it' probably the most complete FM solution for Android, bar none. And it's free, without adds; wait til you try it in landscape
I'm sorry for you inconvenience, but I also somehow feel it's earned - the OP said SuperSU back before Carbon replaced CM; because that's what I was using, and it worked for me - no guarantees if you went your own way. I've re-added the limitation and made it bold+orange in the CM part of the post (Carbon has its own, fully working, su).

Added the 2015.05.03 build of Carbon; links to 2015.04.30 removed.
At this stage, CM users should have everything they liked about CM, already compiled in (except for WhisperPush, the point of which I don't quite see).
Changelog from 2015.04.30:
added Calendar (!!!) - why on earth would the Carbon guys build an ROM without this?!
built on gcc-4.8.x-sabermod-20150429
added CMWallpapers, Video Editor
added the previously-missed vim, unrar, zip and gdbserver
synced with upstream; in particular, there was a noteworthy GPU memory allocation improvement in the kernel
Todo:
add an app for messing with the NV settings (enable/disable bands, enable/disable US GSM lockdown)
enable zram.

Added the 2015.05.05 build of Carbon; links to 2015.05.03/04 removed.
Changelog from 2015.05.04:
set default governor to msm-dcvs - better out-of-box performance
imported the cm-12.1 init support (including swap enabling)
Changelog from 2015.05.03:
support for fstab alternatives, cm12-style (my own code in fs_mgr); now you can use the ROM with either f2fs or ext4 for /cache and /data
massively improved FS performance for both ext4 and f2fs - tuned the fstab settings for best performance;
added radio-tool to enable/disable US GSM lock and groups of radio bands (CDMAs, US GSM/HSPA, EU GSM/HSPA, Sprint LTE, Verizon LTE) - see spoiler in first post
Todo:
figure out why swapping doesn't want to start, despite the device being there and mkswap succeeding (error -16).
Updating the recovery to a 20150505 build is highly recommended.

[PORT] LG QuickRemote for AOSP MM G2 G3 All Variants

Hello, i bring to you the QuickRemote app for your AOSP Marshmallow rom, CM13 or any rom based on CM13 (Resurrection Remix, Bliss, AICP), you may ask, "Why would i want QuickRemote on my AOSP rom if MM has native IR support and Peel or Anymote works without all this mambo jambo?
Well, even though what i just said is true, no remote controller app has the learning method enabled, even on a stock rom, only QuickRemote can enable the IR receiver to learn a controller that does not appear on the device/manufacturers list.
So, that's the reason we want QuickRemote to work on our AOSP rom.
So, before anything, i would like to thank @hikarisei23 because in a comment of his post HERE i found the files for QuickRemote to work on MM wich leads to the second person i want to thank wich is @syndre who on said comment, posted the files that worked on MM, also @KronicSkillz who helped a lot to troubleshoot and also confirmed that the method i'm posting here works.
Well, this is it, after personally testing with: Resurrection Remix, AICP and Bliss, all of them MM amd CM13 based, all of them with the stock kernel and Lambda Kernel i'm confident enough to post it here, days of testing and troubleshooting and 3 different roms later.
So first, the mandatory disclaimer, im not responsible for any problem that may result from using my method and the files i'm providing you, either with your phone or your self-esteem, it's your responsibility to read, re-read and only do what you are comfortable with.
What you will need:​
1. - The phone, this only has been tested with Lg G2 and Lg G3, this may or may not work on another LG phone with IR, you can try, but at your own risk.
2. - The Rom, this only have been tested with AOSP roms either CM13 or CM13 based roms, again, you can try in another rom but at your own risk.
3. - Obviously a Custom Recovery (twrp, cwm, philz)
4. - The three zips im leaving at the end of the post, QRemote_AOSP_MM.zip Fix_Part1.zip and Fix_Part2.zip.
5. - Maybe necessary or not, depending on your rom, Universal init.d from Playstore HERE and Selinux Mode Changer from HERE.
6. - Root Access.
Ok, once you checked and have everything needed, we have to make a little prep on your Rom before starting to flash the zips.
Rom Preparation 100% Needed
You need to set Selinux to permissive, here is where you may or may not need Selinux Mode Changer, First go into "About Device" on your phone settings and in the bottom you will find an indicator for Selinux state, if its "Permissive" you are good to go, some Roms and Kernels have this set to Permissive by default, if it's Enforcing, search in your Rom or Kernel settings, some of them have an option to set it to Permissive, if your rom does not have any option to change it, you will need Selinux Mode Changer, you install it and set Selinux to permissive, after reboot you can check in About Device again to see if it succeded, if it does not work, try again and check the original post, most of the answers are there, i cant give support for this app, also, this app needs root rights, and preferably two reboots after setting Selinux to Permissive.
Next you need to have init.d support, again, some roms have it, but at least for the test that me and the other users did, even though you are pretty sure init.d is enabled it's better to just install Universal init.d from the Play Store and enable init.d manually after doing so, reboot the system at least two times and grant Root access.
Installation!
Now we are ready to start flashing, reboot into recovery and RECOMMENDED, do a Nandroid Backup just in case, but at the moment no boot loops or any other problems had raised from flashing this, but again, just in case. After that, flash the first file: QRemote_AOSP_MM.zip, reboot your system and let it settle for a bit, 1 minute at least.
Now is the part where almost everyone has problems, you have to check in your Sdcard root for a log file named Qremote.log, if the file is there, it means init.d is enabled and in the file it will say if Selinux is Ok, if you don't have the file, check back the first two prep steps and try again.
Now if everything is going ok, is time for the second file, Fix_Part1.zip, reboot and let the system settle again, you may have some force close errors from QuickRemote or QuicksetSDK, its ok, you can try and check if QuickRemote is working, in allmost every case it will not work just yet, but you may have some luck.
Now, is the time to flash the third file, Fix_Part2.zip, again, reboot and let the system settle, now, you should have a working QuickRemote app on you AOSP MM Rom.
This are the steps, if you need more information about what all of this is doing and why you need Selinux and init.d, also why you need to flash 3 files, you can read the troubleshooting section where i explain what i understand about it.
TROUBLESHOOTING
Well, if you are here, it means that this didn't work as planned, so lets make this like a FAQ so you just search your problem and get the answer for it.
P.- I can't see QuickRemote on my app drawer. A: be sure that QuickRemote.apk is not showing as "com.lge...." and has the default green Android icon on your app drawer, sometimes and for reasons unknown to me, this happens for the first day or so, it will automatically change to QuickRemote and it will have the correct icon at least 5 hours after you installed it, it can take more time. A2: Maybe the flashing proccess was not successful, re-flash the file, it will automatically delete previously flashed files and install a new copy of them.
P. - I get force close messages for QuickRemote or QuicksetSDK after completing the proccess. A: try to run QuickRemote after the system settled, most of the times is 1 minute, in some roms and for reasons unknown to me, this messages will appear at boot but after the system settled, you will be able to run QuickRemote without any problem.
P. - QuickRemote opens up but no manufacturers are showing and it also gets really slow. A: this problem shows when either QuicksetSDK is not correctly installed or Selinux is not set to permissive, the solution for the first problem is in my 2 part fix, the version of Selinux included in the first zip, works great with MM but for some reason it will not work out of the box, i dont know if it's missing some files but it may or may not even show under system apps list on your settings menu, what my 2 part fix does is that, deletes the version of QuicksetSDK that the first flash installs and installs a temporary copy of QuicksetSDK wich i believe, writes information needed for QuicksetSDK to work properly, but this newer temporary QuicksetSDK apk, will allmost never work on MM, you can try but allmost every time it will not work, it will constantly force close, so the second fix zip, will delete this temporary QuicksetSDK and the folder it creates in your Sdcard root and install the previous version of QuicksetSDK again, and now, if everything went well, it will work as it's supposed to, i really dont know why exactly, but it works.
A2: the first thing you will notice when you switch to MM is that allmost every app will ask for permission to your Sdcard or camera or microphone wich in LP was not doing, since 4.3 Google is taking extra steps to ensure that you and your information are better protected one of this steps is Selinux (Security Enhanced Linux) wich, for putting it in simple terms, is like a sandbox for your system, only some trust-signed apps can get out of that sandbox and copy files etc... Into your system, those not-so privileged apps cant output anything outside the sanbox and thats why you need to disable or "set to permissive" Selinux, so QuicksetSDK can make the changes necessary for QuickRemote to do its work, it's true that now your system is in a degree "more vulnerable" but if you are a user of this forum, the odds to install something that will damage your system or jeopardize your information are minimal, you need to be really silly to fall for those "your system has problems" or "your battery is gonna explode if you don't install this app" ads that appear on your phone on the daily basis, so, dont worry, but at the same time, just be carefull and have some common sense, if there is a way for this to work with Selinux set to Enforcing, i will update it in the same second.
P. - QuickRemote force closes whenever i try to open it. A: this is caused by either a bad zip flash, or problems with Selinux or init.d, follow the previous answer and the first installation steps again.
P. - I can see QuickRemote and QuicksetSDK on my apps list, no force closes but still no manufacturers. A: Be sure init.d is enabled, i had problems with Roms that had "native init.d support" and emulated init.d will not work, the only way i got no problems with this was with Universal init.d, install that even though you are "pretty sure" your rom supports init.d, the 10QuickRemote.sh script on your init.d tries to get your country to see if you will use the app in, either Korean or any other supported language, it will also give some permissions to a file and it will check if Selinux is Permissive and finally, it will log this to a file called Qremote.log on the root of your Sd, if you have problems and you cant see the file, the problem is 99% most of the time, init.d.
P.- I don't want to flash three files, isn't there a simpler way? A: Unfortunately no, at this moment and after A LOT of testing etc... This is the only effective way i found.
P. - I'm afraid to set Selinux to permissive and leave the door open for all kind of bad ju ju and stuff to invade my sacred Android system, what can i do? A: Skip this hole thing, at the moment, the only way to make this work on AOSP MM is by doing the previous, just be careful, get some common sense and everything will be just fine.
Well, thats all i can think of right now, if you have suggestions, problems or a better way to make this work, please tell me in the comments or PM me, i'm glad to help as far as i can, i hope this helps, i leave you with the needed files and proof that it works.
QRemote_AOSP_MM.zip - MEGA - DRIVE

Great job
Works great on Ressurection Remix 5.6.2. Well done.
Only issues I have are the force close when trying to edit the remote name, and icon and name of the app not showing correctly (which can be fixed with any custon launcher).

Petrit Ziu said:
Works great on Ressurection Remix 5.6.2. Well done.
Only issues I have are the force close when trying to edit the remote name, and icon and name of the app not showing correctly (which can be fixed with any custon launcher).
Click to expand...
Click to collapse
I have not seen those force closes, i have to check, and as i said, the icon and name will eventually get right, for me was 5 hours, but it can be a hole day, and all by itself will set the icon and name correctly, if you have more problems, send me a logcat for this app, maybe we can find why it force closes

Logcat
Logcat

Added to index
[INDEX][LG G2] ROMs, Kernels, Guides and more

@Petrit Ziu after seeing the logcat i think the problem is StrictMode Policy, wich is a policy in android to keep unintentional writes to the system away from the main thread, so the animations, ui etc... Can keep a steady flow and your system runs smooth, because this app was never intended for AOSP and the app comes from Lollipop, i think that the right signatures are missing and Android sees the action of changing the name to a controller "invalid" so it closes the QuickRemote App, lets wait for newer versions of QuickRemote after Lg releases MM to more IR enabled devices to see what app works best, this is the best we can do with the resources we have

@Art Vanderlay Thanks

@Jc_master I think it's already perfect, just pointed an issue i found, but it's totally not a problem for me. Thanks
Sent from my LG-VS980 using XDA Free mobile app

@Petrit Ziu thanks, and dont worry, i'm no developer but i'm learning so much from this, it's good for me to see this problems and know why they happen, it's good to have feedback and even better this errors, if you didn't tell me, i would not know, my system does the same and i had no idea, i will update the post with this information

not work for me
I flashed it a lot of time and patched it and it will be not even work for me :/
I always get FC
D802 CM13 Nightlies

Potter92 said:
I flashed it a lot of time and patched it and it will be not even work for me :/
I always get FC
D802 CM13 Nightlies
Click to expand...
Click to collapse
Well, the only thing i can reccomend is that you use the latest TWRP for your device, you have to follow the steps exactly as i explained and use exactly the apps and files i explain, if that does not work i can just reccomend using another rom, Resurrection Remix for example, your logcat seems to show a problem with the apk itself, you cam try and decompress the files and manually copy and assign permissions to the files but i can't show you how, i lack time to do it

Works great, thank you!
Only issue I've had is the app crashes every time I try to rename a remote.

It works on the D801 (T-Mobile) Bliss rom 6.0.1
just confirming it.
Although I do get some force quit when editing the remotes name etc...

LG D802 CM13 nightlies - works!

Jc_master said:
@Petrit Ziu after seeing the logcat i think the problem is StrictMode Policy, wich is a policy in android to keep unintentional writes to the system away from the main thread, so the animations, ui etc... Can keep a steady flow and your system runs smooth, because this app was never intended for AOSP and the app comes from Lollipop, i think that the right signatures are missing and Android sees the action of changing the name to a controller "invalid" so it closes the QuickRemote App, lets wait for newer versions of QuickRemote after Lg releases MM to more IR enabled devices to see what app works best, this is the best we can do with the resources we have
Click to expand...
Click to collapse
Is there a fix?
MM is out for G3
Thanks

U can change name using SQLite Editor like this:
https://play.google.com/store/apps/details?id=dk.andsen.asqlitemanager
Database: /data/data/com.lge.qremote/databases/qremotesettings.db
Table: tblDevices

Petrit Ziu said:
Works great on Ressurection Remix 5.6.2. Well done.
Only issues I have are the force close when trying to edit the remote name, and icon and name of the app not showing correctly (which can be fixed with any custon launcher).
Click to expand...
Click to collapse
I can confirm this force close on rename issue as well
Eselter said:
U can change name using SQLite Editor like this:
https://play.google.com/store/apps/details?id=dk.andsen.asqlitemanager
Database: /data/data/com.lge.qremote/databases/qremotesettings.db
Table: tblDevices
Click to expand...
Click to collapse
That did it! Not necessarily a solution to the problem but a sufficient workaround for now

On CM13 working great but on exodus I can't manage it to work.
Any one have try it on exodus rom?

Eselter said:
On CM13 working great but on exodus I can't manage it to work.
Any one have try it on exodus rom?
Click to expand...
Click to collapse
Same here. Works on every rom I've tried but exodus. Something funky is happening with the quickset SDK as its present in priv-app or app (forget which one) but doesn't show up in installed apps. I have selinux set to permissive and init.d enabled.

Hello, how to uninstall this qremote? Because I have tried peel smart remote, and it's works great. And the remote (peel) so detail from LG qremote.

ViPER4Android Universal Fix CM13 Android 6.0/+

So... here I will share 2 scripts I made to fix permissions for ViPER4Android running with enforced SELinux.
Why 2 scripts?
I like to keep everything open-source. Here I like to notice, Cyanogenmod is taking the wrong direction in my point of view. Every update takes out something of the customization possibilities of the user, so I am thinking of choosing new ROM. I faced real nightmare with SELinux permissions (well... SELinux is good, but Cyanogenmod doesn't provide any tool or way to manage those permissions). The more funny part is that with branch 13.0 of cyanogenmod there is no more init.d. Before someone corrects me - yeah... there is init.d, but SELinux blocks any script from executing at boot time, so don't use it. You will get your logs spammed by error messages. So... I've tried to enable init.d again, but there is no way to manage init.d to work as before. I've tried lots of different fixes from other posts, but nothing seems to work anymore, because of SELinux restrictions. I didn't managed to find any way to run scripts on boot time with root permissions in a suitable way... without messing with other system files or rebuilding build.img... so I came with those 2 solutions:
ViPER4Android (OpenSource) This is the solution I recommend to all of you. It is full open source. It doens't mess with you current system and it should work on any device/ROM. The zip file contains ViPER4Android app and driver, sepolicy-inject tool from setools-android so we can set permissions for ViPER4Android to work with enforced SELinux and Universal Init.d.
sepolicy-inject is open source equivalent to supolicy tool of Chainfire's SuperSU. I strongly recommend sepolicy-inject over supolicy, because every root closed source app should be threaten as security risk as the code can't be examined. I don't trust it esepcially when it is part of your android root manager
Universal init.d is just a application - it simulates init.d function. Imagine it like init.d on the user side... sadly enough you need to be pre-rooted to get it running.
ViPER4Android (Legacy) Maybe more of you will like this solution as it is more automated and it doesn't require any user action after installing the zip. This zip will do the same as the one above - it will install ViPER4Android removing all other DSP apps, but here come the difference - THIS SCRIPT WILL INSTALL CHAINFIRE'S SUPERSU in order to set SELinux policies for ViIPER4Android. Chainfire's SuperSU uses supolicy-tool - it let you manage SELinux policies on boot time. Chainfire's SuperSU will run everything in /system/su.d/ so again... you have init.d support - this is the real pain in the ass.
Before you download and flash, please read:
Both scripts WILL REMOVE other DSP apps from your device and will install ViPER4Android 2.4.0.1. I STRONGLY RECOMMEND TO USE SOLUTION 1 AS IT IS FULL OPEN SOURCE! Support open source software!!!
INSTRUCTIONS
ViPER4Android (OpenSource) - IN ORDER TO WORK, YOUR DEVICE MUST BE ROOTED! (Your device need to be rooted as Unversal Init.d needs root permissions in order to simulate init.d functionality)Download the .zip; Flash and reboot; Open Universal Init.d and grant root permission if asked; Reboot once more in case it don't work!
Sometimes Universal init.d is not fully initialized and needs some root permissions. That's why you need to reboot second time - then everything works. No further actions needed.
ViPER4Android (Legacy) - Just flash and reboot... but once more - SUPPORT OPEN SOURCE AND CHOOSE SOLUTION 1!!!!
For Samsung devices - if the scripts above doesn't work for you, check this post. Thx to Viper4713 for the instructions and voshchronos for solving the issue!!!
Hope to make someone happy
PS: If u want to make me happy with some beer, here you can donate a small amount. Thank you for your support.

Can i flash it on android one device running on 6.0.1

Yes. If you have any issues, please let me know!

rpangelov said:
Yes. If you have any issues, please let me know!
Click to expand...
Click to collapse
Hi, i tried to install the open source version on my kltedv running resurrection remix 6.0.1 however it is still not working. The init.d shows the kernel doesnt support init.d, and v4a drivers status is abnormal. It is also cause screen freeze and random restart. Any ideas? Your kind input would be very much appreciated. Thanks.

hiropandaz said:
Hi, i tried to install the open source version on my kltedv running resurrection remix 6.0.1 however it is still not working. The init.d shows the kernel doesnt support init.d, and v4a drivers status is abnormal. It is also cause screen freeze and random restart. Any ideas? Your kind input would be very much appreciated. Thanks.
Click to expand...
Click to collapse
I've just readed some info about the ROM you use. As it is based on Cyanogenmod I assume there is root manager builded in. Maybe it is disabled as CM root access is disabled by defaults? Look at: Settings -> Developer Options -> Root Access - turn in on by "Apps only".
Then just follow this steps:
1. Start Universal Init.d
2. Turn it off from the toggle button
3. Run test from the button on the bottom of Universal Init.d
4. If ask for root permissions, grant them!
5. Turn Universal Init.d ON from the toggle (step 2 you turned it off)
6. Restart your device and check once more!
If you still have any issues, please let me know!
Greetz,
Angelov

---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
rpangelov said:
I've just readed some info about the ROM you use. As it is based on Cyanogenmod I assume there is root manager builded in. Maybe it is disabled as CM root access is disabled by defaults? Look at: Settings -> Developer Options -> Root Access - turn in on by "Apps only".
Then just follow this steps:
1. Start Universal Init.d
2. Turn it off from the toggle button
3. Run test from the button on the bottom of Universal Init.d
4. If ask for root permissions, grant them!
5. Turn Universal Init.d ON from the toggle (step 2 you turned it off)
6. Restart your device and check once more!
If you still have any issues, please let me know!
Greetz,
Angelov
Click to expand...
Click to collapse
Hi Angelov, many thanks for your helpful instruction. I couldnt get it work with open source version. However it is working now after i install V4A legacy version. Many Thanks once again.

hiropandaz said:
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Hi Angelov, many thanks for your helpful instruction. I couldnt get it work with open source version. However it is working now after i install V4A legacy version. Many Thanks once again.
Click to expand...
Click to collapse
You are welcome! As I mentioned in the instructions - the legacy script will work always, but I don't like the implementation of it. I am working on new version of the opensource script, so there won't be any issues of that kind. When I am ready I will upload it here after updating my first post.
Greetz,
Angelov

This "universal" fix has been shared several months ago on XDA and a simple root shell is enough to use V4A in enforcing mode.
FYI init.d is deprecated now but it's not related to CM. Use su.d instead.

Primokorn said:
This "universal" fix has been shared several months ago on XDA and a simple root shell is enough to use V4A in enforcing mode.
FYI init.d is deprecated now but it's not related to CM. Use su.d instead.
Click to expand...
Click to collapse
Can you provide me a link to this universal fix you are talking about?
PS: init.d is deprecated in AOSP, i get that. Please read my first post once more, obviously isn't clear enough. Using su.d will result in using closed source tools to manage your Selinux policy's. As I mentioned it above - please support open source software. Every closed source root app has to be threaten as security risk. My opinion...

rpangelov said:
Can you provide me a link to this universal fix you are talking about?
PS: init.d is deprecated in AOSP, i get that. Please read my first post once more, obviously isn't clear enough. Using su.d will result in using closed source tools to manage your Selinux policy's. As I mentioned it above - please support open source software. Every closed source root app has to be threaten as security risk. My opinion...
Click to expand...
Click to collapse
Check the official V4A thread for instance. Others have opened threads in device specific forums or in the App & Games forum.
Have a look at this thread, it might interest you: http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
FYI I do support open-source free/libre softwares, as much as I can.

Primokorn said:
Check the official V4A thread for instance. Others have opened threads in device specific forums or in the App & Games forum.
Have a look at this thread, it might interest you: http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
FYI I do support open-source free/libre softwares, as much as I can.
Click to expand...
Click to collapse
I've seen phh's SuperUser but I didn't tried it - this is one of my tasks for this/next week.
As I've tried the most scripts, I didn't liked all the actions needed to be taken before running the .zip script in order to get viper working. I compile my own Cyanogenmod and I don't use gapps. Almost all apps I use on my device are opensource as I use F-droid as my only market (well... I need whatsapp, but I download it just from the website). Anyway... Cyanogenmod has it's own root manager builded in.... so why I need to install one more, which contains closed source tools in it? That is also the reason I don't advice people to use it... and I don't see that as solution to my problem. AOSP is opensource, but nowadays it is very dependent on some closed-source elements and I want to wipe them all out and use open source alternatives for. I hope you understand why using su.d isn't solution in this case. You just make your self and others dependent on one more closed source app, so I don't get where is the support for open source? I think that opensource script is good solution to the problem without using any closed source tool.
To make it easy as possible - just flash the .zip and you are ready to go, I included the latest version of Chainfire's SuperSu in the legacy script, so you don't need to install it before running the .zip. It looks easier to me....
Actually it is very stupid because the result of using the scripts (doesn't matter which one) you will end up with rooted device anyway (if it isnt already), but in order to get opensource script working your device has to be rooted before running the .zip, but if your device is already rooted, you just flash the zip and you are ready to go.

rpangelov said:
I've seen phh's SuperUser but I didn't tried it - this is one of my tasks for this/next week.
As I've tried the most scripts, I didn't liked all the actions needed to be taken before running the .zip script in order to get viper working. I compile my own Cyanogenmod and I don't use gapps. Almost all apps I use on my device are opensource as I use F-droid as my only market (well... I need whatsapp, but I download it just from the website). Anyway... Cyanogenmod has it's own root manager builded in.... so why I need to install one more, which contains closed source tools in it? That is also the reason I don't advice people to use it... and I don't see that as solution to my problem. AOSP is opensource, but nowadays it is very dependent on some closed-source elements and I want to wipe them all out and use open source alternatives for. I hope you understand why using su.d isn't solution in this case. You just make your self and others dependent on one more closed source app, so I don't get where is the support for open source? I think that opensource script is good solution to the problem without using any closed source tool.
To make it easy as possible - just flash the .zip and you are ready to go, I included the latest version of Chainfire's SuperSu in the legacy script, so you don't need to install it before running the .zip. It looks easier to me....
Actually it is very stupid because the result of using the scripts (doesn't matter which one) you will end up with rooted device anyway (if it isnt already), but in order to get opensource script working your device has to be rooted before running the .zip, but if your device is already rooted, you just flash the zip and you are ready to go.
Click to expand...
Click to collapse
I mentioned su.d because that's a solution with newer Android versions but I didn't say it's the best one. Using FLOSS softwares is a good move but you are using proprietary codes with CM.

Hi everyone, i flashed both of the zips with TWRP but i got an error code : 255. Any idea how to fix it ? Please help me. I'm using an x86 phone btw

trongtin64 said:
Hi everyone, i flashed both of the zips with TWRP but i got an error code : 255. Any idea how to fix it ? Please help me. I'm using an x86 phone btw
Click to expand...
Click to collapse
I think it's because your phone architecture... anyway - I will look at it today and I will let you know if I find a solution for your problem. Can you tell me which phone exactly you own ? Thank you.
Greetz, Angelov

rpangelov said:
I think it's because your phone architecture... anyway - I will look at it today and I will let you know if I find a solution for your problem. Can you tell me which phone exactly you own ? Thank you.
Greetz, Angelov
Click to expand...
Click to collapse
i'm using a zenfone 5 (A501CG) with resurrection remix mm 5.6.7

trongtin64 said:
i'm using a zenfone 5 (A501CG) with resurrection remix mm 5.6.7
Click to expand...
Click to collapse
You have a x86 architecture and this zip is probably for arm only. I guess you need the updater-binary for x86 and place it into the zip in META-INF/com/google/android.

Primokorn said:
You have a x86 architecture and this zip is probably for arm only. I guess you need the updater-binary for x86 and place it into the zip in META-INF/com/google/android.
Click to expand...
Click to collapse
Ok so i need an updater-binary for x86 right? Can i copy it from other zip to your zip? Will it work?

trongtin64 said:
Ok so i need an updater-binary for x86 right? Can i copy it from other zip to your zip? Will it work?
Click to expand...
Click to collapse
AFAIK you can use the one from a custom rom. You need a compatible custom recovery of course.

Primokorn said:
AFAIK you can use the one from a custom rom. You need a compatible custom recovery of course.
Click to expand...
Click to collapse
I'll use the one from my custom rom . Thank you for helping me :good:

It works great. thanks.
my bad for not following the instructions.

[Guide] Enable VoWiFi on custom ROMs

First attempt at making a guide for this, so please feel free to make suggestions on how to clean it up (I feel like it doesn't lend itself well to step-by-step but you're welcome to try).
Great news everyone! (well, all three of us with T-Mobile/MetroPCS in the USA...)
I got VoWiFi to work last night on a couple custom ROMs and successfully made wifi calls. It doesn't require many pieces, but it can be complicated (not just a step-by-step) to get the required pieces into the right places.
- You need a copy of /system/priv-app/CNEService/CNEService.apk from a stock OOS install (I did it with the one from 9.0.3).
To get that, you might be looking at booting into TWRP with the other slot active or temporarily using something like @mauronofrio's fastboot install ROM from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 and just flashing the system image to one slot to grab the file before restoring back to the one you had. Anyway, use caution, be sure of which slot you're on and what you're flashing to, and copy the apk from /system/system/priv-app (the path when you're booted from TWRP instead of inside the active system slot). You'll probably have to use ADB commands to push/pull the file directly to/from a computer if you already have a custom rom installed on one slot with screen lock set up, since /data will likely be encrypted and unavailable when you're booted up in TWRP with the other stock slot active.
- You need to be able to install a rando apk as a privileged system app to get this apk back into /system/priv-app/ correctly on your custom ROM.
There are ways to do this manually that involve lots of permissions and editing XML files for privileged app permissions in a couple places, but realistically you're using a custom ROM so you probably have Magisk (otherwise what the hell are you doing with custom ROMs?) so you should just use https://forum.xda-developers.com/apps/magisk/module-terminal-app-systemizer-ui-t3585851 and pick option 3 to install it. You'll need Magisk, a terminal emulator, and some ability to type a file path to use this module.
- You'll need to make sure that your /system/build.prop file contains the line "persist.vendor.cne.feature=1" (AEX doesn't at first, XenonHD does, not sure about others).
We've got the requisite stuff in /vendor already, this just enables the ability to use it. You'll need to have root access and a file manager/text editor (Amaze is FOSS and available through F-Droid, MixPlorer through XDA Labs is also nice, or use TWRP and a text editor that knows unix line endings on your computer to copy things back & forth via MTP and remember to set permissions after, I think it's chmod 644).
Reboot, unlock, and try to make a test call. Successfully got it to work on AEX & XenonHD last night, I suspect it works for Omni and others as well.
Try some more ROMs out and report back below if it works for you too!

Now if only you could fix the Android Auto bug.
I'm totally kidding. This is awesome. Thank you!

Tested Omni and it works too; just needed the APK added/systemized, already has the correct entry in build.prop.

hello
my op 6 running oxygen ob 10. vo lte work. but when I connect to wifi. vowifi not work ? how to fix it ??

Any chance someone could upload and share the CNEService.apk? Would make life a lot easier...

brmbjn said:
hello
my op 6 running oxygen ob 10. vo lte work. but when I connect to wifi. vowifi not work ? how to fix it ??
Click to expand...
Click to collapse
If it's not working in OOS, I don't know what to tell you. Might just be that the connection isn't reliable enough for it to decide to enable... but I never used OB10; I switched back to stable 9.0.3 after OB9.

Great work!

[debloat-ROM] Back Bacon UI one ui for Canada, eh? SM-A530W October Release

October release is available with or without root
Made a few changes as far as adding in some apk's to hopefully make it stable for everyone.
Besides that, the usual with normal default font BUT lots more choices in the font section.
Enjoy!
*if anyone has solid reasons to remove any apk files i've put back please let me know as some I should not have been removing and others... not so sure
I will no longer be able to provide new copies of this after the October security patch. I no longer own an A8 2018 and without a device to test the work, I do not feel it is appropriate to continue the project. I'd like to thank everyone that participated and I hope you enjoyed using it! If anything changes in the future that will allow me to provide the latest edited firmware, I will definitely be providing it here for you. I am using an S7 now so if you own one and like this work, there shall be downloads available there similar to this one. (Already testing).
Anyone that would like to continue on their own or have access to files used in making it I will try to include as much as possible from the link provided below by the end of October. There is currently a slightly outdated set of files and instructions (from June I believe) on how I made it already available.
Thanks Again!
Oct Security patch zip ready for download
Available with or without root AND with or without exo font - also an attempt to allow printing feature version. "Attempt" meaning I've placed a set of apk files into a separate and clearly labelled zip on the main download page that may allow proper use of the feature which has not been validated as operational by me or any other user. The "print fix" zip is rooted with exo font
This was made ONLY for the SM-A530W! Please do not use if not W (Canadian) variant. Check your phone info before attempting to flash
All ROMS/extras here:
https://drive.google.com/drive/folders/12Vwzn1CxNdT-ISsrOnSL4D353Nr14iRb?usp=sharing
The ROM will function very well and does not require any special patches, kernels, etc except obviously TWRP
Any additional issues you face with added mods most likely will need to be addressed with the creator
*Built by Superr's Kitchen*
Over 100 apps removed
***Find my mobile and pop-up asking to store lockscreen info removed- BE AWARE reduced ability to locate lost device!***
retro shutdown qmg
Overloaded notifications and ringtones
Oreo Weather (pie weather is a serious downgrade)
August Security release
FM tuner and App Lock (Next Radio may now be used starting from July 2019). Gee, THANKS SAMMY! What took you so long? Was it the polar bears?
Goofy selfie stickers that are funny... and creepy *big thanks to hadesRom genius Corsicanu for the find*
Other typical CSC changes
If your plan has wifi calling, turn it on/off once in phone settings to "break in" the qs tile
Dedicated Screen Recorder access in launcher with no shortcut style appearance (if deleted may be re-enabled with activity launcher as shortcut)
Chrome can be safely disabled at any time if desired and auto replaced with system webview
dm-verity + force encrypt already removed
Magisk rooted
Installation is easy as pie
BACK UP FIRST!
Wipe caches, data, system. Internal may be safely wiped and give the "freshest" install but is optional. Then flash away.
Once flash completes, just reboot.
-*Usage*-
You are free to use any ideas/changes included in the zip. In fact, I encourage you to do so. I've mostly pieced together work from other very difficult projects to create this. Nobody has asked me to add, remove or alter anything contained within this page or in shared downloads. Their work is everywhere and it's what made this possible.
Built with Superr's Kitchen
Some screens to sample below. yay

nobody home

empty

I followed your instructions. I was already updated to pie previous to flashing your rom. I am not able to get root. Any ideas why. I also have the Canadian version. Good job on the Rom, I like it. I wish I could get root.

Ok. I can't really suggest anything other than the obvious.
But you've let it boot once before trying, and are adding the apk as well after flashing magisk in twrp?
Hard to figure that one out. If you're using Magisk, i am assuming.

burnt_31 said:
I followed your instructions. I was already updated to pie previous to flashing your rom. I am not able to get root. Any ideas why. I also have the Canadian version. Good job on the Rom, I like it. I wish I could get root.
Click to expand...
Click to collapse
Have you tried 19.1 you may need to flash twice.

I used magisk 19.1. First I used supersu and magisk uninstaller first. I have root now. Thanks for your help. It amazes me that sometime we over look the simplest thing.

burnt_31 said:
I used magisk 19.1. First I used supersu and magisk uninstaller first. I have root now. Thanks for your help. It amazes me that sometime we over look the simplest thing.
Click to expand...
Click to collapse
I know exactly what you mean. I do it all the time.
Nice you got it going. It's pretty lame if you don't root this. I just cut it up and added a couple things and they can be taken out, except radio and the recorder.
Curious if i got it right. If you're on anything other than VMC, is call recording and other micro features working? All the cscfeature xml files are decrypted so you can see what was done.

Everything seems to be working. I appreciate the work, Canadians are usually the last to get Roms. Most are made for the sm-a530f model. I was using the wrong method. One post said about waiting 166 hrs to reboot your phone after zipping RMM_State Bypass etc. etc.. Your way is simple. Once I get a chance I wlll have a look at what you have done, I work long hours. And as you said, what is the point if you cant root. Thanks again.

burnt_31 said:
Everything seems to be working. I appreciate the work, Canadians are usually the last to get Roms. Most are made for the sm-a530f model. I was using the wrong method. One post said about waiting 166 hrs to reboot your phone after zipping RMM_State Bypass etc. etc.. Your way is simple. Once I get a chance I wlll have a look at what you have done, I work long hours. And as you said, what is the point if you cant root. Thanks again.
Click to expand...
Click to collapse
It is 168 hours no reboots and rmm did work that rmm was for Oreo.
I think his would be fine but no guarantees.
Custom kernel 2.0 flash twice.
Light rom works without issue make sure you flash magisk.

Hello I have a530f model with lastest pie version for Russia. I would like to install native screen recorder. Can yo help me ? Please. My email is [email protected]. thanks

fabian_barrios said:
Hello I have a530f model with lastest pie version for Russia. I would like to install native screen recorder. Can yo help me ? Please. My email is [email protected]. thanks
Click to expand...
Click to collapse
Yeah bud. If you unzip the attached file, you can place it in /system/priv-app/ and make sure the permissions are set correctly for the folder and apk. Compare with other apps in the directoty and make it the same.
Then get the activity launcher app from the play store. Use that to make a link for it.

Getting random freezes sometimes, have to reboot phone using hardware buttons. Using Freedom A8

boominboodhoo said:
Getting random freezes sometimes, have to reboot phone using hardware buttons. Using Freedom A8
Click to expand...
Click to collapse
okay thanks for that. It is probably from my csc edits. I can adjust for freedom and hope it makes a difference.
Anything else to mention about it? What you did before flashing, are you using latest twrp, root or non root.... anything at all
no-verity... favourite snack... p.i.n. number(s)... oops sorry not the last two. My mistake. TOO MUCH info. Disregard.

Do a search on xda for rooting your model for the correct version of twrp. U will need no verify no encript. I used the latest Magisk to root. Supersu did not work. I used twrp for the A8 plus and had problems. Get the right one. It's a great rom. https://www.google.com/amp/s/forum....ery-twrp-3-2-2-0-galaxy-a8-2018-t3818201/amp/

I am looking at the csc for FMC and it appears i have doubled an entry. I need to go over all of them to see if i've done it elsewhere. I will have 2 updated ones hopefully late tonight. (Takes forever to upload).
Not sure if that is the cause but i will definitely adjust it.

Quick question in regards to your Rom. I been using it for a while now. Its the best one I can find, I did post a few times at the start. By any chance, did u get adoptable storage working? I know Samsung removed it in Pie. I tried root essentials but still no luck. Thus is not my first time rooting or installing roms. I started with the HTC 1. Lol. So far, u have the best rom for the A8 2018. Its nice and clean. Almost compares with lineage in my opinion. Thanks again. And by the way, I am Canadian.

Thanks
Hey i appreciate the gesture but even though i "made" this, i did it because of other people. SuperR is an invaluable tool. Then you got magisk, the twrp recovery and heck even give ol' Sammy some credit, haha. All i did was spend time learning everything from this site. I can't stress that enough. I still have not paid for superR and i am going to see how i can right after this.
ANYWAY!
Your question. I've never attempted it but i am very certain there's a magisk module that'll do it.
It involved formatting sd to ext 4 or 3. So i will get on it. Got a few 64 gig cards to spare. If you have a computer, grab the superR linux distro. I've run it on 32 bit machines. K... pay superr... adopt a card heheh.

I will look again in the magisk module section. And I give everybody right now credit for all their hard work and sharing it amongst all of us. Thank you. Thank you. I love modding my phones and I could not do it without everybody's help. All my PC's are 64bit.

Nice. If you need any help just ask. Just bought the kitchen.
I'll have something very soon. Mexico's pie has the classic csc folder of old. I think we should unify with some fiesta pie zip ui sorta thingy... um rom.