yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] rriegner:
The touchscreen gesture to open the camera doesn't open the camera for me, it just wakes the phone to the lock screen.

Also, any chance you could include (optical) cursor navigation arrows on the nav bar instead of keyboard switcher button?
[OnePlus 3 & 3T Cross Device Development] uudruid74:
But ... LTE IS 4G!

---------- Post added at 05:41 AM ---------- Previous post was at 05:33 AM ----------

It's because OOS lies about signal strength. There is setting for it in ... build.prop maybe? No ... one of the files has it. I forget.
[OnePlus 3 & 3T Cross Device Development] joshuous:
Works fine for me. I'll think about the suggestion
[OnePlus 3 & 3T Cross Device Development] kipue:
Eh. Delete my post, no point polluting the thread with a non issue that is not the rom's fault :p
[OnePlus 3 & 3T Cross Device Development] uudruid74:
Nougat Navbar is customizable. Google it.
[OnePlus 3 & 3T Cross Device Development] rriegner:
I uninstalled all other camera apps and it worked fine, but when I installed another camera app, it no longer works. Seems like the dialog to select which app to use never opens, so nothing happens but waking.

I managed to get it working with Tasker and two other apps, but I was just suggesting to have it done at the system level instead of requiring three apps constantly running.
[OnePlus 3 & 3T Cross Device Development] uudruid74:
Not sure why you need three apps. The Navbar can be modified to run other apps
[OnePlus 3 & 3T Cross Device Development] rriegner:
My goal was to have arrows appear when I'm entering text, and then go away when I'm not. That required the Custom Nav Bar app to write the changes any time, a Tasker plugin app to watch for active text input boxes (couldn't find a way to detect on-screen keyboard), and Tasker to interface those two apps together.

If you know of another simpler way to accomplish my goal, PM me so we keep this thread from straying off-topic.
[OnePlus 3 & 3T Cross Device Development] joshuous:
Thank you very much for your generosity Mr Ettinghausen :)
[OnePlus 3 & 3T Cross Device Development] greatxgaming:
Zenith Kernel vs Render kernel? which gives better battery life?
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Render tends to be more peformant, stick with Render Zenith and if you do not like it try out Render. It really is a personal opinion.
[OnePlus 3 & 3T Cross Device Development] sawari:
Switch to this ROM after testing many ROM, finally I got what I want, nearly stock look and feel with minor configuration options and with Substratum working. Thank.

Managed to solve the problem of green camera by lowering the DPI, now 400.
[OnePlus 3 & 3T Cross Device Development] joshuous:
Hey glad to hear that :)

And you have an interesting finding there
[OnePlus 3 & 3T Cross Device Development] mady51:
Wowowow
[OnePlus 3 & 3T Cross Device Development] Navi44:
Happens when u leave your screen on for long times ?
[OnePlus 3 & 3T Cross Device Development] mady51:
:D i was sleeping during that time
[OnePlus 3 & 3T Cross Device Development] lpsld:
Battery drain /hour is lower then on the latest pa build.

Also this is an insane camera quality compared to all roms! :)
[OnePlus 3 & 3T Cross Device Development] AndreiVolk:
Hi Josh, from like one week my phone has become laggy and i have hot reboots. When it reboots the phon gets hit. When i'm in some app i have to press back or home button a lot of times to go back to home screen and the lancher crashes sometimes. Also swipe left for google now doesn't work good. I have to swipe a lot of times and it's laggy and it's crashing too. I tried with nova launcher too but nothing changed, it behaves the same.

I atteched a log made with matlog and in the log level i selected only the errors.

Let me know if it's detailed enough or if you need something else.

I'm on the latest build with ob10 firmware beans gapps and latest magisk.
[OnePlus 3 & 3T Cross Device Development] Morphicsn0w:
Teaser

Just a teaser for you all of the new branding coming to 4.0. :)

[IMG="Logo"]http://i.imgur.com/ugHyLXa.png[/IMG]
[OnePlus 3 & 3T Cross Device Development] Generalboii:
ooo looks cool!
[OnePlus 3 & 3T Cross Device Development] omar77w:
So I noticed the app only crashes when it's given the camera permission. I pulled this logcat when both the microphone and camera permissions are already given--the app crashes immediately after I open it.

I also pulled this logcat when I open the app with the camera permission not given yet--the app opens fine and asks me to grant it camera, but as soon as I doso, it crashes.

Hope this helps!
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Hey, have you tried a reboot? Android tends to gets unstable when it is turned on too long. Do you have any possible 'mods' installed?
[OnePlus 3 & 3T Cross Device Development] AndreiVolk:
Yes i tried to reboot but doesn't change nothing. The phone behaves the same after a reboot too.

