Just installed google wallet, works fine.
Changed Build.prop back to stock.
Now, when trying to use S-pen in S-note, get the error:
"polaris engine not supprted with device I650"
Have checked the build prop several times, its right.
Perhaps use Titanium to wipe the cache on S-note?
Any other thoughts before flashing back to stock rooted?
Related
I've searched all over the web for this and all over XDA and there has been nothing conclusive. Hoping we can find something usable here.
Basically, market hangs on starting downloads and does not progress. I can tie the failure only occurring after I install the V1.1.0_r2 update and ensuring top to bottom I have met all the requirements. I work on about 4 NCs for family members and one of our has gotten V1.1.0_r2 working with Market fully functional. 2 of the NC's fail Market and have not tested the 4th since generally, only Market fails but all other functions on the NC work perfectly.
My system:
- 1.0.1 Auto Nootered
- Gingerbread keyboard
- Sideload hack
- Telephony Hack
Here are the symptoms I have found:
- All worked fine on 1.0.1
- Initial install of 1.1 worked for a bit but crashed on adfree host file update and did not work thereafter
- First notice was on Facebook download
- market.android.com can still push installs
What has not worked:
- Clearing Market data
- Clearing download manager
- Starting and stopping downloads
- ejecting or unmounting SD card
- fixing permissions does not work
I've seen this happen on 2 different Nook Colors but not on a 3rd and my personal SC I've repeated the failure across 3 complete factory wipes and resets with the same end result of a working Market that gets stuck on Download Starting.
Any ideas?
You don't have an Android phone, do you? This happens on every device recently, something with the market, has nothing to do with the Nook.
I disagree. I have a DINC and several nooks and I can force this to happen on the nook where the market works fine until I update to 1.1
I was having the same market download behaviour you describe the first few times I attempted a 1.1 upgrade. The thing that finally did work for me was doing a complete wipe of all data, all cache and complete factory reset, even back to the stock recovery partition. Then walked through the upgrade setting things up by hand and not restoring anything from backup. The market has worked fine for me ever since.
You mentioned doing complete factory wipes and resets, and if they were this kind of thorough wipe-everything back to out-of-the-box state reset and not just a restore from an old backup... then I don't know what to tell you. I assumed there must have been something buried in my data that was somehow causing the problem in 1.1, but maybe I just got lucky that last time.
fwiw, here's what I did in case you spot any differences that might help.
- "Erase and Deregister Device"
- wiped dalvik cache and cache partition from clockwork recovery
- used dd to rewrite boot and system partitions to stock out-of-the-box state (1.0.1 version)
- rebooted and went through B&N "first time" setup process, registered with my B&N account.
- auto-nootered
- rebooted and went through google's "first time" setup process.
- performed the whole youtube -> gmail -> google talk -> market setup dance
- installed clockwork rom manager from the market
- followed the 1.1.0 upgrade process
- rebooted and tested everything (including the market)
- started manually loading books and apps back on, avoiding backups made before the upgrade
I don't know if this is of any help, but it worked for me. And I hope someone figures out where the problem actually is before the next B&N upgrade, because I'd rather not have to do all that again.
I did the same thing as you but I did not wipe the dalvik cache. Weird thing was that I was able to get market to work immediately after the update but it stopped working after a bit. Couldn't tell what triggered it and I was only doing hard installs from market. No backups.
I restored to factory via 1.0.1 image several times to try and isolate the problem. It was not decisive since I do have one nook that competed all updates including an overclock and all functions seem to work perfect including market.
issues and FCs with V1.1.0_r2 update
Keep in mind I am a noob at all of this and am barely able to keep up with you guys, but I had problems with FCs and general instability after using the V1.1.0_r2 update and flashing one of the more "stable" overclocked kernals. In general I didn't like the direction my NC was heading and decided to begin again.
I went back to stock using this: http://forum.xda-developers.com/showthread.php?t=945838
and then applied this: http://forum.xda-developers.com/showthread.php?t=922870
and so far everything seems stable.
The people on these forums amaze me with their technical know-how.
Having the EXACT same problem here after doing a wipe and upgrade to auto-nootered 1.1.
After successfully downloading and installing roughly 20 apps, any new downloads now stop at the "Starting Download...." stage. Ive also tried everything short of replacing vending.apk to fix the problem -- nothing has worked. Ill be trying that next... I'll report back after.
I just bought a Samsung Galaxy S3 SGH-T999L with Android 4.3, then downloaded Titanium Back-up, and then started removing several apps (in an attempt to strip the bloatware). Now when I go to Google Play and try to install a new app, I click the "Install" button and wait for the progress meter to reach 100%, but no "Open" button appears afterward (which used to happen). When I search my phone, there are no icons for any of the new apps I try installing.
Does anyone know which app I deleted that caused this problem? Thank you.
Put back you're nandroid backup. (I assume you make one before you start deleting some apps.)
Or flash a stock rom back without whipping. So you dont lose some data.
Send From A Devil3 - f2fs - Dualboot Jb4.3/cm11 Powered Machine
Have you tried rebooting the phone?
if you have installed TB then you have rooted the phone obviously. Explore your data folder from the root directory using TB or any advanced file explorers like Root explorer or Es file explorer. Find the apk files of the apps you have installed just to verify if your play store has downloaded the apps to your phone.
Also are you sure if you removed only bloatware or any core apks related to your android system... like eg: application provider.apk
I did not make a backup. Before flashing a ROM, I wanted to post here and see if anyone knows what app being deleted caused the behavior I described. That's what I'm wondering: Do you know which specific app being deleted would cause Google Play to have the described problem? When I try to install a new app, it gets to "100%" on the status bar, but subsequently fails to display the "Open" button. Everything else on the phone works flawlessly and I put a lot of time into customizing the phone with apps I like.
Having said that, I am curious about the option to flash a ROM that you mentioned. The reason I did not want an Apple phone is because they seemed to restrictive of options and freedom. But lately I am thinking about Google censoring AdBlock from Google Play, the EFF's criticism of doing away with AppOpps, and shoving Google+ down the throats of YouTube users. So, I looked into Cyanogen but my model of phone was not listed on Cyanogen's website for phones tested to work. I am interested to exploring the idea of flashing a ROM (which I never did before) but I definitely want to keep my 4G LTE functioning via T-Mobile. Any ideas?
Yes, I searched. Both issues. Separately.
So I'm finally entering the world of custom ROMs on my Galaxy S III after putting up with rooted stock (UGH TouchWiz) for two years.
The main trouble comes with apps post-flashing. Even between versions of stock (several of which were custom), when I had to wipe the device completely unlike now, whenever I'd sign into the Play Store, the apps I'd previously had installed would be reinstalled. Then, Titanium Restoring was really just a "making sure" option. But on all the ROMs I've tried (three so far), after installing Gapps and signing in, this just doesn't happen. I'm not certain why because it's the same device and I've used TiB to change the Android ID back, even.
And this wouldn't be such a problem IF TiB didn't A) NOT have an option to only restore user apps and B) break push notifications for apps that use them.
What gives? I've Nandroid restored back to stock twice because of this.
P.S. feel free to move this into a device-specific subsection if necessary. These seemed like general issues but they may not be.
621
Hello? This is kinda throwing a wrench in me being able to use my phone. No matter what I do, how many times I sync EVERYTHING, when I flash the new ROM it only downloads a few apps. I'm pretty certain sync just isn't working on my stock ROM. What do I do?
Hi,
I have some really strange App crashes since a few weeks: Google Photos won't run, an app from my carrier (MeinVodafone) and Google Search. The strangest thing is that Google Search is working...partially. I can not open the app directly, but I can open it via voice (timer etc is working and search also has no problems) and I can open the settings in Google Settings (Play Services). Attached are some catlog logs.
I'm running ParanoidAndroid 5.1 (5.1.1) on an d802. Build is from 1st june.
I'm also running XPosed Framework. I already thougt that WebViewGoogle could be the cause for that, but that would affect more apps and I haven't found any hint on that in the logs.
Any tips what could cause these strange crashes?
UPDATE: I just changed my system language to english (from German) and at least Photos is running without problems...
I have 3 possible solutions..
1. Reinstall apps
2. Wipe /data, /cache from recovery
3. Reinstall the rom or choose another rom.
Third should work but idk if you want that.
I already reinstalled them and I'm already running the second or third update. I'll try it with wiping /cache and /dalvik-cache, /data would delete all apps
Ok please update the thread with news
It looks like I cannot wipe /cache, it says done but shows the old "E: cannot mount storage" and then I stuck on boot animation for over 15 minutes, way longer than normal. Repair it also doesn't help that.
I know I can delete dalvik-cache by deleting the files in /data/dalvik-cache/arm. Is there a way for cache too? That would be the only way to do that
@Artim_96 yes there is a way but I think its pointless. Try flashing stock rom or any other non-lollipop rom and then return to lollipop.
I don't think that's the only possible solution. I'm on PA since January, the bug with Google Search and MeinVodafone is only since a few weeks.
It surely isn't only possible solution but it is recommended.
it is pointless to flash a KK ROM, restore the apps, install an LP ROM and restore the apps again. It just makes no sense to do so.
I never said to restore apps, wipe everything (system,data,cache) and flash rom and gapps.
So you want me to reinstall everything, right? Are you kidding me? And what should I use? A blank system just with Google Apps?
I now got search to work again, the problem was the XPosed Module "Force Immersive mode", the other app is still not working, so I made another log with all modules disabled.
But I found another bug: the location service seems to be not working properly: no app that should be shown is there and Google Fit was not working today. (I never really use it, so I just saw that and because Fit was draining the battery to much I just reinstalled it to test it)
Hello,
this is my first post.
My D6503's Camera stopped working after I updated to MM, well only after I played around with the permissions for the google services app. My phone was running stock and I didn't think that anything serious would happen.
I denied the google services permission to my camera in order to cut down on its power usage, unfortunately my camera and torch is now unable to open and keeps saying that the camera is unavailable.
I've tried various third party apps, when I launch them they say the camera is in use.
I've also noticed that my battery life has severely decreased as the camera itself is warm and I think it doesn't shut off.
Since then I've reset the permissions, factory reset, wiped the caches (including the dalvik) various times, rooted and installed a recovery and wiped everything, I've flashed every conceivable stock rom and currently I'm running a custom rom for a locked bootloader.
A few things that I've been wondering:
1.) Is it possible to reinstall or flash the hardware drivers specifically for the phone?
2.) Might I be able to fix this problem by unlocking my bootloader and installing a custom kernel and then reverting back to stock and restoring the TA partition?
3.) is it possible to totally wipe the phone's partition and install everything from scratch?
4.) The sony android system used to have a browser app that is now disabled and replaced by chrome, I've noticed that the browser app is actually still available in the software but a setting somewhere is specifically blocking the use for it. Might there be a service setting that I could reset to gain the function of my camera again?
5.) Might my TA partition settings be influencing my camera somehow (maybe after being corrupted) and is there a way that I could change the settings or edit my TA partition?