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.

[SELFKANG AOSP ROM] CyanogenMod 7.1 GSM Version [UPDATE 10/23 AM]

I was sent this by XDA user: coreless88 who asked me to post this in the dev section (he doesn't have enough posts yet).
** WARNING: I HAVE NOT TESTED THIS PERSONALLY -- USE AT YOUR OWN RISK -- KEEP A BACKUP HANDY **
** THIS ROM IS INSTALLED WITH SAFESTRAP BOOTSTRAP. DO NOT USE KOUSH'S BOOTSTRAP OR YOU WILL SOFTBRICK YOUR DEVICE **
I dabbled in files for some time, twaked the build.prop a little (added some generally known hacks into it for faster touch reaction, better HSPA reception etc.), and added some files .lib/.ro files from Droid 2 Global.
It all worked out nicely. However, as I cannot use a CDMA network (I live in Turkey, so I have only GSM access), I cannot guarantee this will work with CDMA too. I will appriciate it if someone can test it.
Also, Your GSM card will be recognized instantly, but you need to activate the 3G network form the settings, you will need to add your APN manually, atleast in my case I had to put my carriers APN into the list, so this might not be necessary."
Here is the link: http://www.mediafire.com/?d17l4z4885ph4ov
Thanks needs to go to Hashcode, as I just modified and added a missing feature to it.
Click to expand...
Click to collapse

Thanks for the help Hashcode!
I got my clearence to Dev forums, so I will try to contribute even more to this community =] .
First of all, as in my quote in the first post, I cannot guarantee this will work in CDMA network, Hashcode will inspect the files and try to integrate the GSM feature to his original release.
You can find a screenshot of my phone working under the GSM network and 3G enabled.
!!!However, just like any other custom rom, I cannot accept any responsibilities if this rom bricks your phone. !!!
For installing, just use Hashcode's safestrap, for the rest i think you know the drill.
BUGS:
Videos dont run,
Sound is low,
Bluetooth is broken,
Camera is broken,
Also be aware, notification and ringtone sounds are silent by default, you just need to go to settings menu and choose a ringtone for yourself =] .
Edit: Also as I have only 1 Droid 3 at the moment, I need as much testers as I can find for checking if this works for all Europe SIM Cards.

Referved for future use/updates/etc...

Awesome, very thanks to both Hascode and Coreless88
All work fine in france the signal bdm hspda is very good, than the xt883 rom. Exept the camera all work fine for me.
I'm test, if you want, all other release in france, on bouygues telecom.....

thank YOU !! Hashcode and Coreless88

No thank you guys, for trying it and giving me an easy breath as it is my very first development attempt!
nikeusfr said:
Awesome, very thanks to both Hascode and Coreless88
All work fine in france the signal bdm hspda is very good, than the xt883 rom. Exept the camera all work fine for me.
I'm test, if you want, all other release in france, on bouygues telecom.....
Click to expand...
Click to collapse
Also I forgot to mention, my tweaks and Cyanogen codes makes GSM reception and HSDPA signal is much more improved than the stock XT862 Rom.
Right now bluetooth doesn't work, but GPU and CPU working properly, if not better than before.
Here are some more screenshots, for Quadrant, SpeedTest, and A Samurai Vengance 2 (BTW Game runs incredibly smooth).

one another bug, i'haven't delivery report on sms/mms, there's no sound in the build speaker when i phone or receive call, and the sound is very quiet in the speaker phone or handset.

nikeusfr said:
one another bug, i'haven't delivery report on sms/mms, there's no sound in the build speaker when i phone or receive call, and the sound is very quiet in the speaker phone or handset.
Click to expand...
Click to collapse
Hi,
First of all, thanks for your input. I need your opinions to make this better. So here we go,
All notifications and ringtones are silent by default.
You need to get to:
"settings>sounds>ring tone/notification tone" menus and choose your ringtones from there.
Sounds are in this built generally low, because there isn't any proper sound resources prepared with OMAP 4 series of SoC's. I will try to enhance them, but I will need time.
But you can make the phone louder on the speaker by going to:
settings>cyanogenmod settings>sound menu then choose the settings you like the most.

What "general" GSM build.prop tweaks are we talking about here?

