MetaChat can now run in the background BUT !
- If the device goes to sleep iOS cuts the connection – you will be logged out
- background mode is available for 3 seconds to 3 minutes, only the OS decide how much time you get – if the time is up – you will be logged out
- after the “15 seconds” message open the app again – or you …. well you know
This background mode is all in the hands of the iOS but at least gives you time to quick check something or send a message, mail …
For this to work you must allow MetaChat to send you notifications.
In “settings” you can enable/disable a badge counter showing for messages received during background mode.
Be aware that even in the background MetaChat needs a stable connection and some battery.
I got some messages about code not being stable, crashes and other non working stuff.
Please check the official forum and see how many troubles people have with the Linden Viewer. MetaChat cannot solve SLs problems.
If the server is unstable, your connection has packet-drop or hick-ups, changing mobile cell or or or this is not the apps fault.
This version has run on my iPhone X for over 60 hours (on a charger of course) without a single problem or crash.
The apps code is very stable and passes lots of high-end tests before updates are released.
Device heats up
Apps like MetaChat that uses some battery are known for that behaviour because iDevices are passiv cooled (no fans) and thats normal. iDevices cannot break about this because they simply shut down before overheating.
Thats it for now. More updates for 2019 are coming.
The first update in 2019 will have some minor changes to the engine and user interface.
Nothing really impressive but …
Of course Apple won´t let me run the app in background forever but there is a chance to have it online for a time between 3 seconds and 3 minutes. This depends on device usage, battery … so it´s not an estimated time only a timeframe that vary each time.
However this could enable you to quick check a mail or send a message or check your smarthome devices or whatever quick you need.
There is no fixed date when the update will be release because i need some time testing the timeframe. It won´t be in the update if i always get a timeframe < 10 seconds, that´ll be useless.
Anyway. Hope you had a better start into 2019 than me and lets rock.
Because of some reports about new versions are worse than older i rolled back the network code.
- group chat replace /me with name
somehow missed that till now
- cleared problem in IMs send from attached objects to itself
they are shown in open-chat
- fixed problem server not sending “stop typing” message
sometimes the … kept animating forever
- IMs from objects show Object name instead of ???
See the objects name to locate/block it
- rolled back network code for more stability
set connection to sleep after sending some packets and wait for a server response, looks the SL servers are slower than mobile network cards
- Badge counter for new messages moved from timers to events
this should increase the overall speed and remove the pressure on CPUs
- Friend management (adding removing invite) – updated
more like the original client now
There are some reports about random crashes since the latest update and devices heating up.
About the crashes, i will rollback little changes to the network code. It looks iPhones do not like fast network transactions ?
Apple says: Since iOS 11 it is normal behaviour that random devices heat up using random apps. If the temperatures are too high the device will shutdown to not take any damage.
Temperatures around 40° Celsius are “normal” because the CPU and network parts are passively cooled and turn hot on “use”.
Please understand that the heat problem is iOS wise and not the apps fault. Developers cannot control why or when this happens.
Now, when is roll out? Checking the “bad” code that tends to crash on a few devices without a crash log send to me is – check line by line and compare to old code.
Hopefully this weekend the update is ready for approval because during christmas season my time is very limited.
If you encounter frequent crashes please keep in mind that running an SL client far below the minimum system requirements cannot work better than the original client (and after more than 10 years on SL the LL client never worked flawless)
MetaChat has to process a massive amount of data and SL network code is very old and was never officially ported to iOS.
Please use wireless LAN (3G, 4G, LTE …. mobile connections have massive packet loss and are not designed for lossless connection; the app might work but sure not perfect)
Allow the app to fully load on start
Do not switch rapidly between the different tabs. Open a tab starts lots of network processing that will completing even if you select another tab.
You can select the “mobile mode” to stop loading pictures and bigger files when your network is slow.
Please check the SL blog for problems connecting to the network or troubleshooting your connection. (Login on an empty sim …)
Check the current grid status and do not use streaming apps when using MetaChat.
Before releasing an update the app runs 12 hours on 2 devices and only if it pass the update will be released.
No app is bug free and working on the code never stopped.
To help in tracing bugs please allow “send crash reports to apple” this is the only way to see where and when the app crashes.
For the latest update i only received three! crash reports where 2 of come from users force closed the app (not really a bug and not recommended by apple).
Even with all testing some bugs might slip through.
If you cannot start MetaChat because it´s stuck at converting chat-history please read this quick-solution guide:
- unread MapChat count shown with a badge number
- accept animation invites from attached huds (huggers, getclose hud…)
If someone invites you to a hug you receive the “accept/decline” message
(Because of iOS limitations not all related messages can be displayed)
- chats now saved on the fly in SQL Database
if the app crashes or the connection breaks up, all unread chats will be loaded next start (IM; Group; Map)
- Manage Chat History (IM): are displayed grouped by names
- Manage Chat History (IM): can be send as plain text in email
- old chat-logs are converted at login
- Map: fixed a problem with display of NearMe Avatars
- fixed a problem with not showing BadgeNumbers for messages after multiple logins
- Updated the whole code to iOS 12 for more speed stability, reworking all used libraries and frameworks
Minimum required iOS = iOS 11
That´s not the end – look out for more updates ….