yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] iPusak Gaoq™:
good to heard that but i did saw a lot of people having trouble with it (different phone) hopefully there not going to be any trouble with bacon :fingers-crossed:
[ONE Android Development] keipha:
See page #717
[ONE Android Development] iPusak Gaoq™:
There nothing in page #717 that can answer my questions and if you're thinking i'm asking for ETA then guess again, i don't...
[ONE Android Development] SLAlmeida:
Hi all,

I have a problem when I try to change the governor to interactive, the EPO freezes for a short time and then reboots, what can be happening?

I use the KA Mod v15.

Can someone help me?

Thanks
[ONE Android Development] Timmmmaaahh!:
What's on page #717? Is this like room 1408? This is creeping me out, dude. :rolleyes:

Just like anything: if it ain't broke, don't fix it. If flashing clean, I would suggest replacing Magisk V12 in the RR zip with V13.1 OR run the Magisk uninstaller (advised) and flash 13.1 seperately. It is stable after all :)

---------- Post added at 02:00 PM ---------- Previous post was at 01:58 PM ----------

If your "EPO freezes", it's because you've put it in the freezer instead of the fridge :p

But seriously, is that on default (resurrected) kernel? If so, just dirty flashing (check md5 first!) should solve the issue.
[ONE Android Development] keipha:
Sorry. I was trying to answer camera problem. Wrong quote.

---------- Post added at 01:08 PM ---------- Previous post was at 01:07 PM ----------

Page #717
[ONE Android Development] SLAlmeida:
Timmmmaaahh,

I am sorry my bad english.

In Brazil when a smartphone hangs we say that it froze.

I typed it wrong, left EPO instead of OPO.

This is happening with any change in the governor.

The MD5 has been checked and is correct.

It seems to be the case of fradbari90 - post # 7264
[ONE Android Development] Timmmmaaahh!:
Hah, sorry, that was just some satirical humor, I know what you meant.

Can you do me a favor and flash a custom kernel? I just wonder if that changes anything.

...ab123321 Kernel, click here!

...Boeffla official, click here!

...Boeffla unofficial, click here!

...FrancoKernel, click here!

...Lightning, click here!

Perhaps go for Franco, that would be the easiest.
[ONE Android Development] SLAlmeida:
With Unofficial Boeffla Kernel - Boeffla-Config V2 and Franco Kernel r51 - KA mod v15, the change is made normally.

The problem must be in some conflict between the ROM kernel and KA mod v15.
[ONE Android Development] nīīTīīn:
Please make a it compatible with lenovo vibe k6power
[ONE Android Development] remix96:
I'm on an April build of this RR because it is the most stable for me. In these days Magisk updated; can I update it without any problems or risk that the system's stability will be compromised or it's better to not update because i'm on a old build?
[ONE Android Development] Sakti51:
What date exactly is your build?

Im on june build and I got random reboot sometimes.
[ONE Android Development] malcolmm21:
If your device is stable there's no need to upgrade I feel. I'm on the latest build n I updated and Frankly I don't notice any difference
[ONE Android Development] remix96:
I'm on April 17 build with stock kernel, got no reboot from months

I'll update Magisk only to pass safety net's control
[ONE Android Development] Papagaj:
I still don't understand what is Magisk used for, and at this point I'm affraid to ask
[ONE Android Development] jdkulkarni:
Hi All,

After trying Nitrogen (Issue with Dolby installation and GPS connectivity) and Tuga (Issue with battery life and WIFI connectivity) I am on latest build of RR and it is running good.

I observed fast battery drain and SOT is 3-5 hours max.

Another issue that is worrying me is that, battery percentage suddenly drops down by 20% or 25% in few minutes. I think the battery calibration is not correct.

Can you please help me to solve above mentioned 2 issues?

I have flashed ROM after doing factory reset. No major battery draining apps running.
[ONE Android Development] bdwilk:
Magisk is an app (in basic terms) that grants other applications and services root access to your device just like SuperSU. Unlike SuperSU, magisk can also hide itself and the other rooted apps from root detecting services that would block a user from using their services. For example; banking apps, Snapchat, safetynet, Android pay, etc. It has been around for quite awhile now and is still highly maintained to keep up with the ever changing updates to said root detecting services (safetynet), but isn't as stable as SuperSU in my opinion. The link to the magisk thread is below in case you'd like to read more.

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/post68966662
[ONE Android Development] Papagaj:
wooow man, thanks for detailed explanation. Better than google
[ONE Android Development] Timmmmaaahh!:
Considering the age of our device we'll be seeing a steadily increasing number of battery complaints. That aside, those SOT prospects are not bad at all. What is your normal charging routine? It could be useful – if it's been a while – to charge to 100% and let the device drain completely until it turns off. Do this twice. Then try keeping up a charge between 20% and 80%, which preserves its health and provides most accurate representation of the percentages you see.