DoubleYouPee said:
What "general" GSM build.prop tweaks are we talking about here?
Click to expand...
Click to collapse
Hi,
I've added Tweaks for getting stronger reception, making the GSM default network at the boot, tweaks for faster response, etc... You can download the file and look at the system>build.prop (open it via wordpad if you are on windows) and compare it to Hashcode's build.prop.
BTW I am experimenting with audio and video files right now. Post I will post the results when I finish the testing.

Could I apply these build.prop changes my XT862 rom?
Or did you use droid 2 global hacks like someone tried before?

DoubleYouPee said:
Could I apply these build.prop changes my XT862 rom?
Click to expand...
Click to collapse
Why not, this is a free world, and as long as you know what you are doing you will be safe, but if you're not...
Be aware, "build.prop" is a very risky file to touch, and has a central role for the Android to run correctly. I had to use RSD to get back to original software because I stuck at the Motorola logo after some changes. So I took the hit for you allready =].
My advice, directly flash this rom and don't do any editing. Because I did not just edited the build.prop, also added several library files, done a lot of testing, finded new libraries or edited them to make it work.
It will include lots of time, effort, patience and hell of a risk.

coreless88 said:
Why not, this is a free world, and as long as you know what you are doing you will be safe, but if you're not...
Be aware, "build.prop" is a very risky file to touch, and has a central role for the Android to run correctly. I had to use RSD to get back to original software because I stuck at the Motorola logo after some changes. So I took the hit for you allready =].
My advice, directly flash this rom and don't do any editing. Because I did not just edited the build.prop, also added several library files, done a lot of testing, finded new libraries or edited them to make it work.
It will include lots of time, effort, patience and hell of a risk.
Click to expand...
Click to collapse
Well I would love to use this mod, but because:
Videos dont run,
Sound is low,
Bluetooth is broken,
Camera is broken
I'd rather have a GSM-fix for the my current ROM, (kinda like XT883, but then easier)

DoubleYouPee said:
Well I would love to use this mod, but because:
Videos dont run,
Sound is low,
Bluetooth is broken,
Camera is broken
I'd rather have a GSM-fix for the my current ROM, (kinda like XT883, but then easier)
Click to expand...
Click to collapse
Oh!
I completely misunderstand you, I thought you were asking about Hashcode's Cyanogen release. You cannot use these fixes for Motorola roms or any rom that based on a Motorola rom. These fixes and libraries are only for Cyanogen builds, at least thats what I think, as I don't have any development experience with any Motorola rom.
You may try, but that will only make the risk even bigger.
Please be patient, I am trying to fix camera and sound problems right now, and I will try to fix bluetooth in a later date, as I didn't see anyone using bluetooth for ages =] .

Giving this a whirl on my xt860 right now, will edit this post with results. Very nice fellas, thank you both very much! Just want to make sure, this is built for Hashcodes safestrap?
Seems to be doing the same as previous on my bell phone, loops on the first screen, I'm not getting to the boot animation.

coreless88 said:
Also I forgot to mention, my tweaks and Cyanogen codes makes GSM reception and HSDPA signal is much more improved than the stock XT862 Rom.
Click to expand...
Click to collapse
Yes, as I wrote elsewere looks like the wrong signal measurement is a purposely limit introduced by verizon request.
On D2g is the same, the Cyanogen rom, with the same radio have the correct measurement, the XT883 too.
So could be interesting to understand where that three bars are lost and if a quick fix for the stock ROMS could be possible.

