Linux-based 4G phones with Google Assistant sold for $7 in Indonesia
tuxphones.com
tuxphones.com
I wish Firefox OS hadn't thrown in the towel so early. These devices are selling millions of units every month.
However, the effort required to enable a non-touch UI would have been a small fraction of the overall FirefoxOS effort. Something Mozilla could have responded to, if the team was intact.
Web is good enough for 90% of apps, and a bare metal SDK would be needed for games.
Even WebGL 2.0 alongside WebAssembly will be good enough for Flash like games (Google Chrome team will give a talk about WebGPU at IO).
Many of the supposed iOS "innovations" were already there.
That ecosystem, interface, and community no longer exist.
-
Also your comment doesn’t really make sense.
Something that currently exists can still have been ahead of its time. My comment isn’t an indication it doesn’t exist.
When Firefox OS was around, they were still pretty niche.
"KaiOS apps are based on web technologies–HTML, CSS, and JavaScript–and are run by Gecko runtime."
Just consider that Mozilla is pretty much working full-pelt on Gecko and merely keeping up with Google. They (as well as Google) are far away from implementing all currently specified web-standards, of which more get specified all the time.
So, in order to get Servo to the level of current browser engines, they would have to have an even higher developmemt velocity, while not really being able to stop developing Gecko in the meantime either.
Maybe if the majority of components someday are shared between Gecko and Servo, they might do the final step and switch out the core completely, but even that is still far away.
Servo is specifically a research project. To explore what could be done, if one were to do things right. That they were able to isolate and share components, that even came as a surprise to Mozilla.
Swapping out the jet engine of Firefox in flight (Gecko) was likely to be a very bumpy, messy road, thus Mozilla has chosen to break the problem down into manageable chunks by having a parallel team build Servo and push the bleeding edge of performance & features, while having another team break the new code (Servo) and the old code (Gecko) apart into the separate , interchangeable pieces, then clean up standards compliance in the new Servo module and prep it to be replaced.
Essentially, its the Cathedral vs the Bazaar all over again. Microsoft Edge was a ground up rewrite of most of the browser (the Cathedral model of software dev) along with Android (built behind closed doors at Google, then code dumped right before a new major release). Mozilla didn't like how this model could easily backfire, choosing a more metered approach by developing smaller, swappable components in the open.
Apple?
Also remember that you probably don't want to entirely cut Google out of your life, as for example Linux have Google salaried developers. But that's, I imagine, not what you meant.
[0] https://forum.pine64.org/showthread.php?tid=7339 - no canonical site yet
The reason i would buy a linux phone would be to avoid having a MITM burned onto the rom of my phone. The device presented in this article doesnt provide that nessecity.
I think the law of averages applies, not knowing how much google and others payout to burn kruft into peoples product, im going to guess that the increased global saturation level of google ASSistant is worth it for google and a good revenue for the OEM. ill bet the price is subsidied to 7$, i would pay 70$ for this phone, if it had no google ass in it.
> “The full Safari engine is inside of iPhone. And so, you can write amazing Web 2.0 and Ajax apps that look exactly and behave exactly like apps on the iPhone. And these apps can integrate perfectly with iPhone services. And guess what? There’s no SDK that you need! You’ve got everything you need if you know how to write apps using the most modern web standards to write amazing apps for the iPhone today. So developers, we think we’ve got a very sweet story for you. You can begin building your iPhone apps today.” - Steve Jobs/iPhone announcement Jan 2007 at macworld
https://medium.com/datadriveninvestor/2019-the-year-of-progr...
What's old, is new again, 12 years later. It's how it always should have been. And guess what? There's no SDK that you need!! ;)
https://web.archive.org/web/20100603124720/http://www.forum....
All what is left seems to be Web Archive and these sites.
It's nice that a lot has been implemented, albeit slowly. Though some may still think about Apple incentives.
I.e.: http://nolanlawson.com/2015/06/30/safari-is-the-new-ie/ https://news.ycombinator.com/item?id=19586219
Additionally, unlike modern PWAs, web-apps back then had persistence for data only, so you had to reload the entire application over the network at each launch. People back then loved the switch to native apps because they were extremely snappier.
the whole problem is that apple shipped native apps with tons of skeumorphism and animations, so all js frameworks for webapps spend all their efforts to simulate "slide animation on page change" instead of working on hiding the ajax latency or using local storage better.
and in the end, everyone just saw $$$ in using the closed apps from the store.
Seemed to work well enough on webOS for the Palm Pre.
I was working for a very large app (tens of millions of daily users) at the time when firefox was trying to convince companies to port their apps to it.
We were big enough that Firefox sent their advocates to our offices and tried to convince us to port our app. Since what we were offering was a service, we were naturally open to have it on as many platforms as possible. I think that there might have been a monetary incentive as well but I might be misremembering there (I was not part of that negotiation).
After a week with their sdk and help from their devs, we threw the towel.
Publishing our product on Fos would have been impossible while keeping the app quality on par with iOS and Android and there were lots of missing/buggy APIs.
That was our last discussion with Firefox. For as long as there have been phones, there have been web apps targeting them, but there is a reason why we are still building native apps.
I pretty quickly got an Android phone instead.
Thats news to me. I read that KaiOS was built from the ground up & not derived from anything.
> Firefox OS hadn't thrown in the towel so early
That was a rather quite event and I was surprised to see no much discussion around it. An OS by Mozilla can be more trusted than an OS by Google. Why did Mozilla kill the project?
Where did you read that? Read the first sentence of: https://en.wikipedia.org/wiki/KaiOS (all with good citations, e.g., https://support.kaiostech.com/support/solutions/articles/350... )
But the weird thing is that I recently read in some magazine (I am unable to remember the name) about Google investing in KaiOS which was a Brazilian company and the whole article was mentioning how Silicon Valley is unable to understand its customers as they live in a bubble and how its the companies in developing countries that truly understand the needs of the customer and deliver. Its mentioned that KaiOS is gunning at Android for #1 in India and Google's investment was a sign of acceptance and a hint that the new version of Android will get shelved soon. It even referred to India based Zoho as the true challenger to Google Apps & Office 360. Also how wechat is miles ahead of Whatsapp & likes and how in a sense it challenges the whole Silicon Valley in terms of all the features it has. Basically it was urging the readers to not assume that silicon valley products as superior and try others too.
I hope Mozilla reconsiders and starts up Firefox OS again. I prefer it over a company driven product like KaiOS.
P.S. Just noticed that the last name of the KaiOS's CEO is "Codeville".
I just used new generation of the same display, and a one handed Twiddler 3 keyboard.
Raspberry pi doesn't have cellular, so I am looking at Zero phone project which has a solution. But so far I am already extracting value from my wearable computer in many easily implementable use cases.
Battery I am using is this: https://tech.scargill.net/ravpower-the-ultimate-pi-ups/
It indeed helpfully maintains stable power output when being plugged and unplugged from mains itself. But only on one of the output ports. Also this is not always true when there's active power consumer on the second port. Other than that, I'm happy I found this powerbank model.
PostmarketOS is still in a developers-only state, and there's a lot of directions you could take everything that's atop the kernel. My own whim was to incrementally build the userland in Racket (though that's on hold during job search); notes: https://www.neilvandyke.org/postmarketos/
1+: $9.87257
10+: $9.31375
100+: $8.78655
500+: $8.28920
1000+: $7.82000
That is absurdly cheap, and you can be sure with million-unit orders they're probably getting half that price and working direct with the manufacturer. $7.82 per unit @ 1000 for that feature set[1] brings it into the realm of hobbyists to make their own phones. Order the chips, prototype PCB, battery, charger circuit, low-res touchscreen , and mounts for USB+SD+audio from China and get them within a week. 3D print some cases, spend 20 days trying to get video output working on the completely undocumented Chinese display, boom. Made your own functional (but ugly and bad) phone for < $35.
[1]: https://www.qualcomm.com/products/qualcomm-205-mobile-platfo...
Plus, this cheaper chip can be dropped into phone designs from 2014 (Snapdragon 210) and 2015 (Snapdragon 212) with little to no engineering or software work. Seems like a great way to reuse tested cheap phone designs without additional cost or delay in getting products to market.
https://www.aliexpress.com/item/lt4120-Snapdragon-X5-LTE-T77...
https://www.amazon.com/powerday-Mini-PCI-Adapter-Module/dp/B...
https://www.aliexpress.com/item/2017-Newest-SIM-Card-4G-LTE-...
Last one is a complete hotspot and apparently can use the USB port either as a 4G modem (maybe WiFi card also through an internal hub?) or as a power supply port when stuck on a power bank.
https://www.droid-life.com/2015/02/05/us-wireless-carrier-ba...
This module meanwhile will work on all of T-Mobile's bands and all of AT&T's commonly deployed bands: https://www.aliexpress.com/item/EC25-AF-Mini-Pcie-CAT4-Wirel...
Neither T-Mobile or AT&T will brick your unapproved device, unlike Verizon.
[1] https://www.zdnet.com/article/ftdi-admits-to-bricking-innoce...
Unfortunately these are not marketed at all in the Western world and probably wouldn't work on domestic carriers.
https://us.alcatelmobile.com/alcatel-go-flip/
FWIW it apparently uses an older, pre–Google-investment KaiOS.
Edit: It's $100 new which isn't too bad, but less than $40 open box on eBay and other sites. That's practically impulse buy territory. I'll definitely have to consider it.
A Nokia E71 was my daily driver for about a year, starting in 2010. I loved:
- the hardware (slim yet solid, keyboard only slightly worse than a Blackberry, nice tapered+curved edges)
- the extensive list of features (e.g. Wifi+3G, built-in SIP client, support for Exchange ActiveSync)
- support from important apps (e.g. Skype)
I hated:
- How finicky it was. I lost count of the number of times I had set up the mail client again (maybe after re-installing it) because it stopped syncing. (This was back when GSuite free accounts supported ActiveSync, which allowed push email.)
- The weirdness around selecting Wifi or 3G connection (I don't recall exactly what the issue was, but I remember there was something confusing about it).
Whoa, let's not get ahead of ourselves. Pholdables are not even being sold yet, let alone "replacing the desktop".
They certainly are pretty nice... writing this from an HP Specter x360 ;)
And now Google generously writes a check for $20M to KaiOS... No strings attached I'm sure.
It makes me sad that the phone platforms are not free (not just as beer, but especially free as in freedom). It makes me furious that "smaller" players (Sony and the like) weren't strong and smart enough to step together and create an open platform that would avoid Google's control. But I guess when you are strong enough to do that, you no longer have the incentive to. So the users are left with a bunch of bad options... Basically, we are free to choose one or more of: walled garden, data stealing^W^Wadvertising, spyware, UX disaster. Nice. </rant>
But unfortunately, there are many things missing yet.
- decent crypto base - decent set of apps (with contraints on user/input interfaces) [ as of now, there isn't an email app available yet! ]
And pretty much every phone vendor/TelCo is building a walled-garden and an appstore on their own, considering the licensing possibilities offered by KaiOS. Every TelCo will block sideloading of apps and restrict users from offering a full fledged KaiOS experience, as it turned out in the Android world.
Jio runs Jio AppStore. >> Please note: while the JioPhone runs on KaiOS, its app store is managed by Reliance Jio and called the JioStore. For this reason, we can’t guarantee the below apps will be available on the JioPhone, nor does it mean apps available on the JioPhone are available in other countries.
From https://www.kaiostech.com/meet-the-apps-available-on-kaios/
I haven't used kaiOS, but if WhatsApp E2E encryption was possible doesn't it mean that it has decent crypto for implementing RSA/ECC i.e just like a web browser?
You mean the drivers not being in the Linux Kernel/hard to port ? because I have a very hard time believing most smartphones couldn't run the Linux kernel, provided it's compiled to whatever architecture and the drivers are there.
Now it looks more like a pseudo-mikrokernel, with drivers running on their own processes, talking via Android IPC with the kernel layer.
Also it has a much more security knobs turned on as mainline, and many features trimmed down that are irrelevant to Android userspace.
If anything, Android 8 reduced the gap to mainline with switching e.g. to DRM synchronization fences.
> Binderized HALs. HALs expressed in HAL interface definition language (HIDL). These HALs replace both conventional and legacy HALs used in earlier versions of Android. In a Binderized HAL, the Android framework and HALs communicate with each other using binder inter-process communication (IPC) calls. All devices launching with Android 8.0 or later must support binderized HALs only.
>
> Passthrough HALs. A HIDL-wrapped conventional or legacy HAL. These HALs wrap existing HALs and can serve the HAL in binderized and same-process (passthrough) modes. Devices upgrading to Android 8.0 can use passthrough HALs.
> All other HALs provided by the vendor image can be in passthrough OR binderized mode. In a fully Treble-compliant device, all of these must be binderized.
> Legacy HALs (also deprecated in Android 8.0) are interfaces that predate conventional HALs. A few important subsystems (Wi-Fi, Radio Interface Layer, and Bluetooth) are legacy HALs. While there's no uniform or standardized way to describe a legacy HAL, anything predating Android 8.0 that is not a conventional HAL is a legacy HAL. Parts of some legacy HALs are contained in libhardware_legacy, while other parts are interspersed throughout the codebase.
https://source.android.com/devices/architecture/hal-types
A binderized HAL driver only requires a minimal kernel surface, if anything.
Furthermore, I specifically stated pseudo on my description.
Here are some obvious hints to why this is not true:
* there are no HALs defined for even 1/3rd of what kernel drivers you would need to run a modern device
* a bunch of the HALs require you to provide handles obtained from standardized kernel interfaces (e.g. the aforementioned sync objects)
Finally, of course: all HALs run in userland! All their power is in being granted SELinux access to various kernel interfaces! Vendors can not change these rules or risk failing certification.
[1] https://source.android.com/devices/architecture/kernel/andro...
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...
[3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...
/Edit - battery lasted two weeks between charges.
Way to bury the lead! I'd put up with a lot for charge times that long. Or just a backup phpne
and FWIW, I'm British and I've never seen it spelt lede outside of this forum. I guess it's an American thing, and even then, it's pretty wrong.
So as clear as mud then!
That was the most requested feature on JioPhone 1, when it was released & people were ready to put more money into next cheapest android smartphone to have it. Now, WhatsApp is available on both JioPhone1 & JioPhone2.
Obviously it is packaged standalone version of WhatsApp web. WhatsApp team has been very successful in bring consistent performance of their apps on all platforms they support, so I assume it works well.
[1]:https://blog.whatsapp.com/10000649/WhatsApp-for-JioPhone-on-...
Edit : typo
The KaiOS version was built from scratch.
So the KaiOS version apart from sharing UI, might not have much common with the WhatsApp web. Then again, I wonder how much of the tech used for secure communication with the phone from WhatsApp web can be repurposed to make it a standalone application?
By the way I've got a question for people who've used Kai OS / firefox os. To use google apps like youtube/ maps etc do you need to log in like in android?
I hate smartphones with a passion, so just use an old dumbphone. I face a lot of pressure through work to have one though. I'm thinking that if I do eventually get forced back into smartphone ownership I'll opt for a Fairphone 2. Major benefits being the improved environmental consideration, the ability to run Lineage OS (so no Google), and the modular approach makes it easy to hack/repair. Main downside is that it is very expensive (to me anyway... I get that many people these days seem to think £1,000 is a reasonable sum for a Facebook/Instagram PDA!).
Also the question is not really “does it support WhatsApp”, but “does WhatsApp support this OS”. Which may eventually be the case if there's enough market share for that.
[1] https://www.bgr.in/news/jiophone-kaios-surpasses-ios-india-s...
Europe have free sms, so I do have friends with telegram, signal, skype, whatsapp, dumb phones, facebook chat, wire, etc., and at the the center of this crazy venn diagram, we can all discuss with sms for free. Most discussions are not group chats.
In Asia they have big whatsapp competitors like weechat. But I've seen kik used as well.
In Africa, it's also a lot of text message since they get the best coverage.
Whatsapp is definitly popular, but far from a universal.
Give me that phone with monochrome display, the usability of Nokia's original OS and modern network connectivity and I'd jump at it.
I think your best bet is a cheaper feature phone, though most in stores are carrier-locked, so you may have to shop for an unlocked one online.
Of cause I'm in a non-English speaking country, so that may change the usage, but I don't know anyone who uses Google Assistant, Siri or Cortana and only two people who use Alexa, which technically isn't even available here.
The same phone without Google Assistant would be better, sure. But it'd also be much more expensive - if it was allowed to exist at all.
Bingo. That's is what it all about. Free email, free cloud docs and photos, free browser, free web tools. KaiOS should be running Google code. Replace DoD with Google (Skynet from Terminator) though.
Hell. They would even browse Internet using Chrome signed in to their G accounts, giving away browsing history (all their secret dreams, interests that even closest people don't know about)
And these phones don't run Chrome at all.
Its the code that runs 24/7 what matters, Android or a few G services is of no difference.
> I wasn't using my data for anything
Browsing, location, contacts, photos of friends, calendar, emails... the lot. Goal is your full psychological profile, skills, circles, reactions, job positions. From as much data as possible. Uses today are simple ad targeting, maybe 3rd party screening checks. Tomorrow?
I've also heard of kids getting left out of things socially for the same reason. One family tried the "you don't need a smart phone until sometime in high school" thing, but their kid started missing invitations to everything because the plans developed on whatsapp, snapchat, or Facebook - all of which the kid didn't have real-time access to.
They relented and got their middle school kid a smartphone.
Way too much of the social world of students goes through phones to be able to keep up without a smart phone.
My daughter is in middle school, and pretty much everyone in her class has iPhone. Only a few have an Android phone.
School requires every student to have a Chromebook, but even teachers encourage students to use smartphones. Also, one of the apps only works on smartphones.
My daughter has my old Samsung 6s. She doesn't complain or ask for a new phone, but I know she wants an iPhone.
And a mandatory Google account for tracking your kids. I'd change the school.
Any OEM would eventually just replace it for something else, preferably non copyleft.
But who can blame em? The government wants the USD flowing in, and the companies (already strapped for talent and cash to pay for such) get their IaaS for free for decent chunk of time… virtually no push back here like there is in the states to 'some' degree… and it keeps their offices from getting raided again!
This crushes the Raspi3 for the value.
I was looking a bit into this. It seems that KAI os is not an opensource project. Plus the OS is flashed into the ROM of these phones so its also very difficult to install a new OS reliably. So even if you got the GIPO to work with the phone how would you actually program it? Kai OS has a device api [1] but as far as I can tell it does not give you access to linux shell.
If the phone has a usb slot you can use a usb gipo board [2]
[1] https://developer.kaiostech.com/api
[2]https://numato.com/product/8-channel-usb-gpio-module-with-an...
>I'm quite surprised at the cost of a USB GIPO board. I suppose I shouldnt have been.
>Developing an OS for a platform that could change at anytime, seems risky/time consuming.
>novel ways of communication- Put everything on wifi relays, or communication with other peripherals
Might be worth buying one of these phones and taking it apart to see whats inside.
EDIT: Looking to select my microprocessor for a consumer product. An entire computer would be nice.
Or find a device that supports booting from an sd card. I don't think there is any phone out there that supports that. There are not even that many laptops that can boot from an sd card slot. But they can from an sd to usb adapter...
>novel ways of communication- Put everything on wifi relays, or communication with other peripherals
HIGH FIVE!!!!!
This is a very good idea. But then again how will GIPO attached devices send wifi signals and understand incoming wifi signals? You'll need a separate chip for that (If I understand correctly) that would have radios and antennas. I'm sure you can find a cheap way to build such a device using electronic components that you can find online.
A wifi enabled usb is very very cheap. wifi usb cards would be even cheaper, I think. A mobile phone like this is a complete package for about $10-$15.
In practice though, unless you plan to deploy a lot of them, as a hobbyist, your time is likely more valuable than any hardware so it seems reasonable to just go with the most popular platform.
"Customers can get a WizPhone WP006 from vending machines at more than 10,000 Alfamart stores for just USD$7 (IDR99,000)1. Then, with the built-in AllWizapp, customers can unlock shopping benefits in Alfamart by scanning barcodes on each product and making their purchase directly via the app on their WizPhone."
source: I'm Indonesian (but I use postpaid).