If you suspect it's a system issue, you can include a /system wipe instead of just using a factory reset (/data + caches). The troubleshooting flow is straightforward and simple:

Things getting quirky? > Dirty flash! > Doesn't help? > Factory reset! > Doesn't help? > Full clean flash!

Or one could mix things up a bit > semi clean flash (keep /data but ditch /system).
[ONE Android Development] josera22:
Thanks

I would never have found it because I do not understand English.

I use google translator.

Thanks again

I can not install it. There is incompatibility with another app installed, which is the camera. I'm going to uninstall it sooner and it will not let me.

What I can do? I can not find a solution and I have read some pages later to see if anyone was saying how.
[ONE Android Development] akabour:
I also had random reboots that completely stopped after flashing the 20170707 build.
[ONE Android Development] paskalion:
getting 3 random reboot in the last 24 hour. my current build is RR-N-v5.8.3-20170707-bacon-Official

magisk v12 with universal safetynet fix module installed

is there any log that i can/should post?
[ONE Android Development] maxisgsm:
i try to install last night, but i got error 255.

what it this error?
[ONE Android Development] bdwilk:
Did you do a full wipe? Dalvik, system, data, cache. If so and it still happens then try wiping internal. Be prepared to push the ROM and GAPPs from either otg or PC as everything will be deleted from your device. Error 255 usually occurs when restoring backup, not flashing a new ROM. Something with not enough space left on the device (maybe). Give more information for more help.
[ONE Android Development] maxisgsm:
yes, first i format data but it gave me an error, after that i wipe dalvik, system, data and cache, but still have an error.

now i run pure lineageos. i use OTG to flash the ROM and GAPPs.
[ONE Android Development] malcolmm21:
one doing *#*#4636#*#* wifi calling provision switch is locked on off. Anyone know how to activate it since i want to use wifi calling .Latest buid n stock kernel
[ONE Android Development] SenzaSenso:
Hi guys! does alarm work in this rom when the phone is off??
[ONE Android Development] MBDdk:
Unfortunately not. I've just tested it and nothing happened.
[ONE Android Development] Cholerabob:
For reboots the last KMSG is needed, the easiest way to get it is to install kernel Adiutor . There's a fonction that lests you copy the las KMSG to txt.
[ONE Android Development] paskalion:
thanks for the info..

here's my kmsg http://root.paskal.my/last_kmsg.txt

