Im trying to figure out why EVERY custom rom available in both "android development" and "original android development" works pathetically with Project fi.
Stock images from google have always worked stable and flawless with project fi. well i wont say flawless, id still see "no service" every once in a while, but when i needed it it would work. but when i root/ twrp/ and begin to install rom, project fi always ****s out bad.
Small example of some....
Mokee rom = Constantly get "no service" or "emergency calls only"
Omni rom = Cannot send text while on sprint towers, and cannot receive on tmobile
Bliss Rom = Constantly switches between tmobile and sprint, and constantly has "configuring service"
Tesla Rom = Can recieve text, "sent text" never get recieved by the recipient
Pure nexus = No service on tmobile towers
Xtrafactory = work the best, but constantly leaves me "no cellular service" messages and Switches to often
Does anyone else have this problem? is there a simple solution i have not come across? Do i need to follow a guide like this?
coming from a nexus 6 on verizon. im getting really disappointing that i have to be on a stock image to have a fully functioning device, someone please help.
Dirty Unicorns and Uberstock/Ubermallow worked flawlessly for me on Project Fi no matter which network (Sprint or Tmo) was actually being used at that time; and I live in an area where switching between the two is pretty common. If you want to have more control over which network you're using without having to use Dialer codes, look into FiSwitch on the Play Store.
I noticed in your other thread that you complained about LG's CPU throttling, which can be mitigated by using a custom Kernel. Most custom kernels bump the throttle limit up to a higher temperature and the hotplug limit even higher.
Alcolawl said:
Dirty Unicorns and Uberstock/Ubermallow worked flawlessly for me on Project Fi no matter which network (Sprint or Tmo) was actually being used at that time; and I live in an area where switching between the two is pretty common. If you want to have more control over which network you're using without having to use Dialer codes, look into FiSwitch on the Play Store.
I noticed in your other thread that you complained about LG's CPU throttling, which can be mitigated by using a custom Kernel. Most custom kernels bump the throttle limit up to a higher temperature and the hotplug limit even higher.
Click to expand...
Click to collapse
i can force switch on the stock rom and everything work fine. at my home, i get full sprint and tmobile coverage, but none of that matters on a custom rom for me. and even with custom kernels, what really bothers me is the temp to perf ratio.
For the nexus 5x to be even comparable to my nexus 6, the 2 1.8 cores HAVE to be on, which of course causes heat, which causes throttling
noidea24 said:
i can force switch on the stock rom and everything work fine. at my home, i get full sprint and tmobile coverage, but none of that matters on a custom rom for me. and even with custom kernels, what really bothers me is the temp to perf ratio.
For the nexus 5x to be even comparable to my nexus 6, the 2 1.8 cores HAVE to be on, which of course causes heat, which causes throttling
Click to expand...
Click to collapse
Give the ROMs I mentioned a try. I've had rare issues with messages sending or the network activating while on Sprint when on other ROMs but DU and Ubermallow/stock were, again, flawless.
The big cluster on my phone rarely throttles itself. It's a burst CPU, not a workhorse. The LITTLE cluster is supposed to do most of the work. I'm not sure what you're attempting to do with your phone that has you so concerned with the performance matching your Nexus 6, but if it's benchmarks or something heat is always going to be an issue. If you're really not that enamored with this device, you can give the Nexus 6P a shot, now that you're on Project Fi.
Dirty unicorns with stock kernel is what I'm on at the moment. I didn't give it a chance before because DU always sucked on my galaxy nexus, nexus 5, and nexus 6. But on the 5x, its beautiful. For the first time since I've been on project Fi I'm seeing solid constant signal, Fast switching, and no "emergency calls only". I am seeing my phone drop to 3G ALOT more than before, but I can live with that.
And it's not even benchmarks, or games, etc, its literally daily use. I'll notice stutter and lag randomly, even now as I'm typing it its happening. Checking kernel adiutor, and my big cluster is stuck at 633mhz. I can only use my phone for about 3 minutes before it throttles, and its clear each and every time it does.
The bad thing is my CPU temp is reporting at 39, I can see thermal throttling is Set at 45, clearly under the limit. Yet i cannot get the two cores over 633mhz
noidea24 said:
Dirty unicorns with stock kernel is what I'm on at the moment. I didn't give it a chance before because DU always sucked on my galaxy nexus, nexus 5, and nexus 6. But on the 5x, its beautiful. For the first time since I've been on project Fi I'm seeing solid constant signal, Fast switching, and no "emergency calls only". I am seeing my phone drop to 3G ALOT more than before, but I can live with that.
And it's not even benchmarks, or games, etc, its literally daily use. I'll notice stutter and lag randomly, even now as I'm typing it its happening. Checking kernel adiutor, and my big cluster is stuck at 633mhz. I can only use my phone for about 3 minutes before it throttles, and its clear each and every time it does.
The bad thing is my CPU temp is reporting at 39, I can see thermal throttling is Set at 45, clearly under the limit. Yet i cannot get the two cores over 633mhz
Click to expand...
Click to collapse
Glad you got the signal thing worked out.
As for the CPU, I'd recommend using ElementalX Kernel Manager as your kernel app, Kernel Adiutor doesn't even display correct information half the time, it's pretty frustrating because I used to love that app. If you download EXKM, check to see what the maximum frequency is set to for the big cluster. It should always be 1824MHz, the idle should be 633MHz. As I said before, it's a burst CPU. It won't be running higher than that for most of the time that the cores are out of deep sleep. If you're using the stock kernel that came with DU, I recommend you try the BlueJay Tweak that's in my signature. Its the smoothest profile I've used yet and it's specifically made for the stock DU kernel. To help with typing lag (I don't know what keyboard app you're using) you can try forcing GPU rendering in Settings > Developer Options. The lag you might be experiencing is because the stock DU kernel doesn't have input boost like most kernels, which really helps when touching the screen (duh), especially typing because it gives it that extra clock rate for animations (which the gpu should be taking over for after forcing gpu rendering) and word prediction / correction (quite demanding).
On the topic of heat, EXKM should also have a few options for thermal throttling in the CPU section. Thermal Throttling, Core Control and MSM thermal might be the three options, can't remember off hand. Core control should be enabled by default but you can disable that if you'd like. The Thermal Throttling is the limit at which the phone hotplugs the big cluster so you can try bumping that up too as it's set moderately conservatively. These CPUs can handle much more heat than people think.
Well DU was nice until I found out that I have to be in speaker phone during a call for the other person to hear me. And the uberstock ROM is no better with the network problems, particularly the "no service, emergency calls only" which occurred ALOT.
I always use google keyboard or the generic aosp keyboard that comes with ROMs. Its mostly when typing in a browser like chrome/yubrowser/and rs browser.
And I've already cashed out on the Franco kernel updater paid version, so I'm not much for purchasing EXKM yet. But FK updater is showing the same as kernel adiutor, the max for the big cores is stuck at 633. I can lower the max and min anywhere below 633, but as soon as I click a tad higher, it reverts. I think the device may be heating up and Colling down quicker than I can go in and check it.
Maybe i can get more views by commenting instead of making a new thread.
ive noticed on at least 3 roms (omni, Pure Nexus, chroma) that i have sms problems, for example....
Omni, i can send text on tmobile, but not on sprint towers.
Pure Nexus, cant send or recieve anything on tmobile.
Chroma, sent messages always report failed on sprint towers, sometimes it will send, some times it wont.
Google wants me to pay to overnight a sim card, in hopes it will fix my problem. but i dont want to cash out $17(i know its not alot) for a sim card when everything works on stock.
Not sure if this will help you, but CDMA/Sprint doesn't use SIM cards. It uses a SIM card for LTE data, but not for basic voice/sms/3g. They go by the ESN of the phone for voice/sms/3g and the SIM card for LTE data.
Your Fi SIM card is coded with TMobile as the default. In GSM all the service specifics are contained in that SIM card.
I *think* project fi app is doing some software magic to switch to Sprint.
I am *guessing* if that software magic doesn't happen things won't work well on Sprint.
It isn't as simple as the GSM case where everything is handled by the Radio and the SIM card and you just put the SIM in a phone and stuff starts working. The application software running matters because it needs to make adjustments for a CDMA carrier. I'm guessing that stuff it is doing isn't well documented and if the steps are missing various stuff on Sprint won't work. I am guessing many custom ROM developers aren't aware of what Fi is doing so some of the magic is missing.
Related
So here's the deal, I recently rooted my Evo and installed latest Cyanogen (stable). It is amazing and I get over twice as much memory available at an given time than the sprint lovers rom (htc sense). But I have one problem: the cellular/wifi radios are really buggy. First of all, I get significantly less service wherever I am, and I can't ever send a text message over 160 chars (that is, 2 or more txts simultaneously). Now I don't know that the txt issue is because of the crappy stock messaging app cyan comes with or what (if you know any good txt messaging apps let me know, something that resembles the functionality of the default htc sense app?) but here is my main question:
Is there a radio update for the EVO? Regardless that 4G isn't even supported in Cyan (shame since I have to pay 10$ a month for something that's not even an option on the rom) I downloaded 6.1 straight from the cyanogen site and the google apps as well. Flashed through clockwork recovery. Works great and much much faster don't get me wrong, but the cellular radio sucks. Let's sum it up:
1. Cellular radio update?
2. WiFi radio update? (turns on and off randomly, don't get as much range)
3. A rom similar to cyanogen in terms of functionality, but with these issues addressed? (that is, lots more free memory than stock rom, 4G capability, good signal, etc)
Sorry if this makes no sense or goes on too long, but Cyanogen is one hell of a mod, just sucks that it basically downgrades the actual PHONE part of my phone. Thanks for any replies
I'm also having similar issues... For your WiFi, turn the sleep policy to never and see if that helps.
Go to Settings->Wireless & networks-WiFi settings then press menu->Advanced then set your WiFi sleep to never.
As for the cell radio, I'm also having significantly less signal reception. My wife has Baked Snack 1.9 and in the same area where she'll be at full bars, i'll be at like 2 and my download speeds are ass..
killer1one1 said:
So here's the deal, I recently rooted my Evo and installed latest Cyanogen (stable). It is amazing and I get over twice as much memory available at an given time than the sprint lovers rom (htc sense). But I have one problem: the cellular/wifi radios are really buggy. First of all, I get significantly less service wherever I am, and I can't ever send a text message over 160 chars (that is, 2 or more txts simultaneously). Now I don't know that the txt issue is because of the crappy stock messaging app cyan comes with or what (if you know any good txt messaging apps let me know, something that resembles the functionality of the default htc sense app?) but here is my main question:
Is there a radio update for the EVO? Regardless that 4G isn't even supported in Cyan (shame since I have to pay 10$ a month for something that's not even an option on the rom) I downloaded 6.1 straight from the cyanogen site and the google apps as well. Flashed through clockwork recovery. Works great and much much faster don't get me wrong, but the cellular radio sucks. Let's sum it up:
1. Cellular radio update?
2. WiFi radio update? (turns on and off randomly, don't get as much range)
3. A rom similar to cyanogen in terms of functionality, but with these issues addressed? (that is, lots more free memory than stock rom, 4G capability, good signal, etc)
Sorry if this makes no sense or goes on too long, but Cyanogen is one hell of a mod, just sucks that it basically downgrades the actual PHONE part of my phone. Thanks for any replies
Click to expand...
Click to collapse
1. Yes there are new radios, flash them.
2. What the guy above me said.
3. Look in the EVO 4G Android Development section for AOSP ROMs, those the issues are generally generalized across the board. For the mms issues, just use "handcent" from the market.
killer1one1 said:
So here's the deal, I recently rooted my Evo and installed latest Cyanogen (stable). It is amazing and I get over twice as much memory available at an given time than the sprint lovers rom (htc sense). But I have one problem: the cellular/wifi radios are really buggy. First of all, I get significantly less service wherever I am, and I can't ever send a text message over 160 chars (that is, 2 or more txts simultaneously). Now I don't know that the txt issue is because of the crappy stock messaging app cyan comes with or what (if you know any good txt messaging apps let me know, something that resembles the functionality of the default htc sense app?) but here is my main question:
Is there a radio update for the EVO? Regardless that 4G isn't even supported in Cyan (shame since I have to pay 10$ a month for something that's not even an option on the rom) I downloaded 6.1 straight from the cyanogen site and the google apps as well. Flashed through clockwork recovery. Works great and much much faster don't get me wrong, but the cellular radio sucks. Let's sum it up:
1. Cellular radio update?
2. WiFi radio update? (turns on and off randomly, don't get as much range)
3. A rom similar to cyanogen in terms of functionality, but with these issues addressed? (that is, lots more free memory than stock rom, 4G capability, good signal, etc)
Sorry if this makes no sense or goes on too long, but Cyanogen is one hell of a mod, just sucks that it basically downgrades the actual PHONE part of my phone. Thanks for any replies
Click to expand...
Click to collapse
One thing to realize with the bars measuring signal strength...on sense roms they measure cellular signal, while on cyanogen they measure data signal. So most likely it will always look like you have a weaker connection on cyanogen.
01geoffg said:
One thing to realize with the bars measuring signal strength...on sense roms they measure cellular signal, while on cyanogen they measure data signal. So most likely it will always look like you have a weaker connection on cyanogen.
Click to expand...
Click to collapse
??? Who told you this? I'm not seeing the correlation on my and my wife's EVO's... My signal is low when hers is high then my speeds and voice is ass while both of hers is ok.
1) Signal isn't really any worse, just HTC's bars lied about it (it's a common thing with OEM's. Apple did it with AT&T until they got busted and reeled it in a bit). If you want to see your real signal, go into the CM settings, and under the UI section, enable the dB signal display, and disable the bars. THERE'S your real signal.
2) Texting: CDMA is limited to 160 characters. All that Handcent and the HTC Messaging app do is automatically split and join sequential messages, or you can do it yourself when you text, manually.
3) Wifi: CM will automatically stop using a network if it detects that it's going in and out of range so much that it's killing the battery, and right now, you have to manually re-enable the network.
4) Go to a Sense ROM, update PRL+Profile, make sure your PRI is up to date, etc. etc. etc.
5) If you really don't like CM, just search for AOSP ROM's, or you can always go back to a Sense-based ROM. Nobody's holding you hostage except yourself.
I get better everything on CM than I do on Sense.
drmacinyasha said:
1) Signal isn't really any worse, just HTC's bars lied about it (it's a common thing with OEM's. Apple did it with AT&T until they got busted and reeled it in a bit). If you want to see your real signal, go into the CM settings, and under the UI section, enable the dB signal display, and disable the bars. THERE'S your real signal.
2) Texting: CDMA is limited to 160 characters. All that Handcent and the HTC Messaging app do is automatically split and join sequential messages, or you can do it yourself when you text, manually.
3) Wifi: CM will automatically stop using a network if it detects that it's going in and out of range so much that it's killing the battery, and right now, you have to manually re-enable the network.
4) Go to a Sense ROM, update PRL+Profile, make sure your PRI is up to date, etc. etc. etc.
5) If you really don't like CM, just search for AOSP ROM's, or you can always go back to a Sense-based ROM. Nobody's holding you hostage except yourself.
I get better everything on CM than I do on Sense.
Click to expand...
Click to collapse
Yeah I know about the dbm, pretty neat, but ugly in the status bar CM is nice aside from the lack of 4g, which we will get soon. It's just that so far my 3g speeds are ass compared to when I use a sense ROM... nothing can be perfect I guess.
So first a little bit about my phone:
It's a GSM Galaxy Nexus on Telus in Canada. It's rooted and running AOKP M4. I had just flashed Franco Kernel M2, but that's when my trouble started to I just wiped my data, reflashed AOKP M4 and restored from a back-up from before I flashed that kernel. I've never flashed a new radio.
The problem is as follows: when the screen goes to sleep, I lose signal altogether. I don't receive calls, I don't receive texts, nothing. But as soon as I wake the screen, the signal comes back (and it's strong - 3 or 4 bars so it's not a service issue).
Has anybody else had a similar problem? What's the fix?
Any help would be appreciated...thanks!
------------UPDATE--------------
Confirmed that I had no issues after flashing back to 4.0.2 stock. Went back to stock 4.0.4 and the problem surfaced again. Tried B29 of AOKP and utilized a minimum CPU setting of 700 MHz which resulted in no issues with the phone signal after going to sleep. I was able to duplicate the problem when I set the CPU to a minimum of 350 MHz. Went back to 700 MHz minimum and everything is working fine.
I'm wondering if the stock 4.0.4, in an effort to squeeze more battery life, lets the processor speed dip down below the threshold require to keep the phone "listening".
-------------------------------------
I've had the same issue after upgrading my phone to 4.0.4. It started life as a 4.0.2 GSM GNex with the Samsung ICS build on it. I flashed the Google version, then manually updated to 4.0.4. I've been searching the forums and found quite a few people with the same problem, but no real solution yet. I'm going to try a few things before taking a swag at a new radio.
I have the exact same problem
I have a GSM Samsung Galaxy Nexus on Vodafone, and within about 2 minutes of the screen sleeping, it loses connection to the network. When awakened, it will re-establish the connection within 5 seconds or so, but it is intensely irritating as I have missed lots of phone calls with this bug.
It has occurred on both my 4.0.2 patched to 4.0.4 and a clean install of 4.0.4 from google's website
I am about to revert back to 4.0.2, but if anyone can fix it in the meantime I would be eternally grateful.
-------------------------------- UPDATE ---------------------------------------------
I concur with warhummer. After rooting my Nexus again after the 4.0.4 update, and installing CPU Tuner from the Market place, I increased the minimum CPU speed to 700mhz (up from 350mhz) and it appears to be keeping its signal now. This would also tally with the fact that while my Nexus was doing things in the background it would maintain signal, but as soon as it was idle, within a few minutes the signal would die.
--------------------------------------------------------------------------------------
memoreks said:
I have a GSM Samsung Galaxy Nexus on Vodafone, and within about 2 minutes of the screen sleeping, it loses connection to the network. When awakened, it will re-establish the connection within 5 seconds or so, but it is intensely irritating as I have missed lots of phone calls with this bug.
It has occurred on both my 4.0.2 patched to 4.0.4 and a clean install of 4.0.4 from google's website
I am about to revert back to 4.0.2, but if anyone can fix it in the meantime I would be eternally grateful.
Click to expand...
Click to collapse
I've confirmed a fix (for myself anyways) that if you can get a CPU app that can modify the processor speed, try that via the stock 4.0.4. I'm going to flash mine now.
I have the exact same problem. I was on a Rom stock 4.0.2 with root, and after flashing the OTA, I had the problem when the screen is off.
To be sure I flashed the factory image in 4.0.4 but I still had the problem.
I looked at logcat and I had this error that seems to be the problem:
Code:
03-30 15:58:16.639 E/ConnectivityService( 186): Exception trying to remove a route: java.lang.IllegalStateException: Unable to communicate with native dameon to add routes - com.android.server.NativeDaemonConnectorException: Cmd {interface route remove rmnet0 default 10.114.222.1 32 0.0.0.0} failed with code 400 : {Failed to remove route from default table (No such process)}
03-30 15:58:16.639 E/ConnectivityService( 186): Exception trying to remove a route: java.lang.IllegalStateException: Unable to communicate with native dameon to add routes - com.android.server.NativeDaemonConnectorException: Cmd {interface route remove rmnet0 default 0.0.0.0 0 10.114.222.1} failed with code 400 : {Failed to remove route from default table (No such process)}
I'm going to send my phone to repair and hope they change it, or if someone has a solution.
Right now I flashed the 4.0.2 factory image to be able to use my phone.
PS : maybe someone know how to contact a Google dev ? To report the problem to them ?
SetCPU fixes it
How to sort out the problem of losing signal when GNexus goes into Standby:
1. Install 4.0.4 Stock ROM
Either use the OTA patch or do a clean 4.0.4 install from the Google Stock ROMs page.
2. Root your GNexus
There's lots of info about rooting you GNexus. I used CWM to root mine.
3. Install SetCPU
4. Run SetCPU, and raise the minimum CPU speed from 350mhz to 700mhz. Then tick "Set on Boot". (see attachment)
This should now mean your phone functions perfectly well again, and you benefit from the other good stuff in 4.0.4.
Thank you for the solution, but I don't want to achieve it that way for me there is a real problem with probably a hardware piece or something.
I contacted Jean-Baptiste Queru on Twitter, and he said that he will see who can talk to for this.
In the meantime, my Galaxy Nexus is going for repair in the hope I will have a brand new one
mephissto said:
Thank you for the solution, but I don't want to achieve it that way for me there is a real problem with probably a hardware piece or something.
I contacted Jean-Baptiste Queru on Twitter, and he said that he will see who can talk to for this.
In the meantime, my Galaxy Nexus is going for repair in the hope I will have a brand new one
Click to expand...
Click to collapse
i'm having this problem too. but would it be a hardware problem? i don't remember this happening in 4.0.3. you might just be returning it for another phone with the same problem if you update to 4.0.4
It might be a harware problem caused by a some code that was not in Android 4.0.2
I tried CyanogenMod 9 which is on Android 4.0.4 (same bootloader and radio as stock 4.0.4) but AOSP and I had the same issue.
It's really stranged because there are not a lot of people that have this issue.
Let's hope we will have news from Google soon
I stopped having this problem in 4.0.2 and 4.03, when I updated to 4.0.4.
mephissto said:
It might be a harware problem caused by a some code that was not in Android 4.0.2
Click to expand...
Click to collapse
then that's called a software problem lol
mephissto said:
It might be a harware problem caused by a some code that was not in Android 4.0.2
....
It's really stranged because there are not a lot of people that have this issue.
Let's hope we will have news from Google soon
Click to expand...
Click to collapse
I also have exactly the same errors in logcat.
Sent from Galaxy Nexus
I have raised a bug report with Google
I have raised a bug report with Google.
Unfortunately I cannot post a URL, so you need to go to:
code.google.com/p/android/issues/list and search for issue 28133
It might help if those of you who are experiencing this problem add comments to the post, try and raise its profile with Google somewhat.
@ceejay83 : I know, but only a few devices have this issue, that's why I assume it's also related to hardware.
@memoreks : Thanks for the link, I'll go there to also post a comment.
---------- Post added at 11:17 PM ---------- Previous post was at 11:08 PM ----------
Here is the link to the issue on Google code : http://code.google.com/p/android/issues/detail?id=28133
Please star this issue so Google notice it
I've starred the issue at the link posted, and I'm trying radio UGLC1 from the link below to see if it helps to use a newer radio.
http://forum.xda-developers.com/showthread.php?t=1405345&page=37
I found this thread about radios days ago, where you can find all existing radios, if you want to try others.
http://forum.xda-developers.com/showthread.php?t=1405345
Found your thread on google code. This is what I posted there:
I have a similar issue. My phone doesn't lose signal for good, it just drops and comes back on 5 seconds later and this loop keeps repeating with random times between drops(1 minute intervals most of the time). It started right after updating to 4.0.4. I installed an app to help track when signal drops, I attached and screen of the app. I also tested with AOKP build 28 based on 4.0.3 and the problem was still there. I will test a 4.0.2 build soon.
does it only happen in a weak 3g area? i noticed my phone having signal problems after updating to 4.0.4 too. In the secret menu, *#*#4636*#*# the preferred network type is set and stuck to wcdma preferred and if you are like me and are in a weak 3g area the phone will still prefer a weak 3g to a strong 2g signal. it prefers 3g so much that it will still hold on to it for hours even when the signal is too weak to make or receive calls. With 4.0.2 it was set to gsm/cdma prl which prefers a strong 2g but will switch when there is a strong 3g signal. unfortunately you cannot change this setting in 4.0.4.
i tried ugkl1, ugla4,, xxla2 and now using uglc1. they all had similar signal strength and will hang on to a weak 3g, so i dont think the radio is at fault here. an option for those running aokp is to go into the power saver settings and you can set your phone to go to 2g when the screen is off.
I have been having this issue since 4.0.3 on my GSM Nexus. I have tried multiple radio's and multiple kernels. I was having to change the min cpu to 700mhz. I tried FuGuMod's Kernel and it seems to have fixed my signal issues. I am able to keep the min cpu at 350mhz. If you search the thread he explains what he thought was causing the issue. Once he disabled that feature in the kernel my signal issues went away.
http://forum.xda-developers.com/showthread.php?t=1438417
I think its a mix between software and hardware issues. There is some software setting that the hardware doesnt like. But since this doesnt happen to everyone running a certain kernel and only some people there must have been a bad batch of hardware from samsung.
I think I am going to try a warranty exchange with Samsung.
For me at least, it is occurring in both 2G and 3G areas. I have tested it in both, and also in strong and weak reception areas.
Memoreks
Sent from my Galaxy Nexus using xda premium
I am a new owner of a Sprint Galaxy S3. For the first few days, it worked perfectly. But now, for the last week, call quality has been crap. I found that this issue is mostly when the mobile network selection is set to LTE/CDMA/EVDO. When set to CDMA only it's at least understandable. I rooted it so I can try to upgrade the radio. I installed the lg8 update, but that has not helped at all. Any suggestions? Has my phone developed a hardware failure?
Lee1138 said:
I am a new owner of a Sprint Galaxy S3. For the first few days, it worked perfectly. But now, for the last week, call quality has been crap. I found that this issue is mostly when the mobile network selection is set to LTE/CDMA/EVDO. When set to CDMA only it's at least understandable. I rooted it so I can try to upgrade the radio. I installed the lg8 update, but that has not helped at all. Any suggestions? Has my phone developed a hardware failure?
Click to expand...
Click to collapse
Good to hear it is not only me... and it may very well be related to the LTE/CDMA switch! I only just switched that on on Friday I believe and over the weekend all I had was folks telling me they couldn't understand me! I'll switch back and see what happens.
I'm in ATLANTA so was hoping to snag some LTE goodness but haven't yet run across any so I guess I won't miss LTE if I switch it off!
beejmeister said:
Good to hear it is not only me... and it may very well be related to the LTE/CDMA switch! I only just switched that on on Friday I believe and over the weekend all I had was folks telling me they couldn't understand me! I'll switch back and see what happens.
I'm in ATLANTA so was hoping to snag some LTE goodness but haven't yet run across any so I guess I won't miss LTE if I switch it off!
Click to expand...
Click to collapse
I think I just figured it out! I installed a CPU settings app and found that the cpu was running at about 2/3rd it's full speed. As soon as I cranked the min speed all the way up, my call quality improved dramatically.. I wish I knew how this suddenly became a problem, unless I'm just didn't notice the exact time of the call quality problem..
As I fiddle with it more, It looks like these cpu control programs are not working quite right and possibly setting the cpu speed to much lower than the menu says it is. I'm not sure how to get around this.
Anyone know what file I need to edit to set the defaults back?.. or a good free cpu control app that works properly on this device? SetCPU doesn't seem to have a free or demo version anymore.
Lee1138 said:
As I fiddle with it more, It looks like these cpu control programs are not working quite right and possibly setting the cpu speed to much lower than the menu says it is. I'm not sure how to get around this.
Anyone know what file I need to edit to set the defaults back?.. or a good free cpu control app that works properly on this device? SetCPU doesn't seem to have a free or demo version anymore.
Click to expand...
Click to collapse
Has anyone else install Freeza's boot animation CPU speed fix? Now that I'm thinking about it, this problem actually started after I installed that.
Basically, it manifested itself as, after coming back from sleep, calls would be "droppy" kind of like how they are with a really bad signal. Both sides were impossible to hear, but it would never actually drop (nevermind, absolutely full signal). But a reboot would help it until a little while later when I had to reboot.
This was on Blazer 1.7 with Freeza's fix installed. Does anyone else's situation match that? Also, does it go away permanently if the governor is set to performance?
Lee1138 said:
I am a new owner of a Sprint Galaxy S3. For the first few days, it worked perfectly. But now, for the last week, call quality has been crap. I found that this issue is mostly when the mobile network selection is set to LTE/CDMA/EVDO. When set to CDMA only it's at least understandable. I rooted it so I can try to upgrade the radio. I installed the lg8 update, but that has not helped at all. Any suggestions? Has my phone developed a hardware failure?
Click to expand...
Click to collapse
I was having the same problem and after a little digging around in the menus I found under Phone dialer/call settings/Additional Settings is "Noise Reduction". It was on by default. I turned it off and call quality is much better. I was getting choppy audio on both ends of the conversation - very similar to my experience with a fancy Motorola bluetooth headset. It was cutting out more than just noise. Don't know if this is the same problem you are having but it's worth a try. Good luck.
Ok, all of my working with it seems to be in vain. It isn't the cpu, it isn't signal, I think it's just a defective radio. Just need to have it checked out at Sprint and likely replaced. Can't have a phone that no one can understand me when they call.
Had my wife take my phone to the Sprint store for them to check it. Switching phones did not fix the problem. They say it's some kind of network problem. Their advise is to make sure the mobile network setting is set to CDMA and not use the LTE network.
I'm thinking of asking for a refund of the $10 a month they charge for 4g because if I try to use it, the phone is useless.
I've got a two part question for some issues I'd like to address while on 4G (some I've called Sprint about, others I know you guys will have the answer since I'm rooted) that I hope to resolve.
My issues with Sprint is that if I'm on 3G and looking at images via websites, pics obviously load slower, but they're always nice and crisp. I notice that when I happen to be on 4G and go look at images, suddenly they load super grainy. I spoke to someone else who is also on Sprint w/ an LTE 4G phone (not a Note II, something else) who experiences the exact same problem. I've called Sprint about it, but I get the usual run around saying they're addressing the issues, fixing towers, etc. When I first started getting 4G in my area about 3 months ago, it was BLAZING fast, connected the second I came off the freeway and stayed on strong. I realize over time that I'm sharing the same signal with others, but damn.
My issues that I'm hoping you guys can assist with is in regards to the phone staying connected to to 4G more via changing thresholds. As I id before, it was awesome. Now it's gotten to the point where I or the phone have to be near a window, or occasionally I can leave it on the top edge of my couch...but if I happen to handle the phone to answer a text messages, it'll often drop back into 3G. The problem is that I use my phone tethered to my laptop for watching TV....Top Gear, Family Guy, etc that I stream. On 4G it's great, but once it drops to 3G it turns into a buffering nightmare and some shows/sites can't handle jumping around for time frames, so lets say if I'm 15 min into a show, go into 3G and come back into 4G, the show never recovers and I've got no choice but to restart the show. I'm just curious if there's a way to change at what point/signal strength that the phone wants to swap back and forth and basically ask it to stay on 4G more often than not when I'm at home where I actually get 4G.
As for tethering, I'm a stock rooted ROM using TrevEMod tethering because the stock tethering app won't stay turned on, I'm assuming due to using the stock ROM. What I'm curious about is a way to have the phone automated in that once I plug it on, the tethering app turns itself on and then back off again once unplugged from a power cord. At one point I'd used some app where it had me enter parameters to do this, but it only worked to turn on the stock tethering app which won't work.
Bottom line is I'd like my phone to stay connected to 4G more often than not, turn on tethering when plugged in and turn it off when not.
as for the tethering, if you are running the stock deodexed rom, there is a mod you can flash to make the native hotspot work then you will be able to use Tasker or however you automate it turning on. if you are running stock odexed you could always flash stock deodexed, if you were intent enough on making it work.
here is the hotspot mod: http://forum.xda-developers.com/showthread.php?t=2232553
I truly don't know if the stock ROM is odexed or deodexed, I just did a simple rooting procedure and nothing more so I could install a tethering app. Maybe I'm just being naive, but coming from my Epic days where I rooted, ROM'd, kernal'd, OC'd, etc days where I removed tons of apps, added others, etc I never was able to get battery stats/calibration to work correctly, which in turn wrecked havoc on that phone...phone would get super laggy, bog and stumble, then I'd reset the phone and I'd go from 20% battery life to 3%, then realize why the phone was freaking out. Now that I've got this Note II, it works great, I've never felt the need to OC or anything (I wouldn't mind removing stock apps but the SDX Stock App Removal Tool doesn't work), so I'm kinda hesitant in flashing any sort of ROM for fear of reliving past experiences...right now the phone simply works great, I'd just like a few simple features. Any input to sway my decision?
i hear ya, i too like a nice stable setup with everything working. your system is probably odexed if al you did was root, but if you have a file explorer app, when you go into /system/app, you will see each .apk also has an associated .odex file. the deodexed rom has the odex part added back into the apk, but otherwise is exactly the same, no tweaks or anything, every bit as stable, and with nothing removed, but it is easier to make mods for a deodexed rom, such as the hotspot mod!
the decision is yours. it is always a bit of work to flash a rom, but this is defintiely a way to keep the stabilty and reliability, and have the hotspot working the way you want it to! the rom is here: http://forum.xda-developers.com/showthread.php?t=2241930, if you choose to go this route. this is exactly my setup, with the hotspot mod, and it runs great.
I'll read the thread, thanks for the link. Any suggestions for something that will enable the tethering app automatically based on being plugged in, and I've had no luck finding anything in regards to people changing thresholds for the 4G connectivity.
m5james said:
I'll read the thread, thanks for the link. Any suggestions for something that will enable the tethering app automatically based on being plugged in, and I've had no luck finding anything in regards to people changing thresholds for the 4G connectivity.
Click to expand...
Click to collapse
no problem. the app Tasker from the market does things like that, i think it costs a few bucks but it's well worth it. and perhaps there are others.
for the 4G thing, i don't see any setting for that. there are other people who know a lot more about network stuff than i do. there might be a dialer code menu where you can set to receive LTE only, but sorry i can't be of more help there. good luck and have fun!
Read this thread
http://forum.xda-developers.com/showthread.php?t=2407286
In HDR menu there is a LTE only mode..... beware you wont receive calls or texts so if you have google voice set up then perfect
I have tried a number of custom ROMs, Oreo and Pie based. They all have this issue where signal is mostly on zero bars, and it leads to flaky VoIP calls, and low data throughput on LTE. I have read even OOS has this flaky LTE, but it is masked to some extent.
However, I have also heard that some people only have this issue on custom ROMs and not OOS.
• Is there a way to fix the flaky LTE signal, on custom ROMs?
LTE signal used to be so much better, and reliable on Nexus 5, that I never even had to turn on WiFi.
halfbytecode said:
I have tried a number of custom ROMs, Oreo and Pie based. They all have this issue where signal is mostly on zero bars, and it leads to flaky VoIP calls, and low data throughput on LTE. I have read even OOS has this flaky LTE, but it is masked to some extent.
However, I have also heard that some people only have this issue on custom ROMs and not OOS.
• Is there a way to fix the flaky LTE signal, on custom ROMs?
LTE signal used to be so much better, and reliable on Nexus 5, that I never even had to turn on WiFi.
Click to expand...
Click to collapse
I can confirm that this really seems to affect custom roms more than Oxygen OS. For me this has affected my battery life, and i have a bit of a theory: the way android handles signal is that whatever the system reports as its signal affects what the system believes is the max data throughput (such as if your signal was really a 4G signal but you were being registered as a 3G, Android will only pull data as fast as it can believe a 3G signal can), the power it uses on the cellular antennas ( Less "signal" = more power drain). the reason i have come to think this is because i have been testing this theory on both custom roms and Oxygen OS, and in the same locations with the same kind of usage, and custom roms always seem to suffer the symptoms of a low signal, along with a lower reporting signal than Oxygen OS. This can either be due to custom rom devs using an inferior kernel than Oneplus uses, or its truly due to the signal reporting. i dont believe its the kernel, as this issue has been identical in all the custom roms i've been using (CRDroid, Pheonix, Omni, Treskmod, and even Lineage). now as for a solution....... I'm afraid we might be out of luck most people who COULD help live in higher reception areas so they don't understand how this affects those of us in lower reception ares, so they won't be much help as they don't really care. I can't really help because im in college and have two jobs and can't really afford to take the time to finally learn to develop on android (C++ takes enough time right now as it is)(and even though ive been doing android stuff for 8 years i still havent learned any lawl). and ive looked through our forums and some others and havent really found anything of help to us. If I remember correctly, it seems like Havoc OS would actually do like oxygen OS and "Lie" about the reception, but i dont think its had an update in a while. so i think the best bet is just to keep asking around and maybe someone will see this forum and have some help of some sort.
Nobodyslight said:
I can confirm that this really seems to affect custom roms more than Oxygen OS. For me this has affected my battery life, and i have a bit of a theory: the way android handles signal is that whatever the system reports as its signal affects what the system believes is the max data throughput (such as if your signal was really a 4G signal but you were being registered as a 3G, Android will only pull data as fast as it can believe a 3G signal can), the power it uses on the cellular antennas ( Less "signal" = more power drain). the reason i have come to think this is because i have been testing this theory on both custom roms and Oxygen OS, and in the same locations with the same kind of usage, and custom roms always seem to suffer the symptoms of a low signal, along with a lower reporting signal than Oxygen OS. This can either be due to custom rom devs using an inferior kernel than Oneplus uses, or its truly due to the signal reporting. i dont believe its the kernel, as this issue has been identical in all the custom roms i've been using (CRDroid, Pheonix, Omni, Treskmod, and even Lineage). now as for a solution....... I'm afraid we might be out of luck most people who COULD help live in higher reception areas so they don't understand how this affects those of us in lower reception ares, so they won't be much help as they don't really care. I can't really help because im in college and have two jobs and can't really afford to take the time to finally learn to develop on android (C++ takes enough time right now as it is)(and even though ive been doing android stuff for 8 years i still havent learned any lawl). and ive looked through our forums and some others and havent really found anything of help to us. If I remember correctly, it seems like Havoc OS would actually do like oxygen OS and "Lie" about the reception, but i dont think its had an update in a while. so i think the best bet is just to keep asking around and maybe someone will see this forum and have some help of some sort.
Click to expand...
Click to collapse
Thanks for the reply. I wonder if reporting the signal like on OOS would help.
I also have mobile data issues, like voice being muted on VoIP calls, when signal drops to 0 bars.
I hope it gets fixed in custom ROMs.
@codeworkx suggested changing the preferred network type to Global, to an user having LTE signal issues on just custom ROMs.
Looking at the network type in phone info, after dialing *#*#4636#*#*, it appears to be LTE/CDMA/UMTS auto (PRL).
Source: https://forum.xda-developers.com/showthread.php?p=78517417
halfbytecode said:
@codeworkx suggested changing the preferred network type to Global, to an user having LTE signal issues on just custom ROMs.
Looking at the network type in phone info, after dialing *#*#4636#*#*, it appears to be LTE/CDMA/UMTS auto (PRL).
Source: https://forum.xda-developers.com/showthread.php?p=78517417
Click to expand...
Click to collapse
I'll try this again and see, but before I tried this and it didn't really help. AT&T in my area is just horrible and unusable. when I went to D.C. this last summer i had better service and had none of these problems.. maybe someone will make a magisk module that can fix all this...
Nobodyslight said:
I'll try this again and see, but before I tried this and it didn't really help. AT&T in my area is just horrible and unusable. when I went to D.C. this last summer i had better service and had none of these problems.. maybe someone will make a magisk module that can fix all this...
Click to expand...
Click to collapse
After setting the preferred network type to Global, LTE signal and throughput seem to be close to what Nexus 5 used to have, in the exact same area and network provider.
Webpages also seem to load a tad faster. I will still keep an eye on the signal today.
I second this. Have been using AEX for a while now and the signal issue persists which makes me want to go back to stock OOS. I get a max of 2 bars and battery life has taken a hit with SOT of 5-6 hrs on average, before it would be between 8-9 hrs. It's a hard price to pay for all the customization but I feel I'll go back to stock so that I can have better call/signal.
I have tried @codeworkx's suggestion but that didn't help much. Hopefully there's a solution soon.
Yeah me too have that issue. At 1st I thought that the tower nearby my area is not proper. But it's the issue with custom rom
Manaljn said:
I second this. Have been using AEX for a while now and the signal issue persists which makes me want to go back to stock OOS. I get a max of 2 bars and battery life has taken a hit with SOT of 5-6 hrs on average, before it would be between 8-9 hrs. It's a hard price to pay for all the customization but I feel I'll go back to stock so that I can have better call/signal.
I have tried @codeworkx's suggestion but that didn't help much. Hopefully there's a solution soon.
Click to expand...
Click to collapse
neilrayer said:
Yeah me too have that issue. At 1st I thought that the tower nearby my area is not proper. But it's the issue with custom rom
Click to expand...
Click to collapse
What network type do you guys have? I'm on at&t, and I'm gonna try fiddling with apn settings and other stuff and see if there's anything I can figure out, I'm wondering if it's a frequency thing that custom roms struggle with.
Nobodyslight said:
What network type do you guys have? I'm on at&t, and I'm gonna try fiddling with apn settings and other stuff and see if there's anything I can figure out, I'm wondering if it's a frequency thing that custom roms struggle with.
Click to expand...
Click to collapse
I am using Jio . It's india
Nobodyslight said:
What network type do you guys have? I'm on at&t, and I'm gonna try fiddling with apn settings and other stuff and see if there's anything I can figure out, I'm wondering if it's a frequency thing that custom roms struggle with.
Click to expand...
Click to collapse
Updated to AEX 1.9. Network has improved a lot. I've currently set on Global and I'm getting LTE on Airtel India. Connectivity is on par with stock OOS. If you're on AEX, I'd recommend the update.
Manaljn said:
Updated to AEX 1.9. Network has improved a lot. I've currently set on Global and I'm getting LTE on Airtel India. Connectivity is on par with stock OOS. If you're on AEX, I'd recommend the update.
Click to expand...
Click to collapse
Thanks for pointing that out. I looked at the changelog for AEX 1.9, and stumbled upon this change:
https://gitlab.com/APOPHIS9283/frameworks_base/commit/7eee9cb50155c01f03d76f050dd956c9a16abefa
It seems to precisely deal with the signal bars. I guess it's time to request other ROM developers to include this commit in their ROMs.
halfbytecode said:
Thanks for pointing that out. I looked at the changelog for AEX 1.9, and stumbled upon this change:
https://gitlab.com/APOPHIS9283/frameworks_base/commit/7eee9cb50155c01f03d76f050dd956c9a16abefa
It seems to precisely deal with the signal bars. I guess it's time to request other ROM developers to include this commit in their ROMs.
Click to expand...
Click to collapse
Found more about this. Apparently Xiaomi phones also have similar signal issues on custom ROMs. Fix is the same as above, but there are other ways of implementing the fix.
https://piunikaweb.com/2019/01/22/x...tual-cellular-signal-strength-from-end-users/
Edit: Apparently Samsung, Google, LG, Xiaomi, OnePlus and possibly other manufacturers have this change made in stock ROMs!
Carbon ROM has a few commits related to fixing flaky LTE signal, that are not the same as ones mentioned above.
Carbon ROM may not have LTE signal issues, too. It needs to be tested though.
halfbytecode said:
Thanks for pointing that out. I looked at the changelog for AEX 1.9, and stumbled upon this change:
https://gitlab.com/APOPHIS9283/frameworks_base/commit/7eee9cb50155c01f03d76f050dd956c9a16abefa
It seems to precisely deal with the signal bars. I guess it's time to request other ROM developers to include this commit in their ROMs.
Click to expand...
Click to collapse
But this would only change visual representation of signal what about change in actual signal
I forgot about the testing menu accessed by the activity launcher (I'm using AOSiP) and I changed two options: set my radio band country (in the 3 dot menu) to America, and also changed my network type there to LTE/UMTS (PRL Auto) . The network has been slightly improved, but I may go try AEX and see if it's better there.
https://repo.xposed.info/module/me.hbc.ltemobilesignalfix
Made an xposed module for Android 9 Pie to make the LTE signal behave like on stock ROMs. Apps that optimize behaviour based on Signal Strength tend to actually work better with this. This module should work on all custom ROMs, that do not have this already enabled. (Tested working on AOSiP 9 official)
Apart from most OEMs enabling this by default on stock ROMs, some mobile carriers also enable it on their end.
halfbytecode said:
https://repo.xposed.info/module/me.hbc.ltemobilesignalfix
Made an xposed module for Android 9 Pie to make the LTE signal behave like on stock ROMs. Apps that optimize behaviour based on Signal Strength tend to actually work better with this. This module should work on all custom ROMs, that do not have this already enabled. (Tested working on AOSiP 9 official)
Apart from most OEMs enabling this by default on stock ROMs, some mobile carriers also enable it on their end.
Click to expand...
Click to collapse
Can you make it as a magisk module that works systemless ??
vipsms said:
Can you make it as a magisk module that works systemless ??
Click to expand...
Click to collapse
This cannot be accomplished using a magisk module. However, you can use this xposed module systemlessly. Install riru core and riru edxposed (yafha) from magisk manager.
Then you just need to install edxposed installer, to manage your xposed modules.
https://github.com/solohsu/XposedInstaller/releases/