Hey guys, I recently installed [7.18.13][4.1.2][v1.0] ShenDu OS,
and everything works fine aside from getting the message "video recording failed" on snapchat.
But the real issue that I care about is the phone process immediately closes after launching.
So I can't or even receive a call at the moment. Anyone else having this problem?
I've reinstalled a couple of times now. I really like the look of this rom, and
it runs smoothly. It's just, you know, I'd like to call people sometimes.
Thanks
That's a bug with ShenduOS rom port.
I know that ROM is amazing but 2 others have also reported phone fc
It might be because the kernel is missing a few files in the ramdisk since i remember coderzs saying that the .61 cannot be used with cyanogenmod .
Sent from my myTouch 4G using xda app-developers app
Related
I don't think this has been posted yet, but I am seeing a weird bug with the camera that is different than all the other camera/camcorder bugs I've seen, most of which have fixes.
If I am in landscape mode of the home screen on Launcherpro or Go Launcher and open camera app, everything is fine. If I am in portrait mode of the home screen and open camera app, more often than not, I get a camera failed message.
I have tried this with both Launcherpro and Go Launcher. I have reinstalled camera. Wiped cache, wiped data, formatted sf card. Happens with both stock camera and the camera in the EB13 GB theme.
Anyone else experiencing this?
just tested this and my phone doesn't show this bug.
I'm on stock EB13 with camera bug fix kernel over it.
Im actually getting the same problem and im using go launcher idk about LP. Im running the midnight 4.1 eb13 rom.
sometimes the camera will start and be completely black and just sit there and I restart and then get "camera failed" it takes a few restarts to get it going which is annoying because most photo ops are come and go :/
Anyways nice to know im not the only one with the problem. Any help would be much appreciated
cconwing said:
Im actually getting the same problem and im using go launcher idk about LP. Im running the midnight 4.1 eb13 rom.
sometimes the camera will start and be completely black and just sit there and I restart and then get "camera failed" it takes a few restarts to get it going which is annoying because most photo ops are come and go :/
Anyways nice to know im not the only one with the problem. Any help would be much appreciated
Click to expand...
Click to collapse
Yes, that is exactly my issue. Workaround I figured out is to be in landscape mode before launching the app, but this is not really a solution. I found this bug on midnight 4.0 and syndicate frozen rom. Surprised more people haven't seen it.
Sent from my SPH-D700 using XDA App
Camera works fine for me.
Sent From My Evo Killer!
Camera works fine for me
EB13 Bonsai ROM with Bonsai 3.0.0 Kernel OC'ed to 1.2GHz
No problem with the camera for me either
Sent from my SPH-D700 using XDA App
Also no problems with the camera here in this regard. Using a stock RFS kernel with no lag fix.
I have no problems either - I have a stock EB13 that has been rooted via oneclickroot cwm 2.5.5 - no roms or kernels except stock, the only that I have done is install the camera/video lag and the slow rotation fix.
Camera works fine for me. Running the Syndicate Frozen rom.
Greetings. I have a Motorola Xoom and when I run Netflix, the first time it looks fine. After that, When I run it again, the Netflix menu looks huge and I cannot really navigate around it. The only way to fix the problem is to either clear the Netflix cache and data every time before I use it (requiring me to log back in each time), or installing version 1.3 (which then annoyingly prompts me to upgrade every time I launch it).
Does anyone else have this problem? Is there a fix?
Nobody else has this problem? Really?
I run Netflix on Xoom quite often but I don't have the problems you describe. My issues are usually with the app locking up and needing to force close it and restart. It was definitely running much better in the older versions.
I have the exact same problem, but I can't solve it even if I clear the cache. It's somehow showing the "stretched" phone UI instead the tablet UI. It's just unusable now.
Same problem here.....it went away for awhile, but it is back. Even tried facotry reset, didn't work.
I was able to install an HD version on Xoom running ics ROM
http://forum.xda-developers.com/showthread.php?t=1394637
May fix your problem but I doubt it. This should just change the buffering.
I had netflix issues too with honeycomb. It wouldn't even load to even log in.
Flashing the EOS nightly ICS rom fixed it.
What I did is uninstall find version 1.3 install that and visit the market it sees the old version and updates it.
Working fine now.
I have 1.3 if you need it I think but its the one found in xda forums
Sent from my MZ604 using xda premium
Everything was perfect when i was on Android 4.3, any skype calls working, video/audio doesn't matter.
But when i updated my wife's phone to kitkat, some skype calls making phone reboot(black screen, then its loading as usual).
It happens not always. And i have noticed that it crashes only while talking to people who have Windows XP installed(with latest version of skype, checked & updated myself).
When she talks to anyone on 7&8 Windows - everything is perfect.
I have tried all custom roms, original, rooted\not rooted, anything.
I gonna write this issue to Skype too.
Skype support asked that Skype not supporting KitKat yet.
Btw it only happens on Nexus 4, when i'm on my phone (XT910) on KitKat, it works and not hangs.
In my case occurs the same...I believe is maybe kit Kat by itself and usually happens when I leave a call in the background while I use another application. Unfortunately I haven't found any solution for that.
i have noticed that it crashes only while talking to people who have Windows XP installed(with latest version of skype, checked & updated myself).
Click to expand...
Click to collapse
Not really. The problem is a bit more serious: all ROMs (stock and custom) based on 4.3 or 4.4 are affected by this overly annoying camera bug. I obviously hope you're not, but if you end up as unlucky as I did, your camera and LED flash will soon become totally unusable (on all applications), fixable only by reverting to 4.2 or updating to L (I did and it's totally worth it)
Good luck :good:
Also another issue with Skype and N4 is that whrn listening to music and an image is being sent / received in the Skype chat window, fetching that image from the gallery/disk causes the audio system to crash. It's really annoying. Probably it's the same issue as the well-known audio stutters on changing connectivity and high cpu load.
Im using the Verizon G2 and running 4.4 2...xdabebb rom..i use skype a lot for business calls and havent come across this issue at all. On unrooted stock as well as custom. Ive also faced no issues on an S4 i9500...so it might not really be a kit kat issue but a nexus 4 specific...or an aosp based rom specific issue
Sent from my VS980 4G using Tapatalk
I have another kind of issue with my xiaomi Mi2 with MIUI Rom on kitkat 4.4.4. I have systematically a black screen when the communication is established on Skype also using test sound server. The sound is working but I can't do nothing with the phone until the end of communication decided by my correspondant.. Very annoying . I have post the question to Skype 5 days ago but no answer. Skype was working properly on my phone on miuiv5 android 4.1.2
Envoyé depuis mon Mi2 kitkat 4.4.4 Miui6
I'm having the exact same problem ... I was talking on Skype video call and the phone screen went black and I couldn't hear the other party.. I don't if they were able to hear me or not. I had to hold the power button and reboot my phone manually. I don't know what the problem is but its very annoying and it happened three times in a row. I have used multiple ROMs and it was happening on all of them and they were all 4.4.4. I don't flash kernels, I just use the kernels that come with ROM because they have obviously been tested and have been found compatible with the rom. So I know its not because of kernels. Currently I'm on Slimkat latest weekly and was thinking about going back to stock but someone said its also happening on stock ROM. I'm going to try CM11 and see if it happens there as well. Will report back soon. Hopefully it's just a 4.4.4 issue and not a phone issue.
Sent from my Nexus 4 using XDA Free mobile app
Helllllo everyone!
So I apologize for being one of those people who just come here to ask questions. Unfortunately life doesn't have room for me spending time playing with my Android devices anymore, so having it 'work' is more important to me.
I am on 4.3, ParanoidAndroid 3.96. I am not on the latest because it took some time to have the app TouchControl work (with my Franco kernel), and Secure Settings etc. that I chose to just stick with it because it worked really well for me.
The problem!
I recently noticed that if I tried to switch to the front facing camera, it'd hang. After that, I would not be able to use my torch/led, and going into the camera would tell me that "The camera is not connected" or something like that. I could only fix this by clearing all the data on my Gallery, and shutting down, and then turning on again. Reboot would not work.
If I did that, I could go into my camera and use the rear camera fine. Take pictures, record video, etc. Torch works as normal. It's just that once I attempt to go into the front camera, this problem happens.
It's weird because I didn't flash anything or change any settings when this happened. I DID install https://play.google.com/store/apps/details?id=eu.mrogalski.saidit which wouldn't let me record a video while being used, but I since disabled/uninstalled it which solved that problem.
I have done a lot of googling on this problem, and noticed that I am not the only one who has this problem. For some people it seems like their phone is new, and some it just happens out of nowhere. For that reason I suspect it might be a hardware problem that can occur randomly, but it's weird that after triggering the problem, that my torch won't work anymore as well. Unless the torch is somehow tied to the camera/flash, and by triggering the problem when I try to access the front camera, it isn't able to 'call' the camera/flash anymore as a result?
I bought my Nexus 4 from Google in May 2013, so I believe I still have until May 2014 to RMA it, correct? Would I get another Nexus 4 at this point, or maybe I'd get a Nexus 5 instead?
Thanks in advance for any insight into my problem!
I know you would like to keep the rom you are on but to be on that rom you must have a custom recovery installed. So if I was you I would back you're rom up then flash something different to see if its hardware related or not . If so then return the phone.
Sent from my Nexus 4 using XDA Premium 4 mobile app
bladebuddy said:
I know you would like to keep the rom you are on but to be on that rom you must have a custom recovery installed. So if I was you I would back you're rom up then flash something different to see if its hardware related or not . If so then return the phone.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply.
I tried installing the latest PA rom, but came up with an error. I had the rom I was on originally still, so I tried wiping and flashing it again. Finished flashing, went and opened the camera and it still happened. Looks like it's a hardware problem then!
I guess I'll go look up a guide to flashing back to stock now.
The problem arose in the first week of January.
Then I have done necessary criteria to have a custom rom.
But the roms failed to work properly in my phone. Mostly, with every rom, the SOUND was not working,
Then I have installed PE 10 PLUS, and it worked fluently without an issue.
But recently, with the PE 10 PLUS rom, the phone started to misbehave again and the apps are showing errors time to time
like, " X app is not responding", "SYSTEM UI ISN'T RESPONDING" .
And the phone freezes and gets restarted.
I don't think there is a sound IC issue, because, with PE rom, the sound was perfect.. So, what can be the issue and what i have to do?
nilanjan.joy said:
The problem arose in the first week of January.
Then I have done necessary criteria to have a custom rom.
But the roms failed to work properly in my phone. Mostly, with every rom, the SOUND was not working,
Then I have installed PE 10 PLUS, and it worked fluently without an issue.
But recently, with the PE 10 PLUS rom, the phone started to misbehave again and the apps are showing errors time to time
like, " X app is not responding", "SYSTEM UI ISN'T RESPONDING" .
And the phone freezes and gets restarted.
I don't think there is a sound IC issue, because, with PE rom, the sound was perfect.. So, what can be the issue and what i have to do?
Click to expand...
Click to collapse
Hey, I have the same issue with accessing mic speaker and sometimes camera too... I thought it's some IC issue. Let me know if any ROM gets around this issue
shrae said:
Hey, I have the same issue with accessing mic speaker and sometimes camera too... I thought it's some IC issue. Let me know if any ROM gets around this issue
Click to expand...
Click to collapse
Hi there. I used PE 10+ after facing the issue. Around one month, it was okay, but after the month, it started the same issue again, saying, "System UI IS NOT RESPONDING" then everything became unable to use.
Testing many roms, I found Evolution UI latest version working. please be noted, the roms has several bugs and SOT is lesser than the roms I used before.