After following the various video/text guides to install cm7 alpha 2.1 on the TouchPad, I am getting a weird error and non-responsive device.
I have installed cm7 on other TouchPads and had no problem. On this one it re-boots to a screen which says, "Please release keys...". There is no combination of keys which fixes this. Only thing which has worked is to Doctor it.
The only thing different on this TP is that it is the ATT 4G version, which uses a different ROM/Doctor.
I've been searching various forums for 3 days and haven't seen anyone else with this problem.
amenditman said:
...The only thing different on this TP is that it is the ATT 4G version, which uses a different ROM/Doctor.
I've been searching various forums for 3 days and haven't seen anyone else with this problem.
Click to expand...
Click to collapse
Really?? I'm shocked! The search function must be broken, I've read at least 20 or 30 threads on this problem...
Considering they're as common as dirt, the Cyanogen touchpad team certainly must had access to that particular model and I have no doubt ensuring the compatibility & functionality of the alpha on that particular model of hardware was their absolute top priority!
I honestly can't imagine what must have precipitated this unforeseen calamity! Fear not! I'm sure the greatest minds on this forum are feverishly working, day & night, without food or bathroom breaks, to determine the root of this dysfunction using the spare ATT 4G Touchpads they had sitting around, relegated to propping doors open, leveling wobbly tables, etc...
over in the rootz forum for CM, apparently, this is a known issue for the 4G models, copmatibility is not yet available, but it is reported on the bug list so im sure it will be fixed, but as usual, no eta's!
Solidus_n313 said:
over in the rootz forum for CM, apparently, this is a known issue for the 4G models, copmatibility is not yet available, but it is reported on the bug list so im sure it will be fixed, but as usual, no eta's!
Click to expand...
Click to collapse
Thanks, I didn't see that in my internet searches.
Could you point me to the bug in the list? I can't seem to find it or at least I don't want to open a duplicate one.
its issue #398
http://code.google.com/p/cmtouchpad/issues/list?num=100&start=100
link might get removed, but its the open issues list, 2nd page (was apparently reported today, was it you? ;P)
also, i know dalingrin adresses the issue in the thread, but may be something on the back burner for future release and not requested on bug list per se
Related
Hi hkwildboy,
Great appreciation to hkwildboy discovering such an solution for quick GPS locking ........ & here is a CAB who find difficulty in editing Reg edit......
Mod's just for an awareness among all members i created new thread as this is a most essential part (GPS locking) most people complain of......
As per the feed back from senior's i came to know that the cab i attached was not working so please forgive me ...this thread will be closed.
Is the cab uninstallable?
aadadams said:
Is the cab uninstallable?
Click to expand...
Click to collapse
Yes it is uninstallable......
I'm trying it out on AT&T Fuze with Shep's 3g. I'm indoors and cannot get a fix with the standard setup. Outdoors I usually get a fix within a minute or so. I will report if this improves my experience later this evening.
Thank you for sharing this.
no feed bscks
With admitted limited use, I would tend to confirm reduced lag. I was not able to get locks indoors at home or at work either with or without the cab installed so no improvement there. The lag reduction alone makes the cab worthy of install however, as I must also admit to seeing no ill/adverse effects from the install. Thanks for the heads up.
aadadams said:
With admitted limited use, I would tend to confirm reduced lag. I was not able to get locks indoors at home or at work either with or without the cab installed so no improvement there. The lag reduction alone makes the cab worthy of install however, as I must also admit to seeing no ill/adverse effects from the install. Thanks for the heads up.
Click to expand...
Click to collapse
the cab does only help in speed lock of gps , would not help at places where you are not exposed to open space to get sat signals also depends on radio as well, i am residing at place where i do not get a proper signal...can't expect gps to work.
Does it also reduce lag or was that my imagination? I didn't think it could do anything for signal, but I know many woould like to see an answer to that question. Thanks again for making us aware.
Well I hate to burst anyone's bubble, but you do realize that both 5.08 and the new 5.10 Raphael drivers have already addressed the lock-on/aGPS issues, right ????
All you need is a newer radio, and those new drivers. Any ROM here on XDA has those drivers implemented by now.
This file/reg tweaks are really only useful if you're still running the stock ROM. In which case, how much use are you REALLY getting out of XDA ????
In any case, this fix is for stock ROM's. if you're running NATF, or Energy, or ROMeo's, or Da_G's custom ROMS, the fix for this has already been done, on the HTC side.
I'm running 6.5, and since aGPS is actually working, I'm getting locks in under 15 secs, in under 5 if I'm already connected to the internet.
mexiken said:
This file/reg tweaks are really only useful if you're still running the stock ROM. In which case, how much use are you REALLY getting out of XDA ????
Click to expand...
Click to collapse
I don't want to get into any theological debate over the good and evil of it, but there's a lot of people who, for various reasons, are stuck using the stock roms or they are too fearful of flashing.
Just an example, a buddy of mine works for AT&T. One of AT&T's policies (like every other major carrier) is to hand out different handsets to the employees so that they can become familiar with them. Next month he's supposed to sample the Fuze. These types of fixes will actually be pretty useful to him for the purpose of making the fuze realistically functional.
speed_pour said:
I don't want to get into any theological debate over the good and evil of it, but there's a lot of people who, for various reasons, are stuck using the stock roms or they are too fearful of flashing.
Just an example, a buddy of mine works for AT&T. One of AT&T's policies (like every other major carrier) is to hand out different handsets to the employees so that they can become familiar with them. Next month he's supposed to sample the Fuze. These types of fixes will actually be pretty useful to him for the purpose of making the fuze realistically functional.
Click to expand...
Click to collapse
I understand where you're coming from. However, most of XDA's fame and notoriety came from ROM's. Nowadays, it has fixes/updates to things, but at its core, its a place for custom ROMs for HTC phones.
BTW, I should have clarified. AT&T released an official, updated ROM for the Fuze. It, among other things, addressed this issue. So if someone is scared to run a custom ROM, they can always just flash to the official update, and still, problem solved with aGPS.
I have worked for AT&T, so I now the specific program you're referring to. By now, all Fuze's should be shipped with latest update. And even if not, its not very hard to flash to something he likes, and then flash it all back to stock when he needs to turn it in....
And btw, not every carrier does that. At least, not the one I work for now....
mexiken said:
BTW, I should have clarified. AT&T released an official, updated ROM for the Fuze. It, among other things, addressed this issue. So if someone is scared to run a custom ROM, they can always just flash to the official update, and still, problem solved with aGPS.
Click to expand...
Click to collapse
I may be mistaken, as I only spent a few minutes looking, but I can't find an officially released rom update for the Fuze anywhere on HTC or AT&T's site. AT&T's support FAQ claims there's no updates yet. Assuming these sites aren't misrepresenting the facts, I'm pretty sure you're mistaking the firmware update with the Leaked version here: A-GPS works in 5.08 leaked AT&T ROM. Keep in mind, that version leaked less than 6 weeks ago and AT&T is famously slow to release.
You're picking at exactly the point I said I didn't want to get into, that we shouldn't be discussing "To Flash or Not To Flash". Fact is that there's some people who can't...or won't...flash their phones, but installing a cab that notably improves GPS performance with minimal (at this point, virtually zero) risk is surely good for them. There's no reason to knock a good solution if it exists. My point is, XDA isn't just about the latest ROMs, and from the reading I've been doing on here for the last couple of years, I don't believe it's ever been just about the roms.
I'd be willing to bet there's going to be a fair number of people getting use out of this fix. Nearly 300 downloads in just the last 3 days, I suspect at least 10% of those downloaders are getting a lot out of XDA without using a custom rom. In other words, cut these guys some slack, they're doing good work even if it doesn't apply to the majority.
Hi krish_nank
This cab works well with my rom : ROMeOS v.1.95.1 WWE.
Regards,
PB
speed_pour and mexiken stay on topic please.
if you both want to discuss certain things that don't concern the meaning of this thread please pm each other or do it on the msn.
you both have installed the cab? if yes, what are the experiences?
thanks and regards
pabcb said:
Hi krish_nank
This cab works well with my rom : ROMeOS v.1.95.1 WWE.
Regards,
PB
Click to expand...
Click to collapse
in which way did it worked well? i know it is for faster gps locks.
But can you be more concrete?
thanks
I dont suppose this also corrects the gps satellite bars for signal not showing does it ?
(IE TomTom , Igo , and a few others dont report the signal strength )
Thanks Much
GSM Raphael owners take note!
pretty funny. Also a good indication of the subjectivity of this problem and the power of the "placebo effect".
Sorry to say, but this cab really doesn't do anything. It sets pollinterval to 500 which is below the 1 second chip update capability. Da_G demonstrated the ineffectiveness of this. Pollinterval should be 1000. Also this cab sets the logs to 32, another setting that has been proven ineffective.
To fix the missing satellite display, TomTom must be upgraded to v7.910.9185.
There is an AT&T test ROM underlying acquisition time fixes to the GPS system. This correctly enables AGPS resulting in consistent 15 second lock times. It has no effect on position lag.
If you really want to understand GPS issues you must patiently read through the entire mammoth thread located in the raphael forum titled "touchpro GPS lag problems". Switch to the forum and sort by views. It is one of the most viewed threads there. It describes in great detail the various GPS issues starting on about post 300. Videos and real cabs containing tested tweaks are there too.
Here is your quiz. Once finished reading you will be able to easily understand and differentiate between these:
what is position lag?
what is speed lag?
what is a cold start, warm start, hot start?
what is ephemeris and how does AGPS affect this?
how does AGPS differ from QuickGPS?
Why does AGPS have no effect on either lags?
More importantly, you will understand exactly what you need to do to turn your Raphael into one of the absolute best handheld GPS devices out there.
Or, you could just load one of the fixed ROMs and run TomTom v7.910.9185 (yes, position lag is partially based on the navigator you are using)
Sleuth255 said:
pretty funny. Also a good indication of the subjectivity of this problem and the power of the "placebo effect".
Sorry to say, but this cab really doesn't do anything. It sets pollinterval to 500 which is below the 1 second chip update capability. Da_G demonstrated the ineffectiveness of this. Pollinterval should be 1000. Also this cab sets the logs to 32, another setting that has been proven ineffective.
To fix the missing satellite display, TomTom must be upgraded to v7.910.9185.
There is an AT&T test ROM underlying acquisition time fixes to the GPS system. This correctly enables AGPS resulting in consistent 15 second lock times. It has no effect on position lag.
If you really want to understand GPS issues you must patiently read through the entire mammoth thread located in the raphael forum titled "touchpro GPS lag problems". Switch to the forum and sort by views. It is one of the most viewed threads there. It describes in great detail the various GPS issues starting on about post 300. Videos and real cabs containing tested tweaks are there too.
Here is your quiz. Once finished reading you will be able to easily understand and differentiate between these:
what is position lag?
what is speed lag?
what is a cold start, warm start, hot start?
what is ephemeris and how does AGPS affect this?
how does AGPS differ from QuickGPS?
Why does AGPS have no effect on either lags?
More importantly, you will understand exactly what you need to do to turn your Raphael into one of the absolute best handheld GPS devices out there.
Or, you could just load one of the fixed ROMs and run TomTom v7.910.9185 (yes, position lag is partially based on the navigator you are using)
Click to expand...
Click to collapse
Hi Sir, May be i was wrong as i am not a technically sound person about the mobile working.....if you really believe this cab doesn't have helped any one or doesn't help any way....please close the thread.....once it is done i will delete the cab too. I don't want to waste many people time & useless long thread with out working fix.........
By the way it is been mentioned that this cab act as an tweak to get quick satellite fix not to correct a lagging problem ....
Please close this thread if possible or delete the thread itself Thank you
Hi Krish,
in the right corner of each post there's a red white triangle.
If you click on that then the mods know that you want to close the thread but use it only for:
Note: This is ONLY to be used to report spam, advertising messages, and problematic (harassment, fighting, or rude) posts.
each forum has his own moderators contact one of them who are availiable
Hmm, I just updated to Slideme 3.41, keeps FC while loading catalogue. I un-installed and installed it again, same. I'm on Modaco 3.2.
Based on the forum posts on slideme, it looks as though they had a bad update about 5 days ago. This update doesn't work on Android 1.5 devices, and a number of 2.x ones as well. On some other devices that it still works on, a lot of missing apps. I'm not sure when or if they will issue a fix.
The problem is related to a 1.5 issue.
There is no FC on 2.x
sisbell is simply personally attacking us as an ex team member. Ironically, he was involved with this product in the past and we've been fixing all his mess.
We will patch this as soon as we finish our testing, most likely tomorrow.
re: catalog updates, apps populate as they're being fetched when you enter each category.
If you need a version today, you can get the 3.4 also from site.
Excuse that we did not test thoroughly on 1.5's before a release.
I fail to see how this is a personal attack. I'm just giving a user a quick rehash of what I picked up on the forums and twitter. If SlideME is not testing its releases, how is that my fault?
For anyone who is interested on the issues, here are some relevant links:
Android 1.5 - Crashes
http://slideme.org/application/slideme-marketplace#comment-783
Android 1.6 - listings out of date
http://slideme.org/forum/developer-discussion/device-listings-way-out-date
Android 2.x - compatibility problems
http://slideme.org/forum/general-discussion/application-compatibility
You're definitely monitoring anything mentioned about us and first to post a negative comment anywhere on the web - and you claiming you're not personally attacking or just wanting to damage..? How did you manage to post here? When was the last time you posted on XDA? When was the last time you used your twitter, http://twitter.com/sisbell ?
It seems you got nothing better to do, than follow what we do or what is mentioned about us.
Not to mention that most of the issues are due to your own crappy code you left behind, being cleaned up.
I think we have better things to do and I hope you have too as a grown up.
SlideME said:
You're definitely monitoring anything mentioned about us and first to post a negative comment anywhere on the web - and you claiming you're not personally attacking or just wanting to damage..? How did you manage to post here? When was the last time you posted on XDA? When was the last time you used your twitter, http://twitter.com/sisbell ?
It seems you got nothing better to do, than follow what we do or what is mentioned about us.
Not to mention that most of the issues are due to your own crappy code you left behind, being cleaned up.
I think we have better things to do and I hope you have too as a grown up.
Click to expand...
Click to collapse
Wow, I was just answering someone's question, I didn't expect to get hit by a troll. Don't bothering trying to bait me, this is my last post on this thread.
I realize it's still on the horizon and I am not asking when. I have tried FRX06 and updated the kernels and rootfs as they became available. Two things I have not done is use the new RIL2 or try the new audio routing patches.
My setup - VZ TP2/Rhod500. Without looking, I can't tell you which kernel or rootfs I am using. If I were are my home computer where I do the installs, I could tell in a second.
My question is this - in all likelihood, will FRX07 incorporate the new RIL and the BT/audio fixes? I'm not familiar enough with ADB or some of the other things mentioned in the audio routing thread to attempt them at this time.
For the most part, FRX06 is workable for me. I can run it for several days without SODs or random reboots. Other times, it might be a day or two. I do use my BT when in WinMo so it would be nice to have it in FRX0_.
Kudos to the various devs here for their hard work. I hope to be able to use FRX07 in the near future or at least until the company I work for upgrades my phone (wish list - Samsung Fascinate).
Thanks again to the devs and other testers! I have learned a good deal from the posts.
I can't say for sure until it's released, but I'm pretty confident that:
a) The new RIL will most definitely be in FRX07.
b) The BT/audio routing stuff needs some work yet, and to prevent from further delaying FRX07, it probably will not make it.
Feel like this is the place to mention this.
Some posts I read people are testing Bluetooth.
Are they confuzzled users with a different phone or is there something I am missing?
ryannathans said:
Feel like this is the place to mention this.
Some posts I read people are testing Bluetooth.
Are they confuzzled users with a different phone or is there something I am missing?
Click to expand...
Click to collapse
You are missing something.
Check out the "new audio routing" thread, it includes instructions (not for the weak kneed) how to get BT up and running. I've done it on a clean FRX06 install and successfully done several file transfers.
ryannathans said:
Feel like this is the place to mention this.
Some posts I read people are testing Bluetooth.
Are they confuzzled users with a different phone or is there something I am missing?
Click to expand...
Click to collapse
LOL!!!
That's awesome. I think you're the confuzzled one...
[TESTING] New audio routing for Froyo
If we could just get that ril packed in there I'd be happy, bluetooth isn't that important in the grand scheme of things. My wife is incredibly jealous of my inspire and I don't have the money for another. frx05 was her last attempt to use android and she just got tired of sods and poor battery life. For some reason her rhod300 never worked as well with these builds as mine. Hopefully gsm nand will be working soon so I can just wipe out windows mobile and not give her any choice
arrrghhh said:
LOL!!!
That's awesome. I think you're the confuzzled one...
[TESTING] New audio routing for Froyo
Click to expand...
Click to collapse
Heh, thanks.
Saw that but wasn't going to test it, now I see bluetooth in it.
Testing tonight
Over the past ~2 weeks, many people have been seeing this bug. We often write it off as being the bug that requires you to flash a Sense ROM, get a lock, then flash back to AOSP, but this is something different. Rather than discussing this separated in half a dozen different threads, I'd like for us to tackle this bug here in a thread focused to it.
I've seen what I believe to be this bug manifest with two different symptoms:
Full GPS works fine while network location works in some apps but gives you an obviously bogus location in other apps.
Full GPS works fine while network location works in some apps and simply fails in other apps.
NOTE: If Full GPS fails for you (such as in Google Maps), then go tackle that problem first before discussing here. If full GPS fails, then you probably have the bug that requires you to flash a Sense ROM. Please do NOT confuse that bug with this one!
I have seen this bug reported for all functional AOSP-based ROMs that I've followed, specifically CM7, OMFGB, OMGB, and Liquid Thunderbread. The funny thing is that some people get this bug while others do not, and there is not a clear pattern.
As I said before, this is clearly happening on pretty much every AOSP-based ROM. What is not clear, however, are what causes this. So it sure would be nice to figure this out. I'm not sure exactly what we need to do to find this but since you all are smart cookies, we'll still figure this out...
Click to expand...
Click to collapse
We aosp users have been plagued with the location bug for a VERY long time when it comes to rom dev time. Has anyone even bothered to look into it, or has everyone just excepted that it dosent work?
every thread or mention ive seen on multiple forums all ended in DEAD TOPICS.
rootz wiki has a DEAD 9 page thread on the matter, not one further post.
XDA has... 0 threads?( correct me if im wrong) on this, but ALOT of mentions
can I ask a dev to look into this? Excuse me for making broad assumptions, but it appears to me that all devs are doing right now is working on the bells and whistles for their roms and modding kernels and such while this bug got swept under the rug. I can understand that devs are BUSY and I thank them for that, I just request that we iron out this little bug, so that these AOSP gems are FLAWLESS.
As far as I can see, there really isn't any rom out there that will give you Android 4.0 or higher, and that still lets you use the video cam. I'm not too big on recording but I still consider it to be a very integral part of a phone, so of course I don't want to omit on that feature.
Now, ICS has been out for quite some time and the official Android iterations have already moved far ahead, but the latest stable release I can find for Atrix seems to be CM 7. Android 2.3.7. And that was in June 2012. Seems like stone age. Is it really this hopeless or am I missing something?
Lots of apps require at least 4.0 so being stuck on 2.3 feels really frustrating. Any tips on functional roms that aren't missing too many important features?
Wow, after the huge rage over Moto deciding to leave the Atrix behind and all the dozens of threads about that, there are still questions like this?
ravilov said:
Wow, after the huge rage over Moto deciding to leave the Atrix behind and all the dozens of threads about that, there are still questions like this?
Click to expand...
Click to collapse
I started using smart phones two years ago. It took me quite awhile to discover the Atrix, so you could say I missed out on that outrage. I just bought a used Atrix and had hopes of updating it to at least 4.0 but it seems difficult to achieve, despite that a long time has passed. Can it really be that hard to get the recording to work?
Yes, it actually can. Reason being non-existent drivers for proprietary hardware. Sadly this device has been discontinued, despite its great hardware potential, and there is and will be no support for it past GB. So we're left with having to "invent", figure out and piece together stuff on our own.
It's all explained in great detail in many other threads.
ravilov said:
Yes, it actually can. Reason being non-existent drivers for proprietary hardware. Sadly this device has been discontinued, despite its great hardware potential, and there is and will be no support for it past GB. So we're left with having to "invent", figure out and piece together stuff on our own.
It's all explained in great detail in many other threads.
Click to expand...
Click to collapse
Okay, I can buy that, makes sense.
Well, I've managed to find at least some roms at 4.0 and above, so I will try out the most promising ones, starting with AvatarRom and AtrICS. Functionality over "better stats" and all that. And then move on from there. Taking photos and recording is something I do on a regularing basis so it's vital that those parts actually work as intended, other parts I might overlook easier.
Daige said:
Okay, I can buy that, makes sense.
Well, I've managed to find at least some roms at 4.0 and above, so I will try out the most promising ones, starting with AvatarRom and AtrICS. Functionality over "better stats" and all that. And then move on from there. Taking photos and recording is something I do on a regularing basis so it's vital that those parts actually work as intended, other parts I might overlook easier.
Click to expand...
Click to collapse
AtrICS yes, Avatar no due to their servers being jacked up and the ROM not available (disregard if they actually did get that ROM back up). Krystian's CM9 and Epinter's CM10.1 are your heavy hitters that really are worth looking into for a 4.0 and up experience.
If you want the video and picture quality, you can use the Alpha stage ROMs suggested above, otherwise best advice is stay on GB until more kernel work is done.
Per the first complaint (see thread name), doing this thing called research would have told you what @ravilov mentioned. You say you got into smartphones 2 yrs ago. The Motorola ICS debacle happened Sept 29th-ish, 2012. Thats within 2 yrs, and that was a big backlash they suffered.
Sent from my MB886 using xda app-developers app
palmbeach05 said:
AtrICS yes, Avatar no due to their servers being jacked up and the ROM not available (disregard if they actually did get that ROM back up). Krystian's CM9 and Epinter's CM10.1 are your heavy hitters that really are worth looking into for a 4.0 and up experience.
If you want the video and picture quality, you can use the Alpha stage ROMs suggested above, otherwise best advice is stay on GB until more kernel work is done.
Per the first complaint (see thread name), doing this thing called research would have told you what @ravilov mentioned. You say you got into smartphones 2 yrs ago. The Motorola ICS debacle happened Sept 29th-ish, 2012. Thats within 2 yrs, and that was a big backlash they suffered.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
I actually found the AvatarRom, albeit not on their homepage but linked from the forum to some other download source. However, that rom didn't work out very well for me. AtrICS seemed complicated due to me not understanding the whole "vendor" thing they mentioned, so I decided to skip that one entirely. After trying out several roms I went back to CM 7.2 since that at least made the phone function quite good (except one app that seems to have a model specific bug in it).
I'll take a look att Krystian's alternative, whatever it's called. Epinter's seemed to have camera issues?
About "getting into smartphones two years ago": At that time, I nearly hated smartphones, which is why I didn't read very much about them (and therefore, I missed that "why no ICS?"-rage). Just because something "big" happens doesn't mean everyone will know about it. Yes, it's okay to ask me which rock I've been sleeping under. However, I can't point out the rock now, I've forgotten where it was.
Daige said:
I actually found the AvatarRom, albeit not on their homepage but linked from the forum to some other download source. However, that rom didn't work out very well for me. AtrICS seemed complicated due to me not understanding the whole "vendor" thing they mentioned, so I decided to skip that one entirely. After trying out several roms I went back to CM 7.2 since that at least made the phone function quite good (except one app that seems to have a model specific bug in it).
I'll take a look att Krystian's alternative, whatever it's called. Epinter's seemed to have camera issues?
About "getting into smartphones two years ago": At that time, I nearly hated smartphones, which is why I didn't read very much about them (and therefore, I missed that "why no ICS?"-rage). Just because something "big" happens doesn't mean everyone will know about it. Yes, it's okay to ask me which rock I've been sleeping under. However, I can't point out the rock now, I've forgotten where it was.
Click to expand...
Click to collapse
Really? now that is interesting. I wonder if they just restored the link and didn't update their page. idk, ppl have been having issues with the creators of Avatar ROM for weeks now about getting their stuff in order. AtrICS isn't hard to understand. Flash main ROM, then flash Vendor. Its like any CM ROM. Flash main ROM, then flash Gapps. Same concept. CM7.2 (GB) is going to give you the most stability and fully functioning ROM for this device. until the 3.1.10 kernel is given the Beta status, all 4.0 and up ROMs are considered Alpha stage if they use said kernel.
Krystian's CM9 is 4.0.4 running on the 3.1.10 kernel. Epinter's is 4.1.2 and 4.2.2 running the same. all 4.0 and up ROMs will have camera issues due to the need for updated drivers. drivers we don't have b/c Moto refuses (not worth fighting for anymore) to release them.
The ICS mess happened a yr ago. but yes, I do see your point. for example, these galaxys that keep coming out. I see news about them, but I don't go looking at them or reading the news about them.
AtrIcs is somewhat a stable rom with just few issues like average battery timing and sometimes lag in screen lock.Only thing i love about AtrIcs is stock look of moto . Currently i am on Epinter's Cm 10.1 it's also worth trying especially with motoblur theme from play store it's a treat to have Atrix on stock moto look with jb.