[Q] sound quality vs rom/kernel - Droid Incredible Q&A, Help & Troubleshooting

Just bought a rooted dInc that was running evervolv ICS / incredikernel, and the sound quality was ranging from not great (cell calls) to terrible (grooveIP, skype, etc.) Voices sounded muffled with cell/skype and tinny/compressed with grooveIP. Note that this is on my end - receivers have told me that quality on their end was also bad, but I've never heard it & so can't describe.
After running through various combinations of settings, different wifi networks, etc. I eventually flashed back to a near-stock config (Stock+ GB), which seems to have improved the cell quality to the point where it's usable, though VOIP still sounds lousy. However, I really did like some of the features of the custom ROM (back key kills apps, battery use per-app, etc.) and ICS in general. Plus, I bought this phone primarily to use with VOIP. Which is all a long lead-up to my actual question...
Q: Is there a particular ROM/kernel that's known for high call quality - particularly with VOIP apps?
I've searched through the forums and the lists of ROMs, but not found a thread specifically focusing on this issue. As this is my first android phone, I'm not entirely sure whether call quality is a ROM thing, kernel thing, or maybe just a problem with this particular phone. So I'm hoping some knowledgeable dInc owner can enlighten me.

meeotch1 said:
Just bought a rooted dInc that was running evervolv ICS / incredikernel, and the sound quality was ranging from not great (cell calls) to terrible (grooveIP, skype, etc.) Voices sounded muffled with cell/skype and tinny/compressed with grooveIP. Note that this is on my end - receivers have told me that quality on their end was also bad, but I've never heard it & so can't describe.
After running through various combinations of settings, different wifi networks, etc. I eventually flashed back to a near-stock config (Stock+ GB), which seems to have improved the cell quality to the point where it's usable, though VOIP still sounds lousy. However, I really did like some of the features of the custom ROM (back key kills apps, battery use per-app, etc.) and ICS in general. Plus, I bought this phone primarily to use with VOIP. Which is all a long lead-up to my actual question...
Q: Is there a particular ROM/kernel that's known for high call quality - particularly with VOIP apps?
I've searched through the forums and the lists of ROMs, but not found a thread specifically focusing on this issue. As this is my first android phone, I'm not entirely sure whether call quality is a ROM thing, kernel thing, or maybe just a problem with this particular phone. So I'm hoping some knowledgeable dInc owner can enlighten me.
Click to expand...
Click to collapse
Try cm7+incredikernel.
Sent from my DROIDX using Tapatalk

After many different ROMs/kernels/radios, including CM7, I'm stumped. Cell call quality improved a bit after moving off my original evervolv ICS ROM and back to GB, but my 3G strength is still notably worse than my dumb phone, at about -85dBm in my apt. Anyway, it's usable for cell calls.
VOIP over wifi, on the other hand, still sounds pretty awful, with none of the combos I've tried having a significant difference. (Though I did find that direct grooveIP->grooveIP calls sound better than ones to non-VOIP phones.)
So it feels like a case of bad wifi performance, except I've tried several different nets, including my home, which shows 40-50 ping and 5-10Mbps consistently (from the phone).
I guess there's either something wrong with this particular phone, or maybe the dInc generally doesn't have the wifi or cpu oomph to run VOIP apps well. I wish there was some way of testing, short of buying another couple of phones to test against.

meeotch1 said:
After many different ROMs/kernels/radios, including CM7, I'm stumped. Cell call quality improved a bit after moving off my original evervolv ICS ROM and back to GB, but my 3G strength is still notably worse than my dumb phone, at about -85dBm in my apt. Anyway, it's usable for cell calls.
VOIP over wifi, on the other hand, still sounds pretty awful, with none of the combos I've tried having a significant difference. (Though I did find that direct grooveIP->grooveIP calls sound better than ones to non-VOIP phones.)
So it feels like a case of bad wifi performance, except I've tried several different nets, including my home, which shows 40-50 ping and 5-10Mbps consistently (from the phone).
I guess there's either something wrong with this particular phone, or maybe the dInc generally doesn't have the wifi or cpu oomph to run VOIP apps well. I wish there was some way of testing, short of buying another couple of phones to test against.
Click to expand...
Click to collapse
It might be the voip app not putting out high quality audio?
Sent from my ADR6300 using Tapatalk

Unfortunately, it seems to be most/all VOIP apps, at least when using them over wifi... grooveIP, talkatone, and skype all sound lousy. (And oddly, skype and google voice sound fine on the same wifi networks via my laptop.)

meeotch1 said:
Unfortunately, it seems to be most/all VOIP apps, at least when using them over wifi... grooveIP, talkatone, and skype all sound lousy. (And oddly, skype and google voice sound fine on the same wifi networks via my laptop.)
Click to expand...
Click to collapse
That's a problem with the apps then, not the phone
Sent from my ADR6300 using Tapatalk

I'm sort of drawing the opposite conclusion... The "bad sound" constants being: 1) the phone and 2) wifi on that phone, with sound quality being reasonable in all other cases.
The only test I've got left at this point is to find someone with an android-based phone, and have them make calls with the same apps, same location as me. Unfortunately, I don't know anyone who's got a dInc, so can't compare apples to apples.

meeotch1 said:
I'm sort of drawing the opposite conclusion... The "bad sound" constants being: 1) the phone and 2) wifi on that phone, with sound quality being reasonable in all other cases.
The only test I've got left at this point is to find someone with an android-based phone, and have them make calls with the same apps, same location as me. Unfortunately, I don't know anyone who's got a dInc, so can't compare apples to apples.
Click to expand...
Click to collapse
See I think this phone sounds great having used a droidx and various T-Mobile phones. And the wifi seems slightly weaker then the dx, but only slightly
Sent from my ADR6300 using Tapatalk

meeotch1 said:
After many different ROMs/kernels/radios, including CM7, I'm stumped. Cell call quality improved a bit after moving off my original evervolv ICS ROM and back to GB, but my 3G strength is still notably worse than my dumb phone, at about -85dBm in my apt. Anyway, it's usable for cell calls.
VOIP over wifi, on the other hand, still sounds pretty awful, with none of the combos I've tried having a significant difference. (Though I did find that direct grooveIP->grooveIP calls sound better than ones to non-VOIP phones.)
So it feels like a case of bad wifi performance, except I've tried several different nets, including my home, which shows 40-50 ping and 5-10Mbps consistently (from the phone).
I guess there's either something wrong with this particular phone, or maybe the dInc generally doesn't have the wifi or cpu oomph to run VOIP apps well. I wish there was some way of testing, short of buying another couple of phones to test against.
Click to expand...
Click to collapse
I just started playing around with GrooveIP recently as my parents live on a mountain and cell phone service is non-existent no matter the carrier. One of the things that I found was I had to go deep into the android wifi settings and check the "best wifi performance" option in the advanced menu. If I didn't do that, when the screen was off, voice quality became unusable. With that option checked I can talk with the screen off with no problems over wifi. Not sure about 3g/4g calls as I only use on wifi. I also used the adaptive echo canceler with post processing, and lowered the mic gain a bit. Good luck!

Try the gingerbread sense test kernel I built that should have better vopi over wifi. I also made one for aosp rooms on the smaller incredikernel thread (tiny+Chad).
Sent from my Galaxy Nexus using Tapatalk 2

