I have a Telus SGH-T959D Samsung Galaxy Fascinate, and I recently flashed it from stock Gingerbread to SlimICS, using Semophore 1.3 kernel. Phone was working about 95% stable (had to flash a modem, had no data/cell), but battery life was fairly short. I decided to try out using Glitch v14 kernel instead as it seemed to be designed for this specific model of phone (well, the release under the link for this phone). I ran a kernel cleaning script, then loaded Glitch. Seemed to work flawlessly, a bit faster with slightly better battery life. I then started playing around with the ROMs built in power saving which allows for adjusting the data settings while the screen is off (similar to juice defender, just built into the rom). Initially it worked fine, but after about a day I was noticing that when I woke my phone there was no cell reception. I went into the phone Usage Stats (*#*#4636#*#*) and under Phone Info I noticed the 'Set preferred Network type' was set to 'GSM Only'. As far as I know, in Canada, the typical network type is WCDMA, so I set it back to that, and cycled the radio on/off. I can get it back for a while sometimes when I do this, however the setting doesn't seem to save at all and when I put the phone to sleep it typically doesn't wake up with signal. I then have to repeat the process.
Is there somewhere that these settings are being stored in a file on the phone that can be text edited and saved? Maybe write protected? Or is there some other kind of fix that anyone might be able to help me with?
Thanks!
Edit: I did disable the power saving feature in the ROM, but it didn't make a difference.
Related
Hey guys-
Just upgraded to the FR008 Liberated and I dig everything about it but one thing. The battery life was immediately radically reduced from what I was getting with Eclair, and after turning off push and doing everything else to preserve battery life, it seems clear now that the problem is that it is searching for wifi hotspots everywhere.
The Y5 "Battery Saver" utility worked brilliantly on Eclair to turn off the wifi unless I was in a location where I used wifi, and then remembered if I manually turned on wifi in a certain location. I bet this tool increased my battery life by 50% on Eclair. But it totally doesn't work at all on Froyo.
Is there any way to get equivalent functionality from Froyo? Or does anyone know of an update to Y5 that will fix it with Froyo? It doesn't crash, it just doesn't do anything on Froyo.
I tried searching for this but it won't match "Y5" since the word is too short.
I've tried the various things and they all lag the hell out of my phone. And yup, the battery will drain terribly, no one believes it's a problem though, everyone seems to cite "check your apps" and don't realize that people aren't dumb and that the ROM drains battery.
the ROM doesn't drain the battery, but constantly searching for wifi hotspots does. Y5 solved that problem by turning on wifi only when you are in a location where you have configured it to use wifi.
As an example, when I go for a 2-hour bike ride with my phone, it drains the battery about 60% during that two hours, just because I happen to ride through neighborhoods where there are a ton of wifi networks (people's home networks). With Y5 working, it just stopped looking for wifi once I left my house and it only went down about 5-10% during that same 2 hour period.
I'm not sure about liberated, but on cm6 froyo if you go to settings> wireless & networks> wi-fi settings, and then press your menu button three is an advanced option. From in there you can set your wifi sleep policy to disconnect wifi while the screen is off. The phone shouldn't search for a wifi connection when the screen is off in this mode.
Sent from my cm6.1 Aria using XDA App
I suppose that'll help a little bit, but won't help much if the screen is on... like I am using the phone (say, in the car, especially while using navigation)...
Still would be nice if Y5 worked. It was a brilliantly simple solution. Not exactly in the mood to pay $10 for an app to do this but I might have to if it gets too frustrating.
check out Settings Profiles Lite - limited to one rule in the free version and should be able to do what you want.
T
looks like that MIGHT do it, but what a pain to set up for something so simple.
THe wifi sleep thing won't help me, mostly because when wifi goes off and on the network seems to be a bit flaky.
At the moment the only thing that'll work is manually disabling/enabling wifi. However, the widget seems to turn it off only to have it come back on.
sorry to bump, but wondering, does anyone else has a suggestion or a way to get Y5 to work in Froyo?
Hello XDA, I have only just registered here but I have been an avid reader of the Desire S forums for a year ever since I got my phone. My phone has been playing up for some time and I've not let it bother me too much but now it's getting quite annoying. It is an unbranded Desire S btw. I have searched but haven't found anyone complaining of the same problem.
The problem is as such: I first noticed in my house the phone seems to lose signal quite easily, fair enough it's a big house, lots of walls, I can understand that - moving to another room usually resolves the issue. However, what's more concerning is I've noticed it drop from fine to nothing in the same place. Even stranger still, if there is an incoming call and I go to pick up the handset, 9 times out of 10 it will lose all signal. Now my gf thinks I keep hanging up on her...
EDIT after further testing, i have think I have found the root of the problem... If I turn the screen on (call or no call) after two seconds or less it will lose all signal whether I leave it at the lock screen or open it. I suspect the problem may be something to do with the kernel governor. I would be grateful if anyone has any insight into this rather frustrating problem
I tried flashing the latest radio (below) but this has not solved my issue.
For reference, I am running the following:
ROM: IceColdSandwich v8
HBOOT: 0.98.2000 ENG S-OFF
RADIO: 20.71.30.0833U_3831.17.00.16_M
NETWORK: ORANGE
errr, i dunno if it works for you but whenever i at home i switch my network to use only 2g as it is much stronger and i barely get/no 3g signal where i stay, but if i am out i switch that off to get 3g signal. give it a try.
hope it helps :-/
Thanks for your suggestion, I will try it for a while and see how things turn out. I have set in the Mobile Networks settings menu to use 2G only and also for my 'Home' profile in Tasker I have included change mobile data to 2G only.
How did you get on with this. I have the exact same issue with mine.
As well as the above, I have also turned off the power saver mode in the ROM Control menu. It seems to be running fine so far. I haven't tested each option individually yet to narrow down the solution but at least it's working.
I personally suspect the problem is to do with the power saver menu because I had enabled switch to 2G on screen off, so whenever I would turn the screen on it would restart the radio and switch to 3G.
Okay, so I'm sure plenty of you have seen the news about how the dormant LTE radio on the Nexus 4 can be turned on to work with certain frequencies by using the *#*#4636#*#* command.
This command is new to me and so I figured I'd try it out on my Nexus S to see what it could do. Got to it easy enough and switched around the network types for a minute or two. Then when I satisfied my curiosity I figured I'd just change the network type back to the default "WCDMA preferred" and go on about my day.
Wrong.
My phone is now stuck on EDGE. I have turned it on and off, toggled airplane mode, toggled data, pulled the battery out for more than 10 minutes (I know it's very excessive) turned the phone off for a couple of hours, made sure that in the phone's Settings that "Use only 2G networks" is NOT checked, all to no avail.
On the 17th, when I did a speedtest on my phone, my download speed was 6183 kbps. Today, its around 167-180 kbps. Consistently.
I have made no other changes to the phone. And just to make sure that it isn't a Rogers network thing and that it is indeed my phone, I put my SIM card in my old HTC Dream. It got 3G just fine. And its download speed was a few mbps as well (about 2mbps).
I'm currently using CM 10.0.0 and am using the same radio I have been using for months with no problems (I9020XXKB3).
I honestly thought my little experiment would be as harmless as using Android's "Use only 2G networks."
Oh, as it's been quite a few hours, I've done my fair of research and found that people who had this problem somehow lost their IMEI. Mine is perfectly (especially since I haven't made any changes to my phone). It's value in about phone matches the IMEI written under my battery.
I hope I've been thorough enough. I have tried everything I could think of and done my Googling.
Anyone have any ideas on what else I can try?
179 kbps download speed is really painful ...
Put the code back in, and change the type back from wcdma back to whatever it was, this should fix your problem because WCDMA uses different frequencies for anything above edge. Frequencies that rogers does not transmit in. So changing it back will allow you to use 3g/H again
Sent from my awesome Nexus S
Default setting was "WCDMA preferred" and that's what I've left it at.
Why not factory reset?
you can try a reset, flashing a new rom, or if you're feeling particularly crazy, try using the different settings (other than wcdma), and see if it works.
I've tried all the other settings. And I really don't want to resort to a factory reset even with a nandroid backup.
Surely, there must be a straightforward fix to this.
Edit: Okay, problem solved.
Instead of changing the "Set preferred network type:", I pressed menu, chose "select radio band" and randomly selected "AUS2 Band."
It worked! Don't ask me how or why as I live in Canada, but I don't care! I never even touched this menu before. So strange ...
Edit 2: Umm... I can't find the mark "solved" option.
Sorry if this has been mentioned before. I did extensive searching without finding anything before posting.
I have been having some very strange data connection issues with my Verizon S3 running BoneStock v3.3 (awesome rom BTW, much thanks to andybones and all contributers) over the past few days. Starting a few days back, my signal strength and transfer rates while at work were much lower than normal. While investigating this, I found myself exploring the settings menus (About Phone > Status and More settings > Mobile Networks) to investigate the signal strength more often than normal (and I believe it had been the first time I had ever been to the "Mobile Networks" view).
This morning, I noticed that I had a 3g connection only at my house (this is unusual as I normally have a very strong 4g connection at home and a pretty decent one at work). Toggling in and out of airplane mode, or rebooting the phone would result in a 4g connection for about 1-2 minutes or so before it would again drop back to 3g. Using the Speedtest app, I would get about 0.5Mbps or so down, and the upstream test would not even finish before showing "Network Communication Issues" and dropping back to 3g. Additionally, my phone has been running really hot and the battery has been draining much faster than usual. Meanwhile, I had ruled out a regional network issue by testing my wife's iPhone 5, which was maintaining a solid 4g connection while mine was dropping.
While Googling for this issue, I ran across lots of articles/discussions referencing the bad OTA update Verizon sent out back in June. It struck me how perfectly the typical list of symptoms for that update matched what I was seeing. However I couldn't see why my phone would be having such similar issues, as I never received that OTA update before flashing BoneStock, and have had weeks on BoneStock with no problems at all.
Just for kicks, I switched the "More settings > Mobile Networks > Network Mode" to "Global", then switched it back to "CDMA/LTE/EVDO", then rebooted the device, and this has apparently fixed my issue!
To be absolutely clear... the current setting for "Network Mode" was already set to "CDMA/LTE/EVDO" when I checked the setting. I merely switched it, then switched it back. That was 2 hours ago, and my connection has been solid as a rock since then and the phone temperature and battery life has gone back to normal.
Doing more research, I saw that apparently the bad Verizon OTA update configured "Network Mode" to "Global" by default, and that many had fixed their connection issues by switching this to "CDMA/LTE/EVDO". Sounds very similar to my problem, except my UI was not showing that it was currently set to Global.
So, hooray that it's working, but I'm not sure what I did or how it was broken in the first place. My working theory is that the phone's Network Mode was actually set to Global somehow through some other mechanism but the UI was not displaying the setting properly, and by switching it and switching it back I overwrote that setting.
Does this ring a bell for anyone? I'd love to figure out what exactly happened, and hopefully prevent someone else from going through the hair pulling that I went through. Thanks in advance!
Hi,
my phone lately shows an high battery drain, random reboots and signal losses.
Aside from supersu and adaway everything is stock. last-kmsg shows "modem_err"
A few days ago I updated my phone from MMB29V to MOB30H, right after this I went on holiday. (left country)
While being there everything worked fine.
But right after I comeback home the phone started to act strange (see title).
Anyone an idea what could cause the behaviour?
Maybe the update? And I didn't noticed it in holiday because of my disabled data connection?
I tried:
a full wipe, reflash of stock image
flash of old radio
looked out for wake locks (there are non)
using phone without apps (only stock)
Might flashing old bootloader/kernel help?
Maybe interesting:
My provider (Klarmobil (T-Mobile DE third-party)) tends to switch my network mode between 3G and HSPA,
from what I heard and see this depends on my data usage. (HSPA while surfing, 3G while idling). I have the "feeling"
it disconnects when it tries to switch.
Thanks for your help!
Edit:
Added another set of logfiles, showing a "signal-loss", it got so far to ask for my pin again.
Sadly errors still keep happening. I tried the march build and also a custom kernel, no change :crying: