Jump to content

[ALPHA 2][B2G] Firefox OS 1.2 by Daredj


Guest daredj

Recommended Posts

I just forked dazz git repo (That's the reason that alpha1 doesn't contain any fix...)

 

Alpha2 will be from my own git repo, and I'll start to push all changes on it ;)

 

Please be patient, I'm still learning how to work with G300 (It has small diferences with galaxy ace, which was my previous rom devs :P)

 

PS: I'm thinking to make a recovery zip... but Until ALPHA stage, it would be better use fastboot...

Edited by daredj
Link to comment
Share on other sites

Guest Raquel Ferreira

I just forked dazz git repo (That's the reason that alpha1 doesn't contain any fix...)

 

Alpha2 will be from my own git repo, and I'll start to push all changes on it ;)

 

Please be patient, I'm still learning how to work with G300 (It has small diferences with galaxy ace, which was my previous rom devs :P)

 

PS: I'm thinking to make a recovery zip... but Until ALPHA stage, it would be better use fastboot...

 

but i dont know instal by fastboot :p

Link to comment
Share on other sites

Well, I have git repo now, you can check it on 1st message

 

Due to some outdates in Dazz sources, i decided fork from main repo (mozilla), now I'm adding all stuff for our device, please be patient ;)

 

Greetings

Link to comment
Share on other sites

Well, I have git repo now, you can check it on 1st message

 

Due to some outdates in Dazz sources, i decided fork from main repo (mozilla), now I'm adding all stuff for our device, please be patient ;)

 

Greetings

nice :)

I'm diving into this after I finished my current project.

(This will be my first time with B2G and Android development so I have not much expectation to able to move this project forward, but I'll try my best ;) )

Link to comment
Share on other sites

back button does not work,No Chinese

 

Back and menu buttons are not supported on FirefoxOS

 

Check what's working, i said languajes supported on alpha1 are less... in next build i'l add support for all languajes

Link to comment
Share on other sites

Alpha2 is out, check changelog and firsts posts

 

Greetings!

Glad to know you're working on it, it's a good OS. Which branch are you using?

 

Never mind, just looked at the manifest.

Edited by celrau
Link to comment
Share on other sites

 

firefox-os.png

Welcome to the Non-Android Zone!

 

 

DISCLAIMER:

Alpha Stage: USE AT YOUR OWN RISK!!!

 

Your warranty will be void if you proceed on this instalation

Anyway, all goes at your own risk, We are not a technical service, if you brick your phone we can advise you, but we don't take care of any unexpected result (EX: bricked phones).

 

Information:

This is the beggining of the Firefox OS for our Huawei ascend G300.

I started to compile using Dazz sources, and here I'll try to publish new versions and fixes as fast as I can.

 

For "noobs": Firefox OS is a new Operative System for some devices. It's 100% Open Source and that allow us to get our own version running on our device.

More information about Firefox OS: http://www.mozilla.org/en-US/firefox/os/

 

Screenshots:

attachicon.gif2013-12-02-10-18-44.pngattachicon.gif2013-12-02-10-18-54.png

attachicon.gif2013-12-02-10-19-31.pngattachicon.gif2013-12-02-10-20-09.png

attachicon.gif2013-12-02-10-20-21.pngattachicon.gif2013-12-02-10-20-41.png

attachicon.gif2013-12-02-10-25-06.pngattachicon.gif2013-12-02-10-25-59.png

 

Current Stage: Alpha 2

 

Not Working:

  • Camera
  • USB Storage
  • HQ Youtube videos
  • USB internet.
  • Radio FM

 

Working:

  • Languajes: ALL SUPPORTED
  • Everthing else :P

 

Not Tested:

- Audio recording

- Video Playing (due to same camera issue)

- mms (thanks Raquel ;) )

 

Instructions:

  • It requires Android 4+ installed (I recomend ICS due stability), With USB debug mode enabled.
  • Do ALL WIPES AND FORMAT ALL DATA (SD card not obligatory)
  • enter your device in fasboot mode (turn off your mobile, press and hold VOL- & Power during 15 seconds, after thar release the keys).
  • Plug your device to your PC.
  • Flash vía fastboot the 3 images:

example:

fastboot system system.img
fastboot boot boot.img
fastboot userdata userdata.img

After that, just restart your device:

fastboot reboot

DOWLOAD:

 

Alpha 2 CLICK HERE

 

Alpha 1 CLICK HERE

 

SOURCE:

 

B2G: https://github.com/cristomc/B2G

Manifest: https://github.com/cristomc/b2g-manifest

Device: https://github.com/cristomc/android_device_huawei_u8815

Propietary: https://github.com/cristomc/proprietary_vendor_huawei

 

CREDITS & Thanks to:

Dazz: Main git repo and base sources. 90% of credits for him

NOTE: Please ask for make derivated sources... If you do it mention Our Work (Dazzo and mine), I'm doing this for learning-

I'm not winning $$ for doing this... but if you want, you can click on the next link and help me to buy a beer during compilations :)

Give a donation (thank you in advance :) )

 

Please correct the fastboot command to 'fastboot flash <whatever>'

Link to comment
Share on other sites

I think that alpha1 was smoother than this alpha2... Correct me if i am wrong :)

That's why i didn't used DPI correction on first Alpha, but it seems that it's FxOS problem ATM...

Link to comment
Share on other sites

Here you are a logcat for big problem: scaling UI

 

something that i noticed, is that camera app doesn't fit preview with g300 resolution, and maybe it's the same problem for HQ youtube videos.

 

A "quick" solution is force the resolution in each app, but it should be a global fix for that

 

 

http://logcat.scheffsblend.com/view?id=929002

 

I need some help here... any ideas?

Link to comment
Share on other sites

Here you are a logcat for big problem: scaling UI

 

something that i noticed, is that camera app doesn't fit preview with g300 resolution, and maybe it's the same problem for HQ youtube videos.

 

A "quick" solution is force the resolution in each app, but it should be a global fix for that

 

 

http://logcat.scheffsblend.com/view?id=929002

 

I need some help here... any ideas?

Maybe this can help: https://bugzilla.mozilla.org/show_bug.cgi?id=888121

Or this: https://bugzilla.mozilla.org/show_bug.cgi?id=874295

What kernel do you use in this project, the 3.0.8 or the 3.4?

Don't you want to work on FFOS 1.3 instead of 1.2?

Edited by rhen
Link to comment
Share on other sites

Maybe this can help: https://bugzilla.mozilla.org/show_bug.cgi?id=888121

Or this: https://bugzilla.mozilla.org/show_bug.cgi?id=874295

What kernel do you use in this project, the 3.0.8 or the 3.4?

Don't you want to work on FFOS 1.3 instead of 1.2?

 

I'm using 3.0.x ... maybe it's time to use 3.4 but i wasn't too sure of the change, maybe next build will include it

 

due 1.2 it's "stable" now, I prefeer make it work al 100%, but let's see what happen with this bug...

Link to comment
Share on other sites

I'm using 3.0.x ... maybe it's time to use 3.4 but i wasn't too sure of the change, maybe next build will include it

 

due 1.2 it's "stable" now, I prefeer make it work al 100%, but let's see what happen with this bug...

Can you make the kernel to report proper screen width and height?

Maybe Daz can help you with. Since 160DPI is a fallback when the kernel doesn't provide this info.

Link to comment
Share on other sites

Can you make the kernel to report proper screen width and height?

Maybe Daz can help you with. Since 160DPI is a fallback when the kernel doesn't provide this info.

 

Yes i just read that.

 

Maybe 3.4 has that problem fixed, i'll try to compile with that kernel, if bug persist, we must modify that in the kernel

Link to comment
Share on other sites

You might get into other problems switching kernels, my advice is to modify the kernel if hardcoding the DPI in nsWindow.cpp isn't sufficient.

I don't know how camera gets the screen size for preview but I'm wondering if you couldn't hardcode some width x height dimensions in camere.js  to  see if that makes any difference. I'd also post on b2g forum the logcat and ask for some clues.

Link to comment
Share on other sites

You might get into other problems switching kernels, my advice is to modify the kernel if hardcoding the DPI in nsWindow.cpp isn't sufficient.

I don't know how camera gets the screen size for preview but I'm wondering if you couldn't hardcode some width x height dimensions in camere.js  to  see if that makes any difference. I'd also post on b2g forum the logcat and ask for some clues.

Where is this forum? I would like to take a look at it. :)
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.