yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dhacke:
Hi to all,

little update:

after two beginnings from scatch and installation of a new hdd (i underestimate the space hunger of my build environment) i was able to compile and build grapheneOS on my Linux PC. Next i tried to get wireguard support into the kernel. Sadly this step doesn't work atm. The syncing with the wireguard source worked. But the patching process itself gives a error.

From my point of view the wireguard script tries to patch the kernel but it seems to me that the directory where the script wants to work is read-only. Sadly i couldn't find the problematic directory to change the permission until now. The 'find' command didn't help, too. I will try to find it further but of course i'm open for clues etc.

The error notification in the terminal is this one:

PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=10
TARGET_PRODUCT=aosp_coral
TARGET_BUILD_VARIANT=user
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.6.0-trunk-amd64-x86_64-Debian-GNU/Linux-10-(buster)
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=QQ3A.200805.001
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES=hardware/google/av hardware/google/interfaces hardware/google/pixel device/google/coral hardware/qcom/sm8150 hardware/qcom/sm8150/display vendor/google/airbrush/floral vendor/google/biometrics/face vendor/google/camera vendor/google/darwinn vendor/qcom/sm8150 vendor/qcom/sm8150/codeaurora/telephony/ims vendor/qcom/sm8150/proprietary/data/permissions vendor/qcom/sm8150/proprietary/qcril-data-hal/qdp vendor/qcom/sm8150/proprietary/qcril-data-hal/util vendor/qcom/sm8150/proprietary/qcril-data-hal/datamodule vendor/qcom/sm8150/proprietary/qcril-hal vendor/google/interfaces
============================================
[ 99% 588/589] finishing build rules ...
platform_testing/build/tasks/tests/instrumentation_test_list.mk: warning: continuous_instrumentation_tests: Unknown installed file for module 'NexusLauncherOutOfProcTests'
platform_testing/build/tasks/tests/instrumentation_test_list.mk: warning: continuous_instrumentation_tests: Unknown installed file for module 'NexusLauncherDebug'
platform_testing/build/tasks/tests/instrumentation_test_list.mk: warning: continuous_instrumentation_tests: Unknown installed file for module 'NexusLauncherTests'
platform_testing/build/tasks/tests/platform_test_list.mk: warning: platform_tests: Unknown installed file for module 'LauncherRotationStressTest'
platform_testing/build/tasks/tests/platform_test_list.mk: warning: platform_tests: Unknown installed file for module 'PlatformScenarioTests'
[100% 589/589] writing build rules ...
FAILED:
android_kernel_wireguard/Android.mk:7: error: writing to readonly directory: "TARGET_KERNEL_BINARIES"
15:01:51 ckati failed with: exit status 1

#### failed to build some targets (01:46 (mm:ss)) ####
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] SuperITMan:
Quid on Pixel 4 non XL ? :)

Hey [MENTION=9542156]dhacke[/MENTION]

First at all, thanks for sharing! It is exactly what I'd like to have on my new Pixel 4.

I had a look on Magisk website and tried to understand how do you "pre-root" GrapheneOS for Pixel 4 XL but without any results...

When I tried with Magisk Manager on my phone, the modified "boot.img" file had a size of ~35MB instead of the initial ~60MB. Obviously, I was not able to reset the phone with the modified GrapheneOS image.

Could you please share how do you do the pre-root of the GrapheneOS image? :)
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dhacke:
Well if it's requested i can make pre-rooted Builds of GrapheneOS for the Pixel 4, too:)

Apart from that i make the pre-root in the past as following:

1. Downloaded the latest factory image from GrapheneOS

2. Unzipped it on the Computer and copied the boot image on my phone.

3. Patched it via Magisk Manager

4. Copied the patched boot image back into the unzipped factory image on my PC.

5. Edited the Installation scripts

6. Zipped the factory image again and run it with the modified Installation script to flash everything on the pixel 4 XL.

Regarding the file size of the patched boot image:

By me it's the same. But i never encounted problems cause of this. Idk mayby Magisk uses compression.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dakotah2468:
Doesn't rooting graphene os defeat a major part to use graphene vs lineage os?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dhacke:
Is your phone's bootloader unlocked? If not, AVB could have been triggered.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] lostdroider:
Yes, this is literally one of the dumbest things I've ever seen on here.

It's like creating an indestructible padlock for your gate that you don't want anyone to be able to get past and then just leaving the key in the lock.

Creating this and not warning users of how pointless this is is even worse because regular users will assume it's somehow more secure than it actually is.

