yashsingh1/xdaforums huggingface dataset:
[P8 Lite (2017) Development] mateiocristi:
what is this guide for????????????i had pra lx1 and rebranded .

I TRIED TO FOLLOW THE GUIDE BUT FIRST OF ALL OREO_TWRP IS NOT WORKING .WHEN I BOOT IN RECOVERY IT SAYS ERROR. SECCOUND I TRIED TO FLASH THE 3 ZIPS WITH OTHER RECOVERIES BUT I GET ERROR 7.

how can i install oreo on my device please make a working guide!!
[P8 Lite (2017) Development] honorfan:
Hey what are you doing??
[P8 Lite (2017) Development] Hinatasan:
The encryption key is not valid. You need encryption key to download the file..

There are some encrypted files, can you provide the keys please? :)
[P8 Lite (2017) Development] honorfan:
Really bad
[P8 Lite (2017) Development] 9bestenbier:
Does this method also need a SD Card? Cause the problem is that my SD Card slot isn't working at the moment so I was wondering if I can place these files on my internal storage and flash?
[P8 Lite (2017) Development] honorfan:
Bro this thread is not for updating to oreo
[P8 Lite (2017) Development] 9bestenbier:
Well I saw "EMUI 8.0" so I thought that this was a different method.
[P8 Lite (2017) Development] Freysheur:
Yo,

What's passwords for unlock the files ? :(
[P8 Lite (2017) Development] honorfan:
Hi bro

files and this thread is damaged

download update.zip then flash it by oreo no check recovery

then download data zip and rename it to update.zip and flash by oreo no check recovery again
[P8 Lite (2017) Development] Abdala2307:
Hi can i flash it above emui 5
[P8 Lite (2017) Development] gagedekoe:
will this work if i currently have emui 5.1 custom rom and twrp 3.1.1 open kirin edition?
[P8 Lite (2017) Development] seddikhtc:
Fastboot flash recovery_ramdisk its not valid error ????
[P8 Lite (2017) Development] seddikhtc:
~/Downloads >>> sudo fastboot flash recovery_ramdisk IMGS/twrp.img

target reported max download size of 471859200 bytes

sending 'recovery_ramdisk' (39314 KB)... OKAY [ 1.250s]

writing 'recovery_ramdisk'...

FAILED (remote: partition length get error)

finished. total time: 1.256s
[P8 Lite (2017) Development] Katcher12:
Do I need to flash the standard TWRP before I flash the Oreo-TWRP or can I just flash the Oreo one without the latter?
[P8 Lite (2017) Development] Katcher12:
Sorry for the double posting but I'm getting an error when trying to flash the oreo_twrp image. I keep getting

Have I missed a step necessary?
[Samsung Galaxy Note 8 Questions and Answers] InteliDroid:
Hi guys, a new Oreo firmware was released for the N950F under build N950FXXU3CRC7.

Is there a way to find a change log for this. Unsure if worth updating from CRC1 which is a custom rom. Whereas the new firmware build on stock could be better.

Thanks :)
[Samsung Galaxy Note 8 Questions and Answers] jpl69:
Me too. Very curious.

There's a feature on Oreo that when you dismiss a notification it clears the app badge on launcher (even if you didn't read it), i've read somewhere that the last S9 update reverted this situation.

Does anyone know if crc7 reverted this ituation as well for note 8 as it's keeping me on Nougat although i really wanted to do the update.

Thanks
[Samsung Galaxy Note 8 Questions and Answers] shouren04:
I'm not seeing new/second Oreo release for XEF or multi/OXM. What country & is it a first or second release? Sounds like it just may be a carrier specific 1st time Oreo release.
[Samsung Galaxy Note 8 Questions and Answers] Lobo86:
He is from Australia.

https://www.sammobile.com/firmwares/galaxy-note8/SM-N950F/XSA/download/N950FXXU3CRC7/213991/

