yashsingh1/xdaforums huggingface dataset:
[HTC 10 Questions & Answers] Alpert3:
Weird tho, now I'm starting having problem with the battery life...

In MM I can reach 6h+ SOT, now it's getting worse and worse, hardly pass 4h30... I regret that I posted 5h+ previously (because it did...at that time).
[HTC 10 Questions & Answers] rambleon84:
My battery life has been slightly worse, typical use for me is mostly browsing internet, texting, streaming videos and music. On wifi when at home, LTE during the day at work.

Running last version of Viper10 for marshmallow:

Upgraded to Nougat around 3/17 or so.

Running Magisk Viper10 5.6.0 for the duration of this:

I'm a couple of releases behind on the latest Viper, will probably upgrade to current this week. I am using magisk version instead of the full rom. Wanted to try and get Good/Blackberry app suite for work running but still haven't been able to get it installed, so not sure ill stick to magisk or not.
[HTC 10 Questions & Answers] comstockload:
Bingo. Same here. If your phone gives you the performance you need then why upgrade? I have went back and forth between MM and Nougat using the same customized rom (Viper). The battery life is similar on both. With the firmware we currently​ have (241.617) for Nougat, I'm still having a few firmware-related app issues. The camera especially. So I've went back to MM. I run a highly-tuned, lean MM rom which also includes the latest version of Greenify. I used GSam to track down excessive wakelocks and other excessive battery-draining apps, and I also control which apps I allow to start at boot (using AIO Toolbox). I run the EX Kernel using the HawkPepper(820) CPU governor profile which is the best performer for my usage (found through trial and error).

I have a lean and mean Viper 3.5.0 MM rom that I am completely satisfied with. When the next Nougat firmware update is released from HTC I'll try Nougat again. Until then, I love my phone as-is.
[Samsung Galaxy Alpha] crosstiger:
Has anybody tried installing the ROM of the Galaxy A5 for example?
[Huawei Mate 9 Questions & Answers] cd993:
Just successfully got Substratum and my beloved favourite Swift Dark theme working on my unlocked/rooted Mate 9 (MHA-L09).

- Installed Substratum

- Installed Swift Black

- Allowed theme to build cache

- Selected Android v7_0 as Android version

- CAREFULLY selected non-system apps such as Gmail, Pushbullet, Chrome etc.

- Reboot!

It would not allow me to choose Youtube and of course I don't feel it safe to apply the themes to any system UI etc.

But this works to get back some much missed themed apps back with Substratum :)

Update: seems that my changed DPI settings don't stick with having substratum themes applied hmm....
[Galaxy Ace II Q&A, Help & Troubleshooting] C0b0ll:
Hello all,

I tried to install CyanogenMod 13 on my GT-I8160 (Galaxy Ace 2).

I followed a tutorial, but I brick my phone...

So I tried:

I reinstalled stock rom with Odin 3.12.3 (UK_I8160XXNA1_I8160BTUNA1_BTU then I tried with TUR-I8160XXMH1-20130916120104).

Now, when I start the phone (volum up + home + power buttons) , I have following error message:

E:failed to mount /system (Invalid argument)
can't mount /system (Invalid argument)
E:failed to mount /system (Invalid argument)

# MANUAL MODE #
-- Applying Multi-CSC
E:failed to mount /system (Invalid argument)
can't mount /system (Invalid argument)
E:failed to mount /system (Invalid argument)
can't mount /system (Invalid argument)
E:failed to mount /system (Invalid argument)
E:failed to mount /system (Invalid argument)

Then, In recovery menu (volum up + home + power buttons), I tried to install "ClockWorkMod 4.0.0.9". But impossible...

On install, I have following error message:

signature verification failed

What can I do to install CM 13 or Lineage 13?

Regards,

C0b0ll.
[Xiaomi Redmi Note 3 Questions & Answers] tindan:
everything that has something to do with sound is simply not working (sometimes make my RN3SD restart)

1. phone calls : cant make any phone calls (when dialing the numbers, the screen show calling but cant connect, then restart. while reboot, the dialed number rang)