It's pretty likely the GraphineOS devs would call anyone using this an absolute idiot if they ever saw it.

Here's Daniel Micay explaining why Root on GraphineOS is dumb;

"...largely defeats the purpose of core security features like verified boot and attestation including the GrapheneOS Auditor app. Not much point in verifying the integrity of the entire OS (kernel and userspace) and preventing downgrade attacks if the OS is just going to trust the persistent state with root access... it wouldn't make much sense to bother with it at all if that was going to be the case.

It also makes absolutely no sense for developers to take the lazy and ignorant shortcut of requiring direct root access to implement features. They don't have a clue what they're doing and have no respect for the security of their users. "

old.reddit.co m/r/GrapheneOS/comments/du23la/rooted_or_root/fgoab8a/
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dhacke:
God can you please change your tone? You are not forced to use it.

But if you are happier i can stop it. No problem. Mayby i should make it...
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] lostdroider:
I wouldn't touch this, thankfully I'm not forced to use it.

I'm disappointed to see a senior member releasing a modified version of a secure OS - after making it insecure with no warning or heads-up to users who don't know any better.

I feel my tone is more than fair in this instance.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dakotah2468:
Senior memeber just means you have been here for awhile doesn't even mean active. Thanks for confirming what I thought.
[Realme X2 Pro Guides, News, & Discussion] oreopie:
Firstly, I would like to thank [MENTION=5786839]karthick mostwanted[/MENTION] for his work and a thumbs up for keeping Lineage OS updated.

I have an Indian Unit of X2 Pro with 128 Gigs of RAM and I got the ROM working with FP and the payment apps at once. Everything works good here. Only thing which I did not like is the camera, so I'm using PixelPlus GCAM on this ROM.

Coming to the steps (assuming ADB & Fastboot drivers installed) -

1. Unlock the Bootloader. For the same Install the In Depth Test app (pm if you do not get the links for the app on Google) and apply. After a successful review message on the app, use the following commands.

adb reboot bootloader (For reboot into fastboot mode)

fastboot flashing unlock

Select the confirmation dialog on the screen and its done. Then type fastboot reboot for the phone OS to boot. It will erase all your data too.

2. Next step is to install TWRP img file by Mauronofrio (Google it). Download vbmeta.img also, you will get in LOS thread downloads section. Copy the recovery file and vbmeta into the ADB folder where the powershell/cmd is running so the you can fetch it. Reboot into the fastboot mode and give the following command.

fastboot flash recovery recoveryfilename.img

DO NOT REBOOT YET. Immediately type fastboot flash --disable-verification vbmeta vbmeta.img and enter. Don't reboot, with help of Volume and power button combination, boot directly into recovery. Remember, do not reboot phone in any other mode or even the present OS because it will wipe the recovery installed.