compilation date Thu, 15 Mar 2018

KERNEL VERSION

4.4.13-13094739-QB17335707

dpi@SWDG4713#1

Thu Mar 15 15:37:28 KST 2018
[Samsung Galaxy Note 8 Questions and Answers] shouren04:
I see, yeah as I suspected, I wouldn't consider that an upgrade from CRC1.
[Samsung Galaxy Note 8 Questions and Answers] DemGer:
http://doc.samsungmobile.com/SM-N950F/XSA/doc.html
[Nexus 5 Q&A, Help & Troubleshooting] YayJohn:
My normal mic is broken and I want to still use the assistant so is there anyway to make her use the speaker mic? also I'm rooted
[MTCD  Android Head Units Q&A] johnboy999:
Hi guys, first post here.

I recently purchased a Witson V5754 unit for my Astra J which is an Android 8.0 PX5 unit with no external buttons. Everything is controlled by touchscreen or the factory panel buttons and steering wheel controls.

The unit was working perfectly but froze up and couldn't get any response from it. When I switched off the ignition, and then switched it back on again, it came back with the same frozen screen. So, I pulled the radio fuse to cut the power to the unit. On re-inserting the fuse, the unit powers on with the initial multi-media nav splash screen, then followed by a black screen for about 5 seconds before going into a recovery screen saying that it can't load android and my data might be corrupt.

This screen gives me 2 options - try again or factory data reset. The problem is, with no external buttons, I can't move the highlight to choose anything on that screen!

Any ideas, guys and gals?

PS - I would upload a pic of exactly what it says on the screen but due to forum restrictions in my first posts, it won't allow me to attach the pic
[MTCD  Android Head Units Q&A] ikerg:
If you have a reset button (a small hole that could.be pressed helped by a needle) use it for moving between options (short press = move. Long press = accept the chosen option)

Enviado desde mi SM-G950F mediante Tapatalk
[MTCD  Android Head Units Q&A] Anrix:
Hi, have you solved the problem? I have a similar problem with my full touch px5 and I have not found any reset buttons from the unit or the screen.. So now I can't get out from recovery mode. Reversing camera works tho.
[MTCD  Android Head Units Q&A] Xorit:
That Unit (Witson V5754 unit for my Astra J) has no hardware reset button !!!

The hole right next to the SD slot is fake.

Only solution is to open the display part and solder a button to key2 + gnd.

I know, because I have that unit myself and tried all the buttons + combinations, no sauce.

EDIT: Search in my posts or in the hardware section for more info
[MTCD  Android Head Units Q&A] Anrix:
Thanks, will try it soon. I have Witson V5637, but I think the HW is the same.
[MTCD  Android Head Units Q&A] Anrix:
I have the exact same board under the screen, but I couldn't get it to work. Tried with key2, key1 and rst, all with ground. The idea is to get the key2 to ground with the button? When I powered the unit the key2 didn't got any voltages so if it is activated with ground, it is not obviously working.
[MTCD  Android Head Units Q&A] Xorit:
Please find my posts about it.

You need to wire LED1 or 2 .. cant recall, because it functions as indicator.

What the key on single press does is MUTE

Long press powers off the screen and keeping pressed the HU goes to sleep or even longer pressed, reboots.

The indicator starts lighting up when pressed long enough for reboot and start flickering after, where you start to release-push until you are in recovery.

-> Since the mid-long press shuts off the screen, it could happen, that your screen stays black -> press again to power on the screen.

EDIT: Yes, key+gnd does it.

You can even map this new keys in the keystudy app now, because they're resistive.
[MTCD  Android Head Units Q&A] Anrix:
Didn't work with this wiring: key 2 (or key 1 or rst, tried them all) -> switch pin 1, gnd -> switch pin 2. So when the switch is pressed, the key is directed straight to gnd. Should I do something differently? I don't need any indicators, just need to get out of recovery mode.

