Boots to Pandora splash screen with the following message
Pandora http error occurred code: 417 startupAsyncTask
Worked prior to 2.2
Running 2.2 OTA with PRI 1.34-rooted then installed RUU trying to restore PRI to 1.4
Tried uninstalling, reinstalling
Clearing Data and Cache
Any ideas?
SOLVED-8/14/10
So after trying many, many things including several uninstall/reinstall deleting cache and data in the Pandora app and many ##786# while trying to get to 1.4 wiping the user data I got it.
The solution was to boot into recovery and clear the cache here. My guess is that some trace of Pandora was still left and was screwing things up.
For those that don't know how to do this:
1. Unit off hold down the volume up and power button at the same time.
2. This will boot the android on skateboard screen
3. With Bootloader highlighted -the default setting-hit the power button
4. Give it a second and it will HBOOT
5. Use the volume down button to navigate and highlight recovery and hit the power button.
6. If you get the red exclamation in the triangle as I did hold down volume up for a couple seconds and hit the power button while continuing to hold the volume up
7. You will now be in the recovery mode, navigate down to wipe cache partition and hit the power button
8. Reboot and you should be good.
translux said:
Boots to Pandora splash screen with the following message
Pandora http error occurred code: 417 startupAsyncTask
Worked prior to 2.2
Running 2.2 OTA with PRI 1.34-rooted then installed RUU trying to restore PRI to 1.4
Tried uninstalling, reinstalling
Clearing Data and Cache
Any ideas?
Click to expand...
Click to collapse
sorry, confused. What rom are you currently running? Are you doing anything funky, like installing the app on the sdcard?
Thanks for the prompt reply.
Installing Pandora from the marketplace
I was running rooted ota 2.2 and had this issue.
Used the recovery utility and wiped and reinstalled stock 2.2 hoping the pri would update to 1.4 and am still having this issue.
Really strange.
I'm getting this error after switching to midNight ROM with EXT4 file system. Clearing the cache does not help. Uninstalled, reinstalled. Uninstalled, cleared cache, reinstalled.
The weird thing is that it worked one time right after flashing the updated ROM and then the next (and every time after) I get this error.
I am getting this error 417 on my Archos 101 android tablet running Froyo.
The thing is, I installed Pandora on my Dads tablet, he got the same error. However, after he went home, he called to report that it is working.
My suspect:
Something in the port forwarding or firewall (I'm using Smoothwall Express 3.0).
I'd love to hear anyone's input and things to try.
I havent tried my Pandora install on another network other than my home. That would tell me if it's related to my network, but I don't know how to troubleshoot beyond that.
Thanks for any help or responses.
I got the Tablet this morning, and was very happy that it arrived so quickly. However, it seems that there is a several bugs in the system that I don’t know what to do about it.
Yahoo messenger will install, allow you to enter your log in information, but will get stuck on yahoo screen with the smiley face, and “loading contact list.” but will NOT load in. Skype and Nimbuzz works fine BTW.
Pandora Radio will not load at all, and will give several error messages. Boots to Pandora splash screen with the following message Pandora http error occurred code: 417 startupAsyncTask
Sling Media player will log in but won’t load the video.
Since I’m deployed in Iraq, it would be much easier to try to fix the problem before thinking of returning the tablet, so, I used Rom Manager, and tried clearing the cached data associated with it. Restored to factory setting. Then I got in contact with Yahoo who after 2 hours of tech support cannot tell me why this is happening. Pandora referred me to Samsung, and Sling Media don't offer support for the tablet, they only offer support to their software. I really don’t have the time and tools to chase tech support from here. Can someone HELP PLEASE?
REALLY SOLVED-Pandora-http error occurred code: 417 startupAsyncTask
After months and months of trying to resolve this issue on my Samsung Vibrant phone, I discovered the true cause of the problem in my case, and it wasn't the phone at all.
It was due to my transparent proxy server.
I use Smoothwall Express 3.0 for my firewall and utilized the built in transparent proxy services. Whenever I used the Cellular network, Pandora would work just fine. However, whenever I used the WiFi network (With transparent proxy services) I would get the "Pandora-http error occurred code: 417 startupAsyncTask"
Since most Cellular networks don't use proxy servers, if you find Pandora works with no issues with WiFi disabled, then consider that the problem is with the network the WiFi is connected to and not the phone. Most likely there is a transparent proxy server in operation somewhere between you and the Pandora servers.
I believe that you are correct because I'm also running Smoothwall express. Perhaps I can figure out how to get the traffic to bypass through. I'll report back if successful!
Awesome find!
Hi,
currently I'm running the ev nightly-2014-01-02. Since several days I ty to activate a VPN connection into my home lan (connected with an AVM Router). It does NOT work. While the "internal" VPN Software does not tell me some interesting information a second try with VPNCilla shows:
--- cut here ---
Error on establish:
command '693 interface fwmark rule add tun0'
failed with '400 693 Failed to add fwmark rule (File exists)'
Possible reason: invalid server parameter or TUN device unavailable
---cut here ---
With this error message I find in google some information about a VPN problem in 4.4. BUT: my wife's brand new nexus 5 with Kitkat connects without trouble immediately with the same login data.
So what's the problem with ev here?
Any ideas?
Thanks in advance
Steill awaiting response
Really nobody here any ideas?
Hello,
I keep getting the following error messages in the adb logs of my T800 every 5 seconds or so. I'm using the official 5.0.2 Android version supplied by Samsung.
[SDP.PUB_CRYPTOD] ERROR - Failed to open the netlink socket with error: Protocol not supported
[SDP.PUB_CRYPTOD] ERROR - Exiting
What can I try to solve that issue, or at least to stop the system from trying to relaunch the failing sdp_cryptod daemon?
I'm getting the same error all the time, and when it happens I cannot access Internet... Did you figure it out?
Are you using encryption?
Code 14: Could not open database. Some sort of permissions problem?
I have had CM 12.1 on a Nexus 5 for a while. Every time I upgraded to CM13 everything would work fine EXCEPT messaging would keep throwing "Sorry, messaging has stopped" message. So I Stayed on CM12.1. I just upgraded to a Nexus 5X and there is no CM12.1 for it so I tried Cm13 (Latest Nightly 6-18) and it seemed to work fine, just on WiFi and setting it up. I loaded what I always do, Android Firewall, checked all my permissions in Privacy Guard, used SU2.95 so I would have root. It still worked fine connected to my WiFi. I just got back from TMobile where I had to switch from MicroSIM to NanoSIM. put the sim in and the same messaging error shows up. So, working backwards, I unchecked ALL privacy guard, turned OFF the firewall, and rebooted. Still gives me the messaging error. So, I finally read the error message and its SQLite Error 14 on some database. Any ideas what I could try next? I suppose I can reload CM and set it all up again, and see where it starts to fail but that would be throwing away 4 hours from yesterday. I'm also not certain that the native App permissions aren't involved somehow. The phone IS encrypted but I have tried it both ways in the past.
I know there are all sorts of geniuses on here, and I am not smart enough.
Code:
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:309)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354)
at java.util.concurrent.FutureTask.setException(FutureTask.java:223)
at java.util.concurrent.FutureTask.run(FutureTask.java:242)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
Caused by: android.database.sqlite.SQLiteException: unknown error (code 14): Could not open database
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:179)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:135)
at android.content.ContentProviderProxy.query(ContentProviderNative.java:421)
at android.content.ContentResolver.query(ContentResolver.java:493)
at android.content.ContentResolver.query(ContentResolver.java:435)
at com.android.messaging.util.f.oH(SourceFile:53)
at com.android.messaging.util.f.doInBackground(SourceFile:34)
at android.os.AsyncTask$2.call(AsyncTask.java:295)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
... 4 more
EDIT : so i got into App permissions (new to MM?) and made sure the messaging service had storage and read and write on SMS. still looking deeper and searching the net...
EDIT : APN issue? reset to default TMobile settings and rebooted. still fails.
EDIT : could it be that I used the PICO version of OpenGAPPS? anyone had a problem with that? been searching still...
SOLVED : I'm such an idiot. I have been moving my blacklist.db database from version to version so I dont have to put all the numbers in again (wouldn't it be nice if there was a blacklist manager? I have all these spam numbers attached to a contact but you still have to choose them one by one) and of course between CM 12.1 and CM 13 they changed the database format or something so thats why it was crashing. Just one of the many steps I took getting my new phone set up.
If you pull SIM card out of the phone, does the crash still happen?
Reset ZenFone 2. Now asking to verify the account but getting "disallowed_useragent"
I was having touch-screen issues so I reset my phone. When I boot now I get prompted for language, wi-fi, etc. Next screen says:
Verify your account
This device was reset. To continue, sign in with a Google Account that was previously synced on this device.
Click to expand...
Click to collapse
The problem is that there's no place to enter any information, just a button "Verify account". When I press the button I get a Google error:
403. That's an error.
Error: disallowed_useragent
Google can't sign you in safely inside this app. You can use Google sign-in by visiting this app's website in a browser like Safari or Chrome.
Click to expand...
Click to collapse
...but I don't know the app and I can't do anything else on the phone. Can anyone provide an answer on how to fix it?
UPDATE:
So the OS version was really old. I went through a series of updates by side-loading the ROMs from the ASUS support site. After 3 or 4 upgrades I had a completely different experience and it let me verify my account. All seems well for now.
Just a couple of notes in case someone else has issues:
- Using Fedora (linux) desktop I needed to use "sudo ./adb devices" to be able to start the server and perform the side-load. Without "sudo" I was receiving an error about permissions.
- I performed the upgrades starting with the kernel version that was already on the phone and then upgraded to the next release each time after booting to each upgrade. I did this because I received an error on one upgrade saying I couldn't go there directly.
Peace.
I have the exact same issue with a phone that I'm trying to setup for my kid. Where did you get your firmwares for this phone?
Start by going here: https://icr-am.asus.com/webchat/icr...634.649586617.1546133606-337662955.1546133606
Then select "Download Center" from the chat window pane. Select your specific phone model. Select BIOS & FIRMWARE. Be sure to select the correct version for your phone (WW, CN, JP, etc.)
Good luck!