yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] canodroid15:
Don't reboot in-between flashing ROM & gapps. You should be on TWRP 3.0.2 & use the "que" option in twrp to flash ROM & gapps at the same time

If you did flash that way then you may need to do a complete clean flash especially if coming from stock or an old ROM. Our ROM has had the opengapps patch since it came out.

1. Backup everything (Nandroid backup, backup internal SD card & any other important data.

2. Wipe data/factory reset in twrp

3. Wipe system, dalvik & cache

4. Wipe internal sd

5. Go to install, choose from zip, then hit add & choose gapps

6. Swipe to install & wait.

7 When flash is finished, reboot & enjoy

---------- Post added at 08:06 PM ---------- Previous post was at 07:58 PM ----------

New Weeklies live on site, go get em' folks! And as always ENJOY! https://www.teamoctos.com/weekly-builds/
[Verizon Samsung Galaxy S III] Jaws4God:
I think my dad is going to start using my S3... right now it has AICP 6.0 on it.. but he may want a more stable ROM. Does the most current version have any bugs? Was the front facing camera ever fixed?

Thank you!
[Verizon Samsung Galaxy S III] toosurreal01:
Been rock solid for me, and yes FFC is working fine.
[Verizon Samsung Galaxy S III] lepa71:
How is the battery compared to TW 4.3? Thanks
[Verizon Samsung Galaxy S III] canodroid15:
R2 release build is up on site, you can get it here https://www.teamoctos.com/release
[Verizon Samsung Galaxy S III] bigbaluka:
Last weeks build was so stable I was gonna skip this weeks build and then y'all go and release R2... These weekly builds are so stable I find it difficult to install the next build. I mean everything is working perfectly so I think to myself why fix what isn't broken? Then curiosity gets the best of me or I read the change log and then I end up flashing once a week. So I finally decide to skip a week and here you come with a release build. You can take this as a rant or a compliment...:rolleyes::p
[Verizon Samsung Galaxy S III] mi9ke123:
Haven't flashed this ROM in a while (been on an older version of it - it's so stable, I haven't needed to)... Just curious what the best gapps to flash with the RC2 is
[Verizon Samsung Galaxy S III] Droidriven:
Open Gapps, micro, nano or pico pack, your choice.
[Verizon Samsung Galaxy S III] postal302:
Had an issues installing the latest weekly (8-27). It hangs on "Patching system image unconditionally."

At first I thought it was TWRP because I installed 3.0.2 just before flashing the weekly, but after a battery pull, flashing back to TWRP 3.0.0 then trying to flash again it hung on the same spot.

Just wanted to let you know!

I love this ROM, solid as a rock! Keep up the great work!
[Verizon Samsung Galaxy S III] canodroid15:
[MENTION=5562144]postal302[/MENTION], how ate you wiping b4 install? Dirty or clean?
[Verizon Samsung Galaxy S III] Deliquified:
Mine was sensitive too. I fixed mine by smacking it off the gel wrist padding of my mouse pad a few times.
[Verizon Samsung Galaxy S III] bthorne79:
[MENTION=4953607]dernome[/MENTION] the call notification is most likely something on your side maybe a theme or something else the incoming calls is not a issue on the rom side it had been tested and verified working before release just like all our Roms are that's why we don't do nightly or weekly release because we want to give users the best possible build we can with minimum amount of bugs
[Verizon Samsung Galaxy S III] bthorne79:
Removed double post
[Verizon Samsung Galaxy S III] LLStarks:
I'll giv this a try
[Verizon Samsung Galaxy S III] yorkwar:
The 4/22 release works like a charm. Thanks for your effort!

I'm looking for a method to change the SMS font only, but still have no luck.
[Verizon Samsung Galaxy S III] dergome:
[MENTION=4590326]bthorne79[/MENTION] I guess it's due te the fact that I am a non-Verizon sim user using a European sim card. I was told in another thread that i must flash d2gsm_rillblobs.zip, which can be found at mastamoon's files...

I haven't tried yet...
[Verizon Samsung Galaxy S III] lepa71:
Do camera and video recording fully work? Thanks
[Verizon Samsung Galaxy S III] Lehocki:
Working fine.

This is one of the best ROMs I have used on my S3

Sent from my SM-G900V
[Verizon Samsung Galaxy S III] Malave:
Installed yesterday. Everything is working perfectly. The rom itself is smooth and fast. The theming options are great. The dedication and professionalism of Team OctOs shows in their work. Thank you for you work
[Verizon Samsung Galaxy S III] lepa71:
Do you have reduce pixels to 6M to make camera work? How is the battery life?
[Verizon Samsung Galaxy S III] bthorne79:
No you don't have to change anything with camera and battery is a YMMV I'm getting 10-12 hrs on my tmo s3
[Verizon Samsung Galaxy S III] lepa71:
How much the screen time do you usually get?

Thanks
[Verizon Samsung Galaxy S III] Lehocki:
That depends on your battery and your usage . I get the same maybe more I was getting on the ROM I was using before

Sent from my SM-G900V
[Verizon Samsung Galaxy S III] jmw03j:
Amazing ROM, thanks for the hard work. Only issues I've had on the current release in 3 days is the standard camera grief, no reboots or force closes.
[Verizon Samsung Galaxy S III] toosurreal01:
Couldn't get this to boot for me. Did a factory reset, flashed rom and gapps.

Gets to the "Android is updating apps" then finishes, reboots, and goes back to "updating apps" screen.

Any certain modem/firmware?
[Verizon Samsung Galaxy S III] narsciso:
Can someone hint me at a guide for installing TWRP? I've began to realize more and more devs rely on that in comparison to CWM. I've always been on CWM, and can't find any (recent) sources as for what needs to be done to get it installed.
[Verizon Samsung Galaxy S III] bthorne79:
Make sure your on the latest for your device that is NOT locked d2vzw locked boot loader on 4.3 use twrp and make sure your doing a clean install which means don't restore data from another rom you should not be getting updating apps from boot ani it should go right to the start up screen
[Verizon Samsung Galaxy S III] bthorne79:
Twrp can be installed many ways.

Flashable zip

Flashify with the .IMG

Odin with the tar in the PDA(pa)/slot
[Verizon Samsung Galaxy S III] bthorne79:
The camera issues have been resolved you should not have an issue with it if you do make sure you did a clean install and didn't restore data from a different rom it can cause havoc.
[Verizon Samsung Galaxy S III] jmw03j:
I did a full wipe when I switched over and don't believe I used any old data, but something must be up on my end. I'll redo it all just to be sure, would love to be able to access the camera outside of Textra again.
[Verizon Samsung Galaxy S III] postal302:
I've been doing a dirty flash each time. My typical process is:

1. Backup with TWRP

2. Flash ROM

3. Flash open-Gapps (nano for 6.0)

4. Flash MF1 Firmware/NE1 Modem (from InvisibleK) -- I do this each time because I'm superstitious and had trouble from the wrong modem before :p.

This is the first time I've run into any issues on install.

---------- Post added at 02:07 PM ---------- Previous post was at 01:41 PM ----------

... so this might be a bad download. I didn't compare the MD5 before installing it, I rarely ever do so it may have bitten me this time.

I'm having trouble generating an MD5 though. I ran a checksum using FX File Explorer and it did not match the MD5 given on the Team OctOS site. Just for kicks I ran a checksum using ES File Explorer and not only did it not match the OctOS MD5 but it also didn't match the FX MD5. :eek:

I re-ran the checksum for both file explorers and they both returned the same values as the first run, but still disagreed with the each other and the MD5 listed by OctOS.

I'll download the ROM again when I get home and see what I get.
[Verizon Samsung Galaxy S III] postal302:
Turns out it was a bad download. I re-downloaded the ROM and ran a hash on it, both FX and ES calculated the same result as the MD5 from OctOS. I flashed and all is well.

Moral of the story: double check the MD5 before flashing
[Verizon Samsung Galaxy S III] Jaws4God:
well i'm thinking the AICP thread may not have as much of a following anymore... I may switch to OCTOS... but can anyone answer a few questions?

Available?

1. Option to use Pie from Bottom. has option for Notification pulldown on pie.

2. Assign Longpress or Double Press to Recents Hardware button (Screen Off specificially)

3. Disable home button

4. Screenshot, Screen Record, Sound Profile, and Screen Off/Power Menu quick Tiles

5. Proximity Wake

Now i know the front camera is working on AICP.. and I believe someone said its working on this ROM.. But I tried to take a picture using Textra and it froze and rebooted.. (twice , repeatable). Does the FFC have issues inside of apps on this ROM?

Thank You.
[Verizon Samsung Galaxy S III] bigbaluka:
Newer versions of TWRP will check MD5s automatically for you if you have the MD5 file in the same directory as the flashable zip file.

---------- Post added at 01:59 AM ---------- Previous post was at 01:57 AM ----------

No problems for me. I've never used Textra though. Also I rarely do a dirty flash.

---------- Post added at 02:06 AM ---------- Previous post was at 01:59 AM ----------

Flashing Firmware & Modem aren't necessary it doesn't change when flashing ROM. Once you've done it once you're good. You should try it once without and see how it works. Flashable memory can be flashed a finite number of times. Granted it can me flashed many thousands of times but why push it? We flash these things enough as it is.
[Verizon Samsung Galaxy S III] postal302:
Good to know about the MD5 check! I never knew that.

I was pretty sure I didn't need to flash the modem each time, but like I said, I was superstitious. A few months back I had an issue with random rebooting to the point where my phone became unusable. For a full day it wouldn't get past the boot animation without rebooting on its own. To this point I had been using solely OctOS for about six months, only dirty flashing each time (I wasn't flashing between ROMs, kernels or anything else). I Odined back to stock solving the problem until I flashed back to OctOS triggering the reboot issue again. Turns out I hadn't flashed a new modem when I reflashed the new ROM so it was crashing because of the wrong one. Now I know flashing the ROM doesn't flash the modem too, but that time when I had the issue it seems it would have been solved by flashing the modem and not needing to go back to stock.

Coincidentally I didn't flash the modem this time and it's working great. Thanks for the tips! :laugh:
[Verizon Samsung Galaxy S III] RashidVet:
when i flash it , it keeps on restarting the phone , please tell me , is it normal ??!
[Verizon Samsung Galaxy S III] Droidriven:
Did you do a clean install? It involves using the advanced wipes to wipe system and data partitions before flashing the ROM, you would also do the normal factory reset and wipe cache partition and wipe dalvik cache before flashing the ROM.

This is done to clear everything that might cause issues in the new ROM so that you have a fresh clean install.
[Verizon Samsung Galaxy S III] RashidVet:
thanks for your reply sir, but i'm new here , i did the advanced wipes (system, cache, dalvik..) but i dont know how to do the factory reset. is it included in tw recovery ?

by the way if i could ask you one more question and hopefully you dont mind , i installed cm 12.01 and flashed modem gaps and another zip (so i'll be able to hang up calls) , it works perfectly but the sounds doesn't seem play correcty (a kind of distorsion ), how could i fix this ?

thanks in advance .
[Verizon Samsung Galaxy S III] Droidriven:
To factory reset you select the wipe option on TWRP main menu, on the next screen it says "factory reset, wipe cache and wipe dalvik" across the top, swipe the slider on the bottom and that will factory reset.

To be certain that you understand what the advanced wiped are, select the wipe option on TWRP main screen, on the next screen select advanced wipes, then on the next screen select "system" and select "data" do not select any of the other partitions listed, then swipe the slider and it will wipe system and data, then you flash the ROM and Gapps, you won't need to flash the modem again, you've done that and it only needs to be done once.
[Verizon Samsung Galaxy S III] Jaws4God:
what is difference of R2 build vs Standard?

thanks.
[Verizon Samsung Galaxy S III] canodroid15:
R2 is the 2cnd release build. Its like a CM snapshot per say. The latest weekly build will always have the latest from CM source & googles latest security patch. The 9-10 weekly build is rock solid. If you want the latest & most up to date get the weekly build. Weeklies contain the latest code & security enhancements. Most of the time the weeklies are just as stable as the release builds. So to put it short & sweet "OctOs release builds & weeklies" are like "CM snapshots & nightlies"
[Verizon Samsung Galaxy S III] Jaws4God:
thanks for the info, i did have an issue with the stock launcher, when I would go to the app drawer, then hit back button, the home screen would be blank..

so right now im on the nexus launcher which is a nice integrated feature.

i do see this ROM is missing a reboot / power menu tile and also pie controls.. I really like to have those so may go to my next rom to try.

if i missed those features, please tell me where to locate them. thanks!
[Verizon Samsung Galaxy S III] Droidriven:
Power menu options are in the Tentacles app in the app drawer or in pulldown settings.

I don't think Pie is an option, I like Pie controls also.
[Verizon Samsung Galaxy S III] Jaws4God:
Thanks for the info... maybe you have already seen from my sig.. but i'm gonna give OCTos a shot. :fingers-crossed:

I actually meant to bring up the power menu without using physical power button.. I am able to bring up a different reboot menu using Power Toggles but it doesn't have the ScreenShot and ScreenRecord options that the main power menu has.. so when I do need those, i guess i'll have to hold down the power button.

I also found a work around for no pie, i mainly used it so i could avoid using the physical home button, and Power Toggles actually has a home button option for my notification shade.. so that will work.

Thanks for all your help.. hope this ROM is more stable than AICP! :fingers-crossed: :highfive:

P.S. I absolutely LOVE the wallpaper!

[IMG="OctOS Brick Wallpaper"]http://i.imgur.com/8YuLfQ3.png[/IMG]
[Verizon Samsung Galaxy S III] PsiPhiDan:
Is this ROM more customizable than CM13? What sort of features does it have? I cannot find a list anywhere. Also, does it support overclocking the kernel? Or does that just depend on the kernel?
[Verizon Samsung Galaxy S III] Droidriven:
1) Yes, more customizable than CM13

2) you can find a list of features and a changelog listing newly added features at the teamoctos website.

3) Yes, it supports overclocking, this ROM even has its' own custom Kraken kernel and the Kernel Auditor app built into the ROM settings.

