On 21/02/2015 20:02, Felix E. Klee wrote: > Aren’t the processors similar enough?
The issue isn't about the processors rather than the surrounding hardware. The Fire and Fire C use different SoCs and thus will need different kernels. > The device has been out for some time. So I’m not too optimistic. OTOH > Alcatel should be obligued to give me the part of the source that is > under the GPL. The Fire sources are available, and eventually the Fire C/E will be too. I suggest contacting them via their sourceforge contacts and requesting the sources; that should hopefully speed up the process. > Concerning kernel configuration, I just got a reply from the author of > the guide: “IIRC I got it from device itself. Pull /proc/config.gz from > the device, decompress it, rename to .config and run 'make oldconfig'.” I wasn't aware you could read /proc/config.gz on a non-rooted phone, that's a pretty big step ahead. You might try configuring for the 'flame' target which is a JB based build and use the kernel configuration pulled from the phone. That doesn't guarantee it will work though. > Wouldn’t really matter. The phone doesn’t allow root access, and that > makes it unusable for me already. For day-to-day use it’s unusable > because I cannot run [backups][1]. For development use it’s unusable > because I cannot flash firmware. I see your point. > Also, in step 4, one boots the phone with a custom kernel, but AFAICS > without actually installing it on the device. This seems quite safe to > do. That's true actually, I had no idea it was possible. It's a lot safer than reflashing your boot partition :) Gabriele
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
