yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] cs_official:
I've tried getting the problem in the Logcat. Please see if it helps or do I need to provide another Logcat.
[ONE Android Development] g-member:
Why isn't the changelog up to date?

Before i take the time to dirty flash it i wanna know if the changes are usefull for me.
[ONE Android Development] BadWolfTronic:
Hi all, I'm with the last build, clean flashed, I'm facing a strange issue, when the phone is charging, it results always active in battery stats, even if the screen is off, and the charging process is so slow that I have to keep the phone with the screen off otherwise it is not able to charge. I am pretty sure that this is not the slow charging setting complained by some user.
[ONE Android Development] BadWolfTronic:
Here is a logcat of the moment when I plug the charger.
[ONE Android Development] Timmmmaaahh!:
That is, without any doubt, completely unrelated to the ROM. You're either experiencing hardware failure (most likely cause would be the charging cable) or something messed up pretty good in the kernel. Provide some context on your kernel and hardware situation.

What you say is invalid and you omitted to use the magic word – tsk tsk. Updates are always useful* for everyone. The 20170527 changelog is available in this thread, be a big boy find it on your own.

Hah, this one is funny:

"W/SearchServiceClient( 4402): Starting with NO_SESSION handoverId is deprecated. Just don't. You will break."

I don't know what it means but it looks kinda threatening.. scary, lol. The game has all needed permissions, right?

I'm a little confused as to why we're seeing AppOps entries in your log. This was introduced in Android 4.3 but removed again in 4.4.2! Maybe it's just a naming scheme for permission errors, which is possibly bringing us closer to the root cause because there seems to be a uid assignment mistake. Why that happens is still unclear to me.
[ONE Android Development] BadWolfTronic:
Hi, thank you for the response. The kernel is the stock one, the charger and cable are aukey and I have been using them for about one year without issues. However I'll try other chargers to see if the strange behavior persists and I'll provide updates. Thanks again!
[ONE Android Development] cs_official:
Scary? I'd say that's what they meant when they said #NeverSettle ?

On a serious note, the app doesn't request for any permissions at all. As for AppOps entries even I was confused. I guess this'll remain a mystery after all.
[ONE Android Development] Timmmmaaahh!:
Well, I just installed the game (you know, for academic purposes) and it ran smoothly. I got to make some penalties and obtained a gold player: obgeche, ogebche, obcheesy, whatever (this really isn't my thing). Anyway, "remain a mystery" doesn't exist in my book so we're getting to the bottom of this and everyone gets a free ride on the learning train, yay!

Attached you'll find a logcat of me making some passes. Check out those "InitPlayer playerIndex" lines, fine passes indeed! I had to force close the game because it didn't allow me to exit the tutorial normally. I admit, this felt good:

06-01 12:21:36.283 I/ActivityManager( 1602): Force stopping com.ea.gp.fifamobile appid=10199 user=0: from pid 3292
06-01 12:21:36.294 I/ActivityManager( 1602): Killing 32228:com.ea.gp.fifamobile/u0a199 (adj 0): stop com.ea.gp.fifamobile
06-01 12:21:36.295 D/ActivityManager( 1602): cleanUpApplicationRecord -- 32228
06-01 12:21:36.303 W/ActivityManager( 1602): Force removing ActivityRecord{f1ec234 u0 com.ea.gp.fifamobile/.FifaMainActivity t1618}: app died, no saved state

Notice how in my setup it's stating "E/ActivityManager" while yours is using that ratchet "W/AppOps" prefix for java output. This confirms my earlier hunch and makes me question the cleanliness of your flashing procedure. I know this sounds like I'm talking dirty to you but it really isn't, lol.

Point is, where your setup mistaken's uid 10102 for 10095, it has this exact prefix. There is no such thing on my end.

SO. *giving you a cold strict look* What have you been doing, mister? I probably don't need to know :p

What you need to do is fully wipe your system, data and cache partitions and start over with a LOS flash in between, that'll solve a great deal of issues (to be) for you. All clean, no restoring /data stuff. Create and restore backups with Titanium (no system stuff except for some basics like call logs and messages) or rely on Google restore. You know the drill ;)
[ONE Android Development] red5pade:
A page or 2 back I said my phone turned off and wouldn't turn on and what not. Weirdly other ROMs worked but none of RR would including my backup. I decided to wipe internal memory and try flashing RR and that worked. I'll try and get logs if it happens again. Anyone know why this may have happened? I've never had an issue like that
[ONE Android Development] Kitsparks:
Does anyone know how to fix the battery drain? I have the 5.8.3 RR and I seem to be getting less than stellar battery life on it . I'm pretty new to all of this so if anyone could steer me in the right direction I would really appreciate it!
[ONE Android Development] Kondra007:
Could anyone please extrace com.android.documentsui.DocumentsApplication from the ROM and send me it? I accidentally deleted it and don't want to reflash the ROM and change all those settings again.
[ONE Android Development] Shadowghoster:
You don't need to change any settings again if you dirty flash.
[ONE Android Development] lbaty:
TLDR: did the cleanest reinstall I could imagine; still got a random reboot. Suspect one of my configuration steps or hardware error.

Hey [MENTION=4841620]Timmmmaaahh[/MENTION], probably way over the top, but last night I did the following ...

1) return to stock (following this guide)

