I apologize now for the long explanation but feel the info is needed.
I had a replacement phone in March so I could root and after that all was good, I finally in May got frustrated with my lead bunker of a house and no cell signal so I got a Verizon Network Range Extender (Samsung). After I got it and a week of getting it working right my cell signal hasn't been the same, I know the bar graph isn't an accurate representation of the signal so I was watching the Db levels and the fact when I was in the middle of town in the open I had one or no bars and a -104 signal.
After Kaos and Conap got Froyo up and usable I tried using the ROM's but after a week the phone would be so unresponsive it would take literally 5 minutes to find a number and dial it. I would miss calls all the time and constantly would have to reboot. I was at first trying 768 on the OC but eventually stepped it down to 710. I have tried KaosFroyo V19-33 with no luck, each update I do has less and less time between flashing and when it becomes unresponsive. I have Tried CLEB 1.6-2.4 same thing. The only ROM that I can use with the best results is Plain_JaneT2 OC'd at 710.
I currently still have cell reception issues and sluggishness on most ROM's, I am on the current 4.27 radio and have formatted several times the SD card to start with a blank slate. I am not using swap or ext3 for AP2SD. I have unrooted and rerooted 2 times. This phone was pre legit 2.1 OTA.
Not sure what I did or what to do next to get it back in order
morphius2036 said:
I apologize now for the long explanation but feel the info is needed.
I had a replacement phone in March so I could root and after that all was good, I finally in May got frustrated with my lead bunker of a house and no cell signal so I got a Verizon Network Range Extender (Samsung). After I got it and a week of getting it working right my cell signal hasn't been the same, I know the bar graph isn't an accurate representation of the signal so I was watching the Db levels and the fact when I was in the middle of town in the open I had one or no bars and a -104 signal.
After Kaos and Conap got Froyo up and usable I tried using the ROM's but after a week the phone would be so unresponsive it would take literally 5 minutes to find a number and dial it. I would miss calls all the time and constantly would have to reboot. I was at first trying 768 on the OC but eventually stepped it down to 710. I have tried KaosFroyo V19-33 with no luck, each update I do has less and less time between flashing and when it becomes unresponsive. I have Tried CLEB 1.6-2.4 same thing. The only ROM that I can use with the best results is Plain_JaneT2 OC'd at 710.
I currently still have cell reception issues and sluggishness on most ROM's, I am on the current 4.27 radio and have formatted several times the SD card to start with a blank slate. I am not using swap or ext3 for AP2SD. I have unrooted and rerooted 2 times. This phone was pre legit 2.1 OTA.
Not sure what I did or what to do next to get it back in order
Click to expand...
Click to collapse
i cant attest for the network extender but i have noticed if the rom has an overclocked kernal and i use setcpu it turns into a slugg real quick especially with autokiller installed. u might just try a rom and not overclock it and and uninstall autokiller that is if you have that..
Are you using the setcpu widget? That messes things up quite a lot. The degradation in performance is enough that you'll have to pull the battery waking up, even when you're overclocking to 768mhz.
No I never use that I just go on the hopes that the OC is working but I wasn't aware that the OC Kernel and the Autokiller was an issue. May give that a try.
Usually the sluggishness is there but not terribly bad but I am lazy after I flash a new rom and don't set up my screens or apps for a couple of days so that may be the reason there is a window of time that the performace isn't teribble and tollerable but as soon as I do a SetCPU it goes out the window.
Thanks for the advice, just wish you had something for my cell signal.
I don't know about the extender. But yeah don't use the widget. What settings do you use for SetCPU? You may want to call Verizon for the extender.
Ok so day 2 of CELB 2.6 and all is good I didn't go to SetCPU and I noticed when I put the Facebook widget on the screen things got somewhat slow so I took it off. Still have some slow response in the app drawer but that may be from my screen replacement. It is a Verizon screen not a third party but don't know.
As for signal I am just going to suck it up and wait till August and get a newer phone.
Thanks for all the ideas
I would remove setcpu altogether and maybe try a different rom just to be safe.
Sent from my BLACK RAIN V2 using Tapatalk
Related
Hello everyone,
Has anybody else who updated to 4.1.57 find that their Atrix is now kinda sluggish? I don't mean all the time, but every now and then I get random stutters or sluggishness when switching between programs. A couple of times, it even screen locks for a few seconds when waking up. This has never happened to me before with the 4.1.26, where programs just run without hesitation. They either run smoothly, or FC in the process. But now, some of them just becomes jittery.
I wonder if it has something to do with Motorola's battery improvement in the update. When it got sluggish on me, I decided to go to into setcpu to see at wat speed the phone was running. I noticed that the phone was throttling severely all the way down to 216 mhz the second the phone is not being used. it fluctuates up and down but it seems to always drop down there once i dont touch the phone. I think this is causing an issue cuz there's a lot of background apps and widgets running and once you try running an active program, it takes a split second to start, and that split second causes it to stutter.
I haven't had the screen lock in a while, so that's a good thing. But it seems setcpu can't seem to force the cpu to constantly stay high, even if i put the minimum to 1000mhz, so I get those stutters every now and then.
Anybody has any suggestions on this matter? Im thinking if this persists, I might just go back to 5.1.26 until they come up with a major update. Really the only reason I updated was cuz the prompt was driving me mad.
p.s. another way I know how the cpu isnt running a constant 1ghz --- my phone isnt as hot as it used to be. it used to be so warm in my hand, my hand would turn red from holding it.
It takes very, very little time for a modern CPU to change its clock speed. Monitor your computer's CPU clock closely sometime, it almost certainly does throttling to a similar degree. I also observed similar levels of throttling via tegrastats on my Atrix prior to the update.
Personally 1.5.7 has been good for me, at least in the sense that nothing appears to be worse after.
Sent from my MB860 using XDA App
Only heard good reviews on 4.1.57. Can't wait for Bell to issue it too
lol, i dont like throttling. All my PCs n laptops run on full speed (throttling disabled) whenever they're on. I expect the same with my phone x) I just don't like any lag but I understand wat you mean. I still wanna hear what other's feel about the update.
note: I'm about to deodex the phone in a bit. Let's see how it ends
Moving stuff around in device memory is an order of magnitude slower than your CPU changing clock speed, and moving stuff between flash and device member is an order of magnitude or two slower than that. CPU throttling isn't the right place to look for this sort of issue.
As for your computers and not allowing them to throttle...enjoy the power bill I suppose. Even in overclocked scenarios modern processors work just fine with throttling enabled.
Sent from my MB860 using XDA App
Atrix 4.1.57 issues
I have had my Atrix for over a month with no issues. After the 4.1.57 update I have the following 3 issues:
1. The phone randomely reboots (never did this before the update)
2. The cell signal is much weaker; no signal in areas where it had signal before
3. Apps seems to start slower.
I called motorola technical support and asked if there is a way to un-install this update; the answer is NO, all they can come up with is a factory RESET which will not remove the update but will remove all my data and Apps.
I finally sent the phone to AT&T and got a replacement with 4.1.26 and it works fine, especially the battery life and the cell signal and no reboots so far.
Hi, I have recently come back to an SGS2 after dumping one after they first came out. The reason for me was terrible battery life, the 3G, H, H+ switching lockup issue, and poor GPS performance. At the time I think the most recent firmware was XXKE4. My original phone was originally on 3, which I de-branded and upgraded every time a newer version of firmware got released, after a couple of weeks use I noticed a duff pixel, so re-branded, took it back and swapped it for another, did the same customisation and it was still no good, I could be wrong, but I think the received signal strength was worse on the second one too. In any case the aforementioned issues still remained. In the end I got rid of it and went for a HTC sensation.
This proved, ultimately, to be a bad choice, what with all the dust issues, and an even bigger battery life problem than the SGS2, also, despite popular belief, i think the build quality of the SGS2 is better, sensation is horrible and creaky. Anyway, I ended up getting all disappointed with dual-core phones, and went back to my trusty old LG optimus one for a bit of normality. Eventually tho, I got the opportunity to own an SGS2 again, and I crumbled..
Now, I have an SGS2, I was immediately greeted with a software update, which I did, to XWKG4, still 3 branded, only mod was insecure kernel, root, reflash standard kernel. That's it.
Now I have no 3G, H, H+ switching issues, it takes its time sometimes but never gets completely stuck like it used to, GPS is better, Signal strength is actually good, no browser flash crashes, and most impressive, even set up as it was before with multiple push email, whatsapp, skype running constantly, twitter, constant syncing, wifi on all the time, gps on all the time, no battery saving at all, it's using about 4% an hour in standby. Which I think is pretty darn good. In fact, I can't find anything to complain about.
Seems to me, some of these problems could be related to individual handsets, so i'm keeping this one, and not gonna be messing with any ROM's either.
Anyone else got one that "just seems to work"?
Pink spot on camera is my only problem, playing with white balance almost solves this. I get 10 - 12hrs heavy use, 36hrs medium use and 48ish hrs light use. all with wifi on constantly, gps on, emails on push. no signal issues, no yellow or blue tint on screen. sound through headphones is great on power amp, never used stock player, no wake up lag. from reading on here we may be the lucky ones tho, either that or the other happy people don't bother posting
Btw I'm on unbranded voda UK, kf3, stock Rom without root
My wifi keeps dropping out. It'll work for 10 minutes and then stop completely yet still show bars of signal. Latest firmware i've used is KG3. I've now taken it in to be fixed.
No Probs with wifi here, seems to work just fine. Actually, just had my first issue, although nothing major, was using the built in email app, just went to reply to an email and it kept insisting that it was an unrecognized email address, wouldn't let me reply, so just binned it and gone back to using Gmail.
Had 2 phones from O2 in the UK and both have poor in call volume through the headset.
Music volume is fine. I think it uses different hardware for voice calls? Which means it might not be fixable via firmware. I'll make do tho cause everything else is smashing!
Sent from my GT-I9100 using XDA Premium App
Im starting this thread because of every battery thread I've read people NEVER seem to solve the problem unless they replace their ATRIX. Now a few questions. This is directed to any ATRIX owner in an attempt to find a solid solution.
1. Did your ATRIX only start having battery issues after upgrading to gingerbread?ATRIX or have you had issues beginning from stock froyo?
2. Has any solution suggested by anyone ever worked for you?
3. Does your ATRIX get hot and battery drains extremely fast?
4. Are you frequently connected to 4g H+?
If you answer no. To #2 and yes to #3 I suspect it may be a hardware problem...
on the battery this is what I see and find strange and this is the battery that came with the phone.
1880mah
1880/1930
Mah(min/typ)
7.0/7.1
Wh(min/typ)
Idk where to find production number so I guessed its this [GB/T 18287]
On the phone idk the specific so I took a guess too XD [SKU:65230]
if someone knows the two above please correct me but anyways I posted those because we can compare for those that have a problem and maybe pinpoint it to be a factory defect. Again I am doing this because this battery AND heating issue is aggravating and after 2 months I can't stand it anymore no fixes ever worked so help me and those with the issue out by providing information thanks.
Hello,
1-Yes
2-Not really, I have increase the battery life but not good as the stock Froyo.
3-Yes, but as I remember it get hot too on Froyo. Less or more... I don't know.
4-Always
I have buy an Andida 2200mAh battery and use it since 3 week, I will return to the stock battery tomorrow to check if there is a difference.
1- Nope, my battery has always lasted for around 8-10 hours everyday. (I play games and browse the internet everyday).
2-Never had any battery problem so....
3-Not at all. My Atrix has always been cool.
4. for about 4-5 hours a day (usually i am on wifi but wifi or not.....i have the same battery life).
It could be a ROM problem that you are having, maybe doing a clean install of a ROM could help you(do a complete wipe before installing the ROM). Are you using faux 123's kernel? It under-clocks your Atrix to as low as 216 GHz when your handset is idle but overclocks it to 1.1 GHz when it use. You could download setcpu to under-clock it for better battery saving and this will make your phone less hot.
You can and should also download a battery app from the market and see what your battery temp is like compared to other users. If it's a hardware issue indeed, you better return your Atrix and get a new one asap as it could cause you harm in the future.
Jibraldor said:
1- Nope, my battery has always lasted for around 8-10 hours everyday. (I play games and browse the internet everyday).
2-Never had any battery problem so....
3-Not at all. My Atrix has always been cool.
4. for about 4-5 hours a day (usually i am on wifi but wifi or not.....i have the same battery life).
It could be a ROM problem that you are having, maybe doing a clean install of a ROM could help you(do a complete wipe before installing the ROM). Are you using faux 123's kernel? It under-clocks your Atrix to as low as 216 GHz when your handset is idle but overclocks it to 1.1 GHz when it use. You could download setcpu to under-clock it for better battery saving and this will make your phone less hot.
You can and should also download a battery app from the market and see what your battery temp is like compared to other users. If it's a hardware issue indeed, you better return your Atrix and get a new one asap as it could cause you harm in the future.
Click to expand...
Click to collapse
That's just it with everything stock gingerbread my friends ATRIX doesn't heat up as hot and eat through batteries like a fat guy an a dozen doughnuts in one sitting. We both had stock when I tried this his phone easily outlasts mine both on 4g and a factory reset I tested this when he asked me to root his phone I was gunna kill its bat and charge it to root and install unlock etc. And to my surprise holy sh#t his battery life WAY outlasted mine, AND HIS DEVICE IS ONE.MONTH OLDER i've had this ATRIX for 2 months now so its none of whatever everyone is saying about battery caliBS its a firm suspicion on a hardware flaw, the sooner people can find it the sooner Motorola can replace defective handsets, ridiculous, two stock gingerbread motorolas with 100% stock and mine only lasts about had as
long as my friends own who gets battery results everyone brags about.
i own 3 atrixes ive had an atrix since launch day had its issues at first but one thing that was never a problem was the battery it was always amazing lasted 2 days sometimes well since the offical ota uPdate i updated only one that way its my main phone and right away i noticed the heat coming from the metal clip holding the sd card then next i noticed the batt life was losing 10 every 20 mins or so. since i have rooted it just so i could try n use tb to freeze all the bloatware and still nothing then i tryed just bout every other method on this forum so i didnt wanna lose my warrenty on that 1 so i didnt unlock it so i took my other atrix with a slightly cracked screen it was running on 4.1.26 so i rooted it unlocked it and charged too 100 then flashed to alien v3 so wen it was done it upgraded to gb and right away i noticed the heat from it just like my other one and battery life was losing 10% every 20 mins just like my other one i have also tryed everything on this forum im lost now dnt no wat to do somebody please help also as upset i am about this happing im very relieved to c im not the only person with this issue
So, I have one of the first Vibrants to hit the store. I'm running Neobuddy ICS Passion V8. Before the *****ing begins I want to say that I love this rom.
I followed the install instructions to a "T".
I used antutu cpu master to overclock to 1.3 because I read that other people were doing it and didn't see any complaints. When my phone booted to the point where the message that cpu master had superuser privileges came up, it froze and the display changed colors getting lighter and washed out looking. That scared the crap out of me and I thought I had just cooked my cpu. I pulled the battery and rebooted then tried to open the app and change the settings before it froze and failed, rebooting 6 times, battery pull each time. I finally relented and did a factory reset. Previous to this adventure I had it clocked at 1Ghz max and 100 min and was experiencing no lag. I just got greedy. I only changed it at all because I was getting 16 hours of battery life and thought I could trade some battery for speed. I have it running at 1.2 now and it's fine. So this is not so much a question but an answer to anyone who might be asking themselves if they should overclock to 1.3.
Bugs
mute/unmute necessary for incoming call audio
automatic brightness not responsive
complaints
contacts app doesn't match the rest of the theme
no text button next to phone button on contact
no long press functionality on contact
When it comes to Vibrants, all our phones are different. Some users will be able to run at 1.3 from now until our Zombie overlords take over and we're forced into indentured servitude. Others, like you and I will be lucky to run a mild OC without freezes.
I used to oc to 1.6 ghz on cm7
sent from the xda app on my android smartphone.
What he said!
younix258 said:
I used to oc to 1.6 ghz on cm7
sent from the xda app on my android smartphone.
Click to expand...
Click to collapse
My first Vibrant T959, manufactured prior to Oct 2010, used to fly, and overclock like there wasn't any tomorrow, and would flash anything! Was the most cooperative phone I ever had! Wish my wife was like that. LOL
Then I unfortunately got into a true HardBrick with it, and stupidly, instead of JTAGing it, got T-Mobile to exchange it, for a same model, but with a manufacturing date on it of 8-2011!
And this replacement phone, hasn't even ever performed as well as the old one, despite how I set it up, And at first it was stuburn as hell to get it to cooperate with flashing, until I unlocked it, and it calmed down alot, even though that makes no sense at all, but nun the less, it is what it is!
Point is, that each week, month or quarter, the phones aren't consistent in manufacturing qualities or how they run and perform, or the components they use. I had a Thoroughbred in the beginning, and now I how a plow horse, yes she still works well, but needs alot of coaxing, I had to re-do the GPS contacts right so there was firm pressure, and the SW flashes were a ***** in the beginning!
But I believe when this phone first came out, there was better quality of manufacturing and they used the same consistent components, until they shifted their focus on other models to push onto the market!
So again, what Billy Bobs got going with his, Isn't what it ll be with yours!!
Edit: Updated my radios, still having issues. More info in a thread below.
Hey all,
I recently started running leNoob CM9 mod, and I've noticed that my connection has bottomed out a bit. I normally would have 4-5 bars with little issue, now I'm lucky to have 1 or 2. I dropped a call earlier today, and I haven't had that happen in literal years.
Poking around I noticed there were radio versions better than what I'm currently using: (1.22.10.0421r, 1.22.10.0424r) but I'm completely unsure whether that's the problem here, or how to update them if it is.
I'm S-OFF, if that helps the solutions any.
Thanks for your time!
See the firmware thread in the dev section, you can update just your firmware/radios/etc and not have to run a RUU since you're s-off.
Shadowalker97 said:
Hey all,
I recently started running leNoob CM9 mod, and I've noticed that my connection has bottomed out a bit. I normally would have 4-5 bars with little issue, now I'm lucky to have 1 or 2. I dropped a call earlier today, and I haven't had that happen in literal years.
Poking around I noticed there were radio versions better than what I'm currently using: (1.22.10.0421r, 1.22.10.0424r) but I'm completely unsure whether that's the problem here, or how to update them if it is.
I'm S-OFF, if that helps the solutions any.
Thanks for your time!
Click to expand...
Click to collapse
Yes, you can flash the hboot/radio combo by superchilpil, then flash a hacked hboot. Apophis has a thread with hex edited hboots.
Sent from my HTC Rezound using xda app-developers app
wlmeng11 said:
Yes, you can flash the hboot/radio combo by superchilpil, then flash a hacked hboot. Apophis has a thread with hex edited hboots.
Sent from my HTC Rezound using xda app-developers app
Click to expand...
Click to collapse
I was going to make another thread for this, but hey, I saw this one I made a few days ago and it came in handy.
Since the last time I posted I did the firmware upgrade to the 2.xx radios, but that sadly did not help my issues any. My data connection will randomly drop in any situation; indoors, outdoors, whatever. I can flip my phone to airplane mode and back to restore the data connection, and it usually instantly hits 4-5 bar 4G. Unfortunately, not long after that it'll drop to 1 bar and sometimes stabilize back up to 4-5 and stay there for awhile.
Other times, it'll drop to 3G, 1x, or turn off altogether. 95% of the time it will then just stay off until I reboot the phone or hit airplane mode. The rest of the time it'll come back into 3G or more commonly 1x and stay there until it repeats the above drop process.
I've had this problem on all of the CM9 mods I've tried (currently running Rage 1.2). I've tried various network modes but I've had the greatest success of getting any signal on the LTE/CDMA/EvDo/GSM/WCDMA setting; the LTE or CDMA / LTE only ever gets 1 bar ever, and never improves.
Before CM9 on Stock ICS I had 4-5 bars anywhere in my house, and even at work (the center of a very large building) I'd still have 2-3 bars and rock solid data connection. I have not yet tried going back to Stock to see if that fixes my issues, but I'm leaning that way unless anyone has some better options here.
Thanks for your time!
Shadowalker97 said:
I was going to make another thread for this, but hey, I saw this one I made a few days ago and it came in handy.
Since the last time I posted I did the firmware upgrade to the 2.xx radios, but that sadly did not help my issues any. My data connection will randomly drop in any situation; indoors, outdoors, whatever. I can flip my phone to airplane mode and back to restore the data connection, and it usually instantly hits 4-5 bar 4G. Unfortunately, not long after that it'll drop to 1 bar and sometimes stabilize back up to 4-5 and stay there for awhile.
Other times, it'll drop to 3G, 1x, or turn off altogether. 95% of the time it will then just stay off until I reboot the phone or hit airplane mode. The rest of the time it'll come back into 3G or more commonly 1x and stay there until it repeats the above drop process.
I've had this problem on all of the CM9 mods I've tried (currently running Rage 1.2). I've tried various network modes but I've had the greatest success of getting any signal on the LTE/CDMA/EvDo/GSM/WCDMA setting; the LTE or CDMA / LTE only ever gets 1 bar ever, and never improves.
Before CM9 on Stock ICS I had 4-5 bars anywhere in my house, and even at work (the center of a very large building) I'd still have 2-3 bars and rock solid data connection. I have not yet tried going back to Stock to see if that fixes my issues, but I'm leaning that way unless anyone has some better options here.
Thanks for your time!
Click to expand...
Click to collapse
I've also been seeing the exact same issue with my signal but since flashing the Global RUU and Rage. Previously I was on older radios and NeoMax and had high performance on the signals and battery life. Battery life has also dropped significantly since the Global RUU and Rage. :/
neowisdom1031 said:
I've also been seeing the exact same issue with my signal but since flashing the Global RUU and Rage. Previously I was on older radios and NeoMax and had high performance on the signals and battery life. Battery life has also dropped significantly since the Global RUU and Rage. :/
Click to expand...
Click to collapse
In Rage 1.2 at least, my screen-off battery life is almost bulletproof. 8 hours not on the charger and it only lost 3%. Screen-on time though is almost exactly the same as Stock, and that includes going to the Wheatley governor, sio, underclocking the CPU and cranking the screen brightness way down.
As far as the radio issue goes, somewhere in the Rage thread Neo mentioned that radios on AOSP roms atm are hit and miss; some people have no problems, some people have constant problems. Currently there's really nothing they can do about it IIRC, and we'll basically just have to wait until someone can pin down the problem. Either that or go back to a Sense based rom, to which I say, phooey!
Try flashing a ruu then doing a factory reset in hboot after before restoring recovery. Worked for me
sent from my rezound running rage
EFF that that. Don't ever do anything that touches hboot.
from my flying AOKP'd Evo LTE and xda premium
The
scottspa74 said:
EFF that that. Don't ever do anything that touches hboot.
from my flying AOKP'd Evo LTE and xda premium
Click to expand...
Click to collapse
Factory reset only wipes data....
And an ruu likely won't flash if it is corrupted.
Just check md5 anyway, as always.
Sent from my ADR6425LVW using xda app-developers app