Database Develop

[SOLVED] Is Bluetooth broken in JM5/JM7 ?

Greetings fellow Galaxyenz,
I have a Galaxy S that worked all ok with JF5 stock ROM, paired with my car for phone audio, using bluetooth. Never had a disconnect...
Then I applied the procedure in order to get the HackEclair ROM 1.0.4 (flashed JM5 through ODIN, then recovery and applied update.zip). After that, i applied OneClickLagFix 2.0.
##EDIT## I'm currently on JM7 + Tayutama rom and it still exists.....
At the end my phone flies like a Concord, and it performs 2200 on Quadrant =)
My only problem right now is that Bluetooth connections to the Car audio, only last for 30 seconds.
I have to completely disable and enable Bluetooth on the phone in order to get the audio working again... for 30 more seconds... =(
Although the phone rocks with this ROM, having no bluetooth system in the car because of this ROM, is a no-go for me.
Thanks for you time. This forum has a great helping initiative.. It's precious, let's keep it
Cheers
Phk
EDIT -- Developed a dirty fix. Works OK for me now!

Just to make this thread complete, i've found the bug is related to some configuration desynchronization between car and mobile.
So android bt stack must be reseted.
I've developed my first app for this, so that i can reset confs with one click
thanks to every1 at XDA, you guys rock =)
http://www.multiupload.com/KI0WJ2RKZB or Check attached!
Cheers,
Phk

Good work! Finaly someone fixing stuff on own. You sir are all class
Sent from my GT-I9000 using Tapatalk

Word!
10cc

miki4242 said:
Word!
10cc
Click to expand...
Click to collapse
Thanks miki
The app is now on the Market, and i've realized that my car picks up the device faster if it has a new name after the fix, so i will implement a random "Android-XXXX" name for each time you click "Fix" =)
Install it from the Market to make sure you receive updates.
I'll also try to perform these steps, as they as what i really to:
- turn off bluetooth
- run this apk
- press fix
- turn on bluetooth
- change name
- reboot
Cheers!

Cool to see you addressing this with your own fix, but JM5 did have buggy BT with my car as well. Never a problem with JM6, JH1 or JM7. Maybe the better fix is to just get one of those firmwares, which don't have the problem you describe, and also drastically improve GPS (really, they do - for me anyways) and also are much less "laggy" even without fixes.

Hey distorted... Sorry to disappoint you, but I have JM7, and yes, the problem is still there That's why i've built up the tool, i have to use it every 2 days (more or less)
Anyway thanks for the thumbs up! =)
Cheers

Phk said:
Hey distorted... Sorry to disappoint you, but I have JM7, and yes, the problem is still there That's why i've built up the tool, i have to use it every 2 days (more or less)
Anyway thanks for the thumbs up! =)
Cheers
Click to expand...
Click to collapse
Disappoint me? LOL, not at all. I don't have the problem since moving on to newer leaked firmwares than JM5. I definitely had the problem on JM5, though.
Perhaps you should rename the thread, then, if it's not specific to JM5.
Additionally, your OP says nothing about different firmwares other than no problem on JF, but the problem on JM5, maybe you should include that the issue is there on JM7 also.
And finally, if you're still running RyanZA's lagfix, and/or the HackEclair ROM, how do you know they're not the real root of your BT problems?
Coincidentally, I was also on OCLF hack and JM5 when I had BT problems. Maybe it's the OCLF that's the problem, since I am on JM7 and don't use OCLF any more, and don't have the problem, but you do(?).

distortedloop said:
Disappoint me? LOL, not at all. I don't have the problem since moving on to newer leaked firmwares than JM5. I definitely had the problem on JM5, though.
Perhaps you should rename the thread, then, if it's not specific to JM5.
Additionally, your OP says nothing about different firmwares other than no problem on JF, but the problem on JM5, maybe you should include that the issue is there on JM7 also.
And finally, if you're still running RyanZA's lagfix, and/or the HackEclair ROM, how do you know they're not the real root of your BT problems?
Coincidentally, I was also on OCLF hack and JM5 when I had BT problems. Maybe it's the OCLF that's the problem, since I am on JM7 and don't use OCLF any more, and don't have the problem, but you do(?).
Click to expand...
Click to collapse
Yes, i might change the thread name
I'm on JM7 now with OCLF, but there's absolutely no reason for OCLF being the root of the problem.. Have you checked the full source code? I've read it line by line...

Phk said:
Yes, i might change the thread name
I'm on JM7 now with OCLF, but there's absolutely no reason for OCLF being the root of the problem.. Have you checked the full source code? I've read it line by line...
Click to expand...
Click to collapse
Full source code? Do you mean the scripts it runs? Of course I have. I manually ran them one by one to install OCLF on my phone since the batch doesn't work on Macs, and I generally want to know what exactly some script is doing to my phone in case I have to undo the steps if the script borks my phone.
Perhaps there's no reason OCLF (or Hackclair) would cause this problem, but lets look at the little bit of known data we have between the two of us:
Me: JM5 + OCLF = buggy BT
Me: JH1 + voodoo = working BT
Me: JM7 + voodoo = working BT
You: JF3 + nothing = working BT
You: JM5 + Hackclair + OCLF = buggy BT
You: JM7 + OCLF (+ Hackclair??) = buggy BT
The only common elements to EVERY scenario that has buggy BT that we have specifics to so far include OCLF.
It seems perfectly reasonable to assume that OCLF (and/or Hackclair if you're running it in your current buggy BT configuration) are part of the problem (edit: unless of course you just have buggy hardware).
With that in mind, a reasonable troubleshooting step would be to uninstall both OCLF and Hacklair and see if you have issues on stock JM7. If you don't, then we know that one of those modifications are the problem.
Since you've found for you what is an acceptable workaround, it's probably more effort than you're interested in doing to test that out, and I'm not interested in breaking what is a perfectly working combination of firmware/lagfix on my phone to install OCLF to test it out, so we'll probably have to rely on others reporting their configurations that work or don't work.
The only technical reason I might suspect OCLF as the issue is that in my experience, and the reports of others I've read, OCLF starts to lag again after a day or two of uptime on the phone. What if the BT disconnects are related to the system lagging? It's a stretch, I know, but I can't ignore the fact that between the two of us, the only thing we had in common while experiencing BT issues is OCLF. That's significant, in my humble opinion.
All that said, if I start experiencing BT problems out of the blue on any future configuration, I'll certainly look to your app for help!

distortedloop said:
Full source code? Do you mean the scripts it runs? Of course I have. I manually ran them one by one to install OCLF on my phone since the batch doesn't work on Macs, and I generally want to know what exactly some script is doing to my phone in case I have to undo the steps if the script borks my phone.
Perhaps there's no reason OCLF (or Hackclair) would cause this problem, but lets look at the little bit of known data we have between the two of us:
Me: JM5 + OCLF = buggy BT
Me: JH1 + voodoo = working BT
Me: JM7 + voodoo = working BT
You: JF3 + nothing = working BT
You: JM5 + Hackclair + OCLF = buggy BT
You: JM7 + OCLF (+ Hackclair??) = buggy BT
The only common elements to EVERY scenario that has buggy BT that we have specifics to so far include OCLF.
It seems perfectly reasonable to assume that OCLF (and/or Hackclair if you're running it in your current buggy BT configuration) are part of the problem (edit: unless of course you just have buggy hardware).
With that in mind, a reasonable troubleshooting step would be to uninstall both OCLF and Hacklair and see if you have issues on stock JM7. If you don't, then we know that one of those modifications are the problem.
Since you've found for you what is an acceptable workaround, it's probably more effort than you're interested in doing to test that out, and I'm not interested in breaking what is a perfectly working combination of firmware/lagfix on my phone to install OCLF to test it out, so we'll probably have to rely on others reporting their configurations that work or don't work.
The only technical reason I might suspect OCLF as the issue is that in my experience, and the reports of others I've read, OCLF starts to lag again after a day or two of uptime on the phone. What if the BT disconnects are related to the system lagging? It's a stretch, I know, but I can't ignore the fact that between the two of us, the only thing we had in common while experiencing BT issues is OCLF. That's significant, in my humble opinion.
All that said, if I start experiencing BT problems out of the blue on any future configuration, I'll certainly look to your app for help!
Click to expand...
Click to collapse
Thanks man Useful post! I've spoken to RyanZa before implementing this app, to confirm that there were no possible misunderstandings.
About the code: I was refering to OCLF source code (GPLv3) of the Market App
About the lag returning: I reboot my mobile frequently so the 2 day lag-reappear is not the question
Anyway, you are right, there is a common name: OCLF.
I might test this BT with Voodoo. What are the downsides of voodoo vs oclf? oclf is very neat and clean you know... ?

Phk said:
Thanks man Useful post! I've spoken to RyanZa before implementing this app, to confirm that there were no possible misunderstandings.
About the code: I was refering to OCLF source code (GPLv3) of the Market App
About the lag returning: I reboot my mobile frequently so the 2 day lag-reappear is not the question
Anyway, you are right, there is a common name: OCLF.
I might test this BT with Voodoo. What are the downsides of voodoo vs oclf? oclf is very neat and clean you know... ?
Click to expand...
Click to collapse
I don't imagine the apk for OCLF does anything different than the scripts do, essentially make the large data file and then loop mount it. So the end result is surely the same.
I don't really want to pollute this thread with the merits of OCLF vs voodoo, some people get a bit to "religious" or defensive about it and the thread will devolve to being really off-topic if that happens. There are plenty of threads hashing that debate out.
Personally, I think voodoo to be nice and clean as well. Voodoo requires a custom kernel and you install it via Odin. It backs up your data, formats /data as ext4, then restores the data it backed up to it. Simple, clean, reliable, but not as simple as just running an app from the Market. (For the record, Ryan, I'm not saying here that your method isn't reliable. )
The primary disadvantage for you to test it out at this point is that the beta1 is no longer available publicly, and the beta2 won't be released until "sometime this week", so really not easy for you to test out.

I am experiencing problems with a Bluetooth car kit as well, but different. Every now and then, the connection hangs. The stereo isn't receiving anything, but displays connection status for phone and media. The Galaxy S displays connection as well, the music player looks like it is working, but no sound can be heard.
When I turn off Bluetooth on my car kit, the Galaxy S still displays connected status. Turning off via status bar shortcut or settings menu makes it stay in "turning off" mode indefinitely. Sometimes I can't even bring down the status bar. And even shutting down the device doesn't work, as it is not completely powered down, I have to force it (10 seconds reset button) anyway. Then boot up and hope it doesn't happen again right away.
I had that problem with JM6 + OCLF and still on JM7 + OCLF, but as far as I can remember, it didn't happen on JF3, where I had OCLF running for quite a while as well. And I use my car kit every working day. I never ran JM6/JM7 without OCLF though, so this may not be related at all.
Getting off topic now, but I noticed something else with OCLF: when it is applied, and I connect the USB cable, it locks the internal and external SD cards even when in menu mode without choosing "mass storage". In that state, I can't access them neither from the PC nor from the phone. I need to select "mass storage" then disable it again (already put it as default because of that), which is also pretty annoying because my car charger does fake a PC connection (probably because some devices won't charge otherwise).
Before OCLF, I could just ignore the popup menu for USB mode. I am just saying that, because it is another side effect of OCLF which can hardly be explained by looking at the source.

PlanetJumble said:
I am experiencing problems with a Bluetooth car kit as well, but different. Every now and then, the connection hangs. The stereo isn't receiving anything, but displays connection status for phone and media. The Galaxy S displays connection as well, the music player looks like it is working, but no sound can be heard.
When I turn off Bluetooth on my car kit, the Galaxy S still displays connected status. Turning off via status bar shortcut or settings menu makes it stay in "turning off" mode indefinitely. Sometimes I can't even bring down the status bar. And even shutting down the device doesn't work, as it is not completely powered down, I have to force it (10 seconds reset button) anyway. Then boot up and hope it doesn't happen again right away.
I had that problem with JM6 + OCLF and still on JM7 + OCLF, but as far as I can remember, it didn't happen on JF3, where I had OCLF running for quite a while as well. And I use my car kit every working day.
Getting off topic now, but I noticed something else with OCLF: when it is applied, and I connect the USB cable, it locks the internal and external SD cards even when in menu mode without choosing "mass storage". In that state, I can't access them neither from the PC nor from the phone. I need to select "mass storage" then disable it again (already put it as default because of that), which is also pretty annoying because my car charger does fake a PC connection (probably because some devices won't charge otherwise).
Before OCLF, I could just ignore the popup menu for USB mode. I am just saying that, because it is another side effect of OCLF which can hardly be explained by looking at the source.
Click to expand...
Click to collapse
Wow, that's a totally uncommon behaviour from SGS!
How do you flash it? Do you use CSC+MODEM+PDA? Re-Partition?
Cheers, good luck!

Phk said:
Do you use CSC+MODEM+PDA? Re-Partition?
Click to expand...
Click to collapse
Yes, on both updates, all in one step.
But the strange USB behaviour was already present with factory firmware JF3 (after OCLF).
BTW: the Bluetooth problem doesn't happen very often, between once and three times a week I'd say.

PlanetJumble said:
BTW: the Bluetooth problem doesn't happen very often, between once and three times a week I'd say.
Click to expand...
Click to collapse
Yes, same as me. I have to use the fixer to restore connectivity... :\
About the USB, change your SGS using warranty....

Phk said:
About the USB, change your SGS using warranty....
Click to expand...
Click to collapse
I don't think so.
BTW: I moved from OCLF over to Voodoo (and to JM8). And it did solve nearly all problems. Bluetooth never crashed since (also didn't in a few days of Voodoo on JM7). Also now USB connection doesn't automatically lock the SD cards anymore.
And I noticed something else: OCLF prevents fonts from being rendered bold on certain web pages like Google Reader. Missed that before but I thought maybe Google removed the bold fonts to save space. I like it better with bold fonts though, glad to have them back.

Ongoing BT and OCLF Issues...?
Not sure if this is relevant, but I'll post anyway just in case it is and it gives someone else a eureka moment.
I'm on a stock Eclair ROM - JM2, I know, I've re-flashed it several times now...! - and have had no end of troubles with some combination of root, OCLF and/or the other XDA kernel mods that come with OCLF. I've ruled out the last of these by not changing scheduling or anything else from defaults; I doubt it's the first of them because I've tried a couple of different root methods. So it's probably OCLF itself, I just don't have the appetite yet to re-install everything only to screw it up again "to see if" ...
Anyway, rSAP carkit - pair, connect, everything is fine. Install OCLF, and within a day or two (and *perhaps* related to having to remove/reinitiate the ext2 partition because of the Kies sync issues), I get:
1. Carkit unable to see the 'phone at all (rare, may be unrelated)
2. Carkit sees, connects, but tells me there's no signal (dashboard shows blank signal bars, RNS510/Columbus head unit tells me there's no network) - but I can still make calls
3. Carkit sees, connects, but tells me there's no signal as above but genuinely means it: any attempt at calling gives a network error (most common)
4. Carkit and 'phone won't disconnect properly, so the 'phone is locked out of the network until you reboot it (rSAP borrows the SIM identity of the 'phone for the car, so if it doesn't give it back then the 'phone can't reconnect to the network - the handset thinks it has no SIM card). (every time)
I'm just rebuilding the handset (again) without any mods to see if the problem goes away, but I can't imagine it's related to any other application that I have installed.
Pity me and my poor, laggy handset.... if I find out more, I'll report back. I might have a look at the BT fix posted here (thanks in advance!) to see if that helps if the problem does reoccur... or try Voodoo, so long as I can do it without my wife spotting that I'm in the process of breaking that very expensive 'phone again

Questions about CM 6 stable

I'm pretty new in this and I know that probably most of you guys know how to fix these issues. I was running CM6 stable before, but after a couple of weeks of using it I had decided to go back to the sprint stock firmware. Now I am thinking of going back again to CM 6 so I would like to know if some of you can help me out and tell me how to do it. These are somes of the issues that I have had:
1. After some minutes of being using Bluetooth, it disconnects.
2. I had an issue with the gps similar to the one with the bluetooth (it gets disconnected after seconds to being connected)
3. The phone frooze up a couple of times after deleting a photo from the galery right after taking it.
4. Problems with the market. The applications were not downloading properly.
5. Issues to sync contacts with facebook, were not updating after sync the contact.
6. The text messages were not working properly when it was a long message.
Sent from my HERO200 using XDA App

zion69 said:
I'm pretty new in this and I know that probably most of you guys know how to fix these issues. I was running CM6 stable before, but after a couple of weeks of using it I had decided to go back to the sprint stock firmware. Now I am thinking of going back again to CM 6 so I would like to know if some of you can help me out and tell me how to do it. These are somes of the issues that I have had:
1. After some minutes of being using Bluetooth, it disconnects.
2. I had an issue with the gps similar to the one with the bluetooth (it gets disconnected after seconds to being connected)
3. The phone frooze up a couple of times after deleting a photo from the galery right after taking it.
4. Problems with the market. The applications were not downloading properly.
5. Issues to sync contacts with facebook, were not updating after sync the contact.
6. The text messages were not working properly when it was a long message.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
1. Unsure about this, I don't use it.
2. There is a fix for this that involves downloading gps status from the market. Details in the stable thread.
3. I think the gallery issue is still there, but only if you access it from the camera. Just exit out and then go to gallery.
4. Since I've updated my prl I haven't had the market problems.
5. New one for me, sorry, I don't know.
6. Download handcent. Set it to split 160 or more character texts. Then, it should work.
Hope this helps.
Sent from my CDMA Hero. I got some hot Froyo on Hero action here!

