[Q] How to ignore a specific cell/tower ? - General Questions and Answers

I was wondering if there is a way to make a Windows Mobile (6.5, if that matters) ignore a specific cell/tower.
The problem I'm trying to solve is that in the area I'm living in I am having issues only when connected to a specific tower (I know, this is a provider issue - they are probably having problems with that tower, but...) - so I'm trying to make my phone (HTC Touch HD/Blackstone) ignore that tower completely.
The usual suspects:
1. The radio software itself
2. The RIL (Radio Interface Layer) - is there any validation callback from the RIL when the cell configuration changes ?
TIA for any info on this matter...

As far I know you can't do anything about it. This stuff is buried deep in the radio ROM itself.
There is nothing in the standard RIL library that deals with it. The call backs are for requests for information via RIL_xxxxxxx calls. There is a possibility that it has been implemented through the driver catch all function RIL_DeviceSpecific(), but as this is defined by the OEM as the device and driver is built, you have to know the parameters to pass, and what gets delivered back to the callback routine.
Even if this stuff is there, it tends to be undocumented, and may change from OEM to another, and maybe even from one phone model to the next.

stephj said:
As far I know you can't do anything about it. This stuff is buried deep in the radio ROM itself.
Click to expand...
Click to collapse
That's what I feared ..
Thanks for the info.

Related

Can't turn on the bluetooth

