So just getting into the whole rooting and custom ROM install thing, still trying to fully understand what everything means.
So I figured WiMax refers to 4G, hopefully right about that.
What is a Kernel?
What are the Radios and what is included in them?
Feel free to use computer analogies, I'm pretty tech savvy with that.
Sent from my PC36100 using XDA App
kernels types: bridges hardware and softwares processes.
Radio: Also referred as GSM (see below) - commonly used in the form `upgrading the Radio/GSM` - in the field of ROM upgrading. The `Radio` is essentially a ROM that controls the phone function part (as oppose to PDA function part) of your phone. Upgrading this `Radio` software may have effect on your phone reception quality, battery life (optimized phone function), signal strength, etc.
GSM: A system of mobile radio communications. Most common 2G standard. Often used on xda-developers somewhat confusingly to refer to the radio protocol stack or `Radio` in XDA devices. This is slightly misleading as 3G HTC phones use a W-CDMA stack for the 3G communications, and GSM for 2G. In some languages, GSM also refers to the mobile phone itself.
wiki wiki
The kernel, in very non-technical terms, is basically the lower level operating system of the phone. So many things run through the kernel that it's important to choose a kernel that is compatible with the rom you are using. For example, using the wrong kernel on an AOSP rom like MIUI will cause you to lose bluetooth, wifi, or many other things.
Kernels can control how your processor works too. With the right kernel you can overclock, underclock your phone for performance, or better battery life. My personal favorite is SavagedZen if you are using an AOSP rom. They do a great job of taking every request from every rom/app developer and putting the tweaks in their kernel. They support all the HDMI apps out there, they support Wimax (4G), and they are really well optimized.
As far as radios, that is the software that helps your phone connect to things like Wifi, bluetooth, 4G, 3G, GPS, and anything else that requires data come to your phone wirelessly.
Hope that answers your question in simple terms.
Related
Does anyone have any ressources about the internal Software Structures of the Desire? I'm especially interested in the part where the netlock is checked ... questions here are: in which software module is this stuff checked - or which hardware part is responsible for the check?
What do you call the 'netlock' ?? The carrier / simlocking stuff?
AFAIK that's done in the SPL and / or the radio firmware.
Most qualcomm chipsets work with two processors. The real application cpu on which the android OS runs, and a second (slower) processor dedicated on handling all the radio-like functions. Managing the gsm / 3g connections, gps communication, apparently talking to the QDSP chipset for camera control, etc...
Those two processors communicate with a bit of shared RAM. The 'radio firmware' is the software running on those second processors. Little (or even none?) hacking is done on that, we just collect the different versions we find in the field and see what the differences are, results are different person to person.
The SPL is the earliest stage of booting / turning on, mostly the thing that makes sure the radio and OS are started up, and checks what kind of buttons are held to go into recovery or fastboot modes and the like. Compared to normal PC's, see it like the BIOS or maybe even the step before that.
I don't know where the carrier locking is done on the Desire, but seeing as people who flashed the latest radios suddenly get a 'locked' message again, it's probably _before_ the radio image, so that'll be in the SPL.
Details about that are sparse to say the least.. of all the hackers / modders / rom-cooks, only a little handful on the whole of XDA made modified SPL's, and mostly in the Windows Mobile domain. It's also the most guarded piece of design I think by HTC, since it controls all the protection mechanisms.
So good luck finding info .
I have been having a lot of trouble with my Epic's radio behavior since the EC05 radio update. It seems that the normal Samsung "radio stupidity" that I have seen in several of their devices is worse than ever now. The best radio for call performance I have used so far was DG27's (though not data). Essentially, what it is as far as I can determine by using utilities to monitor radio operation, is poor CDMA handoff configuration.
What it does is, for no good reason, switch from a cell site providing a good signal level, to one providing a bad signal level for no reason. Either this, or it holds onto a weakening set of towers while moving, until it goes out of their range and the call drops. The phone will then display the no service message for a few seconds, and then will pick up perfect signal from a different set of towers. I can even watch this happen by driving down a given road while on a call, with another phone in my cup holder. The Epic will start to break up and show very low signal levels, while the other is doing perfectly. Additionally, the direction you drive down this (2 lane) road also has an effect.
I have fixed this before on non smartphones by altering some of the CDMA radio values. T_Add, T_Drop, T_Comp, T_Tdrop. My solution is to increase the threshold on T_Comp a little bit, and drop the T_Tdrop also a little bit. The problem is that I cannot figure how to do this on this phone. Very little radio information seems to be available, and the utilities I have do not work completely on this model.
This issue with how they program their radios seems to be a common Samsung problem, to a much greater degree than with other manufacturers. Sanyo, Palm, and Motorola seem to do a much better job with this, even in cases where they use the same radio chipsets.
I am feeling like a lot of people will find this matter interesting and/or of benefit to resolve.
The only problem I see and I'm sure someone will correct me is the RIL is closed source. Also android was designed around gsm and not cdma. This makes the manufacture and carrier to design a "wrapper" to get the RIL to work on cdma. Now if samsung would release the source.code I'm sure making changes wouldn't be so hard
On a side note I know there's a dialer code ( I forget what it is ) that you can go and play with some settings. One of them being able to switch to cdma instead of cdma/gsm that it is by default.
Sent from my SPH-D700 using Tapatalk
Maybe try ##3282# or *#147852#
My data does the same thing on ec05. I'll have perfect signal and then all of a sudden nothing for like a minute and then it comes back. Least im not the only one
Sent From My Evo Killer!!!
musclehead84 said:
My data does the same thing on ec05. I'll have perfect signal and then all of a sudden nothing for like a minute and then it comes back. Least im not the only one
Sent From My Evo Killer!!!
Click to expand...
Click to collapse
It isn't the data driving me nuts. Data sessions pick up again quickly. It's the dropped calls. Either way, it is partially a symptom of the same problem. The phone is promoting weak towers, sometimes in favor of strong ones, to the active set - which it should not be.
MysteryEmotionz said:
The only problem I see and I'm sure someone will correct me is the RIL is closed source. Also android was designed around gsm and not cdma. This makes the manufacture and carrier to design a "wrapper" to get the RIL to work on cdma. Now if samsung would release the source.code I'm sure making changes wouldn't be so hard
On a side note I know there's a dialer code ( I forget what it is ) that you can go and play with some settings. One of them being able to switch to cdma instead of cdma/gsm that it is by default.
...
Click to expand...
Click to collapse
No and yes. CDMA support was a hack in versions prior to 2.0. Android 2.0 (and later) has inbuilt features intended to support CDMA networks. Some of the companies are still using some legacy code, and some of nomenclature used within the system parameters still reflects GSM however.
This, however, is irrelevant in my belief. I do not think that these parameters are a function of RIL, as RIL is simply the intermediary between the "computer" and "telephone" components in a smartphone. I believe that these issues exist purely, or nearly so, within the "telephone" section of the device.
running_the_dream said:
Maybe try ##3282# or *#147852#
Click to expand...
Click to collapse
What is this ##147852#? I cannot find it in any information I have, and it has no effect on the phone itself.
Not ###47852#. *#147852#. I don't know the name of the dialer. I call it the master meenu. It basically let's you access various front end user settings on the phone. I have used it to reset my 4g radio. Anyway, you may try the testing/phone information menu to change the cdma setting. I'm totally taking a shot in the dark on that, but it does seem to allow you to alter the radio preference.
running_the_dream said:
Not ###47852#. *#147852#. I don't know the name of the dialer. I call it the master meenu. It basically let's you access various front end user settings on the phone. I have used it to reset my 4g radio. Anyway, you may try the testing/phone information menu to change the cdma setting. I'm totally taking a shot in the dark on that, but it does seem to allow you to alter the radio preference.
Click to expand...
Click to collapse
Yes, totally misread that. Nothing seems to apply however, as I do not think it is a software parameter on the phone end. The WiMAX radio is software controlled, through a driver in the operating system. The combination of CDMA radio and baseband processor are more or less an independent device which essentially lives on its own, with its own configuration. It is told what to do through the RIL, which is a piece of software that allows the computer aspect of the phone to talk to the radio, passing it instructions which it then acts upon according to its own programming and configuration. The RIL also allows the radio to communicate its status to the rest of the system.
I am really thinking that this will not be a setting that can be modified from within the phone itself, but will require some external involvement, similar to QPST. On this chipset, however, QPST does not appear to be able to manage these parameters.
If you find out any more info please pass it along. Thank you.
Sent From My Evo Killer!!!
Ah that's really interesting. Wish I could help.
hi,
well i'm against that policy, not able to post at developer threads under 10 posts, else I would have question that directly,...
I've tried several roms and ended at slim beam, first to 4.2.1 which states at stable but also tested the new one 4.2.2 build 2.5
actually i'm fine with the roms, also slim bean but I do have a 3 major issues with all of them which may be related to S3 and asop/cm:
1.) problem using my apple iphone earbuds (yes I'm a iphone user too)
sometimes after mute the microphone, it won't work after de-mute, keep on muted !
microphone not working after re-connecting earbud on a running call, sometimes no audio on earbuds too, sometimes audio even do not work for the whole device -> reboot etc,...
I've found several possible solutions, non of them has worked.
why android doesn't work with that kind of TRRS earbuds, are they incompatible from hardware point of view, do I need special ones which will work on S3.
2.) problem with direct dialing from calendar, not respecting RFC2806
i really need this very often to join conference calls, sometimes the host creates an conf call and including a number with pin as the location.
well almost every mobile os recognizes this and i'm able to direct dial in on selecting the string: iphone, win, even blackberry, but not android.
i know there might be additional apps which can handle this, but it should be implemented into core apps as this is a well known standard and specified in a RFC.
3.) not recognize AP with highest signal strengh within same SSID
it seems that android devices are not able to seamless switch over to different AP within a wifi network with same SSID.
if moving out of range of AP1 and into range of AP2, android devices for some reason are not able to switch to AP2 (with higher signal strengh), therefore it states at AP1 without beeing able to establish any connectivity (because AP1 out of range). as workaround users needs to disable/enable wifi ;-(
this is also something where I have to find a workaround in my current project (creating huge wifi network over europe), because market share of androids is that high and it still have this serious annoying bug.
thanks,
nean
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
10 post rule is there to protect developers from spam and users not knowing what belongs in a development thread and what belongs in Q&A
1. Headphones > Most likely thats just an issue with roms that are version > 4.1.2. Not all the bugs have been worked out, see if you can replicate it with another pair of headphones.
2. I suspect the same thing is going on here, or you would need some more powerful calendar sort of app.
3. This isnt because it doesnt recognize, its because Android is still connected to the last network and says to itself "no need to scan again, I'm already connected". This has to do with how the OS is implemented, not because its a bug with Android. I'm also fairly sure that most other devices do the same thing
CNexus said:
1. Headphones > Most likely thats just an issue with roms that are version > 4.1.2. Not all the bugs have been worked out, see if you can replicate it with another pair of headphones.
2. I suspect the same thing is going on here, or you would need some more powerful calendar sort of app.
3. This isnt because it doesnt recognize, its because Android is still connected to the last network and says to itself "no need to scan again, I'm already connected". This has to do with how the OS is implemented, not because its a bug with Android. I'm also fairly sure that most other devices do the same thing
Click to expand...
Click to collapse
thanks for the reply.
ad 1,2,3.) hmmm, is this working on googles stock os and eg on nexus?
ad 3.) this is only related to android devices, as tested in the lab with several other handheld devices with different kind of os'es. ios, blackberry, windows mobile, etc, all work and do seamless switchover except android. well the last known network and the new one is actually the same wifi network which is specified due SSID, so if android's rescan logic is related to that kind of info it may be wise to consider acces point strength as well, just like all the other os'ses,....
nean24 said:
ad 3.) this is only related to android devices, as tested in the lab with several other handheld devices with different kind of os'es. ios, blackberry, windows mobile, etc, all work and do seamless switchover except android. well the last known network and the new one is actually the same wifi network which is specified due SSID, so if android's rescan logic is related to that kind of info it may be wise to consider acces point strength as well, just like all the other os'ses,....
Click to expand...
Click to collapse
Did you test using stock os and not a AOSP rom like stated in the OP? You can't blame the OS for a issue if it is moded in any shape or form. Try using straight up stock TW and see if it works. AOSP and CM are not 100% designed to work on this phone flawlessly.
tazfanatic said:
Did you test using stock os and not a AOSP rom like stated in the OP? You can't blame the OS for a issue if it is moded in any shape or form. Try using straight up stock TW and see if it works. AOSP and CM are not 100% designed to work on this phone flawlessly.
Click to expand...
Click to collapse
thats correct, but it doesn't work on galaxy stock os either, that's why I've tried custom roms just to find out if its related to samsung stock rom or if its a general android behavior. well the outcome was that it works on aosp/cm a bit "better" (shorter timeout) but not seamless.
my intention is not about to blame anyone, just like to find out where I can adress this issue, or do I need to get in contact with google?
rgrds
Simple question, really.
I'm running Toggle2G on my Note II with a stock-based ROM, but I had to resign the whole ROM and any additional updates (even simple modifications to system APKs) don't install unless I resign those too.
Basically, it's a massive pain. It's worth it, because I can switch automatically to 2G when I'm on wifi to save some battery and automatically switch to 3G only in my car because the speakers pick up 2G interference (and back to 2G/3G when I leave the car because Tasker is great). The included app to automatically switch 2G/3G doesn't work particularly well and can result in signal loss, but used sensibly with Tasker it's fine.
Is there a technical reason that this can't become a standard thing in ROMs? Are there any ROM developers who would consider including this as standard? Is there a ROM I've missed that includes it?
Thanks.
I hope to benefit from someone's WIFI expertise.
Bought for my wife a T-Mobile branded SGS3 replacing her older SGS4G ["S 4G"] model for more power, memory, etc etc. I noticed from the beginning that, compared to all my other handsets, tablets, PC/laptops, this one was troubled on WIFI connections. Found lots of posts around the web, read up on fixes. Gathered the tools together, erased the ROM completely, started from scratch with stock T-Mo ROM, rooted and debloated it. Made some of the standard changes to WIFI options: stopped scanning, disabled power-saving, reset the home/office WIFI to channel 11 , "N" band only. Things improved in that stable, controlled setting.
but 'on the road' with multiple hotspots, hotels, offices, T-mo data service, etc it is still very difficult to use. It will drop otherwise good WIFI connections, and hang in the midst of operating on WIFI. To give a simple example: go somewhere new, find WIFI, connect to WIFI, check EMAIL, Facebook, Messages - find 10 or so messages unread unresponded, try to download/read/respond and the device will get maybe one or two, then simply stop responding. Wait a minute or two and you get the "WIFI Connected" notice again. repeat, repeat...
What I wonder: how many variants of hardware have there been for T-mo, USA, GS3? Is there a model version I can get that avoids this issue?
cognus said:
I hope to benefit from someone's WIFI expertise.
Bought for my wife a T-Mobile branded SGS3 replacing her older SGS4G ["S 4G"] model for more power, memory, etc etc. I noticed from the beginning that, compared to all my other handsets, tablets, PC/laptops, this one was troubled on WIFI connections. Found lots of posts around the web, read up on fixes. Gathered the tools together, erased the ROM completely, started from scratch with stock T-Mo ROM, rooted and debloated it. Made some of the standard changes to WIFI options: stopped scanning, disabled power-saving, reset the home/office WIFI to channel 11 , "N" band only. Things improved in that stable, controlled setting.
but 'on the road' with multiple hotspots, hotels, offices, T-mo data service, etc it is still very difficult to use. It will drop otherwise good WIFI connections, and hang in the midst of operating on WIFI. To give a simple example: go somewhere new, find WIFI, connect to WIFI, check EMAIL, Facebook, Messages - find 10 or so messages unread unresponded, try to download/read/respond and the device will get maybe one or two, then simply stop responding. Wait a minute or two and you get the "WIFI Connected" notice again. repeat, repeat...
What I wonder: how many variants of hardware have there been for T-mo, USA, GS3? Is there a model version I can get that avoids this issue?
Click to expand...
Click to collapse
Is the phone running full MD5 firmware?
Hardware issue if no restoring was done between devices.
Aerowinder said:
Is the phone running full MD5 firmware?
Hardware issue if no restoring was done between devices.
Click to expand...
Click to collapse
yes, in fact I made utterly sure because somebody else asked the same question, same issue. still very flaky. no odd modems or other custom 'wares, just rooted and a few unnecessary apps uninstalled. how many models of this are there, were they made in different locales?
I assume the SoC is the same, but what about antennae, internal connections, etc? any evil interactions between radios? we don't use Bluetooth, so that one stays off all the time assuming the softswitch works
cognus said:
yes, in fact I made utterly sure because somebody else asked the same question, same issue. still very flaky. no odd modems or other custom 'wares, just rooted and a few unnecessary apps uninstalled. how many models of this are there, were they made in different locales?
I assume the SoC is the same, but what about antennae, internal connections, etc? any evil interactions between radios? we don't use Bluetooth, so that one stays off all the time assuming the softswitch works
Click to expand...
Click to collapse
Well, as far as how many there are? A LOT! LOL! I'd imagine a few hundred thousand US variants, and for the T999 and its variants, close to a hundred thousand maybe? I really don't know, and those numbers did not come from anywhere but my head!
But as far as manufacturing, I am pretty sure they are all built in the same place. But, this does not mean that all of the components are from one location. In fact, from batch to batch of the same part, it can vary by where it was made, but also by what company made it. This is unlikely when dealing with the critcal parts such as the SoC, but the WiFi chip is a Broadcom chip. I have no idea if there are multiple manufacturing locations for it, but it is possible. The memory in all devices often varies greatly by the manufacturer.
Anyway, I do agree with Aerowinder. It is most likely hardware related. I'd look into a Warranty or Insurance exchange.