yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Timmmmaaahh!:
I've finally taken a look at your logs. Sorry, I've been really busy testing latest RR O release for Bacon.. Haha, kidding! I wish... For starters, let's completely ignore you're using the LIMBO PRACTICE app as even just mentioning it here is highly XDA-illegal. Feel free to PM me if you need to know more why, just don't ever mention it again in a public thread.

An interesting line that caught my attention is "Build fingerprint: 'oneplus/bacon/A0001:6.0.1", are you sure you're using this ROM? It's supposed to be on 7.1.2.

Apparently, your graphics driver is attempting to access memory that the CPU cannot physically address. I'm not sure how to fix this. If it were Windows, updating your graphics driver would most likely fix it but it isn't so simple on Android (yet). So, let's try something else. Start by wiping cache and Dalvik/ART cache in recovery. You may want to clear data of com.android.phone (Dialer) as that one gave you some trouble according to the logs. You also seem to have com.google.android.dialer installed (Google's dialer), that may be conflicting. Disable one of them (via Settings > Apps or with TitaniumBackup. Don't remove, just disable/freeze) and set the default Phone app to the one remaining (preferrably Google's Dialer).

Further troubleshooting (try the above first): flashing different firmware may be helpful as well. Try flashing this Frankenstein release (make a backup of modem and EFS before you do).

If problems persist, it might be related to "Limbo Practice", that yellow little devil does a heck of a lot more than just blocking ads. You may even have to perform a clean install to remove its presence entirely. If I may suggest an alternative, go with AdAway and add "http://adblock.mahakala.is/" as Host source.

Let me know how it goes! :)
[ONE Android Development] bmark240:
My Build Prop also shows:

ro.build.fingerprint=oneplus/bacon/A0001:6.0.1/MHC19Q/ZNH2KAS1KN:user/release-keys

And my phone settings show the Build Prop & screenshot below after a clean flash. And yes. You can see that it is this ROM.
[ONE Android Development] bmark240:
Sorry. About addition to post.

But the XDA Labs app didn't allow me to post another screenshot (crashed app. Boo.)
[ONE Android Development] Timmmmaaahh!:
Oh, okay. I couldn't check as I'm not on RR currently. That either has a purpose or Varun forgot to adjust it. Oh well, no biggie ^_^

Thanks for the heads up! [MENTION=4670577]ace_apr27[/MENTION] you can ignore the version part :)
[ONE Android Development] osrox:
Me too facing same Problem.

Tried many Camera apps, OP5 mod, Camera Nxt mod, & stock RR camera...

No app works at all.

I tried clean flash of RR rom too, but no help.

A 3rd party app from Playstore, gives an error, that Camera is in use, by another app.

Does anybody know a solution.

---------- Post added at 08:20 PM ---------- Previous post was at 08:09 PM ----------

I'm facing Camera app not working problem.

Even flashing the above OP5 camera app, doesn't work, the app just crashes.
[ONE Android Development] malcolmm21:
Which Rom and kernel are you using, also check the about phone page for selinux status and post it here
[ONE Android Development] TeoJohn92:
Hi, I need some help here. I was running RR-N-v5.8.5-20171020-bacon-Final, everything working fine but having sometimes random reboots. So i tried to change Firmware and i flashed the Frankenstein Firmware linked above. The phone now stucks in the boot animation and it never finishes booting. Any help would be appreciated.
[ONE Android Development] bmark240:
First off try the obvious: clear caches (Art/Dalvik).

Next if this fails:

Hold down the power button on the right side of the phone until it powers off & starts to boot back up. If this works then great!

Secondly:

If this doesn't solve the problem then you need to try a couple of things causing the bootloop problem.

1. Is the bootloop happening straight away?

When it says Powered by Android.

Or

2. Is the bootloop happening later in the boot sequence?

If it is the first case. You need to download & copy a different Kernel to your device & flash it using TWRP.

If it is the second case. You might need to uninstall Magisk.

Download an older version of Magisk & its uninstaller.

Sometimes bootloops are caused by mismatched checksum errors.

The phone is becoming confused by these errors and causing a problem in boot sequence. By clearing caches this will help get rid of errors.

Hopefully this might help you. I'm sure that plenty of others will offer additional help too.

My way of hard reboot (power button to shut off & reboot) should help you regain access into the ROM.

---------- Post added at 11:49 AM ---------- Previous post was at 11:36 AM ----------