random reboot once less than an hour ago
[ONE Android Development] SenzaSenso:
:( tnks...
[ONE Android Development] SenzaSenso:
Can you help me?? I can't use "ok google" everywhere...... Why??
[ONE Android Development] Timmmmaaahh!:
It's not available in your language. Set your system language to US English and it'll work.
[ONE Android Development] SenzaSenso:
No...doesn't work...
[ONE Android Development] Cholerabob:
Wifi reboot happened again

RR 20170317 ( yeah old one but works well for me ) was cleaned flashed

TWRP is 3.0.2.0

No added stuff ( blobbs or themes or anything else )

RR Kernel

Can someone take a look at this ?
[ONE Android Development] Timmmmaaahh!:
Even after reboot? Working fine here... What Google version do you have?
[ONE Android Development] SenzaSenso:
7.6.17.21 arm

With all permission enabled..
[ONE Android Development] Timmmmaaahh!:
Did you flash pico Gapps? That could be related. I always go for Nano, which includes Google Search (and probably some needed components).
[ONE Android Development] SenzaSenso:
Yes, I flashed (or 'I did flash"??) Pico Gapps!

Can I flash Nano Gapps now or I have to do all wipe??

Ps sorry for my English...!!!
[ONE Android Development] bmark240:
Firstly make sure that you have Build Prop edit:

ro.opa.eligible_device=true

Next ensure that you goto:

Settings>Languages & Input>Virtual Keyboard>Google Voice Typing>'Ok Google' detection.

Click Say 'OK Google' any time toggle.

Retrain Voice Model>Get Started.

Follow the prompts.

If this fails then you need to go to:

Magisk Manager> Downloads>Scroll down to>

Google Assistant Enabler.

Download & install the Module.

Reboot & test by following the above procedure

for Retrain Voice Model.
[ONE Android Development] Timmmmaaahh!:
Don't be, your English is fine. Both uses of the verb flash are correct, though I wouldn't brag to technically challenged friends how you were "flashing" last night ;)

The correct procedure would be:

1. Backup everything

2. Wipe only /system

3. Flash ROM + Gapps

4. Wipe caches and reboot
[ONE Android Development] SenzaSenso:
WORKS!! WORKS!! thank you so much!!!!
[ONE Android Development] paskalion:
[MENTION=4841620]Timmmmaaahh[/MENTION] could you please help me with my random reboot issue?

here's the logs
[ONE Android Development] Ztones:
I updated magisk to the latest 13.2. The update worked, it now says I have 13.2 installed. However, I get notifications about 4-5 times a day to update to version 5.06! ??????

Edit : never mind... I think 13.2 is the magisk version, 5.06 is the magisk manager app version.
[ONE Android Development] Dade1:
The second update refers to the apk
[ONE Android Development] Timmmmaaahh!:
A lot going on in there. Could you give some context (ROM version, Kernel ...)?

Give weather permission for starters, go to Settings > Apps > Three dots top right > Show system > Scroll down to OmniJaws and tap it > Permissions > Switch location on.

[personal rant]

Honestly, whenever I see "com.facebook.katana" in a log I feel a sudden twinge coming on. It's the center of so much pain, both system and life wise ;)

[/personal rant]

I'm getting the feeling you've enthusiastically customized some kernel settings and now something is berserking, could that be? Also, what audio controller are you using?
[ONE Android Development] shyam124:
[MENTION=4841620]Timmmmaaahh[/MENTION] - I need help my phone is stuck in a bootloop. I was using the 20th june RR rom update for the oneplus one. Now I have tried to clear cache and system and reinstall the os but it wont install it boot loops in between while installation. Please help me

---------- Post added at 06:25 PM ---------- Previous post was at 06:07 PM ----------

any one please help
[ONE Android Development] raul.lopez1958:
How can you change the font in the last update?

Thx
[ONE Android Development] paskalion:
Thanks for your attention [MENTION=4841620]Timmmmaaahh[/MENTION]

My ROM & kernel details attached below. To be honest, I don't tinker with the kernel. I just use what's come with the ROM. Audio controller is default. I dont use Viper or as such.

Some history on my Oneplus One:

1. Coming from Sultanxda LOS14.1 (lineage-14.1-20170625-UNOFFICIAL-Sultan-bacon) - no random reboot, quite stable, but not much customization, switching to RR (mainly for the statusbar mod and some other useful mod)

2. Flashed Resurrection Remix ( RR-N-v5.8.3-20170620-bacon-Official ) - some random reboot on this build, so I flashed latest build

3. Flash latest RR build ( RR-N-v5.8.3-20170707-bacon-Official )

Please advice.
[ONE Android Development] Timmmmaaahh!:
Don't panic. When you panic, you just start doing random things that probably will make it worse. When your device bootloops, just follow these simple steps:

Get to recovery mode by holding volume down at one boot or turn the device off by long-pressing the power button and hold power+volume down to get to recovery (you seem to have nailed this one so far).

Wipe cache + Dalvik/ART cache partitions and reboot (seemingly your first attempt).

When still in bootloop, get to recovery again.

[optional] You can backup the /data partition at this point if you want to recovery stuff later on.

Wipe everything except internal.

Flash ROM + Gapps (skip Gapps if you keep running into trouble) and reboot.

If you're still experiencing bootloops, target your TWRP. Flash a newer or older version in fastboot.

Repeat until it stops :D

[optional] when managed to boot properly, you can extract stuff from the earlier made /data backup with TitaniumBackup.

It happens that it keeps failing. Sometimes you just need to turn the device off and leave it off for about an hour. Or even leave it be for the night and continue the next day, you'll initiate further troubleshooting with a clear mind. Don't lose track of the battery level, you really don't want it to die in the middle of a flash! Above all: remain calm. Think every step through. If failure persists, resort to fastboot flashing system images. You may want to copy internal /sdcard media (externally!) before doing anything because the further you get in the recovery process, the bigger the chance data will be lost. Good luck!

---------- Post added at 09:34 PM ---------- Previous post was at 09:24 PM ----------

Okay, thanks. Disable that theme first. In Substratum, use the hamburger menu to navigate to Recovery and tap Restore Theme (give it a minute), Restore Fonts (wait for it) and anything else you've had customized. Just today I ran into some issues with a theme gone mental. How frequent are these reboots?
[ONE Android Development] gaurav-singh:
Guys, urgent help required.

This has happened to me twice in a month. I was using RR-N-v5.8.3-20170620 on my OnePlus One. Suddenly, one fine day, I was updating my apps from Play Store. Phone got restarted and is stuck on boot screen forever. This happened to me last month also. I tried everything but finally had to wipe data, system everything.

This happened again yesterday. I installed all my apps again (150+) but again same thing happened. Have no TWRP backups so far (was planning to take one, but this happened). Both times it happened while I was updating apps from play store. No idea what app was updating while it restarted.

I tried below:

1) wipe cache, dalvik cache, reboot ........ no help