No mods installed. Only enabled magisk hide and systemless hosts in magisk.
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Can you check your CPU frequencies, how do they behave? Does your phone idle properly?

If not so then wipe dalvik and cache does it solve it? If not so, take a backup of system then wipe it, flash Vertex, flash Gapps, kernel (optional), root, any other mods. Let me know if worked!
[OnePlus 3 & 3T Cross Device Development] uudruid74:
If it gets unstable, there is a bug that needs to be found and fixed. Rebooting doesn't solve problems, it hides them.
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Well you see, I can have an issue that noone else on the planet has. I want to go through the basics first before stressing out the dev.
[OnePlus 3 & 3T Cross Device Development] uudruid74:
I didn't say you shouldn't attempt a reboot to see what it does! Debugging is fine.

I just take offense to the statement that Android can't run for extended periods or that there is any such thing as being turned on "too long", and the Microsoft culture that we fix things by rebooting them or the dreaded, "Turn the device off, wait 20 seconds, and turn it back on again."
[OnePlus 3 & 3T Cross Device Development] omar77w:
I've found a tiny 'typo' in the warning message when you attempt to power off the device. It warns that it will "reboot" when it obviously only powers off. :)
[OnePlus 3 & 3T Cross Device Development] uudruid74:
Why are you playing with it if you don't know what you are doing? Leave it alone!

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

How is camera any different?
[OnePlus 3 & 3T Cross Device Development] omar77w:
I second this. I captured these two shots only 10mins apart. The first one was shot by Vertex, the second by Paranoid. Both in auto, no HDR. Vertex had significantly better colors and dynamic range!

https://m.imgur.com/a/PkW3M
[OnePlus 3 & 3T Cross Device Development] joshuous:
Don't set this to zero unless you want to disable touch boost completely (please don't)

I've got a build of the kernel with working DCI-P3 according to my testers
[OnePlus 3 & 3T Cross Device Development] joshuous:
Thanks man. Just gotta say though that I'm not a cam expert and did not do much besides using OOS' default blobs.
[OnePlus 3 & 3T Cross Device Development] joshuous:
Thanks for the logs. I really appreciate it when users post logs along with reports (although I prefer it posted on hastebin in general). For your logs there's nothing I can find that helps here.

A note to everyone: if you have an app crash, search the logs for the word "exception" or "Java" and post that section of the logs. This is what I always look for first when a user submits logs.
[OnePlus 3 & 3T Cross Device Development] FloGatt:
The latest (test) version or a not yet published version?
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Test version :)
[OnePlus 3 & 3T Cross Device Development] kingkae:
Is there any way of reducing the amount of heat produced during use on this ROM? I love the smoothness so damn much but sometimes it gets too hot. I've tried playing with Vox Populi and using that testing battery profile in earlier posts, but it still feels hot compared to say, sultan's ROM. I don't know if that would involve more under locking or not. Not to talk bad on this ROM or anything though!!

Thank you!!
[OnePlus 3 & 3T Cross Device Development] mady51:
R u serious? There is no heating issue in this rom. What usage did u have while u observe heating
[OnePlus 3 & 3T Cross Device Development] kingkae:
There's no need to get defensive.

It's just light usage, using Instagram and Spotify and such. It's not that big a problem for me, just an observation and wanted to see what the dev thought of it ?
[OnePlus 3 & 3T Cross Device Development] AndreiVolk:
And for the hot reboots you need ramoops right ?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I use this rom and have never had a heating issue. Really never really had a heating issue with the OP3 on any rom. Except for using GPS too long. So that makes me wonder what is different about your setup.

Did you changes ANY kernel settings from default values?

Did you clean flash the rom?

How is your batterylife?

If you are rooted, can you open a terminal on your phone and run:

su

top

and tell me what process is at the very top? You may have to hit Volume Down + C to make top exit. Then you can scroll up to view the findings.

Should be able to see exactly what the cause is. Sounds to me like you have a process stuck in memory making the freqs run high all the time. Need more information really to be helpful.
[OnePlus 3 & 3T Cross Device Development] uudruid74:
Well, this doesn't answer the question at all.

This ROM supports HAL1 normally, but can support HAL3. HAL1 should look just like OOS camera and all ROMs that use OOS camera with the OOS HAL1. HAL3 should no different than any other custom ROM, except AOSPA. AOSPA has it's own customized HAL. So, comparing to AOSPA doesn't compare to anything other than their own custom HAL and no generalizations can be made.

