yashsingh1/xdaforums huggingface dataset:
[Verizon LG G3] Idrove:
I'm having an odd issue that started after a reboot with M2 and ongoing with M3. Google Hangouts will not merge my SMS and hangouts threads. I've tried the manual method of long pressing on both convos and the "Merge" button never shows.
[Verizon LG G3] tbird462002:
Anyone else having issues with wifi not saving passwords after a reboot. I clean flashed 2 times and I'm still having the issue. I also tried 2 different gapps and that didn't have any effect. I deleted the wifi and dlna folders under data/misc/ and that didn't fix it either.

The wpa_supplicant.conf file in data/misc/wifi gets wiped out every time I reboot.
[Verizon LG G3] red3razor:
Asked around a bit in test group. Not sure anyone has had issue. I have seen others mention in other cm based roms, leads me to believe it may be acquired by cm source upstream. That said, fellow team member pointed to this, maybe will help: http://android.stackexchange.com/qu...-forgetting-all-wifi-passwords-after-a-reboot
[Verizon LG G3] splxtreme:
I didn't see a q&a for this ROM so... I can't for the life of me figure out how to remove the clock app. I found 2 folders with the apk but they keep returning after I remove them.

Any ideas?

---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------

Oh, and I noticed that the screen turns on in my pocket quite often. Any ideas on how to limit this as well?

Thank you!
[Verizon LG G3] articzap:
If I dismiss an alarm early, it still continues to chime away as if I never pushed the dismiss button.

Anyone else run into this?
[Verizon LG G3] andresgp:
Amazing Rom and two questions

This is the best ROM I've ever tested. I'm incredibly grateful to Team OctOS. It just runs incredibly fast and battery life is great, so much better than stock. Plus all the customization options are fantastic.

There's only two small issues that maybe you can help me figure out:

1) It seems that the InfraRed (IR) blaster is not recognized now. I've installed a few remote apps to control the TV and the AppleTV (that were working with the stock rom), and now they say that the device is not compatible (meaning that it does not have an IR). Any way to fix this?

2) Sometimes the device forgets the wi-fi passwords after a reboot. Luckily, the phone works so well now that I haven't rebooted it in more than a week! With stock I needed to reboot almost every day to fix slugishness. Still, it would be great to find a fix for the wi-fi passwords.

Thanks again Team OctOS!!!

Andres
[Verizon LG G3] splxtreme:
You'll have to change the permissions. You'll need to find the app to change it, or just simply download a different kernel. I used http://xdaforums.com/lg-g3/development/kernel-fechdakernel-t3126745 and couldn't be happier. With a little tweaking, I get really good battery life and performance.
[Verizon LG G3] michaelgg13:
Since I installed M3 google play services constantly crashes and the play store can't get a connection. while play music and the rest of the gapps work fine. any ideas? I cleared the google play services cache with no luck.
[Verizon LG G3] greatquux:
You know I had the same problem when updating from M2 to M3. I went crazy doing a lot of things... I eventually decided to do a Titanium Backup (plus SMS Backup) of all my important applications and just set up M3 from scratch and then restored the data for all my apps using Titanium. That worked. Hopefully I won't have the same issue updating to M4 whenever that comes out...

hey devs, any update on how the next milestone is progressing? I think it might be good to wrap up the latest CM fixes for 5.1.1 before 6.0 comes out.
[Verizon LG G3] red3razor:
New builds up at https://www.teamoctos.com/supported-devices/lg/lg-g3/
[Verizon LG G3] megalosdog:
Speaker volume for multimedia is very low, any fix? Thanks.
[Verizon LG G3] greatquux:
Getting the same issue with google play services crashing and being unusable after upgrading from M3. I restored from a backup and all is fine. I'm going to see if I can dirty-flash another ROM.
[Verizon LG G3] johndoe8:
Still running M2 on my G3. Can i do a dirty flash to M4 (wipe cache, install M4 and GAPPS)??? Thanks for any help :D
[Verizon LG G3] greatquux:
You may have better luck than me , I got Google play services crashing constantly, but reinstalling gapps might help with that. I dirty flashed cm nightly from m2 then installed gapps to stop crashing so you should be able to also.
[Verizon LG G3] canodroid15:
Good news! We've decided to start doing weekly builds, you can find them here https://www.teamoctos.com/weekly-builds/ ENJOY! We will still do our monthly milestones.

Weeklies will be done every Friday night & at the latest should be up by Saturday.
[Verizon LG G3] johndoe8:
Sorry to bug. Im just wondering if i can dirty flash from M2 to M4 without any problems. Anyone have any input? thank you very much!!!
[Verizon LG G3] blindguyinanorgy:
android auto

I can confirm that the M4 release works with android auto. I was having issues with older versions of CM12.
[Verizon LG G3] blindguyinanorgy:
sd card

with M4, I can no longer see my SD card. Has anyone else seen this?
[Verizon LG G3] canodroid15:
None of our testers reported this issue. Most if not all have moved to the weekly build. If you haven't flashed the weekly build give it a spin, I'd say its 99.9% stable on all of my devices.

---------- Post added at 02:38 PM ---------- Previous post was at 02:36 PM ----------

Clean flash is recommended.
[Verizon LG G3] canodroid15:
New weekly up on site!

Sent from my SAMSUNG-SGH-I747
[Verizon LG G3] canodroid15:
Hey guys & gals, we had to pull all of today's weekly builds due to a few issues. We're working on it & should have new builds up by 2moro if everything goes right. Sorry for any inconveniences guys. I'll post when new builds hit the site.

Thanks, Team OctOS ?

Sent from my SAMSUNG-SGH-I747
[Verizon LG G3] canodroid15:
New builds are back up now, ENJOY! ?
[Verizon LG G3] canodroid15:
New weekly builds up on site!
[Verizon LG G3] canodroid15:
No weekly this week. Instead We're gearing up for our 5.1.1 milestone (M5) release! LP Weekly builds will continue for all non-Nexus (CAF) devices until each device is brought up to MM. This will take time, which is why we've decided to continue our CM based weeklies for these devices. Going forward with 6.0, we've decided to return to our AOSP roots! We truly value our users & appreciate your patients while we make the transition. Thanks for all the support! Good things to come ? I'll update you guys when the builds go live!
[Verizon LG G3] canodroid15:
M5 is up ENJOY! ?
[Verizon LG G3] CykloneFij:
M5

Salubrios! M5 has been running sweet.

Thank you
[Verizon LG G3] canodroid15:
Glad you're enjoying the ROM man & you're very welcome! Thanks for choosing OctOS ?
[Verizon LG G3] blindguyinanorgy:
Is there M5 highlights like you have for M4 on the website?
[Verizon LG G3] canodroid15:
Yes, you should find the changelog in the zip when you download the ROM. I'm not sure why its not on the website. I'll look into it.
[Verizon LG G3] canodroid15:
New weekly is up, go get it! ENJOY! ?
[Verizon LG G3] canodroid15:
11-14 weekly build up on site!
[Verizon LG G3] mopartonyg:
Is the new weekly 6.0 yet? sorry to ask but the site says AOSP 6.0
[Verizon LG G3] canodroid15:
Its not but we're working on it. We've got the Nexus devices running Oct-M & were working on phasing in our CAF devices now. Were moving to an aosp base so it takes a little while longer on non nexus devices.
[Verizon LG G3] mopartonyg:
Thanks , cant wait
[Verizon LG G3] johndoe8:
Hey guys. Im having an issue with my calls. When i make a call, it seems to connect and then the call ends right away. Looking for any and all help please. Im running M2 btw. Anyone know what could be causing it and possible fixes? Thanks in advance :)
[Verizon LG G3] canodroid15:
Unfortunately, I have no idea what would be causing it. By M2 I assume you're running a really old build. I recommend updating to the latest build. Weekly builds go up every Saturday. You can find them here. https://www.teamoctos.com/weekly-builds/
[Verizon LG G3] canodroid15:
New Weeklies up! Go get em! https://www.teamoctos.com/weekly-builds/
[Verizon LG G3] blindguyinanorgy:
hard reset

