Has anyone else tried the new Google Music app which came out last week or so? For me it FCs on startup... anyone else seeing that? I've tried it running both Perception II and Continuum 5.5, same thing.
I had tried the leaked/prerelease versions of the app that were out a while back, and had no problem with them... I thought maybe the problem was that I still had some remnants of the old versions sticking around, but I cleared the app's cache, uninstalled and reinstalled, and since then have done a clean wipe install of Continuum, but same thing.... it only happens on my Captivate - the app works fine on my other android device. Anyone else see this?
http://forum.xda-developers.com/showthread.php?t=1072664
Been a known issue for Samsung Gingerbread ROMs. Works fine on Froyo and AOSP Gingerbread (MIUI/Cyanogenmod7)
hi,
i´m using docs master v11 at the moment. everything works great but music app has FCs. (7/10 times). other music apps still crash.
using voodoo, dont like dsp.
- tried deleting media data (showing trax 3 or 4 times in player)
- tried to reinstall app(s), but same problem.
is it a problem by source ? for me, some other ics roms still have the problem too. most is aokp base...
still a known problem?
anyone?
Related
I LOVE this appA! Probably my most used, and it unfortunatly hangs on the game overview screen, after a short dimming of the screen. Real bummer for me bc everything else is working great for me on Froyo!
...does anyone have this running successfully on FroYo?? Ive tried pushing into system/app thinking protection was maybe an issue but to no success...any help would be greatly appreciated!
There was another thread on here with ppl that had problems with this same app after froyo was installed. It doesnt even show up in the app store for froyo users. I have an off topic question: does androids mlb at bat app show live video feed of games? I kno the iphone app does. Thanks.
no its audio only and i miss this app tempted to go back to cm because i miss my baseball
infinityhombre said:
no its audio only and i miss this app tempted to go back to cm because i miss my baseball
Click to expand...
Click to collapse
Only works with 2.1 so far, no 2.2 support thusly the darkened screen.
No wonder... I kept thinking MLB at Bat shut my app
off.
just curious...since the MLB app is just for phone access, has anyone tried connecting with their desktop service with flash? Did it work well? I have a hard time justifying purchasing the android app if i dont get comp access as well, especially since it may be possible to have both.
Have not tried myself...
Anyone maybe have a fix for this since this thread has been started though? Still seems to have same issue.
it works just fine for me running 2.2 manual update
No problems with it either, manual download
I was experiencing the non-responsive dimmed screen as well. I went into the application info screen under Settings >> Applications >> Manage Applications and cleared data, cleared cache, forced stop, reopened...and it worked like with 2.1.
What do you mean manual download... I've been wanting to download this and I can't find it on the marketplace
I've loaded the new CM7 RC2 versions from 009 to 011.
The WLOD accurs when launching stock browser or facebook and some games.
What I've done is to go to Cyanogen Settings and to Performance.
I ticked the Set on boot checkbox and changed to Battery saver.. since then haven't had any WLOD on stock browser or facebook for android.
Guess this is OC related.
Although when I restart my phone it gives a "force close " error on Cyanogenmod Settings and changes my govenerback to on demand the WLOD is still not accuring.
Is the WLOD issue resolved in 012 or am I just lucky for now.
Also hope this works for more people or the Devs . Sorry but I can't post on the Devs Threads.....
I've tried everything... no WLOD on the 2 mentioned apps anymore. Don't know what fixed it , but it only stopped after as mentioned above
i would try this but im on the 12 rom. Are you suggesting that going back to 11 and changing the settings, then reflashing and restoring data would work?
I won't suggest that... I went on to the new v012 and now WLOD on v012..
I Will go back to v011 and do the same changes to see what happens..
This was not meant as a solution to the problem just maybe for the DEVS to have a look.
Also on v011 I can play fruit slice but WLOD on v012.
EDIT: also i've noticed when playing 3D games White LED coming on and off but not killing phone and when on low power,, this WLOD issue might be the Mhz Difference and battery types in lots of different phones.
So one custom rom maybe doesn't support various types, hense forth people getting diiferent WLOD crashes
EDIT : Now the fruit slice game works... Haven't changed anything..
This WLOD's are really an extreme random thing, DEVS must have a really hard time.
I think most people don't flash their phone completely the right way maybe even me..
I've noticed that unless you do a complete format of the sd card and don't restore anything from a previous version there is always something
left on the phone and when downloading the same app it uses that data. hense WLOD's (maybe)
v012 Facebook and Browser working
Ex : I've Reflashed my phone cleared all the things off and when I reinstalled the fancy widget's app the downloaded skins were still their, I think lots of apps leave traces so even with the cleaning tools that exist you dont always get rid of everything and with a restore lots of people probably import the corrupted files.
CM 7 v012 is alot better than v011.. Thanks to the DEVS..
i've Had minor issues that somehow sort themselves with a reboot after first load of a app,,, nothing else serious as yet.
v012 Is The most stable Android 2.3.3 so far.
Thanx
Was using a Note with GB and feedly (the news reader) ran fine, then after I upgraded to ICS Feedly just hangs at the first page of news. I uninstalled and reinstalled but the problem persists. Does anyone else face this problem?
Kind of know issue with ics. Feedlt is working on it.
It works with custom roms though
@Galaxy Note™…
Yep, I am encountering the same problem on an ICS Note
Hi
I can't post in real thread so it is here , I'm on big part from beginning (Everest XOOM) and at first everything works great but in last two weeks problem start both on Chrome and Chrome Beta.
I try dalvik wipe , cash wipe, try to use ART , try to reinstall both applications , to remove flash player and finally switch from OMNI to CM11 but there is still same problem
so if anybody have any suggestion it would be great
Many thanks in advance
I install ElementalX-Xoom-2.1 ( full version not vanilla ) and enable zrom and it is better I can work little longer on Chrome but eventually problem occurs again ...
gtrhr said:
I install ElementalX-Xoom-2.1 ( full version not vanilla ) and enable zrom and it is better I can work little longer on Chrome but eventually problem occurs again ...
Click to expand...
Click to collapse
I also had serious problems with Chrome constantly freezing and crashing on my Xoom wifi upgraded to Kitkat Omnirom 4.4.2. I've installed version 33 as advised in another thread (a developer one that doesn't allow me to post there), using an apk file linked on that thread.
I haven't tested this yet but, assuming it works ok, how do I stop it from updating automatically? Any idea on how we'll know when an update appears that is safe to install, and will work?
Chrome Beta
I had the same problem too. Chrome on Omni and TeamEOS kept freezing. Only to kill the running app was helpful till it freezes again.
Then I've installed Chrome Beta (v37.0.2062.55) and since then everything seems ok. Until now no more freezes.
Maybe anybody else to prove that?
Simple fact of the matter is, KK is just slow on the Xoom. I'm amazed that we even saw 4.4, seeing as how mine (wingray) is over 4 years old.
I ran CM11 there for a while, but the constant freezing of Chrome and the slow clunkiness of the interface was enough to drive me back to CM10.1
So, I'm obviously not remotely an expert when it comes to Android mods, but I'm finally fed up with being stuck on Android 4.1 - since it doesn't appear we'll ever get any upgraded qwerty phones ever again, I figured I'd try diy'ing it.
I have successfully flashed TWRP, rooted the phone, and installed what I believe(?) to have been the most recent version of CM11 (I figured it'd be cleanest to keep the phone closer to what it was designed for - I've seen tons of apps require 4.4 at minimum, not too many that require 5+): cm-11-20150626-SNAPSHOT-XNG3CAO1L8-moto_msm8960_jbbl.zip. Was the most recent version I could find, anyway?
I booted it up and for the most part, everything seemed to be working. Everything except Chrome, which crashes reliably and immediately. I tried clearing all the caches (the app's cache + data, and the phone's, from recovery), uninstalling and reinstalling Chrome, I tried the beta version (crashes), I tried a fork, Brave (crashes). Other browsers are working fine, but I like Chrome.
One weird thing I did notice: I was thinking it might be a gapps issue, but weirdly, the Play store, gmail, maps, everything else just installed and seem to work out of the box before I did anything with gapps? I did also try flashing the most recent base 4.4.4 gapps zip from what I could tell (gapps-444-base-20170209-1-signed.zip), but I'm not sure how to tell if it actually did anything? It said it flashed successfully, but (other than having to wait for all my apps to recalculate because I cleared all the caches), nothing noticeably seemed to change on the front-end as a result, and yes, Chrome still crashes. Should I be using a different gapps install than that for the Photon Q? Or anything else I should check/try? Thanks!
Yay! Answered my own question, with sufficient digging!
Answer seems to be basically: the newest version of Chrome (v55) exposed some sort of weird incompatibility with CM, so the easy fix is just not to use it, at least for now. I sideloaded Chrome v54, and it stopped crashing, yay! Source: https://forum.xda-developers.com/showpost.php?p=70762641&postcount=198
Just FYI, the latest version available for this device is CM13.
They are working on Lineage.
Edit - seems you found the CM13 thread already
Yep - I'm glad to see people other than (and smarter than) myself recognize the Photon Q's unique place as being the final and, sadly, best qwerty slider available for our use, and that it therefore needs to be actively maintained even if Motorola won't... I just figured it'd be better to use an OS closer to the one the device was intended to be used with. Once I'm done testing CM11 out on my old half-working phone (re-purposed to a test phone) and push it to my new fully-functional one, I will probably at some point upgrade that first phone to the latest to try it out (probably once a Lineage build comes out, so I can be on a build that's actively being maintained). For right now, though, I figured I'd stick with CM11. Any case, looks like CM13 exposed the same Chrome issue, anyway.