yashsingh1/xdaforums huggingface dataset:
[Wileyfox Storm] mes2k:
Still good :)

Over night with Airplane mode I lost 1% battery in 8 hours. Over the day it also seems good. With kipper it's always hard to say, because the screen consumes a lot of battery when I use the phone.

Another issue:

The FM radio app is not included. kipper has a built-it FM module.
[Wileyfox Storm] PS-DEV:
Thanks for reporting , this is small issues, and i will try to fixing as soon as !

*Also for Germany language , maybe will add in the next UPDATE!

Also, for FM radio, will be included in the next update! :D

Stay_Tuned.
[Wileyfox Storm] PS-DEV:
New build of is UP !

Changelog:

November Security patch.

Pixel Navbar + animation .

New Settings layout .

Improvements and Stability .

Fixed Audio effects.

Added FMRadio .

Disabled NavBar by default.

DOWNLOAD :

https://www.androidfilehost.com/?fid=889964283620767810
[Wileyfox Storm] JonnyTech:
Great work! Is there a 8.1 update available? Thanks.
[Wileyfox Storm] PS-DEV:
Yeah , but have RIL (Sim card) bug .

i will trying to fix ASAP.

if you want to try 8.1 (:

https://www.androidfilehost.com/?fid=673791459329069182
[Wileyfox Storm] JonnyTech:
Thank you, but unfortunately I have broken the USB port on my phone so have to find a way to fix it first :(
[Wileyfox Storm] mes2k:
What kind of Bug?

I have been running the 8.0 Version for weeks now. Stable and fast :) -- THANKS!
[Wileyfox Storm] vel_tins:
running Oreo 8.0, which is fine so far.

Is this project still alive?
[Wileyfox Storm] Infiniterum:
Can someone give me a link to the TWRP they are using to flash this OS.
[Wileyfox Storm] AHMED ZAKADAN:
difference ?

what is the difference between this current thread and this thread in the link

https://xdaforums.com/wileyfox-storm/development/aospextended-oreo-rom-wileyfox-storm-t3686323

they were both created by the same developer i guess which one recieves updates and which rom to use ? what is the diference ?

thnx for the great work

edit : can i use open gapps ? what version/size should i use ?
[Wileyfox Storm] tmish:
Use mini gapps, device system partition has not much space left, after rom install.

Nitrogen is more stable rom than aosp extended.

Soon there will be freshier roms ) Stay tuned.
[Wileyfox Storm] Monate:
deleted
[Shield Android TV Themes and Apps] Mermeo29:
Hi all I'm new to the forum and looking for some advice please..ive just got a nvidia shield 2017 I've switched the apps from unknown sources toggle on but I still cannot install apps such as the downloader app by AFTVnews.com and Aptoid. Any ideas gratefully appreciated.
[Shield Android TV Themes and Apps] jionny:
Are you rooted? How are you trying to install them?
[Shield Android TV Themes and Apps] Mermeo29:
Hi thanks for your reply Ive tried to install on es fike explorer and also on the aftv downloader app...im sorry I don't understand what you mean rooted?
[Shield Android TV Themes and Apps] jionny:
So did you download them with es explorer, can you see them in the apps section of es explorer, also suggest you restart your shield then tick unknown sources again and try
[Shield Android TV Themes and Apps] Mermeo29:
When in file I go to favourites there is no Google option so I chose yahoo for a search engine. Then on yahoo typed in Aptoid tv pressed to download and nothing appears to happen. In.aystore apps say not compatible with nvidia shield. I've only had a firestick previously so I'm struggling to understand what's different the shield
[Shield Android TV Themes and Apps] jionny:
go to browser and type in apk mirror and download the apks from there
[Shield Android TV Themes and Apps] Mermeo29:
Got it thanks for the info Johnny.
[Shield Android TV Themes and Apps] Mermeo29:
VPN

Hello again could you possibly recommend a vpn to use on the nvidia shield please?
[Shield Android TV Themes and Apps] jionny:
I use nordvpn that is my choice, I suggest you do a websearch on best vpn"s and compare them to make your decision
[Shield Android TV Themes and Apps] Mermeo29:
Thanks for the info
[G3 Q&A, Help & Troubleshooting] jlb1959.01:
can anyone or does anyone no why or how to fix the mobile radio wake on vs985,running xdabbeb3.1, no greenify,over night draw is 13-20% battery draw.I've wipe,reflashed,many times,some days only 8%, but a constant draw.in fact the only major draw..didn't know if its kernel issue,bootstack,all of which I've wiped,gone back to 10b,and reflashed..