2.video (cant play any video with sound, including youtube. always show problem while trying to play)

3.music (cant play any music, alwasy show unsupported files)

QC TESTS :

1.play music on SD -> fail

2. Mic Speak loop -> fail : intenal applivation error and unable to access system space!)

3. Call test ;> fail

(java.lang.illegalargumenexception: invalid audio buffer size.

at android.media.audiorecord.audiobuffsizecheck(uidiorecord.java:674)

at android.media.audiorecord.<init>(audiorecord.java:374 and 271)

at com.longcheertel.cit.loopbackbaseactivity $record.run(loopbackbaseactivity.java:177)

at java.lang.thread.run(thread.java:818)

4. sub mic to speaker loopback ->fail (same as mic cpeak loop)

5. Headset plug in ;>fail

6. Headset key;> fail

7. Headset loopback-> fail

8. FM test -> fail

9. Headset plug out;>fail

APP tests

sound recorder :fail (check if another app is currently using the recording feature)

java:2894, 153, 1434, 102, 148, 5441, 738, 628, 674, 374, 271, 1288, 1265, 2884, and 8 more

soundabout does not help at all, no google setting

please if anyone can show me the right ways to solve this sound problem

About my RN3SD (KENZO):

android version : 6.0.1 MMB29M

MIUI version : MIUI Global 8.1 Stable 8.1.4.0 (MHOMDI)

baseband : -8976_GEN_PACK-1.7444 6.1.75478.1

kernel : 3.10.84-perf-g4b39ed7

PS : another thing i found, settings, additional settings, Headphone and audio effects ---> result is back to settings page

settings, sound and vibration, audio settings --> same, back to setting page
[Xiaomi Redmi Note 3 Questions & Answers] Pachenko_Gr:
Did you try factory reset? Or even better fastboot flash latest ROM?
[Xiaomi Redmi Note 3 Questions & Answers] tindan:
already did, no result
[XDA Assist] nafeessalman37:
Dear sir,

I am using Micromax convas nitro 2 e311. I can't acess internt when i flashed custom rom (Resurrection remix 5.7.4) and all other custom rom based on marshmallow.
[XDA Assist] FSadino:
Hello and welcome to XDA-developers!

If you are using a custom ROM, the best way to get support is on your device especific thread or talking to ROM developer about your issue.

Micromax Canvas Nitro
[Galaxy Grand Prime Q&A, Help & Troubleshooting] mita99796:
Does someone know how to fix this?
[Galaxy Grand Prime Q&A, Help & Troubleshooting] Has.007:
Flash stock rom or any Modded SystemUI.
[Galaxy Grand Prime Q&A, Help & Troubleshooting] mita99796:
It looks like i have to flash rom , is there any other way to fix this .I tried with new SystemUI but didn't work .
[ONE Original Android Development] NoSpamDan:
DOWNLOADS

Flashable MultiROM TWRP v3.1.1 Recovery img file: TWRP_multirom_bacon_20170711-07.img

Flashable MultiROM ZIP: multirom-20161206-v33e-UNOFFICIAL-bacon.zip

Flashable MultiROM Uninstaller ZIP: multirom_uninstaller.zip

Dark-themed MultiROM Manager App: MultiROMMgr-GZR-TBO.apk

(premaca's download folder)

You can thank [MENTION=4453409]premaca[/MENTION] and [MENTION=4139665]martinusbe[/MENTION] for much of this.

Previous versions:

Flashable MultiROM TWRP v3.0.3-0 Recovery:

multirom-20170711-v33e-UNOFFICIAL-bacon.zip

TWRP MultiROM:

TWRP_3.0.2-0_multirom_bacon_20161212-01.img

MultiROM ZIP:

TWRP_multirom_bacon_20170224-01.img

MultiROM Uninstaller:

multirom_uninstaller.zip
[ONE Original Android Development] NoSpamDan:
FAQ/FYI

Here are some common questions and answers with MultiROM:

I can't flash a different recovery on my device because the option is not there.

Most likely, the fstab file in the recovery needs to be fixed. You'll probably need to perform the fastboot steps in #2 below.

How to use fastboot to flash a recovery image to your device:

To flash back to another recovery:

Boot your device into fastboot mode.

Copy the recovery img file you want to flash to a place where you have fastboot installed. You probably did this already when you installed TWRP over your stock recovery so you could flash custom ROMs.

Open a terminal/command window in the directory where fastboot.exe and the recovery.img file are, and type: fastboot flash recovery recovery.img (where "recovery.img" is the actual name of the recovery file you want to flash).

None of my secondary ROMs will boot:

You probably need to run Restorecon on the secondary ROM to modify its selinux contexts. To do this:

In MultiROM TWRP, click the MultiROM options in the upper right corner.

Select "List ROMs"

Choose your ROM from the list

Click the "Run Restorecon" button

Reboot into that ROM

I am not seeing the boot menu from MultiROM to select a ROM.

Make sure you injected MultiROM into your primary ROM. To do this:

Flash the MultiROM zip file to your primary ROM.

Click the MultiROM options in the upper right corner

Select the "Inject boot sector" button

Reboot

If you still have trouble, see [MENTION=2605798]nkk71[/MENTION]'s post here with more information.
[ONE Original Android Development] SirSoviet:
Tried with Lightning kernel (which supports KEXEC-hardboot) and tried booting a secondary rom. It leaves me with an error popup saying "KEXEC-hardboot support is required to boot this rom". No-KEXEC workaround isn't working either.
[ONE Original Android Development] ceiven:
can my 16GB-device work??
[ONE Original Android Development] Claudiosvs:
Great mod. Thanks NoSpamDan for keeping it alive!
[ONE Original Android Development] NoSpamDan:
Going to need more details than that... and thanks for the log.

What ROM primary and secondary?

Did you inject the boot image on your primary?

Try flashing your primary as both a primary and a secondary and see if you can add another secondary. This is still in the testing phase but I have Slim7 as my primary and no issues with secondary ROMs. I don't normally even need restorecon on them when I test (unless it gets stuck at the kernel splash screen)...

EDIT: From your log:

[ 3.375133] multirom: kexec -u test has failed, kernel doesn't have kexec-hardboot patch enabled in config!

Sure, why not? You can use an external OTG drive to keep ROMs on. Depending on how much space your ROM & Data occupies will limit what you can do on such a small storage device.
[ONE Original Android Development] analchemist:
[MENTION=4633983]nikhil18[/MENTION] forgot to enable KEXEC in V35. Use V34, it's enabled/working fine there.
[ONE Original Android Development] SirSoviet:
So it seems that the latest version of LK has broken Kexec, so no need to worry about that. Just the No-Kexec workaround that's problematic.

I'm currently using HalogenOS, and any secondary rom won't work. I injected the boot image on the primary rom, otherwise I would be booting straight into the primary rom.
[ONE Original Android Development] NoSpamDan:
Well I edited my last response to include a line from your log indicating that the kernel does not have the kexec-hardboot patch.
[ONE Original Android Development] SirSoviet:
I know that, I said that the latest version of Lightning Kernel has broken kexec-hardboot. All that needs to be fixed is the no-kexec workaround.
[ONE Original Android Development] JT1510365:
developer options still force closes on nougat roms when you install the nougat rom as secondary so how is this nougat friendly?
[ONE Original Android Development] f41lbl0g:
This depends on the rom itself. I believe a commit is needed in order for it to work properly.
[ONE Original Android Development] JT1510365:
What roms would have it wouldn't rr remix rom nougat have it?
[ONE Original Android Development] f41lbl0g:
I haven't used multirom in a while so I don't know.
[ONE Original Android Development] NoSpamDan:
Great question... it's Nougat-friendly because you can install Nougat ROMs as secondary. :) The Developer Options problem is a bug...

As a work-around, you can install your problem Nougat ROM as a Primary, enable the Developer Options there, then move it to a Secondary slot...

Indeed, a secondary ROM needs this: https://review.slimroms.org/#/c/22989/
[ONE Original Android Development] patstar5:
I'm running a marshmallow and nougat rom together with the last version of multirom?
[ONE Original Android Development] oF2pks:
For nougat compatibility, moving to latest [MENTION=2605798]nkk71[/MENTION] multirom modified_twrp 3.0.3-0 is real better 2017-01-27:

https://github.com/nkk71/android_bootable_recovery/commits/android-7.1-mrom

https://github.com/multirom-htc/Team-Win-Recovery-Project/commits/android-7.1-mrom

BTW, MultiROM' OPs should clarify one for all that multirom.zip' s trampoline works fine with all unmodified recoveries twrp/cwm (primary rom install/update only): modified_twrp is only needed for managing 2nd roms.

Of course, using un-swapped unique modified_TWRP recovery is always much "cooler" (I didn't had much success explaining that to p880' users with : how to rom/kickflip and twrp/shuvit...), and NoKexec workaround is a more complicate behaviour.
[ONE Original Android Development] iruiz2:
Even after flashing v33e, Multirom manager says I'm running v33b... Is that normal?
[ONE Original Android Development] NoSpamDan:
I have a version of 3.0.3-0 built, but I couldn't get my multirom zip file to show the boot menu/boot sector. I did flash the zip and injected it but no luck. I have reached out to [MENTION=2605798]nkk71[/MENTION] for ideas on this, but it might be best if he responds here when he has a chance.

For now, I'll put the new TWRP in Post #2 and here if you want to try it. Keep a previous version around just in case you need to fastboot flash it to your device: TWRP_3.0.3-0_multirom_bacon_20170213-01.img

Yes, it's because it's pointing to [MENTION=2605798]nkk71[/MENTION]'s repo, and it's also using his changelog I believe. I'll have to review, but manual installation is best for now. What the app is most useful for right now is managing your ROMs... ;)
[ONE Original Android Development] slipstream7:
Hello, I was still using multirom version 33e along with twrp-3.2.1-0, and lightening kernel.54. RR is internal and I have been booting for a few months from multirom to an Oreo version of LineageOS. All was fine up to today, except for a random reboot from my rom that can occur from time to time, or a system freeze, but these are quite occasional.

Today when I tried to boot from multirom menu, as usual, I got booted into TWRP instead!

I have tried multiple things that are obviously not helping; I have tried to re-install multirom.zip and then inject the boot sector, I even tried to wipe cache and dalvik-ART cache, just in case. I keep getting back into TWRP. I am rusty and hoping someone can point out the right steps...
[ONE Original Android Development] platinoidum:
2 slipstream7,the latest patched twrp with multirom is TWRP_multirom_bacon_20170711-07.img.We need patch latest twrp 3.2.1.0 with multirom, to work with oreo etc.,but no developers to make this,one of him is pass away,others have no time or desire.I will advise to you reflash the TWRP_multirom_bacon_20170711-07 and nougat in primary rom according to the instructions,or forget multirom.Sorry for my english
[ONE Original Android Development] slipstream7:
Hello platinoidum,

thanks for answering me and sad to hear about the developper passing.

I had originally installed the nougat ROM internally anyways and added the Oreo ROM afterwards. I will try to reflash. I was just concerned that I would loose my data for Oreo ROM if I reflash TWRP. Its not so bad if I have to reflash Nougat ROM....I will update if succesful.
[ONE Original Android Development] :
Does anyone know if the latest ubuntu touch is working? I have plans to dual boot jgcaap's cm13 with lightning kernel for kexec and superior camera, and Ubuntu touch OS with a manually encrypted /home and /tmp for data security and daily use.

Any info would be greatly appreciated ?
[ONE Original Android Development] mustang_ssc:
Some feedback:

Been testing it a few hours ago. Flashed your Candy7 rom as secondary with Resurrection Remix 5.8.1 and Lightning kernel CAF v52 as primary and booted with no problem.

The only "issue" i saw is the lack of EFS partitions, so i guess it's still a WIP. Should we expect something else not working?

Besides that solid build.
[ONE Original Android Development] NoSpamDan:
Thank you, as usual, a most comprehensive response. I'm going to look deeper into this tonight if I have some time...
[ONE Original Android Development] areyouanand:
Installed jgcaap 13 as secondary, now unable to get root, if I flash SU it shows successful on twrp, but after I boot, no root. Any solutions?
[ONE Original Android Development] jhedfors:
I am running official LOS14.1 on my OPO. I am unable to boot my secondary ROM (backup of primary) - it just hangs at the OnePlus logo. Attached are my logs.

Any suggestions to get my secondary to boot?
[ONE Original Android Development] nkk71:
Have you considered updating?

[ 3.026775] multirom: Running MultiROM v33b

^^ Bad 1: OP says v33e

[ 3.044511] multirom: allow_nkk71_nokexec=0
[ 3.075883] multirom: nkk71: primary_boot.img location will be=/realdata/media/0/multirom/primary_boot.img
[ 3.076217] multirom: nkk71: locating boot partition...
[ 3.076417] multirom: nkk71: found boot at '/dev/block/mmcblk0p7'

^^ Bad 2: means you have a very very old NO_KEXEC in there, which would probably also mean

this

this

and

this

are not in there (because I added those after no_kexec 4.1), and...

[ 11.124475] init: Running restorecon...

^^ Bad 3: would poof it
[ONE Original Android Development] jhedfors:
Sorry, I am confused. I installed everything from the OP.

I have tried with different kernels with the same result:

Ab123321

Boeffla

Kernel310

The no-kexec workaround does not work for me.

Is there an updated version I am not seeing?
[ONE Original Android Development] SirSoviet:
Just use ab kernel. As far as I know, it's the only kernel with working kexec. And no-kexec is broken with NoSpamDan's multirom.
[ONE Original Android Development] nkk71:
I'm not talking about the no-kexec workaround, it does however allow me *to a certain extent* determine the build you're running, and the above patches, irrelevant of no-kexec, were written after the (no-kexec) version in your logs. And if those are not included, then a 7.x series ROM will not work.

I'm just using the no-kexec version to determine the build date / version, not whether you are using it or not.
[ONE Original Android Development] jhedfors:
OK, thanks!. I will look for that kernel, and give it a try again!

---------- Post added at 12:04 AM ---------- Previous post was at 12:02 AM ----------

Thanks for your help.
[ONE Original Android Development] jhedfors:
Do you have a link to the ab kernel you mentioned? Or are you talking about the ab123321 kernel I am actually using right now?
[ONE Original Android Development] SirSoviet:
https://yadi.sk/d/1vfjUs723B5TBm
[ONE Original Android Development] jhedfors:
Thanks - that is what I have installed.

Perhaps MultiROM is not compatible with CM14.1 as primary. Would love to hear if anyone has been successful.
[ONE Original Android Development] nkk71:
https://xdaforums.com/showpost.php?p=71024536&postcount=21
[ONE Original Android Development] areyouanand:
https://youtu.be/VClN_D7lvd0 people may find this useful. Neglect that crap music.
[ONE Original Android Development] millomonk:
I know this post, but I don't know what it's telling me. My phone is not encrypted.

Maybe fstab has some invalid entries.

I don't know how to debug any further and where I have to look at next?
[ONE Original Android Development] nkk71:
Are you using f2fs?
[ONE Original Android Development] nkk71:
[MENTION=4435460]NoSpamDan[/MENTION] if you want to support f2fs, you'll need to cherry pick this

I'll be adding it to my repo as well, when I start updating multirom again.
[ONE Original Android Development] millomonk:
Yes, I did a full reset with cos a while ago and that switched data partition to f2fs
[ONE Original Android Development] NoSpamDan:
Thanks, I'll look. However, my MultiROM zips are not even showing the boot menu because of the fb errors...
[ONE Original Android Development] nkanthikiran:
Multirom app doest not amend v33e ..it still shows as v33b

I have flashed the files. While TWRP and Multirom are updated Multirom app doesnot seem to recognize it yet. I have attached screenshot. I am using LineageOS 14.1 as main ROM .. Pls suggest .
[ONE Original Android Development] jhedfors:
Hi [MENTION=4435460]NoSpamDan[/MENTION]:

I am curious, with the official version (twrp-3.0.2-0-bacon.img), you have the option to flash an image file to recovery and boot, but boot is the only option that exists in TWRP_3.0.3-0_multirom_bacon_20170213-01.img.

Why is it missing from your version? No big deal, I just do the flash-boot-flash-recovery-restore-boot shuffle. Thanks.
[ONE Original Android Development] crazykc:
It has already answered by NospamDan on Page No 2. Try to go through previous Comments
[ONE Original Android Development] NoSpamDan:
It was some fstab changes I think. But, thanks to [MENTION=2605798]nkk71[/MENTION], I picked the f2fs commit he mentioned, and I have a new version for you.

If you're on the last version I posted with only a Boot option to flash img files to, then you'll need to use fastboot to flash this. But it takes care of a few issues and seems good here. Do report back your findings for the benefit of others. Thanks!

Here's the latest (also in Post #2): TWRP_multirom_bacon_20170224-01.img

I have also updated Post #3 to include some common questions/issues and solutions. Happy flashing!

P.S. I'm still working part time on the MultiROM boot menu issue. Just needed a break from it for a while... ;)
[ONE Original Android Development] SirSoviet:
Kexec-hardboot workaround is in the Multirom zip and not the TWRP image, correct?
[ONE Original Android Development] NoSpamDan:
Well yes but there are pieces in both that work together....
[ONE Original Android Development] oF2pks:
Wish, you guys, have some time for "basic trivials" f2fs clearances:

-if I have primary rom on hybrid

ext4

/system&cache and

f2fs

/data, does it means that all 2nd roms (within

data

/media/0/multirom) are locked to all/full f2fs partitions ?

-can I format /data with twrp' f2fs_ver=1.4, AND run cm13 or lineage14 built with f2fs_ver>=1.6 ?

Checked on /cache

Starting TWRP 3.0.3-2017-02-20-0-ee427c31-[B][U]dirty[/U][/B] on Tue Feb 28 01:57:39 2017
...
...
I:operation_start: 'Change File System'
Formatting Cache using mkfs.f2fs...

[B][U]F2FS-tools: mkfs.f2fs Ver: 1.7.0 (2016-07-28) [/U][/B][modified by Motorola to reserve space]

Info: Debug level = 0
Info: Label =
Info: Trim is disabled
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 786432 (384 MB)
Info: zone aligned segment0 blkaddr: 512
Info: format version with
"Linux version 3.1.10-MRlzma..."
[B][U]Info: Overprovision ratio = 10.000%
Info: Overprovision segments = 43 (GC reserved = 28)[/U][/B]
Info: format successful
I:mkfs.f2fs -t 0 /dev/block/mmcblk0p4 process ended with RC=0
Done.
I:Recreating /cache/recovery folder.
I:Copying file /etc/recovery.fstab to /cache/recovery/recovery.fstab
I:Version number saved to '/cache/recovery/.version'
Updating partition details...

[MENTION=2605798]nkk71[/MENTION] (thx for latest github) , hope that post is relevant to this awesome thread...
[ONE Original Android Development] effry:
could you share this new version asap? btw the f2fs solution was the same i adviced you like 3 months ago ( i posted a reddit link)
[ONE Original Android Development] nkk71:
1- It was not 3 months ago

2- It was not something we weren't already aware of

3- There was a commit for it already

And... ASAP?? seriously :rolleyes:
[ONE Original Android Development] effry:
1 - don t read that like I'm blaming you that the solution was already there some time ago. was just a simple comment

2 - and yes, as soon as possible, doesn t mean NOW , but as soon as it will be ready. At least I interpreted in that way

Sry for any misunderstanding
[ONE Original Android Development] nkk71:
No worries, and thanks for the clarification, I guess it was a misunderstanding.

It's just that so many people have become accustomed to expect instead of just being grateful when a dev updates/releases something.