hello,
unfortunately i cannot turn on the bluetooth from comm manager, it turns on and after 1 second is off again.
any solution for this problem?
thanks.
I have had this problem before and unfortunately am having it again. Only solution I have ever found for this is a hard reset and then reinstalling all your apps. If you try to restore from a backup from Sprite Backup, for instance, the problem remains. This would lead me to believe that it's a setting or a registry issue somewhere but I haven't been able to locate exactly what would be causing it and don't know enough about programming in WM to write something to figure it out.
Not a great answer but there it is.
db
MegaHz said:
hello,
unfortunately i cannot turn on the bluetooth from comm manager, it turns on and after 1 second is off again.
any solution for this problem?
thanks.
Click to expand...
Click to collapse
Hi, I have a Uk version of the touch cruise and I have the same problem. I just did a hard reset but the problem remains. Turning bluetooth on is impossible. It just try's to turn it on and shuts it off immediately.
Maybe it has something to do with GPRS? I am always connected to the internet. I tried to disconnect but then bluetooth still doesn't work. Can anyone help? Thnx!
No one has a clue?
I had this prob with bluetooth and wifi following the use of wmwifirouter- after hard reset and no wmwifi all goes well...
On a French SFR rom
any other idea?
Same problem... beginning to wish I'd gone all Apple and bought an iPhone. Anyway.... To trun it on, I had to go to Comm Manager>Settings>Bluetooth>Mode>Turn on Bluetooth. That worked despite the Comm Manager still showing Bluetooth as "off".
It only connects 1/2 the time to my headset or handsfree in the car
Otherwise, the phone crashes only once a day! Great! Thanks!
ok, great to see more people having the same problem but i hope that someone has a sollution...
When I try to turn bluetooth on in the communications settings i get a message saying there is a hardware error! :S
Ohw btw, I'm not using any router programs or other and my WIFI works fine.
has anybody of you having this problem tried to change to another rom?
if yes? did this worked?
any news on this?
No news, I don't want to try for a different rom because i don't think it will change anything. It just seems like its a faulty device which is a real shame. I've already contacted the place where i bought it and see if i can get a new one.
I also have problems with my microphone during calls, photo camera does often not work and the touchpad reacts very slowly to my touches. Very annoying!!!!
Yup, am returning mine to HTC aswell. Not even sure I want it back. WiFi stopped working too, and then it stopped receiving text messages, and everyone said they couldn't hear me when I called them. Great
Some of you guys got a bad device, there are thousands out there working properly.
If some of you guys flashed a newer Radio, the one form the test-ROM, then this is your problem.
And some of you guys have a quite gay branded ROM (slow responsiveness of touchpad). The original HTC ROM on the FTP and even more so a cooked ROM would solve alot of your problems. But be aware, flashing without having a backup ready is going to void your warranty if you want to exchange it having a custom/non-original ROM on the device.
What's up Schaggo
I am experiencing the same problem these gentlemen are mentioning and my ROM is not gay or lesbian. It is the original one.
TC is my 7th HTC device and I can see the quality of the ROMs decreasing a lot on every new device. I feel like HTC needs a real competitor to move up its arse quicker.
All I can say is that it really annoys me to hard reset this [email protected] everytime I "accidentally" use a native feature called Flight Mode. By bluetooth seems to fly away and never get back.
Lots of time the GPRS settings have to be reconfigured too. Some people I know have problems with GMail IMAP4 accounts when sending messages after some time. I never had this problem on my Kaiser neither on my Niki.
The lack of a video driver really is an egg on our faces, because I can't believe my ole Qtek 9100 responds quicker than these "all the bells and whistles" Qualcomm 7200 super-duper geared up devices.
So, if you feel like not contributing, please do not mess around.
Your signature tells me you are a wise man, but your comments show me otherway.
-Feaps
PB of BT still there with custom rom
MegaHz said:
has anybody of you having this problem tried to change to another rom?
if yes? did this worked?
Click to expand...
Click to collapse
Hi
I've tried many custom rom and the PB continue. "PB with the hardware oh BT".
Hard reset doent change anything.
my initial rom (SFR France) was working
custom rom (blackwidow + Bepe 058) are buging...
nedd some help !
Thanks alot for that input feaps. I guess I have to clarify a little bit.
My answer was supposed to be pointing in different directions. The first and general information I tried to contribute was, that it is not a common Polaris problem to have a broken Bluetooth unit. Which doesn't help at all to ppl affected, but it should tell them, that they probably got a bad device and should exchange it first before blameing htc in general and shouting for an iPhone.
It only was partially directed at specific persons. At madinga for example: did you try hardresetting your device? It could be a corruption in your system which causes all those problems. I doubt it though, if you suffer the loss of so many functions at the same time I suspect the mainboard to be broken. But nonetheless, hardreset it, see if its working, BEFORE you put your backup back on the device again since that could restore the corruption. If it doesnt work, exchange your unit, I hope you'll get a working one back.
My second line was directed at all people which have overwritten their original Radio with the 1.58.25.14 originating from the HTC Test ROM which can be found on the ftp server. The Bluetooth part of that Radio is flawed and leads to the problems described in this thread. I quite nicely pointed that out and told people where to have a look before shouting around. I do know that because I tried it myself and couldnt get my Bluetooth devices working. Once I flashed the original Radio back, my BT problems were gone.
And my third line - in which I may chose the wrong words, 'gay' for example - holds information targeted at people with for example the branded french SFR ROM or the original HTC french ROM. The SFR ROM is just horribly branded and if you go through the threads here you'll find people complaining about problems which then turn out to be related to the ROM. The french HTC ROM is flawed as well, it has severe problems with the volume control. I don't exactly remember what it was, but it's a flawed ROM, thats for sure. The German o2 ROM isnt flawless either, I know that because I originally had that ROM. Once I flashed my orbit 2 with the original HTC WWE ROM, I found it to be working alot better and smoother than with the o2 ROM originally provided. And this is where my last line comes into play: if you suffer problems related to your currently flashed ROM, they could be diminished by flashing an alternative ROM. But if your device is broken, and I personally and strongly believe that everybody fooling around in this forum should be intelligent enough and able to determine the sense of my words, eg. if he/she suffers a ROM problem or if the device just simply is dead and take appropriate actions.
And now to your contribution feaps. I feel personally attacked by your words. Thats why I defended my words in all the paragraphs above. Trust me, I've had enough mobile devices of all sorts to know what it means to get a not working once. Its frustrating and makes you want to throw it out of the window. And being able to see the quality decrease over time is just another drop on a hot stone. I agree. But be honest, if your BT unit works and stopps working once you engage a software based function, the problem is software related, dont you think? As for the GPRS settings, I cant tell. Since I use a free ROM which has the wizard built in (o2 removed it from their ROM) I didnt switch my SIM and the configuration worked, automatically and every single time. And I do use IMAP as well on my personal E-Mail account. Until now I didnt run across any problems, so I cant give you any feedback on that either.
So rethink again if I mess around or not or if I actually try to contribute and help the freshmen, coming into this forum and flashing whatever they find and breaking their devices. And recommending to flash the original HTC ROM, which should be/is the base for everything floating around, breaking your devices, is a serious input to everybody.
Edit: I forgot to add, pointed at nooms, there are cooked ROMs out there which stupidly have the new, flawed Radio baked in. Which Radio are you on? Try Start > Settings > Tab System > Device Information > Tab Version. Are you inadvertedly still on Radio 1.58.25.14 or back to (original) 1.58.21.23?
Hi everyone,
I agree with Schaggo completely. Most of the time problems have something to do with the software on the device. But I a not a tweaker like most of you guys, i've just bought my first (and hopefully not last) HTC phone. If i have problems of some kind, all i can do is reset the thing. A hard reset if necessary. I've done that many times. I can't change the software that comes standard and i don't think i should be the one who has to do that. Shouldnt HTC be doing that??
Anyway, Bluetooth keeps saying it has an hardware error. My radio version is a standard 1.58.21.23 but isnt finding any radiostations here in holland. Is it also broken? (sorry, i know, its a bit off topic)
You're right
schaggo said:
(...)
My answer was supposed to be pointing in different directions.
(...)
And now to your contribution feaps. I feel personally attacked by your words.
(...)
But be honest, if your BT unit works and stopps working once you engage a software based function, the problem is software related, dont you think?
(...)
As for the GPRS settings, I cant tell. Since I use a free ROM which has the wizard built in (o2 removed it from their ROM) I didnt switch my SIM and the configuration worked, automatically and every single time. And I do use IMAP as well on my personal E-Mail account. Until now I didnt run across any problems, so I cant give you any feedback on that either.
(...)
So rethink again if I mess around or not or if I actually try to contribute and help the freshmen, coming into this forum and flashing whatever they find and breaking their devices.
Click to expand...
Click to collapse
Well put. Sorry for being rude, but I keep seeing people offending others day after day in this forum that used to be high level; but that doesn't mean I should act the same way.
I totally misread you and please accept my apologies.
My ROM is: 1.25.405.1 WWE
ROM Date: 12/11/07
Radio Version: 1.58.21.23
Protocol Version: 25.65.30.04H
One thing I could notice is that HTC has a flaw in the Flush HKCU to Permanent Memory While Shutting Down. Some keys are not written.
One example is the MagiCall (an app I use) registration key. The software maker had to write a flush app for doing that. Another example is the Start>Settings>System>Error reporting. No matter what you chose, after a power cycle or a soft reset, it always go back to "Disable...".
I have, also, already tested the device after the hard reset with no extra apps on it. Same lame behavior on BT...
So, SW QA levels are really dropping fast on new HTC models. That is pretty bad.
But anyway, I have an open case with HTC and if I find something contributive I will toch base with this thread.
Once again, sorry for being rude.
Best,
-Feaps
Furio83 said:
Anyway, Bluetooth keeps saying it has an hardware error. My radio version is a standard 1.58.21.23 but isnt finding any radiostations here in holland. Is it also broken? (sorry, i know, its a bit off topic)
Click to expand...
Click to collapse
Then I guess you most probably got a bad unit. I guess the only solution at this time is an exchange.
The Radio-Firmware doesnt control the FM Radio btw The Radio-Firmware controls connections to the providers network, Wireless LAN and Bluetooth. But the FM Radio seems to be really bad in the Polaris, a lot of ppl I know complain about it.
feaps said:
please accept my apologies.
Click to expand...
Click to collapse
No problem dude! There is no need for such an excessive appology. We are in a Forum and people have different oppinions and I think its totally acceptable to shout at each other. I just wanted to express that I'm not in accord regarding your judgement of my post. But thanks a lot, I seriously really appreciate it!
Yes, your device seems pretty standard to me and the scenario you described logically made me think of a software error. But this seems very unlikely now. I'm out of ideas for the moment then, I guess you have to return or exchange it too.
You are perfectly right about the dropping SW QA though. You can notice the registry glitch in other areas as well: backlight timer always reset to 30 sec, and there are more settings all over the place which don't get saved properly.
Again, no problem, everybody lets be cool
Bluetooth doesn't turn on
I have the same problem. Did anyone find a solution?
Also camera fails to initialize, touch pad is sometimes very slow for initial reaction. I have NO added programs beyond manafacturer originals and have tried a number of hard resets. Doesn't help.
Jeremy

