El viernes, 7 de febrero de 2014 08:51:28 UTC-6, pazos escribió:
@Daniel: Did you read any of my posts here?
I resume:
- bootloader changed between 1.0 1.1
- bootloader checks for kernel signature (rebooting if it does NOT
match)
- kernel is
On Friday, February 7, 2014 7:51:28 PM UTC+5, pazos wrote:
@Daniel: Did you read any of my posts here?
I resume:
- bootloader changed between 1.0 1.1
- bootloader checks for kernel signature (rebooting if it does NOT
match)
- kernel is inside
@Daniel: Did you read any of my posts here?
I resume:
- bootloader changed between 1.0 1.1
- bootloader checks for kernel signature (rebooting if it does NOT
match)
- kernel is inside boot.img and boot.img changes too between 1.0 1.1
- now, the only way
Hi Daniel:
I was looking on your site GitHub you're having problems with the Bug #965180.
My question is Is there the same problem in the latest build of version 1.3? Is
that I got this file[1] and want to upgrade my ZTE.
Thanks
[1]
El jueves, 6 de febrero de 2014 14:28:01 UTC-5, Ernesto Acosta escribió:
Hi Daniel:
I was looking on your site GitHub you're having problems with the Bug
#965180. My question is Is there the same problem in the latest build of
version 1.3? Is that I got this file[1] and want to
Hey Daniel, in the compilations is available for 1.3 Is there any I can use?
Not if you have upgraded to the 1.1 ZTE firmware. The boot.img used in
the available download is based on the old 1.0 ZTE firmware, and I
can't seem to build a nightly (with or without the old custom
boot.img) that
On 6 Feb 2014, at 22:01, Daniel Roesler diaf...@gmail.com wrote:
Hey Daniel, in the compilations is available for 1.3 Is there any I can use?
Not if you have upgraded to the 1.1 ZTE firmware. The boot.img used in
the available download is based on the old 1.0 ZTE firmware, and I
can't seem
I have been trying for the past few days to compile using the new ZTE 1.1
release as the backup-inari reference folder. However, I am running across the
same boot loop issue that everyone else seems to be facing[1].
I have opened a Bug #965180 to track this reboot loop issue. Until it gets
Hi Daniel. I asume that you have version 1.0.1 installed on your phone. You'll
need to upgrade it via ZTE upgrade *before* install new builds with other blobs.
Some partitions are upgraded by ZTE upgrades but not via ./flash.sh (like the
bootloader or the modem firmware, and you need to have
ZTE says that info is confidential, I'm not going to buy another ZTE in the
rest of my life (I hope everybody think the same)
I think so too , I am currently running my custom build of firefox os
on the Open. In my case I had to downgrade to the older-firmware with
clockworkmod and
then flash
rant
I'm not disappointed at all in ZTE. This phone is dirt cheap, so what
can you expect for support? For $80, I definitely expected to be
hacking constantly to get it working.
The one I am very disappointed in is Mozilla.
The ZTE Open is their flagship phone and there are many more of them
out
On Wednesday, January 29, 2014 6:56:17 PM UTC+2, Daniel Roesler wrote:
rant
I'm not disappointed at all in ZTE. This phone is dirt cheap, so what
can you expect for support? For $80, I definitely expected to be
hacking constantly to get it working.
The one I am very disappointed
@Daniel: Mozilla has no control over the bootloader, the kernel, the radio
firmware, because its not part of B2G. IMO Its not mozilla's fault but provider
fault. ZTE does not complain with any opensource licenses at all.
I'm currently mergin some geeksphone init scripts to device-inari tree in
What I don't understand:
Mozilla has so much to lose from a bad ZTE Open experience. It is
their flagship device! It's the _only_ native Firefox OS device you
can buy now, and it's extremely cheap so developers can easily try
Firefox OS out.
I'd guess that there's an order of magnitude more app
link to version 1.2 based on 1.0.1 from ZTE http://ul.to/zsta3kfw
link to version 1.2 based on 1.1.0 from ZTE http://ul.to/2jwkruhj
Both built by me, installable through fastboot or cwm recovery. If you look
inside the zip you'll found a lot of zte crap files that explain why are NOT
On Wednesday, January 29, 2014 10:08:55 PM UTC+2, Daniel Roesler wrote:
Finally, not having control over the kernel/firmware never stopped
anyone from figuring out how to make it work. Android modders have
been dealing with that crap for years, and they still keep cranking
out upgrades
Mozilla cannot, and in some cases even ZTE cannot. The mods on XDA are
almost all violating various copyrights.
The entire mobile SOC ecosystem is built on binary blobs and
propreitary binary kernel modules. The blobs are there to feed and
bootstrap the SOC's devices, the blob itself is the
Le 29/01/2014 21:08, Daniel Roesler a écrit :
What I don't understand:
Mozilla has so much to lose from a bad ZTE Open experience. It is
their flagship device! It's the _only_ native Firefox OS device you
can buy now, and it's extremely cheap so developers can easily try
Firefox OS out.
Yep, on it.
On Jan 21, 2014 7:05 AM, joui1...@gmail.com wrote:
Hi Daniel! Can you make these builds flashable on the new 1.1.0b2 update
for the Zte Open?
Thank you! great work!
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
Le 03/01/2014 21:47, an a écrit :
How about, for the sake of sanity, rename any upgrade path for this device to
zte_open?
Everything else is just technical details, really. I mean zte open has been a
total failure from the user/developer perspective maybe it's time for some
sanity.
This
Ack, this sounds complicated. I’m not sure how best to communicate this.
So the ZTE OPEN eBay devices are ikura, and the other ones are inari, or have I
got that wrong? I’ve mainly written the MDN ZTE page from the point of view of
the eBay devices, so perhaps I should add a section about
AFAIK all ZTE Open are Ikura.
But I just learnt like you that the ebay and Movistar devices are
different...
Le 06/01/2014 11:00, Chris Mills a écrit :
Ack, this sounds complicated. I’m not sure how best to communicate this.
So the ZTE OPEN eBay devices are ikura, and the other ones are
On Monday, January 6, 2014 12:00:48 PM UTC+2, Chris Mills wrote:
Ack, this sounds complicated. I’m not sure how best to communicate this.
So the ZTE OPEN eBay devices are ikura, and the other ones are inari, or have
I got that wrong? I’ve mainly written the MDN ZTE page from the point of
Le 04/01/2014 06:01, Daniel Roesler a écrit :
Howdy Alexandre,
I'm getting a make: *** No rule to make target
`gecko-update-fota-full'. Stop. error when I try to run ./build.sh
gecko-update-fota-full. Is there something else I should be doing?
Did you take and applied the patches ?
On
The thing there is that the *config setting* is correct, inari there
works for both the actual inari (testing) devices and the ZTE Open
(ikura). The generated builds only work on one of them, though, based on
what device your backed-up /system files come from.
KaiRo
Chris Mills schrieb:
Hi
Thanks a lot Daniel.
I can't test this now (I don't have my ZTE) but if this works you did
really better than what we had before ;)
Would love to see the blob download part integrated into our own build
system.
Le 03/01/2014 04:58, Daniel Roesler a écrit :
All,
I've updated the repo[1] so
Thanks!
I'm still looking for some documentation on how to create update.zip file.
Has anyone been able to do that?
I think those might be easier for people to use than the flash.sh method
since you wouldn't need to set up adb in your computer (you'd just need to
copy the update.zip file to your
Le 03/01/2014 13:41, Daniel Roesler a écrit :
Thanks!
I'm still looking for some documentation on how to create update.zip file.
Has anyone been able to do that?
Are you referring to https://bugzilla.mozilla.org/show_bug.cgi?id=935059 ?
We already have some tools available that are used by
Hi Daniel,
I'm still looking for some documentation on how to create update.zip
file.
Has anyone been able to do that?
besides the bug mentioned by Alexandre we have the existing
functionality documented here:
https://wiki.mozilla.org/B2G/Updating
Gabriele
How about, for the sake of sanity, rename any upgrade path for this device to
zte_open?
Everything else is just technical details, really. I mean zte open has been a
total failure from the user/developer perspective maybe it's time for some
sanity.
This is no criticism towards someone in
On Fri, Jan 3, 2014 at 11:55 AM, Gabriele Svelto gsve...@mozilla.com wrote:
Hi Daniel,
I'm still looking for some documentation on how to create update.zip file.
Has anyone been able to do that?
besides the bug mentioned by Alexandre we have the existing functionality
documented here:
Howdy Alexandre,
I'm getting a make: *** No rule to make target
`gecko-update-fota-full'. Stop. error when I try to run ./build.sh
gecko-update-fota-full. Is there something else I should be doing?
On Fri, Jan 3, 2014 at 6:53 AM, Alexandre Lissy ali...@mozilla.com wrote:
Le 03/01/2014 13:41,
Hi guys,
Feel free to pass corrections to me to implement, if needed. I wrote the
current docs as they are because I was told the ZTE Open would work with Inari
B2G builds. Let me know what is wrong and needs updating.
cheers,
Chris Mills
Senior tech writer || Mozilla
developer.mozilla.org
All,
I've updated the repo[1] so that it downloads the binary backup for
the nightly build from ZTE's website (so there's no issue of copyright
in the repo).
[1] - https://github.com/diafygi/b2g_inari_nightly/commit/488d759
Happy New Year!
Daniel Roesler
On Thu, Jan 2, 2014 at 5:12 AM, Chris
Daniel Roesler schrieb:
I finally got around to making a nightly build script for the ZTE
Open. I've only tested these my US version of the ZTE Open (updated to
Version 02 before flashing), so I don't know if they work on the UK
version of the ZTE Open.
1) How are you able to distribute the
On Sun, Dec 29, 2013 at 7:24 AM, Robert Kaiser ka...@kairo.at wrote:
Daniel Roesler schrieb:
I finally got around to making a nightly build script for the ZTE
Open. I've only tested these my US version of the ZTE Open (updated to
Version 02 before flashing), so I don't know if they work on
2013/12/29 Daniel Roesler diaf...@gmail.com:
On Sun, Dec 29, 2013 at 7:24 AM, Robert Kaiser ka...@kairo.at wrote:
Daniel Roesler schrieb:
I finally got around to making a nightly build script for the ZTE
Open. I've only tested these my US version of the ZTE Open (updated to
Version 02 before
Le 29/12/2013 17:24, Daniel Dressler a écrit :
2013/12/29 Daniel Roesler diaf...@gmail.com:
On Sun, Dec 29, 2013 at 7:24 AM, Robert Kaiser ka...@kairo.at wrote:
Daniel Roesler schrieb:
I finally got around to making a nightly build script for the ZTE
Open. I've only tested these my US
This is the kind of comment (not contesting it's technical correctness) that
can ruin my holidays :) BTW when I build for zte open it's called full_inari.
So what's the point of tapping ourselves on the shoulder instead of no one.
On Sunday, December 29, 2013 3:24:40 PM UTC+2, Robert Kaiser
Daniel Roesler schrieb:
On Sun, Dec 29, 2013 at 7:24 AM, Robert Kaiser ka...@kairo.at wrote:
2) To prevent misunderstanding, please do not call them inari as that code
name is used for a slightly different (testing-only) device on which those
builds will not work correctly (just like the builds
So should the MDN page be changed to the correct config setting?
On Dec 29, 2013 4:04 PM, Robert Kaiser ka...@kairo.at wrote:
Daniel Roesler schrieb:
On Sun, Dec 29, 2013 at 7:24 AM, Robert Kaiser ka...@kairo.at wrote:
2) To prevent misunderstanding, please do not call them inari as that
You may want to make use of
https://bugzilla.mozilla.org/show_bug.cgi?id=935059 to provide FOTA
updates package.
Le 28/12/2013 19:25, Daniel Roesler a écrit :
Howdy all,
I finally got around to making a nightly build script for the ZTE
Open. I've only tested these my US version of the ZTE
42 matches
Mail list logo
