[OFFICIAL][9.0.0_r46][ASB_2019-11][grus] XenonHD 9.0 (14-11-2019)

[elpaablo]

Ok, I'll try it later. I tested the kernel (boot + dtbo) on MoKee, because the issue seems to be kernel related, and the phone blocked at first incoming call.

 

[elpaablo]

Well, I made a clean install and all the issues I detected are still there. So, in increasing order of importance, auto-brightness is still not completely stable, wifi still doesn't auto-connect to saved networks and incoming calls in deep sleep disable phone. Also, I think global performance is worse. So... not good news, sorry.

 

[krasCGQ]

Well, I made a clean install and all the issues I detected are still there. So, in increasing order of importance, auto-brightness is still not completely stable, wifi still doesn't auto-connect to saved networks and incoming calls in deep sleep disable phone. Also, I think global performance is worse. So... not good news, sorry.

Are you sure you're on latest build?

Sent from my MI 9 SE using XDA Labs

 

[elpaablo]

Yes, XenonHD-190903-Official-grus + vendor 10.3.4 eea stable + factory reset.

 

[GuestK00247]

@krasCGQ
which Vendor is better, China developer 9.7.4 or EEA stable V10.3.4.0.PFBEUXM?
Are these different?

 

[krasCGQ]

@elpaablo

Check with latest build please. It's ROM (device) side change this time.

Sent from my MI 9 SE using XDA Labs

 

[rzki03]

@elpaablo

Check with latest build please. It's ROM (device) side change this time.

is freezing incoming calls fixed on this new build??

 

[krasCGQ]

is freezing incoming calls fixed on this new build??

That's what I want to know from said build.

Sent from my MI 9 SE using XDA Labs

 

[okitavera]

That's what I want to know from said build.

Sent from my MI 9 SE using XDA Labs

Already upgraded to the latest build. And yes, I receive the call while deep-sleep (~30minutes after screen off is already considered a deep-sleep isn't it ? )

 

[elpaablo]

So, I've got bad and good news.
- Incoming calls issue is not solved, but I found out what's causing it: fingerprint unlock. I tested with several calls, first without any screenlock protection. Then I started adding protection modes (pin, faceunlock and fingerprint) until the phone blocked. It doesn't always block like it used to, but it will end up blocked, if I use this kind of protection. I'm using pin + faceunlock without any blocks until now.
- Wifi still doesn't auto-connect to saved networks. Usually, locking and unlocking the phone solves this.
Now the good ones:
- Auto-brightness is much better. It's stable now.
- Although is somehow conflicting with incoming calls, fingerprint detection is fast and reliable.
- Performance is also better. Actually, I think this ROM is more fluid than ever.

Now, I can finally try Okita Kernel 7.5, see if it gets along with XenonHD.

 

[okitavera]

So, I've got bad and good news.
- Incoming calls issue is not solved, but I found out what's causing it: fingerprint unlock. I tested with several calls, first without any screenlock protection. Then I started adding protection modes (pin, faceunlock and fingerprint) until the phone blocked. It doesn't always block like it used to, but it will end up blocked, if I use this kind of protection. I'm using pin + faceunlock without any blocks until now.
- Wifi still doesn't auto-connect to saved networks. Usually, locking and unlocking the phone solves this.
Now the good ones:
- Auto-brightness is much better. It's stable now.
- Although is somehow conflicting with incoming calls, fingerprint detection is fast and reliable.
- Performance is also better. Actually, I think this ROM is more fluid than ever.

Now, I can finally try Okita Kernel 7.5, see if it gets along with XenonHD.

I use stock kramel, with fingerprint registered, and I didn't have incoming call issues.
My additional setup are just magisk and opengapps. No other fancy things.

Did you try clean install ? maybe it'll fix the incoming call issues

 

[elpaablo]

I made a clean install. But I've restored my apps after that. I don't use xposed, I'm not using mods, but I'm doing something I forgot: use stock launcher, see if makes any difference. I was using Nova with (root) double tap to sleep.

---------- Post added at 07:56 AM ---------- Previous post was at 07:46 AM ----------

No go. But I will try again. This time without any apps installed, just a clean fresh install.

 

[okitavera]

I made a clean install. But I've restored my apps after that. I don't use xposed, I'm not using mods, but I'm doing something I forgot: use stock launcher, see if makes any difference. I was using Nova with (root) double tap to sleep.

---------- Post added at 07:56 AM ---------- Previous post was at 07:46 AM ----------

No go. But I will try again. This time without any apps installed, just a clean fresh install.

Oopsie, my bad, after dropping gapps, it happens again.

 

[elpaablo]

Yes, I made a fresh install. Have nothing installed (not even gapps or magisk) except the rom. Enabled fingerprint and the phone blocked on the first idle incoming call.

---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------

I will stay with this rom, for now, though. It's very fast. I want to see if it's stable too.

 

[okitavera]

Yes, I made a fresh install. Have nothing installed (not even gapps or magisk) except the rom. Enabled fingerprint and the phone blocked on the first idle incoming call.

---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------

I will stay with this rom, for now, though. It's very fast. I want to see if it's stable too.

Yeah, I feel that too on the latest updates, performance done right ?

 

[elpaablo]

Okita kernel is working very well with this ROM. :good:

 

[vecino]

Can you try Google Phone from Play Store? It might help.

 

[elpaablo]

Can you try Google Phone from Play Store? It might help.

I'll try it later.

 

[elpaablo]

I tried it but it didn't make any difference.

 

[krasCGQ]

Yes, I made a fresh install. Have nothing installed (not even gapps or magisk) except the rom. Enabled fingerprint and the phone blocked on the first idle incoming call.

I wonder what if you take September 3 build's kernel and use it on latest build...

Sent from my MI 9 SE using XDA Labs