2) updated rom to RR-N-v5.8.3-20170707, flashed gapps, wipe cache, dalvik cache, reboot ...... no help

3) wiped system, installed RR-N-v5.8.3-20170707, flashed gapps, wipe cache, dalvik cache, reboot ...... no help

4) flashed boot image thru fastboot, reboot ...... no help

5) flashed latest recovery thru fastboot, reboot ...... no help

Anyone, please guide me...!!!
[ONE Android Development] Timmmmaaahh!:
I hope you noticed the post just before yours, those steps are valid in your case as well.

On your step 2: if I understand correctly, you're flashing Gapps on a dirty flash. That is generally speaking a bad idea.

You flash boot images before attempting another recovery, let's say that's the wrong order of things.

Try flashing the ROM without Gapps.
[ONE Android Development] iPusak Gaoq™:
Just wondering how long you have use the phone and within that time have you ever replace the batteries?
[ONE Android Development] gaurav-singh:
Thanks for guiding me here. I tried replacing TWRP with older versions (3 different ones) and also tried flashing ROM without GApps. Still stuck at boot screen. :(

---------- Post added at 09:46 AM ---------- Previous post was at 09:44 AM ----------

I'm using OPO since Oct'2014 (almost 3 years). Never replaced batteries.
[ONE Android Development] iPusak Gaoq™:
Time for you to replace your batteries...trust me those bootloop issues will turn from bad to worst soon....
[ONE Android Development] Timmmmaaahh!:
Well yeah, you omitted a /data wipe. If it's all still there, it's completely untouched. It's exactly that partition that's causing havoc. If you'd reboot to recovery right now and only did a factory reset (wipes /data and caches), it should work fine. If it doesn't, your battery is most likely nearing its EOL.
[ONE Android Development] iPusak Gaoq™:
You have a dying batteries...just replace the batteries and all the problem will go away...i know this cause i was one of the first that have a dying batteries and needed charger to boot normally...disconnect the charger and bootloops will appears again....its not rom problem but it is the batteries....just replace the batteries and you will realize that you have been wasting a lot of time flashing this and flashing that just to figure out it was the batteries all along not the rom....
[ONE Android Development] shyam124:
I read the same that batteries are the problem and i want to use my opo only for some 3 4 months now so i hope battery replacement solves the issue.

Planning for a op5 or iphone 7 plus :confused:

---------- Post added at 01:53 PM ---------- Previous post was at 01:52 PM ----------

I had wiped the data except for the internal storage. thats when it started with the charger connected otherwise it was only bootlooping :D

Already gave the phone for battery replacement to a local vendor as oneplus service centers dont have batteries in stock...hoping for the best :p
[ONE Android Development] Timmmmaaahh!:
iWhat??!

Please report back if it worked and how much it cost, I do wonder how much they ask for things like that in a service center.
[ONE Android Development] :
Enyone experience this battery drain?

I think it's some service of Google Play Service

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Android Development] Feske:
Hi everyone, i have problem with clean installed latest version of RR. I set up everything, and when i open camera app, and switch in video mode, everything is fine, going back to photo mode is fine, but third option, landscape or portrait i think, wont work on me. App crashes and can't open again. Then i need to go to app and clear cash and data, then works again but still have problem with this third option, same thing again.

Recovery Tuga power 3.1.1.-2

Wiped: System, data, cash, dalvik ---> flashed latest RR zip and then without reboot flashed latest gapps from today. (pico version) Flashed succesfully without errors.

If anyone can help i ll appreciate that. Btw, good work and just keep work! Support ++
[ONE Android Development] HannibalLecter:
[MENTION=4841620]Timmmmaaahh[/MENTION]

do you prefer stock RR kernel or zanezam boeffla?