I have checked the posts in different thread you mentioned, but they are as jibberish as other answers :)
[MTCD  Android Head Units Q&A] Xorit:
Most ppl try to even enter recovery :-p for that, the indicator helps a lot.

If you are in recovery already and need to get out, key2 long press should activate the highlighted entry. This is also mentioned in the top lines in recovery.

key2 pulled to gnd will do. Assuming you use the gnd provided by that connector.
[MTCD  Android Head Units Q&A] Anrix:
Yes, the gnd was from the same flex connector slot. Checked with a multimeter that it is also a shared ground and the switch was properly wired. Still not working with the switch.

Lyckily I got an usb keyboard. I plugged it directly to usb1-port at the back of the HU while powered up -> didn't work. Then I left it plugged and powered the unit completely off (not even power to memory) and on again -> the keyboard starts to work and arrows/enter key did the trick!

Thanks for your support although it didn't solve my case (which is strange because of the same HW).
[MTCD  Android Head Units Q&A] Jonika21:
is there any way to use the recovery without rst button?
[MTCD  Android Head Units Q&A] Ciechu1916:
At the outset, I'm sorry for digging up the old topic, but I can't cope with my device at all. After connecting to the power, the device displays the Android 10 logo for a second and then the screen is black. I need to enter recovery mode, but like the user above, my device does not have a reset button or any other physical buttons. After disassembling the device on the board, behind the display, I found pins as in the picture, ie RST, RST1, GND1, GND2. After shorting the RST and GND1 pins, you can see that the device is restarting, which I suspect is like a reset button (?). I will be grateful for any help on how to enter this recovery mode.

View attachment 5285885
[MTCD  Android Head Units Q&A] marchnz:
For MTCD/E, I've posted some hardware methods for entering recovery.
[Android Q&A, Help & Troubleshooting] amiri82:
Hi guys.

I have a samsung a5 2017 (a520f)

I know it is a ridiculous question but I wanna know shall I enable "allow oem unlocking" in developer mode to flash twrp and root with magisk?

If so, shall I unlock bootloader or no?

Please answer as soon as possible.

And sorry for my bad English.
[Android Apps and Games] truekasun:
Techie (Tech News),

a simple android application that built to reach the latest technology based news from various RSS Feed providers.

Techie has been designed in order to provide you with a clean, lightweight and ad-free experience while delivering you the best breaking news including mobile, gadgets, wearable, video games, product info, science, art, and tech culture.

Download Techie (Tech News) today, to stay up to date with the tech world.

From Google Play

XDA:DevDB Information

Techie - Tech News, App for all devices (see above for details)

Contributors

truekasun

Version Information

Status: Stable

Current Stable Version: 1.0.7

Stable Release Date: 2018-04-05

Created 2018-04-05

Last Updated 2018-04-05
[Android Apps and Games] truekasun:
Reserved
[Samsung Gear S3] coppertop24:
Is anyone using their Gear S3 with a phone running the Android P dev preview? Been trying to connect mine and it constantly force closes. Just want to see if it's just me or if it is a problem with the app not working with P.
[Samsung Gear S3] iHelp101:
I kept having this issue and finally realized the issue. Android deprecated the hidden API Samsung references (IPackageObserver). This hidden API only works if the app is a system app, so it is weird that Samsung has this. Maybe it makes the experience a little nicer on Samsung devices since everything can be done in the background, but when it causes crashes it is not ideal. All you need to do to resolve this issue is edit the smali file for com.samsung.android.app.twatchmanager.packagecontroller.PackageControllerFactory.

