yashsingh1/xdaforums huggingface dataset:
[OnePlus 6T  Accessories] BuLLeT_PrOOf_wAlleTz:
T-Mobile prices them exactly the same as OP website....

After shipping $ handling
[OnePlus 6T  Accessories] se7ensde:
No they're not the puregear tgsp is 40 bucks by itself at t mobile when it's only 20.95 for the official from OnePlus.
[OnePlus 6T  Accessories] metawave:
I got it Free along with the Phone on the launch day from the store. Question is, do the USB-C bullets work even with the Oneplus 6 through the USB C-port?
[OnePlus 6T  Accessories] tengtengvn:
What's so great about these buds? From the look of it, the cable is thin and probably won't last a few months.
[OnePlus 6T  Accessories] metawave:
If you want to go Truly Wireless within budget, Samsung Galaxy buds is a nice option, even if you don't own a Samsung phone.
[Google Pixel 2 Questions & Answers] harisyks:
Hi guys,

I have not received the November update, and I always received latest security patches on the day of release, so it was strange to me.

Tapping the "Check for updates" button shows no update.

I've been suspicious so I booted into bootloader and it greeted me with an error: "ERROR: OPERATION DENIED".

However, this only happens when I boot into bootloader the first time from booted phone. Every other time the error is not there. I'm not sure if that's the cause of the update not coming, but my gut feeling tells me that.

Current system I'm running is October 5th and I've flashed that via PC since I've had an unlocked bootloader + root after which I've re-locked it and wiped the phone so it's been completely clean.

I've tried to flash it manually via PC without wiping the phone but cmd throws me an error saying some versions are not compatible.

My questions would be:

- has anybody had this error thrown in the bootloader? Since Google didn't really help me

- could this be the cause of the update not coming?

- is there a solution apart from a wipe?
[Samsung Galaxy S7 Edge Questions and Answers] anthonyr1.:
i keep hitting my hotspot limit and it get throttled down to nothing. i have been scouring the net and coming up empty . does anyone no a solution or work around. not currently rooted but will if need be .

thanks
[Google Pixel 2 Questions & Answers] :
Hello guys,

I'm using a Google Pixel 2XL since the beginning and I have a small issue with the Google app on my phone. It does not send me any notifications. The most important for me would be the current weather notification, so I can see the weather anywhere I pull down the shade. I know there are some weather apps that can do the trick, but I prefer the default one.

I have tried everything to solve this issue:

Soft Reset

Factory Reset,

Safe mode

Clear the app's cache and data

Signed up to beta, I thought it help but did not

I have made sure no app blocks the notifications

Uninstall the app's update and install back again

I have even posted a thread on Google's help forum, nobody has responded back yet. And also sent a feedback to Google and sent an email too. Still no answer.

Do you guys have the same problem?

Any idea what else can I do?

Thx
[General Topics] Paul_Days:
How can I remove certain apps from the SPB Mobile Shell launcher.

I know for instance that in the Start Menu, all I have to do is go to the System folder and remove the aliases from the Start menu folder....How can I do the same for SPB Mobile Shell.

All in all I just wanna keep the apps that I use and remove the clutter.

Paul
[General Topics] NiteStalker:
There are several articles in the development and hacking section covering the customization of Mobile Shell, look at those, they will answer this and more.

Also goto spbclub.com, its a forum dedicated to spb programs.
[Honor Note 10 Questions & Answers] bil20:
I am looking for a decent stylus to go with the phone for taking notes etc. Are you currently using anything that you'd recommend?

Will the huawei M pen work with the phone?
[Android Studio] MyburghRoux:
Hi, I have two PC's and 3 android devices, I want to know if it's possible to have android studio open and run app directly on a android device via USB instead of emulator since my PC only has 2 cores, or if I can run the emulator on my laptop which has 4 cores but limited space and screen resolution and no GPU-reason for using main PC- and code on my main PC.
[Nook Touch General] Renate:
I'm always a big fan of eInk.

The city of Cambridge, MA has a pilot project for eInk displays on bus shelters for bus information.

The two foot displays are impressive, I want one!
[Nook Touch General] _ig_:
those must be super expensive...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Useful Resources

How to report bugs:

It is incredibly useful if bug reports are done in a proper way. That saves everyones time and will ultimately lead to a faster bugfix (hopefully).

The following guide from [MENTION=6842057]nathanchance[/MENTION] is a very good guideline on how to properly report a bug!

https://github.com/nathanchance/Android-Tools/blob/master/Guides/Proper_Bug_Reporting.txt
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HellraiserNZ:
Gonna give this a go now. Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
Sweet, thank you sir!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
fsync toggle?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] frewys:
How much do the 3 and xl differ on kernel level?

