yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] halfbytecode:
I clean flashed the 04/19 build and it is quite smooth, in fact more than even the latest stock ROM. It seems this ROM would be a daily driver for a lot of users. There seem to a few things that could be ironed out to make it even better.

- Android System Intelligence and crDroid System are showing high battery usage. The former shows a wakelock for over 3 hours 15 minutes by a persistent download job service, while the latter shows high background usage for about 3 hours 45 minutes. Checked using GSam after a full charge.

- App exit animation, when returning to the app drawer, at times changes to slide down, and manually restarting the launcher reverts it to the correct one.

- There is some lag while expanding/contracting the quick settings, which I hope can be fixed soon. This seems to the only place where there is some lag.

- Battery usage screen seems to be changed from AOSP type to stock Pixel style, and that displays strange percentages and some values like screen on time are even off by 2 hours for me, and they get rarely updated for some reason. This also happens on stock ROM. AOSP battery usage screen seems much more accurate and better. Please revert to that.

- The memory usage text on the Recents screen is black when the dark theme is turned off, but white with the dark theme turned on. It seems it would look better if it is reversed, that is white with dark theme off and black with dark theme on.

- Changing the system font sets it to bold type for a lot of fonts, like Google Sans and others. For some fonts, like OnePlus Sans it is fine for the most part, but some elements like the clock in the status bar are in bold.

- Some themed icons on the launcher were initially using the Pixel like themed icons, for Phone and messages app I think, while the rest were the custom type themed icons. Changing the launcher settings a bit changed them all to the custom type. Can we have an option to switch to the stock Pixel type themed icons? One ROM did have that option.

- While charging, the battery percentage beneath the Battery heading in the Settings app is sometimes not updated. It seems to be only updated if the Settings app is opened, and battery charge increases by a percent while charging. (It seems to be working fine while the battery is discharging though)

Installing Magisk through the recovery worked fine on this build. It did show a different error though, but worked nonetheless.

Even the 32-bit Viper4Android is working on this ROM.

Great work with developing this ROM!
[Google Pixel 7 Pro] geokilla:
How can I flash with verification and verity disabled? I already disabled it on stock Android Flash Tool when flashing the stock April build. Tried to flash in fastboot using fastboot flash --disable-verity --disable-verification -w crdroid.zip but it says it cannot find the file despite being in the same folder.
[Google Pixel 7 Pro] HiM@L:
fastboot --disable-verity --disable-verification -w update zipname.zip
[Google Pixel 7 Pro] wangdaning:
I am pretty sure you need to adb sideload not fastboot flash.
[Google Pixel 7 Pro] geokilla:
Works thanks!
[Google Pixel 7 Pro] geokilla:
Did separate ring and notification volume disappear? They're linked together and I cannot unlink it. There was the ability to separate it in the February build.
[Google Pixel 7 Pro] neroes:
if the smaller update comes out today or tomorrow, the thread title can still be changed to 9.4 ;)
[Google Pixel 7 Pro] omariscal1019:
Fixed next update
[Google Pixel 7 Pro] yurishouse:
Oh and... Not sure if you know but there's two different capt portal app on device apparently... One google branded and one isn't, the one that isn't doesn't work (opens a error page every time.)

I have to disable that one so it doesn't show up every time I try to connect to school wifi.
[Google Pixel 7 Pro] omariscal1019:
gonna take a lok at it later im might push an OTA tonight
[Google Pixel 7 Pro] 5.1:
Hi,

Only have the non google one here. Clean flash btw... 🤔

Cheers,

Sébastien.
[Google Pixel 7 Pro] halfbytecode:
The ROM should really have Dynamic Range Compression working for the audio, like the stock ROM and others have.

On the external speakers, dialogues are quite and sound effects/explosions are really loud. While playing songs from a playlist, one song is loud and the next is low on volume. It requires manually changing the volume for most songs.

Moreover, it would also be appreciated if the bootloader and radio are included in the ROM zip itself, as that would make the OTA updates "complete". Some ROMs are already doing this too.
[Google Pixel 7 Pro] wangdaning:
Maybe suggest the commits you expect it to have?
[Google Pixel 7 Pro] cultofluna:
LoL 🤣
[Google Pixel 7 Pro] halfbytecode:
I actually added a link to one commit earlier to my post, but then found it was already included in the ROM source. Removed the link thereafter.

