There seems to be an issue running this game on any CM based roms on multiple devices. When I run the game in a Touchwiz based rom on my Note II, I have no issues and the game plays normally. On multiple CM based roms, I'm having an issue where the game appears normal until a battle is started. Battles have black screens. You can hear the game playing still, you just can't see anything. Has anyone found a fix for this issue? I searched around and realized it was a common problem on multiple (seemingly all Samsung) phones while running CM.
Any ideas? Nothing I've done so far has worked and I'd really like to both keep my rom and play my game! Yes, I want to have my cake and eat it too! I really don't want to go back to a Samsung based rom.
Ok. Here's something strange. When I enable the Navigation Bar, I can see battles again! Does anyone have any idea what could cause this or have any ways I can fix this without the Notification Bar on? It only happens on CM based roms.
Ask the cm devs
Wayne Tech S-III
Do you have a theme set? I've heard that a custom them will break the game.
It was happening on the regular theme as well. I just open the Navigation Bar to play the game. Works for me.
VassagoX said:
It was happening on the regular theme as well. I just open the Navigation Bar to play the game. Works for me.
Click to expand...
Click to collapse
I will try that, i'm on gs3 with cm10.1, nothing can fix the blank screen
how do you do that? can't find the option....
Related
I'd like to start off by saying these are just things I have noticed and am wondering if they are being worked on or if there is nothing to do about it. I'm not trying to complain but I cannot post in the Dev forum yet so I'm posting here trying to figure out the answers.
1. Is there any way to take advantage of more screen? there is a good 1/4 inch of space at the top and bottom of the screen that you cannot use. The only reason I can think of that there would be so much space is because of the remove button on the top when you drag widgets.
2. Google Talk does not work for me by any means. If I try and log in it says I'm offline and when I click on my user name it says that it had a problem and force closes. Anyone else experiencing this?
3. How hard would it be to add virtual looping to the home screens? that is by far my favorite feature of Launcher Pro along with transition animations.
4. When will the dock and icons preferences be fixed?
5. What is the issue with the camera? Is it just the 3D? or is it because the EVO is supporting 3D the drivers are weird to handle?
I'll probably have more questions so I'll update later. I have searched the Joelz ICS thread for these answers and didn't come up with anything. I hope someone could help me with at least most of these questions. I understand programming but I'm not an android developer so keep that in mind. Thanks in advanced
herousr said:
I'd like to start off by saying these are just things I have noticed and am wondering if they are being worked on or if there is nothing to do about it. I'm not trying to complain but I cannot post in the Dev forum yet so I'm posting here trying to figure out the answers.
1. Is there any way to take advantage of more screen? there is a good 1/4 inch of space at the top and bottom of the screen that you cannot use. The only reason I can think of that there would be so much space is because of the remove button on the top when you drag widgets.
2. Google Talk does not work for me by any means. If I try and log in it says I'm offline and when I click on my user name it says that it had a problem and force closes. Anyone else experiencing this?
3. How hard would it be to add virtual looping to the home screens? that is by far my favorite feature of Launcher Pro along with transition animations.
4. When will the dock and icons preferences be fixed?
5. What is the issue with the camera? Is it just the 3D? or is it because the EVO is supporting 3D the drivers are weird to handle?
I'll probably have more questions so I'll update later. I have searched the Joelz ICS thread for these answers and didn't come up with anything. I hope someone could help me with at least most of these questions. I understand programming but I'm not an android developer so keep that in mind. Thanks in advanced
Click to expand...
Click to collapse
1. I don't get what you're saying by that. In the launcher preferences you can disable the persistent Google search widget so that will open up a tiny bit of space but let's be honest... it doesn't make that much of a difference.
2. Google Talk doesn't work. I'm pretty sure Joel just added it in with further plans for it.
3. The launcher being used is CM's CM9 launcher, Trebuchet, and they have stated that it's in their plans to add in endless scrolling.
4. Again, this is up to CM for when they finish up the first release of the launcher since it's v0.1 alpha right now. Couple of releases off of being added in, and god knows how long til it's 100% functional. CM is generally quick.
5. It'll be just like the long haul that was getting camera to work on 2.3.x when that was the newest that we had. The camera has extremely odd drivers and it is much easier to fix/re-write for a single camera than two, of which 3D is it's purpose... I think we will have to wait on CM to fix up the camera drivers for ICS before we see any real progress in that department. I'd say camera is a long way off. :l
Hope that helps you to some degree!
empiire said:
1. I don't get what you're saying by that. In the launcher preferences you can disable the persistent Google search widget so that will open up a tiny bit of space but let's be honest... it doesn't make that much of a difference.
5. It'll be just like the long haul that was getting camera to work on 2.3.x when that was the newest that we had. The camera has extremely odd drivers and it is much easier to fix/re-write for a single camera than two, of which 3D is it's purpose... I think we will have to wait on CM to fix up the camera drivers for ICS before we see any real progress in that department. I'd say camera is a long way off. :l
Hope that helps you to some degree!
Click to expand...
Click to collapse
That did help a lot thanks. For the first question yeah you can disable the persistent search bar but it doesn't seem like you gain that space back. Its just empty space then. Can't even resize widgets to go all the way to the top. I would say I lose almost an inch of screen space which is significant to me at least. I like my clock widget to be at the very top but on my phone it looks like its in the middle.
for question 5. So your saying even non 3D will be a while for the ICS ROMs?
Thank you for your help I really appreciate it
You can try another launcher. Go launcher works pretty good with Joelz ics rom.
And yeah, you don't get any space back when removing the search bar. That's there for the buttonless phones.
fpineda101 said:
You can try another launcher. Go launcher works pretty good with Joelz ics rom.
And yeah, you don't get any space back when removing the search bar. That's there for the buttonless phones.
Click to expand...
Click to collapse
Yeah I feel like running a different launcher kind of takes away from ICS. I am hoping to keep it as my default launcher. but if no development is made I'll probably go to Launcher Pro
? .
Oooooohhhh you never learn, do you?????
Just try them both and then decide........
Sent from my amazing 10.1 galaxy tab
cm9
I tried both many times but at the end I chose cm9 with pershoots kernal. It had way better sound output for my car system but seems his touchscreen drivers make the screen unresponsive at times need to force reboot . It seemed aokp was more responsive on scrolling but the UI had a few quirks battery and wifi icons were interconnected widgets didn't show correctly, games seemed laggy at times. They are both great roms from great developers. Try cm9 first if u don't like it try aokp. I always use per shoots kernals seems he is very talented. Been using them since the view sonic gtab days..and they never failed me. Make sure to data,cache,dalvik cache,batterystat wipes before flashing any big from jump. Like hc to ics, aokp to cm9!!
ICS CM9 by pershoot: there are fairly regular nightlies, I feel this is the best ROM as of now, Temple run works- which shows that touch sensitivity is pretty good. I found this to be the smoothest of the lot. Very less stagger. I flashed 0515 recently, and am happy with it. You can find the links in the development section.
http://forum.xda-developers.com/showthread.php?t=1528529
http://droidbasement.com/galaxy/roms/cm9/p4/
AOKP: There are more customization options, but the screen keeps getting stuck. Also, there are times when I try to put an app on the home screen, and all that happens is the screen rotates, twice. I really liked the option to put 5 buttons in the combined task bar though. and you can also assign specific actions for long press.
http://forum.xda-developers.com/showthread.php?t=1459287
Sent from my GT-P7500 using XDA Premium HD app
UPDATE
I tried the CM10 preview #5 and theres no delay or "elastic scrolling" at all.
Seems to be something samsung added as a "feature" in the stock rom.
Heres a video of scrolling in CM10
--------------------------------------------------------------------------------------------------
Hey,
I already found this thread but no real answer or solution.
I noticed a lag between the physical touch points and the positions the apps are getting. Some people referred to that as "elastic scrolling" but it seems to be present everywhere.
Heres a little video that shows the touch position from the android developer options and from a multitouch test app.
As you can see the positions the app gets is indeed "elastic" and seems to be delayed just like scrolling.
Another one that shows the scroll delay (even in lists with just a few elements).
I find it quite annoying compared to the direct input on the HOX or even compared to my old phone running CM7 (a Motorola Defy).
Is there any way to get rid of that behaviour? Oh and since I did not try one yet: is the input/scrolling in custom roms delayed too?
The S3 should have enough computing power for direct scrolling ..
I see this elastic scrolling more of a feature.
Me too, this looks more like a feature to me. Can anyone try AOSP-based ROMs and see if the result is the same? Especially on CM10.
KeauHou said:
Hey,
I already found this thread but no real answer or solution.
I noticed a lag between the physical touch points and the positions the apps are getting. Some people referred to that as "elastic scrolling" but it seems to be present everywhere.
Heres a little video that shows the touch position from the android developer options and from a multitouch test app.
As you can see the positions the app gets is indeed "elastic" and seems to be delayed just like scrolling.
Another one that shows the scroll delay (even in lists with just a few elements).
I find it quite annoying compared to the direct input on the HOX or even compared to my old phone running CM7 (a Motorola Defy).
Is there any way to get rid of that behaviour? Oh and since I did not try one yet: is the input/scrolling in custom roms delayed too?
The S3 should have enough computing power for direct scrolling ..
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1690136&highlight=elastic
kulisap said:
http://forum.xda-developers.com/showthread.php?t=1690136&highlight=elastic
Click to expand...
Click to collapse
Did you even read my post?
KeauHou said:
I already found this thread but no real answer or solution.
Click to expand...
Click to collapse
Updated the OP with a video showing scrolling in CM10. Apparently theres no input lag or "elastic scrolling" compared to the stock roms.
Why the hell did samsung add this loose input?
this "elastic scrolling" thing annoys me like hell....
I just bought a quadcore CPU phone, and now my phone likes some WindowsMobile6.0 thing?
Come on Samsung, ever tried scrolling on an Iphone?
Please come up with a better solution...
crolling in CM10. Apparently theres no input lag or "elastic scrolling" compared to the stock roms.
Why the hell did samsung add this loose input?
Click to expand...
Click to collapse
You do realize CM10 is based on "Jelly Bean" and not "Icecream Sandwich" as the current Samsung ROM's are?
ICS has elastic scrolling...
Hey guys! I've recently started using Fourth Bar Jellybean (and by far the most impressive desensed ROM yet), however there are a few bugs I've noticed that desensed ROMs all tend to have and I was wondering if there would be any fixes for the following:
Google Play music turns the wallpaper on the lockscreen black and doesn't show any music controls
HTCLinkifyDispatcher.apk tends to screw things up. For instance, if I click a link to YouTube it will take me to the browser page instead of the YouTube app. If you delete or rename HTCLinkifyDispatcher this fixes the issue, however in chat clients such as imo, IM+, or Google Talk, clicking a link will crash the app.
Those are the most prominent bugs that I can think off right off the top of my head. Like I said, Fourth Bar Jellybean did a REALLY fantastic job of desensing the ROM, but a couple of HTC Sense bugs still remain.
Let me know what you guys think - is there a fix for any of this?
Thanks!
If Rom devs changed their base to a telus base the link issue would be fixed all round without the need to modify anything, the Google music part I'm not sure of since I don't use it.
sent from a smooth place where my fingers trace across the screen to see your face and make you scream!
I think the google music doing that has something to do with the theme. It's not playing nice I'm most likely a bug. I remember flashing a theme and some music controls weren't showing up but they were there since I knew where they were I clicked. Are yours still function?
Sent from my HTC_Amaze_4G using xda premium
fcpelayo said:
I think the google music doing that has something to do with the theme. It's not playing nice I'm most likely a bug. I remember flashing a theme and some music controls weren't showing up but they were there since I knew where they were I clicked. Are yours still function?
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
This thing though is that it's not really a theme, I think it's an issue with the lockscreen itself. Come to think of it, it seems like EclipzeRemix got his to work in his Project Butter ROM. Maybe the apk can be extracted from it and reflashed/replaced in Fourth Bar?
bo1g said:
This thing though is that it's not really a theme, I think it's an issue with the lockscreen itself. Come to think of it, it seems like EclipzeRemix got his to work in his Project Butter ROM. Maybe the apk can be extracted from it and reflashed/replaced in Fourth Bar?
Click to expand...
Click to collapse
It's worth a shot, don't ya think? Better to try and fail that to sit doing nothing until your rom dev fixes the issue, though I do think it may be a system issue, tried updating the app itself?
I was wondering because that is what I had been using up until today. Just rooted and installed CM11 1/19. I was playing around with their stock launcher and finding that there are somethings I didn't like, almost thinking of going back to my old one, but that's it - it's old. As I played, I found that CM's laucher doesn't seem to do all that I'd like it to, do I'll probably switch to nova or another one.
Also, I have the dark theme selected for the messaging app, but it still comes out light. any ideas as to why that might be? I"ve started to play with some styles that will change that, but it also changes other things that i don't like enough to keep it. Just have to keep looking and playing.
Later