Would this flash and work on the 3?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Chronzy:
Working on mine
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] old_fart:
RE: " - Flashing the kernel will keep root ! "

Who had done the steps and ( then the pixel ) lived to see to see another happy day ?

( assuming magisk ( root ) is installed and and has been happy for days... )

turn security pin off, fastboot twrp_323 image, twrp the kernel zip, twrp the twrp_323 zip, reboot back into twrp, wipe the cache to see that the finger presses workie, boot to system, re-verify root is okay, buy the man a beer...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Komodoketavaran:
May I ask if you could add zram zstd from Pixel 2 XL ? It is a BIG improvement for ram management.

Gesendet von meinem Pixel 3 XL mit Tapatalk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] _LLJY:
Kernel is unified, the main difference is the display driver (ftm5 vs sec_touch)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I can include it, but I recommend to leave it on. I know several people that suffered from corruption when something unexpected happened and their device shutting down.

I´ll include the toggle but leave fsync on by default, just like the wakelock blocker.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
thanks for chiming in [MENTION=234314]frewys[/MENTION] :)

also thanks for confirming it works on the regular pixel 3 too [MENTION=2696401]Chronzy[/MENTION]
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
yeah it works :) I tested it.

In theory you can flash the kernel "on the go" without a computer and keep root via franco kernel manager. which is pretty handy.

although I only recommend to tinker with pixel phones when a computer is nearby and available. :good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
yes that´s one of the things I definitely wanted to try in the nearby future. it was my kernel that firstly introduced it on the pixel 2 xl ;) but memory managment on my unit is not as bad as I saw in some reviews/videos.

Additionally I think the underlying cause, when Pixel 3 cannot hold more than 3 apps in background is a bit different than pixel 2 xl "just having 4gb of ram".

But I´m sure there is room for improvement. Just wanted to use the phone as it is to get a baseline of how it works before I start modifying all sort of stuff.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
Thank you :) that'd be great
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Semtronix:
Can confirm it's working. I flashed with FK Kernel Manager. Root still intact, Magisk and all still installed.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c_86:
Worked for me to flash try exkm

Root remainder. Was hoping the kernel would fix an issue with magisk not passing safety net whenever hit the check safety net. It asks me to download. I hit yes and then it fails immediately was like this on stock as well
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Komodoketavaran:
That would be great. It is very bad on my unit.

On my P2XL there are nearly no redraws with your kernel :D

Gesendet von meinem Pixel 3 XL mit Tapatalk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Daisymae:
When I followed those steps my phone would only boot straight to twrp with no touch. Had to flash factory boot.img to get it back.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] elreydenj:
EX is out. Swipe to sleep incoming?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Tomorrow :) I just came home from a long night :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
What's the performanced tunable in exkm?

Never payed attention to it

Btw disabling gentle fair sleepers increases UI responsiveness

echo "NO_GENTLE_FAIR_SLEEPERS">/sys/kernel/debug/sched_features
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
It’s a performance daemon. It controls all sort of cpu/heat stuff in the background. Just leave it enabled.

Gentle fair sleepers.

Did you actually try it on sd845 and verify increased UI responsiveness with multiple uibenches for example?

This “tweak” came up when interactive and HMP were still used. EAS works different and I don’t think that it’s really that beneficial for EAS.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
honestly i just went by how it felt

i had it enabled for a day and disabled and i noticed better performance especially multitasking
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
for me multitasking performance is how many apps the phone is reliably be able to hold in memory.

This setting doesn’t affect that at all.

edit:

Maybe you refered to something else?

I won´t change that by default in the kernel. It´s relatively easy to switch it off via EXKM (user settings) or a magisk post boot script.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
[MENTION=3428502]Freak07[/MENTION] is it safe to flash this kernel over the ElementalX kernel or should I reflash the image first?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I was not near a PC since Friday so didn’t take a look at the ex kernel installer Zip.

It should be good to just flash my kernel over.

But in case you face issues it’s probably handy to have a PC nearby to be able to flash boot.img
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Kernel Update with wake gestures will drop soon :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] skiierx131:
Flashed with the "2a. Boot to TWRP and flash my kernel.zip plus magisk.zip" method, no issues here :good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] elreydenj:
Newest update fails to flash in TWRP..... Anyone else?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] skiierx131:
All good here.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
nope I always flash the releases before they are available for download.

maybe reflash your stock boot.img and start again from there.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] elkay:
Installed successfully on November update fully flashed (minus wipe). Working fine, except I notice that sometimes the homescreen feed on the left closes and restarts when scrolling through it. Not sure if it's signs on the ongoing memory issue still or what. Stock didn't do that from what I noticed.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bggold:
Why lately am I getting the unpacking ram disk failure. I tried to flash v1.70 over ex v1.00 with exkm. running magisk v17.4 r16 of kantjer.