I plan to compare the audio effects configuration and policy files of the ROM and the stock ROM next, to see if I can track down any differences and work from there.

Maybe others can chime in as well, since this is affecting everyone on this ROM as well as Lineage OS. It might even lead to damage to external speakers in the long run, as sound is often distorted and has crackling issues, due to high volume at certain times during the audio playback.

@wangdaning @cultofluna @slogar25
[Google Pixel 7 Pro] slogar25:
Lol. Whats up man
[Google Pixel 7 Pro] halfbytecode:
I just flashed the StagOS April build, and I can say that the sound output with everything working makes a day and night difference!

It seems that I should reiterate that my earlier posts regarding that were infact referring to a bug in crDroid! 😏

Other bugs in crDroid that I reported earlier should be ironed out as well. It would be really appreciated.
[Google Pixel 7 Pro] omariscal1019:
Update today

Fixing NGA and Safetynet

Added header images volume link button many extras
[Google Pixel 7 Pro] omariscal1019:
OTA Pushed!!!

Update
[Google Pixel 7 Pro] DepressedDead:
Thanks! I just flashed the last release. I don't know if it's placebo, but everything feels even more smoother :)

There's one thing, though: the recovery image appears to be broken (after flashing this update). I can reflash the rom package without issues but I can't flash magisk (the recovery just says "error in sideload package.zip status 127"). This is weird because the zip isn't corrupted or damaged; I used the same zip with the previous build.

I don't really know if it's the recovery. I tried booting the old recovery (from your first build) to flash magisk and I got the same result, it fails to flash.

Cheers.
[Google Pixel 7 Pro] DepressedDead:
Well, there appears to be something broken in the ROM preventing me from using Magisk (lol): I tried flashing a patched version of the stock boot image (latest build, of course). It doesn't work, even though I'm using the latest Magisk too (26.1).

And yes, I made sure I flashed the patched img to both slots, but same thing. The magisk app doesn't seem to be detecting the patched boot image.
[Google Pixel 7 Pro] omariscal1019:
Weird I haven tdone anything to recovery, also none of my tester has had any issues
[Google Pixel 7 Pro] omariscal1019:
Let me double check I'll let you in a bit
[Google Pixel 7 Pro] omariscal1019:
i just flashed the patched image thru fastboot
[Google Pixel 7 Pro] DepressedDead:
Did they clean flash? I dirty flashed on top of last week's update (04/19), so maybe that's the issue. I also tried to use the OTA updater and it failed at the last step ("finishing install process"). I didn't have any issues flashing the last build via recovery, though.

I didn't have any issues flashing the patched image. It flashes successfully but the Magisk app doesn't seem to detect the boot img is patched. It's as if the boot image were untouched.

BTW, I just rolled back to the previous build (04/19) and I don't have the issue when I flash (sideload) Magisk. I'll try to reflash the latest build, hopefully it doesn't kill magisk this time.

EDIT: nah, same thing. Sideloading magisk fails on the last release. I did everything as per instructions (flashed to both slots, installed April firmware etc) and it worked great for all releases until today. I think there's something missing in the system image itself (maybe a binary?) because flashing an older recovery image doesn't solve the issue.
[Google Pixel 7 Pro] omariscal1019:
ill upload the init_boot from this build so it can be easier for you guys it will in firmware folder.

just open magisk app after you send image to phone and patch from there then move it back to computer to flash from fastboot

until i figure out whats going on
[Google Pixel 7 Pro] omariscal1019:
cheetah_firmware - Google Drive

drive.google.com

cheetah init_boot
[Google Pixel 7 Pro] DepressedDead:
This is exactly what I did. I extracted the image from the last build, moved it, patched it with magisk and then moved the patched image back to my computer.

Then I ran fastboot flash boot_X patched.img (on both slots), but after restarting magisk simply doesn't work. This is what I usually do to root other phones, I don't know if its a different partition for Pixels.
[Google Pixel 7 Pro] omariscal1019:
flashing wrong image its init_boot not boot image
[Touch CDMA General] yearn:
Hey guys, my freind had a sprint Vogue and the touch screen quit working so he gave it to me. Every thing works fine but that. Iv hard reset, reflashed,tried to operate it through MyMobiler, banged it on the computer desk. Nothing works. any ideas or do I just have a new paper weight? Hes already went to sprint and said he lost it and got a new one so sprint will be no help. I really just wanted it for a genuia pig. but its no use when its stuck at the setup screen.