Further, you snapped a pic under flourescent light which flickers 60 times per second. It looks like one picture was done with the light on the down-side and the second one with it on the bright side.

Now to complicate things further, I use Snapdragon camera. There are two, one for OOS and one for HAL3. I use the latter because it's more stable with a UI from CameraNext. For me, it's noticeably better than the OOS camera on both front and back cameras.

These two were taken with PAEX, one using HAL1 and OOS Camera2, and the other using Sultan's SnapDragon Camera for LOS. Can you see the difference? The pics were taken seconds apart without moving the camera under natural light, and I picked a day when I need a shave on purpose ... something to zoom on :)
[OnePlus 3 & 3T Cross Device Development] kingkae:
Hi there,

I was using Vox Populi values that were posted a few pages back for a battery profile, but that was 4 days ago and I've been using default values since. Nothing else changed.

Completely clean flashed.

Battery life is usually 12 hours, with a max of 3.5h SOT regardless of conditions. Always predicted only 7h left at 100%, when I check it in the morning.

The highest processes (they were alternating between being at the top) were surfaceflinger and system_server.
[OnePlus 3 & 3T Cross Device Development] omar77w:
I really wasn't comparing the technicalities of both cameras and they do not matter to me at all. I was only laying down my experience. I easily prefer this camera over Paranoid. Personal preference. You can try both ROMs and see for yourself.

And those were not fluorescent lights. Those were natural sun rays reflecting on opaque glass--totally natural lighting. This was at noon :)
[OnePlus 3 & 3T Cross Device Development] uudruid74:
That's what I wanted to know! Thanks!
[OnePlus 3 & 3T Cross Device Development] kungfury:
just wanted to know if 60fps has been fixed in the new update?
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Nope, it's a hard one, we may or may not see a fix soon.
[OnePlus 3 & 3T Cross Device Development] 5nickers:
What is the problem? Is the fps not stable?
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Yea, its like 43fps. It's not only Vertex.. Pretty much all roms.
[OnePlus 3 & 3T Cross Device Development] calvinistmac:
It has to do with the proprietary nature of the camera drivers. It's not going to be happening anytime soon, that's for sure.
[OnePlus 3 & 3T Cross Device Development] K-Paradise:
This ROM cured my flashing addiction. It's absolutely the best I've tried for the OP3 thus far. Supersmooth, great battery life while still having all the features needed. Great job joshuous, thank you very much for all your hard work; just made a little donation to show my appreciation. Keep it up! :)
[OnePlus 3 & 3T Cross Device Development] joshuous:
Thank you so much man! Your gift means a lot, and your words even more to encourage me :)
[OnePlus 3 & 3T Cross Device Development] azzio4675:
[MENTION=6745491]joshuous[/MENTION] do you create vertexos for oneplus 5?
[OnePlus 3 & 3T Cross Device Development] calvinistmac:
He doesn't have an OP5 to test with yet, so no he's not building Vertex for the OP5 right now.
[OnePlus 3 & 3T Cross Device Development] CJ-Wylde:
Finally got around to testing some other ROMs that weren't OOS based and landed on this one as my try this last since it's got the best reviews, etc and I'll probably stick to it and lemme tell you... WOW this is a NICE ROM!!! I have asked this before and got an answer but my brain doesn't seem to comprehend so I'm asking again for some added clarification:

When it says 12. Google Camera / OP3T front camera doesn't work?

- You'll need HAL3 enabled. VertexOS has HAL1 enabled by default. To enable HAL3 please flash the HAL3 Enabler. This may also fix front camera issues for OP3T. Be warned that you will lose OnePlus Camera functionality when you go HAL3.

A. I'm confused since when I flipped the included camera app to the front view it works just fine. Am I missing something here?

B. If I did flash HAL3 Enabler, what exactly would I be losing with functionality?

C. Will HAL3 provide better photos than HAL1?

I don't know why I can't seem to wrap my head around these things but if someone could dumb down the answers for me that would be great! This ROM feels a LOT nicer than OOS (Was using FreedomOS). Only thing I was hoping for that it doesn't have or I can't seem to find is center clock settings for statusbar clock. Does this ROM have this by chance?
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
If you aren't having a problem with your front camera, and you don't use Google camera than leaving HAL1 enabled is your best choice as it allows you to use the Stock OOS camera, which in this rom tends to give the best image quality.

HAL3 is for using certain camera apps which require it (like Google camera) or if you're having front camera issues on the 3T. Other than those to situations it is not necessary to enable HAL3
[OnePlus 3 & 3T Cross Device Development] CJ-Wylde:
You sure have made my night, thank you!!! Now to just figure out a way to get center clock and boom baby, done!!
[OnePlus 3 & 3T Cross Device Development] lpsld:
This is besides pa the bsst rom for the oneplus 3/3t