[Q] Device reset on incoming call

Hi,
does anybody knows, where could be bug? When I establish data connection on my raphael, any incoming call or message in most cases cause reset of device. I have no idea, what to check on..
kaliginium
kaliginium said:
Hi,
does anybody knows, where could be bug? When I establish data connection on my raphael, any incoming call or message in most cases cause reset of device. I have no idea, what to check on..
kaliginium
Click to expand...
Click to collapse
Can you give more informatiom?
Is your phone GSM or CDMA?
What ROM are you using?
Have you added any other apps?
Hi! It is important if you can tell us if this is a newer problem or if this had always been the case with your device. Also, if this always happened to your knowledge, can you tell us when you had acquired the device?
Here are a few suggestions:
1) If you can back up all your files/contacts/etc. and try to flash the stock ROM, assuming you are using the original ROM. It could be possible that software could be affecting it. This would be best to wipe evrything away and begin with a cleaner slate.
2) How about, if you can do this on your own, try to install HardSPL, and flashing it to a customized ROM. Chances are if there is a bug in the stock software it could be coming from the stock ROM that is being used (if the first way does not work for you).
3) could it be a virus? I would suggest to install an anti-virus program (I use Lookout Mobile for Windows Mobile - its free and has a pretty good security suite). I can't say how effective its anti-virus program is but it has been pretty good for me. Even install one that is only a trial (ESET for Mobile, Kaspersky for Mobile, etc.) and have it scan your device. If anyone know how good Lookout Mobile is please let me know!
4) Could it be a radio firmware issue? I am not too familiar with this I would hope someone can answer this and maybe they can help you get the proper radio verison and flash it (I believe that you would need to unlock the BIOS - HardSPL basically - to ensure safe flashing of the radio firmware).
5) If the software is not a problem, chances are it could be a hardware issue, as in maybe the GSM chip is bad. I would be more inclined that it is a software problem rather than hardware but you can not rule out hardware.
This is assuming that you are using the GSM version (not CDMA version as I believe there is a separate forum for that).
I hope i am able to help you! Yes I agree with johnjctt1 - It could be an application you have installed that would be simple enough to rememdy, maybe try uninstalling each app, beginning with the newest one you had installed, and try data/voice simultaneously to see if an app was causing the reboot of the device.
Good luck and let us know the progress! This is the best advice I can give you without knowing a little more about your device. johnjctt1 was correct in asking those set of questions. I love how we all can support one another!