Related

MOTOROLA ACTV Smartwatch

Hi,
Opening this thread to try to gather input from these who have or have been exposed to MOTO ACTV watch.
I am particularly interested in BT connectivity (in theory 4.0), notification scope and performance (does it read Whatsapp messages or only sends sender name?), battery life and all operational aspects in general.
Comparisons to I'mWatch or MetaWatch most welcome.
Thanks and regards.
I've returned mine two days ago for a number of reasons.
First, performance. The watch itself is, as far as the installed applications go, relatively performant. Running music can do a little bit of a number on the map redraws but, alas, who cares. It's a fitness tool, it's not made to run Angry Birds. GPS seems to have massive issues locking on and keeping locked, however, for my first 10k run I lost GPS about 1 mile in (clear, open, sky. I checked my phone and my reference TomTom, both had good signal) and regained it only after 3 miles or so.
But here's all the bad stuff...
The device will not, officially, work with anything but Motorola phones. Yes, you can get the apk from other sources (or download it to your Xoom as I did, then suck and push), open the archive, muck with it to remove the check for motoblur.permissions in it, and install it on your non-Moto phone, but that's suboptimal.
Battery life is abysmal. I frequently run/bike more than two hours and that's about all the watch can handle with GPS on. Some people reported 3h with GPS and no music, but since the watch sells based on the fact that it will play music according to your state (it learns what music motivates you and plays it when you break down), that's a major loss.
Unlike the ads suggest, you don't get caller names over BT. Yes, they're theoretically available, practically it's numbers. Makes all the difference when running and deciding whether to answer or not.
Force Closes are quite common (though I hear some of those are fixed in the last update), as are complete watch reboots whenever BT connects or disconnects.
I mentioned GPS but it's so bad I have to mention it again. Seriously, of 14 runs I did with the watch only one, a two-mile run, had GPS for the whole duration. Customer support recommends standing still and letting the watch catch up. Yeah, right, I am at mile five of a fifteen mile run and will just stand still for a little? Nope!
The web interface is ... errrm, well... not so good. You can't delete individual workouts or fix whatever broke when the watch lost GPS or ran out of juice. Synced data is what you get, manual entry and changed data won't work at all or only badly.
The whole system is designed for high performance athletes. And that's the people who need more than two hours of battery life.
All in all, Android lured me in, but in the end not even that could keep me. Check out supportforums.motorola.com/community/accessories/motoactv for a lot of people who just aren't happy...
Shocking indeed.
And much appreciated, Sir.
yes, even in normal handphone, Android has a lot of unnecessary processes running in the background. it really is not an easy problem: complex software is needed to really determine for itself what to go off and on, so that only the minimal software need to be running at any one time. but then increase complexity of software may impact on higher power consumption as well. looking at windows....OS complexity is much higher than linux, as it tried to provide a lot more features, but this results in more frequent bug fixes, more security holes, slower runtime performance etc etc.
my take? watch should belong to another ultra-power-sensitive hierarchy of gadget, and thus even slimmer version of Android is needed. lesser features like scheduling is needed, but just direct realtime running of the exact component needed. MMU/memory refresh should not be there, as memory refresh does take up a lot of power etc. just like uClinux version of Linux, it should be something like uCAndroid (uC can represent micro-controller?).
thanks for the info you saved me alot of money
jluster said:
I've returned mine two days ago for a number of reasons.
First, performance. The watch itself is, as far as the installed applications go, relatively performant. Running music can do a little bit of a number on the map redraws but, alas, who cares. It's a fitness tool, it's not made to run Angry Birds
Click to expand...
Click to collapse
That's weird because I saw CWM play angry birds with it on YouTube and it played fine.
Sent from my MB860 using xda premium
I like mine(but limited athletic use)
I am still within the window of being able to return mine, and switch to the wimm watch, but so far i like mine. The fact that i received it as a birthday present(so no money out of pocket) may be apart of my enthusiasm. I have only had the opportunity to use the watch for one work out. It was at 20% battery when i started(Hadnt charged it in two days) and after about an hour and a half work out i got the 10% alert. I wanted it as a device to mod, especially after i saw CMW rooted it, and Motorola scheduled a release of an api for it. I hadn't tested the GPS so i cant speak on it, but its a fun lil gadget. I will update you guys after a few more work outs.
Anyone get a chance to play with the wimm watch?

ThunderBolt--->Galaxy Nexus Multiple Issues

