Might not be your specific issue but if you've installed any of the jailbreak tools, your hosts file might have been modified so that the update won't validate against Apple's server.
Fixing your hosts file is left as an exercise for the reader – obviously if you play the jailbreak game you're savvy enough to repair the hosts file.
RAM is cheap, and there's no lack of space inside the ipad for an extra chip.
The iPad's A4 processor has the RAM inside the A4 package using package-on-package technology. Perhaps the RAM inside the A4 could have been a higher density, but space inside the iPad is not relevant.
Integrating the RAM minimizes the pinout of the A4 and may have allowed them to avoid a difficult-to-breakout BGA pitch. (Changing from a 0.5mm to 0.4mm pitch allows more pins but complicates PCB routing and PCB expense.) I can't tell from this shot of the A4 what pitch is used, but the pin count is pretty high. Note: You need the blank areas in order to breakout traces and place vias.
Patches from clients for cell firmware end up going into a separate tree for that specific client and are not typically propagated back upstream to the baseline, so every phone manufacturer who develops a phone using any given chipset ends up having to find and fix the same set of hundreds of baseband bugs over and over. If that's true, I'm amazed that the cell manufacturers put up with it. That certainly explains why cell phones have so many hundreds (or thousands) of baseband crasher bugs, and it also probably explains why Google is having to relearn all the stuff that Apple just learned a few months ago, and probably Nokia learned a few months before that, and so on.
This is precisely why Apple will never make a CDMA iPhone for Verizon using a Qualcomm chipset. The baseband firmware workload for maintaining fixes for two different chipset vendor's code bases is not justifiable. Apple chose Infineon for their chipset, and I expect their product roadmaps to remain closely aligned regardless of Qualcomm's offerings.
Apple makes a very limited number of hardware SKUs that can be sold worldwide. Don't expect them to offer variants for specific markets.
You have the code to the app-side of the OpenMoko - the Linux side. Do you have the code to the radio stack? The code to access and manipulate the calibration parameters, change RF chipset behaviour, manipulate handoff. Can you add new custom AT commands to the stack? Or are you just interfacing with the radio firmware via AT?
Jailbreaking is the gateway to the real danger of modifying the baseband radio binaries (not apps-processor). In and of itself, I agree that just jailbreaking won't affect the cellular network.
Post-jailbreak modification of the baseband firmware is what is happening when you unlock an iPhone. This modification invalidates the FCC, CE, GCF and PTCRB certifications of the phone. It has the potential to increase support costs and negatively impact network operation.
Its not analogous to using an IP Sockets API to crash your router. Its like modifying the firmware of your router's PHY and then calling customer support because your network is down.
Please understand that the source code to the GSM modem that you don't have access to, is precisely the portion of the iPhone firmware that is being manipulated by the carrier unlock procedure (but afaik not the jailbreak procedure). Jailbreaking, however, is the gateway to the unlock process â" hence the concern about prohibiting Jailbreak.
Every version of modem/phone baseband firmware must pass significant interoperability and carrier approval test suites before it can be sold or distributed. Why? Because cell networks are heterogeneous amalgamations of multiple vendors handsets, basestation equipment, and firmware versions for each. Think its annoying when a cheap WiFi router doesn't interop well with your existing devices? Is it WiFi certified? Now imagine being a network operator when potentially rogue firmware versions randomly take down portions of your billion dollar network...
Should the unlock process accidentally or otherwise modify the modem/phone calibration or call-handling procedures, the network can be impacted. The cell network stability is dependent on all handsets following the same rules â" one misbehaving handset can affect the rest of the cell... Imagine having your call dropped because someone running an unlocked iPhone did a handoff to your cell...
e.g. One early iPhone unlock procedure caused every unlocked device to have the same IMEI â" an identifer which should be unique in the world. This can cause network (and billing) issues analogous to multiple Ethernet devices with the same MAC address.
Thus Apple's concern about unlocking (which required jailbreaking) may be motivated by customer support concerns.
Should poorly unlocked iPhones accidentally start affecting cell basestations (perhaps only one manufacturer's basestation), Apple will be faced with customer support calls for firmware that didn't pass the standard certification processes, the network operator will be faced with customer support calls, and immense finger-pointing will ensue (between the network operator, Apple, customers, and basestation manufacturers). Reputations will be tarnished and Apple's customer support costs will jump, even though the Apple QA'd firmware does not have the same defects as the hacked firmware. Revenue and expenses will be impacted.
Stepping back and looking at the economic motivations, Apple often makes decisions based on the desire to minimize costs â" customer support costs.
(this also ignores lost App Store revenue, carrier kickbacks, etc. from jailbroken and unlocked iPhones)
I'm all for the freedom of unlocked and jailbroken iPhones, but accusing Apple of trying to maintain a closed system just because they're jerks is ignorant of the processes in place to ensure network stability and a positive user experience by all cell phone users.
(No, I'm not accusing the iPhoneDevTeam of maliciously attempting to release poorly-hacked firmware, but given the earlier IMEI fiasco, it IS possible. I expect we all believe in QA processes, and I doubt the DevTeam has access to a Spirent Its way outside their budget. )
DENNIS (Tom Yager):
Ah, now we see the weakness inherent in the system.
ARTHUR (Microsoft):
Shut up!
DENNIS:
Oh! Come and see the weakness inherent in the system! Help! Help! I'm being repressed!
ARTHUR:
Bloody peasant!
DENNIS:
Oh, what a give-away. Did you hear that? Did you hear that, eh? That's what I'm on about. Did you see him repressing me? You saw it, didn't you?
I suspect the transponders for the Nike+ shoes and Nano were designed for Nike/Apple by Dynastream.
They've had a historical relationship with Nike, 2.4GHz PANs and RF protocol as evidenced by the press releases found here.
Wireless Sports Area Network (SPAN? WSPAN?) anyone? Nike, Suunto and Garmin all appear to have worked with Dynastream, so I wonder about future interoperability. . .
In the days and weeks preceeding the original iBook announcement, when rumors were running rampant about it specifications (including the ability to charge it using a hand crank!), much speculation surrounded what NAME it would go by.
At the time there was an iMac, a PowerMac, and a PowerBook. I never understood how hard it would be to fill in the fourth quadrant with the completely-evident iBook.
It looks like the MacMini introduced what looks like the new naming scheme, and in time *most* products will transition.
iPod (not a Mac) iMac (name is not likely to change, given that it didn't change today) Mac mini, MacBook Pro, and ???
So I think the discussion shouldn't revolve around the poor choice of naming for the new PowerBook, but what the new iBook and new PowerMac's will be called?
MacBook and MacLarge? MacBook Solo and MacTower?, MacBook Express and Mac Pro?
I did this to watch the Calgary Flames play their way to the Stanley Cup final using iChat and a pair of iSights.
I had recently move to San Diego and didn't have a television. My family back in Calgary put a laptop on a chair and aimed an iSight at the TV and I watched several games this way sitting on my patio - WiFi on both ends.
Here's my record of the event
This is almost definitely where the OS X Leopard interface is going and for the most part it's a welcome change.
Almost definitely.
Yes, I'm almost definitely sure that the reviewer knows where the Leopard interface is going. It might be a welcome change, but saying the Aperture is indicative of Leopard's UI is like stating that Panther and Tiger should have looked just like the versions of FCP that directly preceeded them.
FCP, Aperture, DVD Studio Pro, Motion, etc. are all built with a unique, private "Pro Apps" API and are designed to look different from the standard OS X apps (and their publically accessible Standard Cocoa and Carbon APIs).
Some elements of the Pro Apps API might migrate to the standard API for Leopard (similar to how the floating transparent palettes introducted with Motion migrated to iPhoto), but the "Professional" look of Aperture is not a precursor to Leopard no matter how "almost definitely" sure the reviewer may be.
Very correct. My mistake. I was visualizing on the wrong side of the continental divide. The principle I was getting at still remains despite my misinformation.
I did need the geography lesson.
Thanks
(no sarcasm intended)
I'm amazed you've been modded so positively. The parent was not making a cut on New Orleans - I believe the rhetorical device being employed is known by some as satire. New Orleans was a tragedy, and yes, Californians can do more. But problems concerning water span governmental boundaries - municipally, federally, internationally.
California should do more to dig itself out of its own mess, but that doesn't mean that waterless urinals won't help - and that's the point of the discussion, is it not?
I was going to mod the grandparent flamebait, but instead I'll save my modpoints for elsewhere and comment on why I *would* have modded it flamebait.
The entire statement was laden with baiting words. "That's what you get for living in the desert." Ok, yes, it should be evident to ANYONE that desert's equal no water. However, the presence of ample freshwater in *most* of the US does not mean that everyone should burn fresh clean water like its infinitely available.
That's what you get for living in the desert. You countered the parent post, who said that freshwater is plentiful in most of the US by saying that in a couple places in California, there is need for conservation. I hate to burst your bubble, but California is not "most" of the US. Come to the Mississippi river area and tell me there's not enough water.
The problem in California is blatantly ignored by most Californians. Developments continue in most parts of (at least) Southern California despite the fact that the the water supply can't handle the growth. "Everyone" wants to live there but there aren't the resources to support everyone. The problem in California is quite significant to the rest of the country, despite the Mississippi being full of water. California's economy, if it were an independent nation, would be the fifth largest in the world. Its responsible for 14% of the US GDP - $1.5 trillion dollars in 2004. 12% of Americans live in California (more people than in all of Canada) - and that doesn't include illegal aliens.
The Grandparent's basic statement that a clean freshwater supply is, "Not a problem here" is selfish and ignorant. Yes, if fewer people were dumb enough to live in California, then they wouldn't have (as bad of) a problem. But with a powerful economy, a reasonably high average income, and many jobs, there's a reason people are dry in the desert.
Despite the opinions of many Californians I've met, the universe does not revolve solely around them, or their state. Water shortages are rarely an issue in the U.S., outside of California (and I suspect probably mostly only Southern California) and the Southwestern states -- the only exception being the odd seasonal shortage during a bad summer drought in other places, or if the water supply is contaminated for some reason.
No, the universe doesn't revolve solely around Californians, but I've generally found that most Americans think that they already live on the greenest side of the fence. Outside of California water shortages may not be a big problem, but large parts of the US are not as densely populated either. Montana doesn't seem to have water problems. Yay, you win! Oh, wait, that doesn't solve California's problem.
As for water contamination in the US - its a bigger problem that you're aware of. Just because there's water coming out of the taps in your house doesn't mean that its not contaminated.
The Colorado river is tainted with heavy metals after passing through mining tailings in southern Utah (Moab). California drinks the Colorado so dry that the Gulf of California receives very little "fresh" water and is becoming increasingly salinated. Its becoming so salty that the fish population is disappearing. This is naturally having a negative impact on the local population.
The INL, formerly known as the INEEL developed the first nuclear reactors. Nearby Arco Idaho is the first town in the world to be powered by nuclear power. However, how do you run Nuclear reactors in the middle of old lava beds (equivalent to desert)? How do you provide cooling? Oh, there's a large aquifer - the Snake River aquifer? Yes, lets use that. Funny, where does the Snake River end? So yes, there's lots of water in the Mississippi, but is it clean? Is it safe?
Ubuntu X.Y corresponds to the release year (200X) and the release month(Y).
In this case it was October 2005 -> (10/05)
The next release will be Ubuntu 6.4 (April 2006))
Office 2004 for OS X has an entire folder full of resources that are shared between the various.apps (Excel, Word, PowerPoint and Entourage). If you move one of the.app's away from this folder of resources, the app complains and asks to be moved back where it was. In some cases, missing files will be regenerated when your run the.app again. That is, running the app for the first time completes a "small" install process.
This is a compromise between completely self contained.apps (that could be executed from anywhere) and.app interdependency, but it still allows you to move the entire Office 2004 suite wherever you want, and to delete everything associated with the suite by dragging the parent folder to the trash (all except fonts I believe).
Given that Calgary was chosen as the destination before the local University was notified (before they even knew they were even being considered as the destination), the University of Calgary's entry has been developed from scratch in around 9 months. Good luck team, you've worked madly and you deserve to do well.
Despite my bias for my alma mater, I think they've done an amazing job despite having no previous experience.
I was using it in a 130 mA to 1 A situation, but for low current situations (100 uA to ~30 mA) the burst mode operation can still provide 70 to 80% efficiency.
I'll have to look closer at the TEA1211 in the future. I wasn't overly concerned with the LTC3441's low current performance, mostly I had to try and work around its high current limitations.
Slashdot Mirror
Might not be your specific issue but if you've installed any of the jailbreak tools, your hosts file might have been modified so that the update won't validate against Apple's server.
Fixing your hosts file is left as an exercise for the reader – obviously if you play the jailbreak game you're savvy enough to repair the hosts file.
Forget the iPhone OS. I'm pissed that I can't do linux kernel development using Flash.
Since when does open-source development restrict my choice in tools, anyway?
RAM is cheap, and there's no lack of space inside the ipad for an extra chip.
The iPad's A4 processor has the RAM inside the A4 package using package-on-package technology. Perhaps the RAM inside the A4 could have been a higher density, but space inside the iPad is not relevant.
Integrating the RAM minimizes the pinout of the A4 and may have allowed them to avoid a difficult-to-breakout BGA pitch. (Changing from a 0.5mm to 0.4mm pitch allows more pins but complicates PCB routing and PCB expense.) I can't tell from this shot of the A4 what pitch is used, but the pin count is pretty high. Note: You need the blank areas in order to breakout traces and place vias.
Patches from clients for cell firmware end up going into a separate tree for that specific client and are not typically propagated back upstream to the baseline, so every phone manufacturer who develops a phone using any given chipset ends up having to find and fix the same set of hundreds of baseband bugs over and over. If that's true, I'm amazed that the cell manufacturers put up with it. That certainly explains why cell phones have so many hundreds (or thousands) of baseband crasher bugs, and it also probably explains why Google is having to relearn all the stuff that Apple just learned a few months ago, and probably Nokia learned a few months before that, and so on.
This is precisely why Apple will never make a CDMA iPhone for Verizon using a Qualcomm chipset. The baseband firmware workload for maintaining fixes for two different chipset vendor's code bases is not justifiable. Apple chose Infineon for their chipset, and I expect their product roadmaps to remain closely aligned regardless of Qualcomm's offerings.
Apple makes a very limited number of hardware SKUs that can be sold worldwide. Don't expect them to offer variants for specific markets.
That, and Apple HATES Verizon.
You have the code to the app-side of the OpenMoko - the Linux side. Do you have the code to the radio stack? The code to access and manipulate the calibration parameters, change RF chipset behaviour, manipulate handoff. Can you add new custom AT commands to the stack? Or are you just interfacing with the radio firmware via AT?
That is, is the Calypso Moko FW open source?
http://people.openmoko.org/joerg/calypso_moko_FW/all_version__CHANGELOG.txt
Jailbreaking is the gateway to the real danger of modifying the baseband radio binaries (not apps-processor). In and of itself, I agree that just jailbreaking won't affect the cellular network.
Post-jailbreak modification of the baseband firmware is what is happening when you unlock an iPhone. This modification invalidates the FCC, CE, GCF and PTCRB certifications of the phone. It has the potential to increase support costs and negatively impact network operation.
Its not analogous to using an IP Sockets API to crash your router. Its like modifying the firmware of your router's PHY and then calling customer support because your network is down.
Please understand that the source code to the GSM modem that you don't have access to, is precisely the portion of the iPhone firmware that is being manipulated by the carrier unlock procedure (but afaik not the jailbreak procedure). Jailbreaking, however, is the gateway to the unlock process â" hence the concern about prohibiting Jailbreak.
Every version of modem/phone baseband firmware must pass significant interoperability and carrier approval test suites before it can be sold or distributed. Why? Because cell networks are heterogeneous amalgamations of multiple vendors handsets, basestation equipment, and firmware versions for each. Think its annoying when a cheap WiFi router doesn't interop well with your existing devices? Is it WiFi certified? Now imagine being a network operator when potentially rogue firmware versions randomly take down portions of your billion dollar network...
Should the unlock process accidentally or otherwise modify the modem/phone calibration or call-handling procedures, the network can be impacted. The cell network stability is dependent on all handsets following the same rules â" one misbehaving handset can affect the rest of the cell... Imagine having your call dropped because someone running an unlocked iPhone did a handoff to your cell...
e.g. One early iPhone unlock procedure caused every unlocked device to have the same IMEI â" an identifer which should be unique in the world. This can cause network (and billing) issues analogous to multiple Ethernet devices with the same MAC address.
Thus Apple's concern about unlocking (which required jailbreaking) may be motivated by customer support concerns.
Should poorly unlocked iPhones accidentally start affecting cell basestations (perhaps only one manufacturer's basestation), Apple will be faced with customer support calls for firmware that didn't pass the standard certification processes, the network operator will be faced with customer support calls, and immense finger-pointing will ensue (between the network operator, Apple, customers, and basestation manufacturers). Reputations will be tarnished and Apple's customer support costs will jump, even though the Apple QA'd firmware does not have the same defects as the hacked firmware. Revenue and expenses will be impacted.
Stepping back and looking at the economic motivations, Apple often makes decisions based on the desire to minimize costs â" customer support costs.
(this also ignores lost App Store revenue, carrier kickbacks, etc. from jailbroken and unlocked iPhones)
I'm all for the freedom of unlocked and jailbroken iPhones, but accusing Apple of trying to maintain a closed system just because they're jerks is ignorant of the processes in place to ensure network stability and a positive user experience by all cell phone users.
(No, I'm not accusing the iPhoneDevTeam of maliciously attempting to release poorly-hacked firmware, but given the earlier IMEI fiasco, it IS possible. I expect we all believe in QA processes, and I doubt the DevTeam has access to a Spirent Its way outside their budget. )
CMD + down arrow (apple + down arrow) will open the highlighted file or app
uh, OUR fault...
DENNIS (Tom Yager):
Ah, now we see the weakness inherent in the system.
ARTHUR (Microsoft):
Shut up!
DENNIS:
Oh! Come and see the weakness inherent in the system! Help! Help! I'm being repressed!
ARTHUR:
Bloody peasant!
DENNIS:
Oh, what a give-away. Did you hear that? Did you hear that, eh? That's what I'm on about. Did you see him repressing me? You saw it, didn't you?
Actually it looks like the ANT platform would likely be the basis of this implementation.
I suspect the transponders for the Nike+ shoes and Nano were designed for Nike/Apple by Dynastream.
They've had a historical relationship with Nike, 2.4GHz PANs and RF protocol as evidenced by the press releases found here.
Wireless Sports Area Network (SPAN? WSPAN?) anyone? Nike, Suunto and Garmin all appear to have worked with Dynastream, so I wonder about future interoperability. . .
In the days and weeks preceeding the original iBook announcement, when rumors were running rampant about it specifications (including the ability to charge it using a hand crank!), much speculation surrounded what NAME it would go by.
At the time there was an iMac, a PowerMac, and a PowerBook. I never understood how hard it would be to fill in the fourth quadrant with the completely-evident iBook.
It looks like the MacMini introduced what looks like the new naming scheme, and in time *most* products will transition.
iPod (not a Mac)
iMac (name is not likely to change, given that it didn't change today)
Mac mini, MacBook Pro, and ???
So I think the discussion shouldn't revolve around the poor choice of naming for the new PowerBook, but what the new iBook and new PowerMac's will be called?
MacBook and MacLarge? MacBook Solo and MacTower?, MacBook Express and Mac Pro?
Its a limitation of the Qualcomm chipset and software running on the phone. They may be able to scale the same hardware up to 7.2 Mbps in the future.
I did this to watch the Calgary Flames play their way to the Stanley Cup final using iChat and a pair of iSights. I had recently move to San Diego and didn't have a television. My family back in Calgary put a laptop on a chair and aimed an iSight at the TV and I watched several games this way sitting on my patio - WiFi on both ends. Here's my record of the event
Almost definitely.
Yes, I'm almost definitely sure that the reviewer knows where the Leopard interface is going. It might be a welcome change, but saying the Aperture is indicative of Leopard's UI is like stating that Panther and Tiger should have looked just like the versions of FCP that directly preceeded them.
FCP, Aperture, DVD Studio Pro, Motion, etc. are all built with a unique, private "Pro Apps" API and are designed to look different from the standard OS X apps (and their publically accessible Standard Cocoa and Carbon APIs).
Some elements of the Pro Apps API might migrate to the standard API for Leopard (similar to how the floating transparent palettes introducted with Motion migrated to iPhoto), but the "Professional" look of Aperture is not a precursor to Leopard no matter how "almost definitely" sure the reviewer may be.
Very correct. My mistake. I was visualizing on the wrong side of the continental divide. The principle I was getting at still remains despite my misinformation. I did need the geography lesson. Thanks (no sarcasm intended)
I'm amazed you've been modded so positively. The parent was not making a cut on New Orleans - I believe the rhetorical device being employed is known by some as satire. New Orleans was a tragedy, and yes, Californians can do more. But problems concerning water span governmental boundaries - municipally, federally, internationally.
California should do more to dig itself out of its own mess, but that doesn't mean that waterless urinals won't help - and that's the point of the discussion, is it not?
The entire statement was laden with baiting words. "That's what you get for living in the desert." Ok, yes, it should be evident to ANYONE that desert's equal no water. However, the presence of ample freshwater in *most* of the US does not mean that everyone should burn fresh clean water like its infinitely available.
The problem in California is blatantly ignored by most Californians. Developments continue in most parts of (at least) Southern California despite the fact that the the water supply can't handle the growth. "Everyone" wants to live there but there aren't the resources to support everyone. The problem in California is quite significant to the rest of the country, despite the Mississippi being full of water. California's economy, if it were an independent nation, would be the fifth largest in the world. Its responsible for 14% of the US GDP - $1.5 trillion dollars in 2004. 12% of Americans live in California (more people than in all of Canada) - and that doesn't include illegal aliens.
The Grandparent's basic statement that a clean freshwater supply is, "Not a problem here" is selfish and ignorant. Yes, if fewer people were dumb enough to live in California, then they wouldn't have (as bad of) a problem. But with a powerful economy, a reasonably high average income, and many jobs, there's a reason people are dry in the desert.
No, the universe doesn't revolve solely around Californians, but I've generally found that most Americans think that they already live on the greenest side of the fence. Outside of California water shortages may not be a big problem, but large parts of the US are not as densely populated either. Montana doesn't seem to have water problems. Yay, you win! Oh, wait, that doesn't solve California's problem.
As for water contamination in the US - its a bigger problem that you're aware of. Just because there's water coming out of the taps in your house doesn't mean that its not contaminated.
The Colorado river is tainted with heavy metals after passing through mining tailings in southern Utah (Moab). California drinks the Colorado so dry that the Gulf of California receives very little "fresh" water and is becoming increasingly salinated. Its becoming so salty that the fish population is disappearing. This is naturally having a negative impact on the local population.
The INL, formerly known as the INEEL developed the first nuclear reactors. Nearby Arco Idaho is the first town in the world to be powered by nuclear power. However, how do you run Nuclear reactors in the middle of old lava beds (equivalent to desert)? How do you provide cooling? Oh, there's a large aquifer - the Snake River aquifer? Yes, lets use that. Funny, where does the Snake River end? So yes, there's lots of water in the Mississippi, but is it clean? Is it safe?
Ironically there is now a division of
Actually its Ubuntu 5.10, not 5.1
Ubuntu X.Y corresponds to the release year (200X) and the release month(Y).
In this case it was October 2005 -> (10/05)
The next release will be Ubuntu 6.4 (April 2006))
Office 2004 for OS X has an entire folder full of resources that are shared between the various .apps (Excel, Word, PowerPoint and Entourage). If you move one of the .app's away from this folder of resources, the app complains and asks to be moved back where it was. In some cases, missing files will be regenerated when your run the .app again. That is, running the app for the first time completes a "small" install process.
.apps (that could be executed from anywhere) and .app interdependency, but it still allows you to move the entire Office 2004 suite wherever you want, and to delete everything associated with the suite by dragging the parent folder to the trash (all except fonts I believe).
This is a compromise between completely self contained
Its not turned on by default, but you can if you want. http://www.macosxhints.com/article.php?story=20050 430233117572&query=nfs+spotlight
Once the share is indexed, I think the trick is doing a Find (CMD+F) in the Finder, not just using the Spotlight button in the menubar
They're going North from Austin to Winnepeg Manitoba, then West to Calgary.
Given that Calgary was chosen as the destination before the local University was notified (before they even knew they were even being considered as the destination), the University of Calgary's entry has been developed from scratch in around 9 months. Good luck team, you've worked madly and you deserve to do well.
Despite my bias for my alma mater, I think they've done an amazing job despite having no previous experience.
My Gen 1 10 GB suffered this fate (premature hard drive failure) from installing OS X onto it too many times... (developer builds and backups)
If I ever get another iPod, it will be for music, and only rarely accessed (but useful) files.
I was using it in a 130 mA to 1 A situation, but for low current situations (100 uA to ~30 mA) the burst mode operation can still provide 70 to 80% efficiency.
I'll have to look closer at the TEA1211 in the future. I wasn't overly concerned with the LTC3441's low current performance, mostly I had to try and work around its high current limitations.