thanks for any help as all the battery forums say to ask within lg forums..
[Asus ZenWatch 2] azj:
Anyone else have screen-burn in? I always use the ambient display. Recently I've noticed burn-in from the ambient display. Not noticeable when the screen is awake but definite discoloration in ambient mode.
[Asus ZenWatch 2] jshamlet:
All OLED displays experience burn-in. This is actually in the news right now due to the Pixel 2 XL and iPhone X. The only way to avoid it is to turn off the ambient display.

There are ways to mitigate burn-in to an extent, but it increases wear on the display.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mzaslam:
Hi all

I need an Original UK T-Mobile ROM - to re-flash my device as its been locked and wont go past the the bootloader screen.

The only thing I can do now is flash back to OEM ROM. I have tried everything else and nothing seems to work.

can anyone point me in the directrion of the official and NOT re-constructed UK ROM from T-Mobile.

cheers.
[Samsung Galaxy S8 Questions and Answers] hkbazzi:
Hi everyone, is there a kernel that allows voltage control on CPU and GPU voltages?
[Samsung Galaxy S8 Questions and Answers] thatsupnow:
This is the wrong section to asking. This is the development section. But you should've known that.....
[Samsung Galaxy S8 Questions and Answers] timrock7:
i bet you got alot of people excited here bud...
[Google Pixel 2 Guides, News, & Discussion] Kisakuku:
December images for Android 8.1 Oreo

Official factory images

Official full OTA images

Build OPM1.171019.011 - non-operator-specific
[Google Pixel 2 Guides, News, & Discussion] rootuser11:
i am currently running stock recovery + unlocked bootloader + snoke kernel. Can I flash OTA without losing any data? I have not applied magisk or TWRP recovery yet.

just tried it anyway and it worked. but does not pass safetynet anymore due to unlocked bootloader.
[Google Pixel 2 Guides, News, & Discussion] carboncache:
Any idea what Pixel 2 build OPD1.170816.025 is specific to? It's not one of the factory images or OTA zips provided by Google. I'm on AT&T, not in the beta program, and received it OTA via settings -> system -> update around 5:30pm EST today.
[Google Pixel 2 Guides, News, & Discussion] kibmikey1:
Probably specific to AT&T network and radio settings. It's a non-operator specific build, so I'd guess they just tacked on their radio, modem and whatever else is proprietary for them.

---------- Post added at 10:18 PM ---------- Previous post was at 10:10 PM ----------

023 for November on Verizon. Updated by using system update in settings.
[Google Pixel 2 Guides, News, & Discussion] petrus764:
Looks like .025 is rolling out for unlocked models. It brings the saturated option in display -> colors. Which is a bit more poppy and marginally better at crushed blacks.

It has the nov. 5th security patch though, not the nov. 6th.

To get .025 you need to get the ota from the phone - system updates, as it's not on Google's OTA site.
[Google Pixel 2 Guides, News, & Discussion] Large Hadron:
Also brings a navy bar which fades to grey after a few seconds in most apps (but not on the homescreen, at least not with Nova - not tested with Pixel Launcher).

Tried the saturated colours and it made my photos look completely unlike the real colours. Should keep Samsung fans happy then. ;)
[Google Pixel 2 Guides, News, & Discussion] cb474:
I don't see anything when I run the check for updates in the system settings.
[Google Pixel 2 Guides, News, & Discussion] petrus764:
Weird, you are on the september build, right? Not running the 8.1 beta?
[Google Pixel 2 Guides, News, & Discussion] cb474:
I sideloaded the OTA update and it seems to have gone fine, phone boots. But at the end of the process I got this message from adb:

* failed to read command: Success

Is that normal? Seems like a weird message, "failed" and "success."

*

Also, weirdly, the first couple times I restarted the phone after updating I got notifications for a bazillion old text messages, all in a row.

---------- Post added at 01:37 AM ---------- Previous post was at 01:35 AM ----------