Thanks
[Touch CDMA General] link2009:
Had this problem before, I remember turning the power on, trying the screen, turning it off, on trying again and etc... it worked after a few rigorous tries.
[Touch CDMA General] yearn:
Iv turned it on and off probably 100 times and still no luck. plus the hard reset and reflash
[Touch CDMA General] link2009:
You could try replacing the screen with a spare part from...somewhere. Not much more I can say, that's about as far as my knowledge goes.
[Touch CDMA General] yearn:
Thanks, Im hoping it dont come to that
[Touch CDMA General] derekwilkinson:
Sounds like a dead digitizer. You're going to have to either find a new digitizer and going through the hassle of replacing it or replace the entire screen.
[Touch CDMA General] wakerash:
which part is the digitizer. I had the same problem with my vogue and bought a part off ebay which i was 99% sure was the problem. its the small electrical board underneath the dpad. There is a connection that the ribbon from the outer screen connects too.. Does anyone know where i can find a replacement for that part. The one I got from ebay looked exactly like the one from my vogue but when i plugged it in it would cause my phone to shut off. They said it was for the GSM touch not the CDMA
[Vivo X90 Pro Plus] bmw320cd:
Another update camera focused , big improve in photo and video

New Trial update 20.5v Origin OS3

Screen
[Vivo X90 Pro Plus] ef1x:
512 Gb english
[Vivo X90 Pro Plus] carzakone333:
Already updated
[Vivo X90 Pro Plus] Oswald Boelcke:
@bmw320cd Thread closed as a subject matter related on already exists:

https://xdaforums.com/t/new-trial-update-improve-camera-overall.4574191/

Please review the XDA Forum Rules with special emphasis on rule no. 5 and post in an existing thread instead of creating a new one. Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[LG G7 ThinQ  Questions & Answers] ponyoponyo950:
Hello there, everyone I'm newbie here and i wanna ask which CUSTOM ROM should i use for my LG G7 Verizon, i wanna use it for emulation (Skyline for sure, but its minimum requirements is Android 10) G7 Verizon's Android 9 really sucks, i mean the US variant of G7 got Android 10 update but mine's not. I really want to update the OS or custom ROM in order to make it more sufficient. Can you please help me how and give me full instructions please (totally noob), your help will be appreciated, thank you so much
[Redmi Note 8 Pro Questions & Answers] pilsudski:
Hi, i know miui 13 isn't officialy released for redmi note 8 pro but i saw this:

sadly the download links are dead, does anybody know where could i find this rom?
[Redmi Note 8 Pro Questions & Answers] XiaomiUser44658:
This is just a custom-MIUI ROM and it is not official. But you can find an download link on YT when you search for "Redmi note 8 pro custom rom" and click on the first channel. I can´t say anything about the safety, but the performance is a little bit worse than on the official rom.
[Xiaomi 13] nreuge:
I have "media vibration" enabled in settings. But it does not work. For exemple, I don' get any vibration watching a music video in Youtube.

Any idea??

Eu stock rom 14.0.21.0 - Xiaomi 13 12/512 CN
[Xiaomi 13] armsar1978:
Is there such a function?

Vibration only for notifications and calls)))
[Xiaomi 13] nreuge:
Yes, there is such a function, was enabled by default and worked the 1st time I used my device...
[Xiaomi 13] armsar1978:
I bought a phone, I opened the package myself, I have a global version, but there was no such function
[Windows Phone 8 Q&A, Help & Troubleshooting] Maxbrew (Nokia Lumia 520):
Hi there, maxbrew here. I just got a Nokia Lumia 520 and windows phone 8.1 (also carrier locked).

I wanted to install some applications directly from the phone itself since I don't have much access to computers. Is it possible to do?
[Windows Phone 8 Q&A, Help & Troubleshooting] JoachimP:
Hi Maxbrew,

the only way to install apps to the 520 is updating it to Windows 10 MOBILE. Without computer, that is impossible. With computer, it is a challenge, but possible and it runs fairly good. Search for Windows 10 mobile offline updater (W01M_Installer), install W10m, do all possible Updates, perform a hard reset and register it with Microsoft. Then you will be able to use the App store or sideload apps via developer mode.

