I am using the latest Phonegap Push Plugin for my Phonegap Application. It's working fine below Nougat but in Nougat the same code does not work. I have tried to debug several times, also cross verified at server side if there is anything missing but found the device is not recognized by the GCMSender. Also everytime I uninstall and reinstall the Application the registered device token is same whereas in case of the Pre Nougat devices, it's always different after each uninstall and fresh install. The device I am having is Nexus 6P.
Finally after searching so much found the below answer:
Reboot your device since it must have got OTA update for Nougat.
System's cache partition might not have been cleared. Seems to be an issue in Nougat. Below are the steps for rebooting and found the same Push Notification code working in Nougat as well:
-Power down your device
-Press and hold Volume Down and Power simultaneously until you see the boot screen
-Use Volume Down to navigate to Recovery Mode
-Press Power to confirm
-Wait until you see the Android robot then hold down Power.
-Press and release Volume Up
-Navigate with Volume Down to the Wipe Cache Partition option
-Press Power to select
-Use Volume Down to highlight the Yes option
-Press Power to select
-Press Power to reboot
Reference Link: https://productforums.google.com/forum/#!topic/nexus/xEssjbdwpgk
Related
I am using Realme X7 5g (RMX3092). I used ADB to remove all the bloatware in the phone.
I did not remove the launcher / keyboard or any important apps.
Now the Phone is stuck at the login screen.
Video Link
Is there any way to re-enable the disabled packages while in Recovery or Fast boot mode ?
I tried using both and get the error Screenshot
I have one of the old update packages in the memory of the phone but the system is not allowing to degrade to a older version. Screenshot
Any help is appreciated.
I am trying to install Android 10 on an LG Nexus 5x (bullhead) smartphone. I installed the TWRP app, downloaded the Pixel Experience (the OS). I booted into TWRP recovery mode, and installed the OS, then rebooted.
After rebooting, the phone starts with the screen of language setup. Right there, the message "Google Services Framew...keeps stopping" keeps popping up, and I can't press on anything else.
I restarted the phone, went back to TWRP recovery mode, wiped data and installed the OS again. But that message still insists. Is there any way to fix it, or I've just broken the phone forever?
I finally found the offical forum for this Android 10 OS: https://forum.xda-developers.com/nexus-5x/development/pixelexperience-nexus-5x-t3861437/page141
Apparently, many people also experience this issue. I will look further for the solution on the official forum.
I finally found the answer. The Pixel Experience ROM must be installed in a decrypted data partition. Mine is encrypted, so I must remove the encryption.
The simple way is, instead of "Wipe", to choose "Format Data" in the TWRP recovery mode, then proceed as usual.
My goal is to get my Moto G6 phone in Root Mode. I bought a blank phone for this purpose, so no data is at risk. After following the steps on the XDA guide, I only got so before things did not work as they described. If I reboot my phone, I get this blue Moto G6 bootscreen and the phone never boots. I can get TWRP running on the phone though. Right now, my phone is not being recognized by either adb or fastboot. The guide I've been following is at
https://forum.xda-developers.com/moto-g6/how-to/guide-twrp-root-magisk-installation-t3816569
c:\Software\MotoG6>adb shell
error: no devices/emulators found
c:\Software\MotoG6>fastboot devices
c:\Software\MotoG6>
I have the latest Moto G6 drivers installed, but I don't think they apply anymore. If I unplug and replug in the USB cable into my Windows machine, it says it does not recognize the device.
The firmware I saw on the device when it did boot was OPSS27.82-87
* I do not know how to go back to stock because it won't recognize the device enough for me to push the stock image to it. *
*** FWIW, even on step 3 of that guide, it would say the boot image was not signed or corrupt. This happened when I tried to do
fastboot flash boot <insert-boot-image-name-here>.img
someone else had that problem and the recommendation was to ignore the message and reboot to recovery.
(https://forum.xda-developers.com/moto-g4-plus/development/wip-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586/page2)
For those who would say, "Read the **** manual", bear in mind that I did read the manual. No manual said where to get the firmware information they asked for. Also, many of the image links were bad. They did not say how to handle the case where the image did not install as they said it would. Somehow these manufacturers make each phone just enough different, and each firmware is different that it's impossible to predict what a phone will say ahead of time with certainty.
When it shows no commands, press and hold the power button then tap volume up button once. Then release the power button.
If this doesn't work mostly likely needs to be sent back to the manufacturer.
I am trying to create a React-Native app and I need to connect my device to troubleshoot some issues that only occur on the physical device and not the simulator. For some reason I have never been able to connect my Pixel 2 XL to my PC. I am running Windows 10 and I have tried all of the following.
Enabling developer mode and USB Debugging on my device.
Uplugging and replugging my device 20+ times in a row.
Changing the USB port I am using.
Changing the USB connectivity settings in Developer Options > Default USB Configuration. (Options are: File Transfer, USB tethering, MIDI, PTP, No data transfer) I've tried them all.
Restarting my device while it's plugged in
Downloading the Google USB Driver (in Android Studio).
Restarting my PC when the device is plugged in.
Updating my PC, and updating my device.
Checking Device Manager and trying to update the driver. (So the device used to show up with the yellow warning triangle next to it and trying to update the driver never worked. But now, the device doesn't even show up in Device Manager anymore)
Factory Reset my phone.
Downloaded Media Feature Pack for N and KN versions of Windows 10 (Suggested by the google tech support)(I called them)
I feel like I've tried everything previously addressed in every Stack Overflow question on this issue.
Finally solved the issue. The data cable was the problem. If you have tried all the steps above, and nothing is working, buy a new cable. This one works great and seems very durable for my Pixel 2 X: https://www.amazon.com/gp/product/B01N4OKUB8/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
I had this issue too - my Google Pixel 2 XL is about 9 months old. Was developing an app, so using USB debugging to debug the app as I built it. One day it mysteriously stopped working, though no issues with charging. I tried everything, including using all the different USB ports on my laptop, with no luck.
I eventually gave up and started using the emulator on Android Studio, and since I didn't need data transfer for anything else, I didn't send my phone for repair or anything.
A few weeks later it just started working again, all by itself...
I don't think I did anything to fix it - the moral of the story is, if you don't need it urgently, there's a chance it might just decide to work again!
I recently broke the screen of my locked phone and would like to unlock and recover data by using adb, but it's not detecting my broken Samsung Note 5 or even my replacement Samsung Edge 7.
I've tried:
kill-server/start-server
downloading newest usb drivers
enabling developer mode on both phones (I already had developer mode enabled before I broke my Note 5).
using original usb cord given inside the box.
I don't know what else to do.
The problem might be with your computer.Try to use a different computer with adb installed to see what happens.If the problem persists,uninstall your Android SDK and re-install it.
On my Note 5, adb needs the phone's USB connection set to 'USB Data' not just 'charge' (default) before it will recognize it. Once it sees that permission, abd devices will show the phone as 'unauthorized', I then must allow access for debugging on the phone before it will allow access by tapping 'OK' on the popup dialog on the phone.
You could try booting into recovery mode but I don't think Samsung Galaxy allows access vie adb when in recovery. It may depend on the age of the phone.
So it sounds like the phone may be in 'charge only' mode when USB is connected. Your best bet may be repairing the phone.
I am a user of both android studio and Samsung Galaxy Note 5. I solved my issues just the same as you by generating APK files and transfer it to my note 5.
I just found that the reason is unknown resource settings which means my phone only trust google play and block other app. Have a good day.