I know there's a lot of topics about this issue,
but I really haven't found a fix for it.
All of a sudden, a couple of days ago, anything I try to download off Market doesn't start, it just says "Download starting..." and hangs like that.
I am using wireless connection and I have used only wifi since I got the phone.
Problem occurred (maybe) as a result of these events:
- I have upgraded to the new radio (6.35) and SPL
- I have installed new radio ROM and used new google account to sign in (account2(at)gmail.com)
- I have downgraded radio and SPL
- I have returned to my old ROM by using nandroid restore (and in that ROM I have been using my first google account - account1(at)gmail.com)
So you can here see that the problem occurred after switching radios and switching gmail accounts.
Does anybody have any clue about how to fix this?
To repeat, I cannot download anything off the Market, download just hangs forever.
I had also faced some issues with market downloads.
For me it shows downloading.... for a long time but eventually it gets downloaded.
Wait time is also not fixed. Sometimes it gets downloaded immediately and sometimes it takes hours.
Problems with WIFI
It happened to me.
You should turn off WIFI wait for few seconds and enable WIFI again.
For me it worked.
Also see :
http://www.google.com/support/forum/p/Android+Market/thread?tid=57b5e3efa7477b50&hl=en
Thanks for the answers, but unfortunately, I haven't had any luck with fixing the problem...
And the Google Talk fix isn't working (signing in on google talk fixes problem to some people, and downloads start immediately)
A poster in the Amon_RA Donut Rom thread commented that he tweaked with the APN settings and that worked. He did not elaborate. You can check that thread and maybe PM him. I forgot who he was.
I've been getting occasional random reboots EI22, and I've seen reports in the general forum of the same.
There seem to be two main causes of reboots:
WIFI Related (bcm4329 DHD Bus Module TX Queue overflow)The reboots always happen when WIFI is on. The system will freeze up hard for about 10-15 seconds and then just reset. The LAST_KMSG file shows 60KB of nothing but the following:
Code:
[ 5315.816399] dhd_bus_txdata: out of bus->txq !!!
[ 5315.820979] dhd_bus_txdata: out of bus->txq !!!
[ 5315.825411] dhd_bus_txdata: out of bus->txq !!!
[ 5315.829922] dhd_bus_txdata: out of bus->txq !!!
[ 5315.834499] dhd_bus_txdata: out of bus->txq !!!
[ 5315.838929] dhd_bus_txdata: out of bus->txq !!!
[ 5315.843505] dhd_bus_txdata: out of bus->txq !!!
OneDram driver related reboots
After patching the WIFI related bugs I started to get these more often. Here is an example of the log leading up to the reboot.
Code:
[ 13.319028] [OneDRAM](dpram_write) Failed to get a Semaphore. sem:0, PHONE_ACTIVE:HIGH, fail_cnt:1
[ 13.339579] [OneDram] dpram_drop_data, head: 319, tail: 319
[ 13.351715] [OneDRAM](dpram_write) Failed to get a Semaphore. sem:0, PHONE_ACTIVE:HIGH, fail_cnt:1
[ 13.366965] [OneDram] dpram_drop_data, head: 319, tail: 319
[ 13.379178] [OneDRAM](dpram_write) Failed to get a Semaphore. sem:0, PHONE_ACTIVE:HIGH, fail_cnt:1
Another log sample from a reboot, right before it restarts...
Code:
[ 11.585629]
[ 11.585665] dpram_shutdown !!!!!!!!!!!!!!!!!!!!!
[ 11.590957]
[ 11.590986] dpram_shutdown ret : 0
[ 11.598695] Restarting system.
[ 11.600629] KERNEL:magic_number=0 CLEAR_UPLOAD_MAGIC_NUMBER
[ 11.608974] arch_reset: attempting watchdog reset
For the WIFI issue, I searched and found a set of patches on the linux driver project mailing list that address this issue.
See: http://driverdev.linuxdriverproject.org/pipermail/devel/2011-March/012948.html
After applying the patch verbatim I still got the WIFI related reboots, so I slowly pushed the TXQLEN values up until the reboots stopped. Here is the commit from my github that contains the patch that seems to have done the trick.
As for the OneDRAM related reboots, I think I may have found the solution to these too. The problem seems to have gone away when I switched the specific ARM toolchain that is mentioned in the Samsung kernel source README. Previously I was using the 4.4.x toolchain from Googles repo. Thanks to Earthbound for working with me on this one. Aside from Earthbound (he uses the recommended Codesourcery one), I don't know what toolchains others use, but I do know that I have not had one reboot in the four days since switching to the CodeSourcery toolchain.
Here is a kernel (source) with the WIFI fix that was compiled with the 2009-q3-68 toolchain. Aside from the WIFI fix, the kernel contains the following features:
root/su/busybox
init.d script support
bootanimation.zip support
overclock to 1.4/voltage control
keyboard delay fix
ext4/rfs support
CWM5/ROM Manager support (reboot bml8 recovery)
If you are having WIFI or dpram/onedram related reboots, you might want to give this kernel a try and report back.
NOTE: If you overclock or over/under volt please stop doing so if you want to test this kernel and post logs.
Interesting I'll have to try it out, thanks for this!
Sent from my SPH-D700 using XDA Premium App
Thanks for this. Just need an EI22 branch now hehe.
Sent from my Epic 4G
I've experienced a few ramdom freezes and reboots lately even when overclocked to previously stable frequencies- ever since I successful ran with 1.5ghz enabled for two minutes.
I gave this a go, and overclocked to 1.4 and my phone went into a reboot loop- the rom booted up, but would freeze and reboot shortly afterwards.
I'm stable again now after running the VC cwm zip to restore settings to 1ghz.
Is there any useful feedback I could provide? Some sort of log or something?
Sent from my secret underground bunker
I just got another reboot...same issue.
So much for that!!
This bug is defintely causing the reboots though.
mjben said:
Is there any useful feedback I could provide? Some sort of log or something?
Click to expand...
Click to collapse
The system keeps logs in /data/system/dropbox
After a reboot the file with a name like " [email protected]" will contain a copy of the last system log buffer before your phone restarted.
But like I said I just got another reboot. I ran a speedtest over wifi using the speedtest.net app just before my last two reboots so I might be onto a way of triggering the bug.
I'm going to continue working on this. I'm experimenting with larger and smaller TXQLEN values.
Right now running with a TXQLEN of 4096 instead of 2048. It may be that larger is not better; that I needed to go smaller.
I'll keep my github updated.
So how was this different then froyo? Or did the tab ever have reboots?
sent from my always aosp epic
Excellent work!
I'd jump all over this but I stopped getting them after IAP 1.0.5+.
If they start up again I will report back.
the only time i have experienced this particular reboot concerning wifi, was having wifi + 4g enabled at home after a dalvik cache wipe (where the phone starts up, 4g starts first, then wifi simultaneously gets on LAN - both icons are showing, locks up - then reboot) once it restarts, it's all ok, wifi starts first, and doesn't happen again.
(running IAP samurai 1.0.4)
darkierawr said:
Excellent work!
I'd jump all over this but I stopped getting them after IAP 1.0.5+.
If they start up again I will report back.
Click to expand...
Click to collapse
AFAIK, the Earthbound is only mucking around with frequencies and voltages in his kernel. Of course I'm basing this on the only source he has posted, which was from two or three versions of his kernel back. He hasn't posted the source for any of this new builds, so apparently he still views GPL compliance as optional.
The reboots don't happen that often. I've gone many days without a single reboot and then gotten them multiple times in one day.
SenseiSimple said:
the only time i have experienced this particular reboot concerning wifi, was having wifi + 4g enabled at home after a dalvik cache wipe (where the phone starts up, 4g starts first, then wifi simultaneously gets on LAN - both icons are showing, locks up - then reboot) once it restarts, it's all ok, wifi starts first, and doesn't happen again.
(running IAP samurai 1.0.4)
Click to expand...
Click to collapse
No 4G service for me within 40 miles, so I never turn it on, but now that you mention it the lockups I've had have seemed to happen during that split second when both 3G data and Wifi icons show up in the top bar.
toadlife said:
No 4G service for me within 40 miles, so I never turn it on, but now that you mention it the lockups I've had have seemed to happen during that split second when both 3G data and Wifi icons show up in the top bar.
Click to expand...
Click to collapse
yeah maybe something about having two sources of internet... being assigned two addresses, no idea...
earthbound is stuck on the frequency tuning, but i think it's so stable because of the trunks he started with.
SenseiSimple said:
yeah maybe something about having two sources of internet... being assigned two addresses, no idea...
earthbound is stuck on the frequency tuning, but i think it's so stable because of the trunks he started with.
Click to expand...
Click to collapse
What trunk did he start from? He's got no history in github.
I'm assuming nubecoder's since his initial kernels had nubecoders broken video recording. I took a quick look a nubecoder's tree and nothing network related is touched there.
Anyhow in the general and Q&A forums have two reports reboots with Samauri 1.04, so that kernel is definitely not immune.
toadlife said:
What trunk did he start from? He's got no history in github.
I'm assuming nubecoder's since his initial kernels had nubecoders broken video recording. I took a quick look a nubecoder's tree and nothing network related is touched there.
Anyhow in the general and Q&A forums have two reports reboots with Samauri 1.04, so that kernel is definitely not immune.
Click to expand...
Click to collapse
yeah it's not immune, as i said it's happened to me, but it's appeared to me he started picking and choosing from nubernel into rodderick's clean kernel, and as he's said in his OP for samurai, there are elements of Genocide and other forerunners.. i forgot which, he's since removed the part where he says where his mods come from... he did at one point put in a fix for wifi issues, i'm not sure if it's in relation to the same issue (i think it was a general connectivity thing).
i have a short list of todo's for a kernel and have made headway but i really have no desire to compete with the 4 (including yours) on here.
SenseiSimple said:
i have a short list of todo's for a kernel and have made headway but i really have no desire to compete with the 4 (including yours) on here.
Click to expand...
Click to collapse
We are not competing. I just want my phone to be stable. Collaboration is what makes open source work. If you have ideas on how to make our kernels better share them.
@ toad
Iv'e been using your rom for over week and the e122 modem and have not had any reboots.
I do not overclock
I use 4g when i drive in a certain area to stream pandora faster and then it connect and reconnect to 4g
Ive connected wifi and 3g at the same time for picture mail and charging to my sprint account and still no reboot
Dangg.. I had no idea ppl had random reboots on ei22.. I've not seen one.
ksmullins88 said:
Dangg.. I had no idea ppl had random reboots on ei22.. I've not seen one.
Click to expand...
Click to collapse
I just had another one. This time it was the OneDRAM driver triggering a `reboot now`
CAn anyone explain what the OneDRAM driver does?
Toad,
Running your Kernel and Clean GB I had WiFi reboots every 3 to 4 minutes. WiFi would drop and go to the router for DHCP to hand out the IP again. I figured I would give you a chance to work on it and run rooted stock for a few days before trying Clean GB again as I like it! This same issue was even worse for me with ACS ICS v4.
Running rooted stock is a different story all together! I don't get the random WiFi drops, instead I get Android reboots with the freezing that's mentioned. Things run great for awhile before I get stuck in a loop of reboots. I noticed this last time that touchwiz lost all the bar icons besides the applications drawer icon. the bar also doubled in size along with the icon. Very strange!
Anyway, I was able to drop the default home between reboots this last time. The next reboot I launched ADW instead of TW. ADW instantly crashed and offered to email a bug report, So I did. In the stack trace I see that android Package manager has died as a cause of the exception. I am not a java programmer so am at a loss here to what's really happening.
Anyway, I hope this long story may be of some help in tracking this issue down. It looks like quite a few people are having it, and I myself don't want to go back to Froyo
Cheers,
Dave
---------- Post added at 02:02 AM ---------- Previous post was at 01:53 AM ----------
Here is a copy of the stack trace I mentioned...
Stack :
=======
java.lang.RuntimeException: Package manager has died
at android.app.ContextImpl$ApplicationPackageManager.getApplicationInfo(ContextImpl.java:2062)
at android.app.ContextImpl$ApplicationPackageManager.getResourcesForApplication(ContextImpl.java:2554)
at org.adwfreak.launcher.LauncherModel.a(Unknown Source)
at org.adwfreak.launcher.LauncherModel.b(Unknown Source)
at org.adwfreak.launcher.LauncherModel.b(Unknown Source)
at org.adwfreak.launcher.LauncherModel.a(Unknown Source)
at org.adwfreak.launcher.ck.run(Unknown Source)
at java.lang.Thread.run(Thread.java:1019)
Caused by: android.os.DeadObjectException
at android.os.BinderProxy.transact(Native Method)
at android.content.pm.IPackageManager$Stub$Proxy.getApplicationInfo(IPackageManager.java:1280)
at android.app.ContextImpl$ApplicationPackageManager.getApplicationInfo(ContextImpl.java:2057)
... 7 more
Cause :
=======
java.lang.RuntimeException: Package manager has died
at android.app.ContextImpl$ApplicationPackageManager.getApplicationInfo(ContextImpl.java:2062)
at android.app.ContextImpl$ApplicationPackageManager.getResourcesForApplication(ContextImpl.java:2554)
at org.adwfreak.launcher.LauncherModel.a(Unknown Source)
at org.adwfreak.launcher.LauncherModel.b(Unknown Source)
at org.adwfreak.launcher.LauncherModel.b(Unknown Source)
at org.adwfreak.launcher.LauncherModel.a(Unknown Source)
at org.adwfreak.launcher.ck.run(Unknown Source)
at java.lang.Thread.run(Thread.java:1019)
Caused by: android.os.DeadObjectException
at android.os.BinderProxy.transact(Native Method)
at android.content.pm.IPackageManager$Stub$Proxy.getApplicationInfo(IPackageManager.java:1280)
at android.app.ContextImpl$ApplicationPackageManager.getApplicationInfo(ContextImpl.java:2057)
... 7 more
android.os.DeadObjectException
at android.os.BinderProxy.transact(Native Method)
at android.content.pm.IPackageManager$Stub$Proxy.getApplicationInfo(IPackageManager.java:1280)
at android.app.ContextImpl$ApplicationPackageManager.getApplicationInfo(ContextImpl.java:2057)
at android.app.ContextImpl$ApplicationPackageManager.getResourcesForApplication(ContextImpl.java:2554)
at org.adwfreak.launcher.LauncherModel.a(Unknown Source)
at org.adwfreak.launcher.LauncherModel.b(Unknown Source)
at org.adwfreak.launcher.LauncherModel.b(Unknown Source)
at org.adwfreak.launcher.LauncherModel.a(Unknown Source)
at org.adwfreak.launcher.ck.run(Unknown Source)
at java.lang.Thread.run(Thread.java:1019)
**** End of current Report ***
The MOG Mobile Music App gives me a message complaining about no internet connection, or the fact that it can't connect to servers, and it doesn't get past the initial startup splash screen for me to log in or do anything. I've tried forcing it into offline mode several ways, but the app simply will not launch completely. I have perfect internet connection with everything else. It is working just fine on the October 14th Nightly, but is unusable past this, most notably on October 16th and beyond. This is an issue on ALL CM-Based ROM Nightlies dated past Oct 14 such as Beanstalk, Carbon, PACman, etc. So I know it is an issue with a CM patch/update past Oct 14. Is there any way I can resolve this? Running it on a Motorola Atrix HD on the kernel that came with a ROM, I could try another kernel but I doubt it would help anything. Is anyone else having the same issue on other phones? Originally I thought it was a JB 4.3.1 issue but seeing as Oct 14 runs on 4.3.1 it is not. I always clean flash.
Same Problem
Neighbor808 said:
The MOG Mobile Music App gives me a message complaining about no internet connection, or the fact that it can't connect to servers, and it doesn't get past the initial startup splash screen for me to log in or do anything. I've tried forcing it into offline mode several ways, but the app simply will not launch completely. I have perfect internet connection with everything else. It is working just fine on the October 14th Nightly, but is unusable past this, most notably on October 16th and beyond. This is an issue on ALL CM-Based ROM Nightlies dated past Oct 14 such as Beanstalk, Carbon, PACman, etc. So I know it is an issue with a CM patch/update past Oct 14. Is there any way I can resolve this? Running it on a Motorola Atrix HD on the kernel that came with a ROM, I could try another kernel but I doubt it would help anything. Is anyone else having the same issue on other phones? Originally I thought it was a JB 4.3.1 issue but seeing as Oct 14 runs on 4.3.1 it is not. I always clean flash.
Click to expand...
Click to collapse
Seems like I'm not alone in trying to figure out why MOG hasn't been working for my phone. I came from a Google Play Store ROM of 4.3 on my Samsung Galaxy S4, which was working fine but wanted to test out CM 10.2. However, since switching to CM 10.2 a few days ago, I have not been able to get on MOG. I thought it might been an issue with MOG until I restored from the backup prior to CM 10.2 and it's working fine. I'm not sure what patch is in CM 10.2, but I would agree with Neighbor808 that something is causing an issue with MOG.
Fuzzums said:
Seems like I'm not alone in trying to figure out why MOG hasn't been working for my phone. I came from a Google Play Store ROM of 4.3 on my Samsung Galaxy S4, which was working fine but wanted to test out CM 10.2. However, since switching to CM 10.2 a few days ago, I have not been able to get on MOG. I thought it might been an issue with MOG until I restored from the backup prior to CM 10.2 and it's working fine. I'm not sure what patch is in CM 10.2, but I would agree with Neighbor808 that something is causing an issue with MOG.
Click to expand...
Click to collapse
Same issue for me on a Verizon Samsung GS3. Had to go back to 10.1 because I use MOG all the time. Hope someone addresses this.
Me too on galaxy s3 att - either with CM 10.2 or task650. I've had to revert to 4.2. Then you can at least download a bunch of music for offline use and then restore a tibu (as long as you don't disturb the MOG folder in the sd card) and play like that. It sucks, but MOG won't help you since they're committed to beats audio only.
Mog locat
I really hope this thread hasn't died. I have been digging for about a week and i'm at a loss. It seems something changed with cm around oct 14 and ever since then (already stated) that mog doesn't connect. If I stay at the mog startup screen I get the connection was lost message. And also I can get into settings, I get all the usual options but whats weird is at the top it says i'm not logged in and the only option I get is to sign out. I also was able to speak to mog tech support for a couple of days before they figured out I was rooted, at wich time they stated they cannot help me, but they stated all problems with androud 4.3 have been resolved so i'm pretty sure the problem is cm 10.2 and not 4.3. I pulled a logcat of my phone sitting at idle, opening mog, sitting some more and then closing the app. I'm not very experienced at coding or reading logcats but I did run across this
I/SELinuxMMAC( 615): package (com.mog.android) installed with seinfo=default
I/ActivityManager( 615): Process com.cyanogenmod.lockclock (pid 15208) has died.
I/ActivityManager( 615): Force stopping package com.mog.android appid=10099 user=-1
W/PackageManager( 615): Not granting permission android.permission.READ_LOGS to package com.mog.android (protectionLevel=50 flags=0xbc44)
W/PackageManager( 615): Not granting permission android.permission.BIND_WALLPAPER to package com.mog.android (protectionLevel=18 flags=0xbc44)
W/PackageManager( 615): Unknown permission android.permission.START_BACKGROUND_SERVICE in package com.mog.android
W/PackageManager( 615): Not granting permission android.permission.DEVICE_POWER to package com.mog.android (protectionLevel=2 flags=0xbc44)
W/PackageManager( 615): Unknown permission com.verizon.vcast.apps.VCAST_APPS_LICENSE_SERVICE in package com.mog.android
Like I said I dont really know what any of that means but I tried to do research of what w/packetmanager and i/activitymanager are but I am unable to figure anything out.
If anyone is able to decipher any of this I would be very grateful. Also if it helps I have posted the full logcat below
I appreciate any and all help on this problem and I really hope someone can figure this out and get mog working for people running 10.2
http://www.2shared.com/document/1GgfAm9f/mog_launch_and_run.html
new development
I don't remember where but in passing I read that another carrier blocked streaming music. I found that when I tried to use Google play much I got an error similar to the one in Mog. I'm not sure how but I guess you have to dial into the phone and change settings to allow streaming. Going top do more research and hopefully figure something out.
Edit
must have been a temporary problem with Google play, looks like music is working. I really don't want to switch but might be the inky way.
Few days ago, around the 15th of october I started having every few seconds crashes of the google play services.
The error is java.lang.illegalArgumentException wakelock not active.
The frequency of the error makes the phone unusuable.
Initially I though the problem was because I was on older stock release (KTU84Q). Due to a problem I had with my car bluetooth with newer versions I choosed to keep 4.4.4 stock.
So I let the phone make all the incremental updates (OTA) up to the last one (5.1.1 LMY48B).
Unfortunatelly the problem with play services did not go away. So I did a full wipe and went through the initial install procedure. A few minutes latter, still while setting up the phone the crash came back. Except the ROM apps at this point there are no other apps installed. I notice the crashes happened when play services was updated right after I set up my google account.
The play services version that crashes is 8.2.99. I downgraded to 8.2.98 and I still have the crashes. So I went down to 8.1.15 and no more crashes.
The problem is that after a while the phone updates to 8.2.99.
So the questions are:
Is it only me that has this problem?
How do I fix this?
In any case how do I prevent the update of the playservices?
After little search I found the solution.
I had to enable privacy guard and then enable KEEP AWAKE of Google Play Services.