Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,807,128 Members 40,216 Now Online
XDA Developers Android and Mobile Development Forum

[Q] Older phone hardware and the FirefoxOS

Tip us?
 
gmaslin
Old
#1  
Junior Member - OP
Thanks Meter 0
Posts: 21
Join Date: Aug 2009
Default [Q] Older phone hardware and the FirefoxOS

With FirefoxOS being the only real open source platform, there is an undeniable attraction to test it on many older devices. I would like to compile a sticky thread of older phone hardware that lists attempts on these phones. A good start would be the cutoff of the following hardware:
Single CPU 400MHz
256MB RAM
4GB storage
WiFi
Does anyone know if there would be any other attributes that would exclude devices further?
 
Saijin_Naib
Old
#2  
Saijin_Naib's Avatar
Member
Thanks Meter 10
Posts: 43
Join Date: Jun 2014
Gmaslin, from what I understand, the "gonk" layer will require Android drivers from Android v4.x if I'm not mistaken.

I found the list of compatible Android driver versions at some point on the MDN documentation, but I've not stumbled across it again. If I find it, I'll link it here.
 
gmaslin
Old
#3  
Junior Member - OP
Thanks Meter 0
Posts: 21
Join Date: Aug 2009
Saijin_Naib
Hmmm. Does that mean the FirefoxOS makes specific calls to objects in the "gonk" layer that cannot be replaced/renamed? If so, that restriction might severely limit the list of candidates. I've found the biggest headaches with cooking ROMs are getting the drivers sorted out and playing nicely with each other. Any kind of hardware abstraction layer should help organize this process in theory but problems arise when the device in question has a fuzzy relationship to the layer calling it. That list from MDN will be a good starting point but it won't be comprehensive if this thread has anything to do with it.
 
Saijin_Naib
Old
#4  
Saijin_Naib's Avatar
Member
Thanks Meter 10
Posts: 43
Join Date: Jun 2014
Quote:
Originally Posted by gmaslin View Post
Saijin_Naib
Hmmm. Does that mean the FirefoxOS makes specific calls to objects in the "gonk" layer that cannot be replaced/renamed? If so, that restriction might severely limit the list of candidates. I've found the biggest headaches with cooking ROMs are getting the drivers sorted out and playing nicely with each other. Any kind of hardware abstraction layer should help organize this process in theory but problems arise when the device in question has a fuzzy relationship to the layer calling it. That list from MDN will be a good starting point but it won't be comprehensive if this thread has anything to do with it.
GMASLIN, sorry, I'm a complete and utter noob. My knowledge with FFXOS extends only so far as git/build/flash, and that all only happened in the past two weeks or so, haha.

https://developer.mozilla.org/en-US/..._prerequisites
"Important: Only devices running at least Android 4 (aka Ice Cream Sandwich) are supported. If your device is listed above but running an older version of Android, please update it before doing anything."

I've also heard rumblings that not having the up to date drivers can cause issues on newer versions of gecko/gaia, like what happens on the ZTE Open/Inari with current builds. Things like GPS, home button light, and hwcomposer break because the gonk bits are out of date, and ZTE has to provide them.
 
crobjam
Old
#5  
Junior Member
Thanks Meter 0
Posts: 19
Join Date: Sep 2013
Quote:
Originally Posted by Saijin_Naib View Post
GMASLIN, sorry, I'm a complete and utter noob. My knowledge with FFXOS extends only so far as git/build/flash, and that all only happened in the past two weeks or so, haha.

https://developer.mozilla.org/en-US/..._prerequisites
"Important: Only devices running at least Android 4 (aka Ice Cream Sandwich) are supported. If your device is listed above but running an older version of Android, please update it before doing anything."

I've also heard rumblings that not having the up to date drivers can cause issues on newer versions of gecko/gaia, like what happens on the ZTE Open/Inari with current builds. Things like GPS, home button light, and hwcomposer break because the gonk bits are out of date, and ZTE has to provide them.
Anything running Jellybean will run this?

Isn't this separate from Android?
 
djphrost1
Old
#6  
Junior Member
Thanks Meter 2
Posts: 11
Join Date: Nov 2010
Quote:
Originally Posted by crobjam View Post
Anything running Jellybean will run this?

Isn't this separate from Android?
I believe that it's seperate from Android OS, however JB identifies a hardware benchmark. Is it possible that a phone capable of running JB should be capable of running Firefox OS?
 
Saijin_Naib
Old
#7  
Saijin_Naib's Avatar
Member
Thanks Meter 10
Posts: 43
Join Date: Jun 2014
Quote:
Originally Posted by djphrost1 View Post
I believe that it's seperate from Android OS, however JB identifies a hardware benchmark. Is it possible that a phone capable of running JB should be capable of running Firefox OS?
FFXOS uses the Android hardware drivers and runs its own userspace stuff (if I read everything correctly).

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Schedule is up for xda:devcon ’14

With xda:devcon ’14 just around the corner, and the venue close to selling out, there is a lot … more

aLogcat Returns Thanks to XDA Love

The developers of Android, that is Google, gave users several great debugging tools that can be used in … more

And the Winners in the XDA Pebble Development Challenge Are…

Almost two months ago, we set out with Pebble to findthree amazing … more

MediaTek Releases Full Kernel Source for First Android One Devices

Those who might have thought that MediaTek wouldnever release working … more