The OEM has a flash tool and recent builds. You should flash that onto the device and then you can apply your custom build over it. It's good practice to always keep up with the vendor releases.
Andreas Sent from Mobile. On Nov 7, 2013, at 12:04, Kevin Simons <[email protected]> wrote: Hi Andreas, That sounds very much like what I'm seeing. I just received a device with the stock 1.0.1 image that Telenor is using in Serbia, did a config for Hamachi, built and flashed. Would you happen to know where can I get a proper base system to resolve these issues? Regards, --Kevin On Thu, Nov 7, 2013 at 11:26 AM, Andreas Gal <[email protected]> wrote: > What is the base system that was flashed on this device before? Trunk > needs recent drivers. The ICS chocolate drivers that hamachi shipped > with are no longer supported and cause texture locking issues, making > performance miserable. > > Andreas > > Sent from Mobile. > > > On Nov 7, 2013, at 11:20, "[email protected]" <[email protected]> wrote: > > > > First a bit of background: I've just recently begun looking into the > Firefox OS project, so I've not seen its evolution over the previous > months, am not that familiar with the differences between the versions, etc. > > > > Yesterday, I pulled the tip of master for B2G and built it for the > Hamachi (Alcatel) device. After the build, I'm left with a userdata.img and > a system.img file, but no boot.img (I guess related to the fact that the > drivers are proprietary). I booted into fastboot mode with the volume down > + power trick, ran flash.sh -f and the device flashed. > > > > Once it booted, the results were not promising. There was significant > tearing in the UI whenever I scrolled quickly and overall the framerate > felt quite choppy. This is in comparison to the Geeksphone Keon that I was > using previously. > > > > However, I saw a colleagues Hamachi running 1.0.1 and it's like it's a > totally different phone. No tearing, decent framerates. I also see in an > earlier email thread that the performance team from Mozilla is using > Hamachi as their main performance testing device and seeing good (50+ FPS) > framerates on things like scrolling. > > > > So my question is, where's the disconnect? What's the process the > Mozilla guys are using to build for Hamachi and are they using the tip of > master? Am I screwing up something with drivers, etc. that's leading to > this bad experience? > > > > Btw, I booted the device up today and thought I was losing my mind > because I didn't see the tearing, but after a few minutes of playing it > came back. > > _______________________________________________ > > dev-b2g mailing list > > [email protected] > > https://lists.mozilla.org/listinfo/dev-b2g > -- Kevin Simons --- Devices Tech Lead + (47) 99 27 12 74 | [email protected] | www.comoyo.com _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
