Related
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
Hello every one.
I'm the proud user of a HTC Touch Diamond. It has served me well since day one, and now i want to make it even better.
I need the phone to work. And i need Android (read: want). So i'm asking everyone which version do you find more stable. What i need:
Phone. Must work. Must work well. Cannot wait 20 seconds for the device to wake up (while ringing) to show me who's calling me. When i decide to pick up, the other guy gives up, or the call os forwarded to voice mail.
Wifi is a must, that sim has no data plan.
Battery, though superficial due to a 2400mAh bat, it takes alot of calls and sms's.
Market. Must work.
Camera is a bonus, helps here and there.
The rest is rest. i don't need bluetooth, GPS, or anything like that. Anything from 2.1 forward is enough. So... i'm open to suggestions.
I did this same question of the kaiser section, and was greeted with 2 very stable versions. One Eclair and one Froyo.
froyo b ver 6
it is very stable
and the 3d performance is better than the old version
url http://forum.xda-developers.com/showthread.php?t=970476
I'm getting 21FPS (diam100) and 20.2FPS (raph100) with NeoCore with no overclock and camera+camcoder works great
I'm currently using that one.
Though "snappy", its quite slow. Market is a pain. (Wifi)
Takes too much time to wakeup and show the screen (i actually have to unlock to see the screen).
Looking for something else maybe. 3D isn't a must.
I've got three different Android ROMs form different developers and the fastets and most stable ROM would be http://forum.xda-developers.com/showthread.php?t=907509
additions like camera or WiFi works fine for me.
Gingerbread 2.3.3 from March 11th running on my (old and outdated) HTC Touch Diamond 2 (Topaz). Was surprised how fast it is running - no crashes so far.
To get it running on your device please follow following basic instructions:
Extract XDA's FRX05 to the ANDBOOT folder of your SD card (yes it is Froyo 2.2.2 but we will update/replace it in step 2)
Replace the existing system.ext2 with the one you should download from southcape.org. first post, you can't miss is, version from march 11th. In this step we replace Froyo 2.2.2 with Gingerbread 2.3.3
Install newest Glemsom kernel (my choice: htc-msm-linux 20110228_202832)
Replace the existing rootfs.img with the newest one (my choice: rootfs-20110224-3dd92b8.zip), otherwise your device will not boot
Change startup.txt to your needs. I added pm.sleep_mode=1, otherwise my device would have wakeup problems
Tested & working:
Incoming/Outgoing Calls (in active & sleep mode),
WLAN/3G/2G,
Exchange (Email, Calender & Contacts) with push,
Gmail (Email via k-9, Calender & Contacts) with imap idle /push,
No wakeup problems after sleep
Hope I was able to help somebody
bean
------------------------------
Gingerbread 2.3.3 (South Cape/xda, March 11th)
Touch Diamond 2 (Topaz)
Kernel: Glemsom's 1276 & modules-2.6.27.46-01276-g6a6a1c1.tar.gz
Sleep mode 1 - no wakeup problems for a long long time
Did you something special to run 3G data?
I took a complete build which was posted in the froyo thread. everything else is fine, especially the performance up to now
Good write up for people new to XDAndroid. But for people who do not want to take the time, here is the link to my bundles, where all of this is done in a bundle or you can use my system.ext2 files that are more recent builds from xdandroid git. These also have camera working
http://forum.xda-developers.com/showpost.php?p=12205814&postcount=6063
freakatzz said:
Did you something special to run 3G data?
I took a complete build which was posted in the froyo thread. everything else is fine, especially the performance up to now
Click to expand...
Click to collapse
Do you have a cdma or gsm phone? if you have a cdma phone you need to add force_cdma=1 to your startup.txt
I did the exact same things as mentioned in post 1. The build is somehow unstable for my Topaz (Topa100). I have problems with sudden sleep freezes, no real Data Transfer trough the Cell Network. I cannot use 2G somehow, but really i have no idea what i am using. I have the feeling some of the upper bar icons are not even present with my device. I have only 3 icons active. Not a single one showing the Network type.
(i am not sure if standard android multitasking works with XDAndroid, if yes, i cannot access it)
The battery drains itself very fast. The phone enters sleep mode, but after some time the Led indicator goes orange. The phone gets hot, evidence that something is running on the device.
I don't have any ideas, what, where .... i really want to see a video of a stable working Topaz with latest build , so i know what is missing on my device.
Running 2.3.3 on Topaz
Hey, I've been running the 2.3.3 latest build (thanks The Jokah for the post).
Unfortunately there are a few kernel related issues and hardware sometimes won't turn off or be 'off' at all. Plus porting the OS will usually require more resources and processor power which means less battery life. (I hope I am at least remotely correct in saying that)
I've had a few crashes when receiving calls at first but as you can see below I have the settings tweaked to fix that, and i make sure to place an outgoing call first thing after booting. The only thing I haven't got to work is GPS which may or may not ever be fixed (thanks for those of you working on it) My camera and everything else runs smooth even though I'm underclocking it for protection.
I've run most common apps and some others like FB, Skype, Weather Bug (w/o auto location enabled)...I even ran Angry Birds and Fruit Slice.
so all in all its a really excellent build but still has the obvious issues when trying to run an OS package on hardware that wasn't originally developed for it.
I get on average with internet use 5 to 10 hours of battery life so good luck on that end.
Justin:
HTC Topa160 with qualcom 528MHz
Carrier: AT&T
Crappy ram and such
Crappy internal Storage and such
4GB SD external
WinMo 6.5 Rom 2.31.502.4
Radio 4.48.25.20
Protocol 61.39tc.25.30H
Rooted
XDAndroid Gingerbread 2.3.3 Latest Build (and shtuff)
Startup
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2293
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off hw3d.force=1 force_cdma=0 acpuclock.oc_freq_khz=500000 sensor=topaz pm.sleep_mode=2 rel_path=andboot"
boot
your bundle packages doesnt work for me. After run haret and it freezed before get into linux.
bkcheah75 said:
your bundle packages doesnt work for me. After run haret and it freezed before get into linux.
Click to expand...
Click to collapse
Sorry I mean bundles provided by "TheJokah" doesnt work for me. I follow 'Bean+' guideline and gingerbread working well now.
Just battery running fast.
bkcheah75 said:
Sorry I mean bundles provided by "TheJokah" doesnt work for me. I follow 'Bean+' guideline and gingerbread working well now.
Just battery running fast.
Click to expand...
Click to collapse
my bundles are the same as his writeup, but with all the latest files from source. they should work the same
wow - this version is very nice.
---------------------------------------------------------------------------
- when i press the original power button it is not the "home" button
it does the same function like the "end call" button.
answer:
Q. Why does the end call button has the same function as the power button and how do i fix this?
A. The key mapping was changed in a recent rootfs release, to sort that out go into the Main Menu -> SpareParts and select the "End button behaviour" to be "Go Home".
Click to expand...
Click to collapse
---------------------------------------------------------------------------
Q: how can i root this version? (z4root?, SuperOneClick?)
---------------------------------------------------------------------------
Q: As i toggle WLAN, it doest' work - sometimes yes, sometimes no
E-P-S said:
Q: how can i root this version? (z4root?, SuperOneClick?)
Click to expand...
Click to collapse
All the Android ports around here are already rooted.
E-P-S said:
Q: As i toggle WLAN, it doest' work - sometimes yes, sometimes no
Click to expand...
Click to collapse
It always toggles on/off properly for me when I have it turned on from WinMo before using haret.
However, sometimes it turns on, connects to my home network but doesn't really work (no data transfer), disconnecting from and reconnecting to the network seems to fix that.
Rooted
Yes You Right. Big Thanks.
I've installed now:
-Root Checker
-Droidwall
-Superuser
and Titanium Backup
Slow
After the boot, very slow in my case
Cannot do anything
I am very excited! The system is very fast. and battery life is very good!
Good work!
But I have one problem after booting, most applications do not see the sd card as Android Music and Gallery
If you know how to fix this problem, I will be very happy.
Thank you very much, this solved my problem, too. But how can ich activate the task manager, when the home button isn't working like it should?!?
krigav said:
Thank you very much, this solved my problem, too. But how can ich activate the task manager, when the home button isn't working like it should?!?
Click to expand...
Click to collapse
yes, this is mine problem, too
still gps and data problem
i have still this two problems:
data works only after reboot, after switch off/on data no connection!
gps dont work
my impression :
since the camera is working for topaz etc. the development
get very sluggish....
There's already a new version out (March, 25) which is working very well with your decription. But i have still 2 problems:
1. when answering a call, nobody can hear the other person... when finishing this "ghost-call" android freezes...
2. when using facebook-app and trying to post my actual place the phone freezes after some seconds...
any ideas how to fix this?
thx in advance
Maddin91 said:
There's already a new version out (March, 25) which is working very well with your decription. But i have still 2 problems:
1. when answering a call, nobody can hear the other person... when finishing this "ghost-call" android freezes...
2. when using facebook-app and trying to post my actual place the phone freezes after some seconds...
any ideas how to fix this?
thx in advance
Click to expand...
Click to collapse
Did you read about "first-call" need?
Is a well discussed issue on Froyo. I think this issue is still on Gingerbread. After each reboot you need to place 1 single first outcome call. You can make it dialing your own phone number till you listen the unavailable tone. Then drop the call.
After that you can receive calls very well.
been usin this build for 2 weeks now.. no real problems.... ocasional force closes... only when i try to run apps i knew better to not even try!!!
otherwise.. dont have the incoming call problem...
very fast... very what i would call stable.... definetly my favorite ANdroid build for our devices
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.
Hi all,
I'm trying to repurpose my Nexus One as a wifi security camera with ipwebcam. However, the camera seems like it won't work on any ROM I feed it. Now I read a lot on ROMs having broken camera support, but all of them?? I remember the camera was working perfectly before I started flashing it, so what are my options? I tried pretty much every rom available - CM7/10/11, Evervolv, TexasIce, HyperSense, and the camera is always crashing or non fonctionnal. The phone is rooted, blackrosed to partitions 260/8/168, and the recovery has 4ext touch with the sdcard partitioned to 4ext.
So, is there something I'm missing? I would love to create my own ROM that would ditch the calling/phone/3g features to make it more like a super ipcam - with flashlight support, wifi, bluetooth, and gps, but I don't have those skills.
Also, torch is also not working, if that can help.
Any help is appreciated!
I remember that IP Webcam worked with stock 2.3.6 for me. Now I have 4.4.4 (CM11 by parkedraccoon), I just installed it again and it still seems to work although it was just a short test.
Does the app crash instantly on startup or later on while streaming?