4) minor overclocking may be possible depending on the kernel but significant/useful overclocking requires a kernel with OC support built in.
[Verizon Samsung Galaxy S III] Master Cylinder:
And, what's not listed in the installation instructions in the OP or on the website, you have to flash GApps every time you update the ROM. It is mentioned probably many times within the thread but the OP instructions don't make it clear and there's nothing about installation on the website that I could find before I flashed the latest and ran into a crap load of fail. After screwing around with it for awhile then figuring it out, I could've just flashed some new GApps but my patience had worn out and service was needed, so I restored AICP. If I can get my little problem worked out on that one, then ....

I don't have the interest to devote to phone phun that I used to perhaps. One will either have to use new GApps each time on Octo or face updating each time. Could do it with TiBu perhaps. I have rebelled against the daily updating of 4-8 apps, or should I say that my tolerance for such nonsense had been completely depleted, plus sometimes the update stinks, so I only update manually occasionally.

CloudMagic (:good:)is getting on my tits by putting a message at the top of my inbox all the time to upgrade to "Newton"! (:mad:) Yea! Another yearly subscription service! (I just want IMAP - gotta start looking for another one I guess. Yes, there's always Gmail ....)

Sorry about the rant ... but, mostly crickets in the d2vzw forum anyway .

---------- Post added at 11:53 AM ---------- Previous post was at 11:51 AM ----------

PS - If I'm wrong about the GApps thing someone tweak my nose!:cyclops:
[Verizon Samsung Galaxy S III] mamarcac:
I'm a human and I follow the d2vzw threads :laugh:

Actually really appreciate learning from others' experiences here. Been a lurker for years and finally signed up to post in Invisiblek's CM13 thread as he has already released CM 14 :highfive:
[Verizon Samsung Galaxy S III] Master Cylinder:
Holy schlit! What's it like? Crikey! I need to get over there!:good::highfive:
[Verizon Samsung Galaxy S III] mamarcac:
Installed R2 last night with Open Gapps (nano) and I must say this is a very smooth running, responsive rom so far. Only installed Gmail, Chrome and Maps and will let the phone "simmer" for a day before installing the rest of the apps.

Big thanks to the OctOS team for doing this. Camera even works, including FFC, from the R2 release! Hoping this stays stable to use as a daily driver.

[MENTION=5519140]Master Cylinder[/MENTION] I haven't given Invisiblek's CM14 a shot yet. Honestly CM13 (not Invisiblek's builds, mind you) just had too many issues and instability for me. I need my phone as a daily driver and can't have the random crashes, nonrepsonsive screens, inconsistent camera, and lag that CM13 had. Not sure what changed with CM, but back in the days of 10.X for this device, they made a REALLY snappy rom with almost no issues. Must be that some of the devs are working on other things for other devices now, which is understandable.

If OctOS M remains stable and it sure looks good so far through the first 12 hours, you guys extended the life of our d2vzw by several years minimum so thank you!
[Verizon Samsung Galaxy S III] crofutt:
can't receive calls

Installed ROM and everything was working fine. Then I tried to recover text messages using titanium. Now I cannot receive calls. Send and receive text and make calls, just can't receive. Wiped and reinstalled but problem persists. Any suggestions? Thanks
[Verizon Samsung Galaxy S III] Droidriven:
If you made a backup before flashing the ROM, restore that nandroid and then use SMS Backup from play store to backup your texts, then flash the ROM again, restore everything you restored from Titanium except for text then restore the texts from the SMS backup.
[Verizon Samsung Galaxy S III] crofutt:
Thanks for the suggestions. But I already did a wipe and reinstalled. Still no receiving of calls. Next I wiped again and restored my backup from LiquidSmooth. That works fine and receives calls just like before. Wiped and installed OctOs and again no ability to receive calls. Wipe, restored LS then wiped again and installed CM12.1 and that too will not receive calls (That is a reported problem with no solution I found) . wiped and back on LS. I liked the OctOs rom for the few days I used it and would very much like to get it working correctly again. And at the risk of being repetitive, it was working fine until I tried to restore sms with titanium. I dont care about the sms recovery, just want to be able to use this rom. Thank you for the help.
[Verizon Samsung Galaxy S III] Droidriven:
Just to cover the bases and be clear. You still can't receive calls even after doing a wipe and reinstall with or without restoring the SMS from Titanium?

When you say that you wiped, do you mean the normal factory reset, wipe cache and wipe dalvik/ART? Or do you mean you did the advanced wipes to wipe system and data in addition to the normal wipes? If not, try wiping system then flashing the ROM.
[Verizon Samsung Galaxy S III] crofutt:
That is correct. I cannot receive calls with OctOs now. I did NOT try to recover the sms a second time. I did just a normal factory reset each time. I enjoy doing this stuff but am by no means proficient at it. Are there any concerns when wiping the system? I mean, loss of data? I really appreciate you taking the time to help me.
[Verizon Samsung Galaxy S III] Droidriven:
The advanced wipes format the selected partitions so yes all data in those partitions gets wiped, data partition gets wiped when you do a factory reset so that's no different, the difference is it wipes the system partition to ensure that little things that cause issues aren't going to be there, this process is called a "clean" install, it's basically the same as doing a full wipe and reinstall of Windows.

If you were coming from stock a clean install is recommended anyway just to avoid issues. I had to do a clean install when I first flashed OctOS and I do a clean install every time I flash an OctOS update.
[Verizon Samsung Galaxy S III] crofutt:
Thank you again but unfortunately I still have the problem of not receiving calls. Is there a more drastic step I could take? If so, repercussions of doing that? Or perhaps you have another suggestion? I can not understand why it worked great and now it will not. Has to be fixable.....
[Verizon Samsung Galaxy S III] canodroid15:
Are you on the MF1/NE1 bootloader & modem combo? If not you'll need to update in order to run the newer ROMs & have functional phone calls & text etc.. I recommend you read the entire OP of invisiblek's CM 13 thread linked below to get a better understanding of what all you'll need to know before updating. There's also a "nuke-it" zip by invisiblek that deletes the telephony db. you might need to flash at least onnce. Just be sure to do your research 1st. Good luck! Here's the link to invisiblek's CM13 thread...

http://xdaforums.com/showthread.php?t=3269675
[Verizon Samsung Galaxy S III] Droidriven:
That was the next suggestion, I assumed that since they were using ROMs they should know about the bootloader/modem already.

That info should be in every ROM thread because we all know that once they get to where they can flash ROMs and find a ROM thread, they don't go any further than that thread, especially since the info about the bootloader/modem is in old ROM threads, threads most won't even bother looking at since Lollipop and Marshmallow are available.
[Verizon Samsung Galaxy S III] canodroid15:
Good idea, either I or bthorne79 will add it to our OP sometime today ;)
[Verizon Samsung Galaxy S III] RashidVet:
i got a problem guys , i cant get it to connect with 4g , i have 4g sim card and i did tried every single network option , stil dont work , when i check any option of network , it disables my phone network and i can't even make calls, it only works if i select : GSM only or GSM/WCDMA , please help me guys !
[Verizon Samsung Galaxy S III] crofutt:
Yes, I am on mf1/ne1. Didn't have any time today to play around with this but I'll read the thread you mentioned. Thanks for the suggestions!

edit - I scanned through the thread you mentioned but did not find anything directly related to not receiving calls. I saw references to the Nuke it you mentioned but did not actually learn why I would and what it would do. I assume the .db file will rebuild itself or do I need to reinstall the rom? Thanks again!
[Verizon Samsung Galaxy S III] canodroid15:
Noted in the OP under firmware requirements, MF1/NE1 combo. I'll see about linking to the actual files & if i ts cool I'll update OP with a link under the "basic instructions" section ;)

---------- Post added at 12:40 AM ---------- Previous post was at 12:36 AM ----------

To be clear, are you on the MF1 firmware NE1 modem combo? Have you had this issue on other ROMs? Are you trying to use the phone on GSM network or is it a Verizon LTE sim? What ROM are you flashing, weekly or release & what date is the build?