And going....

root@Omega-FA93:~# uptime
 07:33:38 up 727 days, 13:49,  load average: 0.00, 0.00, 0.00
root@Omega-FA93:~#

Still going strong:

root@Omega-FA93:~# uptime
 12:23:21 up 576 days, 18:38,  load average: 0.00, 0.00, 0.00

@crispyoz
Your file will be there, but is being replaced and removed at startup by the code in: files/etc/uci-defaults/14_banner.

@chris-Ó-Luanaigh asked:

A question - why is the global version $19 more expensive?

I'd expect that the chip in the global model that supports all the additional bands is more expensive.

@Cameron-Spitzer
The short answer is: Yes
However, there is more to it than just supplying 3v3 power.

Experience has shown us that the Omega2 is very sensitive to power fluctuations, requires a regulator at least, but a couple of caps are highly recommended together with the use of short, heavy gauge wire due to the current drawn when hitting wifi initialisation at boot.

Your first port of call should be the official documentation here: Powering the Omega with No Dock

Next, doing a quick search of these forums will yield a fair amount of discussion from the enthusiasts here on their own experiences and suggestions on making it a smoother experience for you.
Here is just one thread of many: [Resolved] Omega 2+, Powered without Dock, Shuts off after 18s

Having said all that, do not underestimate the power of having a spare expansion dock available when things go wrong. It is by far the simplest way to power your O2 and get direct serial access to the console for troubleshooting.

Welcome and Good luck !!

Looks like a good move: MIPS Goes Open Source

Will that MediaTek wifi driver that was the bane of our development efforts before the warp core release now enter the public domain, I wonder? ;->

@brolly759 said

I tried the above and it worked, if you have the time, try it to and let me know how it goes!

Well, perhaps you can backup your uboot, but it seems that you can't write it back this way:

# mtd write u-boot.bin mtd0
Could not open mtd device: mtd0
Can't open device for writing!

[edit]
You can, but it's not as trivial, so it requires some hoop jumping to get it done.

# mtd write u-boot-env.bin u-boot-env
Unlocking u-boot-env ...

Writing from u-boot-env.bin to u-boot-env ...
# mtd write u-boot.bin u-boot
Unlocking u-boot ...

Writing from u-boot.bin to u-boot ...

[/edit]

@jokre said:

Another scenario is if I boot the Omega2 up with the battery attached and using USB power and then disconnect the USB power, the Omega2 continues to operate. But... if I re-attach USB power again, the Omega2 dies (and the orange LED goes off and the AP stops to work). Power LED is still on and if I have anything presented on the attached OLED expansion, it still shows even if the Omega2 is not working so the hardware stack has power coming into it.

Fairly common problem I've seen. What I do to overcome it is use a really good power supply (>=2A) and a short USB cable with thick gauge cable.
Typically I see it when powering the device via USB with battery attached and then there's a power failure. The device continues to run on battery, but as soon as the power returns, it dies. Solution = short, thick gauge USB power cable.

@Douglas-Kryder said in [resolved]GPS device disappeared on Omega2 LTE:

@György-Farkas said in [resolved]GPS device disappeared on Omega2 LTE:

