Firefox OS 2.5 unstable on Flame


(shine) #21

I had base image V18D_nightly_V3 when I installed my build. I didn’t flash the latest build. I just renamed the ‘Update Channel’ in Developer Settings section. @Fjoerfoks said that’d be sufficient to switch channels. I guess not (?)


(Marcia) #22

Please update to the latest Base image (v4) - there are fixes in that image that may solve some of the other issues I have seen you mention.


(shine) #23

There’s just one issue - the OS is simulating unnecessary touch events.

A clean flash could rectify the issue for a while, but then again the issue would come back after a while.


(Gabriela) #24

Hace you flashed base image 18D v. 4 yet? You’ll keep having issues till you do!

Mozilla Discourse wrote:


shine

December 29marcia:

some of the other issues I have seen you mention

There's just one issue - the OS is simulating unnecessary touch events.

A clean flash could rectify the issue for a while, but then again the issue would come back after a while.


To respond, reply to this email or visit https://discourse.mozilla-community.org/t/firefox-os-2-5-unstable-on-flame/5694/23 in your browser.

To unsubscribe from these emails, visit your user preferences.

To stop receiving notifications about this particular topic, click here.

Sent Using Firefox OS

(shine) #25

I’m going to do that as a last resort. I have some SMS that I have to save. Is there some way to backup my SMS and apps?


(Gabriela) #26

Unfortunately I don’t know about backups, but what I do know is that the
update issue you have is because the OTA’s size is too big for the system
space. The new base image fixes that problem so you won’t be able to update
without issues till you flash it.

Best regards,
Gabriela
QA Mozilla Hispano Team Responsible


(Mihai Barbat) #27

There is no other way. Just update to V4 as instructed.


(shine) #28

You were right. The latest build (Build ID : 20151229030208) with the latest update from the nightly-latest channel still has the problem - which means that my phone is unusable now. :cry:

(at least I could use it as my primary device for a good 6-8 months). I should probably get a new Android device that has a port for Firefox OS and flash Firefox OS on it. :satisfied:


(shine) #29

Something that I noticed during updates - the update channel changes to nightly after installing a nightly-latest update. Is this normal? or do we have to update the update-channel every time we want to update?

PS : I’m just new to the nightly-latest channel. (I’ve always been on the nightly channel since I believed that it was the most stable update channel.)


(Mihai Barbat) #30

With the more recent versions you will have to set your “app.update.channel.backup” on the device using webide to the nightly channel you are using (nightly-latest) in order to keep it the same after you do an update.

See bug https://bugzilla.mozilla.org/show_bug.cgi?id=1217490 for details.


(Nhirata) #31

The FOTA is fingerprinted to the v4 version and will not work with the v3.

I am currently working on getting a FOTA for the base image the v5 build out so that it can be FOTAed manually or automatically if you have a build less than a certain other build.

We are hoping to get this out sometime in early January.


(shine) #32

I did a clean flash of v4 and then tried using the phone. The phone was unusable in the first place, let alone update.

I struggled (literally fought) with the phone to get the build ID.


(Nhirata) #33

If the v4 is showing issues, I believe that it’s not the software but the hardware.

I think there’s some sort of touch sensor that’s going off on the left middle side of the screen based on the video that I seen in the bug.


(shine) #34

Believe me, it’s all over the top side of the screen. And sometimes wherever the call button is.


(Asa Dotzler) #35

Shine, sounds like bad hardware. I can replace your Flame with a working one if you email me with your complete shipping information and phone number.


(shine) #36

For some reason, I didn’t get a notification either on discourse or via email for this response. Anyhow, I’ll drop in an email later today. Thanks Asa