What Does RIL Do?

What does RIL Do for our phones? is it safe for us wind users to upgrade it using the GetRIL app? thanks for any info, i asked Nyc, but i didnt want to bug him anymroe any input would be nice
The RIL is the Radio Interface Layer. Each baseband chip has its own set of commands. Android uses a common set of commands. The RIL converts android's baseband commands to the commands the baseband chip understands. That is how your phone talks to the radio to make phone calls, send and receive sms, send and receive packet data, etc. Yes, GetRil is safe to use. If you use a stock rom you don't need it. If you use a custom rom the RIL might be mismatched to your baseband chip. GetRil will change the RIL files to match the baseband chip. It is not necessary but it doesn't hurt either.
I am also with Wind mobile ive had everyone tell me when im driving in my truck they cant hear me its all static and stuff. Ive tried GitRIL and it didnt seem to help but i would be interested to hear what other Wind users are experiencing
Making bad decision's one at a time.
Getril doesnt increases your voice quality, it does make.sure your baseband doesnt get puesdo command from your rom to cause kernel panic or baseband crash that you lose signals. It does effect slightly ur signals and data service to avoid packet loss.
Sent via G2X-SINGH UI
aha i tried to do it but it says failed

[Q] What is it about Android that makes creating roms difficult?

What exactly is it about android that makes developing new roms so difficult? For example, most ICS roms for the G2x are somewhat unstable, is that just because devs need to write drivers from scratch, or is it something else that I'm missing?
Another way of saying this would be, what makes "installing" Android different from installing Windows on a PC? (I understand Android needs to flash roms and windows can just install from a disk, but beyond that?)
Also, I don't mean to complain at all, I very much appreciate all the hard work the devs have been putting into these roms; I'm just curious what specifically makes it so challenging?
the problem most of the time comes from how the rom interacts with the hardware.
when an app needs to do something, it calls a function (for example turn on wifi) the rom gets this call and passes it to the kernel. the kernel then passes this call to the hardware which powers on the wifi.
APP>ROM>KERNEL>HARDWARE
a problem can occur at any point in that chain. the app can call a function that does not exist in that version of android, or the rom can call part of the kernel which is not there, or the kernel can try to do something that cant be done hardware wise.
oversimplifying it, porting a version of android is basically matching the function calls from the rom, to that of a kernel that works for this phone.
Now, alot of the problems we have been having with ICS on our phones is because of Hardware Acceleration. we have no offical kernel that supports it. without that we have no way for the calls from the rom to get to the hardware.
the INCREDIBLE devs at Cyanogen figured this out, they wrote those functions themselves. the part that makes this incredible is the fact that they did not know what to call, or where to send it. they had to guess at EVERYTHING! unfornately this also causes problems, while they may have gotten the functions 90% correct, 10% is still wrong. and that is what is most likely causing problems for us. (a stupid example i saw once is that they made a new brightness driver, but it was off by 1 number, so most of the brightness settings would work, but if you tried to set it to 0, it would really set it to -1 and all hell would break loose)
The reason it works so well for windows, is because when a hardware manufacturer makes a piece of hardware (wifi card) they also provide drivers that are pre-made for that version of windows, that way windows can call on standard functions, and that driver will answer those calls! unlike computers, phones very rarely switch hardware, so the hardware manufacturers only give the information of how to make drivers to the phone manufacturers
i hope you get what im trying to say.... i tend to ramble
Klathmon said:
the problem most of the time comes from how the rom interacts with the hardware.
when an app needs to do something, it calls a function (for example turn on wifi) the rom gets this call and passes it to the kernel. the kernel then passes this call to the hardware which powers on the wifi.
APP>ROM>KERNEL>HARDWARE
a problem can occur at any point in that chain. the app can call a function that does not exist in that version of android, or the rom can call part of the kernel which is not there, or the kernel can try to do something that cant be done hardware wise.
oversimplifying it, porting a version of android is basically matching the function calls from the rom, to that of a kernel that works for this phone.
Now, alot of the problems we have been having with ICS on our phones is because of Hardware Acceleration. we have no offical kernel that supports it. without that we have no way for the calls from the rom to get to the hardware.
the INCREDIBLE devs at Cyanogen figured this out, they wrote those functions themselves. the part that makes this incredible is the fact that they did not know what to call, or where to send it. they had to guess at EVERYTHING! unfornately this also causes problems, while they may have gotten the functions 90% correct, 10% is still wrong. and that is what is most likely causing problems for us. (a stupid example i saw once is that they made a new brightness driver, but it was off by 1 number, so most of the brightness settings would work, but if you tried to set it to 0, it would really set it to -1 and all hell would break loose)
The reason it works so well for windows, is because when a hardware manufacturer makes a piece of hardware (wifi card) they also provide drivers that are pre-made for that version of windows, that way windows can call on standard functions, and that driver will answer those calls! unlike computers, phones very rarely switch hardware, so the hardware manufacturers only give the information of how to make drivers to the phone manufacturers
i hope you get what im trying to say.... i tend to ramble
Click to expand...
Click to collapse
That's a very good explanation! Makes perfect sense to me.
Sure does!!!
Sent from my LG-P999 using xda premium