Any more problems you need to see. Find answers in post 3333.
[ONE Android Development] TeoJohn92:
Thanks for the help! Well, first i tried to clear all caches and many reboots but no success. So i made a Nandroid Backup of all partitions and twrp gave me some errors related to persist and modem partition (not remembering precisiously). After that i tried to format data/system/factory reset (in order) just to verify which partiton could be corrupted, but all the time i have bootloop in rom animation (also if i factory reset and clear flashing the rom). So i downloaded the Cm 13 stock rom and clear flashed it in fastboot mode: also in this case i have the bootloop! So i reflashed twrp and reflashed RR rom by twrp (without gapps) and magically the rom boots! Now i'm just trying to restor Nandroid backup hoping it works fine.

Ps: Before i flashed CM13 stock, i restored modemst1.bin and modemst2.bin and persist.img that i had in my pc. Don't know if it could have been help.
[ONE Android Development] Timmmmaaahh!:
You overreacted. Did you give it enough time when the phone wouldn't fully boot after flashing the firmware? You see, when a firmware flash didn't go entirely as expected, the device will hang in boot animation for quite some time (5-10 minutes). Eventually it will automatically reboot to recovery (letting it do this is paramount!). Simply rebooting again to system from recovery (not wiping or flashing anything) will allow the system to boot normally. I have flashed firmware about 30 times so far and this irregular behaviour occurred 4 or 5 times, the result was always the same: a successful firmware flash that just needed a bit more time. Sometimes you just need some patience.
[ONE Android Development] TeoJohn92:
Probably you're right! Maybe i should have tried a hard reboot as you say, but it had been more than 20 minutes in bootloop so i thought there was some problem. However, I restored the Nandroid and everything seems to work fine. Now I should have the stock firmware of the cm13, right?
[ONE Android Development] Timmmmaaahh!:
Hm, 20 minutes is quite long, it didn't take that long before on my end. Do check md5 hashes on firmware zips. And yeah, you now have c6-00241 if you didn't flash any firmware on the side. c6-00241 is still the recommended firmware but each one can give you somewhat different results. Perhaps download a few of them if you want to try again and make a backup of 'modem' and 'EFS'. There's a few linked in my guide. If it would get stuck again for over 10 minutes, just hold power to turn it off and turn it on again normally. Try that at least 3 times to confirm it really refuses to boot.
[ONE Android Development] TeoJohn92:
I usually backed up the modem and efs from recovery, but now those options are gone!
[ONE Android Development] Timmmmaaahh!:
Wait, what TWRP are you using? TWRP 3.1.1-5-TugaPower has been my faithful companion throughout my flashing adventures for a very long time now, never let me down once. Don't use 3.2.1-1, wiping cache takes, like, 20 minutes... More info here. There's also the K releases, though I find that dev highly unethical (personal preference but I should mention it anyway) :)
[ONE Android Development] TeoJohn92:
I'm using last official twrp-3.2.1-0-bacon, and before this i often used twrp for multirom without problems :)
[ONE Android Development] bmark240:
I have to agree with [MENTION=4841620]Timmmmaaahh[/MENTION] on this point.

Use Tugapower TWRP.

His builds backs up EFS properly.

K build is not my thing (always getting failures & errors on ROM & GApp packages with it).

MultiRom version doesn't allow you to backup EFS properly & you have to reflash TWRP through ADB in order to use another version.

One final bit of advice:

If things are not broken. Don't try to fix them!
[ONE Android Development] Timmmmaaahh!:
Oreo RR released!

"The wait is finally over!"

(although we do have to wait just a bit longer for Bacon, so it seems)

Read the Release post on G+

Current devices released so far:

Cheeseburger (OP5)

Dumpling (OP5T)

Kenzo (Xiaomi Redmi Note 3)

Oneplus3
[ONE Android Development] bmark240:
I hope that we have plenty of configuration & customization features on Oreo. That's one thing I enjoy on RR ROM.

I also want Wireguard support at kernel level (or a feature).
[ONE Android Development] sk4ze:
Hope [MENTION=5841742]mustang_ssc[/MENTION] makes a sultanized version as well !

Thank you so much for all of this support on bacon guys!
[ONE Android Development] :
Do you know why Nougat build is taken down. Is it lack of storage capacity problem?
[ONE Android Development] bmark240:
Final Nougat build is here on my Google Drive link:

https://drive.google.com/file/d/0Bx9ATNx5dUjPUjVMWjFFZjI2TEk/view?usp=drivesdk
[ONE Android Development] :
More phones get oreo update. Hope we can have it today or tomorrow. I have that feeling
[ONE Android Development] sr.arenisca:
Why you find that dev highly unethical? idk the k recovery is the best for me
[ONE Android Development] Timmmmaaahh!:
I'm not saying it's a bad recovery, I'm just saying we're not very compatible people. It's a long story but this is a good start. I won't get into it any further. That would be too much off topic and unethical from my part ;)
[ONE Android Development] osrox:
Will OnePlus One be updated to RR-Oreo v6.0 ?

