Flike HD Wallpapers Force Closing Every Time on CM7 - Nook Color General

Anyone else experiencing something like this? I want to make sure it's not just my nook and that it's something that will be resolved either on the app's side or on CM7 at some point. It works fine on my G2 running CM7, so i figure this might be a nook issue or an issue with my particular setup.
Is it working for anyone else? I tried the regular Flikie and it won't even open without FCing...at least the HD one starts up and works for a bit before it randomly shuts down on me. Sometimes the force close dialog comes up and the app still runs fine before it FC's again...not sure what's going on. It runs pretty smoothly too...

Related

Gameboid problem?

Hey, I'm loving my MTS so far, really nice phone. I downloaded most of yongzh's emulators, and it's working great
Problem is, on Gameboid, the emulator seemingly randomly stops and takes me back to the ROM selection screen(or sometimes just resets game). I've tried 2 different GBA bios images. This happens on just about every game I've tried.
Anyone else experience this? Any solutions?
shinkinrui said:
Hey, I'm loving my MTS so far, really nice phone. I downloaded most of yongzh's emulators, and it's working great
Problem is, on Gameboid, the emulator seemingly randomly stops and takes me back to the ROM selection screen(or sometimes just resets game). I've tried 2 different GBA bios images. This happens on just about every game I've tried.
Anyone else experience this? Any solutions?
Click to expand...
Click to collapse
Sorry to here that pal,seems to be working fine for me,i play it all the time,hope they make a game grip for it.
i actually cant even play a game. with gameboid, snesoid and gensoid none of them save my settings(so gameboid can never find the bios file). I e-mailed the dev about it. i think hes looking into it.
Thanks for the replies
And when I set the location of the GBA bios image, it saves that setting fine. The emulation itself is excellent- I was surprised how good it was, actually- except it just randomly stops(doesn't force close- takes me back to ROM selection screen). Even weirder, when this happens it pops up the "Gameboid is running" notification as if I had left the emulator running and went to the home screen. The Nesoid and Snesoid emulators do not have this issue, which baffles me all the more.
Funny you should mention settings not saving, though. My Random Ringtones app will not save the ringtones I have selected in my playlist. After I put a check mark in all of them, when I go back later the check boxes are all cleared. This problem's not as important to me as Gameboid though. I hope it gets fixed
This is not a MTS issue, when i was on my G1 it took me like 4 tries to get the Bios to work correctly. I'm thinking its just an issue on the app itself.
I just tried it on my G1 and I'm having the exact same problem(emulation exiting randomly back to ROM selection screen) >.>
So Jerzeeloon and mylostlonelysoul, since you guys have had success getting this to work correctly, think one of you could PM me?
I have the same problem of randomly returning to the ROM selection menu.
If you like at the Gameboid app in the Marketplace the developer put a note saying "NOTE: I am trying to fix the crash on HTC Legend and MyTouch Slide!"
He's updated and the issue is, indeed, resolved! I've been playing Castlevania: Harmony of Dissonance for the past week and enjoying it immensely. This emulator can go full speed on the Slide almost with no frame skip! Lovin in

[Q] Angry Birds Beta Lite

I was looking forward to playing Angry Birds on my game since I saw how much fun it was on Apple platforms, however there is a problem it's not working on my mytouch 3g. I was wondering if anyone else had this problem as well? Also it wasn't showing up in the market even though Rovio said it would. I'm also running Cyanogen Mod 6 which might be a reason why it's not working.
same problem with me.
can not find in on the market but a direct dl link.
game is just showing the logo and then crashing :-(
I'm having the same problem on my fiancee's mytouch 1.2. Her phone's not rooted, which is what I suspected to be the problem. but if you're not getting it to work even on froyo, I'm guessing it could be a hardware issue. It's strange though, because someone in the vibrant forums said that they had it working on their G1...
My logcat shows that there is an issue with hw3dc. Not sure how to fix that tho.
Sent from my jitterbug
I've looked around and I've seen people say they've gotten it to work on their mytouch 3g. I'm just curious what the problem could be. Be nice if someone who did get it to work could reply and tell us how they got it to work.
I have the same problem, just saw a nice logo with birds and then ..... homescreen :S
Not working on mine aswell. Read something that it will only work on second generation android devices...
If it only works for second generation devices I'm curious as to why they would list mytouch 3g and other similar devices as compatible with the game.
I can't get it to install after downloading it externally (magic 32A with froyorider v1.0)
finally got this running on my vodafone magic running CM6.0 tapping the screen seems to keep the process active so android doesn't auto shut it down when gets low memory
I also got it working on my Rogers Magic running CM6 by repeatedly tapping the screen as the game was loading.
Sent from my HTC Magic using Tapatalk
So i'm guessing it's a low memory problem then?
Edit: So I managed to get passed the title screen by tapping the screen repeatedly however I'm still unable to play it.
Re-edit: Never mind I got it to work. It works fine now.
Runs on my rooted ION running CM6. But it does seem to just stop after a little bit launching a bird. I will try tapping the screen to keep it running.
I'm not sure if it's just cause the game is a beta or not but I've noticed that some parts of the landscape is just white. I'm pretty sure it's supposed to be grass but all I see is white. Does anyone else get that problem as well?
Works on my mt3g running 6.0 rc3, tapping on the load screen does seem to help...once it loads it has not crashed
Sent from my HTC Magic using XDA App
I get that white land problem too! Seems like a pretty wierd bug...
wow the same problem like me! but it runs smoothly in eclair.
ya i get the white border thing too...
Hm....maybe it's a bug then? or it could be that our phones can't render the landscape properly.
Tapping, or rather holding my finger on the screen worked for me too. MyTouch 3G (32B) with CM6.
I had never played this game before and I went from "this is stupid" to "I have done no work for 3 hours."

[Q] NC Keyboard disappears

Just updated to v1.2.0 and re-rooted, but now I have a strange problem. I tried searching these forums, and The Google, but couldn't find anything helpful.
When you click in a text field (e.g., the search box, or the address bar of the browser), the keyboard will pop-up for about 1/2 second, and then minimize again. You can do this repeatedly with the same result - the keyboard just won't stay open.
I've tried rebooting, and even installing a different keyboard (can't get them to appear as an option in NCTools).
Has anyone else run into this? Were you able to fix it?
This used to happen to me when I used a Archos 28 "tablet". It was because there wasn't enough RAM most of the time, so it would close the keyboard to make more.
I doubt that's the case for the Nook Color, though. I've never had a problem with memory on these things.
I've had that happen as well but strangely only when the nook is at an angle like when I'm laying on my back in bed with the screen above me angled downward, tilting the screen so that it is facing up solves it for me, like I said, strange.
Sent from my NookColor using XDA Premium App
ninpo said:
I've had that happen as well but strangely only when the nook is at an angle like when I'm laying on my back in bed with the screen above me angled downward, tilting the screen so that it is facing up solves it for me, like I said, strange.
Sent from my NookColor using XDA Premium App
Click to expand...
Click to collapse
Did you do anything to resolve it, or just live with it?
I just live with it, simply changing the angle seems to solve it, that's a simple enough fix for me.
Sent from my NookColor using XDA Premium App
FYI for anyone that runs into this thread later:
There must have been some glitch in the rooting process that screwed up the keyboard. I ended up doing the whole process over again by restoring back to stock 1.1, updating to 1.2, and re-rooting. Everything works like a charm now.
Incidentally, the stock/update/root process is a lot easier the second time you do it.
Hi, I have the exact issue, anyone knows where I can download 1.1 rom or 1.01 rom? I tried all 1.2, 1.3, 1.4.1, they all have the same issue. Thanks.
Every time before install new ROM, I formatted system, data, and cache, but seems still not totally formatted, cause 1, the keyboard part still mess up, now even cm7 on emmc has the issue. 2, the wifi connection still saved because it auto connects to my network every time flashed. Any idea? Thanks.

CyanogenMod hiccups

I have been using CM11 for a while now and I am experiencing frequents hangs and hiccups. In particular the systems doesn't seem to be able to handle an installation, what I mean is that whenever I install or update an app the system hangs like if it can't handle a multitasking session, the systems freezes. Also, I ofent have my device frozen and I can't turn it on, the screen stays black for long periods, in the order of 5 minuts or more. I'd say this ROM is not functional. Is there anyone else who is experiencing the same problems? I am not sure whether the ROM is not working properly because of some setting I changed but well... I was thinking about going back to stock or to re-format and start over with a fresh CM11 because it might also be that I did something wrong. Any comment or suggestion, personal experiences? is CM11 working on your xperia sp's?
Cellulario said:
I have been using CM11 for a while now and I am experiencing frequents hangs and hiccups. In particular the systems doesn't seem to be able to handle an installation, what I mean is that whenever I install or update an app the system hangs like if it can't handle a multitasking session, the systems freezes. Also, I ofent have my device frozen and I can't turn it on, the screen stays black for long periods, in the order of 5 minuts or more. I'd say this ROM is not functional. Is there anyone else who is experiencing the same problems? I am not sure whether the ROM is not working properly because of some setting I changed but well... I was thinking about going back to stock or to re-format and start over with a fresh CM11 because it might also be that I did something wrong. Any comment or suggestion, personal experiences? is CM11 working on your xperia sp's?
Click to expand...
Click to collapse
It did start lagging after a few weeks and for me the recent button took forever (3 secs ! thats a lot since it never took that much long) to open recent menu. So I reinstalled it not knowing whether it was my fault or CM and to my surprise after a few weeks it did it again and I switched to PAC rom. Never looked back. IMO pac rom is the best experience of kitkat on sp.

Nook HD+ on CM11 keeps crashing

I am running cm-11-20141112-SNAPSHOT-M12-ovation.zip on my Nook HD+. It works flawlessly except for this one issue, which unfortunately renders it extremely unreliable: it suddenly switches off with a pop sound at random times. Doesn't shut down, just suddenly dies. Because of the pop sound that always accompanies the crash, I suspected it to be related to audio, but the audio works fine otherwise. I have most often noticed this crash while running YouTube, but it has happened even on the home screen on occasion.
Has anyone else experienced this specific issue? How can I debug this a little more? Is there a way to enable a trace log or anything that can help troubleshoot more? I'd like to know if it is worthwhile to move to any other CM version.
CM11 isn't very stable on Nook HD. The bugs were just never entirely worked out. You should probably switch to either CM 10.1 or 12.1. 12.1 is the only one still being actively developed and Amaces has it working very well.

Categories

Resources