This started last week. I can usually flash from twrp. But in order to get ex v1.00 flashed I first had to flash stock boot.img. got the same errornin twrp.

Edit:. This has happened with different kernels.

Any ideas?

Thanks
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] janedoesmith:
I was getting the same error. What fixed it for me was uninstalling Magisk before flashing a kernel then flashing Magisk afterwards.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bggold:
I find it easier to boot to recovery reflash twrp, kernel then magisk. No need to uninstall magisk. Hopefully someone will she'd some light on the issue.

Thanks
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] janedoesmith:
Oic. I'm somewhat new to this so excuse the ignorance. I'm always in search for easier or a better way. When you say "boot to recovery", are you booting to the stock recovery or twrp recovery? Also, when you say "reflash twrp" are you booting into twrp using the twrp.img or flashing the twrp.zip? TIA.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bggold:
I have twrp flashed to recovery so I usually can do it all without the PC. I am always near one just in case.

Boot to recovery (twrp already flashed)

From twrp install

1. Twrp.zip

2. Kernel.zip

3. Magisk.zip

This is done only because lately I have been getting an error when trying to flash from exkm. Usually you can just flash a kernel from one of the managers without having to go into recovery.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] webleeper:
Worked perfectly, thank you
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lohanchien:
Yeah use a file explorer. When you click the plus to add the module just pick a file explorer on the Open From menu. It'll work
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Tried with Solid Explorer and Magisk doesn't show up as an option to open it with. Another ideas?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lohanchien:
Don't open it with solid explorer first. Go to Magisk and click on the plus to add a module. At that point you can pick solid explorer on the left menu to open a file with. You can then pick the zram module.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Worked, thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] codygs83:
Forgive me if this has been asked, but what benefits will I see from using this mod? I flashed it with no issues. I don't feel a difference with my useage so far. But thank you for this ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gvsukids:
I installed this via magisk, but when I look at zram in fk kernel I still see it at 1024
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
With latest kernel I have noticed remarkable less battery life, like 10-20% less.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ktdt00:
I've only run this kernel a few times over the last year but I installed it 3.4.3 on Blueline last week with a completely stock July ROM. Over the next 24 hours I noticed a couple instances of heat where I felt the phone get hot in my pocket, something that has never happened to me before.. I continued to use it for an additional 24 hours monitoring battery consumption closely with 3C and AccuBattery. I had one more instance of heat and also noticed very consistently that my screen on discharge speed was 17%/hr and screen off was 1.2%/hr. With stock I had months of history with 11% and .8% respectively. I also noticed that Nova launcher had become my top battery consumer by far when on stock it rarely made the top 10. (not scientific I know...). After 48 hours I reflashed the stock boot.img from July, reinstalled TWRP and Magisk. All my numbers went back down and in the last several days I've had no heat ups. I know everyone's experiences will be different depending on ROM, usage patterns, etc. but that was my experience. I am not a gamer or heavy social media user. I check FB and the news/sports via browser about once an hour, use Android Auto for nav in the car, talk on the phone a few times a day, take a picture or two, etc.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Face_Plant:
Have you actually changed the ZRAM size to 2048 and set it to apply on boot? The point of the module is to make apply on boot work, not to actually change the ZRAM size/compression algorithm for you. Without the module you'd have to manually set it every time you reboot your phone.

Did you do a cache wipe after installing? Did you change any settings?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
I have noticed heating also.

I did not cache wipe as I did the upgrade with EXKM.

I only changed the setting of the ZRAM to lz0. That maybe be that. I gave up on changing ZRAM and now my phone isn't heating.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Face_Plant:
Interesting. For me it was like this:

Without the module I had to manually set the ZRAM size/algorithm via EXKM every time I rebooted my phone, even if it was set to apply on boot. This sure did get old...

After installing the module via Magisk manager and rebooting, the ZRAM size/algorithm had once again reset themselves to the stock values of 1024/lzo.

The only difference for me with the module is now after changing the size/algorithm with EXKM and setting it to apply on boot, it actually sticks now after rebooting. The module did not change the size/algorithm at all, only lets my settings stick.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
How do you cache wipe without going to TWRP?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Face_Plant:
I'm not sure if it's possible, but I could be wrong. It may not even be necessary unless you're upgrading from another kernel, but I do them out of habit and to make myself feel better because I'm starting off with a somewhat clean slate.