The USB Host port of this board is not accessible (it's not exposed) because it's currently used by the LTE module.
So flash the firmware via USB is not possible at all.

thanks. so i read the guide and there is no mention of firmware recovery for this LTE model. is that the case or is there some undocumented path like maybe just creating a serial connection from the interrupted boot sequence menu to a computer. or, maybe store a copy of the firmware in a special folder on the emmc . or did they give this LTE no recovery path? i've been thinking about getting this LTE to replace a particle electron but having had to do the recovery sequence on a few original omega2+ because of bad firmware, i'd won't buy one if recovery isn't possible.
thanks for your insights, very helpful info.

I thought we put our concerns regarding this USB recovery aspect to rest just after the project launched. Well, I seem to have been convinced enough so that I decided to back the project, but I can't seem to find that now...

@Edward-Cheadle asked:

@Janus-Sanders Do you know if this Docker Image;
https://hub.docker.com/r/onion/omega2-source/
will work for my Omega2 Pro;
https://onion.io/announcing-the-new-omega2-pro/

Yes, it will, but that docker image is a bit long in the tooth now, so there are a few things you'll have to do, namely:

• fix the ubuntu package install environment
• install the time package
• update the source
• switch to the openwrt branch
• create a symlink to the O2 .config if building firmware b222 and later

Something along the lines of (after creating your container):

# fix the ubuntu package install environment
# install the time package
apt-get update
apt-get -f install
apt-get install time

# update the source
git pull

# switch to the openwrt branch
git checkout openwrt-18.06

# clean out any old LEDE related feeds
./scripts/feeds clean
./scripts/feeds update -a
./scripts/feeds install -a

# create a symlink to the O2 .config (only relevant when building firmware b222 onwards)
ln -s .config.O2 .config

# build
make

I took this from my container's history, so I hope I haven't missed anything or made any errors.

Also make sure you allocate enough space for the container. I suggest 30GB at a minimum, but more if you have it.

If you'd like to build a particular firmware revision, it's useful to add a few git tags where necessary. If you are interested here are the last few of mine:

git tag v0.3.2-b222 96400e1
git tag v0.3.2-b221 221604e
git tag v0.3.2-b220 0984915
git tag v0.3.2-b219 7cdd57e
git tag v0.3.2-b218 adfead5
git tag v0.3.2-b217 d624ea1
git tag v0.3.1-b216 c22c17c

Then you can run a specific build with a:

git checkout v0.3.1-b216
make

And going....

root@Omega-FA93:~# uptime
 07:33:38 up 727 days, 13:49,  load average: 0.00, 0.00, 0.00
root@Omega-FA93:~#

@jokre said:

Another scenario is if I boot the Omega2 up with the battery attached and using USB power and then disconnect the USB power, the Omega2 continues to operate. But... if I re-attach USB power again, the Omega2 dies (and the orange LED goes off and the AP stops to work). Power LED is still on and if I have anything presented on the attached OLED expansion, it still shows even if the Omega2 is not working so the hardware stack has power coming into it.

Fairly common problem I've seen. What I do to overcome it is use a really good power supply (>=2A) and a short USB cable with thick gauge cable.
Typically I see it when powering the device via USB with battery attached and then there's a power failure. The device continues to run on battery, but as soon as the power returns, it dies. Solution = short, thick gauge USB power cable.

@Lazar-Demin

Thanks for the update and indeed, I did receive a "Your Crowd Supply order has shipped!" notification for my LTE's on 1 November.
Apologies, I meant to post a follow up about that, but have been somewhat distracted.

@TheMonkey-King said in Omega2 LTE just launched!:

I haven't heard anything from Onion or Crowd Supply. What is going on with shipments, please? I should have my order in hand or at least an explanation of the delay. I tried Crowd Supply but it's a black hole over there.

Please advise.

Thank you.

Seems some have made it out to backers:

• [resolved]GPS device disappeared on Omega2 LTE
• Omega2 LTE Wireless not working
• Omega2S+ LTE - GNSS/GPS positionning : no init file

So I'm also wondering where in the world my O2 LTE's might be...
@Lazar-Demin - Are you able to provide an update on the current status for us?

@Douglas-Kryder said in [resolved]GPS device disappeared on Omega2 LTE:

@György-Farkas said in [resolved]GPS device disappeared on Omega2 LTE:

The USB Host port of this board is not accessible (it's not exposed) because it's currently used by the LTE module.
So flash the firmware via USB is not possible at all.

thanks. so i read the guide and there is no mention of firmware recovery for this LTE model. is that the case or is there some undocumented path like maybe just creating a serial connection from the interrupted boot sequence menu to a computer. or, maybe store a copy of the firmware in a special folder on the emmc . or did they give this LTE no recovery path? i've been thinking about getting this LTE to replace a particle electron but having had to do the recovery sequence on a few original omega2+ because of bad firmware, i'd won't buy one if recovery isn't possible.
thanks for your insights, very helpful info.

I thought we put our concerns regarding this USB recovery aspect to rest just after the project launched. Well, I seem to have been convinced enough so that I decided to back the project, but I can't seem to find that now...

@Suman-kumar-Jha
This is a bit beyond my skills as I don't python much and don't AWS or MQTT at all, so perhaps someone else can get you to the answer much quicker than I can.

However, looking at the error you posted, it looks like you are getting a timeout while trying to publish.

Perhaps you need to increase the timeout duration?
A bit of google searching reveals that there are a couple of timeout settings that can be tweaked (.configureConnectDisconnectTimeout() and .configureMQTTOperationTimeout()), perhaps you need to look into those?

There's also this open issue on the aws iot python sdk (which I assume you are using): Recommendation on handling publishTimeoutException #211

@Suman-kumar-Jha
Please check if you have both of the ca-certificates and ca-bundle packages installed as explained here: FAQ: I get Error 48 or Error 77 when using curl

[edit]
Or perhaps review if the solution documented in this thread is helpful: Connected and immediately disconnected from AWS IoT ?

Still going strong:

root@Omega-FA93:~# uptime
 12:23:21 up 576 days, 18:38,  load average: 0.00, 0.00, 0.00

@György-Farkas
Is there supposed to be some level of compression built in there? I don't think so, but I haven't been following along to closely recently.

fwiw, I understood @Douglas-Kryder 's question to be more along the lines of: Given a 500K persistent storage facility, how much of my data could I store there compressed as a backup.
Apologies if I misunderstood.

Anyway, that potential misunderstanding aside, looking at your figures regarding the persistent storage, I'm a bit confused with the values that you've posted.
eg. Here:

root@Omega-5BE1:~# rm /mnt/mtdblock7/*
root@Omega-5BE1:~# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/mtdblock7          512.0K    196.0K    316.0K  38% /mnt/mtdblock7 # empty

The size: 512.0K - That's ok
The used: 196.0K - That's not empty

So something looks off with that partition.

@Douglas-Kryder
The answer you will find universally for this questions is: "It depends."
Specifically, it depends on the "compressibility" of the source you are compressing.
Some things compress well, eg. text
Some things don't compress at all (or so little as to be meaningless): eg. compressed files

Once you have a reasonably good idea about what you intend to store in the partition in a compressed format, you will have to do some trial and error to determine how well it compresses and whether or not it will fit.

I don't think there's any other way to determine an answer to your question, but if there is, I'd be interested to know as well.