Related
Hey all, Just bought the g-tab as my first android device. I liked playing with the Xoom and iPads in the store, but wanted the same experience for cheap and knew that I would have to root this g-tab thing to unleash that awesome hardware value. So far I've easily put TNT Lite 4.2 and it really is much faster and more usable then the Tap N Crap that viewsonic shipped. Thanks a bunch devs for fixing what should have never been modded in such a crappy way.
My question is will there every be Android 3.0 available for the gtab? I just read an article about how google is trying to ensure oems don't mess up the UI like viewsonic did to protect their reputation. Since the gtab wasn't even an official android device, I'm wondering if Honeycomb will even be available to viewsonic or devs here to put on the gtab.
I totally agree with this article. Google shouldn't be as totalitarian as Apple, but this lack of quality control is making Android look bad in the public sphere (not to hackers of course) So did I just buy a dead end device?
As a new user - I still can't post links, so here's the pasted article from pc world:
Why Google's Tighter Control Over Android Is a Good Thing
Limiting availability of Android 3.0 code and apparent tightening of Android smartphone standards means that Google finally gets it about the platform.
By Galen Gruman, Infoworld Apr 6, 2011 11:30 am
Last week, Google said it would not release the source for its Android 3.0 "Honeycomb" tablet to developers and would limit the OS to select hardware makers, at least initially. Now there are rumors reported by Bloomberg Businessweek that Google is requiring Android device makers to get UI changes approved by Google .
As my colleague Savio Rodrigues has written, limiting the Honeycomb code is not going to hurt the Android market . I believe reining in the custom UIs imposed on Android is a good thing. Let's be honest: They exist only so companies like Motorola, HTC, and Samsung can pretend to have any technology involvement in the Android products they sell and claim they have some differentiating feature that should make customers want their model of an Android smartphone versus the umpteenth otherwise-identical Android smartphones out there.
[ Compare mobile devices using your own criteria with InfoWorld's smartphone calculator and tablet calculator. | Keep up on key mobile developments and insights via Twitter and with theMobile Edge blog and Mobilize newsletter. ]
The reality of Android is that it is the new Windows : an operating system used by multiple hardware vendors to create essentially identical products, save for the company name printed on it. That of course is what the device makers fear -- both those like Acer that already live in the race-to-the-bottom PC market and those like Motorola and HTC that don't want to.
But these cosmetic UI differences cause confusion among users, sending the message that Android is a collection of devices, not a platform like Apple's iOS. As Android's image becomes fragmented, so does the excitement that powers adoption. Anyone who's followed the cell phone industry has seen how that plays out: There are 1 billion Java-based cell phones out there, but no one knows it, and no one cares, as each works so differently that the Java underpinnings offer no value to anyone but Oracle, which licenses the technology.
Google initially seemed to want to play the same game as Oracle (and before it Sun), providing an under-the-hood platform for manufacturers to use as they saw fit. But a couple curious things happened:
Vendors such as Best Buy started selling the Android brand, to help create a sense of a unified alternative to BlackBerry and iOS, as well as to help prevent customers from feeling overwhelmed by all the "different" phones available. Too much choice confuses people, and salespeople know that.
Several mobile device makers shipped terrible tablets based on the Android 2.2 smartphone OS -- despite Google's warnings not to -- because they were impatient with Google's slow progress in releasing Honeycomb. These tablets, such as the Galaxy Tab , were terrible products and clear hack jobs that only demonstrated the iPad's superiority . I believe they also finally got the kids at Google to understand that most device makers have no respect for the Android OS and will create the same banal products for it as they do for Windows. The kids at Google have a mission, and enabling white-box smartphones isn't it.
I've argued before that Android's fragmentation, encouraged by its open source model, was a mistake . Google should drive the platform forward and ride herd on those who use it in their devices. If it wants to make the OS available free to stmulate adoption, fine. But don't let that approach devolve into the kind of crappy results that many device makers are so clueless (or eager -- take your pick) to deliver.
So far, Google's been lucky in that the fragmentation has been largely in cosmetic UI areas, which doesn't affect most Android apps and only annoys customers when they switch to a new device. The fragmentation of Android OS versions across devices is driving many Android developers away , as are fears over a fractured set of app stores. Along these lines, Google has to break the carriers' update monopoly, as Apple did, so all Android devices can be on the same OS page.
It is true that HTC's Eris brought some useful additions to the stock Android UI, serving as a model for future improvements. But the HTC example is the exception, and Google's apparent new policy would allow such enhancements if Google judges them to be so.
More to the point is what the tablet makers such as ViewSonic, Dell, and Samsung did with their first Android tablets. Their half-baked products showed how comfortable they are soiling the Android platform. For them, Android is just another OS to throw on hardware designed for something else in a cynical attempt to capture a market wave. The consistently low sales should provide a clue that users aren't buying the junk. But do they blame the hardware makers or Google? When so many Android devices are junk, it'll be Google whose reputation suffers.
Let's not forget Google's competition, and why Google can't patiently teach these companies about user experience: Apple, a company that knows how to nurture, defend, and evangelize a platform. Let's also not forget the fate of Microsoft and Nokia , who let their Windows Mobile and Symbian OSes fragment into oblivion. And let's remember that the one company that knows how the vanilla-PC game is played, Hewlett-Packard, has decided to move away from the plain-vanilla Windows OS and stake its future on its own platform, WebOS , for both PCs and mobile devices. In that world, a fragmented, confused, soiled Android platform would have no market at all.
If Google finally understands that Android is a platform to be nurtured and defended, it has a chance of remaining a strong presence in the mobile market for more than a few faddish years. If not, it's just throwing its baby into the woods, where it will find cruel exploitation, not nurturing or defense.
I didn't read your 1000 word post, but I read your topic. HC on GTAB has NOTHING to do with Google. It has everything to do with Nvidia abandoning GTAB.
The media has an idea in their head but they are shooting the messenger. Google has no choice when Nvidia stops producing source for the proprietary elements of the system.
Nvidia simply does not care about Harmony which is the hardware reference legacy devices are built on.
So this device is going to be left behind when it comes to the new android stuff?
It is interesting that you ask. With 318 posts here you have to have followed some of the threads discussing this before. At this point in time I don't think anyone knows. Lots of speculation, lots of pent up desire and the best Devs ever so I am sure there will be improvements, Will it ever make full HC who knows?? If you read your article carefully, even the stuff out there ( Zoom and Transformer) does not have complete Honeycomb.
I wonder what Honeycomb will bring to the picture that we don't have already. I have my gtablet rooted and running TnT 4.4 and it's sufficient for almost all my tablet needs. Yesterday I was reading Kindle books to the kids, streaming movies/music from my media center PC, watching youtube and browsing the net, all with nary a hiccup. I even got a cheapo keyboard leathercase to use for editing documents. If it's the UI, the current Launcher Pro Premium and GO Launcher EX are pretty nice alternatives.
I have played with the XOOM tablet at Best Buy and thought other than some pretty UI and a nicer screen, functionally I wasn't getting much for double the price.
samaruf said:
I wonder what Honeycomb will bring to the picture that we don't have already. I have my gtablet rooted and running TnT 4.4 and it's sufficient for almost all my tablet needs. Yesterday I was reading Kindle books to the kids, streaming movies/music from my media center PC, watching youtube and browsing the net, all with nary a hiccup. I even got a cheapo keyboard leathercase to use for editing documents. If it's the UI, the current Launcher Pro Premium and GO Launcher EX are pretty nice alternatives.
I have played with the XOOM tablet at Best Buy and thought other than some pretty UI and a nicer screen, functionally I wasn't getting much for double the price.
Click to expand...
Click to collapse
Thats interesting. What ROM are you running? Most of my video is choppy, and I read in the dev forum this has to do with no video acceleration yet for the Gingerbread versions.
Good point - if it does what you want it to do then so what if it's not the newest... I'm a little embarrassed, but still rockin out to my first gen iPod nano a the gym
Guess I still wanted whatever tablet specific ui improvements that honeycomb was expected to bring.
nitefallz said:
Thats interesting. What ROM are you running? Most of my video is choppy, and I read in the dev forum this has to do with no video acceleration yet for the Gingerbread versions.
Click to expand...
Click to collapse
As I mentioned in my post, my ROM is TnT Lite 4.4 with Clemsyn's kernel (v9). I can stream 700 MB avi files with no stuttering or choppiness. I use GMote app on the tablet and the GMote server in the media PC. My video player is Rockplayer, which is free from the market.
I too was just at Best Buy bout a week ago and messed around with the Xoom for a little bit. Quickly I realized why its been a couple years since I've been to this store (prices?!?!), not to mention the help asking me if I had any questions and if I was looking to buy the Xoom (they left me alone after proclaiming I was completely satisfied with my gtab).
The only real difference I could notice (which in my eyes was a big one) was the interface. Its definitely more "flashy" in looks and prettier for eye-candy, but no real difference outside of that, actually seemed to lag a bit; almost comparable to the gtab out of box.
Me personally, I'm in no hurry to see any kind of honeycreams equivalent make its way to the gtab. I'm more anxious to see gojimi release their vegan ginger Beta more than anything right now. Been counting the days (sometimes hours) since reading their update about him coming back from vacation, lets do this!
Closing thread - see this
http://forum.xda-developers.com/showthread.php?t=1026411
Hi guys. I hope this is the right place for this question. I'd rather have put it in the development forum, since I expect more devs frequent it than here, but I'm not sure it would be appropriate.
I will be writing a paper for an Operating Systems class looking at the Android OS. Specifically, I intend to compare it with Linux, giving consideration to the optimizations that were made for developing it as a mobile platform. I would like to also incorporate some analysis of the source code. This would likely include compiling a kernel from the source and probably installing some variant of it. I do not have any experience with OS/ROM development but I do have a decent amount of programming experience.
I would like to know if anyone has any favorite resources on the web, or even print, on this topic that would qualify as "academic." Unfortunately, this means forums and wikis are out. As far as I can tell, resources on this topic are scarce—or maybe I'm just not looking in the right place. I would appreciate any input I can get.
Thanks in advance!
bump
10 char
You could browse around here: http://developer.android.com/resources/index.html.
Android is Linux with Google's user space running on top of it. If you're just doing OS-level comparisons, it should be a pretty short report.
Google adds a very small number of things to the kernel, like wake-locks, but those are (allegedly) getting phased out in favor of "native" constructs.
I guess it would be more appropriate to say I'm interested in OS engineering rather than development for the OS, dealing particularly with the kernel.
Are there no major modifications done to the Linux kernel in such respects as scheduling, memory management, paging algorithms, I/O, etc. to optimize for mobile devices? I can't seem to find much that actually discusses how these are implemented in Android. For example, I am aware that there are apps that allow us to change the scheduler: are these just toggles for stock Linux code implementations?
There are a bunch of device drivers, obviously, but the only real kernel changes have to do with something called "wake-locks", which are a specialized form of locking that allow applications to prevent the phone from going to sleep. And one of the Linux kernel guys has demonstrated how an existing construct can be used to the same effect. Google has tried (with varying degrees of enthusiasm) to try and get their stuff integrated back into the kernel because anything _not_ in the kernel is a lot more work to maintain.
Right now, the kernel ARM maintainers are working on improving device management on ARM (currently, there's not much reuse, resulting in a dozen or so different drivers for some common IP blocks), which is a cause near-and-dear to Google's (well, Google's-phone-making-partner's) heart, so Google is probably going to try to avoid doing anything seriously incompatible.
Thanks for the info. I guess Android will have to sit this one out then.
I can't seem to find much on this, so I thought I'd ask the question. I personally use a Samsung Galaxy Nexus and was a previous owner of a Galaxy S1. I also sport an Apple Macbook Pro and I love the computer.
There's been a constant "reminder" from various articles how developing for iOS appeals to the developer more than doing so for Android.
This topic has spawned countless of times, and with the recent intro of Instagram to Android, that topic has been re-written once more to show why iOS is "dominant" among developers compared to Android. Article HERE.
Thing is, with all this talk about developing for iOS being better, I find myself asking "if that were true, then why do developers still develop for Android? If that were true, Instagram wouldn't even bother coming to Android...especially since it's free."
So what would make developers for Instagram want to make an app for Android when according to these articles:
Developing on Android is "harder" because it has to adapt to countless hardwares
Android developers make less than iOS developers
Do you develop for both iOS and Android? What's your take? What actually entices you to want to work on the Android platform?
It would be nice if a developer who works on both platforms can give some insights. Please no fanboy or anti-apple talk here...I am sure many of you Android users like me, would have had your friends who are iPhone users bring up such a topic on how they've read that developing for iOS is better, and you can't explain to them why people still make apps for Android cause there's little material online to covers that topic. I'm genuinely curious to know from a developer's perspective
Developers want to get their program out to as many people as possible so they develop for platforms where the customers are at. The two biggest phone operating systems right now are iOS and Android.
Developers choose iOS first because their is a lot less device diversity with iOS devices so developing an app is probably easier. It has also been shown that there is more money to be made selling iOS apps than Android apps which could be due to the fact that people who are on a tight budget may see an Android device as a better deal or may have a carrier that doesn't even sell the iPhone. Piracy is an issue on both platforms but it could be argued that Android is easier to pirate on since apks can be sideloaded without rooting where as iPhones have to be jailbroken. But sideloading apks is used for legit reasons as well, like testing betas, nightlies and other apps that aren't distributed through App Stores.
Android apps have to account for multiple screen resolutions, ratios, and densities. Most regular apps scale just fine. Games seem to be where there are the most issues and I really wish Google would address the issues. It seems each GPU type needs its own support (PowerVR, Nvidia, Adreno, etc). I really wish Google would implement something like DirectX so games can be played on any GPU with enough power. iOS has the advantage here because only a single GPU type is used, PowerVR I believe, so all games can be optimized for it. Couple that with the fact that iOS tends to bring in more money and this is why the game developers usually favor it over Android.
Thanks for the insight. I figured gaming would be difficult for developers but didn't understand why, I just naturally assumed that "if the app seems more complicated, it naturally equates to more complications making it run on various hardwares".
Am I right to say then that when tech reviewers write about how Developers favor iOS to Android, it's mostly pertaining to gaming?
What about non-gaming apps? Is reaching as many people as possible the only incentive to go Android? Take Whatsapp, or Instagram that recently came out...it's free on Android, it also has to deal with multiple hardwares (though now I'm assuming it's actually not as tough as it sounds to accomplish if the app's fairly simple)...is there an incentive for developers to create an Android App...cause the guys at Instagram or Whatsapp could have gone "Well there's nothing here for me, I'll just stick to iOS"...because from what I see, it looks like opening it to the Android market meant having to stress their servers with a sudden influx of users, which mean spending more money to maintain them so it doesn't slow down too much...it seems like a lose-lose situation from where I'm standing. =\
I guess for some apps, google ads are what keeps them going...like Draw Something. I do wonder though how Whatsapp and Instagram manages its upkeep when it doesnt have ads...and if the answer is that they use the money earned from iOS to manage their expansion, is it really worth it if the goal is just branding purposes.
If there is a market to reach developers will develop. Web developers had to put up with the terrible non standard supporting ie6 for years. It was a real pain to develop for but had a large user base that couldnt just be ignored. Android is the same way, developers go where they can reach the consumer. Luckily android its nowhere near as bad as ie6 was.
Sent from my Touchpad using Tapatalk
spunker88 said:
If there is a market to reach developers will develop. Web developers had to put up with the terrible non standard supporting ie6 for years. It was a real pain to develop for but had a large user base that couldnt just be ignored. Android is the same way, developers go where they can reach the consumer. Luckily android its nowhere near as bad as ie6 was.
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
Thanks for the input! From your take, it seems like developers make apps for Android not because they want to, but they have to.
Do you or any of the developers reading this, can testify that there are some ups to developing on Android as compared to iOS.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
lufc said:
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Click to expand...
Click to collapse
Hi, sorry the topic may be [Q] but it's meant to generate comments and thoughts pertaining to the Android platform as per the sub header for Android General
Could it please be sent back to Android General? The Q&A section seems to be a place for people to post technical questions they need help solving.
Anyway, anyone else able to share their thoughts? Do you develop for both iOS and Android? It seems so far that people prefer to develop for iOS and lesser for Android, but they do it cause they have to as a means of reaching to the masses, but not really because they want to.
Anyone beg to differ? Do you have a reason why you actually prefer developing for Android over iOS?
Hi,
I'm a web developer, and when I decided to try mobile development, I made the choice to develop only for Android, for various reasons, but mainly because I'm not a fan of the Apple ecosystem.
This is not fanboyism here, I'm not bashing Apple, they make great products. But I prefer a fragmented ecosystem, with various companies, various devices, various app markets, etc. because this is a great source of opportunities. I also like the fact that android is open-source, leaving the availability to study the source code and hack around.
As for the difficulty to develop for various devices, I'd say that I'm used to it, being a web developer. Web devs are used to cope with various browsers (some of them being pretty old) and different screen sizes. See for example the mediaqueri.es site (cannot post link since I'm a new user)
thibaultj said:
Hi,
I'm a web developer, and when I decided to try mobile development, I made the choice to develop only for Android, for various reasons, but mainly because I'm not a fan of the Apple ecosystem.
This is not fanboyism here, I'm not bashing Apple, they make great products. But I prefer a fragmented ecosystem, with various companies, various devices, various app markets, etc. because this is a great source of opportunities. I also like the fact that android is open-source, leaving the availability to study the source code and hack around.
As for the difficulty to develop for various devices, I'd say that I'm used to it, being a web developer. Web devs are used to cope with various browsers (some of them being pretty old) and different screen sizes. See for example the mediaqueri.es site (cannot post link since I'm a new user)
Click to expand...
Click to collapse
Thanks for your 2 cents! Am I right to assume that in fact, having to deal with different hardwares and screen sizes are actually a norm among developers before iOS came along? In other words, yes, Apple is right to say criticize that other platforms are harder to work with compared to iOS but that's because iOS is the exception among developing platforms where it's system is easier to work with?
spunker88 said:
I really wish Google would implement something like DirectX so games can be played on any GPU with enough power.
Click to expand...
Click to collapse
But Android and iOS already have something like DirectX - OpenGL ES 1.1 and 2.0.
The_R said:
But Android and iOS already have something like DirectX - OpenGL ES 1.1 and 2.0.
Click to expand...
Click to collapse
Thanks for the additional input...if there always is a direct standard like Open GL in both iOS and Android, what's the difficult part about manufacturing games for Android?
iOS required Apple computer to install their development environment. And You must pay 99$ per year for being the official iOS developer..
ayen1234 said:
iOS required Apple computer to install their development environment. And You must pay 99$ per year for being the official iOS developer..
Click to expand...
Click to collapse
I'd actually say that it is worth it.
yeahyeahright said:
Thanks for the additional input...if there always is a direct standard like Open GL in both iOS and Android, what's the difficult part about manufacturing games for Android?
Click to expand...
Click to collapse
I think its large number of the types of Android devices. It really isn't as simple as just supporting different screen sizes. Doing that is actually a really simple task using OpenGL.
With my own games I've experienced that what generally works on my test device won't necessarily work the same way on someone else's. For example, some devices support textures of any size while some devices have a constraint of the texture size being a power of 2. On many of my games which need multitouch, I've experienced that it doesn't always work the same on all devices either. On some it is downright broken while on other it just works fine.
There are many such other issues which you'd be aware of only after experiencing them.
The reason for this is the different hardware and the different software implementations that each phone manufacturer brings in. Even if the game "works" on a wide range of devices, there is always a different feel that you get when playing on a different device because of the hardware variations. You might get a good frame rate on a high end phone but have you tried playing it on a low end one? I've seen games from even the big publishers working fine on a high end phone but it just is completely glitchy on a low end one.
Now for a small developer with limited resources it can get really hard to test on and support as many devices as possible. This is one of the main reasons I feel that it can get really hard to develop games on Android. It just requires more effort if the developer wants to guarantee a good experience on a wide range of devices.
The other factor as stated before is that the iOS platform is more uniform. And moreover there are more people who are apparently willing to pay for your game on iOS than on Android. With one of my own games I've experienced that I've made more money in the last 10 days by selling it on the iOS App store than on Android in the last one year with ad revenues.
I actually started developing games on Android initially and one of the really big disappointments for me has been that I am not able to sell my games on the market(now Google Play) because Google checkout for merchants is only available in a few countries. This was the main reason for me to consider moving over to iOS. I think I could sell on a different market like the Amazon App store if I really wanted though.
Inspite of all that I'd say that Android is a great platform.
Wow thanks a lot for the insight! It's great to understand it from a developer's POV, especially one who works on both platforms.
I realise people do comment a lot about Android users less committed to pay for an app, I wonder why...I don't think it's due to their budget, my guess is that their afraid it may not work well on their devices...to that I think Google could really push hard and promote it's 15 minutes refund policy which I think a lot of users are not aware of....I use the 15 minute window a lot and it helps me to decide if something is worth my time buying or not.
I guess the "openness" of Android has allowed phone manufacturers to get really creative with their products (Touchwiz, Sense, Dual Screens, Qwerty Keypads etc) but at the same time, makes it harder for a developer to create stuff, probably even harder than creating stuff on a Windows Desktop.
Do any of you think that having "game settings" like you get on a Windows PC will help change this experience? Either one where the user gets to tweak the graphics (low, med, high) and performance, or perhaps one where the game will adjust graphics to the "recommended setting based on your hardware"? Is this even possible on Android or it's more complicated than you'd get on Windows?
yeahyeahright said:
Do any of you think that having "game settings" like you get on a Windows PC will help change this experience? Either one where the user gets to tweak the graphics (low, med, high) and performance, or perhaps one where the game will adjust graphics to the "recommended setting based on your hardware"? Is this even possible on Android or it's more complicated than you'd get on Windows?
Click to expand...
Click to collapse
Yeah, I have actually seen a few games that do that, and it does help. But it also requires some extra time and effort on the developer's part.
In some of my games too, I've added some simple settings in order to change the control schemes, so that if one of them doesn't work for you, you could choose the other one. Graphically, though, my games are really simple.
yeahyeahright said:
Thanks for your 2 cents! Am I right to assume that in fact, having to deal with different hardwares and screen sizes are actually a norm among developers before iOS came along? In other words, yes, Apple is right to say criticize that other platforms are harder to work with compared to iOS but that's because iOS is the exception among developing platforms where it's system is easier to work with?
Click to expand...
Click to collapse
Having to deal with different hardwares started to be a thing of the past, with the explosion of web apps. One platform for all, what a dream! Then came smartphones and tablets, and developing for a native platfrom became cool again.
Anyway, building for the web is still the only way to reach anyone with an internet access. The only problem with web apps is that it's harder to monetize. But the web's decentralized architecture is not a bug, it's a feature. That is what guarantees it's freedom and independance. You don't have such guarantees on a centralized market managed by a single company, whose first goal is profit.
Well, this post was slightly off-topic, sorry about that.
Thanks both of you for the really good insight. I guess Android is great as a supposedly "open" phone os, it certainly has a lot of hurdles to clear in order to please and entice developers the way iOS does, I'm not certain it can get there, but I do think they do make an effort, like the just upgraded emulator which shows Google's commitment to better developed apps (talk about timing!).
I'm certainly happy with my Android phone and from what I've read about the negative results developers gain from working on Android than on iOS, I take my hat off to those that stick around on this platform and try to make things happen. *clap*
=)
I choose Android for one reason. It's much cheaper. Only 25$ one time. iOS is 99$ every year
Hey guys,
I'm a writer for PhoneArena.com and I'm working on a piece about Android development. The idea is inspired by Koush saying that he is considering "adopting an Android 4.0+ only app development policy", and I wanted to get some ideas as to what you all see as the pros/cons to this approach.
I understand that dropping support for 2.x leaves out just under 50% of the market, but I guess I'm wondering how much you find that those users use apps. Koush and some commenters have insinuated that the Play stats for apps show that most users that actually download apps are on 4.x anyway.
What do you think? What are the pros/cons of developing only for Android 4.0+?
Thanks!
-Mike
I still code all my apps 2.3.3+ because there's not much I need in the later versions because of the great work of ActionBarSherlock, Android Support and Holo Everywhere. I run an app development company at android-app-development.ie, clients are usually local companies and the apps aren't exactly earth-shattering. They don't need many features but I get an earful if a customer can't install on their Galaxy S2. Still a great and hugely popular phone, most of them running 2.3.3.
Maru OS - providing Ubuntu -like "convergence" feature for our beloved Kenzo/Kate
Hi.
While browsing XDA,
Just came across this great post on xda feed. - https://www.xda-developers.com/maru...-to-nexus-7-2013-flo-other-ports-in-progress/
And I thought - this could be excellent, if, could be developed for our beloved Kenzo with the help of collaboration amongst a few Kenzo Devs.
This could - if implemented - manage to keep us on the excellently compatible Android OS while providing with a feature much awaited by lovers of the same.
@Umang96 @Ashish94 @xyyx @TheStrix @TheDarkStrix @mistercheese @Bitti09 @kairi_zeroblade @Plamb1r @abhishek987
Also, as I could make out, this is based off of AOSP, so maybe, if interested, perhaps @xyyx and other AOSP-based developers could also include just the commits in their own ROMs to make them an even awesome-er experience for themselves and their users!!!
Even though we have neither MHL compatability (I'm not too sure if that's a hardware related additional thing, or if a few commits might solve that issue as well), nor an HDMI slot in our phones, Maru coupled with Chromecast seems like a pure dream come true!!!
Would love it if you guys could please look into this. I know all you wonderful people are already devoting your precious time to other projects, but, and I firmly believe - a collaboration amongst you, if you guys would work together, perhaps as (MaruTeamKenzo), that could certainly make it possible sooner than anyone could expect !!
Cheers, and loads of love to all you amazing people!!!
bumpardo bumperty bump!
shanx_verma said:
bumpardo bumperty bump!
Click to expand...
Click to collapse
Bumping after 1 hour? Really?
Bump yet again.
To users who poll - please leave a comment, as I cannot view your names.
It well be a great idea
I want remix os
Nice initiative, I would really like a hybrid OS for kenzo as well.
But you can do this already.
Linux Deploy + VNC ( or stream desktop to DLNA if you need it on television )
More advanced personal computing
Hey,
I just dropped by as I to have just stumbled upon! MaruOS.
It sounds interesting, as dies what Samsung have done with the S8 docking mode and what Cannonical had been aiming for with Ubuntu (seems like that's now faded). (even Project Ara/greybus had some promise beyond mobile until it was canned)
However, I actually found Maru while looking for projects that might run more than classic mobile apps on a mobile platform. The current model is fine for a lot of things - games, communications, note taking, productivity, activity tracking etc....
But I want more. I want mobile devices that are active in the web (both local and online). I want IPFS to be feasible. I want to be able to serve up offline content in my locality (a la piratebox).
We can't realistically expect stable platforms is we hack all of that into ROMs, so why not container's?
Containerised server apps on mobile would be unmittigatedly cool.
Sure the hardware, particularly battery, is restrictive, but having run multiple Docker images on both a Pi and a cheap-ish (<80GBP) Intel-based Ubuntu machine (tbh Rasbian on a Pi made 'bunty on Intel look a bit pathetic for Docker usage in performance and stability - possibly storage or chipset limited, but still...) I think we're approaching a time when it's viable.
Imagine flexible, opt-in local cloud apps powered by smartphones & an orchestration tool. The cost of providing infrastructure and hardware to support events/gatherings could drop through the floor....
... obviously that's a bit of a tangent from the aim of Maru right now, but it's (if I understand this correctly) running Debian with android compatibility, so including Docker (or plain LXC) and an orchestrator for managing images/containers, along the lines of an app manager for traditional mobile "apps" doesn't sound impossible (and I'd settle for CLI on a touchscreen if it gave me the ability to fire up a server on my phone, or test a new tool without a laptop).
It does seem to be in line with the original concept of mobile devices being more than smartphones nowadays, with much more potential than we currently use...
p.s.
I know this is a bit of a rambling post, but local webs (potentially synching back to wider web via IPFS or plain old git), the ability to participate personally on line with real tools, not just feeding the advertisment-powered content machines is really appealing to me. It's not likely to be mainstream any time soon, but you've got to start somewhere.
I want remix os