yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] CapAdamT:
Hey all, I broke my Pixel 7 Pro's screen while trying to do a deep clean, am getting a replacement in soon... I have this ROM installed and am curious... Will I be able to use Google's fingerprint sensor calibration tool with the ROM installed? Or will I have to factory reset, install stock ROM, calibrate, and then go back to Evo X?
[Google Pixel 7 Pro] thomas.raines:
Finally got the time to update to A14. I installed the base packages in bootloader, booted to recovery and sideloaded evolution_panther-ota-uq1a.231205.015-12310250-OFFICIAL.zip. At about 47% I got a message in recovery screen that said if I want to install additional packages, I need to reboot to recovery. I though odd, but I choose reboot to recovery now and sideloaded the rom again and got same message but selected no and rebooted to rom. I'm on A14 now and things seem to be fine, just thought that message was odd...
[Google Pixel 7 Pro] kodycdrews:
@thomas.raines here's a good explanation.
[Google Pixel 7 Pro] reg66:
Ok, so are you up and running with the rom download from the cheetah link I gave them or still have issues?
[Google Pixel 7 Pro] anonymouseli:
no i think its good
[Google Pixel 7 Pro] AnierinB:
The ota.zip sideload installation finishing at 47% is normal for userdebug builds on aosp based recoveries. The dialog is also normal as you need to reboot to recovery before installing any add-ons (e.g magisk), since they target the active slot while the ota.zip targets the inactive slot. So you need to reboot to recovery after sideload for the slots to switch before installing any add-ons. If not, then you just reboot to system.

recovery: Ask to reboot before installing anything after A/B update · Evolution-X/bootable_recovery@a16da11

Change-Id: Id3e44ddbe11119fcc66d379216f8f5e683979a9f

github.com

This also ties into why when attempting to retain root when running in-system ota, you need to patch the inactive slot only when the installation is done and haven't rebooted yet; As the ota is installed to the inactive slot and your device subsequently switches to that slot upon reboot. Patching it beforehand would result in it getting overwritten during the update process.
[Google Pixel 7 Pro] thomas.raines:
Yeah I figured it was something like that, and I don't root so no need for majisk any more. Just odd as I've never seen that message....

On another note, signal on verizon seems a little low, and at boot, it takes a bit to connect to the verizon network. Flashed the latest radio from stock rom (14.0.0 UQ1A.240105.004.A1, Jan 2024, Verizon), but that didn't help.

WiFi works perfect though.
[Google Pixel 7 Pro] letmedanz:
Is there a way to disable app icons for persistent notifications from showing in the status bar?
[Google Pixel 7 Pro] kodycdrews:
Where I live and work, my signal is almost always poor lol. But I have noticed that I completely lose service ("network unavailable" with an '!' covering the signal icon) more often than when on stock. Not sure if it's software- related or not, but it is interesting that you brought up a similar issue.
[Google Pixel 7 Pro] thomas.raines:
I edited the APN with #6 on the list. Signal is about the same, but it appeared to connect to the network a lot faster. I'm not sure if changing the preferred network type would make much of a difference. What we need is someone that is on stock and could give us a comparison (something I'll try this weekend when I have more time). Although I'm not entirely sure, this could be an issue with the ROM/kernel. But it could also be an issue with the radio.img. I might try flashing an older radio.img to see what happens, but again, when I have more time.
[Google Pixel 7 Pro] kodycdrews:
Mine appeared to be defaulted to the same settings as #6. I believe it was like that when I was on stock too. But I'm assuming my issue is location-based, since my iPhone 13 pro didn't get much better service either. When I'm out and about, no issues whatsoever! But if you do end up doing some testing, let me know what you find out!
[Google Pixel 7 Pro] BIGWORM:
Anyone have any issues running equalizers with this ROM? Both Wavelet and JamesDSP refuse to cooperate.
[Google Pixel 7 Pro] thomas.raines:
I meant to say I checked it, not set it. Either way, I just flashed a radio image from A13 stock, and still had the same results.
[Google Pixel 7 Pro] D<3'SJ2427:
Im using V4A, I think an Alpa build for A14. Seems to be working fine w/Spotify after Audio FX app being disabled. I was using Rootless James DSP via Shizuku on a different phone that is completely stock and that seems to work ok as well. I wasn't like rigorously testing them so ymmv

Releases · AndroidAudioMods/ViPER4Android

ViPER4Android app configuration files. Contribute to AndroidAudioMods/ViPER4Android development by creating an account on GitHub.

github.com

GitHub - timschneeb/RootlessJamesDSP: An implementation of the system-wide JamesDSP audio processing engine for non-rooted Android devices

