Please help me, facebook crashes on stock rom randomly... I've even flashed stock rom again with all wipes, but same, 251 version nougat, I don't wanna customs, tried few, I want working 1 key too
Related
Hello,
I don't have permission for posting in dev section so I'm asking my question here (yes,I did go through the forum n google to find a solution)
From the time I've started using custom roms,my camera app is not working properly. It crashes after 3-4 shots n my phone reboots. My phone freezes on the preview screen for a few seconds n then restarts. At first I thought its a rom issue but I've faced this same problem on reflex s,rcmix 2,leedroid 2.5 and SGBS and this problem never existed in the original rom.
What could be causing this? I'm using s off desire with 1gb ext partition (created using clockwork recovery screen)..
appreciate the help
thanks
Did you do full wipe before install ROM ?
If not, please do so.
If yes, I don't know the answer.
You can try install default ROM and start all over again though.
hello
thanks for the reply,I always do a full wipe when installing a custom rom..but don't know why this issue...
I'm scared to try the stock rom as I don't know what my original country was as I bought my phone from the local market without any warranty...!
someone...??
thats disappointing
try the sense 2.1 camera - it should work. To be honest I never had this problem when trying those sense-based ROMs, so no other idea.
Try flashing a newer/different radio
thanks for the replies..I didn't know the radio could have anything to do with the camera...will update n test for 2days n rite back
I'm using sgbs rite now with sense 2.1 camera...before this I had rcmixs,reflex s,Lee droids...all had similar issue,some more than the other..
BTW off topic does anyone know how I can get only sense 3 weather on sense 2.1? And which is a good sense 3 rom with stock android lock screen working...as sense 3 lock screen n caller screen is kinda annoying!
thanks
Hello everyone,
I'm posting on here because I can't find any solution to my dilemma which I am sure that other people in the AOSPA legacy community have also experienced. I have been using Paranoid Android on my T989 since the 4.4.3 update and I have regularly updated my roms since then. Somehow ever since I updated my phone to 4.5 beta 3, something prevents me from being able to hear or be heard during regular phone calls around an hour after I restart my phone.
I have tried everything to try to make my phone back to normal, I have updated my versions of AOSPA, I have downgraded to stable versions, I have gone to a debloated stock rom (which worked perfectly fine but who likes touchwiz android 4.1.2?) and back to AOSPA, I tried the latest Carbon nightly rom and the problem persisted, I have wiped my internal memory, cache, davlik, etc. multiple times. I am at a total loss as to what I should do to fix this issue. I'm currently running it on 4.6 beta 1 and I still have the issue.
I really love my GS2 and I don't want to part with it or have it running stock. Please help me.
I really appreciate it,
Chris
I've had the same issue , I was running the latest liquid smooth rom . I just flashed back to stock using Odin and all is fine on the stock rom . I just rooted again and am hesitant to install another kitkat rom for fear of this calling issue ........ Anyone else with this problem ?
Playnhooky said:
I've had the same issue , I was running the latest liquid smooth rom . I just flashed back to stock using Odin and all is fine on the stock rom . I just rooted again and am hesitant to install another kitkat rom for fear of this calling issue ........ Anyone else with this problem ?
Click to expand...
Click to collapse
I am also getting this problem on Slim 7.8....must be an audio-caf issue....Can someone go back to an old KK rom (one from earlier months) and see if they experience the same issue? Preferably cyanogenmod
I flashed to stock rom via oden and spent the weekend with the phone and all was good , I flashed to the latest cm-11 with no addons , stock cm-11 kernal and after an hour or so I lost call audio again . We must have done something to the phone in a previous rom cause not many people are having this issue . Now I have flashed about 75 different roms with no issue , I hope someone finds the problem cause I'm not to keen on the stock rom !
I've seen posted that snapchat was the cause of the no call audio problem we are having , I flashed the latest liquid smooth rom last night , download all my apps that I usually do except snapchat and I've had no issues with the calling bug . All is working great .
Hi there
since lollipop i change my official 4.4.4 stock rom to 5.0 leaked stock rom from skin 1980 and then i changed it to his chupachups rom, everything was going very good in both roms very fluid, and without having calls issues, then i try the cyanogenmod 12 rom from manusps4e, thats when im starting to have this issue:
everytime i try to make a call the screen goes black and i cant re-activate it, i can make the call but i have to reboot the G3 so i can use the phone again. its the same thing when i receive a call.
so then after many nightlies from this rom i try the cloudy and go back to stock but al got the same problem in every rom.
what you guys think it is?
do you think its firmware problem? rom problem? or hardware problem?
NOTE: sorry if i couldnt explain myself perfectly but im latin american so my English its not very good. and this is my first post
Hello. I have a problem when i installed custom rom like CM and AOSP . Snapchat and instagram cant upload videos its said failed
But when iam back to stock rom everythings working fine . Please i need help can anyone tell why!! I want solution for this :S please
Installed Custom rom and script , ONLY IN LOUDSPEAKER, what can I do ???
I have the same problem since an hour.
But no custom rom. Just a new xposed module.
Any suggestions?
i got the same problem please someone help us
please someone know how to fix it i got hte official rom but i got the same problem
Yesterday I flashed the stock ROM again.
I didn´t found another solution.
Now it works fine again.