The method makeInstance() needs changed to false (So it doesn't try hidden API). After that you will have to re-sign Samsung Gear, Accessory, and Plugin APK's because they use a shared user ID. One issue I noticed is due to having to re-sign the APK Samsung Pay was giving me issues. Hopefully Samsung resolves this issue soon.
[Samsung Gear S3] dsmitty166:
Can you share the APK?
[Samsung Gear S3] Jackz314:
I'm working on it, if nobody else shares it I'll try and upload it here.:)
[Samsung Gear S3] huskerpat:
Please do post it. I'm tempted to roll back if I can't get my watch working.
[Samsung Gear S3] julk13:
Did anybody test Samsung Gear with P Beta ?
[Samsung Gear S3] Djfrost:
DO NOT INSTALL ANDROID P IF YOU HAVE THE SAMSUNG GEAR APP ON YOUR PHONE.

Sorry didn't mean to yell but it will render your gears s3 a paper weight...and Samsung could care less

---------- Post added at 01:18 PM ---------- Previous post was at 01:14 PM ----------

I have been trying to opt out of android P for 18 hours now...and got nothing. Getting ready to just do a warranty exchange.

---------- Post added at 01:27 PM ---------- Previous post was at 01:18 PM ----------

don't do it...your gear smart watch or fitness device will become useless. Requested a rollback from Google back to android O 19 hours ago and haven't gotten it yet. Cant even sideload the previous android O.....
[Samsung Gear S3] Thealshear:
There is a way to get it working I did it with my pixel 2 xl on DP1 when it was released I flashed the factory image while removing the -w command from the script, this preserved my data and I was able to continue using my watch.
[Samsung Gear S3] samt3:
Just grab the Oreo image from Google and use fastboot to flash it. You might can even get by without having to factory reset the phone doing it that way if you just remove the "-w" from the fastboot command.
[Samsung Gear S3] huskerpat:
Don't think I can do that on a locked bootloader. Got a Verizon phone.
[Samsung Gear S3] samt3:
Yea your right. Forgot Verizon have there bootloaders locked down. My girlfriend had the original Pixel that ended up being the Verizon model. I ran into the exact same problem on her phone with the Oreo beta. The roll back kept failing to download. I think I ended up joining the beta and exiting it about 10 to 15 times before it successfully downloaded.
[Samsung Gear S3] TheUndertaker21:
i came here for that