Greetings,
I recently upgraded to the Galaxy Nexus from my modded thundebolt running Cyanogen, both on Verizon.
This phone despite rave reviews has been a huge disappointment to me.
Battery Life This is an issue highlighted on this forum and all over the web. This phone's battery life is significantly worse than the Thunderbolt was out of the box. The latter was solved with a root and cyanogen install. I certainly hope the same can be said of the Nexus. As a medical professional, this device is simply unusable. I am currently getting less than 4 hours. The device is always running hot, as if some program is chewing through the battery, but a fix is elusive at this point. I have tried two nexus phones at this point.
Speed Another big disappointment. I have once again tried two devices, both with the quick OTA update. The device is extremely sluggish in virtually every regard. Opening programs, sliding through menus. I have actually tested my thunderbolt against the nexus on opening and running many different programs, from games, some of which are unplayable on the Nexus (may be an ICS issue) to opening simple email like gmail. The Thunderbolt is significantly faster and smoother. I admit I am a bit mistified by this one, hearing so many with rave reviews of the speed. I am not sure if this is because others are coming from much older devices or if there really is a speed issue. The Thunderbolt was clearly much faster in every regard. Again two separate
Vibrate This is a major issue for me, being in the medical profession. The device doubles as my pager, and missing pages can obviously be dangerous to my patients. I have again tested and confirmed this on two separate Nexus devices.
Voice to Text The google engine that transcribes on the fly only works with the android keyboard. Further, I have found it to be much less accurate than my thunderbolt using flex t9. I even tried the latter on the nexus, reproducing many of these problems. Not sure if this is a microphone issue on the nexus.
Games Some are simply unplayable. This may be a native problem to ICS, but my favorite game, frozen bubble plus is no longer a viable time waster.
Camera The concerns about this are well justified. It does fine in sunlight, but anything with a flash is absolutely horrid and unusable. For those who enjoy sharing a quick photo via facebook, texting, whatsapp, picasa etc, you are seriously going to be disappointed. The focus is inconsistent, and the flash over saturates the pictures. Major step behind the Thunderbolt.
There are other annoyances. Long pressing a text box allows you to change input method.
I haven't figured out if you can assign an on screen "hardware" button to a task by long pressing like you can on the thunderbolt. I have the find key on my thunderbolt assigned to the voice command. So I can long press on it and text, email, search directions etc with one simple long press. I don't see an easy way to do this on the Nexus, another major inconvenience.
In fact the only way I see to use the voice capabilities is to keep the google search bar on the home screen. I don't see the program even listed in the apps.
Perhaps many of these issues can be addressed in an upgrade, but this device's starting point is very disappointing to me, worse than the bolt.
4 hours?
I don't know what to say to any of that.
First, I easily get 18-25 hours DAILY depending on how much I use the phone. And I'd like to point on that I am a HEAVY texter (girlfriend ). Maybe you have the LTE version? I'm sure you would get ****ty battery life on LTE all the time and inside of a hospital with low reception.
Second, this has got to be the the fastest and most "fluid" device I have ever owned. I come from a dualcore Tegra 2 G2x, and the Galaxy Nexus just blows it out of the water. There is no comparison. Needless to say, I've also owned a Nexus One, Samsung Vibrant, and a G2 (The G2 with a processor most closest to your Thunderbolt).
Third, the phone vibrates just fine in my experience. If you're having troubles with it, put your incoming call ringtone on silent and raise your notification ringtone volume. That way you don't have to worry about a random call disturbing the peace.
Fourth, you must remember this is a Google Nexus device. Most games come optimized for Nexus devices. Give it time, your favorite games will be updated. In the mean time, there are plenty of other games you could play (Age of Zombies? )
Fifth, are you really going to complain about the focusing? The Galaxy Nexus has an instant shutter speed. If you want a better focus, how about you hold onto the shutter button before releasing it instantly?
I don't know about changing the input method via long press since the stock keyboard is the best I've ever used on an android device.
If you really do need a "hardware" search button, just apply a mod. If not, then just press home and it's there right at the top. Seems pretty convenient to me
I'd just like to point out to you that most of these "issues" will never be fixed as they are UPGRADES from the previous versions of android. Sorry
I am indeed an LTE user on Verizon. The battery problem seems to be real, as documented on this forum and elsewhere.
Good to hear you are doing so well, implying that there is some kind of drain issue isolated to the verizon LTE launch.
I am coming from a Thunderbolt, and while the device isn't slow, the rooted/modded bolt was significantly faster at launching gmail, yahoo mail, go sms texting, facebook etc... I suspect that this too will be fixed, but its frustrating that a more powerful device on paper is actually performing worse than an almost year old device.
Any other Thunderbolt users notice the lag on the nexus that I am referring to?
The vibrate feature is perhaps a matter of personal preference. What is fine for you, may not be nearly enough for others. I will try your suggestions though and appreciate it. I prefer to have my device in my pocket, and need to feel the vibrations as they are often emergent pages. Again, the vibration issue seems to be a real problem documented hear and elsewhere on the web.
The camera issue isn't about the speed, which is impressive. The problem is too many photos don't focus properly. The bolt took terrific pictures in comparison albeit at a slower pace. Flash photography indoors is not even passable in my opinion. Perhaps this latter problem can be or has been fixed in 3rd party camera applications. I am just not aware of any at the moment.
The gaming issue concerns me the least. I agree that this will likely be fixed with updated games quickly. I only raised it because my number one favorite game was affected!
Assigning voice capabilities to a long press is a real convenience on the bolt. I don't even have to look at the screen to make it text, email, call, find directions, do a google search, or launch an application. While you may find an alternative "easy" isn't he whole point about android the UI and being able to customize it to your hearts content. I am 100% confident that this will be addressed in some modification or add on program, but it is not easily done now.
Thanks for your kind thoughts.
I'm coming from a Thunderbolt and I noticed the slow responsiveness when calling on some apps in the Nexus right away. I guess my expectations were pretty high from the get go. I'll give it some time, The developers put a lot of work into the Tbolt to get it to perform fast, I'm sure the same will happen with the Nexus.
Sent from my Galaxy Nexus using Tapatalk
The problem is you came from a device that had development optimization for almost 10 months to a brand new development phone. If you were running a stock Thunderbolt the whole time, you would more notice the difference between the two phones. I also came from a thunderbolt running MIUI ICS and Eternity ROMS, I can tell that this phone is significantly better in every respect but the camera. But, as a phone, I don't expect the camera to be awesome. The vibrate is more elegant on this phone compared to TBs brutal shock of a vibrate, I still feel it just fine.
Your other annoyances sound more like trivial irritations rather than actual device problems, aside from the battery in which case I would say turn off LTE and it would last longer. Changing the hardware buttons wasnt a stock feature on any android phone, that was part of development. People forget that these devices take a dew days to a week for battery to run properly and once development takes off, this phone will be a monster in a month's time when everything is better optimized and features are added.
Sent from my Galaxy Nexus using XDA App
chocoyo00 said:
I'm coming from a Thunderbolt and I noticed the slow responsiveness when calling on some apps in the Nexus right away. I guess my expectations were pretty high from the get go. I'll give it some time, The developers put a lot of work into the Tbolt to get it to perform fast, I'm sure the same will happen with the Nexus.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I was really surprised because the responsiveness of this device has been one of the big selling features. I agree that this will likely be corrected with OTA updates and modded devices, but out of the box I was expecting it to be faster than my nearly one year old Thunderbolt, and was disappointed it wasn't.
mb02 said:
The problem is you came from a device that had development optimization for almost 10 months to a brand new development phone. If you were running a stock Thunderbolt the whole time, you would more notice the difference between the two phones. I also came from a thunderbolt running MIUI ICS and Eternity ROMS, I can tell that this phone is significantly better in every respect but the camera. But, as a phone, I don't expect the camera to be awesome. The vibrate is more elegant on this phone compared to TBs brutal shock of a vibrate, I still feel it just fine.
Your other annoyances sound more like trivial irritations rather than actual device problems, aside from the battery in which case I would say turn off LTE and it would last longer. Changing the hardware buttons wasnt a stock feature on any android phone, that was part of development. People forget that these devices take a dew days to a week for battery to run properly and once development takes off, this phone will be a monster in a month's time when everything is better optimized and features are added.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I agree that many of these issues can be corrected. When I bought my bolt, battery life was dreadful. After a quick root and cyanogen install, it was resolved. But out of the box, it still was a more polished experience than this device is.
These may be "trivial irritations" to you, but they are significant to me. I am looking for the most complete and polished smartphone experience. The nexus promised everything, and has not delivered as of yet in my experience. In fact there is really very little it has lived up to judging by the hype.
Clearly there are others with similar problems. I hope and expect many/most to be fixed.
This may be germane to those of us coming from an optimized Bolt, which is still a very worthy piece of hardware. I cant speak for other devices, as the only other android device I have extensive experience is the original droid incredible, which ironically is still fantastic and faster in many ways to the new Nexus in my experience.
At this point, very little of the promised features and experience have lived up to expectations. Perhaps the hype was too great, but I am hopeful this all will be fixed with software updates.
I hope people don't take this as a personal attack on the device, as I know many feel passionate about such things.
well, hardware wise the Nexus is superior to the Thunderbolt and almost as good as the Rezound. I think the main issue right now is ICS. i notice its still very buggy and lots of apps i used to use either dont support ICS or have issues running on ICS. its just a matter of time before everything is running properly.
Brand new Operating System, on a brand new phone. You have had the phone all of 4 days and expect it to be perfect already. I think you need to give it some time. You already said yourseld you modded your TB. Expect the same with this phone. And when and on a new OS you can not expect every app to work immediately. Looks like you should of waited a month to get the phone, or go back to the TB for another month and hold onto the Nexus. I currently have a TB myself.
voxigenboy said:
well, hardware wise the Nexus is superior to the Thunderbolt and almost as good as the Rezound. I think the main issue right now is ICS. i notice its still very buggy and lots of apps i used to use either dont support ICS or have issues running on ICS. its just a matter of time before everything is running properly.
Click to expand...
Click to collapse
I suspect you are correct. I was just surprised that virtually nothing that was promised on this device has been realized at launch. I am used to new phones being buggy, but virtually every aspect of this device has fallen short at launch and not consistent with the reviews.
worm- said:
Brand new Operating System, on a brand new phone. You have had the phone all of 4 days and expect it to be perfect already. I think you need to give it some time. You already said yourseld you modded your TB. Expect the same with this phone. And when and on a new OS you can not expect every app to work immediately. Looks like you should of waited a month to get the phone, or go back to the TB for another month and hold onto the Nexus. I currently have a TB myself.
Click to expand...
Click to collapse
I never said I expected it to be perfect. That is an unreasonable expectation of any device, even one that has matured and polished over time.
I do expect a flagship device to deliver on some of what was promised. This device has delivered on very few promises at launch. So far disappointed, but very hopeful it will be fixed.
makes me appreciate my hspa th even more
priapos said:
I never said I expected it to be perfect. That is an unreasonable expectation of any device, even one that has matured and polished over time.
I do expect a flagship device to deliver on some of what was promised. This device has delivered on very few promises at launch. So far disappointed, but very hopeful it will be fixed.
Click to expand...
Click to collapse
But there are bugs with any device, especially on a new OS. Look at apple, they know how to bring new devices to market, but at launch iOS 5 was plagued with bugs, most notable was the battery drain.
But what promises hasn't the Nexus kept? I'm a little curious. Because to me, the Nexus line promises to bring the best hardware and software in terms of functionality, and to me the phone doesn't fall short of any expectations.
To each his own, right?
priapos said:
I am indeed an LTE user on Verizon. The battery problem seems to be real, as documented on this forum and elsewhere.
Good to hear you are doing so well, implying that there is some kind of drain issue isolated to the verizon LTE launch.
I am coming from a Thunderbolt, and while the device isn't slow, the rooted/modded bolt was significantly faster at launching gmail, yahoo mail, go sms texting, facebook etc... I suspect that this too will be fixed, but its frustrating that a more powerful device on paper is actually performing worse than an almost year old device.
Any other Thunderbolt users notice the lag on the nexus that I am referring to?
The vibrate feature is perhaps a matter of personal preference. What is fine for you, may not be nearly enough for others. I will try your suggestions though and appreciate it. I prefer to have my device in my pocket, and need to feel the vibrations as they are often emergent pages. Again, the vibration issue seems to be a real problem documented hear and elsewhere on the web.
The camera issue isn't about the speed, which is impressive. The problem is too many photos don't focus properly. The bolt took terrific pictures in comparison albeit at a slower pace. Flash photography indoors is not even passable in my opinion. Perhaps this latter problem can be or has been fixed in 3rd party camera applications. I am just not aware of any at the moment.
The gaming issue concerns me the least. I agree that this will likely be fixed with updated games quickly. I only raised it because my number one favorite game was affected!
Assigning voice capabilities to a long press is a real convenience on the bolt. I don't even have to look at the screen to make it text, email, call, find directions, do a google search, or launch an application. While you may find an alternative "easy" isn't he whole point about android the UI and being able to customize it to your hearts content. I am 100% confident that this will be addressed in some modification or add on program, but it is not easily done now.
Thanks for your kind thoughts.
Click to expand...
Click to collapse
you cant compare a rooted device with a custom rom and kernel to one that is just rooted stock, its like comparing my old droid 1 to the galaxy nexus, your not comparing apples to apples
now maybe it could be that i came from the droid x(rooted and running cm7) but this phone is just amazing compared to my droid x and my og droid
sure i lost some features like longpress to search but i gained so many new ones(face unlock, 4g, google wallet, ect.) that i see they weigh out the loss of that feature, just my $0.02 though
battery on the other hand though is really bad, i will get about 5-6 hours at most(im a heavy user though) i just reset my battery stats for the first time though so im gonna hope that fixes it, have you though about getting the extended battery?
I put the extended battery in yesterday and made my way home from my best friend's place (a 3 hour drive). I listened to music via Poweramp over the car stereo for 2 hours and 15 minutes of the drive and then took a 45 minute phone call. Checked the battery after all that and the Gnex was at 71% battery. My guess is those of you with issues have some rogue app blowing your battery up. And comparisons with the Thunderbolt? My friend's brother in law had a loaner Thunderbolt he got from VZW whilst waiting for a new phone to come in as warranty replacement. It was running the stock ROM. The Nexus is crazily significantly faster than a stock TB. Reiterating the point of others, just wait til the devs get 10 months of development time on the Nexus - hell, give them 2 weeks and come to us and tell us how the phone is versus the TB. I had a Rezound. Great phone, but lack of S-Off (root) and dev support is why I jumped ship back to the Nexus.
I just sold my Thunderbolt, and I don't have any speed issues with the device whatsoever. It is much, much quicker than the Thunderbolt.
My launch TB had horrific battery life. I guarantee yours did too. Only after significant modding and kernel work for months was the TB acceptable with battery life. While I agree battery life stinks right now, it will get much better, and much quicker than the TB did.
One of your programs isn't compatible with ICS and it is sucking up your battery by running all the time. Try to find out what it is.
Games/apps need to be rewritten to be compatible with ICS. Give it time.
After a month or two, this phone is going to be twice as good than it is now. We already have Google Wallet available after 3 days! It is just going to get better.
Download "Camera ZOOM Fx" and your photos will be a lot more detailed and colorful
bhazard451 said:
I just sold my Thunderbolt, and I don't have any speed issues with the device whatsoever. It is much, much quicker than the Thunderbolt.
My launch TB had horrific battery life. I guarantee yours did too. Only after significant modding and kernel work for months was the TB acceptable with battery life. While I agree battery life stinks right now, it will get much better, and much quicker than the TB did.
One of your programs isn't compatible with ICS and it is sucking up your battery by running all the time. Try to find out what it is.
Games/apps need to be rewritten to be compatible with ICS. Give it time.
After a month or two, this phone is going to be twice as good than it is now. We already have Google Wallet available after 3 days! It is just going to get better.
Click to expand...
Click to collapse
I agree that the battery life on the original Bolt was terrible. The starting point of the Nexus in my opinion is many leagues worse. Today I had to recharge my device 4 times. The last time was after it drained in just over 49 minutes!!
The device has been wiped and factory default, so anything that is sucking up the juice, came with the phone. Its incomprehensible that Google would launch a device with a built in program using this much juice.
Given the comments in this thread, I just spent the past half hour testing an unrooted Bolt, bought the exam same day, from the exact same store as mine. The device was quicker than my Nexus in virtually every regard. Launching gmail, yahoo mail, browser, go sms texting, scrolling, opening settings... You get the point.
I agree the device will get better. It cant get much worse in this regard.
I will be quick to root and install cyanogen.
I am very disappointed at this time, but look forward to brighter future for the device.
45 minutes? something is wrong with your phone or you are on the edge of LTE signal
priapos said:
I am indeed an LTE user on Verizon. The battery problem seems to be real, as documented on this forum and elsewhere.
Good to hear you are doing so well, implying that there is some kind of drain issue isolated to the verizon LTE launch.
I am coming from a Thunderbolt, and while the device isn't slow, the rooted/modded bolt was significantly faster at launching gmail, yahoo mail, go sms texting, facebook etc... I suspect that this too will be fixed, but its frustrating that a more powerful device on paper is actually performing worse than an almost year old device.
Any other Thunderbolt users notice the lag on the nexus that I am referring to?
The vibrate feature is perhaps a matter of personal preference. What is fine for you, may not be nearly enough for others. I will try your suggestions though and appreciate it. I prefer to have my device in my pocket, and need to feel the vibrations as they are often emergent pages. Again, the vibration issue seems to be a real problem documented hear and elsewhere on the web.
The camera issue isn't about the speed, which is impressive. The problem is too many photos don't focus properly. The bolt took terrific pictures in comparison albeit at a slower pace. Flash photography indoors is not even passable in my opinion. Perhaps this latter problem can be or has been fixed in 3rd party camera applications. I am just not aware of any at the moment.
The gaming issue concerns me the least. I agree that this will likely be fixed with updated games quickly. I only raised it because my number one favorite game was affected!
Assigning voice capabilities to a long press is a real convenience on the bolt. I don't even have to look at the screen to make it text, email, call, find directions, do a google search, or launch an application. While you may find an alternative "easy" isn't he whole point about android the UI and being able to customize it to your hearts content. I am 100% confident that this will be addressed in some modification or add on program, but it is not easily done now.
Thanks for your kind thoughts.
Click to expand...
Click to collapse
My GN is on order and I currently have a modded Thunderbolt. I can't stand that phone at all, and I have been rooted and running Team BAMF ROM for a while. It lags horribly even with overclock, and while on 3G I barely get 7-8 hours. I hate it.
I'm hoping your problems don't translate to mine.

