Database Develop

working Android on TOPAZ

Hi,
can someone help me with my issue with Android ?
It doesn't work after LOOOONG boot:
1. camera
2. Wifi
3. GSM module + data connection
This things are the most important for me and it doesn't work.
Do you have tips because this procedure upwards doesn't work.
I configure it with this procedure from samsanchez88:
http://forum.xda-developers.com/showthread.php?t=641021&page=154
Or do you have some other procedure in which will work: GSM module, GPS, WIFI and Camera ?
Thanks for help.

GSM Fix
In the Setup.txt you will notice close to the end there is a command Force_CDMA=1 change the 1 to a 0.
As far as the WiFi, It works fine on mine so does the WiFi Router.
Camera is not working yet.

Smleth said:
In the Setup.txt you will notice close to the end there is a command Force_CDMA=1 change the 1 to a 0.
As far as the WiFi, It works fine on mine so does the WiFi Router.
Camera is not working yet.
Click to expand...
Click to collapse
Does will somebody fix the camrea problem or rather will fix this issue in Android 2.2?
Does the data connection works on your Topaz [ EDGE, UMTS, HSPDA ] ?

Currently zImage or kennel for topaz is incomplete, despite xdandroid builds are working fine on other devices except camera, such as original diamond. So, topaz has some functionalities being worked on.The lastest achievement is gps(buggy) and slight power management.The camera is not even supported by android according to xdandroid page. This does not seem to be zImage problem.
If you want most complete bleading edge kenel drivers and fix bugs, go to glemsom.anapnea.net/android/htc-msm-android/ and read people's comments and download accordingly.(some builds are screwed bewarned)

Camera
So Camera will never work on TOPAZ ?
It doesnt work the data connection why ? It also doesn't work ?
Why doesnt work moutUSB as external storage ? It also doesn't work ?