Note: I'm just looking for an official reply in: Yes or No.

& NOT an ETA !!!
[ONE Android Development] wah_luck:
A very technical question indeed!
[ONE Android Development] Rpbht:
Hello Devs. I just want to know whether bacon will get oreo or not ? (its not like an ETA but just want to know )
[ONE Android Development] drishd:
Wait is finally over!Expected in next 3 to 4 hrs.
[ONE Android Development] Rpbht:
Thanks Alot Man !
[ONE Android Development] ace_apr27:
I flashed the boefla kernel. It's made the reboots a LOT less frequent but they still happen from time to time. An entirely new problem that has arisen now is that sometimes, the phone doesn't charge at all when plugged in. It doesn't drain, but it definitely doesn't charge. Last night, I put navigation on for my hour long drive and plugged the phone in to the charger (it was at 16%). When I reached my destination, it was at 17%. This is crazy considering that normally, it would probably have been at ~85%+ in that time (yes, with nav on and all that). Rebooting the phone has fixed the problem so far. If I plug in and see that it isn't charging after about 5 to 10 minutes, I unplug, reboot and replug. This usually fixes the non charging issue. Any idea what might be causing this?

osht okay! Thanks for letting me know, I had no idea!!

This is really strange. After my last post, I did another clean flash (nuked EVERYTHING, including internal storage) and installed the latest boefla kernal. This seems to have taken care of MOST of the random reboots but has introduced new issues. (see above).

I'm planning on nuking the thing again today. I'll skip the yellow smiley and go with AdAway as you suggested. Will keep you posted!!

Thanks!
[ONE Android Development] xda481:
In advance, please answer!Oreo put on a clean section or "Data" do not touch to save the settings?

Sorry for my English!
[ONE Android Development] LTMendarynas7:
you will need to do clean flash (formatting everything except internal storage)
[ONE Android Development] preshit_more:
Why its taking so much time to upload??! Am becoming restless... Waiting eagerly for RR oreo..
[ONE Android Development] zx604176460:
agree
[ONE Android Development] :
you can look at nexus 5, they still haven't got it after 2 days
[ONE Android Development] Timmmmaaahh!:
Seriously guys? Relax and follow Varun on G+. And c'mon, we're all excited about this release but the same old rule applies: no ETA!

Sizzled with Bacon ?
[ONE Android Development] TippEx1:
What gapp we'll need to use?
[ONE Android Development] Timmmmaaahh!:
I'm sure any 8.1 package will do. I'll probably be using the latest unofficial by deadlyindian. Nano should be your best bet.
[ONE Android Development] varund7726:
To keep you guys updated on the O build , yes it built and its booting

Everything works except for camera which is a major issue

It will take some time to fix .

It'll be a miracle if I get it to work this week .

Most probably an O test build will be given to my testers next week .

Thanks
[ONE Android Development] himanagendra:
Omgg ? ? ???m gtng d feeling of a good spicy tasty yummy meal aftr long time tnkusmch broo ?

Ps: lucky to b a part of tester team
[ONE Android Development] preshit_more:
I was unable to wait for hours....was checking the g+ every now and then....and now a week....omg..

Just give me the RR as it is....i will buy a camera separately.... Lol...
[ONE Android Development] GIL0802:
Thanks for the continuous support!

So guys, it'll be a new xda thread, right ? Or he'll edit this one ?
[ONE Android Development] bmark240:
[MENTION=4817632]varund7726[/MENTION]: In the other ROM releases, both

Agent_fabulous and jhalayashraj are using Sultanxda camera blobs

on Snap Camera. Could you just use that as a test until a better workaround gets released by the lineage team?

I'm sure that there are plenty of us who would bug test for you.
[ONE Android Development] varund7726:
That's an interesting workaround .will try that

Although a quick update

I have camera working but camcorder is broken
[ONE Android Development] pritambhadane:
You are the bosssss :good:
[ONE Android Development] pranavrocksharma:
Take your time and make a good rom with camera functionality
[ONE Android Development] wah_luck:
How different it is going to be from the Agent Fabulous ROM, which is an fully functional Oreo. Btw this ROM is working excellent..

Wish i had an extra OPO to try soon to be launched RR-Oreo:silly:

RR as usual would be having tons of Customisation options
[ONE Android Development] Ricardo reverb:
Good job varun ????, please take your time and don't forget the oreo on onyx

Best regards

Ricardo
[ONE Android Development] ironfreak:
https://sourceforge.net/projects/resurrectionremix-oreo/files/bacon/

Waiting...... :p
[ONE Android Development] evenkirs:
Dont know if its related somehow but right after I updated snapchat to latest "most hated" update, I cant pull my notification bar anymore and also my phone does not show any notifications anymore. Still notification light works and I get messenger notification sounds.... Flashed my rom again - did not work :(

Rocking RR-N-v5.8.5-20171020-bacon-final

Edit: Clean flash worked for me. Installing all apps and setting up settings was annoying tho..
[ONE Android Development] Timmmmaaahh!:
Clean flashing is a bit drastic for such issue, no? Still, kudos for your efforts! I think completely uninstalling Snapchat and installing it again should've worked. Another thing to try would've been manipulating Expanded Desktop settings (forcing notification bar to be visible).

Edit: Apparently this is a known issue, see post below.
[ONE Android Development] minecabla:
I've had that problem multiple times already.

This article has a fix for it: https://www.xda-developers.com/broken-navigation-bar-lock-screen-ota-update/

You should bookmark it. Just in case you get this problem again. :)
[ONE Android Development] ace_apr27:
Looks like it really was the smiley. After the clean install I did last week, the ROM has been rock stable. Not one random reboot. I'm guessing the smiley's interference with Google Ad services causes stuff to become unstable. Ah well. AdAway is working okay for now. Guess I'm going to give the Xposed framework a shot too (I hadn't installed it because I suspected it to be the cause of the reboots).

If I do end up with an unstable system, Oreo should be out soon so I'll simply clean flash to that one :D
[ONE Android Development] atulpchaudhari:
I am using AdGuard... But on Lineage OS 15.1 latest build as on page no 152 of LOS 15.1 thread
[ONE Android Development] mcflurryXD:
The download links that work are only for 5.8.0? Links in the OTA on my device show 404 errors?
[ONE Android Development] atulpchaudhari:
Go to Page no 849, u will find there, the link for final Version of ROM.... Besides the cloud space costs money... May be developer may have deleted or may subscription ended.....
[ONE Android Development] mcflurryXD:
That build is 9-24, the OTA says the latest is 10-20.
[ONE Android Development] emil90:
phone is restarting constantly, not loading the os

Hi

I was on the latest resurrection remix build on my oneplus one. Suddenly yesterday, the phone restarted multiple times while I was using it for browsing. Now it is rebooting constantly and it does not load into the os. I restored the backup from the TWRP recovery, still it is the same.

