Search results

Or, install the test builds that AB has already posted which are OOS13 fw based. Or, just wait a little while until they get released.

There's only one channel - just look for the recent conversations https://t.me/EvolutionXOnePlus8

All of the chat is over in the telegram group.

As mentioned above, instantnoodle and instantnoodlep need sideload and data format with the latest build. kebab is ok without

Yes, but only if you use the specific Arnova gcam build with 48MP. You need the underlying patches, which are included in the rom, but also to use the specific app version, which isn't recommended for day to day. LMC for day to day and then Arnova just for 48MP.

No, C36 should be fine. It's minimum not required. C33 was the default for a long time with people running c35 as well.

We don't have adaptive charging, but do have Smart Charging - allows you to set the max and min charging levels so that it bounces between, say, 85% and 95% whilst on charge. It doesn't do the "and then charge to 100%" step, so set the min point carefully as that may be what you have when you...

I don't remember the specific details.. Take a look on telegram if you want to dig into it. But the gist of it is that the 8T doesn't have a normal sensor, I.e the same as other devices, and so it doesn't work in evox, lineage or others. And oos has some nasty algo to make it function.

No, it's a hardware limitation with 8T's where they've worked around it in the stock ROM - there isn't a normal sensor built in, and no-one's yet worked out how to make it work - in any of the custom roms AFAIK. For now, to quote AB, cope.... Just turn auto brightness off - it just doesn't work.

AB has said that OTA got broken and is now fixed, but will require a sideload of the next build to install that fix and then OTA will work again going forwards.

Make sure you have the same firmware on both slots...

TBH, I had trouble when trying to update to the latest builds - couldn't get past booting into fastboot or recovery. But, I hadn't cleaned flashed since A12 versions so no idea what was hanging around. So since I was going to have to clean flash anyway, I MSMed back to OOS11, flashed to C33...

No, it's not pre rooted. It has work around so that it passes SafetyNet out of the box, but it's not rooted. Just follow all the steps outlined here and you'll be fine. Coming from vanilla oos is pretty straight forward if you just follow the steps 1 by 1.

Have you updated recovery?

Automatic brightness doesn't work with 8T since they don't have a normal brightness sensor. No ETA on that one. I think the aptX thing is also known, but my headphones don't support that, so not sure.

Nope - anything less than C20 won't work, and some of us found that anything less than C31 caused heating problems (which exist in OOS as well). If you've got the C33 .zip, you probably just need to tell it to ignore the version check - change oplus_update_engine_verify_disable=0 to =1 in the...

MSM back to OOS11 and then update to OOS12, but why would you want to?

If you're comfortable with adb, you can hurry along the optimisation by doing ... adb shell cmd package bg-dexopt-job You'll need to turn on usb debugging first, make sure you've certified the pc by doing a adb devices If you're not comfortable with that, just wait for it to sort itself out...

Odd then - I'm the same C33 on 8T with evo from 25th and I don't have any heating issues now. It'll be running background optimisation for a while - always hotter with high drain right after an update, but you mine's not hot now.

What fw version are you on? I, and others including AB, think that heating problems existing on C21, but they're fixed on C33.

No - fastcharge for 8 and 8p are not fixed yet. 8T and 9R do fastcharge, but lock screen display doesn't work

You're using an out of date version of fastboot

No, you didn't follow the instructions in the first post. If you just flash the rom, you'll brick your phone. You have to flash the OOS12 firmware first. If you're on the latest 6.5, you've got the right OOS11 firmware to start from, so you can skip step 1 of the instructions. Other than...

Did you flash the firmware first i.e. All of the steps apart from the format, or just flash the 6.6 rom? If it's the later, then you're in msm territory, or some have had luck switching to the other slot, but that takes access of course.

OOS camera and warp are WIP in current (now 7/22) builds - various gcam builds work fine though. Some seem to have tried updating the fw, sideloading the rom and then skipping the format step at the end - i.e. follow all of the instructions and just skip the format, but I haven't seen anyone...

He's going to work on it once the big things are done. So, have to use GCAM until then.

AB left his warp charger elsewhere, so doesn't have one atm. Sure it'll get fixed soon though.