Willis111 said:
Giving this a whirl on my xt860 right now, will edit this post with results. Very nice fellas, thank you both very much! Just want to make sure, this is built for Hashcodes safestrap?
Seems to be doing the same as previous on my bell phone, loops on the first screen, I'm not getting to the boot animation.
Click to expand...
Click to collapse
Hi,
Your thanks are appriciated, and I am sorry for this rom also did not worked for your XT860 =/ . I guess Motorola did everything they possibly can to protect their region based software versions.
I guess the fix will be simple, but I am afraid either Canadian Android developers are rare (BTW I don't think so), or they don't want to develop for / they don't have this device.
The Solutor said:
Yes, as I wrote elsewere looks like the wrong signal measurement is a purposely limit introduced by verizon request.
On D2g is the same, the Cyanogen rom, with the same radio have the correct measurement, the XT883 too.
So could be interesting to understand where that three bars are lost and if a quick fix for the stock ROMS could be possible.
Click to expand...
Click to collapse
Indeed, It seems low GSM signal was the goal for them. Either for the purpose of making the Verizon "look like" superior to European Networks, or just for making it a Verizon semi-exclusive and a pain in the ass for any other carrier.
The problem is the Verizon's firmware itself, for example, even the non-US devices (XT860, XT883... you name it) are listed by "cdma_solano" in the build.props, and while those files are filled with CDMA codes, there are hardly more than 6 lines of GSM related codes. So my simple tweaks does nothing to improve the signal (tested/proven).

coreless88 said:
Indeed, It seems low GSM signal was the goal for them. Either for the purpose of making the Verizon "look like" superior to European Networks, or just for making it a Verizon semi-exclusive and a pain in the ass for any other carrier.
Click to expand...
Click to collapse
Indeed this is the only reasonable explanation, the same behavior in five ROMs can't be a bug.
The problem is the Verizon's firmware itself, for example, even the non-US devices (XT860, XT883... you name it) are listed by "cdma_solano" in the build.props, and while those files are filled with CDMA codes, there are hardly more than 6 lines of GSM related codes. So my simple tweaks does nothing to improve the signal (tested/proven).
Click to expand...
Click to collapse
Maybe is omething hardcoded in the libril or whatever in the userland, surely is not the radio itself.
XT883 is not affected, so we should try to replace some piece to spot the culprit, BTW this process would be easier when the bootstrap will be fixed to work on XT883, (why doesn't work on that rom is a another nice mystery).

Indeed, a GSM ROM would be great

FYI, audio and video codec issues are being addressed in my next build of CM7.
I'm going to give the GSM ROM a test drive and see how the CDMA stuff is affected. As well as look at the differences by file.
Hopefully, i can incorporate coreless88's changes back into the main ROM so that we don't end up with 2 CM7 ROMs (CDMA and GSM).

[Q] N1 doesnt see certain hotspots

Ive tried with stock 2.3.6, CM7 and CM6 and although the CM roms improved wifi reception by leaps and bounds, my N1 will still not recognize some very necessary wifi SSIDs, namely the one at work. On my laptop, my old phone (Optimus T), and everyone elses smartphones there is no problem connecting at work. The access point is provided by a Fortiwifi 60c server. fortinet.com/products/fortiwifi/60C.html
Has anyone else had this problem or know the right direction for a solution? Wifi at work is a must!

it's not an adhoc network is it?
try moving closer to the source and see if other android phones can see it too

No, the network in question is not an ad-hoc. Yes, as I said in my original post, other smartphones and wireless devices have no problem making this connection.
I flashed and upgraded my phone's baseband radio to the most up-to-date version and my phone still doesn't see the network in question. I'm just about out of ideas.

Radio has nothing to do with WiFi.
Try different kernels.
Make sure that the visible access point isn't Wifi N.

Thanks for the experienced suggestion, thats just what I needed. Is there much risk involved in flashing kernels like there is with radios? Is the process the same, boot into recovery then install zip? Ill do the research myself here in a few hours when Ill have the free time but I'd like your input as well, Jack_R1, since it sounds to me like you know what you're talking about here. I'm hoping that you'll reply before I give this a try.

There is no risk when flashing kernels - in the worst case, if the flash went wrong, you can always boot to recovery and flash again.
The process is the same.
Kernel should be compatible with your type of ROM (AOSP GB/AOSP ICS/CM7/CM9/MIUI/etc).

[FIX] GPS Fixes

Hi,
So I've noticed alot of people have problems with their GPS from time to time on these forums so I've decided to collate any and all fixes into one place. Here they are:
NOTE: I'm not responsible for any harm done to your phone. These suggestions are tried at your own risk. These steps can be taken in any order you want and a reboot is recommended after you try each step.
First thing you can do to get accurate fixes is to go to the Location settings on your phone. Tick the boxes next to 'GPS Satellites' and 'Google's location service' (Press agree when the prompt comes up). Also click 'GPS Source' and make sure 'Use Internal GPS' is selected.
Click to expand...
Click to collapse
Second thing you can do is download the 'GPS Status & Toolbox' app from the market. Once installed go into the app and hit Menu and then select Tools. From the popup menu select Manage A-GPS state. Select Reset and then Download. Reboot and see if you can get a fix now.
Click to expand...
Click to collapse
It is recommended you have a Nandroid backup before trying anything below.
Third thing you can do is download this GPS Fix made for the Legend (From Kot_Ik’s CM7.2 unofficial thread). Put it on your SDCard and reboot to recovery and flash it.
Click to expand...
Click to collapse
Fourth thing you can do is flash a new radio in recovery. Get one from here. Try the bottom 2 first before trying the top one. This doesn't seem to be supported in the latest versions of CWM so you should load an earlier fake flash zip file. Go here for the recovery and instructions (Thanks ranger4740)
Click to expand...
Click to collapse
Last thing I can think of is to change ROM's and see if that fixes anything.
Click to expand...
Click to collapse
That's all folks. If you're reading this part and your GPS still isn't working then I've got no idea what's going to fix it

smithchipz said:
Third thing you can do is download this GPS Fix made for the Legend. Put it on your SDCard and reboot to recovery and flash it.
Click to expand...
Click to collapse
This is not needed for old stable releases and was fixed a few weeks ago (so recent RCs and nightly builds already contain that bugfix).
smithchipz said:
Fourth thing you can try is download a gps.conf file from here that's related to your country/continent and flash it in recovery.
Click to expand...
Click to collapse
All of the files I checked there are invalid.

ali ba said:
This is not needed for old stable releases and was fixed a few weeks ago (so recent RCs and nightly builds already contain that bugfix).
All of the files I checked there are invalid.
Click to expand...
Click to collapse
Ali Ba, as you are the legend master, can you please explain why my legend could never achieve GPS lock on ANY version of CM, stable or not, no matter how long my phone tried until I started using the GPS fix mentioned above. I ask because you are the master, and you did say its not nessasary. So that advice is a bit confusing.
Thank you
sent from my legend using zeubeas cm9 beta2

ali ba said:
All of the files I checked there are invalid.
Click to expand...
Click to collapse
Hello ali ba,
can you explain, how a valid gps.conf looks?

alligator_asl said:
can you explain, how a valid gps.conf looks?
Click to expand...
Click to collapse
It is a config file parsed per line. This means that there shouldn't be any new line characters for lines that the system has to interpret as one.
It's perfectly OK to use a local NTP-server, by the way. It just doesn't fix problems at all. The short differences in the time the packets take to be sent and received are eliminated by the NTP protocol anyway.
Most so called "GPS fixes" are bogus at best (using the newest baseband firmware is something I'd recommend though).
ranger4740 said:
Ali Ba, as you are the legend master, can you please explain why my legend could never achieve GPS lock on ANY version of CM, stable or not, no matter how long my phone tried until I started using the GPS fix mentioned above. I ask because you are the master, and you did say its not nessasary. So that advice is a bit confusing.
Thank you
Click to expand...
Click to collapse
Everything I say is right so you are wrong per definition. Also, I'm the reincarnation of an ancient demigod and I'll send a shipload of trained African killer bees to decompose your cell phones after you should you dare to question me. Any more questions?

ali ba said:
Everything I say is right so you are wrong per definition. Also, I'm the reincarnation of an ancient demigod and I'll send a shipload of trained African killer bees to decompose your cell phones after you should you dare to question me. Any more questions?
Click to expand...
Click to collapse
Well, good question by ranger4740, but bad answer...

This fix gps.agps.legend.zip is not for CM9. If you flash this, you are flashing a lib which nobody knows where is from.

zeubea said:
This fix gps.agps.legend.zip is not for CM9. If you flash this, you are flashing a lib which nobody knows where is from.
Click to expand...
Click to collapse
Sorry the fix is from Kot_Ik’s CM7 thread. Updated the post to show this.
Sent from my Legend using XDA

Exactly, it is for CM7 Kot_Ik, because it is built in that rep for that version, only clarifying for avoid to see posts from people flash CM7 libs on CM9, because it is not the way.
smithchipz said:
Sorry the fix is from Kot_Ik’s CM7 thread. Updated the post to show this.
Sent from my Legend using XDA
Click to expand...
Click to collapse

After trying to update gps.conf file for my locatopn Europ/Poland both .zip files (Europ and Poland) crashes during updateing... is there anything ealse i can do to make it works ?;>
after those tryes i ve downgraded cwm useing ranger's update file and instaled latest radio.zip... after rebot gps still couldn't "lock" my positon... with custom settings for gps made by zuebas in cm9beta2 it founds and uses up to 13 satelites but couldnt lock position.... what ealse can i do to make it work properly ?
EDIT: after updating from latest to newest radio (now useing 47.26.35.04_7.05.35.26L) it can't even find any satelites, earlier it was finding up to 13-14.... I've reset and downloaded A-GPS state..... and still nothing

maxydem said:
After trying to update gps.conf file for my locatopn Europ/Poland both .zip files (Europ and Poland) crashes during updateing... is there anything ealse i can do to make it works ?;>
after those tryes i ve downgraded cwm useing ranger's update file and instaled latest radio.zip... after rebot gps still couldn't "lock" my positon... with custom settings for gps made by zuebas in cm9beta2 it founds and uses up to 13 satelites but couldnt lock position.... what ealse can i do to make it work properly ?
Click to expand...
Click to collapse
I'm not sure apart from all the steps I listed in first post. Sorry :/

maxydem said:
After trying to update gps.conf file for my locatopn Europ/Poland both .zip files (Europ and Poland) crashes during updateing... is there anything ealse i can do to make it works ?;>
after those tryes i ve downgraded cwm useing ranger's update file and instaled latest radio.zip... after rebot gps still couldn't "lock" my positon... with custom settings for gps made by zuebas in cm9beta2 it founds and uses up to 13 satelites but couldnt lock position.... what ealse can i do to make it work properly ?
EDIT: after updating from latest to newest radio (now useing 47.26.35.04_7.05.35.26L) it can't even find any satelites, earlier it was finding up to 13-14.... I've reset and downloaded A-GPS state..... and still nothing
Click to expand...
Click to collapse
Ok, what I have noticed so far using legend. Don't mess with gps.conf using other custom gps.conf I've use some before (instant lock) and its bogus as Ali ba put it.
Just use faster fix is enough.
OK, now currently I'm on zuebes cm9 and GPS works but getting it to lock is something else. And I love my waze.
I'll get in my car and start waze. Wait for a minutes or 2 than start moving. Lock or no lock, just start moving. Don't drive so fast but stay constant either 40kmh or 60kmh will do just fine. My lock usually happens when I stop at a junction or a traffic light or slow down before a corner.
Then when you lock for the first time. You can combo for the next trip as long as you on your waze at the same spot before leaving. It's instant lock for some cases but need to start over if it does not lock. Assume you use waze.
But if GPS is important. Use stock based rom and ogo2s rom also have good GPS if I remember well... I think its something about HTC didn't release GPS source that we ended up like this.
Sent from my Legend using Tapatalk 2

Alright I've changed the post and removed the step about changing the gps.conf.

maxydem said:
After trying to update gps.conf file for my locatopn Europ/Poland both .zip files (Europ and Poland) crashes during updateing
Click to expand...
Click to collapse
I'm sorry that it broke your device, but I can't do more than pointing out that these files are invalid.
Oops... said:
Well, good question by ranger4740, but bad answer...
Click to expand...
Click to collapse
So I point out that these files are not only useless (as most GPS fix instructions are) but also broken and invalid and what do I get? Some random guy jumping at me telling me how stupid I am because GPS coincidentally started working on his device after doing some useless things?
You know, that's not even something I have to do (as if I was getting paid for support), I'm doing it because I'm basically a nice guy.
And then you, another random "I know how to register an account so let's attack people"-user, shows up. Thanks, you're welcome. Oh, I was right, by the way. The files are broken. The fixes don't work.
psyionx said:
Ok, what I have noticed so far using legend. Don't mess with gps.conf using other custom gps.conf I've use some before (instant lock) and its bogus as Ali ba put it.
Click to expand...
Click to collapse
Thank you for actually reading what I write.
psyionx said:
I think its something about HTC didn't release GPS source that we ended up like this.
Click to expand...
Click to collapse
That's right. There's a bug somewhere in the GPS module but we never got any sources so we don't really know how to work around it. The GPS module on the Legend doesn't have public sources so we hacked together some code from different versions. It works pretty well - once it starts working.
I sometimes can't get a GPS fix either when I started the device with GPS turned off or after toggling GPS a few times. Yeah, it is broken and I am aware of that.
The only "solutions" that really work are rebooting your device with GPS and mobile internet connection turned on. This lets it download AGPS data, inject the current time into the module and you'll get a fix within 20 seconds.
Using the latest radio (=baseband firmware) for your region has been reported to kickstart GPS as well. That's the only fix I can confirm, everything else is shenanigans and you should get your money back .

ali ba said:
I'm sorry that it broke your device, but I can't do more than pointing out that these files are invalid.
So I point out that these files are not only useless (as most GPS fix instructions are) but also broken and invalid and what do I get? Some random guy jumping at me telling me how stupid I am because GPS coincidentally started working on his device after doing some useless things?
You know, that's not even something I have to do (as if I was getting paid for support), I'm doing it because I'm basically a nice guy.
And then you, another random "I know how to register an account so let's attack people"-user, shows up. Thanks, you're welcome. Oh, I was right, by the way. The files are broken. The fixes don't work.
Thank you for actually reading what I write.
That's right. There's a bug somewhere in the GPS module but we never got any sources so we don't really know how to work around it. The GPS module on the Legend doesn't have public sources so we hacked together some code from different versions. It works pretty well - once it starts working.
I sometimes can't get a GPS fix either when I started the device with GPS turned off or after toggling GPS a few times. Yeah, it is broken and I am aware of that.
The only "solutions" that really work are rebooting your device with GPS and mobile internet connection turned on. This lets it download AGPS data, inject the current time into the module and you'll get a fix within 20 seconds.
Using the latest radio (=baseband firmware) for your region has been reported to kickstart GPS as well. That's the only fix I can confirm, everything else is shenanigans and you should get your money back .
Click to expand...
Click to collapse
By quoting me you are implying I'm some one that only knows how to register and start attacking people, how did I attack you, most people here know your the master who gave us all cm for our legend which is wonderful, and I simply asked you as you are the expert to explain how? Then you come back with your B.S answer attacking me, for no real good reason Instead of explaining humanly the answer, you also imply I attack people, when all I do here is try and learn to do stuff, and help others when I can.
Any way best you add me to your ignore list then you won't have to see me attack and abuse every one on xda developers ever again! Hey better still report me to the mods and get me permanently band from xda forums if you've seriously got some evidence of constaintly attacking members.
Sent from my Legend using XDA

ali ba said:
... And then you, another random "I know how to register an account so let's attack people"-user, shows up. Thanks, you're welcome. Oh, I was right, by the way. The files are broken. The fixes don't work.
Click to expand...
Click to collapse
Calm down. Nobody attacks people. I appreciate your work concerning the Legend port - and stated that several times.
Not giving an answer is ok - as you said, no paid support.
However, I can't agree on statements like ...
ali ba said:
... Everything I say is right so you are wrong per definition. ... Any more questions?
Click to expand...
Click to collapse
as they are rude by definition. No more questions ...
btw, thanks for clarification
The only "solutions" that really work are rebooting your device with GPS and mobile internet connection turned on. This lets it download AGPS data, inject the current time into the module and you'll get a fix within 20 seconds.
Click to expand...
Click to collapse

ugh! this is unnecessary fighting, ali ba might just misunderstood ranger4740 questions, cos it sound corny at first look but if you read it again it's just a genuine question.
about gps fixes, we should trust the expert, yes this won't work as ali ba said there's some bugs in gps module. This fixes might work on other devices but I wonder if it does anything for our Ancient Legend

homi3kh said:
ugh! this is unnecessary fighting
Click to expand...
Click to collapse
Agree. Back on topic

...So I am using Zeubea's ICS ROM (BETA3) and my GPS isn't working.
I have refreshed the AGPS-data and flashed the newest (?) radio (7.13.35.05).
In what way is the radio dependent on my geographical location? I live in Sweden, am I using the correct radio?
I get no lock, but I get accuracy of roughly 2km. How is this?
Also, I'm searching for an app to see how many satelites I am connected to, havn't found one yet.
Any help in this would be greatly appreciated - thank you in advance ♥

MarkInDaPark said:
...So I am using Zeubea's ICS ROM (BETA3) and my GPS isn't working.
I have refreshed the AGPS-data and flashed the newest (?) radio (7.13.35.05).
In what way is the radio dependent on my geographical location? I live in Sweden, am I using the correct radio?
I get no lock, but I get accuracy of roughly 2km. How is this?
Also, I'm searching for an app to see how many satelites I am connected to, havn't found one yet.
Any help in this would be greatly appreciated - thank you in advance ♥
Click to expand...
Click to collapse
try using mobile data to get a good starting point (google's location service), also check gps source in location settings, and then try to get the precise location somewhere with a good view of sky....every next time it'll be faster, (you can even disable google's location service if you don't like it being turned on,it should still work faster than the first time after flashing)
edit: i just tried what i wrote above and got fix in no time,even from my room,using zeubeas cm9 beta3 freshly flashed... so, enable mobile data for a brief time until you get gps lock then you can disable it if you wish

My second N6, the same problem

I bought the Nexus 6 (blue, 64gb) the day one, in November and since that day I noticed random reboots in a particular situation. When I switch to a WiFi network to another it shuts down and so I have to turn it on. When it turns on I have lost all my WiFi networks configurations, so passwords, dhcp settings, etc.
Random reboots rarely happen also in camera/gallery apps.
I tried to send it back to google and I received a new nexus. The first one was produced in June 2014, the new one in December 2014. The issue is still there. [emoji17] I've also tried to update to 5.1 but no resolution.
I have rooted, installed twrp, decrypted both my nexus 6 with toolkit.
How can I solve the problem? I was very happy with this phone.

Try using it completely stock and see what happens. I'd say chances are that if you set both up the same, it's something you're doing and not the hardware on 2 different phones.

But other people have made the same basic mods on their nexus and their phone has not this kind of issue.

Is it every network? Maybe try a stable custom ROM to see if it happens there too. Could be a problem with specific networks or even apps. Troubleshooting is the key. First try full wipe, no restored Apps.

I could be as simple as an app the developer has not updated since gingerbread or something stupid like that.

Is there a way to find the malicious app?

There definitely *was* a bug causing loss of wifi networks, and I think there may also have been a reboot involved there (not sure if we rebooted it manually, or if it just did it on its own as a response to a wpa_supplicant crash...). It was across the board for Android 5.0 though, not limited to Nexus 6. I saw my wife's Nexus 5 do it once. Never actually had it happen on my 6.
I'm not sure if this bug was fixed or not, since it wasn't something we tried to reproduce, and only happened once. The bug is definitely related to wpa_supplicant, since that is the only program that actually interacts with its configuration file (which is where the wifi configurations are actually stored).
As far as galleries go, you're not giving much to guess by. I certainly haven't seen galleries cause reboots like that. Maybe you are using a bad one?
Try this gallery; https://github.com/lbdroid/Android-Binaries/blob/master/Gallery2.apk
That is the actual AOSP gallery, modified to install as a standalone application. The source code is in another repository on my github.
*note: it will not do you any good at all to swap out your phone, since there is no indication that you are experiencing a hardware issue.

But why other people doesn't experience this problem that is related to WiFi? All people use WiFi and every time. Is there a way to fix the WPA_supplicant issue? Maybe a custom ROM?
My first n6 had also an hw issue, I think, because before it rebooted it gave me some little "buzz" from the top speaker.

mouse100 said:
But why other people doesn't experience this problem that is related to WiFi? All people use WiFi and every time. Is there a way to fix the WPA_supplicant issue? Maybe a custom ROM?
My first n6 had also an hw issue, I think, because before it rebooted it gave me some little "buzz" from the top speaker.
Click to expand...
Click to collapse
all people use WiFi is an incorrect statement. you can say most ppl use wifi, but all would never happen. I hate using WiFi and NEVER use it except when its absolutely necessary. ive probably used WiFi 2 times on my n6 since getting my n6 in November, and there's no WiFi issues here.

mouse100 said:
Is there a way to find the malicious app?
Click to expand...
Click to collapse
Yes, start with stock and install a few apps at a time until you get the problem. Given the fact that you have 2 different phones experiencing the same problem, it is much more likely that it is something software related rather than hardware (though I suppose it could be possible if you're really unlucky ).

mouse100 said:
But why other people doesn't experience this problem that is related to WiFi? All people use WiFi and every time. Is there a way to fix the WPA_supplicant issue? Maybe a custom ROM?
Click to expand...
Click to collapse
You said that it happens when you change from one wifi network to another. Most people don't do that. Most people have one wifi network at a time and don't change it.
There is also a huge difference between wifi network configurations... A/B/N/AC, frequency, bandwidth, multiple-bands, encryptions, etc.
My first n6 had also an hw issue, I think, because before it rebooted it gave me some little "buzz" from the top speaker.
Click to expand...
Click to collapse
Normal.