2) unlocked bootloader & installed TWRP Tuga 3.1.1-0 (following this guide)

3) booted CyanogenOS

4) in recovery I wiped system, data, cache and dalvik then flashed Lineage OS 20170529 & Open Gapps ARM 7.1 Nano 20170531

5) booted Lineage OS (skipped account, etc)

6) in recovery I did factory reset then flashed RR 20170527 & Open Gapps ARM 7.1 Nano 20170531

7) additionally I flashed: PMSCameraNextModv7, boot animation, camera sound, custom hosts & bloat remover.

8) boot RR and sign in with google account, use google wizard to restore all previously installed apps. Enable privacy guard by default for all apps

9) set lock screen pin & encrypt device

10) install V4A via Magisk as per post 3333

11) notable apps include: AccuBattery, Greenify, Naptime, AdAway, Viper4Android (these are the only low-level ones that I think could possibly cause issues)

Unfortunately despite the above this morning I got a new random reboot.

kmsg attached - any ideas?

View attachment 4168531
[ONE Android Development] red5pade:
I personally use lightning kernel los version. Some people like the OOS version with OOS blobs but I couldn't ever figure out how to flash without breaking my camera.

Just flash the lightning kernel v38. You'll have to reflash it after every update... But that's it. I would go to bed with maybe 20% and wakeup with maybe 18%
[ONE Android Development] phillibl:
After you flash RR and gapps just stop and test it for a day. If it's okay flash/mod one thing and test it for a day. Repeat until you add all your mods/apps.
[ONE Android Development] Kitsparks:
No way that's awesome! I'm going to do that now thanks!
[ONE Android Development] lbaty:
Thanks [MENTION=4597400]phillibl[/MENTION] that makes sense. I'll give it a go.
[ONE Android Development] bdwilk:
This is part of your problem. Always wipe at least system and data before flashing another ROM.
[ONE Android Development] lbaty:
Thanks [MENTION=7478074]bdwilk[/MENTION], normally I would.

On this I was following Timmmmaaahh's instruction (perhaps too literally), he said: "flash official LOS (latest nightly), boot it once, set up the basics (skip accounts), wipe it again (just factory reset this time) and flash RR again".

To try phillibl's suggestion I have today wiped system, data, cache and dalvik before flashing RR & GAPPS only (I haven't flashed any other mods).

This also takes into account your suggestion so I will report back in a day or two.
[ONE Android Development] HannibalLecter:
This has to be the cleanest install ever.

Great job both times, doing it and listing it. :)

where to get this? custom hosts & bloat remover.

why do you need custom hosts when you have adaway installed? I thought when you flash custom hosts, you dont need adaway.
[ONE Android Development] pranavsultania:
I have the same problem as you do. This happened after the 2705 build. Before that everything was fine. The battery life has improved significantly though.

Also, I've noticed that the phone keeps dropping the data network about once a day. The only fix is to reboot the device.
[ONE Android Development] Timmmmaaahh!:
Actually, [MENTION=7478074]bdwilk[/MENTION], that isn't true. At least according to moderator [MENTION=3946657]xanthrax[/MENTION] and the official TWRP team, see his post on that here:

I just dug like half an hour to retrieve that post, lol. Who are we to question these methods that are dictated by the people that developed them in the first place?

It actually makes sense too. I still believe wiping /system can still be useful if things get awry, it's just not required on every clean flash or even a ROM switch.