If your battery life or performance decreases after installing an update to a kernel or anything else that has a huge impact your phone's battery life/performance, then a cache wipe is usually the first troubleshooting step that should be done to see if that fixes it before reporting the issue to the developer. After wiping the cache your battery life will be slightly worse for a few days, but will go back to normal (or maybe be even better) after a day or two.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
Strange, never had this issue before. Anyone got any idea why?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
Maybe you are on Android Q?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
Nope. Dirty Unicorns. 3.4.0 flashed fine. 3.4.3 isn't.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
Now I remember I had kind of this with Franco a long time ago.

Maybe just try EXKM, I seems to work when Franco isn't.working.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
I don't, but [MENTION=4544860]osm0sis[/MENTION] probably does. AnyKernel is his baby, as is the flashing code in FKM. I don't know what he's comparing the device on.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] osm0sis:
It just checks the device name props, so you should compare what's in the DU build.prop with what's in the zip anykernel.sh and see if something's off.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
Hmm. Do you notice anything odd?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
That's a file dump. What do you get when you run

getprop ro.product.device

in a terminal emulator.

It's normally the same as the file dump, but not always.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
crosshatch

Edit: so it's a FK manager issue, exkm flashed it fine.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
That should match. The actual code that does the check is in update-binary

if [ "$(file_getprop /tmp/anykernel/anykernel.sh do.devicecheck)" == 1 ]; then
ui_print "Checking device...";
device="$(getprop ro.product.device)";
product="$(getprop ro.build.product)";
for i in 1 2 3 4 5; do
testname="$(file_getprop /tmp/anykernel/anykernel.sh device.name$i)";
test "$testname" || break;
if [ "$device" == "$testname" -o "$product" == "$testname" ]; then
ui_print "$testname";
match=1;
break;
fi;
done;
ui_print " ";
if [ "$match" != 1 ]; then
abort "Unsupported device. Aborting...";
fi;
fi;

file_getprop is defined in ak2-core.sh

file_getprop() { grep "^$2=" "$1" | cut -d= -f2; }

which extracts the following line from anykernel.sh and returns what follows =

device.name1=crosshatch

(device.name2 is blueline, but the code should break after it matches on crosshatch)

Did you try it again?

---------- Post added at 11:25 PM ---------- Previous post was at 11:21 PM ----------

I think it's more likely to have been a gremlin of some kind. I use FKM all the time and didn't have an issue. The code that threw the error isn't FKM code, is all in the kernel zip.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
I see. Interesting. Cheers for that. I tried a few times even after rebooting but it wouldn't work. Tried with EXKM and it flashed fine.

I'll report it to Franco.

Thanks for checking btw. Much appreciated.

Ah, just saw your edit. Very odd.

I tried again only EXKM is working to flash it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] osm0sis:
Yeah that's super weird. EXKM and FKM are both using topjohnwu's new switchroot binary (probably due to be renamed to not be confused with the Nintendo Switch mod), and the device check is fully working fine here on my OP6T with FKM, latest Magisk Canary and the latest FK AK3 zip.

Can anybody else in this thread verify the issue on the same or different ROM?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] muttonhead411:
Just flashed 3.4.3 with FK. Worked just fine. On stock rom with magisk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
As I said, no issues here (on that score) - but I'm on rooted stock.

---------- Post added at 02:38 AM ---------- Previous post was at 02:29 AM ----------

You said 3.4.0 worked? Can you try that version again? I'd have to check the release notes for the exact timing (@Freak07 ?) but I'm pretty sure he switched to AK3 from AK2 recently. I wonder if that has anything to do with it.

Also, if I'm not mistaken, Freak07 is running DU as well, although I don't know if he tests with FKM every time.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lukefgoogler:
Given that EXKM and FKM are wonky when switching ZRAM compression algorithms, lzo-rle is probably best for 90% of the Android use cases, and lzo-rle is standard in Linux 5.1, should we be campaigning for the next Kirisakura build to have lzo-rle as default instead of lz4? Seems most of the posters who care are trying to switch to lzo-rle, and having issues using kernel managers.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
[MENTION=271629]jcm[/MENTION]11 - no version is flashing via FK anymore. Strange.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dijia1124:
Set to minimum brightness but the screen sometimes changes itself between minimum and brighter... Turned off adaptive brightness and it keeps minimum ..Seems I'm the only one get this issue ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
What version of FKM? Also what version of Magisk are you running?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
FKM 4.4.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Should have tried this sooner, but the key was that previous versions were no longer flashing successfully. [MENTION=4544860]osm0sis[/MENTION]

I hadn't tried flashing with this version of FKM (it's a very recent update). I can confirm that it errors out on me as well with "device unsupported".

I have some other issues with this version as well. Guess I'll have to pay GitHub a visit.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] osm0sis:
I'm using FKM 4.4.1, latest Magisk Canary and still no issues on my 6T, so must somehow be some peculiarity with this device?