With this rom i continually have to pull the battery. This has been true m2-m5. It seems to get worse as days go by since last flash. I do not wish to flash weeklys just to have it be stable.

is this an issue with ocOS or CM on G3 in general?
[Verizon LG G3] articzap:
I never do battery pulls with my G3 and I've been on a few different ROMs. I'm currently running M5 and before that was M2. Have been running OctOS for 5 months or so now with zero issues.
[Verizon LG G3] articzap:
I setup a new WiFi network in my house and now my rooted G3 is DHCP looping. It does not do this on any other network, and worked perfectly with my old setup.

Thoughts?
[Verizon LG G3] blindguyinanorgy:
i went to stock 5.1.1 (35B) pre rooted to try and fix my battery pull issue. Its driving me crazy and ill go back and deal with battery pull if i have to. However I am getting a error message:

cant install this package on top of incompatable data. please try another package or do a factory reset.

It does show that it is looking for baseband 23c or 24B. I tried flashing the 24b modem image to see if it would help but no results.
[Verizon LG G3] canodroid15:
Hi everyone! Hope all is well. I wanted to let you know that there will be no weekly builds this Friday/Saturday due to the Christmas Holiday. We at Team OctOs would like to wish you and your families a Merry Christmas and happy holiday season! We look forward to picking up again next week and may even have a couple surprises for you! Peace! And thanks for understanding.
[Verizon LG G3] articzap:
Thanks for the update!

I hope you and the entire OctOS team enjoy your holiday's as well!
[AT&T Samsung Galaxy S 5] hsbadr:
MultiSystem is a powerful tool for locked- and unlocked-bootloader Android devices with many features that at least includes the following:
[AT&T Samsung Galaxy S 5] hsbadr:
Video Tutorials

A quick preview of MultiSystem v1.0 tested on Lollipop for VZW Note 3. The video has been captured on a stable virtual ROM of JasmineROM v5.0.1. It's FULLY compatible with FlashFire on virtual/stock systems. More devices will get supported as well, after required testing.

[YOUTUBE]CsMZl2PfQFQ[/YOUTUBE]

[YOUTUBE]A7fYBPiArlw[/YOUTUBE]​

Facebook: https://www.facebook.com/hsbadr/videos/vb.331488823689599/428178174020663
[AT&T Samsung Galaxy S 5] hsbadr:
How to check if you are running a Stock/Virtual System?

There're many ways to check whether you're running a Stock or Virtual system. MultiSystem app should include this simple check at some point. That's important to avoint ruining the Stock system & keep it safe. To make it clear to NOOBZ & anyone who's requesting "another" proof even though I owe hime nothing. Very weird!

Anyway, BusyBox mountpoint applet can print the current block/device mounted to /system mountpoint by running the following command:

busybox mountpoint -n /system

The stock system is mounts the original system partition:

[B][COLOR="Red"]/dev/block/mmcblk0p23[/COLOR][/B]

while the virtual system mounts a loop device associated with a system IMG:

[B][COLOR="Blue"]/dev/block/loop0[/COLOR][/B]

Here're two videos for both stock & virtual systems...

[YOUTUBE]lks1D4eAZ1g[/YOUTUBE]

[YOUTUBE]o2ryf2Xr1rU[/YOUTUBE]

UPDATE:

Now, you could run the following command to print the current system (stock or virtual) and the system device (physical partition or loop device):

MultiSystem status

Note: The block device number (mmcblk0p23) may vary per device & per variant !
[AT&T Samsung Galaxy S 5] hsbadr:
How to repartition microSD card for MultiSystem?

You can use any tool/program for partitioning on Android, Linux, Mac, or Windows. For example, MiniTool Partition Wizard is a good partitioning tool for Windows. So, let's use it for this task. Simply, you need to follow this PDF tutorial (thanks to [MENTION=3271517]carl1961[/MENTION]). In sum:

Step 1: delete old partitions on SD card

Step 2: create FAT32 PRIMARY partition

Step 3: create EXT4 PRIMARY partition

Then, apply changes (note that the program UI may get changed in newer versions).
[AT&T Samsung Galaxy S 5] hsbadr:
How to check microSD card partitions for MultiSystem?

You need to correctly repartition microSD card into two partitions:

exFAT or FAT32 for the 1st partition (your new external storage)

EXT4 for the 2nd partition (your MultiSystem partition)

Use the directions in this post!

You should check your 2nd SD partition in EXT4 format mounted to /MultiSystem:

check that the /MultiSystem directory exists after a reboot

check that the 2nd SD partition (/dev/block/mmcblk1p2) is mounted to /MultiSystem by running the following command in Terminal Emulator or ADB shell:

mount | grep /MultiSystem

The output should be:

/dev/block/mmcblk1p2 /MultiSystem ext4 rw,seclabel,relatime,data=ordered 0 0
[AT&T Samsung Galaxy S 5] hsbadr:
How to check MultiSystem Installation?

The 1st thing to do after installing MultiSystem is to check the /MultiSystem directory & its contents (it shouldn't be empty!). Then, check usage by running the following commands in Terminal Emulator or ADB shell:

su
bash
MultiSystem

If it retuns "MultiSystem not found" or permission denied, try to use open MultiSystem app to Update Configurations & try again. If this does't fix it, try the following command:

/MultiSystem/bin/MultiSystem

This should work if you've MultiSystem binaries installed in (extracted to) /MultiSystem directory. If so, you can create a symlink in /system/xbin as follows:

mount -o remount,rw /system
ln -sv /MultiSystem/bin/MultiSystem /system/xbin/MultiSystem

Then, test it by running:

MultiSystem

The last thing before using it is to check the boot options: reboot & monitor the GREEN LED indicator for 3 seconds (change in the app) , which give you the following options:

Volume UP = Primary virtual ROM

Volume DOWN = Secondary virtual ROM

HOME KEY = Stock System

Sure, you should have installed one or more virtual ROMs.

Backup & restore or creating/installing a virtual ROM are easy as copy & paste: all img's will be at

/MultiSystem/img/system

To backup a virtual/stock system, you have many options:

Use create function to create from stock system

Use copy function to copy the IMG

Copy & paste with a new name

Use FlashFire (fully supported on virtual/stock ROMs)

...

If you've IMG mounting issues, run the following commands:

mount -o remount,rw /system
busybox ln -sv /proc/self/mounts /system/etc/mtab

If this doesn't help, try mounting from Terminal Emulator or ADB shell after selecting the IMG in MultiSystem app, by running the following command:

MultiSystem mount virtual
[AT&T Samsung Galaxy S 5] ecera:
I've read up on the Q&A and development op. After following the instructions here is my current situation. I have the multisystem installed on a stock rooted rom(NCE w/OA1 bl). My ext sd is partitioned in two primary sections. One Fat32 and the other ext4. 50gb and 20(ish)gb. The app opens fine. I clicked install and received a toast notification on the bottom. Then I tried to flash the multisystem zip in safestrap. Flashing in multisystem was not possible for me. When I selected the zip from the multisystem "select file" option nothing appeared in the space under the option. When flash was pressed nothing happened. Anyways, I ended up flashing in safestrap. It appeared the the script was ran and my phone rebooted. The op said to wait for the green led light and set selinux to permissive. Never got that screen. I've tried it a few times now with same results. After I flashed the multisystem zip in safestrap and not getting the green led and multisystem screen on boot I tried flashing the zip in multisystem. Same result, I am unable to flash from the app. It lets me select the file. But after that it doesnt appear in the items to be flashed and pressing the flash button is met with a toast but nothing happens. I'm stuck any help is appreciated. Thanks.
[AT&T Samsung Galaxy S 5] Billy06010:
stupid question. Do you have to be rooted for this to work?? Tried on locked lollipop bootlader from att and it force closes.
[AT&T Samsung Galaxy S 5] hsbadr:
You can't use the flash function until you correctly install MultiSystem. Follow OP instructions & install MultiSystem from within app; then, flash the ZIP file via FlashFire. If this doesn't work for you, send me the log file (if created at all) & /system/bin/e2fsck.

Also, you may get assistance from VZW N3 users here: http://xdaforums.com/verizon-galaxy-note-3/help/qa-multisystem-android-t3089530

Root access is required.
[AT&T Samsung Galaxy S 5] ecera:
Here are the two files. I odined to NCE w/OA1 bootloader because I ended up soft bricking after a failed flash attempt of the Multisystem.zip in flashfire.(no idea why that happened, I probably goofed up somewhere). Followed muniz's upgrade method for lollipop to keep root OC4 w/OA1 bootloader. Followed the steps as you said to properly install Multisystem. Same result. When I'm on lollipop when I click to add a file in the Multisystem apk it doesn't even open up the files. As it did when I was on 4.4.2 NCE. That's one difference I noticed. The reason I updated after I Odined to NCE stock was that the phone was really laggy. Overall it was the same result for me trying to install Multisystem. Again, I appreciate your help. Thank you.
[AT&T Samsung Galaxy S 5] Rakuu:
I got this installed and everything looks correct, i dont see any green led on boot though. Do you need to have a second rom installed for mulisystem to show up?
[AT&T Samsung Galaxy S 5] hsbadr:
It seems that you're missing some steps here. Could you please follow or this post or this one, but with skipping any device-specific steps? Just read that post to understand/find the step(s) you've missed. Also, before doing anything, you can check MultiSystem installation: http://xdaforums.com/showpost.php?p=60554742&postcount=6
[AT&T Samsung Galaxy S 5] hsbadr:
Which version have you installed? The latest version fixes LED indicator for S5 & S4.
[AT&T Samsung Galaxy S 5] ecera:
I followed the steps as explained in the two posts you quoted. Same result, no green LED after flashing the zip. I went to terminal emulator after flashing the zip and performed the command "mount | grep /MultiSystem" and nothing happens. I just get a new line for a different command. I went into /MultiSystem in root browser. Folder is empty. Not sure if that's normal. On a side note, Is there anyone on ATT S5 running rooted Lollipop that has successfully installed MultiSystem that can chime in?
[AT&T Samsung Galaxy S 5] hsbadr:
Ok, MultiSystem v1.3 will get released today.
[AT&T Samsung Galaxy S 5] ecera:
You are awesome and thanks again for helping me out.
[AT&T Samsung Galaxy S 5] Rakuu:
I have the latest one, my /Multisystem has some folders in it, mount | grep /Multisystem comes upbwoth proper output and running Multisysyem does give an output. Should i turn on runnkng at boot in the settings? Or is something broke that you're going to fix in 1.3?
[AT&T Samsung Galaxy S 5] hsbadr:
No, the on-boot commands is device-spcific kernel tweaks that are currently disabled. Check changelog in the main development thread. Mainly, it now has an option automatically mount the stock or secondary virtual IMG on boot. This has some flashing-releated considerations that I'll explain ASAP.
[AT&T Samsung Galaxy S 5] hsbadr:
You can consult [MENTION=5906506]Rakuu[/MENTION] on his successful installation of 1.3.
[AT&T Samsung Galaxy S 5] Rakuu:
I just want to double check, i'm not supposed to get any screen right? Just the green led which im supposed to press a key after seeing?
[AT&T Samsung Galaxy S 5] hsbadr:
Right! GREEN LED >>>

Volume UP = Primary virtual ROM

Volume DOWN = Secondary virtual ROM

HOME KEY = Stock System

You can press multiple time if you wish to make sure it picks up you choice. The SleepTime for boot options can be set in the APP (default: 3 seconds).
[AT&T Samsung Galaxy S 5] Rakuu:
And pressing nothing just boots stock?
[AT&T Samsung Galaxy S 5] hsbadr:
The active system: stock or primary virtual system.
[AT&T Samsung Galaxy S 5] hsbadr:
http://xdaforums.com/showpost.php?p=60583625&postcount=6
[AT&T Samsung Galaxy S 5] Rakuu:
Whats the process for making a system.img? Is the only way to install the rom you want and make the copy?
[AT&T Samsung Galaxy S 5] ecera:
I would like to update that I finally got MultiSystem working after many tries. Many thanks [MENTION=5906506]Rakuu[/MENTION]. Walked me right through it.
[AT&T Samsung Galaxy S 5] cmerlyn:
Hmmm, followed the instructions carefully, including re-partitioning the external card. Installed MultiSystem, hit Install. Used FF to flash the zip file. Made sure I used v1.3. After reboot, no green light. Must have missed a step somewhere. For now, no big deal as the TMS5 and Alliance ROMs need a bit of tweaking to work with MultiSystem.

Edit: Installed again, followed the exact same steps, got the green light. Got "Process system isn't responding. Do you want to close it? Wait OK" and closed it. Restarted phone, got same error message, told it to wait. Got "Auto update of time and date." Seemed to reboot again. Stayed on the AT&T screen a long time. Screen went black, got "Process system isn't responding. Wait OK" Screen black with notification bar.

Just cycling through this. Pulled battery and restarted, working fine now. Whew!
[AT&T Samsung Galaxy S 5] tswb:
i have the same issue can some body guide me step by step or make an video about install multisystem on s5 at&t g900a please.
[AT&T Samsung Galaxy S 5] cmerlyn:
I am running stock rooted lollipop (muniz_ri) on G900a.

1. Downloaded the MultiSystem apk and zip files (v1.3)

2. Read everything again

3. Copied apk and zip to external SD Card

4. Made sure I had Flashfire working by loading it, hit + and install zip or ota and browsed to where the files were.

5. Read everything again

6. Turned my phone off. Note: I did not die.

7. Took card out of phone and put it into an adapter

8. Put adapter in PC and copied everything to the hard drive.

9. Carefully followed the steps outlined in the PDF file that shows how to format the card.

10. Copied everything back to SD Card

11. Put card back in phone and booted up. Made sure everything was OK.

12. Ran ES File Manager, browsed to where zip and apk files were. Ran apk.

13. Ran FF, browsed to where zip and apk files were. Flashed zip.

14 Phone rebooted. No green light.

15. Repeated steps 1-14. Got green light, but phone wouldn't boot.

16. Pulled battery. Replaced battery, started up, got green light. Booted properly.

Step by step, with booboos and everything. It now seems to be working. I can not stress enough: Read everything until you understand it.. Copy it and print it. Follow steps precisely. It may not work, but at least it won't be because you did something stupid.
[AT&T Samsung Galaxy S 5] hsbadr:
MultiSystem Video Tutorial

[YOUTUBE]CsMZl2PfQFQ[/YOUTUBE]​

Thanks To: [MENTION=4246643]Tomsgt[/MENTION] , aka RootJunky ;)

Don't forget to subscribe & like the video to show appreciation of his great effort & time spent in making the video :highfive::good:
[AT&T Samsung Galaxy S 5] tswb:
now i got the green light how to run different rom.. im on rom 4.4.4 kitkat and i want to run Twi5ted lollipop V6 on virtual.
[AT&T Samsung Galaxy S 5] unk2009:
I installed MS tool (Via Rootjunky tut) but was unable to launch Terminal Emulator from within the app ( I then ran TE independently) it worked but It didn't say stock image but instead it was Jasmine 5.0.1 ? Also, which would be the best way to install another rom (i.e. Rakuu's Twisted Lollipop V6 or TalkingMonkeys' TMS 5 1.0) using MS Tool?

Thank you for this awesome tool