3. Format Data. (Don't Wipe, Use FORMAT DATA Option). Wipe Cache & Dalvik.

4. Keep the Files in a USB Storage such as Lineage OS, Magisk 20.3, Open Gapps Nano ARM 64.

5. Insert the USB drive through an OTG and go to TWRP mount option and mount external storage. It will start showing files. Now go to install and select OS. Wait, don't run now. Add Gapps to the same queue and then run.

6. After successful installation, wipe cache and dalvik and reboot your phone.

7. After you setup everything, again boot into TWRP recovery and install magisk 20.3.

You are done and all set !

Note - Do not remove/uninstall system apps using root access in LOS, it may break. Happened with me when I tried to uninstall DuckDuckGo, it went into bootloops.

Will be happy to answer any doubts for this installation. Comment below if you need further help !
[Realme X2 Pro Guides, News, & Discussion] asusgarb:
Do you mean by using apps like titanium backup, systemapp remover or similar?
[Realme X2 Pro Guides, News, & Discussion] Benjamin Kuruvilla:
Did you rooted with new lineage OS 18 ?
[Samsung Galaxy Watch] Saxithon:
Hi all,

After flashing my GWA2 (SM-R830) following this guide to change my CSC, there's now Green Writing on my Watch whenever I boot the watch. In addition to that, OTA Updates are now failing.

A person in that post has the same issue as I had and fixed it by flashing stock firmware but that doesn't seem to fix it. I'm back to BTA1 and the green writing still persists as well as OTA still failing. The watch is fully working, except for OTA and said writing.

Anyone got a lead on why that is and possibly how to resolve it?

Edit: Solved it by reflashing it and leaving "Auto Reboot" ticked.

Image of the writing:
[Samsung Galaxy Watch] adfree:
Engineer Bootloader... sboot.bin from Combination Firmware...

This is what you see...

Rollback Prevention crap...

Later more...

Best Regards
[Samsung Galaxy Watch] Saxithon:
Is that reversible? or am I just stuck with non-working OTA?
[Samsung Galaxy Watch] technoyama:
Yes it's reversible. Flash this firmware using NetOdin https://drive.google.com/open?id=1ZaoBm2hFXT2QTeZxrS8j4sqqgVyp6Iqo . After that, use Galaxy Wearable to update Tizen to the latest version.
[Samsung Galaxy Watch] omocom:
I have exactly the same problem with an Active 2. Can someone point me in a direction toward Firmware to re-flash an 820 too please? (is this just leftover from the combination firmware I used during a region change?)
[Samsung Galaxy Watch] Saxithon:
I simply reflashed the 3-multi files and kept the "Auto Reboot" in netodin ticked.
[Samsung Galaxy M30 Themes, Apps, and Mods] Azamsm:
Samsung Flagships has this blur ui elements in app drawer, or in notification shade. I know there must be some code in the system that enables it but in budget phones- it doesn't exist. It's just dimmed. So any Dev know how can blur UI elements be enabled in budget Smartphones like M30 itself?

Any ideas, suggestions or solutions will be much appreciated.
[Touch Diamond, MDA Compact IV General] mcseven:
Hi *,

I installed the latest 1.93 rom, german, onto my diamond. Unfortunately,

now the direct push functionality does not function anymore. I installed

the CA certificate, configured the server and switched on WLAN.

When launching Active Sync, it will sync with the server three times (!)

in a row and then show "last synced on [...]". Mails being sent to my

inbox will onlypopup in outlook, not on the device unless manually sync'ed

via send/receive.

ROM 1.37 only synced once and then showed "connected to exchange".

Mails being sent to my inbox will popup on the device and then on the

outlook running pc.

can anyone confirm that or perhaps offer a solution?

Did a hardreset without any luck. Since I dont need touchflo,

I'd revert to 1.37 if nothing can be done about active sync...

bye,

seven
[Touch Diamond, MDA Compact IV General] silat27:
Hi,

I´ve installed ROM "Diamond_bElite_Premium_0.97_fixed_040C_by_bepe"

everything works fine, except that I am not able to activate microsoft direct push. It´s grey in the communication manager and can not be enabled.

Do I have to activate this on a different way?

please help.

HTC Touch diamond
[Touch Diamond, MDA Compact IV General] darthbane2k:
Push works just fine. Im connected to my exchange server over the air and everything works via activesync as normal
[Touch Diamond, MDA Compact IV General] LandyMan:
I am having the same issue ... did you manage to sort it out?

Thanks
[ASUS ROG Phone II Questions & Answers] Biedronczak:
Hi i have issue with Areocooler. In armoury crate speed slider is on full speed, but Fan dont blow on full Speed. Its werid because before Updating i to A10, there was clearly noticable that Fan blow cold air i to back of phone. Now its barley noticable.
[Samsung Galaxy Watch 3] pzman89:
I know this watch just came out but I'm thinking about getting the LTE version of the larger size. Does anyone know if LTE is completely disabled will the watch get the same battery life as the Bluetooth only model? I don't really have current plans of using it but would like it there if I change my mind. Maybe someone has a similar experience with one of the other galaxy watches?
[Samsung Galaxy Watch 3] kodiak799:
I have the LTE version and have not activated it with a carrier. With AOD and screen brightness maxed, no power saving or other optimization....I have 63% battery left and it tells me 1 day, 4.5 hours remaining. I have the larger 45mm watch. That's basically no active use outside a couple of notifications.

I think my wifi is off and watch is connected via bluetooth to phone. You should easily get a day, but probably not nearly two days. But note this is accomplished mainly by limiting you to 15% brightness in DIM mode. It's only a 340mah battery. Seems to take about two hours to fully charge.
[Xiaomi Mi 10 Pro  Questions & Answers] sm1232:
How is the battery life of Mi 10 pro?

Can everyone post their battery comsumption of Mi 10 pro here.

Mine : standby time (screen off) almost 1 % a hour,cause of draining is Phone idle.
[Xiaomi Mi 10 Pro  Questions & Answers] typos1:
I m finding it to be extremely disappointing - I dont play games, I rarely watch videos, yet just half an hour of calls, 20 mins of browsing a bit of whatsapp use and some texting and my battery can lose 25%.
[Xiaomi Mi 10 Pro  Questions & Answers] sbetatester:
Mine seems to be amazing. If i dont play games my SOT will be above 7-8 hours with 144hz on.

Usually my SOT is 3-4 hours with 3 hours of voice calls as well and 30-40% left.

Wifi, mobile data, gps, bluetooth &144hz refresh rate settings turned on.

View attachment 5145685
[Samsung Galaxy Note 20 Ultra Accessories] advocate2:
I used the Amfilm Tempered glass protector for my Note 9, but see that their protectors for recent models go for $39. Wow. I think I paid $12 for the Note 9. With the new Gorilla glass on the Ultra, do folks think I still need a glass protector, or would a film type protector be enough? Any recommendations?
[Samsung Galaxy Note 20 Ultra Accessories] jah:
The Ultra is so expensive that I decided to get the Ultimate Shield protector x 2 with full adhesive. With 10% discount UK price is £27
[Samsung Galaxy Note 20 Ultra Accessories] craigels:
Just out of interest is a screen protector needed with this new stronger glass?
[Samsung Galaxy Note 20 Ultra Accessories] princeasi:
To avoid the possibility of micro-scratches, I'd still invest in a good SP.
[Samsung Galaxy Note 20 Ultra Accessories] oneandroidnut:
Anybody know if the ultra comes with a screen protector pre installed??
[Samsung Galaxy Note 20 Ultra Accessories] raul6:
Not for sure. Some reviewers mention it exists some don't mention it at all. For now,50/50
[Samsung Galaxy Note 20 Ultra Accessories] advocate2:
I've never used a protector that needs UV to attach. Are this type that much better than the regular Tempered glass protectors?
[Samsung Galaxy Note 20 Ultra Accessories] felloffthetruck:
No. they do not come with the factory installed protector like the S20 Ultra did. Just a thin peel off film like on the back of the phone.
[Samsung Galaxy Note 20 Ultra Accessories] oneandroidnut:
Ummm that's what the note 10 and s20 had
[Samsung Galaxy Note 20 Ultra Accessories] Snowleopard1900:
I am not sure, I am using a Whitestone Dome Tempered Glass screen protector on my Note 8 and ordered the one for the Note 20 Ultra...... Whitestone Dome protectors come with a UV light in the kit and I have been very happy with them. I only had to replace it on the Note 8 1 time and it was my fault for dropping the phone.... The phone made it through it fine with zero damage to the screen, but they are expensive.
[Samsung Galaxy Note 20 Ultra Accessories] Mr. Orange 645:
For now, I just ordered a 2-pack of the Ringke Easy Dual screen protectors for $10. I loved them on my Note 10+ and my wife's S10+.

I also used Whitestone Dome on my Note 10+. I liked it, but it certainly affected the fingerprint sensor.

I wont be spending $65 on Whitestone Dome this year (although it's 20% off right now on their site).

If there's some decent competitors to Whitestone Dome for the Note 20 Ultra, like there was for the Note 10+, I may consider one of those.
[Samsung Galaxy Note 20 Ultra Accessories] advocate2:
It looks like AmFilm has a UV application protector coming out:

amFilm Ultra Glass Screen Protector for Galaxy Note 20 Ultra, (2 Pack) UV Gel Application, Tempered Glass, Compatible with UltraSonic FingerPrint Scanner for Galaxy Note 20 Ultra (2020) that's going for $39.99 at Amazon. It won't be in stock until 8/25. I just ordered the Spigen wet application film protector until the reviews come in on the AmFilm. I have the Sammy LED Wallet case so the front of the phone is mostly covered when not in use.
[Samsung Galaxy Note 20 Ultra Accessories] felloffthetruck:
No, the S20 Ultra had a factory install plastic screen protector that was pretty decent.

The Note 20 ultra only has that thin plastic to protect the screen during shipping, two different animals.
[Samsung Galaxy Note 20 Ultra Accessories] allklrnoflr:
Ringke is what I ordered as well, Have it on my 10+ and the installation is so easy-
[Samsung Galaxy Note 20 Ultra Accessories] Mr. Orange 645:
The only thing I don't like about the Note 20 Ultra version is that it's the "Wing" version, so it wraps around the edges of the device. I'd prefer it stop at the edge of the screen, but it will do for now.
[Samsung Galaxy Note 20 Ultra Accessories] JLine05:
If anyone is interested in the dome, they've got a deal right now - 2 pack for $52. Need to use code Note20...Probably doing it myself, they are the best I've used.
[Samsung Galaxy Note 20 Ultra Accessories] TheXclusive814:
Did those Ringke screen protectors affect the fingerprint reader?

---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------

Did the fingerprint reader still work?
[Samsung Galaxy Note 20 Ultra Accessories] Mr. Orange 645:
No. They're just a thin TPU screen protector.
[Samsung Galaxy Note 20 Ultra Accessories] TheXclusive814:
I emailed Ringke and they said that the one for the note 20 ultra should work with the fingerprint scanner. We shall see
[Samsung Galaxy Note 20 Ultra Accessories] Mr. Orange 645:
They definitely will. I'm.sayijg from experience with the Note 10+ and the S10+, which both use the same fingerprint reader, that they have no effect on the fingerprint reader.

It's only affected when there's an air gap between the screen and the screen protector. These are a film that applies directly to the screen.
[Touch Diamond, MDA Compact IV General] blade80:
Hi!

I have installed SmileySMS on the phone but it doesnt work that satisfying. The only thing that happens is that my messages comes with some random smileys now but I have no control of which ones I can use myself when I sent an sms. What program or addon do you guys use for this to work like on a normal mobile-phone? I want to be able to choose frome the smileys that exist.
[Touch Diamond, MDA Compact IV General] uniqueboy:
You could try using "TouchPal" (google it) a great sip with a slide out smiley page, or you could try "Vito SMS", not used the Vito SMS myself, never felt the need for it,but I do believe it has a smiley option.
[Touch Diamond, MDA Compact IV General] blade80:
Thanks! It worked perfectly
[Android Head-Units] dranias:
Hello from a new member.

Junsun V1 Android 9.0 2G+32G DSP

Model: 8227L

Android Version 9

Kernel Version: 3.18.79 (gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05))

Build number: full_8277L_demo-userbug 9 011019 1550113051 userdebug

Custom build: version alps-mp-04.mp5

MCU : TS907.190518(H)

(cannot ling screenshots of specs in the site?)

I have a weird unsolvable problem with my Junsun V1 Android 9.0 2G+32G DSP which I bought to replace my old 7" unit.

When I fitted in my car, I use the RCA outputs connection cable driving a processor and then the amps, it would make a loud thumping noise through the system whenever I changed mode on the screen (see Youtube video https://www.youtube.com/watch?v=aHNONRLvbPU). It does this on the bench test as well.

Sound through the normal speaker outputs is clear and without any problems.

On investigation with a multi meter, I found that every time I changed mode, the power Amp Cont. supply would switch on and off, thereby creating the thump through the speakers. Even if I use the antenna power supply which is constant even with mode change, it still thumps, as RCA outputs convey the on/off thump of the AMP Cont through them.

After referring this problem to the seller, he said it was a mainboard problem, and I returned the unit which he exchanged for a new unit. However, the new unit has exactly the same problem ( it was a new unit, as I made sure of certain markings on the returned unit).

Seller sent me a Software Update, which did no changes at all!

The seller then finally informed me that the AV cable adapter RCA out and Amp. Cont. connections are not compatible with this unit, software problem, even though they give the AV connector together with the unit!

Has anybody had a similar problem with a similar unit?

I have tried changing various parameters in the factory settings with no luck.

Could it be a simple setting adjustment with the unit which not even the seller can help with, as in the end I will have to return the unit.

I could use a high low converter which ultimately degrades sound further.

Would appreciate any input. thanks.

[/IMG]
[Android Head-Units] dranias:
specs

:good:
[Android Head-Units] dranias:
Firmware update

I have the firmware update for this Junsun V1 2020 unit as well if anyone needs.
[Android Head-Units] britain4:
I’ve got the same branded unit, 2gb+32gb Junsun V1. on my car the antenna power is retained from the original head unit and I’m not using amps at the moment so never tested the outputs on mine to compare.

Firstly I would try wiring the remote wire from the amp to a permanent 12v feed to see if the thump still happens.

If it goes away it’s up to you whether you want to send it back as it’s clearly not “right”, personally I’d rather keep it and try and find a switched live in your car to power the amp remote instead, or use the amp output from the Junsun with a relay rather than connecting to the amps directly.
[Android Head-Units] dranias:
Hello

Have tried that. Wherever you give remote power for the amps from, the thump unfortunately is carried through the RCA's from inside the unit from the mode change. It causes an on/ off in the Amp Cont power, and the RCA's out pick it up from the mainboard of the unit. Have thought of maybe sourcing the RCA outputs directly on the board before they reach the TDA7851L amp, but don't want to dive that deep yet :(
[Android Head-Units] marchnz:
Not Android Auto, requested thread moved to Android head units.