My last cycle was 3 hours SoT what is low, normally I get like 5-6h but it was over 1day in standby so that is really good.

There are no laggs in the UI and I also can play medium-heavy games without any problem.
[OnePlus 3 & 3T Cross Device Development] arifqur:
To get clock customizations use a substratum theme called kklock. And use the one for pa.

https://xdaforums.com/oneplus-5/themes/v4-2-k-klock-customize-statusbar-clock-t3629157
[OnePlus 3 & 3T Cross Device Development] CJ-Wylde:
Whoot! I didn't realize K-Klock had non OOS compatibles, thanks!
[OnePlus 3 & 3T Cross Device Development] arifqur:
Glad to be of help
[OnePlus 3 & 3T Cross Device Development] joshuous:
Keep HAL1 if you plan to use OOS Camera. Switch to HAL3 if you wish to use Google Camera :)
[OnePlus 3 & 3T Cross Device Development] joshuous:
A new official should be coming out soon :)
[OnePlus 3 & 3T Cross Device Development] Nemuritor01:
Define "soon" :silly: :laugh:
[OnePlus 3 & 3T Cross Device Development] joshuous:
Will be releasing a final test build to testers. Then it should be out
[OnePlus 3 & 3T Cross Device Development] Nemuritor01:
Great... :good:

Is there a possibility to join the test group?
[OnePlus 3 & 3T Cross Device Development] samisharora:
Was planning to flash 3.2 today but saw latest commits on ur git and managed to make myself wait for next :p. Eagerly waiting for official :)
[OnePlus 3 & 3T Cross Device Development] nokia_16:
Same here... Planning to flash today.. Now waiting for the next update :)
[OnePlus 3 & 3T Cross Device Development] calvinistmac:
Check your private messages please.
[OnePlus 3 & 3T Cross Device Development] joshuous:
Lemme know if your OTA updaters work guys (if you're on Official 3.2 atm). I'll release the official update post a while after
[OnePlus 3 & 3T Cross Device Development] _millig_:
It is ! I'm downloading the latest build, thx !
[OnePlus 3 & 3T Cross Device Development] Rawwrius01:
Works perfect :)

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] mateileul:
It works, downloading now the latest.
[OnePlus 3 & 3T Cross Device Development] oyogen:
OTA works! I'm downloading the update. :)
[OnePlus 3 & 3T Cross Device Development] TNSMANI:
It is working and I am downloading it. Thank you.
[OnePlus 3 & 3T Cross Device Development] kalpik:
Is it just me or the new update is really laggy? Scrolling specially is noticeably laggier.
[OnePlus 3 & 3T Cross Device Development] Nemuritor01:
:laugh:

That was fast Josh.

I'm downloading. Nice to see dci-p3 has been added. :svetius:
[OnePlus 3 & 3T Cross Device Development] omar77w:
Successfully updated the through OTA! Interestingly the first time around it asked for root permission, booted into recovery and didn't do a thing. Second time around–it already had root permission– it booted into recovery and installed flawlessly.
[OnePlus 3 & 3T Cross Device Development] joshuous:
​

Thanks guys for letting me know that the OTA worked :)