since, you are good at it, could you list a few different findings you got after using both.

thxx a bunch.
[ONE Android Development] Magnum_Enforcer:
Thread cleaned.

This is a development forum. Please treat it as such. If your post isn't relevant to the development of this ROM, move along.

Cheers,

Magnum_Enforcer

FSM
[ONE Android Development] Timmmmaaahh!:
Sure.

Stock RR: easy, safe, stable, great performance, okay battery life.

Boeffla: steep learning curve, insane amount of customizability (also implies easy to break things if you don't know what you're doing), many governors to experiment with, can provide better performance/battery life balance but it's difficult to achieve the "perfect" profile.

I personally prefer the latter as it's been a great learning experience. For newer users looking to try another kernel I'd rather recommend FrancoKernel due to its flash-and-forget nature. [MENTION=4817632]varund7726[/MENTION] there's still plenty of bacon love for you! Please don't abandon us ? ? ?
[ONE Android Development] osrox:
Post shifted to Volte thread.
[ONE Android Development] Isuru cs:
is panorama mode work in this rom without crashing??
[ONE Android Development] loco-cork:
Today's update after flashing goes straight into boot-loop.

Did it as always, 1. Boot into recovery and backup, 2. Flash latest RR, 3. Wipe Dalvik and cache, 4. Reboot ... and it boot-loops ... so I restore the backup ... and it works again. Tried it with and without flashing of GApps.

Never had a boot-loop problem before, and I always flash the latest RR.
[ONE Android Development] malcolmm21:
Works with bacon camera
[ONE Android Development] Bloembol:
Same here! Boot-loop.

Luckily I have a backup, so will have to restore... now....
[ONE Android Development] bdwilk:
[MENTION=5263290]loco-cork[/MENTION] [MENTION=5080028]Bloembol[/MENTION] did either of you guys have a theme applied when trying to update? If so then disable all overlays before dirty flashing. If you don't disable and get a bootloop then go back to TWRP and flash the rescue zip in the sub's folder and reboot.
[ONE Android Development] Bloembol:
No theme. I have substratum itself installed, but as a matter of caution I uninstalled all themes...

Yes, I did have problems in the past with themes.
[ONE Android Development] bdwilk:
OK. Just a thought. Maybe semi-dirty flash. Wipe everything except data and flash ROM and gapps.
[ONE Android Development] iPusak Gaoq™:
i dirty flash latest build and no bootloop issues on my phone....perhaps (just speculating here) it have something to do with Magisk...i'm using latest Magisk v13.2 before dirty flash it and you still using Magisk v12....
[ONE Android Development] loco-cork:
I have no theme engine installed. Latest Magisk and Magisk manager (flashed after last update). One app (HashTag for Instagram) installed since last update.

Don't really want to clean flash as have no time to go through all the settings again.
[ONE Android Development] Bloembol:
Hmmm... Magisk told me I had an old version, 13.1.

I updated to version 13.3 and flashed the latest rom again. Again stuck in a boot loop... :(

Anyone any idea?
[ONE Android Development] Timmmmaaahh!:
I have an idea on the latest bootloops; they could be related to a change in Magisk version as it has virtually no backwards compatibility. Any present modules may be killed during a dirty flash, causing havoc to the system. Pre-flashing this can be prevented by uninstalling all modules first. Post-flashing this can be fixed by flashing the Magisk uninstaller found in the official Magisk section of XDA. I clean flashed, not a single problem here. [MENTION=7478074]bdwilk[/MENTION] I finally got rid of my corrupted Substratum situation. I suspect it was related to either a corrupt backup of a system component I restored with TiBu (most likely), the iOS animation style flash (still a proper contender) or a particular Uber iteration of ZZ's Boeffla kernel. I'll find out more tomorrow.
[ONE Android Development] loco-cork:
Ok. Semi-dirty flash (wiping only system) kind of worked. Phone booted and all, but lots of stuff was broken (like Google services etc.). But at least now I know that the problem lies within the system part. So when I have a chance (more time) I'll do the Titanium Backup, clean install and restore from TB then. For now I'm restoring with nandroid backup. Thanks for all the suggestions.
[ONE Android Development] ryh2013:
Look here

https://xdaforums.com/oneplus-one/development/rom-resurrection-remix-t3507102/post72860093
[ONE Android Development] Timmmmaaahh!:
When you flash the ROM again, you're actually downgrading Magisk back to 13.1. That's because Magisk 13.1 is included in the RR zip. When you made backups, I'd go for a completely clean flash in your case.