Development Custom firmware

Originally Posted by robot

Snepscheut, please also post result of those commands:
# cat /data/property/persist.sys.sc.miny
# cat /data/property/persist.sys.sc.minx
# cat /data/property/persist.sys.sc.maxy
# cat /data/property/persist.sys.sc.maxx
# cat /sys/devices/system/cpu/cpu0/op

miny 263
minx 90
maxy 3968
maxx 3991
op: 6 name: mode 3 [enabled 0]
pclk:788 baclk:197 xpclk:394 dclk:394 aclk:156 aclk2:312 vcc_core:1000

sorry for being late.

Jos vd Snepscheut

So far...
Keyboard issues were fixed, and overall input speed were improoved. Code were rewrited and now it's stable, and useable

Now working on app's design, additional features and integration with current eDGe's eink software.
Still looking for way to improove power saving (my goal is to improove battery run time up to 7 days). Unfortunetally seems that all known ways were not enabled in kernel modules loaded in EE.

Robot,

it's nice to see you working this fast.
I hope to enjoy your work soon, now I'm not only waiting for entourage but also for you! ;-))

Jos

what version of android is in this custom firmware?

any chance for beta testers?

PXA168 App note. http://www.datasheetdir.com/go/-bvb-jklm-ljl.pdf

XScale , ARMADA based on ARM
3rd Generation Intel XScale(R) Microarchitecture Developer's Manual http://download.intel.com/design/int...e/31628302.pdf

robot, you are great.
this is a beatiful device, the only problem it has it's the lack of optimized/complete software but with developers like you we can wonderful things.
I hope entourage will release sdk soon, some developers can't "afford" this low-level approach, and with some tools it would be easier to build a developer community.
Good luck

So far...

I was able to use ACCELEROMETER (and it's allready second device's feature which is not published anywhere )). Accelerometer is good enough to detect my table vibrations while typing Will think if it can be used somehow in firmware.

keng2000, thanks for the links but I'm looking for PXA developers manual (the one which contains the list of "signals" and "registers" which allow to directly send command to specific marvell's PXA hardware).

MichaelV, it's based on default firmware, so currently it's also 1.6. I'll notify if beta testers will be needed.

Originally Posted by robot

I was able to use ACCELEROMETER (and it's allready second device's feature which is not published anywhere )).

Ur kidding, there's an accelerometer? That's one thing I felt like this device was lacking. If you find a GPS hidden in there, it's perfect.

3g ??...........

Originally Posted by skapsal

Ur kidding, there's an accelerometer? That's one thing I felt like this device was lacking. If you find a GPS hidden in there, it's perfect.

It's not as good as I hoped. Accelerometr (or G-sensor) is present in EE. I can activate it and read data from it.., BUT unfortunatelly android apps seems unable to interact with g-sensor. Probably it was disabled in EE's android to avoid problems with screen orientation and there's way to reeanable it, but I didn't looked for it.

Originally Posted by robot

It's not as good as I hoped. Accelerometr (or G-sensor) is present in EE. I can activate it and read data from it.., BUT unfortunatelly android apps seems unable to interact with g-sensor. Probably it was disabled in EE's android to avoid problems with screen orientation and there's way to reeanable it, but I didn't looked for it.

I guess the important thing is that the hardware is there. Surely it's only a matter of time before you or someone else manages to crack the software integration part.

You really have done some stunning work so far, robot

Keep it up and well done.

Originally Posted by robot

It's not as good as I hoped. Accelerometr (or G-sensor) is present in EE. I can activate it and read data from it.., BUT unfortunatelly android apps seems unable to interact with g-sensor. Probably it was disabled in EE's android to avoid problems with screen orientation and there's way to reeanable it, but I didn't looked for it.

Maybe you keep this for your 2nd update?

what is the second hidden device? I do not understand why having one and not advertise/support. it will make the rotate button redundant or release it for other uses (like lcd/eink syncronisation like in Alex). also sorry to ask, why not working on a 2.1 / 2.2 firmware?

Originally Posted by robot

It's not as good as I hoped. Accelerometr (or G-sensor) is present in EE. I can activate it and read data from it.., BUT unfortunatelly android apps seems unable to interact with g-sensor. Probably it was disabled in EE's android to avoid problems with screen orientation and there's way to reeanable it, but I didn't looked for it.

This is one of the videos I watched before I actually made the decision to buy the edge. http://www.youtube.com/watch?v=hmpy-...eature=related In it there is reference to a built in accelerometer around 4.53 minutes into the video. Although, when I inquired about the accelerometer in an email to tech I was told the gentleman mistakenly spoke. How odd.