The newest Dec kernels fix the gallery issue.

Grab the latest nighty. They are now much more stable than the official stable. Darch is just busy and still hasn't made one of them official but I can tell you I'm on 89 and it never felt better.

stayclean said:
The newest Dec kernels fix the gallery issue.
Click to expand...
Click to collapse
Good call, now that you mention it, I haven't had gallery issues since I flashed one.
Sent from my CDMA Hero. I got some hot Froyo on Hero action here!

[Q] HeyTell App Issues

Is anyone else having issues using the app HeyTell? The only ROM i can get it to work properly on is the stock AT&T 2.1, it doesn't even work on the stock 2.2 update. Basically on stock 2.1 I can send and receive messages perfectly without missing a message or having to close the app. If I update to 2.2 or flash a custom ROM, I can send about 2 messages and then it stops sending or receiving, I have to close the app and then try to send the message again. Once I open the app again, whatever the person sent to me is lost and they have to send it again.
Just putting this out there, I have emailed the developer and they are stating that they have no issues. I don't know what else to try, I have cleared the app's cache, uninstalled and reinstalled, I am out of ideas.

I've never even heard of this app before... I'll install it now and tell you how it goes.
EDIT: Okay, I obviously have no friends on this at the moment... But I've been clicking around the app and it seems fine? I'm using Paragon RC6 right now. The GPS/Map component seems to be working fine anyway... I can't really send a voice clip or message through it (no-one to send it to).
EDIT2: Okay, I somehow sent a voiceclip/message to myself and I've recorded it, sent it, and then received it fine. I'll keep playing around with this a little bit further in the morning.

I really appreciate it, it will work at first, and then just stop sending and receving, the little sending icon just spins and spins...then you have to force close it and then start it again, then it works for a few messages and then stops again.

I'm having the same problem with the HeyTell app. It's pretty much hit or miss for me, sometimes it works good for a while, sometimes it sends blank messages. I have a ton of friends using this app on iPhones or other Android devices and they aren't having problems at all.

I have emailed the developer and he states that it works perfectly for him on his phone, whether or not that is true, I am not sure.