devs are working on everything.
camera support is comming that is only thing not supported by haret android system yet.
mount usb does not work because simply you cannot afford to give sd card to pc while you are using it. That does not mean impossible as devs are again working on it.
data is actually working go above link to replace zimage with latest version(do read people's comments if data is working. ) and it should work. is sad that shadowline abandoned the thread and android devs are seem to be working more on bringing leo to android instead of topaz...
go wiki and read advanced user section pls....

1. Do you know when exactly will work the camera [ in 2 months, 3 monts, 4 monts ] ?
2. It have sense to work as function "mount usb" - flash disk, I use it on Win Mobile everyday as flash disk. Do someone of devs want work on it?
3.Will someone work also on the power managment that the device can run at least one day ?
4. Why doesn't work the speaker or headphones when I play music ?
Thanks for info.

As squarememory says, the developers are working on all this issues. Porting android and a linux kernel to this phones is not a simple job. The kernel support general hard, but the config for the phone is very specific. Adjusting drivers to work with the phone's hard implies a lot of work.
Grab a seat, take it easy, they are doing an excellent job, and when they got issues solved, you gonna see the results reflected in the repos.

I know that they are doing goog job but can you tell me just rough estimation when main bugs [ Power, Camera, SOUND from speakers or headset ] will be solved ?
Thanks.

Mate, no one is paying them to do this, they're not a company or selling this as a product. And like everyone else they have a Real Life, a job, family, etc.
That will be ready when they have time and when they can solve the problems.
1 day, 20 years or never. No one will never know, so try help instead of asking when or why because no one here have the obligation to do it.

Dude, I know they do that for free and have theirs lives. But human is not patient if something like and that's my story. I appreciate their work because it's amazing to run different OS on the same phone.
That's it. I didn't want to bother anyone.

be patient or buy an andriod device.

I know the answer. And it is... "nobody knows"
Porting is a serious job, which requires TONS of inspiration, time and knowledge. Let's suppose "knowledge" is a fixed value (at least not decreasing during the process), but "time" and "inspiration" can't really be estimated.
In other words, it's a hack and it will be there... when it is ready

for this to work you'll need to have the latest "modules-*******" for topaz file

@ all
For connection with sd-card and management about android,read this thread.
With the last kernel and XDAndroid it works like a charme.
http://forum.xda-developers.com/showthread.php?t=815940
greetz
pego2007
Only thing that not working on my topaz is the camera,but i hope they can fix it soon.

Sprint Users Whats not Working 2.1?

Being a sprint user myself upon the camera development this morning (still needs work but something is better than nothing)
i have come to realize that Eclair and Android on The Sprint HTC Touch
is very close to complete.
only things left that i know of are:
bluetooth audio (music playback)
video recording
Video playback
but i want to see if anybody else has found anything.

thoughtlesskyle said:
Being a sprint user myself upon the camera development this morning (still needs work but something is better than nothing)
i have come to realize that Eclair and Android on The Sprint HTC Touch
is very close to complete.
only things left that i know of are:
bluetooth audio
and video recording
but i want to see if anybody else has found anything.
Click to expand...
Click to collapse
bt audio works for calls.

Yea I know it is but not for audio routing so you can't listen to music through it

Video playback is also still not working.

I'm running the super eclair from incubus
Well the camera on mine still isn't working after the update. It loads but when i take a picture it crashes.
I'm very new to this so I'm trying to learn as I go.
but also I'm not receiving text for some reason, everything else seems to be working fairly well.

diabolicalnyc said:
I'm running the super eclair from incubus
Well the camera on mine still isn't working after the update. It loads but when i take a picture it crashes.
I'm very new to this so I'm trying to learn as I go.
but also I'm not receiving text for some reason, everything else seems to be working fairly well.
Click to expand...
Click to collapse
Text messaging is a known issue with super eclair. It works on other builds.

cool now that the camera is working does everyone have MMS setup to send?

acegolfer said:
Text messaging is a known issue with super eclair. It works on other builds.
Click to expand...
Click to collapse
He mentioned it was.
maybe i'll try another one. I really like his version but text is pretty important.

My phone specifies that its a Tmobile my touch now after upgrading it to Myn’s Warm Donut Android 1.6 with Prodical Sun Theme. Also I get a MMI code issue. What should I do to fix this.

Tsvallette said:
My phone specifies that its a Tmobile my touch now after upgrading it to Myn’s Warm Donut Android 1.6 with Prodical Sun Theme. Also I get a MMI code issue. What should I do to fix this.
Click to expand...
Click to collapse
its always going to say my touch 3G, thats just what he has the build set to recognize the phone as, it shouldn't cause any problems
i have no clue what an MMI code is so im not sure

This is day two of going back to this phone and I dont have any data connection. In two more days according to Sprint I should have 100 percent access to whats on my account. I hope I have data connection soon. If I dont have it back by then I will be posting it here. I miss my data connection!

Tsvallette said:
This is day two of going back to this phone and I dont have any data connection. In two more days according to Sprint I should have 100 percent access to whats on my account. I hope I have data connection soon. If I dont have it back by then I will be posting it here. I miss my data connection!
Click to expand...
Click to collapse
what happened there, was your Data working before you flashed to android?

I have the Vogue and the Titan. I switched from my Vogue to the Titan due to some minor issues and now my Titan is doing the same thing. Before switching back to my Vogue I flashed the rom with the Android, liked it alot and then called up sprint and did a switch back to my newly improved Vogue. According to the sprint rep it will take upto 4 days for all provisioning to be complete. As of right now I have it all working except for the data. My phone doesnt even show a data connection and when it tries to access something via internet it says "You don't have a network connection. Ths could be a temporary problem or your SIM card may not be provisioned for data services. Please try again when you are connected. If it continues, call Customer Care."
Ohh yah, *2 and *4 doesnt work. I was going to call them today to see if they could speed things up but cant call them this way.

Tsvallette said:
I have the Vogue and the Titan. I switched from my Vogue to the Titan due to some minor issues and now my Titan is doing the same thing. Before switching back to my Vogue I flashed the rom with the Android, liked it alot and then called up sprint and did a switch back to my newly improved Vogue. According to the sprint rep it will take upto 4 days for all provisioning to be complete. As of right now I have it all working except for the data. My phone doesnt even show a data connection and when it tries to access something via internet it says "You don't have a network connection. Ths could be a temporary problem or your SIM card may not be provisioned for data services. Please try again when you are connected. If it continues, call Customer Care."
Ohh yah, *2 and *4 doesnt work. I was going to call them today to see if they could speed things up but cant call them this way.
Click to expand...
Click to collapse
yea so i have an easy fix to your problem, flash back to windows mobile once its back an loaded access the internet, it should do some sort of dialing #777 thing then flash back to android after IE loads any sort of web page.
you should be perfectly provisioned right now the max it usually takes is like 24 hours, although i do still have nightmares from my days as a service tech provisioning those sprint Direct Connect phones
but yea so if you were in android before you activated the phone thats why you dont have data

Thank you. I relized that I would probable needed to do this but I didnt want to if there was a easier way to resolve this issue. I recall that I needed to do this when I went for stock rom to nfs 6.5 and had no internet as well. I then needed to load the 6.3 rom and then back to 6.5. This time I reverted to the 6.3 nfs rom and straight to this one.

okay so I am super new to this...i have a sprint vogue and i am running the zen-hero files from my sd card...I cannot get my caller id to work to save my life...it shows just numbers when someone calls me please help...

LEAKED *7/27* Stock 2.2 ROM - **CONFIRMED BUGS**

The original thread is a complete mess and it's impossible to find posts detailing CONFIRMED bugs. Let's try to keep general discussion of the leaked 2.2 ROM in the original thread and use this thread for bug reporting.
THIS IS NOT FOR HELP/PROBLEMS WITH INSTALLATION OF THE LEAKED ROM. Only post here if you have the leaked ROM up and running and have encountered a bug.
Post here you think you have found a bug. If it cannot be repeated by multiple users, it's not a confirmed bug, but more likely an improper installation or software conflict of some sort.
If a potential bug is posted by someone and you can repeat it, please quote the original post of the bug report and "Confirm" in body of your post. If multiple people can confirm that they can repeat the bug, I'll update this post and list it. If someone posts a bug and you know a fix, quote their post with your fix (or link to thread with fix) in the body of your post.
I'll try to keep this OP updated with a list of CONFIRMED bugs and fixes if one is known. If your bug is already listed here, please don't clutter up the thread by posting it again..
CONFIRMED BUGS:
1) Some purchased apps will not show up in the Market. Fix here
2) Multiple reports of recording in 720p in the camcorder causing a FC or screen freezing
3) Multiple reports of problems with MMS:
a) Handcent seems to work fine (no reported problems with MMS)
b) Stock Messaging appears to be hit-or-miss (MMS works for some, not for others)
c) Chomp seems to work for some people, not for others
4) Original Gmail app has some issues, puts a 0 at the top of messages and gets messed up during some replies. Fix:Install working gmail.apk (Fix here:http://forum.xda-developers.com/showthread.php?t=738188)
5) Browser FC when hitting the back button while inital page is still loading (confirmed by multiple users)
6) Streaming Audio Quality: "decline in audio on pandora as i listen to it bluetoothed to my stereo and now the sound has a major decline in quality" FIX: there is a patch for that works, but it hurts the Quadrant benchmark score. the linpack score remains the same and the phone still feels just as fast though. Fix here. Use the UPDATED fix, not the original one (original one is only for fixing Market)
7) Swype: multiple users report that Swype will stop working (cannot "swype", only tap keys) after reboot. Others report no problems. Sounds like a Swype install problem for people having trouble? FIX: Toggling Input Method off Swype and back on Swype seems to fix the problem.
8) Multiple reports of data connection dying off. lower bars on data then dropping from 3g to 1x speed. Intermittent WiFi connection dying as well.
9) Multiple users report poor battery life