Yes, just on the build that came with the phone. I was reading elsewhere that it can take a few days to a week or more, before people get the OTA pushed to their phone, after it goes up on the developer website. You can see I went ahead and sideloaded .018. I wonder if I'll still eventually see a update for .025 on my phone. I don't see the saturated option you mention. Also, I'm one of the people with the clicking noise and .018 did not fix that. But I see some people on the Google product forums saying they got an update and it did fix it. I wonder if they got .025.
[Google Pixel 2 Guides, News, & Discussion] petrus764:
If you sideloaded .018 you'll probably not get .025. I'm guessing you'll have to downgrade first if you want it. Make sure to update your ADB and Fastboot versions to the newest, as you'll end up with a bad flash with older versions, resulting in having to flash each file inside the image file manually.
[Google Pixel 2 Guides, News, & Discussion] cb474:
I wondered about that. Apparently .018 does not have the November 6 security patch, which seems to include the patches for the Krack vulnerability. It's weird that Google is pushing .025 to some devices, but posted .018 on the website at the same time. And I read the 2 XL is getting updates pushed to it, even though there are no November OTA images on the developer website.

So it's okay to flash an older OTA image over a newer one?
[Google Pixel 2 Guides, News, & Discussion] petrus764:
In theory it should since Googles OTAs are full system images in fact. But as I said, you need the latest fastboot/adb, and it's on your own risk. I haven't tried it.

You could also see if you find the .025 OTA URL from google, but I have no idea if that can be flashed over the .018 build without issues.

Fyi the .025 build is also on nov 5, not nov 6 security patch and the saturated mode sucks. So I wouldn't bother if I were you.
[Google Pixel 2 Guides, News, & Discussion] cb474:
Yes, I saw what you said about adb/fastboot. Thanks. I'm up to date on that.

I thought I read somehwere that .025 is Nov 6. Hmm, oh well. This article says it's the Nov 6 security patch that fixes Krack: https://9to5google.com/2017/11/06/android-november-17-security-patch-nexus-pixel/ Hard to believe Google still hasn't patched Krack in .018 or .025.

My main reason for wanting .025 is that it sounds like it might fix the clicking issue that some people have. On the Google product forms some people are reporting the update fixes the issue, others are saying it does not. I'm wondering if the difference is that some people sideloaded .018 and other got the .025 update pushed to them.

---------- Post added at 03:07 AM ---------- Previous post was at 02:44 AM ----------

Well, I tried to downgrade, by sideloading the older OTA image and I got this message:

E: Update Package is older than the current build, expected build newer than timestamp 1508187794 but package has time tamp 1504244601 and downgrade not allowed.

Installation aborted.

I wonder if I can flash the factory image? But then will that disable future OTA updates on my phone?
[Google Pixel 2 Guides, News, & Discussion] petrus764:
You can flash the factory image and it won't disable future OTA's but for factory images you need to have your bootloader unlocked. If it's locked now unlocking it will wipe your device.
[Google Pixel 2 Guides, News, & Discussion] Dilbert83:
Mine just recieved the .025 patch and i can comfirm its November 5th.
[Google Pixel 2 Guides, News, & Discussion] cb474:
Thanks. Yeah, I unlocked a while ago, so I would be able to root when that became available, without having to wipe my device. And I'm hoping there will be a version of Lineage OS for this device, so I can get away from the nightmare that is Google's update process and other ridiculousness.

Anyway, I'm downloading the factory image now, but I guess I might wait a couple days first to see if .025 does get pushed to my phone. All I can say is, WTF Google? Also, did you notice that there was a spelling mistake in that error code the OTA sideload output, "time tamp"? Brilliant.
[Google Pixel 2 Guides, News, & Discussion] petrus764:
Remember to remove -W from the flash-all.bat script or else it will wipe your device.

I doubt google will push .025 as it's not the first time they've done something like this.
[Google Pixel 2 Guides, News, & Discussion] carboncache:
The .025 build also cleared up my pesky clicking noise issue, in addition to the new color settings (Boosted, Natural, and Saturated) and fading grey nav buttons.
[Google Pixel 2 Guides, News, & Discussion] cb474:
Well, I became impatient/stupid and decided to try to downgrade to .010 by flashing the factory image (since the adb sideload of the OTA image did not work). Wow, that was an extreme mistake.

