Originally Posted by baranovskiykonstantin

Hi!

First of all want say thank you all for your hard work!

I want to share the experience of the assembly system using these scripts.

Host system: Ubuntu 14.04 32bit.
Configuration files are left unchanged.

1. build_kernel.sh
Kernel build will fail (circular dependency between libphy and of_mdio).
Solved the problem with a patch.

Originally Posted by baranovskiykonstantin

2. install_debian.sh
The first installation of the system also failed. As it turned out the problem was established scratchbox. Later, repeated the installation on another computer using the same operating system without scretchbox, is making progress, but met another problem. To solve this problem need to disable automatic mounting of the card reader and mount the card manually.

Originally Posted by baranovskiykonstantin

3. configure_u-boot.sh
Here, everything went without problems.

Finally managed to run the system on N900

I hope it will help others avoid similar problems.

Originally Posted by sulu

Depending on your location some mirrors will be faster than others and some might even have an unstable connnection.

For example I come from Germany (Berlin region), so ftp.de.debian.org should be best in my case. But in fact ftp.cz.debian.org is usually faster and more stable for me.

So if you live closer to New York than to Indianapolis (that's where debian.org is registered) in terms of server hops, usually also but not necessarily geographically chosing the Columbia University mirror would make sense.

Originally Posted by saponga

EDIT: Its running now.

Originally Posted by Android_808

wicket: any updates lately?

Originally Posted by wicket

I've recently been thinking that maybe I need to change the direction of the project and evolve it into a full Linux distribution based on Debian (and/or Devuan). It's becoming less and less like Debian with the stuff that gets added to it (e.g. non-Debian kernel) and with the decisions I make about what packages should or shouldn't be included by default. My thoughts are that it currently needs to be bleeding-edge to deliver the best possible experience but the long term objective would be that many of the differences could eventually be merged back into Debian. My personal focus would still be for usability on the N900 and Neo900 but I would also like to look into getting libhybris running on it so that it will be usable on Jolla and supported Android devices.

Originally Posted by wicket

Raising funds would also enable me to buy a second N900

Originally Posted by DDark

I personally don't like the idea of bleeding-edge approach, but I like the idea of debian-based distro with voice-calls support.

Originally Posted by DDark

What about getting in touch with Neo900 team and obtain one of those Mozilla donated phones?

Originally Posted by sulu

I agree with DDark. You should get in contact with the Neo900 devs.
Maybe you can team up in your efforts to bring Debian to the N(eo)900.

Originally Posted by sulu

Besides phone support, power consumption seems like a major issue to me. I get about 6 hours of battery runtime with DebiaN900 (idle with backlight off but not suspended).
I know it's a huge leap but I'd like to have four times as much (trading suspend with still working calls for actually doing something on the phone).

Originally Posted by wicket

I would hope that this would generate much more interest and external contributions to the project than it currently has. In turn I could raise funds via donations, hopefully enough to be able to justify being able to dedicate up to 20 hours per week of my time. Raising funds would also enable me to buy a second N900, and cover hosting costs for a website and APT repositories. In the longer term, I will look for a sponsor to make it sustainable.

Originally Posted by wicket

I have however recently started an experiment which should allow us to run much of Fremantle on top of Debian with little overhead and hopefully it will bring its power saving features with it.