Best regards,

Joachim
[HTC Excalibur] bratz:
I see the tricolored screen, and now??? how can i make the hard reset?
[HTC Excalibur] drkfngthdragnlrd:
The tri-colored screen is for reflashing an official ROM. You are probably looking for the "other" "Hard Reset" procedure. I believe you hold both soft buttons while powering on and it resets you WM installation to factory defaults...
[HTC Excalibur] bratz:
i dont know who are the soft button....
[HTC Excalibur] stylez:
Here you go with pictures :)
[Treble-Enabled Device Questions and Answers] nabulsi08:
Hello

I see that there are A and AB GSI ROMs. I want to ask what the difference is and which I need for my phone.

Thanks in advance.
[Treble-Enabled Device Questions and Answers] spider1163:
Hello,

The treble info app will tell you everything about your phone

Treble Info - Apps on Google Play

Helps you check Project Treble, A/B and Architecture for GSI installation

play.google.com
[Treble-Enabled Device Questions and Answers] nabulsi08:
Oh, thanks 👍!
[OnePlus 9] simonpeters:
Guys, i have a oneplus 9 5g phone locked to Tmobile. I can only use wifi for the mean time. All sims i have tried doesnt work. I am from Ghana and would like to remove the lock so i can use my local sim.i dont know where to start from. Any help i would be much grateful. This is my email simonpeters.600@gmail.com
[OnePlus 9] TheMadScientist:
Pretty much t mobile is your only hope. Maybe paid services Which you will not find or get any help on here.
[OnePlus 9] wizardknight:
These phones will frequently work with t-mobile resellers too, but no guarantee. You might consider mint mobile.
[OnePlus 9] bigd2442:
https://xdaforums.com/t/convert-t-mobile-oneplus-9-to-global-or-other-firmware.4277169/

You can get bootloader unlock this way and then flash global to it with the msm tool in that link.

T mobile is a bit of a pain to get the unlock code, you have to get a number from the phone using adb and then submit a request on their website using the serial and that number... A week or so later they will send you a unlock code that can be used in adb and then the normal process to unlock after that.
[Introductions] Mobiloop:
Hi all! First of all my name is Matias, I'm new here and I'm no expert modding or repairing phones. I've done some tweaks, flashing some roms in old devices but nothing complicated. I'm happy that this forums exists as I've found helping comments or threads more than once. Today I signed in because I can't solve a problem with a phone I'm trying not to throw away.

I have a Samsung J5 Prime (SG570M) that is stuck in download mode. I have already flashed the stock rom with Odin (both last version) and when the flashing ends, it says 'succesful' in Odin, but when the phone reboots it doesn't boot up, the screen remains black. It's not a bootloop because the samsung logo doesn't even appear. Any suggestion what could it be or what should I do? I already tried changing PC, USB port and cables.

Any help would be awesome, thanks in advance!
[Introductions] ze7zez:
If you haven't used the 4-file flashing firmware in Odin, you should.
[Introductions] Mobiloop:
Hey, thanks for answering! Yeah, I have used the 4-file firmware and followed all recommended steps from the sammobile guide. Don't know what else to do :/
[G1 Android Development] sonikamd:
breaking..ok, old news: RC30 (jailbreak fix)

http://www.tgdaily.com/content/view/40063/140
[G1 Android Development] hondamx525:
Curious about this. Im not in the know enough to do anything with root, but for all of you that have access, if others update, will they be able to use anything that you develop or create with access to root? hopefully....
[G1 Android Development] sonikamd:
I 'm wondering how can I prevent this. I'm in about the same boat as you honda. Root is a stranger to me... But, I'm sure it would suck if I get stuck out side of the loop :/
[G1 Android Development] neoobs:
If you look there is another thread where someone else posts what to do... although he hasn't got the files on the forum yet he is having some issues uploading them.
[G1 Android Development] quedijo:
JUST DON'T UPDATE TO RC30. It's that simple.

If you don't understand how to get root, just wait till someone (I would but haven't had time) makes a very detailed yet simple method.
[G1 Android Development] sonikamd:
Ah, I'm still running RC19 and have yet to experience Google's update process.

