Hi!
Newbie here,
I've got a problem with cany crush saga on a CM10.1, latest kernel from Kowalski and the full nonneongaps from Tonyp (excellent rom by the way).
When i start the game, no problem. But when i hit the play button the screen starts flashing, the music starts and the touchscreen responds. The phone keeps on working as supposed to. I can shut the game with the home button.
It's not a big problem for me, but the kids are playing this very often on my phone.
Is there a fix for this?
I tried also the 10.1 Rom from avatar, same problem. Went back to ICS with NVFlash and candy crush saga is working fine.
Thanks in advance
if the same behaviour shows with different roms/kernels, then obviously the game have major problem with p990's hardware.
when the P990 is running on ics (stock or nv flash recovery there's no problem with the app. For me that rules out hardware.....
Same thing here, exact same kernel. The top line and bottom line of the screen flicker black on and off, the game responds but the graphics don't update.
Lent the phone to a friend so I'm not sure when I'll be able to try this, but I hope to update when I do.
sastraxi said:
Same thing here, exact same kernel. The top line and bottom line of the screen flicker black on and off, the game responds but the graphics don't update.
Lent the phone to a friend so I'm not sure when I'll be able to try this, but I hope to update when I do.
Click to expand...
Click to collapse
this happened to me but in my sony tablet. i was using it normally but suddenly when i start the game around 1 hour after not playing it its flickering. any help?
I am having the same problem :crying:
efmoraes said:
I am having the same problem :crying:
Click to expand...
Click to collapse
The problem is kernel related. Try a different kernel, and with reduced ram hack value if available.
I had been sent a private message by someone 3 weeks ago regarding this, asking how to fix it. I suggested him a different kernel, even tried it myself and it worked
So its either got to do with the high ram hack value or some other tweak in the kernel that causes the issue in this game.
rugglez said:
The problem is kernel related. Try a different kernel, and with reduced ram hack value if available.
I had been sent a private message by someone 3 weeks ago regarding this, asking how to fix it. I suggested him a different kernel, even tried it myself and it worked
So its either got to do with the high ram hack value or some other tweak in the kernel that causes the issue in this game.
Click to expand...
Click to collapse
yeah! im that bothersome person who ask many developer about that... hehe
just use AIOtool, and duat boot.. u can use avator rom or temasek(without flashing the kk), and a daily driver w/ kk...
don't worry i think spica1234 will help us, if he gets some free time! ^__^
thanks for all the developers here, temasek. pengus77, spica1234, tonyp, sreeprajay, bippi79..
hoping benee, jordanrulz, civato, stefan see this! & the members of Hackfest )
goood day, i have same problem with candy crush please help me how to fix candy crush
heres my ROM
cm-10-1-NIGHTLY-su660-fixed.zip
kowalski-kernel-100p5-oldbl_CM10.1.zip
please please help me how candy crush work
There has been written a lot about this app in the development section. Try to search in kernel or ROM threads (but don't reply with your issue as it doesn't belong in this sections and people got sick of it). As I remember, changing to latest Kowalski stable without ram hack (KK M1 norh) could help...
Sent from my LG-P990 using xda app-developers app
thank you for the reply
but im using su660 phone
Related
I'm using Overcome GB RC1 and when I run the game there is no sound. Is this unique to me? I am also using the 3.0.3 kernel from this threadhttp://forum.xda-developers.com/showthread.php?t=943669 but it seems to happens regardless of kernel used. Any hints??
Is it a legit copy
It is, I support professional devs as well as hobbyists like the superstars on XDA and elsewhere.
If someone is viewing this thread and has the game installed and it works properly please confirm and let me know what your tab's configuration is, thx
Useless_Alias said:
It is, I support professional devs as well as hobbyists like the superstars on XDA and elsewhere.
If someone is viewing this thread and has the game installed and it works properly please confirm and let me know what your tab's configuration is, thx
Click to expand...
Click to collapse
Works perfect for me, config in my sig.
Works for me now also, restocked and went to Overcome Gold no kernel changes....must've been something I mucked with thanks for the replies
I have the same problem with Overcome Hermes. I will try a restock and see if it helps me as well. With "no kernel changes" hope you mean using the Overcome kernel.
Edit: Alright. For anyone having the same problem: I found out that if your Tab is in Silent-mode, gameplay sounds will not play, though movies sounds (e.g. from intros) will. Even cranking up the media volume to the maximum will not help. Put the ringer volume to at least 1, and the problems are over.
Hi, i recently switched to Cyanogen, and love the OS so much, but it seems the sensors not working proper..
My son loves playing that temple run game, and before i installed cyanogen it worked great, but now when he plays the person running is on the right side of screen even when on flat table, idk how to sort it, and ive tried reading all over the net, i hope someone can assist.. tyvm..
SO when playing Temple Run with phone upright with the person running is stuck to the right, and same in all sensor apps..
I have the latest stable mod, and the LG Optimus 2x from FIDO..
I have also tried the figure eight, and tried using compass apps to calibrate, but still no go.. Plz help someone..
thx so much.. I appreciate all the effort to assist me..
Try to flash latest temaseks kang. I had this problem on some roms with lg p500, on orange boston too, hd2 too.
Sent from my Optimus 2X using XDA
and fyi, the sensor works fine on Owain's domination. I ran Temple Run as a test too.
Thx so much for the replies...
and yes xtrustkillx, i have issues on those games as well..
I am going to try flashing that different rom, and hopefully that sorts things..
If anyone else has any idea's please do feel free to assist I am very grateful for all the assistance..
and aragorn7, tyvm for your reply.. I was reading around and i see that is another very good looking rom, so hopefully one of those two new roms the replies have shown me will assist me with this problem.. thx again..
I have this problem with any kind of rom or kernel , I`m on stock based rom now , Django Manouche but any kernel I try or rom, I have the same problem , I see this in gallery as well or any kind of games or apps that use gyro sensor. Is there any way to calibrate it from hidden menu or something else? :|
yes i hear that forforce
I have now tried a few alternate cm7 roms, and still same problem, it's a very weird problem as in Temple Run the runner is just off to the right, and yet still runs stait if u leave in on flat surface.. so idk whats goin on.. it's drivin my son nuts though.. lol
any help anyone?? i've tried flashing other roms, but still having same problem? thx for your help..
I would suggest nvflash v10b rom, root it and flash latest cm7 kang and etana kernel.
Sent from my Optimus 2X using XDA
thx for the reply, i tried it now finally, and yet still same problem, i dont understand what happened, i can't even flash my stock backup as it just givs me a bootloop..
its very weird though, cause its liek the sensor is just off to the right a bit, as when playing temple run or similar, the runner will still run in a strait line, he is just off to the right of the screen instead of in the center, and i cant figure out what to do to sort it..
I hope one of you very smart individuals will figure out a fix.. thx for all the help..
My guess is that trere is different filesystem on stock. I have tried installing a bunch of apps and find out that advanced bubble level allows to calibrate but dunt know if on system level too. You must try on your own.
Sent from my Optimus 2X using XDA
xtrustkillx said:
My guess is that trere is different filesystem on stock. I have tried installing a bunch of apps and find out that advanced bubble level allows to calibrate but dunt know if on system level too. You must try on your own.
Sent from my Optimus 2X using XDA
Click to expand...
Click to collapse
thx for reply, and yea i figured out about the file system, gunna try that ext3 to ext4 or visa versa, and try estoring the stok backup.. but if that dont work, im completely lost, idk what could have caused this problem, everything was fine before the first flash of CM7.. so idk..
thx again for all the help..
I'm baffled and trying my very best to work out why I'm getting the BSOD on this phone. There appears to be no logic or pattern to when it occurs, so it's very difficult to diagnose what's causing it. I've now had two of these phones where it has occurred. The first one I took back and got a replacement under warranty. The second one worked like a charm on stock GB with no flashing of basebands, but since messing about and installing both CM10 and the latest ICS ROMS it's started happening again.
It seems to occur most when I go to charge the phone. It'll just die a death and I'll have to take the battery out before it even thinks about starting up again. Perhaps the most annoying thing of all is that it resets all time and dates and will then fail to use the network provided settings.
Has anyone else had this problem and found a solution that works long term? What about the cause? The strange thing about it is that it can go for a week without doing it...then, it'll happen twice in one day. And it's getting frequent to the point of being very irritating. I'm wondering If a different baseband would help. It currently detects it as unknown, but if memory serves I flashed the old 528 original stock baseband for use when I first installed CM10.
I have experienced it in every rom (I have experienced it in: cm10, all GB roms Ive tried, all ICS roms etc..) but not in cm 7 ... so I usually go back to that rom most of the time..
What baseband are you using? Whether or not it has anything to do with it I don't know. Desperately trying to find a fix. I'm thinking it can't be a rom issue. I'm just hoping it's not the phones hardware.
Sent from my LG-P990 using xda app-developers app
The worst thing is don't know how we carry cm10 bugs after flashing over different roms even with full wipe..I lost my amazing battery life after cm10 flash got new battery calibrated food full wow did smart flash still battery life drains like in 10% in hour even without any use....gross
This bug has been reported in the CM10 Bug Thread, you should take a look at it.
Basically the workaround is to turn on your screen before plugging the phone to a charger. There are users saying that they also have a lot of BSOD's when plugging the phone in CM10.
Don;t you think that questions has its own thread? Hope your eyes are still in good condition.
To prevent BSOD you can try hihger min cpu clock frequency.
Rayman96 said:
Don;t you think that questions has its own thread? Hope your eyes are still in good condition.
To prevent BSOD you can try hihger min cpu clock frequency.
Click to expand...
Click to collapse
You seem to be in a foul mood lately, passing such comments on all threads.
And for your info, increasing min cpu clock frequency has no effect on cm10 bsod. It may work in some roms, but not on this one.
Rayman96 said:
Don;t you think that questions has its own thread? Hope your eyes are still in good condition.
To prevent BSOD you can try hihger min cpu clock frequency.
Click to expand...
Click to collapse
Dude if you read my post im saying it occurs whether cm 10 or not. Changing clock frequency did nothing for me so thanks for pointing out the obvious. Like i say, it's a problem I've always had with this phone whether I was on stock gb or not and im getting sick of it. I just wondered if anyone knew the reason and a sure, concrete solution.
Sent from my LG-P990 using xda app-developers app
I am on CM10, and I never get random BSODs. I am on the 11/20 nightly.
For me, the one and only time a BSOD occurs is if my screen is off, and I plug in the charger (USB or wall), and the charger doesn't cause the screen to turn on automatically. If the screen turns on the moment the charger is plugged in, I won't get a BSOD.
My "solution" at the moment is to always turn on the screen before plugging in my charger. No more BSODs.
I used to get random BSODs even off the charger on earlier nightlies, but after 11/10 it was all right.
Mine is just the opposite....whenever i dont have it charging the bsod will appear sooner or later if its plugged in everything is ok...i tried changing min freq and clean installed all cm 10 nightlies so far but nothing has helped.
Sent from my LG-P990 using xda premium
haunterx said:
Mine is just the opposite....whenever i dont have it charging the bsod will appear sooner or later if its plugged in everything is ok...i tried changing min freq and clean installed all cm 10 nightlies so far but nothing has helped.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
Same here with CM10, and some days worse than others. Although weirdly it was exactly the opposite with stock GB or CM7 - it would do it mostly while charging.
See this is my point.. Just how many folk are having this problem with the device? I might contact LG support to see if it's a known issue. I have it both whilst charging and not whilst charging. A Google of the topic does support a fair number of everyday stock users as having this issue. I just don't think it's a rom specific issue. The occurance is so spasmodic I think it's simply coincidental.
Sent from my LG-P990 using xda app-developers app
withoutwings said:
Same here with CM10, and some days worse than others. Although weirdly it was exactly the opposite with stock GB or CM7 - it would do it mostly while charging.
Click to expand...
Click to collapse
Same here. With CM7, very, very rarely would the phone just "die" with a black screen when charging. If I had it plugged in via USB to my computer and then immediately plugged into the wall charger, it would almost always BSOD. The only way to recover was to unplug it, pull out and re-insert the battery. This happened so rarely (especially if I always rebooted the phone after using USB) that it wasn't a problem for me.
With CM10, it will instead BSOD if it's just left idle with nothing connected. This happens 0 to 10 times a day with no logical pattern. Some days, I almost think the problem is gone, others the phone is almost unusable because it keeps dying. It has never had a BSOD while charging. This has happend with every nightly build of CM10. I've also had the problem where the caller/person I call just hears "dialup modem" type noise.
Monday evening I flashed SU660 V30c baseband. Still no BSOD as of today (noon on Wednesday). However it has gone this long without BSOD before, so fingers crossed. I have a "Made in Korea" P990 and it previously had Baseband 20I-EUR. Also going to do a few test calls to see if the noise problem is still there.
That's very useful to know. As you say the problem is so bizarre and so random that's almost impossible to know until weeks later if it's been solved for good. I just hope that final ics and baseband release will put the issue to bed once and for all. Can anyone confirm whether or not they have had this issue with the latest leaked ics baseband?
Sent from my LG-P990 using xda app-developers app
48 hours without a BSOD after flashing BB 30C however now calls have gone completely quiet. Neither party can hear a thing.
Back to the drawing board :silly:
Is anyone else's phove really hot when BSODed or is it just mine? When I was on Gueste 3.6 everything was ok until it BSODed, that's when cm10 came out, tried it, changed a few basebands and didn't have it for almost a month, suddenly a few days ago while I already returned to default bootldr and partition sizes on gueste 3.8ext3 with v28g bb I think (20121110)
Sent from my Optimus 2X using xda premium
UPDATE ON BSOD: I used Titanium Backup to freeze the stock browser (using chrome now lol) and for the past 3 days I haven't had a BSOD. Can people try to do the same and report what they find?
neovdr said:
UPDATE ON BSOD: I used Titanium Backup to freeze the stock browser (using chrome now lol) and for the past 3 days I haven't had a BSOD. Can people try to do the same and report what they find?
Click to expand...
Click to collapse
Truth is that I always use root uninstaller and remove the stock browser and this is the first time I haven't. Hmm... let's see...
Sent from my Optimus 2X using xda premium
I think BSODs occur when the relationship between rom, kernel and baseband is not so good.
Yes it appears to be that way. Unfortunately we don't have a BB for the P990 that works properly with ICS/JB ROM (call audio bugs etc.), which is why development of CM10 for P990 was abandoned. I'm now back on CM 7.2 and everything works as it should.
Q.1
As I said I had problem with SU Binary on my Galaxy note GTN7000.Is the SU-Busybox the same for ICS/JB so I can just update my busybox?
Q.2
I try to flash the Ultimate_N7000_XXLSC_JellyBean with PhilZ-cwm6-XXLS7-XJB-3.1-signed and when I full wipe,format what it needs I try to install the ROM and I have this error message:E:Installition Aborted.emb/Ultimate_blah_blah_blah cantbe installed.Its the kernel? Where do I wrong?
Q.3
I see some users after answering or asking something have something like "Logo".I see they have ----------------- to separately there post after posting and then they add their logos
(I know this question is not about JB but idk where to post it)
E.G
blah blah blah blah blah blah
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Click [:good:thanks]
Click to expand...
Click to collapse
1. Should work fine with both ICS and JB, changes in 4.1 were not that great for the apps not to work.
2. Most likely a bad download, try downloading again.
3. I think you're talking about "signature" feature, it's in your user panel.
Akiainavas said:
1. Should work fine with both ICS and JB, changes in 4.1 were not that great for the apps not to work.
2. Most likely a bad download, try downloading again.
3. I think you're talking about "signature" feature, it's in your user panel.
Click to expand...
Click to collapse
1.Thanks for answering am gonna try it
2.I think its not the download cuase I use rupidshare and d-host and I got the same problem.and also some users had this problem
3.thanks a find it
Yes update. It will ask to update the binary no. Press yes n there you go. What I did
from the man hiding in your attic....
Yeah as if 2
This seems to be a common issue. Install a different kernel and do the installation
nokiamodeln91 said:
Yeah as if 2
This seems to be a common issue. Install a different kernel and do the installation
Click to expand...
Click to collapse
I have the PhilZ kernel ls2 safe?
it is safe but if you are getting error on installation, try changing the kernel. try the latest hydracorereborn kernel
Nevermind Guys
nokiamodeln91 said:
it is safe but if you are getting error on installation, try changing the kernel. try the latest hydracorereborn kernel
Click to expand...
Click to collapse
I dont find Hydracore Reborn,but thanks.I use PhilZ Kernel XXLSC-XJB-3.1 To flash the Ultimate_JB_LSC And i really love the rom.Thats mean there is no reason to answer for anything,cause the rom includes binary with no bugs like Eyebee 4.1.1
Thanks to
nokiamodeln91 and ayong chia and Akiainavas
Click to expand...
Click to collapse
Good. Merry Christmas
Sent from my GT-N7000 using xda premium
Hey, just a heads up on my experience with JB/UltimateN7000. My advice is don't do it..
I had the latest ICS stock German version with root, and mostly everything was acceptable. Default Samsung home screen was very smooth at first, but as I install apps (about 20 apps, no games) and use it more, it gets slow after about a week. Then I install Nova Launcher, and it's much better (smoother and responsive) than the Samsung launcher, but it feels slow time by time as if the device is already showing it's age. (I bought this for $600 in April 2012, and it already has 3 tiny cracks on the thin rim that wraps the screen, never been dropped, no scratches anywhere.)
I keep hearing about how JellyBean is wonderful and all, the awesome project Butter, and that it's going to be the true cure to make everything fast and smooth, competitive enough against Windows Phone and iPhone.
This is the same promise that ICS had when we were on Gingerbread. Lack of hardware acceleration on the graphics was the explanation back then. Even after ICS, it's still not as smooth as the competitors even with superior hardware.
I installed this XXLSC based Ultimate N7000 (had stock leaked JelleyBean for couple days before), I'm sorry to say this, but the performance really sucks. I understand that it could be due to this being a leaked ROM, but I'm kind of worried about this device's future. I wonder how are you guys are using your devices with leaked JellyBean.
What's with the lock screen, the overwhelming ink drop effect? The hardware is clearly lacking, but why are they (Samsung) trying to shove stuff in?
What's with the the pull down (notification) menus' small buttons on the top - springing back every single time wasting CPU cycles?
The dialer still takes 2-3 seconds to pull up. Opening contacts, or switching to recent call history tab makes me hesitate because it takes so damn long. This was a problem also in ICS.
Did you guys try the Camera app? Try taking a picture, and then try to review the picture you just taken. How long does it take? Mine takes about 30 seconds, and it lags horribly while doing all that. Now try that on a iPhone, it takes less than 10 seconds, and no stutter at all. (No, I hate iPhone's closed eco system so no thanks.)
It's like playing a FPS shooter game with high quality graphics/every effect enabled but only at 15 FPS, when it could play 30 FPS with lower graphics quality/effects. (I would much prefer at least 60 FPS though.)
I'm going back to my ICS stock backup for now, and maybe later on when Samsung releases JellyBean, and some developer makes a lean version, or do it myself, and I'll try it again.
It's just sad to see that a relatively powerful dual core phone is too slow to function satisfactory these days.
Lastly, thanks to the developers, and sorry for the vent. Please don't get me wrong, I'm not trying to mock you or anything. I really do appreciate you and every other developers out there.
Click to expand...
Click to collapse
hp79 said:
Hey, just a heads up on my experience with JB/UltimateN7000. My advice is don't do it..
Click to expand...
Click to collapse
That's why i ALWAYS go AOSP. Never had such problems, even in beta/experimental releases of CM. Anyway, hope OP has resolved his problems already.
Akiainavas said:
That's why i ALWAYS go AOSP. Never had such problems, even in beta/experimental releases of CM. Anyway, hope OP has resolved his problems already.
Click to expand...
Click to collapse
The only thing am waiting for is project butter. Until then I too are sticking with ICS.
hp79 said:
Hey, just a heads up on my experience with JB/UltimateN7000. My advice is don't do it..
Click to expand...
Click to collapse
This is your opinion..
I don't agree with this
Akiainavas said:
That's why i ALWAYS go AOSP. Never had such problems, even in beta/experimental releases of CM. Anyway, hope OP has resolved his problems already.
Click to expand...
Click to collapse
Did u even try XXLSC?
No issues like he say.Everyting is working fine
I want to thank the developers for this amazing rom but i want to say that some apps are crashing several times before they work properly and there is some lags that i hope u can fix.
If someone move the post to the main thread i'll be thankfull cz i cant post there:good::good:
karaki93 said:
I want to thank the developers for this amazing rom but i want to say that some apps are crashing several times before they work properly and there is some lags that i hope u can fix.
If someone move the post to the main thread i'll be thankfull cz i cant post there:good::good:
Click to expand...
Click to collapse
i believe it happens due to low memory access, aka ram available. if i were you id just switch to cm11 its best option for now
det0xx said:
i believe it happens due to low memory access, aka ram available. if i were you id just switch to cm11 its best option for now
Click to expand...
Click to collapse
But the cm11 has many unworking stuff and isnt stable till now am i right? Please give me a report about the cm11 to make the best choice.Thanks in advance.
karaki93 said:
But the cm11 has many unworking stuff and isnt stable till now am i right? Please give me a report about the cm11 to make the best choice.Thanks in advance.
Click to expand...
Click to collapse
well whats not working or something that u my use thats not working? for me DCM and CM11 are the only functional roms for MY experience. Eveyrthing works fine. I am running latest CM11 from @cars1189 with his christopher k kernal with no issues
SlimKat Volume Levels
det0xx said:
well whats not working or something that u my use thats not working? for me DCM and CM11 are the only functional roms for MY experience. Eveyrthing works fine. I am running latest CM11 from @cars1189 with his christopher k kernal with no issues
Click to expand...
Click to collapse
I'm kind of a "ROM-a-holic". I like to try new ROMs all the time. I really like SlimKat (by "jfbs"), but I've noticed that the volumes seem to be very low...even when I have them turned all the way up I have a hard time hearing the caller. Am I just imagining this or have others noticed this? I've been using it for several weeks and really like it, but will probably go back to CM11 for awhile (until SlimKat gets another update) and see if I notice differences in the volumes. If anyone else notices this issue maybe they could pass it along to jfbs. I love all the great work everyone is doing with the ROMs for this relic of a phone!!
det0xx said:
well whats not working or something that u my use thats not working? for me DCM and CM11 are the only functional roms for MY experience. Eveyrthing works fine. I am running latest CM11 from @cars1189 with his christopher k kernal with no issues
Click to expand...
Click to collapse
so these rom now are full functional and stable ? U dont got apps crash and reboots?
eyespy63 said:
I'm kind of a "ROM-a-holic". I like to try new ROMs all the time. I really like SlimKat (by "jfbs"), but I've noticed that the volumes seem to be very low...even when I have them turned all the way up I have a hard time hearing the caller. Am I just imagining this or have others noticed this? I've been using it for several weeks and really like it, but will probably go back to CM11 for awhile (until SlimKat gets another update) and see if I notice differences in the volumes. If anyone else notices this issue maybe they could pass it along to jfbs. I love all the great work everyone is doing with the ROMs for this relic of a phone!!
Click to expand...
Click to collapse
For me slimkat has a better sound than my last rom RemICS-JB and it seems like stock for me but i agree volume need more boost
karaki93 said:
For me slimkat has a better sound than my last rom RemICS-JB and it seems like stock for me but i agree volume need more boost
Click to expand...
Click to collapse
I don't have slimkat, but I used slimbean for a long time. I had a similar volume issue there. What worked with slimbean was actually to click volume _down_ one click and then turn it up. Maybe that workaround will fix your problem. Good luck.
Sent from my SGH-T399 using xda premium
Thanks man I will try
Another issue
When im running an app and the screen is off it might not turn on again just the lights and if someone called me the phone rings after the call is dropped and in natural case he take about 5 sec to show that someone is calling
karaki93 said:
Another issue
When im running an app and the screen is off it might not turn on again just the lights and if someone called me the phone rings after the call is dropped and in natural case he take about 5 sec to show that someone is calling
Click to expand...
Click to collapse
those are wake locks i face every so often on each roms. more on slim for a reason idk