Hey guys I've ran cm11 for about a year now, and recently went back to TW stock due to BT issues on CM11. BT works great on stock. I've recently upgraded to cm12 and bt issues are better than cm11 but not as good as stock. Is this because I am running a different modem? I am on MDK bootloader, I was wondering how do i tell which radio+modem I am running. I've always had issues with MMS and Internet when my signal is less than 50%, which shouldn't be the case. I figured a updated radio might fix this?
Related
Just wanted to say that ive been lurking here ever since I had a Windows HD2....
Anyways, I flashed CleanRom 4.7 yesterday and charged it fully before taking it off the charger this morning. Despite the abnormal battery drain (which is abnormal even for a just flashed rom) and the weird signal issues with it switching to roaming and the like.
I clean flashed the rom, and currently have the Perseus kernel.
EDIT: I also couldn't get a GPS lock which I believe is/was a common issue? I would also receive the VZW text messages and WiFi authentication errors, even when connected to an open WiFi connection.
Only reason I didnt post this in the Development section is because of the post count.
Are you having issues with any other ROM?
Did you make sure to flash the ROM for your carrier?
I use CleanROM ACE, my wifi works as expected.
The Verizon text message will go away if you log into your Verizon account and remove the backup feature.
The GPS can be fixed by flashing a different ROM, getting a GPS lock, then flashing back to clean.
pool_shark said:
Are you having issues with any other ROM?
Did you make sure to flash the ROM for your carrier?
I use CleanROM ACE, my wifi works as expected.
The Verizon text message will go away if you log into your Verizon account and remove the backup feature.
The GPS can be fixed by flashing a different ROM, getting a GPS lock, then flashing back to clean.
Click to expand...
Click to collapse
I came from Beans Build 12 and I didnt have any problems then besides being able to get a GPS lock. I switched over to CR 1.5 SE just to see how it goes, and if it runs smooth thats what ill stick with until he comes out with another build for ACE.
Just a little update:
Battery drain is far more stable (or normal), and everything else for the most part seems like how it should. Only thing I havent tried is getting a GPS lock.
Guess CleanRom 4.7 isnt for me as of now lol
Was on CM10 WiFi and reception was a problem and was getting dropped. Flash STOCK ROM then flashed back CM10 to see if it would fix things and NO. Now I'm back on STOCK ROM and EVERYTHING works PERFECTLY and running smooth with ME's Kernel. Anyone have similar issues? I really like CM but don't want to flash all similar CM10ish ROMs to find out WiFi is Borked. How come only some have select or problems with reception and WiFi? Its not like I flashed other radios. I'm still on JB radio. Just frustrating
Sent From my Dope Droid DNA
Hi Everyone,
So I recently made the switch from 4.2.2 to 4.3 today morning. I went from dvhexer's CM10.1 to CM10.2 and found that everything is nice and smooth and fast - installed without problems etc.
Then I made my first call to check my voice-mail and I got no sound from the earpiece on the phone. Being the clever fella I am, I turned on the speaker and I could hear that the call was in progress. I next tried headphones and that worked too. So I googled the issue to see and I saw a couple people who had similar issues.
I flashed several modems/radios (including some hybrid morrislee variety), flashed several kernels but ultimately couldn't get the sound to work. I also tried bruthaedhung's PACman Rom (4.3) and it had the same issue. Does anyone here have a fix for this issue? I'm in a health related professional grad schools so privacy in calls is kinda important and I can't always have speaker phone calls!
Thanks for your help!
EDIT:
My LGOG has not been converted to an N4 (Ever) it is currently running CM10.1 without any issue (no hardware failure). The only thing that may be different here is that I am on T-Mobile instead of AT&T (unlocked AT&T model). The problem is only showing up on the custom built 4.3 roms.
I had an unlocked S4, which took an unfortunate dive and ended up non-functioning. I used my phone insurance to acquire a new (unfortuantely) updated phone running the full MK2 suite. First order of business was a root & install of SafeStrap, followed by installation of Hyperdrive to Rom Slot 1. I use my phone with my 2013 Subaru XV Crosstrek's bluetooth handsfree for both calling and media playback, and I use this feature EVERY SINGLE DAY. Unfortunately, not any more. I cannot get more than 15 seconds of connected time over bluetooth with the phone. I've tried multiple wipes. I'm fairly certain the issue doesn't exist on stock rom; so I may end up just customizing a stock rom in slot 1 by removing absolutely everything and building it from the ground up, since I don't have to use the (apparently buggy) mk2 modules.
Edit:
I'm seriously considering selling this phone and getting something more friendly to modding, this is a repeat of the Droid Bionic at this point.
Is there a question here? Did the stock rom blue tooth work ok?
Sent from my SCH-I545 using XDA Premium 4 mobile app
And this is why I shouldn't hastily write a post.
Yes there should be a question:
What can I try to fix the issue of frequent (alarmingly) bluetooth disconnects?
What kind of logging can I do to try and help provide developers with the information to fix this?
Anybody else have this problem? Any experience fixing it?
If I can't get this fixed, I have no choice but to move to another phone. Preferably at Verizon's expense.
Even more irritating: The phone is listed as compatible with the Crosstrek. I'm going to test that it works fine using the stock rom and bluetooth, and factory resetting my head unit.
Did you install the MK2 modules after installing Hyperdrive?
s.whiplash said:
Did you install the MK2 modules after installing Hyperdrive?
Click to expand...
Click to collapse
Yes. Originally when I installed it WiFi and Bluetooth didn't work at all. I realized quickly my error was the lack of installing the MK2 modules. I wiped and installed again, this time ensuring the MK2 modules followed the rom install. I got everything set up the way I like to, and began day to day use of the phone. Since then I have had the bluetooth connectivity problems I described above.
Bluetooth is rock solid on stock. I'd really rather not have to play this game where I can install stock or.... basically stock... and now that I'm locked kernel and radio wise if I have issues further with OTAs I'm just as stuck with a near useless phone as I was with my Bionic
I'm afraid that I don't have anything else for you, except try a different ROM. Bonestock or Eclipse? Bluetooth works pretty good for me with multiple headsets and vehicles. My only issue with Bluetooth is not all the apps will pass metadata to my truck. This happens with all 3 of these ROMs and I think it is a TW 4.3 limitation.
Are you doing anything to boost the Bluetooth volume? With my previous phone I boosted the Bluetooth volume via some hacks and my truck would not like it.
I know what you mean about having a locked down phone. I came to the S4 via a warranty replacement from an unlocked S3 running SlimBean and SlimKat.The problem is that most of the new phone that are coming out all have bootloader hurdles.
I'm having the same issue with my SGH-M919 (T-Mobile) running rooted stock TW. I've documented my issues and a few LogCats here. Have you figured out a solution?
Greetings all,
newbie to XDA so please bear with me.
I have been looking over posts for a while and still noticed the same issues with the Sprint Glaxay Note 3 and custom Roms.
So, can someone please tell me the process that works for getting you GPS to work and stable netowr (LTE/WiFi).
I noticed any Rom with a KitKat base works fine, however, when you move into a lolipop based Rom
or CM12, GPS and Network fail.
I use TRWP and have found no solution in getting the GPS to work.
What am I doing worng?
Thanks all,
I found this solution for the mobile data issue:
forum.xda-developers.com/note-3-sprint/development/baseband-modem-nh7-odin-flashable-t2882926
I'm still trying to find a fix for the GPS issue myself. GPS will somewhat work sporadically but it won't get a solid Lock like it's supposed to
Thanks, I found the priest rom works flawlessly and GPS is working with stronger signal.
I also found less wifi and sprint network issues.
KitKat killer worked as well but had issues on sms and others were it would freeze up. Connectivity issues as well.
Priest is the best I have found and can't say enough good things about it, wish it was easier to find and updated to the 5.1 base, other than that, it solved my problem.