tried to pair my watch but no P support yet :(
[Samsung Gear S3] fiffan86:
My Tmo Gear s3 is working perfectly fine on my p2xl on android P, I had it setup before taking the P Beta OTA.
[Samsung Gear S3] keaheng:
Not working on Android p beta 2. Samsung does not give a f*** about their users.
[Samsung Gear S3] Patofety:
Samse issue here, it'd be good if there is an alternative app
[Samsung Gear S3] armada786:
Why would Samsung support software that is not meant for general use and aimed at developers? Google even warns you it is not to be used as a daily driver and all your software may not work. Stop being so entitled. Support for P will come in due time, probably during one of the later builds that finalize the APIs if the O preview was anything to go by.
[Samsung Gear S3] cpetersen2791:
Mine worked too (including Samsung Pay), until i lost bluetooth connection, and to "re-pair". Couldn't reconnect without going back to Android O. Gear App kept crashing.
[Samsung Gear S3] jidccruz:
My Gear S3 is working fine with my Pixel XL with Android P DP2. All notifications and fitness related features are working. Also, Samsung Pay is working on the watch. The only problem is you cannot open Samsung Pay anymore in Gear app. It will only show "Installing Samsung Pay (Gear Plug-in)". Samsung store and Samsung health are both okay.

I came from Oreo 8.1 with Gear paired completely with my phone. I just opt in Android P DP2 and update it.
[Samsung Gear S3] Rosmith:
So is it if you already had everything set up it works fine on the beta?
[Samsung Gear S3] gettinwicked:
I flashed P with the -w removed and my S3 already setup. Works perfectly. I'm assuming most of you who are trying to pair did a clean install of P? Just flash back/unenroll to O, set it up completely, then go back to P. All this work is definitely worth it. P is awesome. Anyway, if the one poster gets the apk so it works if you need to re-pair Bluetooth, that will be very cool too. I'd like to be able to factory reset if I run into issues that are fixed that way.
[Samsung Gear S3] Jackz314:
Guys, problem solved! I worked out the APKs, take a look at my thread.
[Samsung Gear S3] KingOfAntarctica:
I'm using a Pixel XL and Gear Fit 2. I applied the P Beta as soon as they announced it during I/O. Everything was great with my Gear Fit 2 until I tried to open the Gear app yesterday. It force closed immediately and dropped the connection to the band.

Now the Gear app always force closes and I cannot restore the connection. I removed the connection, cleared the app data storage and cache and now the Gear app opens fine until I try to select the band during setup, which starts the force crashes again.
[Samsung Gear S3] chrisc44890:
I just spoke to a Samsung rep and they said the dev team is working on an update to fix the Android P incompatibility.
[Samsung Gear S3] arcanexvi:
Thank you for your work getting my watch back up and running!

Any progress on Samsung Pay or are we playing the waiting game?
[Samsung Gear S3] Jackz314:
Unfortunately still waiting because I still don't know what Samsung did to detect changes in APKs, if you have any suggestions I'm more than happy to hear them.
[Samsung Gear S3] acomp182:
[MENTION=325297]jackx[/MENTION]314 Worked perfectly with my Gear S2! Thank you!
[Samsung Gear S3] Ramonchito2:
Just chiming in, my doesn't work either

Unfortunately, I'm having the same problem which sucks, however, I like Android P too much to downgrade. Seems like Samsung probably won't have this fixed until P is fully released. Should we just start some kind of "hurry up and fix this" petition with Samsung or something :p
[Samsung Gear S3] ram4ufriends:
Did you look at this thread? I am Android P and Gear S2 works fine

https://xdaforums.com/gear-s3/help/gear-s3-gear-devices-incompatibility-t3789231/page6
[Samsung Gear S3] Ramonchito2:
That's neat, I didn't notice that it was still connected to my Health app. Good to know! However, the problem wasn't concerning the health app, it is with the Samsung Gear app, the only way to get phone calls, text messages and notifications, etc on the watch.
[Samsung Gear S3] silverhd07:
Using S3 on Android P beta

While the Gear app still doesn't work on Android P beta, you can set up your S3 without connecting to your phone. When your watch asks you to complete setup on your phone, scroll down and talk on the question mark. Then scroll down and talk to setup your watch without connecting to your phone. Follow the setup and your in. Connect your watch to WiFi. It isn't perfect, but at least we can still use our watch in a limited capacity until Samsung makes the gear app compatible with Android P. Otherwise, it's just an expensive paperweight...
[Samsung Gear S3] mobileman88:
I have been reading that those who upgrade to p via ota/fastboot without wipe from o would not get this problem as long as it's working before the upgrade

---------- Post added at 12:37 PM ---------- Previous post was at 12:35 PM ----------

Another way is to downgrade to o, have everyone setup before upgrading to p then it will continue to work
[Samsung Gear S3] rfuser:
Not true. Had gear app for months then did ota p install. Weeks later my gear app now crashes on beta 3 , installed ota beta 4 and still happening . Cleared app cache and installed older gear app. Not use. Even cleared out phone contacts on phone
[Samsung Gear S3] mobileman88:
Ouch. I am getting this on my device which has been updated to July update and Magisk 16.6
[Samsung Gear S3] mobileman88:
Anyone got Samsung pay working on their gear s3 after upgrading phone to P?
[Samsung Gear S3] Ramonchito2:
Yes Samsung Pay oddly enough works just fine. I still get steps, weather, sleep etc. Any thing else phone dependent however such as texts, calls or even adding new watch faces :thumbsdown: :smh:
[Samsung Gear S3] mobileman88:
How did you upgrade to P? Reinstalled any of the Samsung stuff and which device?
[Samsung Gear S3] mobileman88:
I have 2 sets of Gear S3 linked to 2 different Essential PH1 on P. 1 worked while the other one doesn't. Go figure. Same exact commands were use to upgrade and root them. For the one that works, one thing I noted is that the Gear app icons below the Gear S3 stats are greyed out somehow although it does not affect any of the sync/steps/notifications. Have yet to test Pay if it works.
[Samsung Gear S3] braso:
I've been looking for a non-root solution to this issue without any luck. I am running the Android P Beta on my Pixel 2 XL. There is a workaround of sorts that still allows you to connect to the phone and receive texts etc.

I rolled back to Android 'O' and did a factory reset. I reinstalled the Gear App, plugin etc. and got the phone working fine. At this point, I added all the apps and watch faces I wanted as you can't do that once on the 'P' beta.

I triggered an OTA update to the 'P' beta and the phone updated. As long as you don't try to open the Gear App on your phone, it will continue working as normal (receiving notifications, syncing steps to S Health, playing music etc.). If you do open the Gear App, it will FC and lose the connection between the phone and the watch. Nothing will allow it to reconnect, and I have tried clearing app data, resetting the watch and a number of other steps. I made sure the Gear App is not anywhere on my desktop so I don't accidentally open it. As stated earlier, certainly not ideal, but it is a workaround nonetheless.
[Samsung Gear S3] mobileman88:
A new Gear S plugin was released in the play store. Phone auto updated to 2.2.03.18071141N and the Gear app kept crashing after that. Had to restore the old Gear S plugin which prompted me to reset the whole watch. After which I had to setup everything all over. There's now a prompt about a new Samsung Pay update. I guess it'd probably end up with the same issue. I am on the July P release.
[Samsung Gear S3] SuperSnake23:
Has anybody gotten the new Gear S plugin update on android O and then upgraded to android P? If so did the gear app update fix the FC issue???
[Samsung Gear S3] mobileman88:
Was in P when I updated. Then the app fc all the time until I restored the previous version from backup
[Samsung Gear S3] SuperSnake23:
I am guessing that it may work if you update the app in O and then upgrade to P but I have already downgraded once and that was a pain since I had to wipe. I will try again tonight and report back what I find.
[Samsung Gear S3] mobileman88:
That's a massive pain. Now it is prompting a pay update. Pay still works but not sure for how long more. Samsung is getting 1 star for the apps in play store. But they just don't seem to care
[Samsung Gear S3] flamingspiral:
Apologies if this has been said already, but I found a way to get the watch to connect to the phone, if you were connected before so you can at least get notifications. I selected 'find my phone' from the watch and forced a connection from the watch, it paired, and I can now get notifications! It's not a fix, but it may help.
[Samsung Gear S3] cpetersen2791:
How did it go. I downgraded to O, and got it working again, but I don't want to update to P if it still won't work.

Thanks,
[Samsung Gear S3] chnzshyguy:
This worked! THANK YOU! This should hold me over to a full fix...
[Samsung Gear S3] SuperSnake23:
I updated to newest Gear plugin (2.2.03.18071141N) on android O (8.1) then updated to Android P (DP4) and it was working fine. DP5 update came through yesterday and is still working. I am able to open the gear app, sync works, notifications, etc... That being said my first time on old plugin version worked for some time after going to Android P. I really don't know what was the trigger before that broke the communication. I also would not have tried to open the gear app I just know that it did have a connection for a while and I got notifications.

---------- Post added at 06:51 PM ---------- Previous post was at 06:44 PM ----------

Seems to be working on P with new plugin.
[Samsung Gear S3] gawarner:
I would love to know the answer to this question as well!
[Samsung Gear S3] roldo22:
I did this yesterday and everything seems to be working correctly now. Gear app does not FC and connects to my S3 like it did previously. I am seeing all alerts and S health syncs with my watch.
[Samsung Gear S3] gawarner:
Just tried it with new release of gear plugin and latest Android p and it works

For the first time, the app is not shutting down!