DCI-P3 support for compatible displays (not for my OP3 though :()!

Downloads

VertexOS v3.3 (IMPORTANT: Please flash the hotfix kernel after you flash VertexOS)

RenderZenith EAS 009 standalone kernel with HOTFIX v3 for DCI-P3 kernel panics

Edit: hotfix v3 fixes sRGB issues in v1 and v2

Use the latest firmwares available (stable or beta is fine)

I recommend a Nandroid backup and clean flash. If you want to dirty flash from the previous official, please wipe /system and flash ROM, GApps and Magisk.

VertexOS v3.3 changes

* Updated to CAF LA.UM.5.8.r1-02200-8x98.0 tag

* Improve Schedutil performance (I noticed before it was performing terribly compared to Sched)

* Re-enabled sdcardfs

* Back to CFQ for now

* Updated APNs from LineageOS

* Updated to latest blobs and device tree commits from LineageOS

* Reverted VR framework until someone tells me they want to use it

* UI fixes (LTE+, Shutdown message, etc)

* Camera has the processing dialogue again (I haven't smali edit it yet)

RenderZenith EAS 009 changes

* Upstreamed to Linux 3.18.60

* Updated with latest LineageOS commits

* Enable RCU_BOOST

* Disable BUS_AUTO_SUSPEND

* Cherry-picked some commits from Pixel kernel

* Tuned sRGB for S6E3FA5 display

* DCI-P3 support for S6E3FA5 displays (tunable is in /sys/devices/virtual/graphics/fb0/dci_p3. Please set it with Ex Kernel Manager or a script to echo 1 into the tunable. I'll maybe add a toggle in future)

* Enabled Boeffla Touchkey driver by default (capacitive keys light up OOS-style)
[OnePlus 3 & 3T Cross Device Development] zedbg:
Ota works thanks
[OnePlus 3 & 3T Cross Device Development] AWildRattata:
Does the latest update fix the wierd bug when it doesn't reconnect to WiFi?
[OnePlus 3 & 3T Cross Device Development] joshuous:
I have no idea what this bug is
[OnePlus 3 & 3T Cross Device Development] AWildRattata:
Sorry, probably could have been more specific. It was the only thing throwing me off from this ROM.

It's mentioned here: https://xdaforums.com/showpost.php?p=72186492&postcount=876

and here: https://xdaforums.com/showpost.php?p=72091887&postcount=767
[OnePlus 3 & 3T Cross Device Development] TNSMANI:
There was no such bug.
[OnePlus 3 & 3T Cross Device Development] AWildRattata:
I've quoted two other people that have experienced it right above your past.
[OnePlus 3 & 3T Cross Device Development] joshuous:
You know those posts were from months back right?
[OnePlus 3 & 3T Cross Device Development] omar77w:
Wow, happy to report this has been fixed! That was so quick!

Thanks a lot, and here's a humble donation my homie. :good:
[OnePlus 3 & 3T Cross Device Development] AWildRattata:
Yes. I haven't seen it mentioned in any other change logs. But I don't religiously check xda either. So without actually answering my previous question, I assume it was fixed awhile ago?
[OnePlus 3 & 3T Cross Device Development] joshuous:
I assume so, because I don't face such issues atm
[OnePlus 3 & 3T Cross Device Development] joshuous:
Thank you very much Omar :)
[OnePlus 3 & 3T Cross Device Development] vishruthys:
I think the disable backlight switch is not working backlight stays on even if the switch is turned off
[OnePlus 3 & 3T Cross Device Development] UnbracedTundra:
Installed the ROM after flashing OB10 firmware with BeansGApps. I got the green camera bug but it took pictures correctly. For me, what fixed the green screen was flashing HAL1 enabler followed by HAL3 enabler.
[OnePlus 3 & 3T Cross Device Development] calvinistmac:
We don't support BeansGAPPS. If you need this problem looked at you need to clean flash again with OpenGAPPS, then take a log, save it in hastebin.com and then post it here along with any applicable screenshots. Sorry for any inconvenience.

EDIT: Sorry for the double post.

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

Confirmed.
[OnePlus 3 & 3T Cross Device Development] ranaxda200:
Can you please elaborate why not to use Beangapps? As only that gapps fully support Google voice over support at startup flawlessly.
[OnePlus 3 & 3T Cross Device Development] Bearthquake:
I assume because beansgapps and opengapps are coded differently (hence the slightly different functionality) and Josh built the ROM to be compatible with opengapps.

Not trying to be a smartass, but if I could assume, this answer is the reason why.
[OnePlus 3 & 3T Cross Device Development] joshuous:
Main reason is because I use OpenGapps. So
[OnePlus 3 & 3T Cross Device Development] calvinistmac:
Every version of OpenGAPPS I've used since the beginning of June has had Google Assistant (which is what I think you mean) support on initial setup. If I'm wrong please elaborate as your wording is slightly awkward.

Yes the reasoning is because it's what the dev (Josh) uses and it's what he supports, and since he's the one doing all of the debugging we need to comply with his wishes.
[OnePlus 3 & 3T Cross Device Development] oyogen:
If I want HAL3, must I flash the HAL3 enabler again after dirty flashing the update?
[OnePlus 3 & 3T Cross Device Development] calvinistmac:
Yes you should, because it'll overwrite it.
[OnePlus 3 & 3T Cross Device Development] kentexcitebot:
No, that's not how Gapps works.

First of all, Gapps doesn't touch camera. At all. Green viewfinder is because of the nature of HAL1.

Second, you need to realize OpenGapps is completely UNTESTED and built nightly, contrast to Beans which has an entire community of testers and more through backers. If anything, you'll have problems using Open. Period.

I understand why you suggested Open since your maintainer uses it as DD, but please: let's not blame everything on Gapps. Thanks :)