Not trying to thread jack but for some reason my hey tell doesn't get messages on time. I'll be next to a buddy and I'll get a message that he sent hours ago. Does anyone else have this issue? I just have the 2.2 froyo update, no custom roms.

I thought for sure HeyTell would work on Official 2.2 as well but I have the same issue your stating. Like I said though, the developer states he has no issues...I am not sure what is going to happen.

HeyTell Support
Are you sure you contacted HeyTell support? I don't have any record of sending a "works for me" answer on a report like this...drop me another email to refresh my memory at [email protected] if you can - thanks in advance!
So! We're aware of an issue on the Galaxy S series phones (Fascinate, Epic, Captivate, Vibrant) introduced by 2.2 firmware (Samsung only, 2.2 makes HeyTell better on other phones). Symptoms appear to be spotty network reporting, media player issues (inconsistent record behavior), and the OS killing HeyTell during screen dims.
We're currently working hard to find a workaround for affected users (and trying to get more info from Samsung), but in the meantime, if you could do us a favor and email us your firmware revision number and any logs you have related to the behavior, we'd greatly appreciate it!

Since I had the issue with Stock 2.2 and not with Stock 2.1 I am running Stock 2.1 until there is a fix. If your asking me for logs I cannot help you there unless I put 2.2 on my phone. i am currently running HeyTell version 181, I am willing to load 2.2 and work with you and get you information, just let me know. I love this app, but my phone is kinda laggy and slow running 2.1 and I want to be running 2.2.

I"m also using HeyTell on 2.2 and having quite a bit of troubles. I'd be happy to send you logs if you could explain to me how to do so. Thanks!

Just a little update, I finally got tired of stock 2.1 last night and decided to try out MIUI. I was pleased to find that after sending more than 10 messages back and forth, HeyTell has not failed yet.... I will be testing all day at work today, I am not sure if they updated the app or if something in MIUI allows it to work. I just thought I would update those few of you that have had the same problem as me.

Everything is still working fine with HeyTell, I am running MIUI Beta 6 and HeyTell is working perfectly. I did notice an update to from the market, I am hoping that could be a fix for other cutom Roms and Stock 2.2.

As MIUI has no samsung crap in it, it should work fine, since it seems to be a samsung issue. Runs fine on CM7 as well.

We put a workaround into builds 1.1.3 -- that fixed it for stock, but didn't catch all of the custom ROMs, so we spun 1.1.4 - give that a whirl and it should work. If anyone runs into this issue again, shoot us an email with your model number (Menu > Profile > Email Support sends this to us, so that may be the fastest method, but also don't forget to include a description of the issue you hit).

Oh sweet so HeyTell should be working fine now with stock 2.2? I will test it now, thanks alot!

Ever since I downloaded the update the app works great! Thanks!

Hey Tell Message Queue Issues
I've been having a problem for a while now where message don't come in automatically, as if they're caught up in the queue somehow. I have to exit HeyTell multiple times, manually click on the message, hit the stop and play buttons, or multiple combinations of all of these just to get a single message to play sometimes. I'm using a Samsung SGS3 with Synergy. Any way to fix this issue? Thanks much!

Gingerbread GPS slow fixing??

Since I received the Gingerbread OTA I have seen that when run gMaps it takes long time (minutes) to fix GPS. I think that is only for cold start, coz after fix if I close an restart the GPS it fixes in few seconds as normal.
I have tried with GPS Status but it seems everything OK.
Before Gingerbread it was really fast fixing both in cold and warm start.
Thx
Sent from my Nexus One using XDA App

I've also noticed the same problem. GPS seems to be much slower getting a fix on my position - even with a clear sky and at places it worked well before. Don't know if there's much I can do about it but hope for a patch from Google.

Seems that it's a very common issue, try to google " gingerbread slow gps fix"
Sent from my Nexus One using XDA App

Stock 2.3.3 ROM after OTA update, GPS only locked 1 out of 10 tries, and took a long time to do so. It is not even stable, and lost signal after a few minutes. I had looked everywhere including google forum, and there is no joy.
Finally read it somewhere to try GpsFix in the market and now GPS fixes in <10 seconds!