[Q] General "ROMing" Questions

Hey guys. I rooted my AT&T S3 recently, using the guide on GalaxyS3Root.com. However, I'm still rather unsatisfied... namely because the performance--especially battery and wifi performance--of this phone isn't that good.
So, I've done some research about ROMs, but I think the best way to do this would be to simply ask more experienced Android users about their advice. Two main questions (I'll bold them in case you don't care about my explanation):
Does anyone know a ROM that has a better "WIFI radio", and has lower power consumption than the stock? Well, no, the battery life part is mostly a no-brainer, I guess, since I'm pretty sure other ROMs do. The main thing is Wifi.
Particularly, the way the WIFI is so unreliable on my campus (GA Tech) is quite annoying. While my iPhone 3GS would seamlessly transitioning to closer wireless hubs in a building, this thing waits until the one that's like half the building away is fully out of range (it stopped being able to use the signal from it a long time ago). Someone on another forum mentioned that some ROMs may use a better WIFI radio ("the software controlling your 3G/WiFi receiver chip"). That's why I'm interested. Unfortunately I don't see any of the ROMs outright stating this information...
Battery life... well, honestly I should probably weed out more bloatware, but I have heard certain ROMs do this better. So before I go picking out weeds, I figured I would ask.
If the answer to the first question is yes, then does anyone have any guides to recommend for getting a ROM up and running easily (ie minimal hassle) and properly (ie nothing left to chance)?
Sorry if this is wall-of-text-ish, and thank you for your assistance.
WiFi is controlled by the kernel. Try anew kernel first
Sent from my A510 using Tapatalk 2
WiFi is kernel level. Try ktoonsez kernel, it has the newest WiFi drivers from Samsung. Also has tons of options to tweak your phone to optimize performance and battery life. Also if your on the stock ROM I recommend you flash a jellybean ROM immediately lol
Thanks for the replies, guys. Is installing a new kernel any more difficult than installing a ROM? Any recommended how-to's?
Also, for that ktoonsez kernel:
Will it work on my 4.0.4 phone? Also, the only thing I found was a code repository. Is there a precompiled version of that kernel? I mean, I've done plenty of C/C++ compiling here and there, but I still kinda don't wanna mess anything up and end up bricking my phone.
Thanks
Download from this thread. Make sure you download the right one (tw ICS)
http://forum.xda-developers.com/showthread.php?t=1756776
If you don't have a recovery installed download ROM manager from the market and install cwm.
Then follow the directions in that thread. General kernel flashing procedure is flash kernel, wipe cache & dalvik, fix permissions.
jefferson9 said:
Download from this thread. Make sure you download the right one (tw ICS)
http://forum.xda-developers.com/showthread.php?t=1756776
If you don't have a recovery installed download ROM manager from the market and install cwm.
Then follow the directions in that thread. General kernel flashing procedure is flash kernel, wipe cache & dalvik, fix permissions.
Click to expand...
Click to collapse
Alright, I went ahead and did it. Installation went pretty smoothly (booting into CWM was the most trouble, just took a few tries..). The device is a bit warm right now, but it may be because I'm charging it. I hope this kernel doesn't eat my battery up more because of some random bugs. I do notice it has some clocking settings, though, which is really good. Namely, being able to set the maximum clock while the screen is off sounds like a pretty nifty power management thing.
Well, I'll be trying it out more over the next few hours.
Thanks a lot for your help.
Next issue:
As for improving battery life in general, does anyone have any app suggestions (app killers, bloatware to get rid of, etc). I already killed allshare (very happily I might add...). I think I saw a list somewhere on these forums, of bloatware it's safe to get rid of, but I'm not sure which particular apps have the most effect.
xshadowinxbc said:
Alright, I went ahead and did it. Installation went pretty smoothly (booting into CWM was the most trouble, just took a few tries..). The device is a bit warm right now, but it may be because I'm charging it. I hope this kernel doesn't eat my battery up more because of some random bugs. I do notice it has some clocking settings, though, which is really good. Namely, being able to set the maximum clock while the screen is off sounds like a pretty nifty power management thing.
Well, I'll be trying it out more over the next few hours.
Thanks a lot for your help.
Next issue:
As for improving battery life in general, does anyone have any app suggestions (app killers, bloatware to get rid of, etc). I already killed allshare (very happily I might add...). I think I saw a list somewhere on these forums, of bloatware it's safe to get rid of, but I'm not sure which particular apps have the most effect.
Click to expand...
Click to collapse
Titanium backup is a good app for removing bloatware. Also check out this thread for tweaking the kernel to save battery life http://forum.xda-developers.com/showthread.php?t=1886233
xshadowinxbc said:
Alright, I went ahead and did it. Installation went pretty smoothly (booting into CWM was the most trouble, just took a few tries..). The device is a bit warm right now, but it may be because I'm charging it. I hope this kernel doesn't eat my battery up more because of some random bugs. I do notice it has some clocking settings, though, which is really good. Namely, being able to set the maximum clock while the screen is off sounds like a pretty nifty power management thing.
Well, I'll be trying it out more over the next few hours.
Thanks a lot for your help.
Next issue:
As for improving battery life in general, does anyone have any app suggestions (app killers, bloatware to get rid of, etc). I already killed allshare (very happily I might add...). I think I saw a list somewhere on these forums, of bloatware it's safe to get rid of, but I'm not sure which particular apps have the most effect.
Click to expand...
Click to collapse
Kernel's have governors and I/O schedulers that you can tweak to get better battery life. As a start since you're on KT747, I suggest Ktoonservative and noop. You can look more into those on the KT thread.
DarthDerron said:
Kernel's have governors and I/O schedulers that you can tweak to get better battery life. As a start since you're on KT747, I suggest Ktoonservative and noop. You can look more into those on the KT thread.
Click to expand...
Click to collapse
I agree with this suggestion. The largest increase in battery life happened when I changed my governor to conservative and i/o scheduler to noop.
Sent from my Nexus 7 using xda app-developers app
Hmmm.... well, that kernel didn't solve my wifi problem at all.
The battery life (when idle) went up by a tremendous amount, though, which is great. Android Kernel now hardly ever shows up in my battery monitoring app as one of the largest app drains, and that part is great. Opera seems to be a bit "heavy" on the battery lately, though... may just be Adfree.
I'm not actually sure what the wifi drivers solved. My wifi didn't really seem to perform too much different with them either way, and it certainly didn't improve the GS3's ability to keep a signal with multiple hubs around. I guess Apple is just that far ahead of Samsung when it comes to both their wifi drivers and their wifi hardware (which is sad, because I'm comparing a GS3 to a 3GS). Sigh. At least I'm graduating this semester anyway.
Does anyone have a different suggestion?
Again, thanks for all the help.
In the advanced wifi settings there is an option to ignore weak wifi signals you could try that although I havent had much luck with it, I have three wifi routers in my house to cover the whole house. Also see the below link to deal with tbe bloatware.
http://forum.xda-developers.com/showthread.php?p=27878819
xshadowinxbc said:
Hmmm.... well, that kernel didn't solve my wifi problem at all.
The battery life (when idle) went up by a tremendous amount, though, which is great. Android Kernel now hardly ever shows up in my battery monitoring app as one of the largest app drains, and that part is great. Opera seems to be a bit "heavy" on the battery lately, though... may just be Adfree.
I'm not actually sure what the wifi drivers solved. My wifi didn't really seem to perform too much different with them either way, and it certainly didn't improve the GS3's ability to keep a signal with multiple hubs around. I guess Apple is just that far ahead of Samsung when it comes to both their wifi drivers and their wifi hardware (which is sad, because I'm comparing a GS3 to a 3GS). Sigh. At least I'm graduating this semester anyway.
Does anyone have a different suggestion?
Again, thanks for all the help.
Click to expand...
Click to collapse
Exactly what problem are you having with WiFi? I believe once your phone connects to a router, it stays connected until you disable it or go out of range. I've never heard of any type of computer that keeps scanning for better signals. This would just waste battery life. There may be a 3rd party app out there to do this but I wouldn't be interested in that.
As far as improving reception, there's no software upgrade you can do to improve WiFi reception. I think the only benefit new drivers have is faster to establish connection time. Some cases (including my speck candy shell) ive noticed have interfered with signal strength slightly.
jefferson9 said:
Exactly what problem are you having with WiFi? I believe once your phone connects to a router, it stays connected until you disable it or go out of range. I've never heard of any type of computer that keeps scanning for better signals. This would just waste battery life. There may be a 3rd party app out there to do this but I wouldn't be interested in that.
Click to expand...
Click to collapse
So you say, but that seems to be what my 3GS did, and the battery life on it wasn't bad at all. For instance, I could keep Skype on while talking to my friend throughout a large building with multiple wifi hotspots without hardly any interruptions (elevator aside.. well no sometimes it even worked in there)... and it had an Otterbox case on (a fairly bulky one). Heck, sometimes it even kept Pandora going while I was walking around campus, not even inside of any buildings, and pretty far away from the nearest wifi. On the other hand, the data speeds capped out a bit faster than the GS3... but that wasn't an issue since it was still well over 1-2MB/s.
Compare this to my GS3, which can't even keep Anime Radio playing within that same building. Hell, it can't even Pandora going... which is much more bandwidth-friendly and probably even caches a full song while playing it, so you don't get interruptions during outages. Don't even think about Skype.
I guess the GS3 just has a much weaker WIFI reception, both hardware and software. I think it could be improved if the software controlling it tried to at least immediately jump to another hotspot when the signal started getting too weak.
As far as improving reception, there's no software upgrade you can do to improve WiFi reception. I think the only benefit new drivers have is faster to establish connection time. Some cases (including my speck candy shell) ive noticed have interfered with signal strength slightly.
Click to expand...
Click to collapse
Yeah, I was just in a bit of a state of denial, I guess. I paid that much money for a "future tech device" that has worse wifi than something that was released well over a year ago. It's a little pathetic... exacerbated all the more by the fact that I'm still using that minimum data plan (~200MB/month) that I was using on my iPhone. I'm not trying to be an iPhone fanboy or anything. It's just that considering the evidence, this is just how it is. I might try getting it back to Best Buy since I'm still under there insurance, and try getting a new one to see if it has better WIFI reception, but it's difficult to do full testing without a control. I'd need to find someone else on campus that has an GS3 and then compare our signals.
Also, I am using a case. It's just an Otterbox Commuter.
In the advanced wifi settings there is an option to ignore weak wifi signals you could try that although I havent had much luck with it,
Click to expand...
Click to collapse
It's worth a try. Where is this at? I can't find it.
That is interesting that you get much better performance on an old iPhone 3gs. Not really sure I've seen enough evidence to say the iPhone 3gs has better WiFi hardware than the gs3. Apple has been known to use top of the line hardware everywhere (that's why they're so expensive) so it wouldn't surprise me.
On a more productive note, why not use your mobile data?
jefferson9 said:
That is interesting that you get much better performance on an old iPhone 3gs. Not really sure I've seen enough evidence to say the iPhone 3gs has better WiFi hardware than the gs3. Apple has been known to use top of the line hardware everywhere (that's why they're so expensive) so it wouldn't surprise me.
On a more productive note, why not use your mobile data?
Click to expand...
Click to collapse
Me and my mother have about 1 GB shared between us now, and that just happened recently. Until now, I was pretty much using a 200MB/month (or was it 250... whatever) plan, like I said in my last post. 200MB/month gets raped fast, even trying to use it minimally. Daily usage is pretty much impossible with that little per month. 200/30 is about 6.7 megs maximum per day. That's about 2 songs in Pandora.
I'd try flashing another ROM. Make a nandroid and try aokp, cm10, or slimbean. Its worth a try. I haven't been on the stock ROM since July and I've never had a problem with WiFi.
Advanced wifi settings are located here
Settings...press on wifi...capacitive menu button on phone....advanced. Should be in there.

SCH-I515 Radio

I've done some research on this issue, and I'm afraid the answer is going to be: "it is what it is," but I recently acquired this phone and have noticed a decrease in cell coverage over my (*wildly awful*) LG Revolution.
For starters, 4G seems flaky at best. It has 4G coverage, but it is very spotty, unpredictable, and sometimes, even when it says 4G, I'm getting speeds equivalent to dial up (much worse than 3G). I can safely state it has significantly lower 4G coverage than my Revolution did. As for voice reception, while it has not cut out on me when I'm "above ground," it is non-existent in my basement. While this would seem to equate to a "well duh" statement, my previous Revolution was able to get a bar.
My phone is up to date with the latest updates, and is running on 4.2.2 with a baseband version FK01/FK02.
I'll say that it is a beautiful phone that was crafted fantastically as a solid Android device that would put my old phone to shame, but it seems like maybe this phone was crafted as a 4.75" tablet first, then the radios were slapped on as an after-thought? Has this been anyone else's experience? Are there fixes for these issues, or is this an inherent hardware issue?
This is my first Samsung phone on top of several Samsung tablets I've owned. While they are winning me over as an Android manufacturer, they are sliding off a cliff as a phone manufacturer so far (LG took that dive from 20,000 ft.)...
On an aside, battery life is a bit of a joke as well. I have orders in for batteries, extended batteries, etc. to fix that problem, though.
these are all issues that have been covered many times over. yes, the lte version has crappy signal pickup. mine is horrible for being in a decent size city with full 4g coverage, and 3g is even worse, a complete joke if you will. you can try flashing different radio combos to see what works for you. and battery, you hit it on the head, all you can do is get a bigger battery and try different kernel and setting combos to try and max out battery life. good luck with your phone, it's a great phone though for being over a year old now.

Razr M my favorite Android phone so far..

I current have the DroidOG, Droid X, HTC Rezound, Note 2, SG3, SG4, and iPhone5 and the Razr M is my favorite so far but giving the SG4 some time to see what its all about.. It's much too familiar, SG3/4/Note2 all pretty much have the same feel. Before the phones listed i've had many other Droids, etc.
I love everything about the M, except for it's signal.. I never drop to 3g where I live on any of my 4g devices but this one manages to drop to 3g. I guess it has to do with antenna size/length but everything else this phone is perfect (for me).
I don't expect everybody to favor smaller phones but after owning larger Android phones I feel the Android experience in a iPhone sized package is "right" for me.
I hope Moto makes similarly sized, powerful phones in the future!
-Div
Diversion said:
I current have the DroidOG, Droid X, HTC Rezound, Note 2, SG3, SG4, and iPhone5 and the Razr M is my favorite so far but giving the SG4 some time to see what its all about.. It's much too familiar, SG3/4/Note2 all pretty much have the same feel. Before the phones listed i've had many other Droids, etc.
I love everything about the M, except for it's signal.. I never drop to 3g where I live on any of my 4g devices but this one manages to drop to 3g. I guess it has to do with antenna size/length but everything else this phone is perfect (for me).
I don't expect everybody to favor smaller phones but after owning larger Android phones I feel the Android experience in a iPhone sized package is "right" for me.
I hope Moto makes similarly sized, powerful phones in the future!
-Div
Click to expand...
Click to collapse
Me too... I know Google is going to revamp Motorola to a large degree but i hope they still make small sleek versions of all of their lines like they did with the new RAZR line
Sent from my XT907 using xda app-developers app
After configurating most of my apps i'm getting severe lag when typing.. Its not registering my typing until 1 second or so afterwards.. and sometimes going in and out of various apps that are already loaded in memory is pretty sluggish and laggy. Freshly RSD'd the latest 4.1.2 build.. So i'm not sure whats going on.
The M was my first smart phone, and thus, my first Android phone. I can't say it's my favorite because I have nothing to compare it to. However, I did choose it because of its size, build quality, and battery life. At the time, there wasn't much development and if I would have chosen purely off of development, I would have went wtih Samsung. However, the Sammie phones feel "cheap" to me. After playing with the S4, though, the graphics quality is 100x better than the M, but I don't really care.
RikRong said:
The M was my first smart phone, and thus, my first Android phone. I can't say it's my favorite because I have nothing to compare it to. However, I did choose it because of its size, build quality, and battery life. At the time, there wasn't much development and if I would have chosen purely off of development, I would have went wtih Samsung. However, the Sammie phones feel "cheap" to me. After playing with the S4, though, the graphics quality is 100x better than the M, but I don't really care.
Click to expand...
Click to collapse
I suppose I could say that so far I like the RAZR M over other Android phones that I have had. To list I've had:
HTC Thunderbolt, Motorola Defy XT, DROID 2 Global, DROID X, and DROID RAZR M
I miss various features from all of them, but I think overall I prefer the one I have now being the RAZR M. I'm not sure what my next phone will be. My current contract isn't up until December 2014, unless I pay full price for my next phone.
Was my favorite phone until now because it won't boot
But I will say after using the droid incredible, it was quite a nice phone
Jason 907 said:
Was my favorite phone until now because it won't boot
But I will say after using the droid incredible, it was quite a nice phone
Click to expand...
Click to collapse
Why can't you get your RAZR M to boot? Can you get it into fastboot mode and rsdlite it back to stock? :'(
I have to deduct more points from these three glaring problems (so far):
1) Long pauses (lag) when switching apps (even after they are loaded into memory). Things like Seeder don't seem to help at all (at low, medium or agressive profiles). Sometimes I'll be trying to type on the keyboard and it pauses for so long it shoots out a long sentence i just typed out.. Very annoying. Being this is the same hardware internally on the SG3 except 1gb less ram.. The SG3 had zero lag ever. Surprised Moto hasn't figured out what the hang up is here by now.
2) Charging the phone while Hotspot Tethering is active.. Mine will not charge, it says it's charging but it's unable to keep up a charge.. the battery still drains very fast while plugged in. This is using the built-in Hotspot, not third party app. This is important to me, my work sends me on business trips often and they pay for my phone bill but I can't rely on this phone to serve me internet while I do work. My SG3/Note2 will charge to 100% while tethering without a hitch. I've tried various wall-bricks.. Ranging from 1amp to 2amp to 5watts to 10watts.. none make any difference. It feels like the phone just heats up way too much during tethering and I bet the internal charging circuit just turns off as a protection.
3) LTE signal is bad compared to every other LTE phone i've had on Verizon.. My city is well blanketed in thick 4g LTE.. About 2 bars to Max bars almost everywhere you go on any other LTE device i've used. This one is 1 bar most of the time sometimes 3 max (rare).. And it seems the battery drains pretty quickly hunting for signals based on poor antenna reception.. But when using 3G, battery life seems much better.. Luckily 3g is usually more than enough speed for me.
Diversion said:
I have to deduct more points from these three glaring problems (so far):
1) Long pauses (lag) when switching apps (even after they are loaded into memory). Things like Seeder don't seem to help at all (at low, medium or agressive profiles). Sometimes I'll be trying to type on the keyboard and it pauses for so long it shoots out a long sentence i just typed out.. Very annoying. Being this is the same hardware internally on the SG3 except 1gb less ram.. The SG3 had zero lag ever. Surprised Moto hasn't figured out what the hang up is here by now.
2) Charging the phone while Hotspot Tethering is active.. Mine will not charge, it says it's charging but it's unable to keep up a charge.. the battery still drains very fast while plugged in. This is using the built-in Hotspot, not third party app. This is important to me, my work sends me on business trips often and they pay for my phone bill but I can't rely on this phone to serve me internet while I do work. My SG3/Note2 will charge to 100% while tethering without a hitch. I've tried various wall-bricks.. Ranging from 1amp to 2amp to 5watts to 10watts.. none make any difference. It feels like the phone just heats up way too much during tethering and I bet the internal charging circuit just turns off as a protection.
3) LTE signal is bad compared to every other LTE phone i've had on Verizon.. My city is well blanketed in thick 4g LTE.. About 2 bars to Max bars almost everywhere you go on any other LTE device i've used. This one is 1 bar most of the time sometimes 3 max (rare).. And it seems the battery drains pretty quickly hunting for signals based on poor antenna reception.. But when using 3G, battery life seems much better.. Luckily 3g is usually more than enough speed for me.
Click to expand...
Click to collapse
I've also noticed that the Seeder program doesn't seem to help much. I've had lag with the keyboard too, especially waiting for it to pop up when I tap on a text field. It takes a second or even two. And the first few letters are laggy, but I'm using swiftkey. This phone does get hot when tethering, but I think I was able to charge my phone at same time.
motoroid7 said:
Why can't you get your RAZR M to boot? Can you get it into fastboot mode and rsdlite it back to stock? :'(
Click to expand...
Click to collapse
I am going to try this tonight.. hope for the best
Jason 907 said:
I am going to try this tonight.. hope for the best
Click to expand...
Click to collapse
Really hope you are able to fix it; If you didn't know, and I apologize is if you already knew this information
Power + Vol Up + Vol Down to get into Fastboot, then just use fastboot/adb binaries or rsdlite :}
Diversion said:
I have to deduct more points from these three glaring problems (so far):
1) Long pauses (lag) when switching apps (even after they are loaded into memory). Things like Seeder don't seem to help at all (at low, medium or agressive profiles). Sometimes I'll be trying to type on the keyboard and it pauses for so long it shoots out a long sentence i just typed out.. Very annoying. Being this is the same hardware internally on the SG3 except 1gb less ram.. The SG3 had zero lag ever. Surprised Moto hasn't figured out what the hang up is here by now.
2) Charging the phone while Hotspot Tethering is active.. Mine will not charge, it says it's charging but it's unable to keep up a charge.. the battery still drains very fast while plugged in. This is using the built-in Hotspot, not third party app. This is important to me, my work sends me on business trips often and they pay for my phone bill but I can't rely on this phone to serve me internet while I do work. My SG3/Note2 will charge to 100% while tethering without a hitch. I've tried various wall-bricks.. Ranging from 1amp to 2amp to 5watts to 10watts.. none make any difference. It feels like the phone just heats up way too much during tethering and I bet the internal charging circuit just turns off as a protection.
3) LTE signal is bad compared to every other LTE phone i've had on Verizon.. My city is well blanketed in thick 4g LTE.. About 2 bars to Max bars almost everywhere you go on any other LTE device i've used. This one is 1 bar most of the time sometimes 3 max (rare).. And it seems the battery drains pretty quickly hunting for signals based on poor antenna reception.. But when using 3G, battery life seems much better.. Luckily 3g is usually more than enough speed for me.
Click to expand...
Click to collapse
Yeah, moto did a crappy job on the launcher. It looks great and has good functionality, but it's laggy as crap. I'm getting no lag at all on CM 10.1, and it seems to be nicer on the battery.
The tethering situation sounds odd... I would say check your charger but it appears you've done that. I can tether and charge happily, so it seems like there's something up with the device. Doesn't make sense at all because I'm in an awful coverage area and I tether fine on 1-2 bars 3g and even 1x
Sent from my XT907 using Tapatalk 4 Beta
sloosecannon said:
Yeah, moto did a crappy job on the launcher. It looks great and has good functionality, but it's laggy as crap.
Click to expand...
Click to collapse
Is this not true with most oem launchers? I can't recall a phone I've not switched to either ADW (a few years ago) or Apex, nowdays.
I've owned a Incredible 2, Droid X2, Razr, Galaxy S3, and currently a Razr M. What drove me away from the phones before the Razr M was a mix of A) the stock software being terrible, and B) homebrew support missing or terribly buggy. Lets be honest - 3rd party roms don't live up to stock roms in terms of stability. What you may gain in customizability in roms like Cyanogen or AOKP, you lose in stability or even battery life. I'm sure many of you will disagree, but that's my opinion.
Anyway, as for the Razr M - it's one of the few phones that I think has an acceptable build quality. METAL for the casing, the only better-built hardware than that is an iPhone 4 or 5. The 'kevlar' back is a gimmick and the gorilla glass or whatever screen is standard now but I can't complain.
Hopefully if Google changes the look of Moto's phones, they'll stick with a similar build.
That being said, I do have a few issues with my M - Sometimes it wants to stay on 3G in an area I have decent (although weak) 4G service and I need to toggle airplane mode to get it on 4G. And the plastic bit around the headphone port fell out.
All I'm gonna say is sometimes I effing hate this phone and other times I'm freaking pumped about its strength. Its like that hoop-d Honda you won't admit is yours but when you are driving you feel like its a Ferrari.
I was so bummed to go from the g-nex to this when I saw the dev on it, but now I have been feeling motivated to learn to dev myself for it! I love this device through and through... It has taken the biggest beating thus far, and I have beat up some phones...
Sent from my XT907 using xda app-developers app
Coming from a Nexus family of phones.... and S2- S3, I'd have to say this phone is a piece of garbage lol...
Dual core krait like S3 but less pixels to run?? WHY IS THERE LAG?? HTC one S does not have lag and they have the same processor. Same with american HTC one X....
poor software poor software... have to stick with CM10 which gives me horrible battery life on GSM...
... oh and sometimes in orer for my phone to charge ( including wall outlet), i have to reboot the device...
very frustrating.
Time to get the asus padfone or something fun again
EDIT : Bunch of new roms past few days... lets see what we can do!
stealthj said:
Coming from a Nexus family of phones.... and S2- S3, I'd have to say this phone is a piece of garbage lol...
Dual core krait like S3 but less pixels to run?? WHY IS THERE LAG?? HTC one S does not have lag and they have the same processor. Same with american HTC one X....
poor software poor software... have to stick with CM10 which gives me horrible battery life on GSM...
... oh and sometimes in orer for my phone to charge ( including wall outlet), i have to reboot the device...
very frustrating.
Time to get the asus padfone or something fun again
EDIT : Bunch of new roms past few days... lets see what we can do!
Click to expand...
Click to collapse
Never experienced lag on stock once you replace Moto's garbage launcher. Install Nova or Apex and give it another try.
Sent from my XT907 using xda premium
Leraeniesh said:
Never experienced lag on stock once you replace Moto's garbage launcher. Install Nova or Apex and give it another try.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
I did, the lag was systemwide. including the keyboard...swype...
But its not that bad, i may have exaggerated a bit
stealthj said:
I did, the lag was systemwide. including the keyboard...swype...
But its not that bad, i may have exaggerated a bit
Click to expand...
Click to collapse
I dunno... my lag is pretty bad. I tried CM 10.1 last night, and it's stupid fast. The only problem is that for some reason my cell signal dropped significantly with CM vs Stock.
dingurt said:
I dunno... my lag is pretty bad. I tried CM 10.1 last night, and it's stupid fast. The only problem is that for some reason my cell signal dropped significantly with CM vs Stock.
Click to expand...
Click to collapse
Those are just the signal bars. The actual signal is the same.
Sent from my Nexus 7
Hmm... I'll check that again then.

Categories

Resources