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
Related
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?
Recently upgraded my DINC to ICS using Abduction v1.81 and I'm having a problem with Chrome Beta. When I launch it initially everything seems fine, it asks for log-in info which is provided and then shows the tab and search icons. When actually entering a web address, though, the entire page is blank. It would seem that it is going to the address but nothing ever shows, regardless of what website is chosen.
I have searched the Abduction forum to no avail, no one else seems to be having this problem after the AOKP Build 26 update, or at least hasn't spoken of it. Possibly an HWA problem?
HTC Incredible
Abduction ICS v1.81
V6 SuperCharger (tried Chrome before/after running scripts...same issue)
Holo-mod
No other mods to speak of really. Any ideas would be appreciated.
chrome beta
i have had the same problem on my nexus s 4g running 4.0.4 and it would only open up and it would be blank and foreclose shortly after i noticed that it is a rom problem because i just flashed a new rom and chrome has been working great maybe do a back up and try a new rom see if that helps!
I have strange problem with PLEX since I moved from GB to LPY ICS. I can't connect to the media server over 3G or over Wireless external connection. If I try it in my local wireless network everything works fine. Same goes for Media Qloud.
I didn't change anything on my rooter or WF settings since I moved from GB. I found users reporting similar issues with S2 on ICS but nobody offered solution.
I wonder if any of you have similar problems.
plex error
hello, I had a similar problem with plex.
I found it on a warez site (I know it's wrong ...) and I fell in love with this application.
to support the Developeur I bought it ....
on gb no problem, but under ics I could not play video (seveur error ...)
I handed my pirated version v2.0.3.3 and it works again
Hm, it must be something specific to ICS for Note or S2. I tried version 2.0.2.6 but no luck.
I can't believe nobody else have this issue with ICS. Maybe something left form GB LC1 causing the problem. I did full wipe before flashing ICS but I can't do it now while I am on ICS since LPY kernel is dangerous.
Hi, I have a problem with the spelling of the HTC One S, only seems to work in certain applications such as sending SMS and Hangouts, but it isn't working in applications like Twitter or Facebook.
I tried activating the spell check of HTC and google. Any idea why that might be?
It happens with rooted stock roms with android 4.1 and 4.2, with Cyanogen seems to work properly but I love the stock camera and prefer to stick with the stock rom.
Thank you.
Any tips? The problem seems related to Sense, I installed a rom with android 4.3 and sense 5.5 and the problem still happens...
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