[QUESTION] Is there any hardware testing and diagnostic tool?

Update 25-11-21: My friend told me that there are already some hardware-based physical tools that implement JTAG (IEEE 1149.1). I couldn't be able to say more about this because know nothing about electronics. (Those are very scarse to get where I live).
I'm recently entering this world of mobile phones and I was struggling with a phone which was unable to get the carrier signal. And a friend of mine which has been in this world for like 6 years now said: "It has to be a problem with the modem (hardware integrated component to communicate with the carrier)". By the way, he reached this conclussion after several practical testing without any successfully result. Coincidently he had a complete board for that cellphone model and after a replacement, the phone was able to have reception (also call and receive). But this was a radical solution, like formatting a PC because of one of the installed programs is just misbehaving.
So my doubt: Is there any hardware testing or diagnostic tool capable of interact with each (or several) components on the board and performance several actions and get their status?
For instance, let's say, before replacing the entire board from the example before, we were aiming to check the integrated modem status and if possible send instructions to send and receive instructions from the carrier. Can this be done? Be it this testing and diagnostic tool software or hardware based? Something resembling the POST (Power-On Self-Test) performed when a computer boots up, but be it done for testing and information gathering arbitrarily.
Full disclosure, before replacing the entire board we hard reset and also flashed the phone, without any successfull outcome. We spent like 4 days banging our heads against the wall. With such a hypothetic tool we could have saved ourselves a lot of time and effort. Maybe such a tool already exists and here I am posting out of ignorance. In both cases, any help is appreciated.
PS: I used the term modem in this post but I don't truly know if this is the proper term to refer, my apologies in advance.
PS1: I stumbled upon this tool named PC-Doctor but the Android version has to be installed in the phone's Android OS. But almost all phones we receive are close to dead (logo stuck, boot loop, FRP bypassing required), so installing an APK probably would not be an optimal solution here.
Thanks in advance!
ppdmartell said:
I'm recently entering this world of mobile phones and I was struggling with a phone which was unable to get the carrier signal. And a friend of mine which has been in this world for like 6 years now said: "It has to be a problem with the modem (hardware integrated component to communicate with the carrier)". By the way, he reached this conclussion after several practical testing without any successfully result. Coincidently he had a complete board for that cellphone model and after a replacement, the phone was able to have reception (also call and receive). But this was a radical solution, like formatting a PC because of one of the installed programs is just misbehaving.
So my doubt: Is there any hardware testing or diagnostic tool capable of interact with each (or several) components on the board and performance several actions and get their status?
For instance, let's say, before replacing the entire board from the example before, we were aiming to check the integrated modem status and if possible send instructions to send and receive instructions from the carrier. Can this be done? Be it this testing and diagnostic tool software or hardware based?
Full disclosure, before replacing the entire board we hard reset and also flashed the phone, without any successfull outcome. We spent like 4 days banging our heads against the wall. With such a hypothetic tool we could have saved ourselves a lot of time and effort. Maybe such a tool already exists and here I am posting out of ignorance. In both cases, any help is appreciated.
PS: I used the term modem in this post but I don't truly know if this is the proper term to refer, my apologies in advance.
PS1: I stumbled upon this tool named PC-Doctor but the Android version has to be installed in the phone's Android OS. But almost all phones we receive are close to dead (logo stuck, boot loop, FRP bypassing required), so installing an APK probably would not be an optimal solution here.
Thanks in advance!
Click to expand...
Click to collapse
When you say modem, that could be taken to mean two things.
1) it could refer to the radio, the actual radio hardware component.
2) it could refer to the modem software that is part of your stock firmware and controls the RIL(Radio Interface Layer).
Typically, when we in this community say "modem", we are referring to the modem software. When we are referring to the hardware, we say "radio".
In the case of your device, it could be that you had the proper radio hardware and that it was "able" to function but possibly your modem software was not correct. Or it could have been that you did have the correct modem software installed but your radio hardware component was actually damaged or not able to function.
If it was an issue with improper modem software, you could have potentially downloaded and flashed the correct modem software to solve the issue.
If it was an actual fault in the radio hardware, switching the motherboard or at least unsoldering the radio component and replacing it with a new radio component is the correct solution.
If the device was from a different country/region or if the device was from a different carrier than the carrier that you were trying to activate it with, it was probably just a case of needing to flash a compatible modem software to work in your country/region or on your carrier network.
Yes, there are tools to diagnose the hardware but they are generally software based and are useless to diagnose the device if it doesn't at least power on and function in some manner. I know there are android apps available that can be used to test/diagnose the internal hardware components but they all probably require rooting the device.
It stands to reason that there should be various PC software based android hardware component testing/diagnostic tools that are used via connecting the device to PC but I've never looked into that or ever had a need for them.
As for hardware based tools to test or diagnose Android based hardware components, I'm not versed in what they could be, but I'm fairly certain that they exist and are used, it would not make any sense if they did not exist.
A Google search for:
"Android hardware testing and diagnostic tools"
Should find lots of tools to start researching.
Droidriven said:
When you say modem, that could be taken to mean two things.
1) it could refer to the radio, the actual radio hardware component.
2) it could refer to the modem software that is part of your stock firmware and controls the RIL(Radio Interface Layer).
Typically, when we in this community say "modem", we are referring to the modem software. When we are referring to the hardware, we say "radio".
In the case of your device, it could be that you had the proper radio hardware and that it was "able" to function but possibly your modem software was not correct. Or it could have been that you did have the correct modem software installed but your radio hardware component was actually damaged or not able to function.
If it was an issue with improper modem software, you could have potentially downloaded and flashed the correct modem software to solve the issue.
If it was an actual fault in the radio hardware, switching the motherboard or at least unsoldering the radio component and replacing it with a new radio component is the correct solution.
If the device was from a different country/region or if the device was from a different carrier than the carrier that you were trying to activate it with, it was probably just a case of needing to flash a compatible modem software to work in your country/region or on your carrier network.
Yes, there are tools to diagnose the hardware but they are generally software based and are useless to diagnose the device if it doesn't at least power on and function in some manner. I know there are android apps available that can be used to test/diagnose the internal hardware components but they all probably require rooting the device.
It stands to reason that there should be various PC software based android hardware component testing/diagnostic tools that are used via connecting the device to PC but I've never looked into that or ever had a need for them.
As for hardware based tools to test or diagnose Android based hardware components, I'm not versed in what they could be, but I'm fairly certain that they exist and are used, it would not make any sense if they did not exist.
A Google search for:
"Android hardware testing and diagnostic tools"
Should find lots of tools to start researching.
Click to expand...
Click to collapse
Honestly I didn't know radio was the proper term to refer that hardware component. Now I do and thanks to you.
However, in this case I just used a practical problem to communicate my idea. I should have expressed myself in a better way. The underlying issue was the diagnostic tool itself, and not the radio problem I used, maybe like some sort of low-level query-based tool to test and diagnose the components.
And I also should have done some research in google before posting here too. Maybe I got lucky. Just in case I could find any solution to my issue, I will gladly post it here.
Thanks for the reply.

Categories

Resources