I thought the update was mandatory and done without user input, just a "congratulations, you phone is now a little slower!"

So we can just deny the update with the stock sw?
[G1 Android Development] JesusFreke:
When you get the OTA update, it pops up a message window asking if you want to install. You say either say yes, or "not right now". I think it will keep bugging you to install, and possibly go ahead and automatically install it if you say "not right now" enough times. (I'm not positive about that.. I just remember seeing something like that when I was looking through the source for the updater app).
[G1 Android Development] damnitpud:
I think it works like Windows updates, it gives you option to update now or later and if neither is hit in a certain time it will install it automatically. I am going to test this when my update comes. I will hit Update later and see what it does. but i have read others comments saying they never seen the update now or later window and got the new version anyhow.
[G1 Android Development] Disconn3ct:
I'm on the train right now so someone else (or me) can post detailed directions. But if you get root and rename/remove /etc/security/otakeys.zip they (probably) can't update you automatically.

While that file is in place they might be able to upgrade without prompting (anyone want to search the code for info?)

UPDATE: They -can- forcibly update you: http://xdaforums.com/showthread.php?goto=newpost&t=443328
[G1 Android Development] SmartBrother90:
google should wonder ppl do thing themselves...wen they have to come up with 3 update in less than a month....there always worried about security and not functionality..lol...i mean cmon i had to buy a new sdcard jus to get RC 29...cause it sure wasnt commin to me via OTA....i wonder wat i have to do to get RC 30..
[G1 Android Development] benmyers2941:
Correct spelling and punctuation may be a good place to start :p
[G1 Android Development] punkzanyj:
Well, I accepted RC29 and I've noticed the phone is faster and has better battery life.

I've also been very conservative with usage because I'm waiting to install and run apps from the SD card.
[G1 Android Development] mouseclone:
jailbreaking the t-mobile RC30 update

From what I have read so far it is not possible to re do the images on the G1 because of the RC30 patch from T-Mobile. Mainly because you do not have root, and the second because without root you can't remount the /system partition as RO.

adb allows you to mount the /system partition as RW. Would this not do the trick.

./adb shell
#mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p1 /sdcard vfat ro,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0

This was the out put that I got. Now to run the remount from adb.

adb remount
-
remount succeeded

now to make sure that this really worked.

./adb shell
-
# mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 rw 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p1 /sdcard vfat ro,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0

as you can see the /system directory is not in rw mode and not ro mode.

To test to see if this is the case.

vi test.push (:wq)
adb push test.push /system
adb shell
# cd /system
# ls
test.push
lib
media
framework
fonts
etc
build.prop
bin
usr
sounds
recovery.img
app
lost+found

As we can see this did seem to work. I do not have a T-Mobile RC30. I have mine jailbroken already. with the steps that JesusFreke laid out.

I was wondering if it would be possible to do the same steps but with using adb to mount the fs in rw, and then using adb push to push the recovery.img to the device into the /system dir.

doing another push of the test.push file seems to take.

adb push test.push /system
vi test.push (i incerted the leter i)
adb push test.push /system
0 KB/s (2 bytes in 0.048s)
adb shell
# cat /system/test.push
i
#

So this might be the break that people are looking for that have the T-Mobile RC30. JesusFreke I know that you said that you have one with an RC30 from T-Mobile. Would you be willing to try this at the risk of bricking the phone? I know that is a $400 question, or anyone else for that matter.

If you do try it, please let me know the results. I have a friend, whos wife has the RC30 from T-Mobile. He is not willing to risk his wife's wrath.
[G1 Android Development] jashsu:
It works on emulator.exe but will the live RC30 adb server accept remount? I notice that there are no references to remount in the official documentation. Alas I don't have any official RC30 G1 to test with.
[G1 Android Development] ballaholyk84:
Id bewilling to trythis right now. I have a Modded RC30 that I will update to the official RC30 that I am sending back anyways for defects. Anyone wanna tell me how to flash mine back to Official RC30 and Ill get to trying.
[G1 Android Development] Koush:
The RC30 you have from JesusFreke gives the adb daemon root permissions. What you listed will not work on a Google RC30.
[G1 Android Development] ballaholyk84:
Meaning that as soon as you type in adb shell and hit enter it will not even start the daemon?