You did well, [MENTION=4921949]lbaty[/MENTION]. There's just one step I've got a question about. In step 2 you mention "unlocked bootloader", does that mean you actually locked it again? If so, never do that again, that's a downright OPO killer. You can read my personal experience with this here (123 posts of horror, enjoy). I'm still unsure about Viper though, that might still be your culprit. As I recall there were a number of microphone issues in your logs as well. Could you send me a PM with your Viper settings and program version? Just go to Menu > Save Effect Profile and send me that file. I'll then import it and see if it happens on my device as well.

Besides that, there's a number of factors in your case that increase the risk of an unstable device. I'm a little surprised you're 'only' getting occasional reboots so far. Several mods + Privacy guard + Encryption + Viper... It's going to be a tough cookie to pinpoint where exactly the problem lies, that's why I suggest we communicate via PM only until we got it sorted, then report back here with the outcome.
[ONE Android Development] uudruid74:
I recommend Viper instead :)

---------- Post added at 09:31 AM ---------- Previous post was at 09:25 AM ----------

A few root apps still need busybox and the Magisk built in one seems to cause Magisk to randomly lose root (requiring a reboot to fix). I would turn off thw built in one and then flash the busybox module for Magisk, but then, use root to enter the module directory under Magisk and change the folder name from bin to xbin. I don't know why the module author chose bin, but many apps are hard coded to look in xbin.

---------- Post added at 09:36 AM ---------- Previous post was at 09:31 AM ----------

Steps 3 and 5 are totally unnecessary. Don't install all those OS's and boot them. Waste of time.

