Related
ok saw a post on the sprint hero boards and wanted to ask over here aswell since the g1 area has a lot more developers for it.
would porting webOS to an android phone seem possible? I had a palm pre for a bit was cool and fast, I like android more but the thought of running it would be cool
Noooooooooo
You mean porting over apps?
or running webOS on your phone?
In a word:
No.
In more words:
We need drivers. There are no WebOS drivers for Android devices. Many of the existing drivers that we need are proprietary, meaning (and I'm not sure on this part) most likely the hardware specifications necessary to write drivers are closed as well. If they are not closed, it would be possible--but not for a team of geeks like XDA. You'd need a major entity, like Google, to do it, which won't happen. Besides, not all of WebOS is completely open-source, just like not ALL of what goes into Android phones is. It's just not possible--even if the driver issue could be overcome, which it can't.
Yet another word:
This is a question, so it belongs in Q&A. Not to be a jerk or anything, but just letting you know, so next time you can post there.
Doesn't seem possible at this current time however I disagree with the post above if all of xda devs came together then it might be possible due to the fact cyanogen im guessing could make his own drivers etc. However as said above it would not be possible due to the fact it is not completely open-source
ps: Why would you want webOS it is nothing compared to android - IF you agree then post back with this a smile ^_^
xillius200 said:
Doesn't seem possible at this current time however I disagree with the post above if all of xda devs came together then it might be possible due to the fact cyanogen im guessing could make his own drivers etc. However as said above it would not be possible due to the fact it is not completely open-source
ps: Why would you want webOS it is nothing compared to android - IF you agree then post back with this a smile ^_^
Click to expand...
Click to collapse
Have you ever written a device driver? You need detailed spec of the interfaces of the piece of hardware you're trying to talk to. Without them you're trying to build the Empire State Building blindfolded with a teaspoon and pair of pliers.
linuxluver said:
Have you ever written a device driver? You need detailed spec of the interfaces of the piece of hardware you're trying to talk to. Without them you're trying to build the Empire State Building blindfolded with a teaspoon and pair of pliers.
Click to expand...
Click to collapse
Okay so simply put we would need MacGyver to write the drivers...
you know, none of this is true, as the drivers for all of the HTC android phones have the drivers built into the kernel (as opposed to running as modules with the exception of wifi) because of GPL, they have released this information, albeit kinda late (*cough* CDMA hero) one stumbling block is how WebOS is going to interface with the drivers may be different, keep in palm has its kernel modifications "drivers" also available (once again because of GPL) so if interfacing is different, it COULD possibly be reverse engineered... the actual WebOS platform IS closed source however, making this all much much more difficult.
http://developer.htc.com/
http://opensource.palm.com/
dont let anyone tell you its impossible, its not. Are you going to port it? No, if you had to start this thread, then its not likely.
mbazdell said:
Okay so simply put we would need MacGyver to write the drivers...
Click to expand...
Click to collapse
rofl..............
Napoleon said:
Impossible is a word only to be found in the dictionary of fools.
Click to expand...
Click to collapse
That said I like my android
linuxluver said:
Have you ever written a device driver? You need detailed spec of the interfaces of the piece of hardware you're trying to talk to. Without them you're trying to build the Empire State Building blindfolded with a teaspoon and pair of pliers.
Click to expand...
Click to collapse
Also yeah without knowing about the phone it is like building the empire state building. That's why you buy the phone open it up find details on the phone first off and try and figure it out by taking a long look and experimenting otherwise you will never get anywhere. It is like life without actually doing it and just saying about it you will never achieve it so you do it
If Cyanogen or another dev decided to do this it is not impossible as long as they know how to build a device driver which i know 4 of the devs on here can do it is not impossible. The question is would they actually do this project?
Personally I do not see a point in this project if you wanted a webOS why didn't you buy a palm sry if i may sound a little rude but it is the truth why buy a android?
If i may have sounded rude in the sentence above i am very sry you can shun me down
xillius200 said:
For linux once never went my way and stop having a go i was just voicing my opinion it is a free country im just saying with cyanogenmod, Wesgarner, Ctso, Kingklick etc. we stand a great chance at doing it and i bet cyan must have made a device driver before. so please don't go off on one i don't care if this get's made as stated below android is better anyway so get off my back linuxluver and stop being a jackass all I was trying to say is it could be done and not impossible you are making it sound like we have no hope in hell.
ps: I only wan't to come on here to chat and make friends not to be abused
ps2: Also yeah without knowing about the phone it is like building the empire state building. That's why you buy the phone open it up find details on the phone first off and try and figure it out without taking a long look and experimenting you will never get anywhere. It is like life without actually doing it and just saying about it you will never achieve it so you do it
Click to expand...
Click to collapse
You really have no idea whatsoever as to how computer hardware works. Like the other person said, there just isn't a chance in hell of a small group of people working in their free time without the cooperation of hardware manufacturers to do what you're saying.
Look at AOSP, think of all the people working on it, and we still don't have everything working on it correctly. And that's with an open-source OS, not to mention Android was meant to use on these HTC phones anyway.
Web OS is really nice but doesn't seem very popular considering only 2 phones have it while. 10+ phones will come out with Android. I bet if this was done the person asking would use it for like a month then go to another ROM. Which means all that work trying to make drivers would go in vain.
xencor said:
You really have no idea whatsoever as to how computer hardware works. Like the other person said, there just isn't a chance in hell of a small group of people working in their free time without the cooperation of hardware manufacturers to do what you're saying.
Look at AOSP, think of all the people working on it, and we still don't have everything working on it correctly. And that's with an open-source OS, not to mention Android was meant to use on these HTC phones anyway.
Click to expand...
Click to collapse
So is a small group of people not good enough look at bill gates for example creator of microsoft started of with the apple man 2 people now we have microsoft windows and apple so are you saying a small group of people can't do something amazing every now and again?
Also i do not care about webOS i hate webOS in fact i just wanted to extract my opinion and further fourth nothing is impossible look at wireless electricity about a few years ago seen as a myth now look at it. This could be done one day maybe not now but sometime in the future. Most of webOS is in java anyway and most of it is using dbus.
I thought that emulating it on a jvm may be possible? like freedsb running over the top of windows in a vm.
Also all those who port drivers from windows to linux and max to windows etc. have no help from the manafacturers and they still manage to do it and they work alone.
Im not going to voice my opinion in this thread again i have had enough with people who don't let people talk their mind all it was was an opinion nothing more and a possible chance of it working instead of it sounding like it's impossible unless you try you will never know and that is that stuff this thread i have had enough with you people i am out of here don't bother replying to this because i will not read it.
xillius200 said:
So is a small group of people not good enough look at bill gates for example creator of microsoft started of with the apple man 2 people now we have microsoft windows so youre point is?
Also i do not care about webOS i hate webOS in fact i just wanted to extract my opinion and further fourth nothing is impossible look at wireless electricity about a few years ago seen as a myth now look at it. This could be done one day maybe not now but sometime in the future.
Click to expand...
Click to collapse
Do the developers on XDA have a source of revenue that I'm unaware of? Do they have billions of dollars in profits that spurn growth and encourage new, more experienced developers to join the business and help? Is there even a business at all?
The answer is no. There is no R&D department behind XDA. There is no venture capital firm supporting cyanogen or kingklick with money.
Again, you really have no idea what you're talking about. This isn't just a "take open the phone, look at the serial number on the board, and then write your own driver." This is something that computer manufacturers spend years developing their own proprietary code and then design specific chipsets to work with it. Years and money, lots and lots of money.
And you're still forgetting that webOS and even parts of android are not open sourced, which complicates it even further, even to the extent of making a webOS port technically illegal under copyright laws.
xencor said:
not to mention Android was meant to use on these HTC phones anyway.
Click to expand...
Click to collapse
not 100% true, both android and WebOS run on top of the linux kernel, drivers are already written, like I said, its not a rewrite of drivers, rather interfacing with hardware may be different, but thanks to GPL, we can more easily figure out how the software interfaces with the drivers since we have drivers (albeit for some different hardware) for both Palm AND Android devices... obviously this would all be no easy task... but hell, android work tits on my Kaiser, with the radio/sms/wifi/camera/gps.... and it WASN'T designed to run android!
something else to mention I suppose is the work done to get Mer Linux (Open source replacement for Maemo) running on the Kaiser/Vogue, it booted and its X system worked enough to get to setup information, albeit the screen was too low of a res to do much and it has far too little ram to be useful... let me put it this way... it would be entirely possible for someone to port WebOS over, though the radio/BT/Wifi/accel/etc. may not work initially. I'd be stoked to try out test builds, and I think so would MANY other people.
*broken down: android wasnt meant to run on these phones, linux was meant to, and android was meant to run on top of that*
xencor said:
Do the developers on XDA have a source of revenue that I'm unaware of? Do they have billions of dollars in profits that spurn growth and encourage new, more experienced developers to join the business and help? Is there even a business at all?
The answer is no. There is no R&D department behind XDA. There is no venture capital firm supporting cyanogen or kingklick with money.
Again, you really have no idea what you're talking about. This isn't just a "take open the phone, look at the serial number on the board, and then write your own driver." This is something that computer manufacturers spend years developing their own proprietary code and then design specific chipsets to work with it. Years and money, lots and lots of money.
And you're still forgetting that webOS and even parts of android are not open sourced, which complicates it even further, even to the extent of making a webOS port technically illegal under copyright laws.
Click to expand...
Click to collapse
I have already said in my earlier post that it is not open-source so read b4 you post and even the smallest one man on his own can do someting incredible look at DA cracked the psp 14-15yo and wrote his own drivers and software and look at the ps3 hacker who has found exploit through the memory neither of them have a company or backing just normal people and are you saying that is not possible?
i will not talk any longer all in all webOS is a stupid idea it could be possible one day and end of
ps: I don't like but jmhalder is cool
jmhalder said:
not 100% true, both android and WebOS run on top of the linux kernel, drivers are already written, like I said, its not a rewrite of drivers, rather interfacing with hardware may be different, but thanks to GPL, we can more easily figure out how the software interfaces with the drivers since we have drivers (albeit for some different hardware) for both Palm AND Android devices... obviously this would all be no easy task... but hell, android work tits on my Kaiser, with the radio/sms/wifi/camera/gps.... and it WASN'T designed to run android!
something else to mention I suppose is the work done to get Mer Linux (Open source replacement for Maemo) running on the Kaiser/Vogue, it booted and its X system worked enough to get to setup information, albeit the screen was too low of a res to do much and it has far too little ram to be useful... let me put it this way... it would be entirely possible for someone to port WebOS over, though the radio/BT/Wifi/accel/etc. may not work initially. I'd be stoked to try out test builds, and I think so would MANY other people.
*broken down: android wasnt meant to run on these phones, linux was meant to, and android was meant to run on top of that*
Click to expand...
Click to collapse
Thank you for talking some sense on the subject that it is possible thank you very much i respect you because you think anything is possible you may go far in the world. the one's who never try may never know and for that will fall behind. You are the only one on here who talks sense and for that i applaud you
ps: Very Much thanks from Xillius200 for believing it to be possible instead of just shooting it down
ps2: It takes a true person to not give up and takes a less person to give up straight away so never give up
xillius200 said:
I have already said in my earlier post that it is not open-source so read b4 you post and even the smallest one man on his own can do someting incredible look at DA cracked the psp 14-15yo and wrote his own drivers and software and look at the ps3 hacker who has found exploit through the memory neither of them have a company or backing just normal people and are you saying that is not possible?
i will not talk any longer all in all webOS is a stupid idea it could be possible one day and end of
Click to expand...
Click to collapse
DA did not write his own drivers. "Cracking" and using existing drivers is not nearly the same thing, nor is using a loophole in a PS3 memory chip.
Again, i'm sorry, but you just have no idea what you're talking about.
As someone else has pointed out by now, it might actually be possible to get webOS on an android phone, but that's only because the drivers already exist, not because cyanogen and XDA are gods and can do what you're proposing.
xencor said:
DA did not write his own drivers. "Cracking" and using existing drivers is not nearly the same thing, nor is using a loophole in a PS3 memory chip.
Again, i'm sorry, but you just have no idea what you're talking about.
As someone else has pointed out by now, it might actually be possible to get webOS on an android phone, but that's only because the drivers already exist, not because cyanogen and XDA are gods and can do what you're proposing.
Click to expand...
Click to collapse
I am not calling them gods writing different drivers seperate to a device is possible and DA did write some of his own drivers for the psp for addons and linking to the pc. Also to gain access to the memory he had to make a device and write a driver for it that devices already came wth a driver but he wrote his own. This was a different person XD
And i have had enough i am out of here dont know why the hell we are argueing you do not know much about android either so leave it at that and keep the forum open
I here by cease this fighting going on and say good day
Hi all
MY QUESTION
How much work is it to get Ubuntu working on a cheap tablet, (in terms of weeks and stress/reliability)? I'm about to spend a year writing tablet software that needs cheap hardware. If I find a capable Android tablet going cheap, is it reasonable to consider getting Ubuntu working on it, instead of restricting myself to the Android OS to use cheap tablets? Would Ubuntu C++ apps still kill performance? (Ubuntu will save me lots of development in other ways.)
ALL comments pleease, however brief and knee-jerk.
BACKGROUND (all feedback gratefully received)
I'm at the design stage of a project to use tablets to improve education in poor countries. Extremely briefly, the tablets will use elements of social media to enable children to collaborate remotely and asynchronously on projects, and game aspects to get the kids excited, who have probably spent the day working on the fields, and to welcome kids with special needs. The system will enable education to continue in complex emergencies, such as droughts and conflicts. Currently most kids drop out after grade one as the education they're offered is so poor. Tablets can support teachers and enable kids to get more out of their classroom and homework time.
The system needs some clever back-end engineering to operate a local social network if there is no internet connection. (I'm thinking something like NodeJS acting as both a p2p client and a server.) It also needs to run on cheap devices, if it is to be adopted by third world Ministries of Education.
I am currently torn between Android and Ubuntu for tablets. Android will presumably be the cheapest platform for the foreseeable future - tablets now go for as little as $40 wholesale. However Ubuntu for tablets now offers the ability to bring a proper IT education to these children, as they can learn office software, desktop OS, etc. Ubuntu also provides source code I can customize, eg, GCompris, Tux4kids, KDE and Epoptes. I can see Ubuntu on other tablets here, but it seems the Nexus 7 is the cheapest tablet I can currently get Ubuntu on and performance is still an issue. Is that fair to say?
I can write everything using C++ and OpenGL to squeeze as much as possible out of every processor cycle. I have been a developer for 15 years, but am pretty ignorant when it comes to hardware/OS level.
My alternative is using something like Titanium and Unity, (I don't think HTML5 will perform well enough), so I have a bit more platform flexibility, at the price of having to develop everything from scratch, and using technologies for the back-end stuff that aren't as ideal, (such as Android Java and/or Titanium JS). But perhaps that keeps more options open for me?
My feeling is I should go for Ubuntu, but the price needs to reliably reach considerably below $100 to become a nationwide system in a poor country.
Obviously any comments or thoughts on any aspect very gratefully received. Don't restrict your comments to my question - I want all your wisdom!
Huge thanks for reading all this and any contributions
Chris
Re-post
perhaps you would get more of a response if you made this a bit shorter, and re-posted on ubuntu.stackexchange.com, android.stackexchange.com, and programmers.stackexchange.com
Also, perhaps a little off topic, but have you considered using coffeescript? :cyclops:
Thought it might be a stackoverflow question, this forum is amazing for tablet OS dev though. As ever I blather on too much...people have complained in the past.
All three? Wouldn't that be bad netiquette?
That's kind of a tricky question because technology is always evolving and prices fluctuate so much that in a year you might be able to get a device for half the price. I'm not knowledgeable about the new Ubuntu options but if your gut says go Ubuntu, than do it.
Thanks, I'd love to say gut instinct served me well, and I'm all for intuition, but I wouldn't trust it enough to dedicate 6 months of development on its hunch. However these replies and the act of writing the question has crystallized my view a little so I now have more targeted questions.
found this excellent guide on the hassles of porting an OS to a new device...
http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Porting-Android-to-a-new-device/
and this
http://stackoverflow.com/questions/...droid-kernel-porting-from-one-device-to-other
So looks like a month, best case, with expert developers and a device well-known for being hackable. So to port ubuntu to a $40 device, I'm thinking three+ months, plenty of risk, and much pain.
Some other interesting posts:
A little gritty detail on porting kernels: http://stackoverflow.com/questions/...droid-kernel-porting-from-one-device-to-other
A tutorial on building (compiling, not developing) a kernel: http://forum.xda-developers.com/showthread.php?t=2110842
The best post I found on porting ROMS: http://forum.xda-developers.com/showthread.php?t=1941239
Porting modules from within kernels: http://forum.xda-developers.com/showthread.php?t=1751966
Porting cyogenmod, (a ROM, not a Mod, as anyone on this forum probably knows): http://forum.cyanogenmod.org/topic/15492-general-cyanogenmod-porting-discussion/
A new kernel developer: http://forum.xda-developers.com/showthread.php?t=2173411
A vocab for noobs like me: http://www.talkandroid.com/guides/beginner/android-rom-and-rooting-dictionary-for-beginners/
I was wrong. Ubuntu Touch is based on the CyanogenMod kernel, which is widely ported.
From Canonical's FAQ on the bits of CyanogenMod used: "The kernel and a few low level drivers for network, video, audio and some other hardware features are taken, all the higher level parts have been taken out. On top of this the whole Ubuntu is started in an chroot environment." ( https://wiki.ubuntu.com/Touch/FAQ#How_is_Ubuntu_Touch_connected_to_Android.3F)
As a result it has already been ported to about 40 devices, and porting to a further 30 is work in progress, listed here: https://wiki.ubuntu.com/Touch/Devices
CyanogenMod officially supports 172 devices, and unofficially supports another 59.
Officially supported devices: http://wiki.cyanogenmod.org/w/Devices
Unofficially supported devices: http://wiki.cyanogenmod.org/w/Unofficial_Ports
Hello all,
This is most probably a silly question, but as I watch my Playstation 3 age and slowly grow irrelevant (debatable with bluray and whatnot), I was curious as to the possibilities of developing android compatible with its cell-processor architecture. Considering it is capable of having linux operating systems installed, I would not think that Android would be too far of a step from that. Anyway what would be the biggest hurdles and what would the limitations of such an operating system on this platform have? Thanks for your time!
Daxiongmao87 said:
Hello all,
This is most probably a silly question, but as I watch my Playstation 3 age and slowly grow irrelevant (debatable with bluray and whatnot), I was curious as to the possibilities of developing android compatible with its cell-processor architecture. Considering it is capable of having linux operating systems installed, I would not think that Android would be too far of a step from that. Anyway what would be the biggest hurdles and what would the limitations of such an operating system on this platform have? Thanks for your time!
Click to expand...
Click to collapse
I think it's not possible.. Yet..
Different architecture...
It might be possible but I am guessing it would take ages to understand the difference in the ps3's architecture, let alone start developing for it.
im pretty sure it wont be worth it though, since tons of time would have to be devoted to such a project, that in the end of the day might not even have any benefits.
Well, I had this idea 2 days ago, and I've given it a lot of thought. I want to rip apart AOSP and rebuild it using python and elf binaries instead of making everything in Java and making a decision file so it seems faster and more responsive... I want to rip out the Dalvik JVM, rip out everything pretty much, port the latest python, as well as the 2.7.x legacy python interpreters to Android and build an interface for loading python compiled or uncompiled(well JIT compile it whenever the md5 hash changes of the installed package, and also add support for pure elf binaries as packaged apps for the heavy lifting and performance, and rebuild from as little code from AOSP as possible a whole phone system, with lighter apps and any apps really done in python, and give the option for the binaries for high performance and multithreaded apps. We'll be using FOSS products modified to suit our needs, and building everything phone related that we can't use with an open license in python. So essentially rewriting every system and user app, from scratch in python, and of course we can optimize with C libraries and for that extra performance boost I'll edit the libs if I feel it's worth it with asm optimization. Call me a masochist but I love finding uses for my asm skills. I'm a noob to Android specific development but have a good working of using Linux(I've been using it 20 years although I've only gotten good with it in the past few years. I've been coding for 25 years, 13+ of those were spent learning assembly and os development. I've written functional minimalist kernels for hobby projects in pure asm, both x86 and arm, although I'll admit I'm less practiced on the arm instruction sets. So, python and native binaries as apps instead of Dalvik Java, and an entire interface in these 2 options from the system UI to the dialer to the calculator... Etc... Most of the basic app set will be python based in my vision of how this will work, and the developers can use c or c++ or anything I port a compiler for or write one for, and a set of python libraries that are C based and also matching libs for the libc component, probably based mostly on the same code for both C and Python. I feel like supporting python will result in more app developers wanting to write for our marketplace because most coders I know agree with me that writing code in python is better for rapid deployment as well as being less of a pain to implement. So app market fills up faster, more app developers, high performance native elf binaries, and a completely new design offering competing features against Android and iOS. We will have to rewrite everything from the system UI to the typical basic user apps. I'm guessing I will take me between 6 and 8 months to get the OS to a point where it's ready for app developer to start working on the core apps, then when that's done we can release a beta that also serves as a developer preview build for people to populate a marketplace before the OS goes into a public beta phase, by which point the developer preview users should have some non-essential apps to add appeal to the OS. I don't want this to end like Symbian where you have a superior OS and no apps and no device support beyond a few crummy phones from one maker. I'm looking for input on what people think of this idea. We will still be bound by AOSP licenses unless I go crazy and go overkill replacing everything from top to bottom. I can write Android drivers, I can port the toolchains and interprter, and I can make some of the apps, but once the core of the OS is finished and the HAL is available to all our supported languages, I'm going to need app developers to help me because writing a huge complete and quality OS release by myself would take many years. If you have any comments or criticism or advice or anything to say about this new project please post it or message me. Right now I'm collecting e-mailed addresses or other contact info for people interested in app development. I have 6 people so far who want to help but a 7 man team can't build Rome in a day so I'm going to need support from others to make this happen in a reasonable time frame with a completive selection of useful apps.
I'd like to create a superior alternative to Android and do it in a way that will encourage it to be adopted by people and hopefully even device manufactures will pick it up once the project matures and be shipping phones with it as the stock ROM/OS. For now I'm in the research/hacking phase, as I only started about 36 hours ago and have only been working with Android as developers for a couple months, but I feel confident I can do this if the right people help out, and I feel like Android has gotten too bloated and people are just using it because it's better than iOS, but in reality iOS provides competing performance on far less powerful system specs, which I think we can achieve if this is done right. Which would put a normal 4-8 core Android phones performance off the charts in comparison. I have Nexus 5, a Galaxy S5 Neo, a Galaxy Grand Prime, and I'm going to order some more phones when I get paid so I have more devices to mess with and do kernels/driver developers for. I think at first though we start with a stripped down AOSP that boots and gives debugging and and other logs, both on screen and via ADB logcat, so that we have a debloated core system to build on top of, which is what I worked on for the past 36 hours straight. Now it's time for rest but I thought before I get the sleep I missed while working on this I would make a post here and see what other people think of the idea. If we package source and the core OS has the toolchains to build for the device being installed to, we can avoid the whole thing that Android does with binaries where they package every architecture into an apk and let the installer chose the one to use. I want this OS to be easy on RAM, CPU time, and as a result have much better battery life. So... 6-8 months is the timeframe I've given myself to make platform developers can build on, but it could be more or less depending on how I exactly do everything and what FOSS stuff I use compred to how much I build myself. I am a minimalist programmer who thinks that programmer today just use tools and code that is easy to write and less time consuming because they know most people have resources to waste, but I don't want a shred of bloat in this thing, and I want it to offer every useful feature Android+g-apps offers before rolling out the developer preview. I figure if I can find another 30-40 devs, the project could be ready to roll out as stable v1.0 in 2.5 to 3 years, and I feel like we could negotiate with IP creators to license their stuff for a cut of device licenses for manufactures using the system. It wouldn't be much money per device but if we can take large chunk of Android's market share the revenue could be significant. Maybe this is all a pipe dream but I want to do it both for myself and for the people who would want to use it, and the potential for profit isn't a bad thing to consider although there's no guarantee we'll make a single penny in the end. Since I was 7 years old and exploring the world of coding, I dreamed of doing OS development, and I realized this project has much better chance of being adopted than my homebrew x86_64 OS I've spent the last 6 years working on, so I've dropped that project and will be working on this 16-18 hours a day since my hobby is OS development and I love to take on challenges that force me to learn, adapt, and become better at what I already do and love which is coding. Sorry this has turned into a big rant but I'm done now. Any feedback positive, negative, or suggestions to modify my idea to improve what we end up with, will be greatly appreciated. You can even call me an idiot or moron but all the people who've told me I can't do things with Android have so far been proven wrong and labeled as pleb coders who think because no one else can do it, I can't... And I don't give up when I commit to something like this. The guys who said I couldn't make a Exynos/MALI 200 driver set for my custom kernels and ridiculed me for even trying were proved wrong in under 4 hours with my PoC kernel, which now has full hardware support. They said it was impossible to support undocumented hardware, they said I couldn't even make a ROM for it, and I'm beta testing the ROM I made right now as I type this post out. They said I couldn't do a lot of things and all it did was make me work faster so they looked worse for being naysayer. I am going to buy a bunch of phones for development with a variety of different hardware configurations, and I'm going to have this running on all of them eventually just to stick it to those pleb Android "hackers" who mocked me for setting lofty goals. I got into this because when I started looking around at how people do these things I instantly knew my years of coding and hacking and just messing with things to learn more about them would make me a great ROM Dev, the it quickly progressed and I got into modding AOSP, modding the kernel I based mine off of, and then when I was in my Brazilian Jiu-Jitsu class my mind wandered from the lesson just long enough to conceive this idea before I got choked out for not paying attention.
So yeah, again. need input, need other people's ideas to add to my own, need to know if there is enough support from the community to have a full set of apps plus more in a market place in a matter of a few years. I have too many ideas at this point and I can't use them all because some of them are incompatible with other ideas I have... But work has begun and I look forward to any comments or criticism, or mocking that will encourage me to prove more people wrong. Anything you got to say, speak your mind I won't hold it against you, I might even respect your input and adopt your idea(s) instead of my own if it/they are better than what I've been brInstorming since the conception of this project 2 days ago.
Sent from my prototype Galaxy S5 Neo ROM(work in progress)
Wow - that's a mouthful, eh?
Hi, I'm an Electrical Engineering Student going into my third year of Engineering. After taking my first Digital Processing class I fell in love with hardware and software. My friend who's a mechanical engineering student in the same year and I created a company and by using community fundraising, we've finally made enough money to start thinking of actually embarking on a large enough quest. Here's the thing - you've probably understood where I'm going with this so without further ado - We want to create a smartphone. We are a team of around 7 engineering and computer science students wanting to create an android smartphone who have not the slightest clue on where to start.
There is a whole slew of things I could be looking for from you guys and I'd greatly appreciate if you all could help me out. I have only once owned an Android device and it was running Android 4.0 when I had it - ever since then I had switched to iPhone (not because it was superior but rather because it was the more financially viable option since I was a software developer and making apps on the App Store generally generated more revenue than apps on the Play Store) therefore I am very VERY noob in terms of Android OS. That being said, here's a short list I came up with of things I think I may need but feel free to add suggestions if you choose to do so.
Information on the Android OS
Information on ROM creation
Information on picking parts
Information on manufacturing opportunities (i.e. factories that will custom produce a prototype or two for you)
Information on creating a Stock ROM for your device lineup
Information on finding the most absolutely stock version of Android (does that exist?)
Information on perhaps other projects in the same ideaspace
Information on how smaller companies such as OnePlus or Essential started to create their phones.
Information on languages I should know (I already know a lot of languages but perhaps there's something more lower level than I need to know?)
Overall, thanks for reading this post and I hope to see replies soon!
Best Regards!
RoyalKingMomo said:
Wow - that's a mouthful, eh?
Hi, I'm an Electrical Engineering Student going into my third year of Engineering. After taking my first Digital Processing class I fell in love with hardware and software. My friend who's a mechanical engineering student in the same year and I created a company and by using community fundraising, we've finally made enough money to start thinking of actually embarking on a large enough quest. Here's the thing - you've probably understood where I'm going with this so without further ado - We want to create a smartphone. We are a team of around 7 engineering and computer science students wanting to create an android smartphone who have not the slightest clue on where to start.
There is a whole slew of things I could be looking for from you guys and I'd greatly appreciate if you all could help me out. I have only once owned an Android device and it was running Android 4.0 when I had it - ever since then I had switched to iPhone (not because it was superior but rather because it was the more financially viable option since I was a software developer and making apps on the App Store generally generated more revenue than apps on the Play Store) therefore I am very VERY noob in terms of Android OS. That being said, here's a short list I came up with of things I think I may need but feel free to add suggestions if you choose to do so.
Information on the Android OS
Information on ROM creation
Information on picking parts
Information on manufacturing opportunities (i.e. factories that will custom produce a prototype or two for you)
Information on creating a Stock ROM for your device lineup
Information on finding the most absolutely stock version of Android (does that exist?)
Information on perhaps other projects in the same ideaspace
Information on how smaller companies such as OnePlus or Essential started to create their phones.
Information on languages I should know (I already know a lot of languages but perhaps there's something more lower level than I need to know?)
Overall, thanks for reading this post and I hope to see replies soon!
Best Regards!
Click to expand...
Click to collapse
You need to start with exactly which hardware components you will put in the device. That is what will decide everything about how the software should be built.
As for figuring out hardware and design, you won't get much help here with that.
The majority of this community is everyday users, the rest are software developers and most of them are self taught non professionals. We deal with custom software development here. This forum won't do you any good until you have a working hardware design.
Sent from my SM-S903VL using Tapatalk