Related
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.
I really want Eclair bad.. but I can not live without a camera.
What exactly is the ongoing issue with getting Elcair camera to work - is it a kernel issue or a user space one?
If it is user space I might start looking into it myself using the working donut code as a starting point.
There seems to be very little information on this board about the *development* of Eclair. Everyone is just talking about builds and cooking. Should I be looking at another board for actual Java hacking to get the user-space working (assuming it is in user-space) ?
I think it's due to user space as everything works fine in Donut builds. For example, BlueTooth works fine in polyrhythmic's Eclair builds for Kaiser, while other eclair builds don't.
I'm sure if someone took a look at what polyrhythmic did with his build, you could get bluetooth working on other eclairs, and this could maybe even help figure out how to get the camera working as well.
Just shows how we really took advantage of polyrhythmic's work.
Dukenukemx said:
I think it's due to user space as everything works fine in Donut builds. For example, BlueTooth works fine in polyrhythmic's Eclair builds for Kaiser, while other eclair builds don't.
I'm sure if someone took a look at what polyrhythmic did with his build, you could get bluetooth working on other eclairs, and this could maybe even help figure out how to get the camera working as well.
Just shows how we really took advantage of polyrhythmic's work.
Click to expand...
Click to collapse
BT works in the Eclair builds on this forum too, Perhaps not so well on your Kaiser however.
Did Poly get BT audio working?
Regarding the camera. Thats a great question. I am not sure who is working on it?
myn said:
BT works in the Eclair builds on this forum too, Perhaps not so well on your Kaiser however.
Did Poly get BT audio working?
Click to expand...
Click to collapse
Guess he didn't, just tried it myself and it only connects. No BT audio. According to his front page that BT audio is a kernel problem.
For the record, I don't care about Bluetooth, at all. But I can't go to eclair with no camera.
If it is confirmed user-space, then maybe I will start looking into it myself... although, I find it hard to believe months have gone by based on a simple userland issue?
i think it is user space also, because using an eclair NBH on warm donut camera works fine, but same NBH with eclair and the camera doesnt work so that would rule out the kernel most likely
Yes, it's a userspace problem, I wrote the userspace cam lib for cupcake and donut but there will be some changes needed for eclair and froyo.
I don't have much time at the moment and would rather make the kernel better with what time I do have.
It's probably not a difficult job to get it working, pm me if you need any pointers.
Dukenukemx said:
Guess he didn't, just tried it myself and it only connects. No BT audio. According to his front page that BT audio is a kernel problem.
Click to expand...
Click to collapse
polymod 2.1g with the BT&WIFI update had btaudio working for kaiser.
2.1d lost btaudio but is a much faster build.
mnjm9b said:
polymod 2.1g with the BT&WIFI update had btaudio working for kaiser.
2.1d lost btaudio but is a much faster build.
Click to expand...
Click to collapse
I haven't used Polymod in months. I should probably give it another try.
Hi,
Few month ago, my N1 falled on the street and the touch screen broked. I ordered a new one, dissassembled the phone to replace it, reassembled and everything was working fine.
Then one week ago, i dissasembled it again to clean some (a lot of) dust that went under the screen. Now everything is still working except the GPS.
GPS test doesn't show me any satellite, nothing... it just say "GPS on"
I'm using cyanogen 6.0 rc3.
Does anyone knows where to look inside the phone to check if something is broken ?
popopow said:
Hi,
Few month ago, my N1 falled on the street and the touch screen broked. I ordered a new one, dissassembled the phone to replace it, reassembled and everything was working fine.
Then one week ago, i dissasembled it again to clean some (a lot of) dust that went under the screen. Now everything is still working except the GPS.
GPS test doesn't show me any satellite, nothing... it just say "GPS on"
I'm using cyanogen 6.0 rc3.
Does anyone knows where to look inside the phone to check if something is broken ?
Click to expand...
Click to collapse
Have you tried a couple of different ROM / kernel combinations to make sure it's not a software issue?
Well i was using kang o rama 1.0 b2 with an intersecraven kernel, then i switched to the last service pack of kang o rama (so based on cyano 6.0 rc3) with the kernel that comes with it.
I think if there was a problem with gps in the the cyano / kang o rama, it will be widely reported here. And the GPS was the only thing that always worked fine in almost all roms /kernel i have tried.
popopow said:
Well i was using kang o rama 1.0 b2 with an intersecraven kernel, then i switched to the last service pack of kang o rama (so based on cyano 6.0 rc3) with the kernel that comes with it.
I think if there was a problem with gps in the the cyano / kang o rama, it will be widely reported here. And the GPS was the only thing that always worked fine in almost all roms /kernel i have tried.
Click to expand...
Click to collapse
Many users report problems with GPS on RC3. Check that thread.
The GPS problem occured days before upgrading to RC3. I installed RC3 only to see if it fixes something but nope.
People on the thread says that with the RC3, it's quite long to get GPS lock, about 5 min. For me, it's impossible to get any GPS lock, even after half an hour, outside during a sunny day.
The problem started to show right after dissambling the phone, not after changing software. So i suppose i did something wrong while reassembling.
if you made a nandroid you can try flashing it back... as gerikss said, many users are having gps issues on CMRC3
heya,
I was having GPS problems as well with my first Nexus One - turned out to be hardware problems, had to send it back.
I installed GPS Status from the Market, and mine wasn't able to see any satellites - is yours able to see any satellites?
http://forum.xda-developers.com/showthread.php?t=711448
Hmm, it sounds like you've put yours through the wringer though...haha...and taking it apart? Yeah, not sure if warranty will repair that for you. You can give it a shot?
Cheers,
Victor
popopow said:
The GPS problem occured days before upgrading to RC3. I installed RC3 only to see if it fixes something but nope.
People on the thread says that with the RC3, it's quite long to get GPS lock, about 5 min. For me, it's impossible to get any GPS lock, even after half an hour, outside during a sunny day.
The problem started to show right after dissambling the phone, not after changing software. So i suppose i did something wrong while reassembling.
Click to expand...
Click to collapse
The problem is not in the phone but the RC3 build which is widely used right now. Change it and I GUARANTEE it will work fine. FYI.. Rodriguez, Cyanogen, and Kang all use the build.
Is my english that bad ? My GPS problem started to occur with RC2 ! then i installed RC3. And they started right after dissambling my phone, not after any kernel / rom / radio / software change.
Like victorhooi said, GPS test program (or any gps diagnostic) is giving me no signal.
No matter i dissambled it or not, my phone is not under warranty, I got it offered at a google conférence.
I guess i'll have to live with only 3G location until a new phone will make me want to leave my N1.
popopow said:
is my english that bad ? My gps problem started to occur with rc2 ! Then i installed rc3. And they started right after dissambling my phone, not after any kernel / rom / radio / software change.
Like victorhooi said, gps test program (or any gps diagnostic) is giving me no signal.
No matter i dissambled it or not, my phone is not under warranty, i got it offered at a google conférence.
I guess i'll have to live with only 3g location until a new phone will make me want to leave my n1.
Click to expand...
Click to collapse
most likely if the gps is showing "on" as you stated in post 1 then the gps isn't "broken", but most likely a loose connection. Some problems are solved flashing back to factory rom. If the gps was broken it wouldn't activate.
this post fixed it for me.
forum.xda-developers. com/showthread.php?t=625061
Hi,
flashed modaco r21 with stock froyo kernel, did what's told in the previous post (in fast, it was already like this). Still no GPS. GPS Test shows me no satellite.
I tell you, it's inside the phone. Maybe something is really broken, maybe just not connecte something correctly. But i want to know where to look before opening it again.
I'm having problems with my GPS too. I remember that it used to work well with FRF91. I still have locked bootloader and I rooted yet. Most of the time, it takes me a while to get a GPS lock, 5-10 minutes. Sometimes, it never gets a lock. Any ideas?
Update: I fixed my problem with the link in post#11.
A test/stock anykernel for CM6 inc is up on rom manager under the Koush section. Please test it out and let me know how it compares. I am working on tracking down some instability issues.
Having issues with built in tethering says error. Pre 9 seems to work however after toggling wifi.
Anyone else?
Used it for a day...
I'd have to say one of the biggest downfalls was that it didn't have most features within the kernel enabled. I didn't notice any immediate problems even with the stock kernel, unless what I ran into (described below) might be involved.
When trying to initially download the new kernel via ROM Manager, I was in a location where cell was -120 dBm (basically non-existent) but I had Wifi. Wifi always seemed to take forever to link up, unless I went into settings (then it'd find the AP immediately and connect). ROM Manager basically said it couldn't do anything, despite having Wifi. I don't know enough about the inner Android workings to know if that's unrelated or not.
With the new one I noticed mainly I had very few governors to work with. TBH I only spent a day with it because I couldn't stand how often I ended up having to charge it. I don't OC so that sort of thing has never been an issue - just UC
Edit -- I should mention I'm using 2.15.00.09.01 baseband and CyanogenMod-6-09202010-NIGHTLY-Inc build. Haven't tried newer dailies yet.
sucker4pa1n said:
I'd have to say one of the biggest downfalls was that it didn't have most features within the kernel enabled. I didn't notice any immediate problems even with the stock kernel, unless what I ran into (described below) might be involved.
When trying to initially download the new kernel via ROM Manager, I was in a location where cell was -120 dBm (basically non-existent) but I had Wifi. Wifi always seemed to take forever to link up, unless I went into settings (then it'd find the AP immediately and connect). ROM Manager basically said it couldn't do anything, despite having Wifi. I don't know enough about the inner Android workings to know if that's unrelated or not.
With the new one I noticed mainly I had very few governors to work with. TBH I only spent a day with it because I couldn't stand how often I ended up having to charge it. I don't OC so that sort of thing has never been an issue - just UC
Edit -- I should mention I'm using 2.15.00.09.01 baseband and CyanogenMod-6-09202010-NIGHTLY-Inc build. Haven't tried newer dailies yet.
Click to expand...
Click to collapse
2.15.00.09 radio literally KILLED my battery. I went back to 2.15.00.07 and battery life is great again. FYI.
Everything is good for me with this kernel. No issues. Flashed it last night.
dnoyeb said:
Having issues with built in tethering says error. Pre 9 seems to work however after toggling wifi.
Anyone else?
Click to expand...
Click to collapse
At the moment, I'm using Miui but wanted to note that this is the only kernel which allows Pre-9 Wifi tether to work on Miui (in my hands, King's #1 and #2 AOSP kernels gave me errors with Wifi Tether). Thanks for providing this kernel, Koush. Will give it a try with CM and see how that goes.
I had a soft reboot last night with this new kernel while I was on facebook. 0 wifi used.
Radio 2.15.00.07
Not sure if it's the kernel or just the latest nightly, but I'm loosing my data connection quite often. Otherwise, its running great.
dnoyeb said:
Having issues with built in tethering says error. Pre 9 seems to work however after toggling wifi.
Anyone else?
Click to expand...
Click to collapse
My built in wifi tethering isn't working either....sad day. I was loving how fast my phone charged
New version, number. 11 is online, testing now.
I haven't had any problems with this kernel yet even on wifi. I have also noticed decent battery life.
Droid Incredible
S-off
.77 hboot
Latest radio
Ruby Rom
mikeacela said:
I haven't had any problems with this kernel yet even on wifi. I have also noticed decent battery life.
Droid Incredible
S-off
.77 hboot
Latest radio
Ruby Rom
Click to expand...
Click to collapse
Funny, I'm running the test2 on Ruby as well. Been rock stable for 4hours. Practically a record for my phone on Ruby. Hope it makes it through the night.
Using the "test2" kernel.
Built in tethering works for me.
I'm running the 9/27 nightly.
No other issues so far.
P.S. I would love if internal memory was mounted properly in Windows.
Does anyone know if this new kernel is underclocked?
Sent from my INCREDIBLE using Tapatalk
Another question would be, does anyone know if test kernel #1 or #2 is the test kernel in rom manager?
Ty07allstar said:
Does anyone know if this new kernel is underclocked?
Sent from my INCREDIBLE using Tapatalk
Click to expand...
Click to collapse
showing up as a 245-998mhz one with compcache optional... Not that I put much credence in quadrant scores, but I'm pulling over a 1300 on that. So plenty quick.
Also does anyone know if its undervolted?
Sent from my INCREDIBLE using Tapatalk
Ty07allstar said:
Does anyone know if this new kernel is underclocked?
Sent from my INCREDIBLE using Tapatalk
Click to expand...
Click to collapse
#2 is running at default clock.
So far looking good on test#2 for me (9.26 nightly). I just had a meeting in a location where the phone has frozen up nearly every time I was running CM 6.02 or any previous build and it worked fine. If I make it out to lunch, then back home later today without a freeze I think we may have a winner. Or at least I'll have a winner...
I grabbed the test kernel on friday night via the ROM manager, am I running the latest test, or is there a new one with the same name? In other words do I have to redo it to get the test #2 I am seeing comments about?
I am running test2 and my only issue is with wifi cutting out and erroring out when running things like streaming media in the background, but no reboots. Tt just cuts out the wifi, and resumes relatively well upon turning the screen back on. For some reason the screen being off sets off a timer that cuts out the wifi after a while. I've tested this with both Pandora and Slacker. No cut outs when running over 1x CDMA (3G doesn't work in my office) except when my signal becomes nonexistant.
I have never been able to use turn by turn. I've used Google Maps after enabling GPS and WIRELESS NETWORKS AND THEN WHEN i SWITCH over to Google Nav it says Searching for GPS....but yet it gets me text directions on how to get there and if I make a wrong turn it doesnt update with how to get there from the current location
Ive seen videos of people being able to use their GPS and Ive had this phnoe since last year. What in the hell...please help.
Baseband:
32.36.00.28U_4.06.00.12_7
Kern:
2.6.37.2
Cyanogen 7.0 RC2
If you can't use GPS in any application I would say it's hardware related and you need to send it in for repair/replacement.
I would assume you have the newest version of Maps and you have wiped and tried the stock rom already.
Can you provide logs?
Oh damn Im out of warrant :\
Im frustrated
and the weird thing in Google Maps, when I have GPS and wireless network enabled it grabs my location within about 500 yards of my real location but on Google Nav it says searching for gps and when I use the GPSstatus app it doesnt lock or anything it has that loading icon
500 yards is your network location. That would be flat out awful and useless for GPS. My GPS fix is usually in between 3-10 meters.
Download GPS status from the market and see what it shows.
Sent from my Nexus One using XDA App
Oops did not see the last line where you already tried the app.
As said before try a full wipe/ restore to stock if you haven't already. Other than that it will need to be sent into HTC to be fixed.
Sent from my Nexus One using XDA App
Ill try a full restore and report back
Not quite the same ....
I am getting problems where the GPS lock takes far too long, but it does eventually get there.
I am on:
Android - 2.3.3
Baseband - 32.50.00.32U_5.12.00.08
Kernel - 2.6.35.7-59423-g08607d4
Build - GRI40
All pretty standard stuff, the issue really is that it used to work great on 2.2 & earlier radios, so I guess the question is what is the best radio for 2.3.3 & GPS ?
cottinghamm said:
I am getting problems where the GPS lock takes far too long, but it does eventually get there.
I am on:
Android - 2.3.3
Baseband - 32.50.00.32U_5.12.00.08
Kernel - 2.6.35.7-59423-g08607d4
Build - GRI40
All pretty standard stuff, the issue really is that it used to work great on 2.2 & earlier radios, so I guess the question is what is the best radio for 2.3.3 & GPS ?
Click to expand...
Click to collapse
If you don't have the same issue, then why post in the thread with a different issue? Start a new thread for a separate issue. Fwiw, stock Gingerbread radio is 5.08 which is what you should be using, not 5.12.
I think it's more of a CyanogenMod 7 issue since I couldn't have locked the phone with RC2 also. Try updating to RC4 it works for me now.