If I were looking for a culprit, I'd guess the camera mod.
[ONE Android Development] Timmmmaaahh!:
Yeah, I forgot to ask [MENTION=4921949]lbaty[/MENTION], what is that anyway?
[ONE Android Development] uudruid74:
He posted a link. Its some sort of camera HAL tweaker. By far the most low level and potentially conflicting bit on the long list
[ONE Android Development] Timmmmaaahh!:
He did? I fail to see it... If you're referring to the CameraNextMod, I'm using that one as well for a long time now, no reboots on my end, it performs exquisitely. Of course, I'm not combining it with encryption and such. I was talking about his "camera sound", sounds a lot more dodgy...
[ONE Android Development] uudruid74:
Should be just a replacement sound file
[ONE Android Development] uudruid74:
Here is a screenshot of Accubattery for this ROM, the battery is the original and running about 80%. However, projected SOT is nearly as high as my 3T, and standby time is nearly double. The 3T gets 112 hours while this ROM is getting over 186 hours standby (over a week!). This is using Lightning kernel v56 (for the OOS hybrid blobs) and Greenify. All notifications work fine (better than my 3T ROM).
[ONE Android Development] Timmmmaaahh!:
Partly recorded during your nighttime? In that case those prospects wouldn't be so abnormal. My stats include 140 hours of testing and those are actually a combination of stock kernel and ZZ-Boeffla (see below). 43 hours, not too bad either I'd say! That's why I don't understand why some people are still complaining about drain or charging, this baby is still running pretty sweet! Oh and I should add that I sometimes indulge in some heavy gaming (Sandstorm, poorly coded, heats up way too fast, but I'm hooked!), that does impact my stats in a very negative way :p
[ONE Android Development] lbaty:
Thanks [MENTION=7466743]HannibalLecter[/MENTION], it certainly was time consuming!

You're right, my flashable custom hosts is pointless when AdAway is working; it's an old-ish version of the hosts file taken from Adaway that I started flashing while I was having problems with Root & Adaway. View attachment 4168946

Custom bloat remover is my own adaption of someone else's script that removes apps like Gello, Calendar, email, Trebuchet, etc. View attachment 4168947

I didn't purposefully lock the bootloader; Not sure if this re-locks when one returns an OPO to stock? I guess I was just blindly following a guide to install TWRP.

Wow, that's quite a read. Shame your RMA experience was so poor. Thank goodness for Indest, Reboot101 & others to keep your faith in OPO!

Thanks [MENTION=4841620]Timmmmaaahh[/MENTION] I'll message you tomorrow.

Thanks [MENTION=5880917]uudruid74[/MENTION], I don't really know what I'm doing (that's surely clear).

I think I read somewhere that I needed boot LOS after flashing and thought I should do the same with COS13 (it's quicker to boot each once than to restart the whole process!).

There are 2 camera components; neither dodgy ...

1) CameraNextMod based on [MENTION=4841620]Timmmmaaahh[/MENTION]'s recommendation in the famous post 3333. Tried it once, now it's my favourite camera.

2) flashable camera sound is nothing more than replacing /system/media/audio/ui/camera_click.ogg with a sound of my preference View attachment 4168948
[ONE Android Development] Timmmmaaahh!:
The bootloader lock is usually included in batch files and automated tools, that's why it's better to do these things manually.

Yeah, luckily it was at the time OnePlus finally got their customer service somewhat together so I did get a replacement eventually, it's been much worse in the very beginning. Still took me over two months of back and forth mailing (40+ messages on top of the thread in a single ticket! I gave it a bad rating :p). Funny enough I performed this mess-up the second day I had the device! It ran well for exactly one single day :)

Oh okay, I figured it was to disable the sound, which would've been silly because there's a switch for that in settings. Cool beans :cool:

[MENTION=5880917]uudruid74[/MENTION] [MENTION=4921949]lbaty[/MENTION] It actually is important to fully boot the OS as it finalizes some things in the setup. I'm not sure if this is still needed today but I've had users complain before about driver issues that skipped this step. Besides, it only takes a few minutes, causes no harm, and it only has to be performed once. This step excludes all doubt. I'll do the same with Android Oreo before flashing RR O ;)
[ONE Android Development] uudruid74:
Reduce your process. The only ROM you need to flash is the one you are attempting to install. Look, you have 5 areas to deal with.

Your system partition where the ROM goes, and it overwrites everything on there (even formatting it is pointless, although some people say to wipe it but that is just to stop tricky installers from saving stuff from addon.d and reinstalling it). Each time you flash to system, it overwrites the old.

Your boot partition holds the kernel. This is normally written and replaced when flashing a ROM.

Your recovery partition is TWRP.

Your data holds app data and internal storage.

The rest is firmware. Usually only stock ROMs install this and that is why some people say to install stock or say to install latest cyanogen ... to set the firmware.

Once the right firmware is installed, you don't have to install it again, and you can get ZIPs of just the firmware. There is no reason to install all these different OSs and boot them and all that. Your poor phone!

Clean Flash is backup data, wipe data, flash ROM, flash gapps, flash root/mods, reboot and restore data.

Dirty flash you don't wipe data. You might wipe dalvik cache if you updated android versions.

Keep It Simple!

---------- Post added at 02:37 PM ---------- Previous post was at 02:26 PM ----------

Silliest thing I ever heard. No reason for any other OS to touch the system. What drivers do you speak of? Android's driver model is weird, but if you clean flash there isn't anything left of the old OS anyway. Think about it.

Boot the OS you are installing, none other. You might want to boot before installing Magisk and mods, but load one OS and boot it to replace it? Nonsense.
[ONE Android Development] Timmmmaaahh!:
LOS includes more than what LOS-based ROMs provide such as the recommended baseband. This eliminates any leftovers from other projects and updates outdated elements from old systems like COS. I did not invent this practice, I was merely instructed by devs myself to do so. You're the first person I encounter here that denies this. I'm not saying you're wrong but I'd like to see it confirmed by a dev first.
[ONE Android Development] SathwikNVS:
I just installed the latest build of RR os on oneplus one and also open-gapps mini. But after booting up, while setting up, I cannot go past the "set up as a fresh device" screen... when i press on "set as fresh device" it simply says "setup wizard stopped working" and shows the close app button, which on pressing leads back to the first page of language selection. Help me asap.
[ONE Android Development] bdwilk:
Use beans gapps.

https://xdaforums.com/android/software/gapps-dynamic-gapps-t3487192/post69295660
[ONE Android Development] Cholerabob:
Stop installing stuff and run RR alone for a while to see if it crashes, after that install apps ONE by ONE with time in between to see WHO makes you phone crash, all that junk on top of another may be the problem... As always IMHO
[ONE Android Development] SathwikNVS:
well, thanks for the fast reply. :D But what i did was this ---As soon as it shows the app crashed message, i immediately tried to swipe down the notification drawer (this was hard, took a few attempts, but worked). then i switched on the wifi there and then came back and hit the "setup as a fresh device" button. it then asked me to connect to the wifi since the wifi was now ON and thereafter it worked just fine---. :good:

Now all i need to know is, when will this be fixed? Is it a temporary bug or will it persist even while updating to future builds?
[ONE Android Development] vivalala:
Deleted.
[ONE Android Development] bdwilk:
I think you're in the wrong thread. As far as I know OnePlus One doesn't have a fingerprint button. At least mine doesn't have one.

What date is your open gapps?
[ONE Android Development] amoutie:
I got a weird situation: my OPO's stuck in RR logo., or any ROM's logo. I mean, I was having a call, I moved the phone from the ear and black screen. No way to turn the screen off. I forced the phone to shut down pressing the button. It rebooted and then stucked on RR logo. I wiped cache and still stucked. I tried a clean install of RR, installed LOS and again, stucked on LOS logo. I tried even an old backup of RR (an april one) and still, stucked at ROM's logo... I need my phone, and it was working pretty well until this!

I was on TWRP 3.1.0.5 by Tuga and RR 27/05 version. Now I'm on same TWRP but I don't know what version of RR. I may try to fastboot stock ROM and install RR again... is it right?

Edit: I tried to flash stock 13.1.2 and it booted correctly. I'll try to flash RR again.

Edit 2: Flashing RR after a long way from Stock to RR appears to have worked. I lost all my datas, but better than nothing. Now I'm facing "just" slow charging... almost 2.5h to charge from 33% to 100... What can I do?
[ONE Android Development] vivalala:
I'm sorry, I thought it is OP2 thread.
[ONE Android Development] gabe13:
slow charging? I know that stock rr kernel has charging rate settings (or at least it had when I've used it, I'm on LK now)

get kernel adiutor mod and check under power section if there is any charging rates, if there are just set them at some high value (mine are maxed)

if you already have those set up get Ampere from playstore and check your charger and cable
[ONE Android Development] lbaty:
[MENTION=5880917]uudruid74[/MENTION] thanks for taking the time to explain all of the partitions and how they work.

The process I followed was not normal for me ... I guess I went over the top due to frustration.

[MENTION=4120922]Cholerabob[/MENTION], this sounds like good advice but my reboots only occurred as frequently as twice a day -or- as infrequently as every 2nd day (usually at the most inconvenient time!).

I would have to run RR with no apps installed for perhaps 3 days, then test addition of a new app every subsequent 3 days? (going through each of my 60 apps would take ~6 months!)

Or are you referring to non-play store apps? (my apps are all from play store except AdAway, Viper4Android, MiXplorer & MagiskManager).

Out of curiosity, how many apps do you have installed? Is 60 considered a lot of additions? (excluding apps from the Rom & Gapps)
[ONE Android Development] bebybee:
Im newbie in here, im from cm 12

May i through flash this rom ?

Sorry, cmiiw
[ONE Android Development] HannibalLecter:
God I just read your experience with that kernel. Cannot imagine what you would have been through on the second day of buying the device.

I am not as experienced or knowledgable as you but I have been flashing custom ROMs on my i9100, n700, bacon, Xiaomi mi3.

Never ran into such a deep issue.

I have restored stock cm11 on my one plus one running fastboot commands manually one by one (the modem, userdata_64 etc ones)

from here

https://xdaforums.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471

these steps

fastboot flash modem NON-HLOS.bin

fastboot flash sbl1 sbl1.mbn

fastboot flash dbi sdi.mbn

fastboot flash aboot emmc_appsboot.mbn

fastboot flash rpm rpm.mbn

fastboot flash tz tz.mbn

fastboot flash LOGO logo.bin

fastboot flash oppostanvbk static_nvbk.bin

fastboot flash boot boot.img

fastboot flash cache cache.img

fastboot flash recovery recovery.img

fastboot flash system system.img

fastboot flash userdata userdata_64G.img

Thank god I never used a toolkit or shortcut to do that automatically else I would have ended up with a locked bootloader myself.

ALso, I never go crazy with flashing all the different mods. I usually stay on the stock kernel and rarely flash a custom kernel too.

Used to flash on Samasung galaxy s2 Dorimanx and Siyah (oh that developer, i forgot the name, was a genius. he moved on to s3 and then I lost him) Kernel.

I am scared after reading your ordeal.

First I would Not have even known that forum. I only have the stamina to follow xda (feel more comfortable on it with many users)

Second, waiting for so many days for official oneplus guys to respond.

i am scared of flashing now.

I willl never even open blisspop thread now. was that kernel related to blisspop rom or it was an entirely diff kernel?
[ONE Android Development] uudruid74:
An app should not be able to reboot the phone. Install RR and root, but no other kernels or low level stuff. Make sure you are on known good firmware. Then install your apps.

If it reboots, see if you can get a lastlog