Hi, everyone I am new here. Playing around with my Note 2 i317m Telus, flashing couple of roms and end up with Jedi series. Currently, running the Jedi-X19, it work perfectly and I just tried the newest Jedi-X20 , everything working great except viber, it can not start, when i choose it, it just open and stop, this never happened before. I tried to flash the rom again but the problem is still there. Need help. Thanks all.
Good I am not the only 1 with this issue. I am having the same issue with viber.. It keeps crazing when I try to open the app. I moved to beanstalk 4.3.1 for now..
Related
Hey guys,
I'm sorry if this has been posted before, but I've searched on the forums and on Google with no luck. Recently, my sound stopped working on my GSIII running CarbonRom 1.6. Nothing out of the ordinary happened, it just stopped working one day. Also when I'm in a call, the person on the other line cannot hear me. I've checked the sound settings numerous times and have made sure that I am not in silent mode.
I have tried other 4.2.2 ROMs and they all have produced the same result. I have also tried a factory reset and formatted data in TWRP. I reverted back to stock and have noticed that the sound seems to work when I'm not running 4.2.2 ROMs. Does anyone know what the problem might be? I really prefer the look and feel of vanilla Android and I'm really bummed out that 4.2.2 ROMs seem to kill sound. Thanks.
re: 4.2.2 roms
jdsung said:
Hey guys,
I'm sorry if this has been posted before, but I've searched on the forums and on Google with no luck. Recently, my sound stopped working on my GSIII running CarbonRom 1.6. Nothing out of the ordinary happened, it just stopped working one day. Also when I'm in a call, the person on the other line cannot hear me. I've checked the sound settings numerous times and have made sure that I am not in silent mode.
I have tried other 4.2.2 ROMs and they all have produced the same result. I have also tried a factory reset and formatted data in TWRP. I reverted back to stock and have noticed that the sound seems to work when I'm not running 4.2.2 ROMs. Does anyone know what the problem might be? I really prefer the look and feel of vanilla Android and I'm really bummed out that 4.2.2 ROMs seem to kill sound. Thanks.
Click to expand...
Click to collapse
That's an easy questiion, like I have been saying all along none of the cm10/aosp/aokp or ported roms
are ready for prime time, they are good for those who want to experiment with a few features not found
in stock t999 4.1.1 Touchwiz Jellybean roms. None of the cm/aosp/aokp roms even have the Wifi calling feature.
That's why after trying all the aosp/aokp/CM and ported roms I have come to the conclusion above.
So unless you like experimentation only flash T-Mobile T999 stock 4.1.1 Touchwiz Jellybean roms
or any of the custom roms which are based on T-Mobile T999 Touchwiz v4.1.1 Jellybean stock rom.
The best custom T999 T-Mobile Touchwiz Jellybean 4.1.1 based rom in my opinion
is the Wicked v9.1 custom rom, check it out you won't be disappointed.
Good Luck!
You could always try to flash your 4.2.2 Tim of choose and choose not to restore Google backup, Google backs up settings. If it works without setting up your account then go from there.
Sent from my SGH-T999 using xda app-developers app
Guys I just received my phone from service after the SDS syndrome.
I flashed to PACman ROM and PRObam 4.4.6 and 4.3 nightliy but with all three I am having problem with WiFi.
It seems to not been able to connect with all three.It says saved and then does not connect.
Any ideas? Otherwise what would you recommend me to flash to right now?
Please help me because I need a solution asap. I don't even have the stock rom and I need to download it, so I'd like to hear your opinions before I do.
orbitech said:
Guys I just received my phone from service after the SDS syndrome.
I flashed to PACman ROM and PRObam 4.4.6 and 4.3 nightliy but with all three I am having problem with WiFi.
It seems to not been able to connect with all three.It says saved and then does not connect.
Any ideas? Otherwise what would you recommend me to flash to right now?
Please help me because I need a solution asap. I don't even have the stock rom and I need to download it, so I'd like to hear your opinions before I do.
Click to expand...
Click to collapse
well try phoenix rom if want the 4.1.2 as for me the default sometime created problem connecting to wifi which still does and temporary solution solves it but its irritating when phone takes time or does not connect,which I found that the phoenix rom used to connect in a sec as it should be and never had problems connecting
Yeah,being this your first flashing experience,i suposed,why did you chose the 4.3 builds?I think wifi thing is 4.3 issue,if you want fast buttery smoth everlasting juice deliciusness flash thunder lite rom...
shhbz said:
well try phoenix rom if want the 4.1.2 as for me the default sometime created problem connecting to wifi which still does and temporary solution solves it but its irritating when phone takes time or does not connect,which I found that the phoenix rom used to connect in a sec as it should be and never had problems connecting
Click to expand...
Click to collapse
Thanks I will try it, I am out of solutions for fixing this weird issue with the CM 10.2 custom based ROMs. Just in case that 4.1.2 creates issues as well, can you recommend me your best 4.1.1 which works like a charm for me now?
Cruzfire said:
Yeah,being this your first flashing experience,i suposed,why did you chose the 4.3 builds?I think wifi thing is 4.3 issue,if you want fast buttery smoth everlasting juice deliciusness flash thunder lite rom...
Click to expand...
Click to collapse
No this is far from my first flashing experience even with Note 2. It's my first flashing experience as I said after receiving my phone from SDS syndrome (mobo was swapped). Why shouldn't I flash to the newest build if I can?
It had 4.1.1 and worked great as it works now with a custom 4.1.1 rom. The problem is with other custom ROMs and yes everything works amazing except WiFi connection with the CM 10.2 based that I tested (Nightly,Probam,PAC).
It should be a software issue with some devices in this code.
orbitech said:
Thanks I will try it, I am out of solutions for fixing this weird issue with the CM 10.2 custom based ROMs. Just in case that 4.1.2 creates issues as well, can you recommend me your best 4.1.1 which works like a charm for me now?
Click to expand...
Click to collapse
well stay away from 4.1.1 rom as its prone to sds so avoid it and yes thunderlite is even an amazing rom fast and stable now its upto you what u choose plus thunderlite has the battery advantage too if you go for phoenix choose 240dpi mode in aroma and enjoy the beauti of the beast ,the choice is yours, earlier i have tried N7100 Resurrection Remix® but in that case too wifi worked fine for me ,I would suggest a complete wipe install ,even wiping your system but do a backup of your current before proceeding in case.
shhbz said:
well stay away from 4.1.1 rom as its prone to sds so avoid it and yes thunderlite is even an amazing rom fast and stable now its upto you what u choose plus thunderlite has the battery advantage too if you go for phoenix choose 240dpi mode in aroma and enjoy the beauti of the beast ,the choice is yours, earlier i have tried N7100 Resurrection Remix® but in that case too wifi worked fine for me ,I would suggest a complete wipe install ,even wiping your system but do a backup of your current before proceeding in case.
Click to expand...
Click to collapse
Also tried 4.2.2 RootBox before and it still gives me the problem with WiFi. There's definitely something fishy going on with anything from 4.1.2 and above for me from what I've tested with 6 different ROMs..About the SDS syndrome I checked with eMMC program and it says it's a sane chip this time, before it warned me it was an insane one and after some time my phone had died on me.
Anyway I've had enough, just finished installing Phoenix V13 and tweaking the basics. Works amazing thus far and it looks like a great rom. WiFi works great and I think I'll stay with this one for the time being.
10 days without this beast were A LOT, I'm bored looking even further I hope this one will serve me well..
orbitech said:
Also tried 4.2.2 RootBox before and it still gives me the problem with WiFi. There's definitely something fishy going on with anything from 4.1.2 and above for me from what I've tested with 6 different ROMs..About the SDS syndrome I checked with eMMC program and it says it's a sane chip this time, before it warned me it was an insane one and after some time my phone had died on me.
Anyway I've had enough, just finished installing Phoenix V13 and tweaking the basics. Works amazing thus far and it looks like a great rom. WiFi works great and I think I'll stay with this one for the time being.
10 days without this beast were A LOT, I'm bored looking even further I hope this one will serve me well..
Click to expand...
Click to collapse
definitely it will
first i installed pacman rom for galaxy note 2 gt n 7100 and once it boots up this error appears onces every second, which is extremely irritating.....and now i installed probam and same error even on this rom as well.......both are 4.3 roms and its freaking me out i have been searching for some solution from longest time and many have the same problem but no particular solution. please if anyone knows how to get rid of it please let me know.....regards
greatgrandking said:
first i installed pacman rom for galaxy note 2 gt n 7100 and once it boots up this error appears onces every second, which is extremely irritating.....and now i installed probam and same error even on this rom as well.......both are 4.3 roms and its freaking me out i have been searching for some solution from longest time and many have the same problem but no particular solution. please if anyone knows how to get rid of it please let me know.....regards
Click to expand...
Click to collapse
I was getting this recently after downgrading from Androwook and installing PAC rom and gapps, was also getting it with some apps: "Unfortunately, Calendar has stopped. Blame Tyler."
I reinstalled PAC rom and gapps after wiping cache/dav/system fully and I'm not getting system ui ones any more but still getting it on Calendar.
I've heard suggestion that it's a corrupted gapps causing it but then im not sure I the system ui ones would be related and i md5 checked the files on the SD.
Anyone with more experience who can shed light on this?
To avoid cross posting asking abut this and other PAC romo issues here:
http://forum.xda-developers.com/showthread.php?t=2333171&page=33
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 .
Hello,
I'm pretty new to this and had installed CM12.1 before but wasnt as happy as I'm now with DN4.
Cause of the S pen functions and 3G working but might go to CM when it's finished maybe to test it out.
Now I was wondering if with DN4 v2.1 if you can install a different launcher instead of what it has now.
And can use it on CM 12.1 I tried but it didn't work as it crashed my firmware. Now DN4 currently works perfect but still would like to try a different launcher and before I test it and maybe screw up the firmware
I was wondering if someone could tell me if it's possible.
Many thanks much appreciated.