What should I do now? Please help
[ONE Android Development] preshit_more:
Any chance for happy news this weekend? Its been one week my friend is teasing me with RR on his phone...:(
[ONE Android Development] AZGeek:
The happy new is that it is now the weekend.[emoji1] No ETAs! It's a rule. You can look it up.

Sent using my OnePlus One (bacon - God's candy)
[ONE Android Development] preshit_more:
Haha...bro...i was not asking for ETA....just a bit curious that's it...

Don't mind...
[ONE Android Development] bmark240:
Try and use an older build & see if it has the same bootloop problems. Do not update the kernel or Magisk. If this is still a problem send a Logcat log.
[ONE Android Development] Wolfensteinor:
The phone starts dialing 112 when I press the emergency button.

Is this supposed to happen?

How can I change it to 911 because I'm from USA?
[ONE Android Development] Timmmmaaahh!:
Doesn't 112 work as well in the US? 911 works just the same here in Belgium.
[ONE Android Development] Wolfensteinor:
http://fox6now.com/2013/03/01/alert-in-case-of-emergency-dial-911-and-not-112/

I think it works for me so far because my carrier redirects 112 to 911. But might not work on non GSM phones.

Is there a way to change it?
[ONE Android Development] Timmmmaaahh!:
Ugh.. Why is the US so stubborn in adopting other standards? Anyway, we shouldn't dwell on that. Now is a particularly difficult time to address such issues as RR Oreo is in full development (release imminent? :p) and releases for Nougat will most likely be fully discontinued (not such a surprise as last release has "final" in its title).

To clarify the problem a bit more, what emergency button are you referring to? The one on a secure lockscreen shows a dialpad first (which allows calling 112 AND 911), doesn't it?
[ONE Android Development] noname000:
lightroom export issues

Hey there!

I'm using the RR rom on my OPO since last week and this is awesome. All the apps works so much better than before, except one, Lightroom (Lr). As I haven't found any related post by search, I have to write my issue. I've used the CM 12.1 rom before, and the Lr was perfectly exported the edited dng photos while on the RR rom, I got an error message withoutany useful information, only stating that there is an error. The app is also a bit laggy, it wasn't on the CM rom.

Anyone else having this issue with the app?

Could someone try this, if he/she has the same problem with the app?

Would really appreciate some help with this.

Thanks in advandce. :)
[ONE Android Development] bmark240:
Hey there!

Could you go to app settings.

Either do this by holding the icon & sliding it to the top of the screen and choosing App Info.

From there goto storage option.

Clear Cache. Clear Data.

Or goto Settings->Apps->Highlight the App by pressing the icon.

Clear Cache. Clear Data.

If this fails, you might have some stray files that do not belong anymore (why they are known as orphan files).

Boot into TWRP-> WIPE CACHE & ART/DALVIK CACHE. Reboot into system.

Hopefully this will solve the most common issues.
[ONE Android Development] iPusak Gaoq™:
Well if you haven't change the batteries since you bought the device then it is time for you to changes it....
[ONE Android Development] tlg68:
When will rr 8.1 be published?
[ONE Android Development] bmark240:
Please read our Rules on XDA & don't ever ask for an ETA. It is considered rude in the world of mobile development.

Go to this link & refresh every minute:

https://sourceforge.net/projects/resurrectionremix-oreo/files/bacon/
[ONE Android Development] Papagaj:
It will be published 3rd July at midnight
[ONE Android Development] Enigma817:
gapps error

when i tried to flash gapps it showed me the error code 70. how can i fix it?
[ONE Android Development] Timmmmaaahh!:
You're trying to install a Gapps package that is too large for Bacon's limited /System partition. Try a smaller package like Nano. I don't really remember but I think Mini is the largest one (~340MB) that works on Bacon. Depends on your ROM size of course.
[ONE Android Development] atulpchaudhari:
Last time I heard, I think in month of April.... Have u personally contacted Varun on this subject....... will have to wait but not tht long...

As even LOS or even AOSP (Stable -Not totally stable people have issues with this stable version of AOSP ROM too)..

Need to keep patience..... If base ROMs are stable yet, can't expect to get RR Stable One ASAP......
[ONE Android Development] Timmmmaaahh!:
No no, [MENTION=6153232]Papagaj[/MENTION] is right. There will be grand fireworks the day after to celebrate the Bacon release of RR O!

*sigh*

Now can we please stop speculating?

Refresh the download page like a maniac, follow Varun on G+, keep an eye on the RR G+ community, follow his Cheeseburger/Dumpling releases and be patient.

We'll get there eventually =)
[ONE Android Development] bmark240:
What people seem to forget is Varund is very busy releasing for newer phones, bug testing, (Camera, GPS etc) finding solutions & back porting for our 801 chipset. I know that there are other Oreo ROMS out but those will not have the feature set that Remix has (yes even Dirty Unicorn's & Candy builds).

TL DR: it's not just about the source code anymore ¯\_ (ツ) _/¯
[ONE Android Development] RBwai:
Please for an advice. How to disable "ROM update" notification. As latest Rom was very problematic, I' m back on 20170924 version. So how to disable annoying ROM update notification?
[ONE Android Development] Turpb:
Go to RR settings => Other => OTA. Disable updates and have a fun.)
[ONE Android Development] xxexusxx:
is root still enable? or do I have to do that myself?
[ONE Android Development] bmark240:
Root is still enabled by default: Magisk 14.0 automatically installs within the ROM setup.

Please note however:

Root will NOT be included in Oreo builds in the future.
[ONE Android Development] atulpchaudhari:
Hey Guys, Is this one for our OnePlus One or sum thing Else???
[ONE Android Development] atulpchaudhari:
I am talking about tht Green coloured link is tht a Test ROM for OPO?

---------- Post added at 08:08 AM ---------- Previous post was at 08:05 AM ----------

Or is it for D851 (which nothing but LG G3 T-Mobile)?
[ONE Android Development] Timmmmaaahh!:
Honestly, what do you think when reading "This folder has no files."?
[ONE Android Development] gegabit:
where i can download RR last release?
[ONE Android Development] amoutie:
https://sourceforge.net/projects/resurrectionremix/files/bacon/Nougat/
[ONE Android Development] Zokki66:
Thanks for the link. Finally I can update my OPO again
[ONE Android Development] Ricardo reverb:
The sourceforge.net servers for the oreo builds are down??

?