An implementation of the system-wide JamesDSP audio processing engine for non-rooted Android devices - timschneeb/RootlessJamesDSP

github.com
[Google Pixel 7 Pro] neroes:
C:\platform-tools_neu>adb sideload evolution_cheetah-ota-uq1a.240105.004-01090311-OFFICIAL.zip
* daemon not running; starting now at tcp:5037
* daemon started successfully
serving: 'evolution_cheetah-ota-uq1a.240105.004-01090311-OFFICIAL.zip' (~11%) adb: failed to read command: No error

Can anyone clear this up?!

platform-tools_r34.0.5-windows
[Google Pixel 7 Pro] AnierinB:
Read OP #3
[Google Pixel 7 Pro] neroes:
I'm updating the previous version

#edit

I did the update OTA. then that worked
[Google Pixel 7 Pro] Kingzak34:
Thanks to @AnierinB for the update, Bluemail is working again. @scorpio76r Maybe your app is fixed too.

I hope we'll see Figerprint scanner customisation some day. Anyway thanks a lot for your work!
[Google Pixel 7 Pro] scorpio76r:
I just downloaded TypeApp again and, it still immediately crashes when I open it. The issue is app related. I'm glad to hear that Blue mail is working for you now. This one I have been using is working for me. I do miss TypeApp though, I had that apps agarithm trained 😊
[Google Pixel 7 Pro] Kingzak34:
Looks like it works on my end now (it didn't before the update)

And it's a perfect copy of Blue Mail lol that's why both didn't work.
[Google Pixel 7 Pro] scorpio76r:
Thanks for the heads up. I will update and, try to download again.

Edit * I just took Evo-X latest update and, now type app is working.
[Google Pixel 7 Pro] michalsunrise:
Hello can I install it on xaomi mi 11 ?
[Google Pixel 7 Pro] reg66:
This is the pixel 7 forum, so no! Have a look at your forum
[Google Pixel 7 Pro] Aluc@rd1387:
1. Vibrate on call connect is not working still now. Just informing the issue.

2. Fingerprint recognition a little under the fingerprint icon after activated app lock for app.
[Google Pixel 7 Pro] thomas.raines:
I think they are saying the fingerprint area and icon are not aligned.
[Google Pixel 7 Pro] scorpio76r:
I understand what they were saying. I was going to point out a issue that I found until I found that the issue was on my end.
[Google Pixel 7 Pro] AnierinB:
1. Will look into it.

2. Resolved (will be in upcoming release):

Revert "udfps: Remove navbar inset for BiometricPrompt" · Evolution-X/frameworks_base@5ef982f

This reverts commit 96962a2fc0898e0d9dfb51346085615b107f2774. Unneeded on U, actually causes misalignment

github.com
[Google Pixel 7 Pro] SONO1:
Hi !

Please , can someone check..if Edge Lightning real works ?

Thanks Alex
[Google Pixel 7 Pro] luckyluke113:
Anyone meets the issue with Wifi Mesh?

My Pixel 7 Pro doesn't auto-switch to the nearesh node anymore.

I've tried with an iPhone and it still worked well.
[Google Pixel 7 Pro] thomas.raines:
@AnierinB

Posibly got some bugs/issues.

Signal is low and stays on LTE/4G most of the time (I'm on Verizon). After reboot, it takes the phone about 45-60 seconds just to connect to the network. I flashed back to stock A13 and signal has full bars. Flashed stock A14 and signal is has full bars, but looks like it's preferring LTE/4G. On both A13 and A14 it took the phone about 15-20 seconds to connect to the network I tested this with the phone sitting in the same spot. I also flashed radio.img from both A13 and A14 stock on EvoX and tweaked phone info/APN, but no improvement to signal. WiFi works great though. I did run into a Reddit thread where several users are having signal issue with A14 (I'm assuming stock).

Some secure apps like PayPal & my Dr's app, crashed/force closed after inputting password. I try clearing cache/data and even uninstalled/reinstalled these apps. Unfortunately, I was not near my PC and could not get the logcat to really see what was going on. My banking and credit card apps worked fine.

Could not access voicemail. Verizon requires a pin. I input the same pin I've used for years and it told me to try again. Tried again with same results. Called and reset my pin, waited 30 minutes and still it would not accept my pin. Once I flashed back to stock, no issue accessing vm.

Google sees this as a YU Yureka device and not a Pixel 7. Didn't really pay attention to this since I've seen similar things like this in the past, but now I'm wondering if that is contributing to some of these issues.

In linux, I have to sideload the rom as root. Not really an issue, but may want to note it in the install steps.

I'm about the flash latest build again and see if there is any improvement or not since I was on EvoX A13 when I flashed EvoX A14 build.

After flashing latest build, Paypal, my Dr's app and amazon fc'd when trying to log in, but after connecting device to pc for a logcat, they are all working now (very odd).

I am able to access my voicemail. Not sure what happened here, but it's looking like these were me issues

As for siganl, I'm gonna say it's about the same as A14 stock now but don't quite have full bars (about 4), and still seems to be favoring 4G/LTE. So, it looks like Google got some stuff to fix?

Was still recognized as a YU Yureka device by google. I got an email after install to finish setting up my YU Yureka device.
[Google Pixel 7 Pro] Yeedatoy:
The Yureka device is intentional as part of passing integrity. Naturally you're going to have issues if you flashed from Evo 13, Straight to 14. You should have flashed stable 14 on both slots before flashing the Rom, or whatever AB has written in the instructions. I'm running a Verizon SIM as well and have zero issues. I will say that Verizon, especially with all of its MVNOs sometimes ends up just needing the APN switched.... but the way you sit right now, it's not really possible to know without seeing some specific screenshots what firmware you have on the other slot. Evo updates package full firmware updates, but it's still important to make sure you're on the correct android version before you flash. You always need to make sure you have a stable base before you move forward with any modifications. The most important software related components are packaged in those specified Android versions listed in the installation instructions, as that is what contains your modem and several other extremely important and essential components necessary for the correct operation of your device, and to ensure as much as possible that if something goes wrong and you make a mistake during flash time, the device has somewhere to fall back on and still boot correctly or at least get back into it state where you can start over again. Don't underestimate the importance of some of those first few steps, especially if you continue on and try to flash something else and get to the point where you have no idea what is loaded on to which partition and you end up flashing a fast boot ROM and something goes wrong and you end up with a bricked device.
[Google Pixel 7 Pro] thomas.raines:
I'm guessing that you're saying the Yureka passing integrity is only if you're rooted, correct? I haven't rooted a device in so long, that I have learned it's really not needed (for me). But maybe declaring that in the OP might be helpful...

In the flashing instruction it says nothing about flashing latest stable on both slots. I'm assuming you are talking about flashing latest stock A14, which I did. Even if I have to factory reset due to an issue, I will flash stock first, set it up, then flash the custom rom/images.

I know from experience, Verizon can be a huge pain to deal with. But I'm currently on the firmware that came with the rom, and I still have the same results as stock A14, g5300q-230927-231102-b-11040898.

I had an issue with something I was testing and decided to factory reset. Had an issue with secure apps fc'ing again, but I setup my vpn and now they all work.

Overall, I see your point with what you're saying, but I've been doing this a long while.

As for radio issues, it looks like it's been an issue off and on with this device, some worse than others.

Pixel 7 poor signal strength in areas with good coverage - Google Pixel Community

https://www.reddit.com/r/GooglePixel/comments/zb9mb5

Cell service - Pixel 7 + Android 14 updates

Since updating my Pixel 7 to Android 14 a couple weeks ago, I have completely lost all cell service. No calls, no text. Phone has a "No SIM - No Service" message in the corner. The SIM works in my previously, heavily damaged phone; and new sims do not function in my current phone (spent a...

community.verizon.com

Pixel 7 Pro 5g issues

My pixel 7 Pro shows 5g full signal, but I cannot download anything unless I change the default to LTE. 1. Is anyone else having this issue? 2. Is there a fix for it?

community.verizon.com
[Google Pixel 7 Pro] AnierinB:
Rooted or not, it is required for passing Play integrity API. Anyways, that fp was blocked by google yesterday, so users should update to the 01/15/2024 PifPrebuilt in op #2 to pass on the latest builds.

As for your first post, you mentioned that you needed root to sideload the ROM on linux? If that's the case then it is definitely a local issue on your setup. Sounds like your platform-tools folder is owned by root
[Google Pixel 7 Pro] thomas.raines:
I thought the play integrity API was for rooted only. Gonna flash it now.

That's what I thought at first but I checked the permissions and it looks to be owned by me.

I copied my adb lib to /home/thomas/bin, and I'm able to do all other abd functions under user. Only sideload is affected.

-rwxrwxrwx 1 thomas thomas 2152530 Jul 4 2016 adb

-rw-r--r-- 1 thomas thomas 1060174 Jan 1 2008 NOTICE.txt
-rwxr-xr-x 1 thomas thomas 7885616 Jan 1 2008 adb
-rwxr-xr-x 1 thomas thomas 303864 Jan 1 2008 etc1tool
-rwxr-xr-x 1 thomas thomas 2523512 Jan 1 2008 fastboot
-rwxr-xr-x 1 thomas thomas 13408 Jan 1 2008 hprof-conv
drwxrwxrwx 2 thomas thomas 4096 Dec 1 07:15 lib64
-rwxr-xr-x 1 thomas thomas 262184 Jan 1 2008 make_f2fs
-rwxr-xr-x 1 thomas thomas 262168 Jan 1 2008 make_f2fs_casefold
-rwxr-xr-x 1 thomas thomas 874640 Jan 1 2008 mke2fs
-rw-r--r-- 1 thomas thomas 1157 Jan 1 2008 mke2fs.conf
-rw-r--r-- 1 thomas thomas 38 Jan 1 2008 source.properties
-rwxr-xr-x 1 thomas thomas 1522536 Jan 1 2008 sqlite3

When I try to sideload as user:

MainFrame A14 $ adb sideload evolution_panther-ota-uq1a.240105.004-01090202-OFFICIAL.zip
loading: 'evolution_panther-ota-uq1a.240105.004-01090202-OFFICIAL.zip'
* cannot read 'evolution_panther-ota-uq1a.240105.004-01090202-OFFICIAL.zip' *

I guess I could try using the one in platform-tools dir?
[Google Pixel 7 Pro] linuxgod05:
Does anyone know how to fix this weird outlook issue? It only happens with this ROM anytime I try to type in a email address it comes up with this attached image. Instead of showing me the list of possible people to email to. Stock Google ROM doesn't seem to have this issue even with all the settings the same.

Just wanted to say how awesome this Rom is. It's amazing! Thank you for all the hard work you've done
[Google Pixel 7 Pro] yahya2110:
hello any help please im getting this error (adb server version (31) doesn't match this client (40) in the last step when trying to use adb sideload commande
[Google Pixel 7 Pro] mad4some:
Try the command again but put parenthesis " " around rom name like "evolution.zip". I had a similar error and that fixes it for me.
[Google Pixel 7 Pro] yahya2110:
still getting error (adb: failed to read command: No error) even after formating pc and reinstalling the usb and fastboot tools,changing the cable,the usb port ,all the steps are fine except the last one with adb sideload,the connection is always lost bettwin the pc and the phone,a frustrating situation
[Google Pixel 7 Pro] Wmateria:
Mine got stuck at 1% as i mentioned few threads ago..what i did was download the zip again, and then it had no problem installing to 100%, i did a factory reset and then rebooted. This was from a clean Jan Patch firmware already.
[Google Pixel 7 Pro] justin333:
Was this working in Stock ROM for pixel 7?
[Google Pixel 7 Pro] kodabmx:
Ok. So after a few years of running Samsung phones with stock ROM (didn't want to blow the e-fuse and F*** knox), I smashed it (fold 3) into many pieces because it pissed me off one final time.

Now I'm using a Pixel 7 Pro.

With the stock ROM, I had several apps that just didn't work. Smart Life would take 2 minutes to load if it ever did, SofaBaton app for a remote would only load on the first run, then you had to wipe the cache and data for the app to get it to work again.

Chromecast didn't work on the stock ROM while trying to pair with a Nvidia Shield Pro.

This and many other little quirks were bothering me so I installed this ROM.

All those things work now. Battery life was kinda crap until I found out that this ROM keeps the data connection alive while using WI-FI by default. Turned it off in Dev settings, and now the ROM has great battery life.

I even got Magisk and LSPosed installed with working Google Pay and banking apps.

I'm not using WI-FI calling (what the hell for? I live in a city with excellent cell coverage) so I couldn't tell you if that works.

I particularly like the slider control for animations in dev settings. 0.1x scaling makes the phone fast without totally getting rid of the anims.

OH and the damned fingerprint scanner actually WORKS with this ROM.

With the stock ROM, I found myself having to lick my finger and wipe it off before it would recognize it.

ADB is kind of a pain in the butt sometimes (it'll take a few minutes after booting to "see" the device using a USB cable, but wireless ADB works right away if you want to screw with pairing codes.

I flashed it using Manjaro GNOME (Linux).

A question for the devs: Will there be support for video over the USB connection or is that a HW limitation?
[Google Pixel 7 Pro] vkass:
Adb shell

settings put global window_animation_scale 0.1

settings put global transition_animation_scale 0.1

settings put global animator_duration_scale 0.1
[Google Pixel 7 Pro] MultiCulti:
hoi, i just tried on other phone again to be sure 😅

on stock and also with different pixel launcher it is like this if i turn off (pause) the workspace!

So there no apps visible!
[Google Pixel 7 Pro] AnierinB:
Keywords:

> Stock

> Pixel launcher

Evo:

> Not stock

> Doesn't use pixel launcher

> intended behavior

Not quite sure the point you're trying to make, they're different launchers and ROMs. Saying something is a bug just because it behaves slightly different yet retains the same underlying functionality is inaccurate.
[Google Pixel 7 Pro] Bestiole222:
I'm trying to install the rom but still at 0% after 10 minutes, how can I stop the process? Thanks
[Google Pixel 7 Pro] wgrant:
I had the same issue over and over again. Eventually it worked but I think it was just luck. I flashed stock January to both slots, wiping data then followed instructions for this ROM till it worked. If it got stuck (usually at 6%) I would cancel the side load command, reboot my phone to recovery, wipe again then attempt install.
[Google Pixel 7 Pro] Bestiole222:
I can't remember how to stop the adb command line so I do a alt+F4, the second time the installation was ok but I did a dirty flash coming from unofficial evo, and this brought me to bootloop. So I had to stop the phone, went back to recovery and wipe data. After that the phone booted, but I had to install all my app again.
[Google Pixel 7 Pro] t-ryder:
Thanks for the ROM.

Bug description: when using a shortcut (nova launcher widget or 3rd party app to lock / via the accessibility + device admin functions) to lock the device (which is IMO the most elegant and convenient way to do so) the screen does not turn off, it first shows the lockscreen for a second and then turns off. Feels like some annoying flickering every time locking. Other ROMs (Graphene OS, Statix OS, Stock ROM) don't do this.

How to reproduce: use shortcut to lock screen of Pixel 7

Logcat: s.a.

Screenshots: not needed

.:.

EDIT: to get rid of the effect I activated the old school CRT-off animation
[Google Pixel 7 Pro] t-ryder:
Do you guys flash using a proper data cable? Some time ago I was using a not that good cable for sideloading ROMs on my Pixel 6 and it got stuck again and again until I used the original cable. By now I got me a high quality pretty long cable and all works. Seems like the newer Pixels in combination with some USB hubs/controllers don't like every cable.
[Google Pixel 7 Pro] AnierinB:
I'll look into this. Thanks for following post #3 by providing logs and an accurate description of the issue.
[Google Pixel 7 Pro] Bestiole222:
Yes I use the original cable, I install unofficial and official evol with sideload command, and I had to do the install twice for the two roms. Don't know why.
[Google Pixel 7 Pro] justin333:
in the latest build, does safety net passes out of the box ?
[Google Pixel 7 Pro] Wi1son:
Anybody using another kernel they prefer over stock?
[Google Pixel 7 Pro] manban10:
Thank you for the rom. It's so smooth and everything just works. Battery life has been great, better than the stock rom. I haven't had any issues so far and it's been a week. I will update if I find anything wrong.
[Google Pixel 7 Pro] djisma86:
You have kernel stock or not? Standby drain?
[Google Pixel 7 Pro] manban10:
I am just using the one it came with. I went to bed with 100% and woke up with 98%. About 6 and a half hours.
[Google Pixel 7 Pro] Crazyiain:
Amazing ROM running perfect on my pixel 7 pro thank you to everyone.

Any help i followed the steps to patch the .img boot for magisk everything installed but magisk is still showing installed N/A

Do I need to download the original firmware boot?.

Cheers
[Google Pixel 7 Pro] reg66:
Are you using latest platform tools or some old, perhaps minimal adb fastboot version...?
[Google Pixel 7 Pro] yahya2110:
i use minimal_adb_fastboot_v1.4.3
[Google Pixel 7 Pro] reg66:
change it to latest Platform Tools

here

Might wanna check your drivers for pixel are up to date too...

Oh, and you may, possibly, run into conflicts between the adb instances installed, get rid of minimal 1st just in case, then install latest SDK PT
[Google Pixel 7 Pro] yahya2110:
thanks for you interest my friend, ive installed drivers via android studio.i still get an other error message ,look to the attachement picture

by the way i didnt update to the last version of android 14,i have upsidedowncakeprivacy sandbox under android 14 and i didnt perform a factory reset in crdroid recovery,in case if its a deal in these error messages,thanks for your time
[Google Pixel 7 Pro] reg66:
hmm... only things i can think of at this stage are uninstalling Platform Tools and reinstalling to root of C drive and also, try a USB 2.0 port rather than 3.x (if you have a USB 2.0)

Not sure if it's still a thing, but Ryzen PCs and laptops used to act up also. Are you Intel or Ryzen?

Did you uninstall/get rid of the previous minimal 1.4.3 as per my edit before? Having more than 1 instance of Platform Tools can cause conflicts