[ONE Android Development] uudruid74:
OPPO? You mean OPO? What hardware problems? I haven't had at all that I would attribute to a hardware problem.

Yes, a port. All ports are done from source! So I don't know what you mean by that comment. This is the Temasek ROM, but not by Temasek. Now it may be a recompile and repackaging as I don't know if any changes had to be done from Temasek's sources to get it running on the OnePlus, but it's not the original Temasek ROM. It's a port of Temasek to the OnePlus. And Temasek is in-turn a fork of Cyanogen which is a fork of AOSP. An example of the problem is the issue with the OTA - Katinez finally forked it (THANK YOU!) because upstream wasn't fixing it and it was a stupidly simple bug. But, we're pretty far down the development chain. Thus, its nearly impossible to pin down if bugs are AOSP, Cyanogen, Temasek, or the OnePlus port. And then Temasek itself is borrowing from other source trees, so bugs could be introduced from those sources as well. There is no way to tell who is responsible for a particular quirk. The only logical thing to do is to report here and let them slowly get pushed back up the chain as each person checks off and says, "Nope, that code came from here" and hands it off. When whoever is reponsible for the code in question is ready to look at it, they'll ask for logs.

The original black screen problems had to do with how you had profiles set up or something. I'm not having black screen problems at the moment, so we can't fix that, but I also have profiles turned off (although if someone is still having those issues with 15.6 and has profile on, I'll turn them on to see if it causes the bug!). Do you use profiles to turn off your screen lock? Maybe thats why you never saw the black screen bug. As I said, I believe the offending code changes were reverted. You assume that because you don't see the problem, that it doesn't exist, or that they are "monjo ninja tricks". Maybe we should send you a ROM Settings backup to see if you can reproduce the problem? That would be fairly easy ... back up yours, pull mine off my drop box, restore, test. The old "works for me" doesn't hold water. If a user CAN screw it up, then its buggy.

The other issues I mentioned, I only mentioned, not reporting them yet - but they were examples in our discussion. I ended up changing from PIN to Gesture on my lock screen and then changed it back. This has made the problem of not being able to type the PIN go away. Its likely still a bug - it should never exhibit that behavior, but I think its going to be too tough to track down. Luckily, I had face recognition on or I would have had some issues! The trusted "location" still isn't working (not a huge deal for me, but likely a bug). Cleaning cache partition wouldn't fix the clock, but going into AppInfo and wiping all its data has gotten my alarm clock working. Jury is still out on who is at fault with MTP but I'm not done testing.

Although ... [MENTION=3814731]katinatez[/MENTION] if you're listening, the clean full device wipe has made the weird issue with BlueTooth and the media queue getting messed up unreproducible.

Anyone know why my OnePlus register as USB keyboard and mouse devices under Linux? MTP and USB networking and all that work (although the same problems with the network selection on USB are still there). Here is /dev/input/by-id/usb-OnePlus*

usb-OnePlus_A0001_4f2341cf-if01-event-kbd

usb-OnePlus_A0001_4f2341cf-if02-event-mouse

usb-OnePlus_A0001_4f2341cf-if02-mouse​

Weird?

As to a PM to you when I have issues & logs, try this ... copy a couple GB of data over MTP while simultaneously playing an MP3, and hmm ... turn on something to chew through some of your CPU cycles. I use Viper set to high sound quality with a lot of stuff turned on and it can chew up a lot of CPU (benchmarks run about half than when I'm not playing music through Viper). See if your MTP transfers start dying. I'm not convinced if the problems are random, if its related to buffer overflows from the CPU being too busy (which shouldn't cause errors in and of itself unless there is a bug in how it handles the buffering), or if its just me. Its quite possible that no one has recently tried transfering a couple GB of data over MTP recently, or they didn't do it with a busy CPU? It could just be my laptop's funky USB support. So, my next step it to test on another PC, but thats the next issue I'm looking at. If I can reliably reproduce it on another machine I'll go for logs. If no one can reproduce it, then logs are kinda pointless.

So far this is a forum, where bugs and problems should be discussed to see who else has similar issues and find common work-arounds. There hasn't been an official bug-reporting method that I know of. So, don't get too bent out of shape when people are looking to see who else is experiencing similar problems.

---------- Post added at 10:40 PM ---------- Previous post was at 10:28 PM ----------

What specifically is getting the axe?

When people test this, please report back. I'll likely be a late adopter for awhile while things stabilize.