[Q] [devreq]updates on aosp location bug? - Thunderbolt Q&A, Help & Troubleshooting

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.

Related

Mods please close the thread.....

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

Another ROM recommendation?

I'm still running the original stock VZW/HTC ROM. I know, I know, slow adopter... I'd like to root and go with a ROM that delivers better battery life and a basic debloat. However, nearly every ROM I read about seems to have a major (in my humble opinion) flaw. A non working camera or video camera, non working voicemail notification, malfunctioning signal strength bars, no 4G, etc., etc.
Is my only choice really a Froyo ROM? I'm not willing to stomach any major loss of functionality (or apps), be it phone, camera, calendar, GPS, navigation, various google apps, Bluetooth, WiFi, 3G and 4G, working signal strength bars, etc. I guess I am also in the "I prefer Sense" group but also have not given non Sense ROMs any time.
If responding I kindly request a few sentences of explanation/clarification rather than just saying "Get ROM X, it rocks, it is the best". Thanks in advance.
Everything works on most the gb roms, with some needing certain fixes to fix certain things. Gingeritis 3d, with chingys new radio is tits imho
Sent from my TBolt using my f***king thumbs...
Well, I'm not going to give you a few sentences, but I can tell you that I use Gingerth3ory (link in my siggy) and everything works, including vvm as long as you apply the bootable zip fix for that. Before, vvm was the only thing not working.
Camera, videocamera, wifi, 3g, 4g all work. I switched to youmail for vvm because I wanted netflix over stock vvm so that meant a GB ROM.
I highly recommend Droid Theory's latest Senseless Rom. This is the smoothest and quickest ROM of his yet and that is saying something. There is a large mod community if you're interested in that. Most importantly, DT is very responsive and provides great support. He will be coming out with an update very soon to fix the market issue.
Sent from my ADR6400L using XDA App
http://forum.xda-developers.com/showthread.php?t=1176922
http://forum.xda-developers.com/showthread.php?t=1187545
http://forum.xda-developers.com/showthread.php?t=1187545
Just showing there's been 3-4 other similar posts in the past few hours, just to avoid fragmenting answers or not getting the answer you wanted.
Just follow my link in my signature.
Synergy is the way to go.
Thanks folks.
OK we have votes for Gingeritis 3d, Gingerth3ory and Droid Theory's latest Senseless Rom. Has anyone ran more than one of these? Any important compare/contrast between them? I care much more about stability and battery life over eye candy. Those are my top 2 concerns. If those things are improved over the stock VZW/HTC ROM I should be happy. The biggest problems with this stock ROM for me are maintaining a data connection when switching from 3G to 4G and back. Also the speed of the GPS lock is very slow. How are these things in these recommended ROMs?
(yareally: You posted 2 identical links but mentioned 4 threads. Yes the questions in some of these were related to mine but certainly were not identical request.)
I'm going to venture a guess you haven't actually looked at the threads or the dev's pages. Most have a thread for bug reports. GB ROMs are about as solid as any OTA these days. If you're new to flashing DO NOT, DO NOT use Synergy. It's a frankenstein project with no official stable release and a constant onslaught of nightlies with no end in sight. STAY AWAY FROM NIGHTLIES. Try BAMF. Try Gingeritus. Try Eaton. Try GING3R3DTH3ORY. Try something that's known to work and isn't revised several times a week. From the sounds of it, Eaton might be what you want. It looks and works very much like stock.
swamp2 said:
Thanks folks.
OK we have votes for Gingeritis 3d, Gingerth3ory and Droid Theory's latest Senseless Rom. Has anyone ran more than one of these? Any important compare/contrast between them? I care much more about stability and battery life over eye candy. Those are my top 2 concerns. If those things are improved over the stock VZW/HTC ROM I should be happy. The biggest problems with this stock ROM for me are maintaining a data connection when switching from 3G to 4G and back. Also the speed of the GPS lock is very slow. How are these things in these recommended ROMs?
(yareally: You posted 2 identical links but mentioned 4 threads. Yes the questions in some of these were related to mine but certainly were not identical request.)
Click to expand...
Click to collapse
last one was a miscopy, there was another one at least on the front page, but I was half asleep at the time. I said 3 to 4 btw, not 4. There have been lots though of rom reccomendation postings though and felt you would get a better idea by reading what other people had asked already.
i'm using Synergy with the "06275r" radio and the dreamKernal. i also have SetCPU on set to "performance". it runs really smooth and the battery life is better then stock.
i've tried pretty much every ROM out there and have had this running for several days now. i like it and will keep it for a tad bit longer(why just a tad? i can't help it.. i like to keep trying new ROM's)
loonatik78 said:
If you're new to flashing DO NOT, DO NOT use Synergy. It's a frankenstein project with no official stable release and a constant onslaught of nightlies with no end in sight. STAY AWAY FROM NIGHTLIES....Try something that's known to work and isn't revised several times a week.
Click to expand...
Click to collapse
I have to disagree. Just because Synergy is updated every night does not mean you must flash reflash every day. The nightlies have very minor revisions (adding HTC Car Panel, changing the host file for better ad blocking, changing the Market icon color, changing the email splash screen, etc). If you don't need the newest revisions, then don't flash the latest nightly until something comes along that you really want/need. Synergy nightlies aren't released because it is an unstable rom. Quite the contrary. I have tried roms from 4 other devs and Synergy is the fastest & smoothest of them all. The only time I've had lockups or reboots is when I overclocked too much, which would have happened on any rom.
Don't be dissuaded from trying Synergy because there are nightly updates. If anything, that should tell you the devs are committed to making it better.
sublimaze said:
I have to disagree. Just because Synergy is updated every night does not mean you must flash reflash every day. The nightlies have very minor revisions (adding HTC Car Panel, changing the host file for better ad blocking, changing the Market icon color, changing the email splash screen, etc). If you don't need the newest revisions, then don't flash the latest nightly until something comes along that you really want/need. Synergy nightlies aren't released because it is an unstable rom. Quite the contrary. I have tried roms from 4 other devs and Synergy is the fastest & smoothest of them all. The only time I've had lockups or reboots is when I overclocked too much, which would have happened on any rom.
Don't be dissuaded from trying Synergy because there are nightly updates. If anything, that should tell you the devs are committed to making it better.
Click to expand...
Click to collapse
I don't agree with that and I'll tell you why. Let's say I tell Joe Bob to go try synergy. He does, and downloads who knows what on whatever night. Then he has a problem... Now what? Try to decipher Ziggy's advice? Try another nightly version? As far as I'm concerned nightlies are for developers. I think that because that been the whole point of nightlies from the beginning. I'm pretty sure CM was the first, but even they did that in support of a release candidate aiming towards an official release. I wouldn't tell someone "Go try a CM nightly!" even if they were looking mostly solid. I've read almost all of the thread for synergy. It's hardly a work without error. I don't believe that project is dedicated to producing reliable ROMs. They show no sign of such in any form, be it a release candidate or a final release. It appears to be a few developers tinkering and experimenting, in many cases against the law, and I cannot in good faith suggest someone fresh on the scene jump into one of the most convoluted ROMs for the Thunderbolt.
I've been using nightlies for INC and they've all been stable for the past several months. They just keep adding features. At first it sort of bugged me that I never had the most updated version but then I just lived with staying with my version for several months until I got bored enough to flash the latest.
If nightlies isn't your thing then that's fine but I don't see a reason to tell other users to stay away from them. Generally they *will* have more bugs because the dev's don't thoroughly check the ROM's before they release - they expect the people who flash to find the bugs and then they fix it in the next releases, but after a while all those bugs are gone- then they move to adding a new feature and that may have a bug, and the cycle continues.
But in most cases these bugs are very minor and overall the ROM is superior in performance / battery / features than other ROM's.
POQbum said:
I've been using nightlies for INC and they've all been stable for the past several months. They just keep adding features. At first it sort of bugged me that I never had the most updated version but then I just lived with staying with my version for several months until I got bored enough to flash the latest.
If nightlies isn't your thing then that's fine but I don't see a reason to tell other users to stay away from them. Generally they *will* have more bugs because the dev's don't thoroughly check the ROM's before they release - they expect the people who flash to find the bugs and then they fix it in the next releases, but after a while all those bugs are gone- then they move to adding a new feature and that may have a bug, and the cycle continues.
But in most cases these bugs are very minor and overall the ROM is superior in performance / battery / features than other ROM's.
Click to expand...
Click to collapse
Please read what I wrote. I would not tell a NEW user to try a nightly. That would be stupid. The last thing some virgin flasher needs is to flash some nightly that got some new test kernel cooked into and its quirky as hell, or some jazz like that. We ALL wanted our first flash to work and not freeze or crash. I'm telling a NEW user to stay away from nightlies, not the experienced guy. I don't care how stable one night's version might be, or if almost all of them are. They are test beds and you don't know what you're getting night to night. And NO nightly I've ever used has been quirk-free.
loonatik78 said:
Please read what I wrote. I would not tell a NEW user to try a nightly. That would be stupid. The last thing some virgin flasher needs is to flash some nightly that got some new test kernel cooked into and its quirky as hell, or some jazz like that. We ALL wanted our first flash to work and not freeze or crash. I'm telling a NEW user to stay away from nightlies, not the experienced guy. I don't care how stable one night's version might be, or if almost all of them are. They are test beds and you don't know what you're getting night to night. And NO nightly I've ever used has been quirk-free.
Click to expand...
Click to collapse
Well.. I've had plenty quirk-free. But the Incredible nightlies are more polished than the thunderbolts.
I think you shouldn't tell them not to flash a nightly, just warn them of possible issues and explain to them what they are (and they would see this anyway because every nightly thread I've been to explains this)
POQbum said:
Well.. I've had plenty quirk-free. But the Incredible nightlies are more polished than the thunderbolts.
I think you shouldn't tell them not to flash a nightly, just warn them of possible issues and explain to them what they are (and they would see this anyway because every nightly thread I've been to explains this)
Click to expand...
Click to collapse
if someone is starting a thread like this, reading threads probably ain't in their game plan. I don't give advice to strangers I wouldn't give to a friend. You run something like a version of BAMF and you're running something a dev has hung his hat on. Not so with a nightly because there will be another tomorrow night! Telling a noob to try a nightly, regardless of stability, is like telling your kid to learn to drive behind the wheel of a Kenworth. If something goes wrong, its going to become a bigger deal than it would be if the guy had flashed 2 or 3 ROMs. This seems real obvious to me. Are you forgetting your first experience rooting and flashing ROMs? I'm not gonna warn someone of the dangers of doing something I consider stupid. I will say "If you want to do something stupid, go flash a nightly for your first ROM. If your LUCKY it will all work right. If it doesn't, go fly a kite because you're own your own, bro."
Thanks for the further comments. Let's not try to get too side tracked on one ROM with many nightlies. I definitely prefer to steer clear of a ROM with nightlies. I'd like to let others do all that valuable beta testing and simply benefit from their work. Selfish - sure but uncommon - no.
Just to clarify some personal details that may help with recommendations. I've read many of the posts here from the devs themselves on their ROMs. However, slogging through hundreds of pages on a small handful of ROMs is not my idea of fun... I'm quite computer/phone literate but have not done programming in years. I also work in the software industry. After years of crappy and unstable WinMo devices and plenty of random freezes, resets and data loss, I've found a pretty nice new home with Android. I'm not afraid to experiment, trouble shoot, etc. However, I want a phone to USE much more than to constantly tinker, repair, troubleshoot, etc. I'd like a really mature, stable bulletproof ROM along with the ability to have GB and keep Sense. It is incredibly difficult for me to read the oftentimes massive features lists on the first page of any given ROM thread and distinguish it from other competing offerings. Despite being pretty computer literate, most of those pages are nearly entirely "greek" to me.
Perhaps there is no single best ROM or recommendation but I am going to continue to read all the replies here and hopefully get my choice narrowed down. Of course I realize no ROM choice is permanent. I'll just say again I like to USE my device rather than constantly "tinker".
Cheers.
InfuseTh3ory ... Try it.
Since you like Sense then check out Gingeritis
http://www.themikmik.com/forums/viewforum.php?f=271
Sent from my ADR6400L using XDA App
gingertheory is a nice solid build that I've been running the last couple of weeks. No big deal breakers as far as bugs.

Display says "Please Release Keys..." after install CM7

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

Why not make an overview thread for ROMs?

I've noticed that whenever someone asks, "What ROM should I use?" the responses are either brusque (e.g. "Just install whatever and find what you like,") or unverifiable ("I've had okay luck with XYZ").
When I choose a ROM, the first thing I care about are the bugs. And yet, there is no single thread in the development forum that has a list of all the current ROMs, and a list of bugs. Some developers are very good with updating the first page of their thread, clearly listing the bugs, and yet for other ROMs, you have to dig until you get to post 1579 on page 157 to find that such-and-such functionality doesn't work.
Why doesn't anybody do this? Why isn't there a sticky at the top of the development forum that clearly lists the major ROMs in development, and keeps track of the main bugs? This makes selecting a ROM much, much easier.
TSGM said:
I've noticed that whenever someone asks, "What ROM should I use?" the responses are either brusque (e.g. "Just install whatever and find what you like,") or unverifiable ("I've had okay luck with XYZ").
When I choose a ROM, the first thing I care about are the bugs. And yet, there is no single thread in the development forum that has a list of all the current ROMs, and a list of bugs. Some developers are very good with updating the first page of their thread, clearly listing the bugs, and yet for other ROMs, you have to dig until you get to post 1579 on page 157 to find that such-and-such functionality doesn't work.
Why doesn't anybody do this? Why isn't there a sticky at the top of the development forum that clearly lists the major ROMs in development, and keeps track of the main bugs? This makes selecting a ROM much, much easier.
Click to expand...
Click to collapse
Personally, I think it's easier to manually visit the thread of every ROM and read the reviews (plus bugs are always mentioned in 1st/2nd/3rd post), or just flash them one at a time and see for yourself.
Fatal1ty_18_RUS said:
Personally, I think it's easier to manually visit the thread of every ROM and read the reviews (plus bugs are always mentioned in 1st/2nd/3rd post), or just flash them one at a time and see for yourself.
Click to expand...
Click to collapse
I'm sorry, I don't mean to be rude (or antagonistic), but how is that easier? Wouldn't you rather just have a single page where you can see all the reported bugs for the major ROMs? How is it easier to flash it yourself, and then discover these bugs?
For example, one of my recent phone ROMs had a bug where SMS messages of a certain type would not work. This was neither mentioned on the first, second, nor third posts. Moreover, it was mentioned by certain testers, but buried within the 50-or-so pages of the thread. I realize that a lot of using other people's ROMs involves your own testing.
But I'm simply making a suggestion that would help you isolate bugs before you even flash. Isn't that just, like, common sense?
Anyways, it's a small suggestion. If people don't care and prefer not to have a central thread for this, then it doesn't bother me much. I just thought that it would help a lot of new people.
TSGM said:
I'm sorry, I don't mean to be rude (or antagonistic), but how is that easier? Wouldn't you rather just have a single page where you can see all the reported bugs for the major ROMs? How is it easier to flash it yourself, and then discover these bugs?
Click to expand...
Click to collapse
As strange as it sounds, yes it is. Even though when you know the list of bugs for ROM "X", it's simpler to flash that ROM, and see for yourself if that bug is annoying/makes the experience of using your device worse, or maybe you can even face with bugs that aren't even mentioned in the thread, helping the other users of the same ROM, and mentioning the issue to the developer, in hopes that it will possibly be fixed with the next update.
Of course that's time consuming much, but at least that way you can experience those bugs by yourself, and, if they are not that much of a deal and you can live with it, you'll still be using that ROM, instead of trembling in fear before the known bugs, and telling the ROM "good bye", and continuing the search for the perfect one.
I'm not saying anything against the guide like that, it's a wonderful idea (especially if you're going to be the one who makes that guide), but it'll still require you to visit the threads for each of the ROM that you'd count in the guide a "Major".
An index thread would indeed be useful, at least to list the ROMs and other resources, with working links. Like I did for the One X here.
As for including a list of bugs. I don't see that as being practical. Bugs can be numerous, and are not always experienced by every user of a ROM. I'd be hesitant to assume that something is a bug (might just be user error), if I were not the dev. And for ROMs that are still active, bugs are ever changing, and it would be a significant task to update the list every time new build is issued. Listing of bugs is probably best left to the developer. In the end, if there is a ROM you like, its not that hard to go through the last several pages of the ROM thread, and see what common bugs people are experiencing. That is what I've done for every new ROM I've tried for the last 5-6 years.
The only reason "why not" make an index thread (listing the ROMs), is simply that nobody has taken the time and effort to do so. You want to do it, go for it. Then PM the mod, and if you did a decent job, they will probably sticky it for you.
For me, frankly, this device is unfortunately too late in its life cycle for me to care enough about creating and maintaining such a thread. That's the simple reason.

Just a "wondering", a general question about all the "bugs" in AOSP (or other) roms?

Just a "wondering", a general question about all the "bugs" in AOSP (or other) roms?
There is a list of 10 or so bugs that come with all custom roms, a couple of which are problems with the camera, problems with wifi and tethering Hotspot, etc.
All (most) of these bugs do have solutions that involve after the fact things that need to be done once the roms are installed.
Please don't take offense. I know you devs and others put in a lot of time, effort, and hard work, many times being under appreciated (not by me, really, thanks for all you do), working on these custom roms. but my question is:
Is there some way that these individual bug fixes can be incorporated into the original custom rom zip? What keeps that from being done?
I'm really not trying to offend any of you, just trying to understand a little, since I know nothing about development at all. I can only use your good work if given, and I follow exactly, your posted instructions. I don't know enough to deviate from them.
Again, sorry, no offense meant at all.
Thx
As you haven't seen an answer yet, I figured I can offer a possible explanation. I'm not a dev either, but the key is that although Android is open, many of the drivers are not. For this reason, there are often many binary blobs that are part of a release that need to be included to let things work. And it's not easy to find out what's needed either, so it's mostly trial/error.
For example, for the camera, there is a driver somewhere that the stock app is looking for. If it's not there, it crashes out. That's why non-stock ROMs can't use the stock camera. Pretty much every (hardware) device in the phone requires a driver... and most of these are closed-source. Sometimes, you can pull it and it works... but sometimes they don't (either because something else is missing, or because the manufacturer intentionally made it break when it's off-stock). It's dumb, but this is the reality.

Categories

Resources