Assuming you mean 6.6 not 5.6, then yes, it's a known problem at the moment.

Then just follow the instructions in the first post. If you don't flash the firmware you'll brick your phone.

Have you already flashed to oplus 12 firmware? If you're already on 6.6, then you don't have to clear data, if you're not on 6.6 already then you must flash the c20 firmware first. Read the instructions in the first post.

Its a known problem. Hopefully fixed soon.

There's no OTA yet because of the need to update firmware. AB's said that he won't push OTA until most people have updated - else there will be lots of people with bricked phones.

AB has said that the camera is something he'll work on shortly, but he's not planning to include Atmos. For now (and IMHO for ever), use one of the gcam ports.

Do you mean you're on evo-x 6.6 alpha builds, in which case you just need to follow the intructions on the first post for a dirty flash, or are you on OOS12 itself?

If you're on the oplus alpha, then I think you can just follow the dirty flash instructions, but to move from the oos11 to oos12 oplus firmware, it's defo going to need a clean flash.

That's the approach I always tend to take if I switch ROMs and it certainly seems to minimise odd glitches. One additional thing I do is to flash the OOS11 build twice - to make sure both slots are the same. Download it as a local zip and load it twice. Never sure if it makes a difference...

Hi @AnierinB I just wanted to say thanks for fixing the night light scheduled on/off in the latest build.

Hi @AnierinB . Looking at the change log, I assume you didn't get a chance to look at this one yet. But, just in case you did, the latest build still has the same issue with macro lens on 8T. Always grateful for the great work, but just to flag it to you since you mentioned you hoped to fix it.

The night light issue has been around for a little while and already reported. I've given up for now and just turn it on and off using the tile

Hmm - bit more playing. The icons seems to get "stuck" for me. So, initially, no VoWiFi or VoLTE icons, but I'm connected fine. Then, reboot System UI, and I get VoWiFi icons. Turn off WiFi, and VoWiFi icons stay displayed, and no 4G icon (since there's now no wifi, it should be showing 4G)...

No, I don't see any icons, but I can call with flight mode on, and only wifi enabled, so wifi calling must be working I think

I think they're working, but the icons aren't working. Try putting flight mode on, turn on wifi, and see if you get VoWiFi - that seems to work for me, so I think it may just be icons. @AnierinB , this seems to be a bug introduced in the most recent build - previous one showed the icons cirrectly.

You don't need root for play store, gpay, banking etc.. I'm running the current EvoX on my 8T, unrooted and everything works fine. The only slight funny thing is 2 apps (Barclays Bank and the NHS app in the UK) don't like fingerprints - they work fine, but biometrics don't work. GPay and all...

Hi @AnierinB . In case you get a chance to look at it, I've tried several gcams today, and they all crash if you try and use the macro lens on my 8T. The error message in the logs all look similar ... 05-14 20:44:51.058 11477 11477 W ProtoDataStoreFlagStore: Unable to retrieve flag snapshot...

Hi @AnierinB . I'm not sure if you expect them to work, but on 8T, the macro lens doesn't work, even with the snapcam versions. When switching to lens 3 (macro lens), any of the gcam versions I've tried crash. I've tried Greatness, BSG, Wichaya and all with the same result. Happy to post logs...

I think there's a little bug in night light. I have dark mode and night light set to come on on and off at dusk and dawn. dark mode works fine, night light turns on at dusk, but doesn't turn off at dawn. If I look at its setting, it's still turned on, but says "will turn on again at Sunset".

L1 for me as well

Thanks. Ok, I gave it a crack this evening and it's all up and running now. One thing I noticed is that the macro camera doesn't work in gcam. When you add in as an aux camera, and then try and use it, gcam crashes. It's the same on Nameless, but works on PE. I wondered if anyone had found...

Could someone tell me if Evo-x supports google pay when not rooted. I'm having some problems with Nameless so thought I'd give it a try, but use g pay all the time and don't want to root.

As I said, I don't know if this is the cause on evo-x, but the same problem with no doubt similar 12.1 base is mentioned on PE and Nameless, with the double flash being suggested as the fix.