GPS-Fix Problem with Gingerbread
Hello,
i have the same problem after upgrading to Gingerbread 2.3.3. I have found this thread in the Google support forum (Search after this with Google):
GPS Navigation problems after Gingerbread update
and the issue is known aswell at Google issue tracking list (Search after this with Google):
NMEA Listener no longer working after upgrade to Gingerbread Issue ID 15500
The issue has been assigned medium priority over there. Maybe if more people can go there and star the issue, it will get up voted.
Sorry that i doesn't post the links directly, but its not permitted for me (not enough post so far)

The issue hasn't been assigned anything yet, the priority is 'medium' by default, once someone takes ownership of it, it should get a proper priority.

In the meantime you might like to try this:-
http://www.androidpolice.com/2010/09/09/gps-fix-for-cyanogenmod-6-on-the-nexus-one/
It works for me.
Hope it helps.

[email protected] said:
In the meantime you might like to try this:-
http://www.androidpolice.com/2010/09/09/gps-fix-for-cyanogenmod-6-on-the-nexus-one/
It works for me.
Hope it helps.
Click to expand...
Click to collapse
Yes, the GpsFix only worked for a few days, then the same problem surfaced again. So I followed the link and voila! now fast GPS fix again! Thanks!

Seems that 2.3.4 update fixed it...
Sent from my Nexus One using XDA App

I had the same problem on 2.3.4 and I fixed with the GPS Status, there is an option to clear all gps data. That worked for me, now the gps fix my position in a few seconds.

i used this
i have been using this [APP][ROOT] FasterFix [V1.5] - xda-developers. It needs root and also needs to be run once everytime i flash a nightly.
I get a fix in "seconds" rather than instantly. But i'm going to try that link posted above. You guys should check it out since nobody has mentioned it.
edit: on a second thought, i'd rather not try anything else because of the golden saying "if it ain't broke don't fix it" : )

That app will do nothing for the O2X, as it doesn't use the gps.conf file.
Anything it does is a placebo. CM7 now comes with a couple of GPS fixes, and that is probably the difference you're seeing.

[Q] kabaldans CM10 nightly - some issues

