I tried the new, for android, cinemagram app but when i record a video in the preview I get this.
Apart from the case it might be a bug of the app itself, I got similar kind of behaviour some time ago when i was taking photos and tried to open them in gallery or in various other apps that used any kind of images. I don't have a clue what it might causing this, has anyone else noticed anything like that? Right now I'm on latest 4.2.2 pacman rom but had this on other 4.2.2 roms too.
sespiros said:
I tried the new, for android, cinemagram app but when i record a video in the preview I get this.
Apart from the case it might be a bug of the app itself, I got similar kind of behaviour some time ago when i was taking photos and tried to open them in gallery or in various other apps that used any kind of images. I don't have a clue what it might causing this, has anyone else noticed anything like that? Right now I'm on latest 4.2.2 pacman rom but had this on other 4.2.2 roms too.
Click to expand...
Click to collapse
4.2.2 or 4.1.2?
4.2.2 as i said...does it matter?
Same here, I'm on AOKP MR1 build 6 + Dorimanx 9.13 I guess this has to do something with the app itself or the new video drivers
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Same Problem here...
I have the same problem, running on RevoltJB, Android 4.2.2, Dorimanx 9.12! Any solutions yet, or is it really a software problem?
Same problem here, with JellyBam 7.4.0. Seems like a render issue, but is very weird, because the render works flawlessly in the front camara. I did some research and it seems to happel to all the CM based roms.
Anyone found a solution?
It's been 2 months i haven't seen this behaviour on gallery or anywhere else. So I assume it's just a cinemagram bug. Can anyone confirm this behaviour outside this specific app or a different version that worked with this app?
The rest of the apps works flawlessly, even the camera/video recorder.
Having the same problem, no matter which version of the app, it's always the same.
Camera on the side of the screen works, the main one doesn't.
I tested with every version of the app, i always update it, tried uninstalling, clearing cache and data but no luck.
I'm on a galaxy s2 i9100 with cyanogenmod 10.1 nightlies (always up to date)
Inviato dal mio GT-I9100 con Tapatalk 2
Related
Is anyone else having an issue with google chrome crashing at launch on cyanogenmod 9?
The last few builds seem to ruin support for chrome mobile as the second you click on the chrome icon, you get the error message "Unfortunately, Chrome has stopped"
The last 2 versions seem to have this issue
Grab FnC Nov 11th. Its based on the most recent source and has a working camera, plus I don't have any issues with chrome.
Sent from my cm_tenderloin using xda premium
I assume you mean this one ?
http://forum.xda-developers.com/showthread.php?t=1944556
I will test it out and see how well it works with chrome
Also do you know which kernel to use with it, (CM9 overclock kernel or the aokp overclock kernel?, the overclock kernel is just too good to give up (it makes VLC player a lot happier and makes the stick it app work better when I want to do a little split scree web browsing and video watching)
Razor512 said:
Is anyone else having an issue with google chrome crashing at launch on cyanogenmod 9?
The last few builds seem to ruin support for chrome mobile as the second you click on the chrome icon, you get the error message "Unfortunately, Chrome has stopped"
The last 2 versions seem to have this issue
Click to expand...
Click to collapse
No issues with Chrome here, either - running 11/11 FnC.
Let us know if you still have issues after a flash. :good:
I think I figured out the issue, the newer updates of chrome crash if you have your device set to 120dpi
only thing is that the default 160dpi makes everything too big
eg here is the touchpad at 120dpi
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Razor512 said:
I think I figured out the issue, the newer updates of chrome crash if you have your device set to 120dpi
only thing is that the default 160dpi makes everything too big
Click to expand...
Click to collapse
Yea, just tested out changing the DPI, and it does break Chrome.
160 is pretty..... well, big, but I've learned to make do in the mean time.
I took this as an opportunity to upgrade to cm10.
Now I have 120dpi and Chrome works. Not sure why it does on cm10 but no longer on cm9 at 120dpi...
It includes the OC frequencies
Sent from my SAMSUNG-SGH-T989 using xda premium
I was having this problem too. I uninstalled current Chrome. I installed the one from link below and it is working with nightly 11/11 at 120 dpi. http://www.androiddrawer.com/6430/download-chrome-18-0-1025308-app-apk/#.UKWnYWG3M81
My new solution for this, since cm10 was random rebooting on me and flash didn't work right in the stock browser:
I installed ParanoidAndroid cm9 version. It lets you set per-app DPI settings.
So now I have 132 system-wide, Chrome at 160 which keeps it from crashing.
I tried to update Chrome to the latest version and it can't be open since that. CM9 nightly 10.28
Ever since I flashed Rootbox for the first time, I've been experiencing this problem on Aosp/Aokp roms.
This usually happens when I'm using the phone in vertical position for a while. Then all of a sudden, after, for example trying to watch a video on YT, I realize I can't rotate the screen.
So far I've used CM9(which I'm using right now), Rootbox (both Ics and JB) and RR(JB). I've used the RR with dorimanx kernel and the problem persisted. The only way to fix this is to restart the phone. If I'm lucky, it'll start working again after some time without restarting. If I use a Stock or Miui based rom, everything works fine.
Does anyone have any idea what f. is going on? This is becoming very annoying.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-I9100
Anyone?
boki9999 said:
Ever since I flashed Rootbox for the first time, I've been experiencing this problem on Aosp/Aokp roms.
This usually happens when I'm using the phone in vertical position for a while. Then all of a sudden, after, for example trying to watch a video on YT, I realize I can't rotate the screen.
So far I've used CM9(which I'm using right now), Rootbox (both Ics and JB) and RR(JB). I've used the RR with dorimanx kernel and the problem persisted. The only way to fix this is to restart the phone. If I'm lucky, it'll start working again after some time without restarting. If I use a Stock or Miui based rom, everything works fine.
Does anyone have any idea what f. is going on? This is becoming very annoying.
Sent from my GT-I9100
Click to expand...
Click to collapse
I too had the same issues a few weeks back, while using jellyBAM. I didn't bother though, coz I didn't use landscape much.
I did find out that after turning on and off autorotate a few times, it becomes normal again. And oh yeah, sometimes I have to reboot!
I hope someone else can come up with an explanation!
"To err is human, to forgive is divine"
Sent from my SGS II
I'm trying to use the new video feature on instagram. I'm able to view others videos but when I try to record a video it doesn't save my progress. It starts over and shows this message.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To verify that its not a rom issue I wiped and reflashed Black Jelly Beta...I also wiped and flashed Alpha and Padawan JB 2. I get the same results with all three.
I'm not sure if its a app issue or a problem with my phone. If anyone has any advice, I'd really apreciate it.
Thanx in advance
A BIG @ZZ JAR OF BLACK JELLY
Someone over in the Q&A section had the same complaint. It sounds like the app isn't ready for prime time yet. Did any version of the app work for you?
rangercaptain said:
Someone over in the Q&A section had the same complaint. It sounds like the app isn't ready for prime time yet. Did any version of the app work for you?
Click to expand...
Click to collapse
No I have not been able to record video since they added the feature. I sent an email to instagram support but haven't heard anything. Surprise...surprise...
A BIG @ZZ JAR OF BLACK JELLY
+1 to the list, getting same issue. If I run instagram on a non touchwiz rom and try to use the camera, the phone freezes. Finally able to get it up and running on a TouchWiz rom with camera working, but video issue is the same for me (won't let post, seems to record but then starts over asking to record up to a certain point)
I've had exact issue and it still hasn't been addressed almost a week later....
same here
Sucks that this issue still hasn't been fixed by instagram. Read reviews from play store and every single Note 1 user cannot use video feature. I bet if all these people would only rate only 1 star it would be addressed and fixed.
TE TOQUE said:
Sucks that this issue still hasn't been fixed by instagram. Read reviews from play store and every single Note 1 user cannot use video feature. I bet if all these people would only rate only 1 star it would be addressed and fixed.
Click to expand...
Click to collapse
Agreed!
A BIG @ZZ JAR OF BLACK JELLY
Will Chrome work on any ROM for the X2?
The notes for the Cyanogenmod 10 build say:
"Some ICS/JB Apps Will Crash: This is noticeable on Chrome for example. This is because our drivers don't have External OES Textures. Basically that means when the apps want to draw using them (such as with Chrome's tab preview) the app will crash. This is the same problem on CM9/ICS. There is nothing we can do."
but I am asking whether that means that Chrome is essentially unusable or if there is some bypass such as disabling tab preview (I do not know what tab preview is, or how central it is to Chrome).
Thanks!
no.our kernel is too old so it dosent have certain things a ics/jb kernel regquires to run chrome (which is why chrome only runs on 4.0+) therefore there is essentially no way to run chrome (to my knowledge at least) + no there is no way to disable the indvidual part of chrome for it to work.we just dont have the necissary resources to do it.
Last time I played with my x2 chrome did work fairly well on cm9. That's not to say there wasn't the occasional issue though
Sent from my SCH-I535 using XDA Premium 4 mobile app
Lrs121 said:
Last time I played with my x2 chrome did work fairly well on cm9. That's not to say there wasn't the occasional issue though
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
huh,really? mine never worked when i had cm9 running (or 10 even either,both latest versions) would always force close when i would try to open,everything else was fine tho
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry to wake up an old thread, but I am posting this from my Droid X2 on Cyangenmod 10, Android 4.1.2, in hopes it will help somebody. I Tried many versions of Chrome with no luck. Was getting a force close upon open.
Then I installed Chrome Dev version 48. Opens and runs perfect. But seems to have tab preview disabled by default, hence why it runs. Very fast and stable.
These are just a few minor bugs and glitches I've noticed using the newest version of the developer preview
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6P using XDA-Developers mobile app
Other than these issues, it does work well
Sent from my Nexus 6P using XDA-Developers mobile app
Update: I shut the phone off and back on and all bugs fixed ?
Sent from my Nexus 6P using XDA-Developers mobile app
Actually the graphical issues are probably not due to the preview. It may the apps that need to update their APIs, especially when the graphics rendering API is now Vulkan.
Yeah, in my daily use I haven't run into a single hiccup with Preview 2. I think it's safe to say that it's getting pretty dang close to perfect. Any issues people are experiencing are likely due to the apps they use, rather than the operating system.
The only "issue" I have is Facebook periodically not responding/crashing. However, that's happened on every iteration of Android I've used since like 2012 because Facebook is the Worst.App.Ever.
The fact that Facebook is the only app still not having a colored status bar says a lot about the devs behind it. Don't expect any changes anytime soon.
Enviado de meu Nexus 6P usando Tapatalk
Has anyone noticed that hangouts does NOT show up as heads up? Snapchat and I think ESPN does. But hangouts .... Doesn't.
My phone is randomly rebooting when wifi connections are lost. Anybody seeing this (or know a fix)?
Anybody else having BT issues that are very similar to that of current CM13 builds? On Dev Preview 1 BT worked perfectly for me, but on Preview 2 I'm getting a little bit of stuttering every few seconds as if there's a blip in the music. I clean flashed and left everything stock. I do not have this issue on Stock M or AOSP 6.0.1 builds.
uodii said:
Anybody else having BT issues that are very similar to that of current CM13 builds? On Dev Preview 1 BT worked perfectly for me, but on Preview 2 I'm getting a little bit of stuttering every few seconds as if there's a blip in the music. I clean flashed and left everything stock. I do not have this issue on Stock M or AOSP 6.0.1 builds.
Click to expand...
Click to collapse
The latest preview is having issues with Android Auto and Fitbands BT connectivity.
I'm having am issue with in call sound.... It's is almost 50 percent lower than on marshmallow... Has anyone noticed this....