First, it turned out I did not have the newest version of fastboot, even though I was sure that I did (so much for Arch Linux being "bleeding edge"). After I flashed .010 all my phone would do was boot the the bootloader (it wouldn't even from there go to the recovery or power off). I thought the problem was .010, so I decided to try to reflash .018 with the factory image of that. That's when I discovered my fastboot problem, because with .018 it actually quits and warns you that you don't have the right version. Once I got the right fastboot, I flashed .018 and it booted up fine. Having not learned my lesson, I tried .010 again, with my updated fastboot. This time it booted to the "G" screen and then just got stuck with the progress bar endlessly looping. It was hard to get it to boot back to the bootloader, using the key combination, but finally I got it. Then I flashed .018 again and everything seems fine (fingers crossed).

So downgrading seems to not be an option by any avenue.

Weirdly both with the older fastboot and the newer one, even when flashing .018 that worked, I got an error message everytime:

sending 'bootloader_a' (38728 KB)...
OKAY [ 2.095s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 2.099s

Don't know what that "command flash error" is. Not very reasurring. But doesn't seem to be a problem at least with .018 factory image. I don't know if the bootloader really failed to be flashed, since .010 and .018 come with the same bootloader version. Or it's just something else that failed with "updating: partition:0."

So a lot of trouble to end up back where I started. I'm super annoyed if I won't get .025, since it seems to fix the clicking issue. I can't believe Google posts one OTA update online and pushes a different one. That is just so stupid.
[Google Pixel 2 Guides, News, & Discussion] km8j:
How do you force the OTA or use the image on a stock Pixel 2 unlocked from Google
[Google Pixel 2 Guides, News, & Discussion] G3N3RAlM30W:
What Diesel_Jeremiah said

I had problems due to outdated adb & fastboot. First thing I'd check if you are having problems.
[Google Pixel 2 Guides, News, & Discussion] Stauf99:
I've read a lot of weird things happening lately so I just want to know I won't mess anything up.

Will I have any issues if I take the 8.1 OTA update on my google edition pixel 2 rooted with Magisk?

Update: Update would fail everytime I tried it. Uninstalled Magisk, rebooted, and updated without issue.

Haven't noticed any issues so far
[Google Pixel 2 Guides, News, & Discussion] fjm568:
So, are you still rooted, or do you have to root again with Magisk?
[Google Pixel 2 Guides, News, & Discussion] Stauf99:
lost root, but since there's no roms or anything out yet I don't have use for it (and none of the magisk modules have done anything useful for me when I had root)

I read a lot of people having issues after rerooting with magisk after updating to 8.1 on this thread, so I'm just going to wait until things get stable and there's more development for the pixel 2
[Google Pixel 2 Guides, News, & Discussion] Diesel_Jeremiah:
Magisk V15 fixed a lot of issues. Both of my Pixel 2 are working just fine. Viper4Android is also working very well.
[Google Pixel 2 Guides, News, & Discussion] Stauf99:
wow, V4 finally works now? without custom kernel?

I'll have to check it out again, thanks for the heads up
[Google Pixel 2 Guides, News, & Discussion] peikojose:
How can we get 0.25? Can someone capture OTA link?
[Google Pixel 2 Guides, News, & Discussion] petrus764:
Not sure why you're having these issues. You should be able to downgrade to the previous version, first boot may take a while. Could be slot issues, if it was installed to slot a but slot b is active for instance. Shouldn't happen but you never know.

If getting .025 is your biggest priority and you don't want to wait another month, id set slot A to active, do a full wipe in recovery, then flash the system image from september with -w. Then boot and let it sit for at least 20 minutes if it's stuck on the G-animation. This means of course having to re-setup the device from scratch.

fastboot --set-active=a

As you know the pixel phones have two slots(partitions) for seamless upgrades. Flash-all.bat flashes your active slot and installs system_other.img to the inactive partition and wipes data if -w is in the script.

This unless google has changed something with the P2 that we don't know ofc. After all this is the first update to this device. I doubt it though, and after all, there's a reason why the factory images are available.
[Google Pixel 2 Guides, News, & Discussion] peikojose:
Is there a way to extract the boot.img form the phone?
[Google Pixel 2 Guides, News, & Discussion] oxidepshyco:
So I was looking at factory images for the new update. Seems like build number is the verizon version? Even though I ordered unlocked one from the google store.

Build no. in phone - OPD3.170816.012

Factory Images-

8.0.0 (OPD3.170816.012, Sep 2017, Verizon)
[Google Pixel 2 Guides, News, & Discussion] petrus764:
Is there a verizon sim in the phone?
[Google Pixel 2 Guides, News, & Discussion] oxidepshyco:
No sim was there. Also no verizon apps were found. :\ I have been using it for few weeks now I just noticed it.
[Google Pixel 2 Guides, News, & Discussion] petrus764:
Yes, but are you on verizon?

It's not a verizon model if you can enable oem unlocking in dev settings.
[Google Pixel 2 Guides, News, & Discussion] dbrohrer:
I purchased an unlocked version from the Google store a couple weeks ago. No Verizon sim in the device when it arrived. Booted it up and activated it on T-Mobile. Yesterday I tried to unlock the bootloader and found OEM Unlock option greyed out. I contacted Google support. They escalated my request to engineering for review.

I think some models shipped with their IMEI numbers on the list of Verizon devices (or however the server side switch that locks this down works). Stupid.
[Google Pixel 2 Guides, News, & Discussion] oxidepshyco:
No, I am not on verizon.

And ****, its grey'd out, I can't enable it. Looks like google messed up and sent me verizon one instead of unlocked one.
[Google Pixel 2 Guides, News, & Discussion] petrus764:
Yep.
[Google Pixel 2 Guides, News, & Discussion] oxidepshyco:
Man google has messed up a lot. Let me know what the support says after the review please. Thanks
[Google Pixel 2 Guides, News, & Discussion] dbrohrer:
FYI, an XDA member posted a bug report to Google for the same issue. Seems there are a lot of people with this.

https://issuetracker.google.com/issues/68897739

I will post an update once I get something back from Google.
[Google Pixel 2 Guides, News, & Discussion] yankee1390:
Here's the .25 link I captured

https://ota.googlezip.net/packages/.../68b137f1c40f62a2307f807f04c137a90f983dfb.zip
[Google Pixel 2 Guides, News, & Discussion] oxidepshyco:
Yep I saw that. And commented as well. Also thanks for updating once you get something back from support. Hopefully it can be fixed by a software update.
[Google Pixel 2 Guides, News, & Discussion] rob61280:
Thanks for the link that help me upgrade from 018 -> 025
[Google Pixel 2 Guides, News, & Discussion] dbrohrer:
You made my day. Thank you very much! Installed and up on .025 build.
[Google Pixel 2 Guides, News, & Discussion] peikojose:
I would like to know also if you can extract the boot.img from your phone?

I would like to have the 0.025 boot.img to try to root that one.
[Google Pixel 2 Guides, News, & Discussion] smith8ca:
Sorry for the newbie question, but how did you use this link to update?
[Google Pixel 2 Guides, News, & Discussion] dbrohrer:
ADB sideload from a computer to your phone's recovery. There are detailed instructions from Google here:

https://developers.google.com/android/ota

Its easy if you have the right drivers and adb / fastboot files.
[Google Pixel 2 Guides, News, & Discussion] Shibang:
Same here. I got trigger-happy with sideloading 018 and was severely bummed that my phone was still having the ticking noise. Just sideloaded using that 025 link and my Pixel 2 no longer has that dreaded ticking!
[Google Pixel 2 Guides, News, & Discussion] rob61280:
Just a quick update, Google have now posted the 025 update, it's marked EMR for some reason.

https://developers.google.com/android/ota
[Google Pixel 2 Guides, News, & Discussion] piccit:
Emergency manual release? To get the krack fix out, would be my guess
[Google Pixel 2 Guides, News, & Discussion] murtezahu:
anybody have any idea what EMR stands for?
[Google Pixel 2 Guides, News, & Discussion] rob61280:
Emergency/Enhanced/Early Maintenance Release?
[Google Pixel 2 Guides, News, & Discussion] Kisakuku:
Updated the OP with two new build numbers and a note about KRACK vulnerability not having been patched in November updates.
[Google Pixel 2 Guides, News, & Discussion] cb474:
What's the difference between these two versions of the updates? The captured link for the update pushed to devices is only 50 Mb. The image on the Google developers page is a whole 1.5 Gb image. How can they accomplish the same thing? Is there a reason to flash one over the other? And what's the proper way to flash the smaller file? Also has anyone tried the whole EMR version?

I'm also curious like others what EMR stands for.
[Google Pixel 2 Guides, News, & Discussion] xene97:
Hopefully someone can answer my question. Which OTA do I download? I have an unlocked device from the Google store but am on Verizon. Do I use the OPD1 (which I'm assuming that I do since my build number is currently OPD1) or the OPD3 Verizon one? Thanks in advance - would hate to screw up my new toy.