hey folks,
I have been following all the Milestone development threads since the very beginning, and have gone through each inkarnation of kabaldans incredible work since CM6. Recently, I updated to CM10 (first without, now with 2nd boot) and am absolutely amazed by how far our good old milestone has come. While playing around with it quite a bit, I have come across some problems (I would love to report them in the appropriate development thread, but the 10-post-count won't let me unfortunately.)
First, I really loved the keyboard multipress-system since I live in Germany and have to enter Umlauts very frequently (ä, ö, ü, etc.). The multipress-system sped that up greatly. Now, although the corresponding settings are there in the Milestone-specific part of the Settings-app, multipressing actually doesn't work for me in CM10. Is that problem specific to me, or is multipress not yet fully integrated in CM10?
The second thing I noticed (probably since 2nd boot, but I am not entirely sure) is, that in the Settings under About Phone > Status neither IME nor Serial number are displayed (instead, it says "unknown"). This also prevents me from launching Whats App - it quits saying "Your phone could not be identified ....".
Does anyone else experience those issues - and/or could perhaps somebody please post this into the CM10 development thread, so kabaldan notices?
thanks, mvol

mvol said:
hey folks,
I have been following all the Milestone development threads since the very beginning, and have gone through each inkarnation of kabaldans incredible work since CM6. Recently, I updated to CM10 (first without, now with 2nd boot) and am absolutely amazed by how far our good old milestone has come. While playing around with it quite a bit, I have come across some problems (I would love to report them in the appropriate development thread, but the 10-post-count won't let me unfortunately.)
First, I really loved the keyboard multipress-system since I live in Germany and have to enter Umlauts very frequently (ä, ö, ü, etc.). The multipress-system sped that up greatly. Now, although the corresponding settings are there in the Milestone-specific part of the Settings-app, multipressing actually doesn't work for me in CM10. Is that problem specific to me, or is multipress not yet fully integrated in CM10?
The second thing I noticed (probably since 2nd boot, but I am not entirely sure) is, that in the Settings under About Phone > Status neither IME nor Serial number are displayed (instead, it says "unknown"). This also prevents me from launching Whats App - it quits saying "Your phone could not be identified ....".
Does anyone else experience those issues - and/or could perhaps somebody please post this into the CM10 development thread, so kabaldan notices?
thanks, mvol
Click to expand...
Click to collapse
I have issue like this, and I can see IMEI and IMEI SV, but the Serial Number is "unknown".

after doing a full wipe, IMEI now shows up for me as well, but unknown serial and multipress problems remain.

mvol said:
hey folks,
(I would love to report them in the appropriate development thread, but the 10-post-count won't let me unfortunately.)
Click to expand...
Click to collapse
You are almost at the 10th post.
Maybe wiping everything is a solution for that?

mvol said:
hey folks,
I have been following all the Milestone development threads since the very beginning, and have gone through each inkarnation of kabaldans incredible work since CM6. Recently, I updated to CM10 (first without, now with 2nd boot) and am absolutely amazed by how far our good old milestone has come. While playing around with it quite a bit, I have come across some problems (I would love to report them in the appropriate development thread, but the 10-post-count won't let me unfortunately.)
First, I really loved the keyboard multipress-system since I live in Germany and have to enter Umlauts very frequently (ä, ö, ü, etc.). The multipress-system sped that up greatly. Now, although the corresponding settings are there in the Milestone-specific part of the Settings-app, multipressing actually doesn't work for me in CM10. Is that problem specific to me, or is multipress not yet fully integrated in CM10?
The second thing I noticed (probably since 2nd boot, but I am not entirely sure) is, that in the Settings under About Phone > Status neither IME nor Serial number are displayed (instead, it says "unknown"). This also prevents me from launching Whats App - it quits saying "Your phone could not be identified ....".
Does anyone else experience those issues - and/or could perhaps somebody please post this into the CM10 development thread, so kabaldan notices?
thanks, mvol
Click to expand...
Click to collapse
Hi mvol,
I am running the new CN10 10/24, the seril reports also Unkown but it doesnt stop me from running and using WhatsApp app.
regards
EP

WhatsApp now works - it looks like the full wipe which solved the unknown IMEI problem also fixed WhatsApp.

mvol said:
WhatsApp now works - it looks like the full wipe which solved the unknown IMEI problem also fixed WhatsApp.
Click to expand...
Click to collapse
Realy ? I will have a try !

I also went through this and really soh after giving a factory reset was decided that in fact

have you guys tried multipress using the hardware keyboard? Does it work for you?

mvol said:
have you guys tried multipress using the hardware keyboard? Does it work for you?
Click to expand...
Click to collapse
here using the shift and alt is working normally above 2 keys simultaneous ... not tested on that specifically, you will use more than 2 simultaneous keys?

with "multipress" I mean the feature invented by nadlabak/kabaldan that allows one to press the same key multiple times very quickly to enter special characters (like pressing "a" two times very fast producing "ä", for example.) It worked perfectly for me in CM7, but it doesn't anymore in CM10...

anyone, please?

It works fine for me. I use it frequently.

mvol: I still haven't found the time to implement the multipress feature completely in CM10. Only a few of the final bits is missing. Please be patient.

thanks for your answer - in that case, I'll wait patiently

Link not working for me
Hi All,
Im unable to access the latest builds for milestone CM10 by kabaldan. Please can anybody provide alternate link?
Thanks

Hello people!
I'm a long time CM ( 6 and 7 ) user on my Milestone.
After updating it to CM10 ( full wipe, ext3 partition formatted ), adb does not find my device anymore.
I have changed the USB settings and enabled the debugger in development, but nothing changes. Even after a restart.
Running on Ubuntu 12.10.
Any ideas?
Thanks!

The issue I have is quite annoying, if I can use such a word in a development stage . After each restart, the network is being forgotten, so I have to switch to the airplane mod off and on.

@pt0: This is a known issue, if I can say that. I experience this too, though not after every restart. I think it's a problem we can live with.