4) Original Gmail app has some issues, puts a 0 at the top of messages and gets messed up during some replies. Fix:Install working gmail.apk (Fix here:http://forum.xda-developers.com/showthread.php?t=738188)
Beat me to it, but theres the link to the thread that fixes it.

Making more threads about the same things makes it even harder to find information.

acidbath5546 said:
Making more threads about the same things makes it even harder to find information.
Click to expand...
Click to collapse
very true !!!

If someone sends me a list of confirmed bugs and fixes then I'll add it to the main thread.

lets mention the streaming audio quality. there is a patch for it that works, but it murders the Quadrant benchmark score. the linpack score remains the same and the phone still feels just as fast though.

I've had 3G not turn on from a reboot now twice. Had to reboot to get it to work.

hrm
I couldn't get backup assistant to work, it won't connect.

delete my post please

Sending is fine. That's my fault. I'm an idiot.

Browser FC when hitting the back button while inital page is still loading

My phone has been running slower and hotter since flashing the 2.2 leak

Maybe add to #4 about Gmail that once you copy the fixed gmail.apk and reboot, you may get infinite Force Closes from Gmail. It happened to me. The fix is to go to Settings -> Applications -> Manage Applications -> All -> Gmail -> Clear data. Then you'll have to open Gmail twice to get it to work.

When connecting to a PC with a data cable, and going into disk mode, I am only able to access the phone storage, and not the sdcard.

I have received a few MMS messages in Chomp tonight and they have worked fine. Not sure what that bug is about?

Quick question, does anyone have the ACTUAL 2.2 OTA update that is signed and completely untouched from HTC that would flash using a stock recovery? All we seem to have is the modified / rooted version, ide like the legitimate copy if possible

Joe92T said:
Quick question, does anyone have the ACTUAL 2.2 OTA update that is signed and completely untouched from HTC that would flash using a stock recovery? All we seem to have is the modified / rooted version, ide like the legitimate copy if possible
Click to expand...
Click to collapse
Of course its out there. However you won't have root if you use it. The rom is EXACTLY the same as if you applied the OTA. Except a little older radio and you get to keep root.
Plus it has the same bugs... At least VZW/HTC knows what bugs this has, 5300 beta testers so far. The official OTA should be flawless.

Anyone else having an issue with Wifi? I installed the new radio, rooted and installed 2.2 as advised. Everything appears to be working fine for me (camera, Market, etc..) but when I attempt to connect to the same router that was working when using 2.1 it keeps looping at 'Obtaining ip address ...' but will never establish a connection. I googled Froyo 2.2 wifi obtaining ip address and got several hits for other phones running 2.2 but nothing so far for the Incredible. Any thoughts? Anyone able to get wifi working?

jfair9 said:
Anyone else having an issue with Wifi? I installed the new radio, rooted and installed 2.2 as advised. Everything appears to be working fine for me (camera, Market, etc..) but when I attempt to connect to the same router that was working when using 2.1 it keeps looping at 'Obtaining ip address ...' but will never establish a connection. I googled Froyo 2.2 wifi obtaining ip address and got several hits for other phones running 2.2 but nothing so far for the Incredible. Any thoughts? Anyone able to get wifi working?
Click to expand...
Click to collapse
I never once had any issues with wifi. Grab the logs and send 'em to me and I'll see if I can find anything.

I'm noticing an interesting thing with Swype. After most reboots I can not "Swype" only use the keyboard. The workaround is to change my input method back to the stock keyboard and then back to Swype and it works fine. Anyone else noticing this?

[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

[Q] No 3g with CM 10.1 plus some other less severe issues

Greetings,
Just a few days ago I installed the most recent CM 10.1 nightly, first 20130319 and now updated to 20130323. For the most part, my phone is working well, but I do not have any 3g data service nor have I had it since installing CM 10.1.
I have a Droid 3 XT862 being used in the US on Verizon's CDMA network and placing and receiving calls works. I *can* send and receive SMS as well, although in a test I did toay I sent very short 25 character text from my Droid 3 on the Verizon network to another Android device on the Sprint network and it arrived a mere 2h15m later.
I have read many messages on this forum and others, but either the problem addressed is too far removed or the ideas/changes suggested are offered with little explantion as to why, so I am unsure if making any of these changes would be a good idea. I did read through the build.prop on my device and it certainly appears that it is more or less configured and ready for CDMA usage. I have performed a *228 PRL update, but it did not appear to help. CM 10.1 makes available, unlike the stock ROM, a menu/page full of mobile network settings. I have tried to work with some of these settings, toggles, preferred network types, and so on, but again none of these changes seems to have had an effect on my 3g data connection.
Am I doing something wrong? Does anybody know how to fix this? Or perhaps it is a new/temporary bug in CM 10.1?
As for the operation of everything else under CM 10.1, I like it very much. It is a very big step up from before, when I was first using stock Android 2.3.4 followed by the Maverick ROM, which, while better, sure liked to crash/reboot when under memory pressure. I do have a few issues that I hope others might be able to help with:
* The hardware keyboard's ALT key does not appear to work anymore which rules out half the symbols on the keyboard, making it far less useful. I also cannot use it any longer with VX ConnectBot as some of the mappings do not seem to work. For example, the "OK" key used to work as a CTRL key. Maybe these are related? Any idea how to fix this?
* The backlight on the hard buttons and on the keyboard was, previously, triggered by a light sensor (I think). Now the backlight comes on when there is any tapping, swiping, or button/key activity. That's fine, except that the timeout for the light is extremely short, on the order of about two seconds. In a dark environment, this can be annoying.
* It's slow... my god is it slow! I think this is due almost entirely to a severe lack of free RAM on the device, but I don't know what to do about it. Some programs, like GMail, take forever to start, while many others are just very slow to use/respond. I see the "Not Responding" popup appear *much* more than ever before, but, as I know these apps are just slow and not dead, I always just tap on "wait" and go on with what I was doing.
I really don't think I have that much running in the background or foreground to use all of this RAM. I have replaced Trebuchet with NemusLauncher in hopes of freeing some memory. I have three widgets only: a clock/weather widget, the standard calendar widget, and the Google Voice inbox widget. In the background, besides whatever Android and CM run, I have Google Voice and imo (the instant messanger) running. I believe that is it. Is there *anything* I can do to improve the speed issue? I understand how Android handles memory, so it is clearly not about just increasing the "free RAM" value. That said, however, it seems that if there were fewer apps trying to use the limited memory then this would naturally be higher to begin with.
I have a decent collection of apps, but the number is much smaller than in the past and most all of them should remain dormant unless I actually run them... or so I believe.
Okay, so those are the issues. I could add battery life and the camera to that list, but I have read on the forum that, no thanks to Motorola, the camera is unlikely to be available anytime soon, and I have also read that the battery issues should be resolved soon.
So, um... please help! And great many thanks to all of the hard working devs who bring us better software and especially to those who help those of us with devices that are practically *new* and yet abandoned by the carriers. Extra kudos to those finding ways to work around locked bootloaders and proprietary binary blobs.
--John Gruenenfelder

Can you force it to EVDO only? And what happens in a stock ROM?

In the mobile network settings page, as mentioned above, I can, and have, tried many of the options. Among them is the preferred network type.
It defaults to 'global' which actually sets it to LTE/CDMA, though this is not an LTE device. I have tried all of the options that make sense (i.e. nothing GSM related). I have tried Evdo-only and currently have it set to 'CDMA/Evdo auto'.
None of these settings has changed anything. To test, I disable WiFi and see if I have a Net connection.
With the stock ROM, as well as the Maverick ROM, when I have 3g, the letters '3g' appear in the status bar next to the mobile signal strength icon and there are two small arrows to indicate I/O. This is what I expected to happen with CM.
-Sent from my XT862 using xda app-developers app

I have a 3g update, but no solution yet.
In the mobile net settings page I have the network set to 'CDMA/EvDo auto'. Then I turn on airplane mode to force the radio off, then turn airplane mode back off.
The radio comes back and as it does I can see the network strength icon briefly add an R, presumably meaning reconnecting, followed by a 1x, and finally by a 3g. Then the 3g disappears. This entire sequence takes only about 3 to 5 seconds. If I do this while viewing Settings->About->Phone, I can see the current radio/network states change. Of course, I do all of this with my local wifi connection off.
Also, I did try a network type of 'EvDo only' and the above sequence still occurred but without the 1x step. However, this sequence didn't seem to occur as reliably as when the network is set to 'CDMA/EvDo auto'. For reference, the phone info page under settings indicates that this phone or network is 'CDMA - EvDo rev. A:6'.
So, it would seem 3g is at least possible, if fleeting. What should I do now? I really don't want to stop using CM 10.1.
--John Gruenenfelder

Same issue here. No 3g. In the system status, it will briefly show the mobile network status as "connecting" then drop back to disconnected.

If you reboot into stock it works right?

MrObvious said:
If you reboot into stock it works right?
Click to expand...
Click to collapse
Me or rocksolid99?
In my case, I, well, did not follow the correct Safestrap update procedure when I went from 1.x to 3.05. As such, I *think* my stock ROM may be slightly hosed. I *do* have a complete backup of the original stock that I created with Safestrap 1.x, but 3.05 does not "see" it when I tap on the "Restore" button in recovery. So, I have it, I'm just not sure what I should do if I really need to restore that backup.
However, I have installed the Minimoto 1.7 ROM into slot 2 in Safestrap 3.05 and if I use that ROM (which is a super stripped down Droid 3 stock) then 3g works just fine. I did not have any network/connection issues and did not need to take any extra steps to get 3g to work.
--John Gruenenfelder

I'm pretty sure data has not worked in cm10.1 since 3/11 build.
Sent from my XT860 using xda premium

Endoroid said:
I'm pretty sure data has not worked in cm10.1 since 3/11 build.
Click to expand...
Click to collapse
Really? Good to know. Thanks for the info.
If I might reiterate on my other CM 10.1 problem, they keyboard? Right now, the ALT key does not work which means that I cannot access most of the punctuation keys. Strangely, in many apps when I press ALT I will see the cursor change with the upside down triangle at the top of the cursor bar indicating that ALT has been pressed. Good, but if I press any other key it is not recognized. It is as though I had not pressed anything. The ALT indicator doesn't even change or go away. The only thing I can do is continue to press the ALT key to cycle through its states (off, one-key, locked). Could this also be a bug in CM 10.1?
Is there a better or more correct location to submit these issues? Since these issues are/may be bugs in CM 10.1, should I not submit a bug report directly?
Beyond the 3g/data and keyboard issue is the RAM usage. It uses a *lot* of RAM. Is this just the way it is? The Droid 3 lacks enough RAM to really make a serious go at Android 4.2?
Thanks again!
--John Gruenenfelder

JetpackJohn said:
Is there a better or more correct location to submit these issues? Since these issues are/may be bugs in CM 10.1, should I not submit a bug report directly?
Click to expand...
Click to collapse
As a matter of fact, there is: http://androidhosting.org:8050/projects/device-motorola-droid-3-xt862
Hashcode tweeted that last night...
Beyond the 3g/data and keyboard issue is the RAM usage. It uses a *lot* of RAM. Is this just the way it is? The Droid 3 lacks enough RAM to really make a serious go at Android 4.2?
Click to expand...
Click to collapse
When Motorola hinted that this was the reason why the D3 and X2 would not get ICS, nobody believed them.
I think it's pretty clear that CM on the Droid 3 at the moment is alpha/beta status. If you want stability and full features, you need a Gingerbread ROM. Minimoto is best for me.

doogald said:
As a matter of fact, there is: http://androidhosting.org:8050/projects/device-motorola-droid-3-xt862
Hashcode tweeted that last night...
When Motorola hinted that this was the reason why the D3 and X2 would not get ICS, nobody believed them.
I think it's pretty clear that CM on the Droid 3 at the moment is alpha/beta status. If you want stability and full features, you need a Gingerbread ROM. Minimoto is best for me.
Click to expand...
Click to collapse
+1 anything above gingerbread is not stable. Some people manage to use them for daily drivers but they have to deal with the bugs. Myself, I need a camera and I need my phone to work all day, I use it for my job. As such, I run minimoto, as it is quite stable, and any bugs that do arise can be dealt with as it's based on gingerbread, which is stable on our devices. Liberty is also a good rom to use, it's based on an older system version but it's quite stable and has lots of features, as opposed to Minimotos minimalist goal.
Sent from my XT860 using xda premium

has anyone tried making a swap partition for cm10.1 ?
I made it and it seems to be much much faster or the latest nightly (04/07/2013) is quicker.
anyhow I have it up only for about an hour it remains to be seen during the day how it's reacting
regards

Endoroid said:
I'm pretty sure data has not worked in cm10.1 since 3/11 build.
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Have you (or has anyone) successfully booted CM10.1 on the XT860? I just get bootloops after install. MiniMoto has been working great for me though.