You may have heard that Mozilla are building their own mobile OS based on Firefox. To put it simply, if you've heard of ChromeOS, then it'll work in a similar way; the browser IS the OS.
What's interesting for us is that it's heavily based on android. Basically they've kept the HAL, hacked out Dalvik and anything java, and replaced it with Gecko. In theory any device that runs Android can run FirefoxOS.
It's still alpha software, it's supposed to eventually be compatible with ARMv6 devices, but as I found out while trying to build it for my LG Optimus One, Gecko is still hardcoded in many places to ARMv7. Their test devices include the Galaxy Nexus and Galaxy SII, so special hardware isn't needed.
Therefore it should run fine on the Nexus 7 right?
Well, not quite. FirefoxOS is based on ICS, but Nexus 7 runs only Jellybean.
I've tried building with ICS sources and Jellybean sources, making the necessary changes to get it to build. However with Jellybean sources it doesn't get past the Google screen, and ADB loops without many error messages to analyse. With ICS sources ADB isn't even accessible, the kernel and/or the proprietary blobs are probably not compatible.
If anyone wants to take a look at my changes, they're at my github. Some of the changes to Gecko I got from this bug at Mozilla, but it's out of date and incomplete (there is a patch in the B2G repo).
Hopefully with more eyes looking at it, we'll get it working!
This seems very interesting...when do you think it will flashable for the 7, and will you be looking for testers?
Sent from my Nexus 7 using xda app-developers app
you will probably have to hack libs just to get it booting, you could try building ics first then after you have that running por tfirefox OS to it
I built it for the gnex but it was nowhere near usable, it has no onscreen button support which as we know is no good for us nexus users.
I reckon give it a few months before trying to do anything with it, its buggy and has no features as yet. The market is invitation only for registered developers, I couldn't get any signal on it even though they said that it was working. WiFi worked but not very well.
Sent from my GT-I9300 using xda premium
adfad666 said:
...FirefoxOS is based on ICS, but Nexus 7 runs only Jellybean.
Click to expand...
Click to collapse
There was at least 2 cases of people who received Nexus 7 hardware with some dev version of ICS on it. Not sure if anyone has had any luck with getting that version of ICS up for download though.
There is no home button, assets are the wrong size, some screen resolutions are incorrect, wifi doesn't seem to manage to connect, but it launches, and the UI is pretty buttery smooth
Click to expand...
Click to collapse
https://wiki.mozilla.org/B2G/Nexus7
see here
It's building I'm gonna upload it when it's finished. I also managed to map the volume keys to the home button since no softkeys will work.
That page was last updated January 29th, things have likely changed since then.
Sent from my Nexus 7 using xda app-developers app
I know that this thread is really old, but I think we should try to build because they got it working on the Nexus 7 2013 and it supports touch gestures for closing applications.
Maybe I'll do it some time but I have to learn how to build first with building Firefox OS for my Galaxy Nexus. Maybe someone with more knowledge could try to build. It would be great!
+1
What he said. Someone try this, Pliz
Related
Hi all,
First of all, I'm amazed and gobsmacked at how much work all the devs put into their respective ROM's, it's amazing the effort and hard work ppl put in. Passion is alive and well on XDA
Now, to business. I have my Galaxy SII, a Galaxy S, and an Acer Iconia A500. I've flashed them all with their respective ICS. I would think (and hope) that probably out of all of them, the SII has the biggest dev base and most power. The ICS ROMs for the A500 and S are almost perfect. They run completely vanilla with no or almost no bloat, they look and behave the same (icons for network activity inside the bars for example, contacts app looks the same) and have had no hiccups whatsoever.
Come the SII, the only ROMs I've seen are cooked from Samsung sources with their phone and contacts apps, they crash and reboot and if it weren't that I have gone past the point of no return in regard to effort I'd have gone back to Gingerbread days ago.
Is anyone out there developing a completely vanilla "Google" rom that isn't themed to look like ICS, but actually uses the ICS apps etc. I can't understand how the Iconia and SI can have this while the SII seemingly doesn't.
Can anyone open my eyes on this? I'd love to get something as stable onto my SII as I have with my other devices, ICS is brilliant to use on them...and barely bearable on my beloved SII.
Cheers
<:3)~
Ummmm correct me if I am wrong but that's exactly what the CM team are trying yo to do....
And you can already download and install that, so long as you are happy with the bugs at present.
Unless you meant something else???
Sent from my GT-I9100 using XDA App
You miss reading the cm9 thread. Check it out....its still alpha.
Sent from my GT-I9100 using Tapatalk
I'm more curious about the fact I would have thought the SII having a bigger user and dev base...certainly more than the A500 I thought it would have the most stable and mature code base - yet it seems the opposite is true.
I've been running 4.0.3 on my SI for weeks now and its never bugged out. Installed the A500...and Oh wow its like a brand new tablet!! I wonder is it because of Exynos or some other reason we can't have the same stability and performance right now.
Sent from my Acer Iconia A500 using Tapatalk
Your ignorance and disrespect is pretty bad (even if you don't mean it). I think you should do some reading for a while and get yourself acquainted with what's involved.
I didn't ask this to be dissed by someone...I'm sure even you would agree the development cycle and challenges for all three devices would be similar given they all use different processors. So is it easier to compile for the A8 and Tegra than the A9?
I have been looking and downloading a number of ROMs...and if someone has created a ROM in a similar vein to Thor's on the A500 and Onecosmic's on the SI, well I'd be grateful for the heads up...in fact I'm just about to download and test the Pure ROM I just spied over in dev...so see how that goes. Still I'd be happy for someones *constructive* input.
Of course I'm claiming ignorance...if I knew I wouldn't ask...geez lol
Sent from my Acer Iconia A500 using Tapatalk
It's a wonder no one bothers doing a straight AOSP compile for any device, really. CyanogenMod comes the closest. There are a few people who played with doing a straight AOSP, but they base it off CM's work and strip out the extras.
When I wanted the AOSP experience with Gapps, I installed CM7 on my SGS and installed the stock Gingerbread launcher. It was the closest I got.
Trebuchet is basically the stock ICS launcher with features added, so it won't be so bad. You can also replace it with the stock launcher as well.
Try Airbus 360s ics rom that's aosp and is fantastic he should be releasing beta 2 tonight.
sent from my iPhone 4S.
haha I bet that confused ya
You're question is a bit noob so don't expect much answers.
Here is a short one to sum it for you:
AOSP - Pure android base without modification.
CM - almost pure with modifications.
STOCK - Hardware Manufacturer (eg. Samsung's) "official originated" release.
Stock - can have it all. CAUSE - Samsung has sources and support/docs for ALL hardware API of the device.
CM/STOCK - While there are some changes BOTH use the same origin.
To sum it, for proper functionality BOTH use SAME kernel/libs base.
So if some hardware functionality broken in one it'll be broken in other =
If CM9 haz no h/w decoding === APPLIES for AOSP.
Another thing to keep in mind, CM9 currently is in the process of adding CM features so current builds are very close to AOSP with functionality.
SUM IT UP:
if (CM9 != working) AOSP.isNotWorking()!
ttg said:
if (CM9 != working) AOSP.isNotWorking()!
Click to expand...
Click to collapse
That's a piece of horrible code, dude
Hey Guys!!!
Ever heard of BOOT TO GECKO?!
Mozilla created Firefox, Seamonkey, Thunderbird, and now a smartphone operating system, known as Boot To Gecko, or Mozilla OS...
I am planning on working to port this amazing operating system to our smartphone, it will probably be a BIG project; which is another topic.
Is any developers here in our LG Optimus One area of XDA willing to work with me to get Boot To Gecko on our P500s? It would be amazing, even if it is on a linux/android based port (or themed ROM maybe... port itself is better)
So yeah
Also, I have not a lot of spare time during day between 9am-6pm because of work, so around nighttime I am free, so is on weekends...
I would love to see this on our phones, even sideloaded (multiboot) capability would be amazing, then we could have endless possibilities! I would have DoozzzedUIv4 and Mozilla B2G, and it would be amazing.
I would say good luck, but I'm the one to be working on it
CJ
8-year bump just for add information that may be relevant to anyone reading this post:
on B2G GitHub, there's a pull request for adding support for the P500 in the build process, so it should be compatible if someone compiles it.
Sent from my Galaxy S5 using XDA Labs
MLX said:
8-year bump just for add information that may be relevant to anyone reading this post:
on B2G GitHub, there's a pull request for adding support for the P500 in the build process, so it should be compatible if someone compiles it.
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
Man someone did all that work only for it to never see the light of day, its been so long that not only the phone died but the os too. Hard to believe that my 150 dollar phone is more than 16 times more powerful than this.
Fandroid Tech said:
Man someone did all that work only for it to never see the light of day, its been so long that not only the phone died but the os too. Hard to believe that my 150 dollar phone is more than 16 times more powerful than this.
Click to expand...
Click to collapse
Yeah, funny enough I have a LG P350 (not a p500), I would have tried to build it nowadays (just for the sake of trying) lol
MLX said:
Yeah, funny enough I have a LG P350 (not a p500), I would have tried to build it nowadays (just for the sake of trying) lol
Click to expand...
Click to collapse
I used to have an LG P500, the battery bloated a few years ago so I got rid of it thinking I wont miss it. Oh well that was a mistake. There is cyanogen os for the LG P350 so it would be easy to port firefox os overlay to the phone, it should run great as all the applications are minimalist. I am currantly trying to port Lineage 18.1 for my Samsung A11 but I am having issues with the camera, phone calls, etc. Android porting used to be so much more simpler back then, or I am just too unfamiliar with the new environment. The phone is armv6 so the maximum android version it can run without being extremely slow is android 4.4. I could get the lastest twrp version working but it would be useless on it. Postmarketos should run nicely on it.
Fandroid Tech said:
I used to have an LG P500, the battery bloated a few years ago so I got rid of it thinking I wont miss it. Oh well that was a mistake. There is cyanogen os for the LG P350 so it would be easy to port firefox os overlay to the phone, it should run great as all the applications are minimalist. I am currantly trying to port Lineage 18.1 for my Samsung A11 but I am having issues with the camera, phone calls, etc. Android porting used to be so much more simpler back then, or I am just too unfamiliar with the new environment. The phone is armv6 so the maximum android version it can run without being extremely slow is android 4.4. I could get the lastest twrp version working but it would be useless on it. Postmarketos should run nicely on it.
Click to expand...
Click to collapse
actually b2g can't be even built because of the repositories being down, while archives exist you need to patch the source to use the correct paths and that's something most people won't do to run an outdated os
btw I also got twrp3 on some armv6 devices, a nice but useless things indeed
Guys, I'm working on developing an AOSP ROM. I need your help in choosing a phone I can use for the testing. I was thinking of starting with a cheap Samsung Galaxy series phone since they have dual bootloaders (boot.bin and sbl.bin). Better safe than sorry, right? My work partner suggested we start off with a Vanilla Android phone, like an old LG. Can you guys recommend me one to proceed with? Is there a phone out there with Vanilla Google Android and possibly two bootloaders ?
Anyone?
c'mon guys !!
Most developers like the Nexus series phones since they are easy to unlock the bootloader and have a lot of other devs.
Thank you for replying But is the Samsung Galaxy series the only one in the Android universe with dual bootloaders?
Also, what phones run on Vanilla Android other than the Google Nexus series? I take it the old LGs do? If so, which ones?
Someone, please respond...
bump!
Someone please provide some input on this..
I REALLY gotta know this at the earliest so I can acquire the phone. Someone, please help out !!
not sure if this helps but the pantech burst is getting the ICS update shortly (they have it ready just having server issues trying to get it out today) its a cheep but badass att lte phone
I don't live in the USA. I need something available internationally. Also, it needs Vanilla Android. Is Google Nexus my only chance?
Prasad007 said:
I don't live in the USA. I need something available internationally. Also, it needs Vanilla Android. Is Google Nexus my only chance?
Click to expand...
Click to collapse
If your serious about development and testing pure vanilla Android is the way to go and the Google's Nexus line of phones and tablet it the way to go. You can easily compile AOSP for these devices, easily unlock the bootloader and root to flash custom ROM's. Also kernel sources are easily available, along with other great resources that will allow you to learn a lot about development.
shimp208 said:
If your serious about development and testing pure vanilla Android is the way to go and the Google's Nexus line of phones and tablet it the way to go. You can easily compile AOSP for these devices, easily unlock the bootloader and root to flash custom ROM's. Also kernel sources are easily available, along with other great resources that will allow you to learn a lot about development.
Click to expand...
Click to collapse
That's EXACTLY what I needed to hear! Thank you so much for your time! Considering I'll start with JB, is it necessary to acquire the latest Nexus available, or will any older variant do?
Prasad007 said:
That's EXACTLY what I needed to hear! Thank you so much for your time! Considering I'll start with JB, is it necessary to acquire the latest Nexus available, or will any older variant do?
Click to expand...
Click to collapse
I wouldn't go any lower then the nexus s, since that's the oldest pure Google device that officially supports compiling AOSP JB from source. Personally I'd pick up the galaxy nexus if you want something right now. If you can wait until around November (November 5th) it's rumored Google is launching several (Supposedly five new nexus devices) new nexus devices to celebrate androids 5th birthday :thumbup:
Sent from my SCH-I535 using xda premium
shimp208 said:
I wouldn't go any lower then the nexus s, since that's the oldest pure Google device that officially supports compiling AOSP JB from source. Personally I'd pick up the galaxy nexus if you want something right now. If you can wait until around November (November 5th) it's rumored Google is launching several (Supposedly five new nexus devices) new nexus devices to celebrate androids 5th birthday :thumbup:
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Good to know Guess I'll be picking up the Galaxy Nexus then!
I'm Chinese on mainland of China. Today I read a news about the so called "Android Window System ". First of all I just think it would be a ugly copycat of floating apps or something similar, but while I was watching the demo video I was totally shocked. It might be really a breakthrough for android tablet in my eyes. I don't know how many of you can read Chinese and can link to this video site due to China's Government Firewall, but if you can, you must have a look.
The news site : http://www.cnbeta.com/articles/244878.htm
The video site : http://v.youku.com/v_show/id_XNTgzMjAwNDMy.html?x
(there are three demo videos in the news, I post one of the video address here, you can find all the three in the last of the news. If anyone interested in helping me to post in YouTube, just contact me. )
Sent from my Nexus 10 using Tapatalk 4 Beta
Cool I want this
Sent from my SCH-I545 using xda premium
6 words: I want, I want, I want!
This better go open source...
Sent from my Nexus 10 using Tapatalk HD
This is no different than Samsung releasing their devices with multi-window.
What you've shown is a Rockchip's device running Rockchip's version of the Android OS on 4.2.2 with the multi-window UI implemented.
This is not Android 4.3, 5.0, 6.0, or 9.0.
Please do not spread misinformation! Do your research! It'd be nice to have but...
johno86 said:
This is no different than Samsung releasing their devices with multi-window.
What you've shown is a Rockchip's device running Rockchip's version of the Android OS on 4.2.2 with the multi-window UI implemented.
This is not Android 4.3, 5.0, 6.0, or 9.0.
Please do not spread misinformation! Do your research! It'd be nice to have but...
Click to expand...
Click to collapse
I didn't mention it is any official Android version. It's true that it is for Rockchip's devices and use Rockchip's own sdk. I just wanted to show you guys what these devices can actually do. Multiwindow may not be useful on phones, but I want it on my tablet, and I believe many nexus10 owners think the same.
Sent from my Nexus 10 using Tapatalk 4 Beta
I understand. I was just saying it's similar to what Samsung released with their multi-window. They already showed it can be done. Rockchip just did there's much better. N10 is capable of anything but unless someone that can do this, for free, it's just more eye-candy. Cornerstone was there but Google intervened, more or less, and we're back to square one. Devs can most definitely utilize cornerstone but they don't. Why is that? Google.
Cool, but not going to happen just yet.
auronm scorese
It is highly desirable that Google implemented in the next version of Android (4.3 or 5.0) MULTI management of native to their Nexus devices.
johno86 said:
I understand. I was just saying it's similar to what Samsung released with their multi-window. They already showed it can be done. Rockchip just did there's much better. N10 is capable of anything but unless someone that can do this, for free, it's just more eye-candy. Cornerstone was there but Google intervened, more or less, and we're back to square one. Devs can most definitely utilize cornerstone but they don't. Why is that? Google.
Cool, but not going to happen just yet.
Click to expand...
Click to collapse
Cornerstone was stopped by Google because it supposedly caused lots of issues
Sent from my Xperia Play (r800x)
I know they did. I said they intervened.
CM tried to but Google stopped them. It was mostly due to the integrity of app Window resizing.
Sent from my Nexus 10
Could seriously breathe new life into the tp seeing as how it's supposed to be built to run on lesser hardware.
Sent from my XT1058 using Tapatalk
Well, it did just come out. CM hasn't even started on it. Can't say I expect a build for at least a month, could be wrong though.
It doesn't run better on lesser hardware per se, just uses less RAM. I don't think we've really been having issues with memory, and we're still stuck with our slow Snapdragon S3.
With the amount of devs the TouchPad has, we are relying on just a handful of people to get 4.4 on it. I feel 4.3 barely made it to the TouchPad. I would love Kitkat on my beloved tablet but I hate to say that I have my doubts.
jsgraphicart said:
With the amount of devs the TouchPad has, we are relying on just a handful of people to get 4.4 on it. I feel 4.3 barely made it to the TouchPad. I would love Kitkat on my beloved tablet but I hate to say that I have my doubts.
Click to expand...
Click to collapse
I don't even think there's a doubt someone will do a build... But it's nice to know that we won't be limited by memory. Anyway, chalk this thread up to boredom. My moto x has almost nil going on so I'm hanging out in here
Sent from my TouchPad using Tapatalk
murso74 said:
I don't even think there's a doubt someone will do a build... But it's nice to know that we won't be limited by memory. Anyway, chalk this thread up to boredom. My moto x has almost nil going on so I'm hanging out in here
Sent from my TouchPad using Tapatalk
Click to expand...
Click to collapse
If someone does though, I just hope its as usable as it is currently. I have a Galaxy Nexus and I am already seeing bugs with ports to that device. Which isnt normal with a Nexus device. So the TouchPad may not be any better. Dont get me wrong, I really hope we see something though.
jsgraphicart said:
If someone does though, I just hope its as usable as it is currently. I have a Galaxy Nexus and I am already seeing bugs with ports to that device. Which isnt normal with a Nexus device. So the TouchPad may not be any better. Dont get me wrong, I really hope we see something though.
Click to expand...
Click to collapse
The galaxy nexus is a problematic device. First, google already said no-kitkat for the GN. Second, it's cpu and TI demise.
Your galaxy nexus is now on the list of abandoned nexus devices.
Now, regarding out tablet, first it's a qualcomm so we're not all alone on this one, but it's a very unsuported and old-unknown-binaries rom.
MAYBE someone figures out how to get the camera and bluetooth working. I keep my hopes high.
Not ready
I'm still having problems getting 4.3 settled on my TP. Too many issues (including repartitioning) still need to be solved first.
scy1192 said:
It doesn't run better on lesser hardware per se, just uses less RAM. I don't think we've really been having issues with memory, and we're still stuck with our slow Snapdragon S3.
Click to expand...
Click to collapse
I am positive that someone will be get Android 4.4 to work especially with the fact that it uses less RAM for running the applications. Usually XDA and Rootzwiki member drmarble helps at getting the initial work for the next version of Android to work. He helped get Android 4.3 (CM 10.1 and 10.2) to work on the Touchpad. And of course JCSullins will help with developing for Android 4.4.
I am sure ROM builders like Milaq and Shumash will provide CM 11 ROMs that are Android 4.4 based although I wouldn't expect to see a CM 11 ROM until January/February at the earliest and until the official CM 11 development has begun.
Android 4.4 launcher on my HP Touchpad.
Sent from my TouchPad using xda app-developers app
blmvxer said:
Android 4.4 launcher on my HP Touchpad.
Sent from my TouchPad using xda app-developers app
Click to expand...
Click to collapse
I tried that too. I dont know why the search bar is of to the left. Maybe its a DPI thing. But we havent seen a Nexus 10 with Kitkat yet. I'm looking forward to seeing what its like on that device.
Running Android 4.4 on my Nexus 7(2012) and I gotta say I love it, except the keyboard pops out every time you navigate to the home screen.
Sent from my AOSP on Grouper using xda app-developers app
Sent from my AOSP on Grouper using xda app-developers app
i just dont see this version becoming popular.
It seems to be more of the integration of other devices and their data harvesting than any user advantages.
Despite the name, and an actual marketing contract with nestle this time, i personally think they chose the right theme colour.
Because its going to be s**t
I see 4.4 more of a stepping stone into a much bigger change to the OS.
Sent from my AOSP on Grouper using xda app-developers app
There are a lot of good things under the hood in KitKat. It will be interesting to see if anyone manages to get it running, especially with ART. Too bad my TouchPad is moving on to another owner. Finally decided to pull the trigger on a 2013 Nexus 7 LTE.
Sent from my Nexus 7
KitKat is coming for the hp touchpad. Even have wifi working for me on the evervolv test build made by flintman
KitKat Pre Alpha Build from Flitnman
Time to start talking about Kitkat and the new ACMEInstaller4/5
Android 4.4 Kitkat Test Build Guide and Links:
[ROM] Evervolv | 4.0.0p1 [AOSP 4.4] [TEST] W/UMS support
Download 4.4 Kitkat Pre Alpha Gapps here:
Notes:Low to Medium battery drain(-4mA to -30mA) h/w video, Test Build Make a Backup!, Automated Updater and Installer, Audio plays with the screen off, Camera, No Bluetooth.
Note: Windows users may need to do the following in order to attach the Touchpad with the USB cable.
1. Go into Device manager. You will see "MTP USB Device" under portable devices.
2. Right Click it and select update driver software
3. Select Browse my computer for driver software.
4. Select Let me pick from a list of device drivers on my computer
5. Select USB Mass Storage Device then click next.
and/or
6.To transfer files to PC, turn on USB mass Storage from the USB connection notification on the Android device.
Note(Important): Backup and transfer all your SDcard files to PC. This is a testing build and could wipe files from your SDcard data.
[Note(Important): I would recommend increasing the size of your System Partition for this build. After my install I had 398/400MB free, so Flash the 512MB zip below or use Tailor to adjust the size.
Note(Important): This is an Android Open Source Project (AOSP) rom not a CyanogenMod (CM) rom. Dirty flashing an AOSP rom over a CM rom can causes errors and rebooting issues. Always do a clean install when moving from CM to AOSP and vise versa.
Flash through recovery to change the partition size to 512MB(Gradular&codycoyote)
Download 4.4 Kitkat Pre Alpha Gapps here:
Checkout iMark90's thread here:
I'm running kitkat and yeah its nice
Sent from my Touchpad using Tapatalk
have to be patient:fingers-crossed: