Mini0801 Hacking (Hardware and Software)

[ChpStcksRlz]

What is that camera? The menu doesn't look like a mini 0801

 

[jokiin]

What is that camera? The menu doesn't look like a mini 0801

it's an 0803, A7 version, the look is very similar but the menu has some different options

 

[ChpStcksRlz]

Interesting! Please take some sample shots. I'd love to see some night footage. It's a direct successor to our 0801's?

Is the mini 0801 GPS bracket compatible? (That way I don't need to buy another GPS model)

Does it also use mini-usb? Or is it now micro-usb?

So many questions, sorry

But it'd be a good device to let my tax return take a bite at that way I'll have the 0801 in the back and 0803 in the front.

Last but not least, do you have a release date?

 

[jokiin]

Interesting! Please take some sample shots. I'd love to see some night footage. It's a direct successor to our 0801's?

Is the mini 0801 GPS bracket compatible? (That way I don't need to buy another GPS model)

Does it also use mini-usb? Or is it now micro-usb?

So many questions, sorry

But it'd be a good device to let my tax return take a bite at that way I'll have the 0801 in the back and 0803 in the front.

Last but not least, do you have a release date?

it's only on a beta firmware right now, there are some image quality adjustments that need to happen but Chinese New Year got in the way of that

samples have been done as Mini and Micro versions, no firm decision which will be released as yet, leaning towards Micro unless some fault pops up, tooling for Micro USB version of the bracket and housing is already completed

GPS bracket may be interchangeable, will have to double check, they are physically identical (the mini USB version at least) need to make sure the hardware is compatible though

expected mass production end of February, available shortly after

 

[Jeremy]

Wait, Jokiin does your company make the mini 0801?

 

[jokiin]

Wait, Jokiin does your company make the mini 0801?

no, I'm just working with someone else and giving them a hand with the product

 

[GJHS]

no, I'm just working with someone else and giving them a hand with the product

So you can provide us a good place to buy and eliminate the copy of the copy that someone copied?

 

[jokiin]

So you can provide us a good place to buy and eliminate the copy of the copy that someone copied?

I can certainly let you know who will have real ones

 

[GJHS]

I can certainly let you know who will have real ones

Thanks, it's one of the things I most love about the Mobius. They make it easy to ensure you get a good product

 

[Tobi@s]

Not sure if it helps you work it out or not but this menu can operate with 3 buttons, up arrow to the top then long press up arrow to access the next menu option, this is how the A7 version of this camera is currently configured

Just tried it now.. Unfortunately it doesn't work. Long pressing up closes the menu. Long pressing ok takes a snapshot and Long pressing down doesnt result in any action.

 

[Tobi@s]

Different Containers (mp4, mov and avi) and their bitrates (TS still unstable and not included):

 

[Tobi@s]

After ~two days of testing I can say that the avi-modified Firmware ist the most stable one I ever used. Not a single crash/freeze/etc..
lol

 

[borland]

Are you saying you're able to enable AVI recording on later firmware that is configured for MOV recording?

What do you suppose the problem is that the developers can't seem to fix? Do you think they have been using an outdated sdk that doesn't correctly implement MOV?

I notice over the weekend, that mine (fw 1202) had locked up (would not shut down on its own, but would with long-press of power button). Leading up to that, it had been recording a string of 'Invalid' MOV files. Those 5 minute length files can't be viewed and show a yellow bang in Registrator Viewer.

 

[Tobi@s]

Nah I guess they just compile it with MOV as default, no idea why, probably because almost all dashcams use mov/mp4

Some more info on the avi test:
AVI with aac audio: no problems with the camera and recording, but when viewing in VLC and other players audio starts to late and Ends after the video
AVI with ac3 audio: camera freezes on every shutdown
AVI with adpcm audio: gonna test it tomorrow edit: camera freezed after first test drive

Edit: Tested AVI with aac again today, still no Problems (except the audio problem)

 

[ChpStcksRlz]

Can the Rom Kitchen change sound files? I found some sound files that would sound great when a car starts up

 

[Tobi@s]

Yes, it is possible in v0.2(not released yet). But you need the files as .pcm filetype.
Working everyday on it, almost finished the core functions, but I got one problem with building the FS section and I'm too cross eyed to find the faulty code... Maybe I'll solve that today

 

[ChpStcksRlz]

Oh cool, keep it Tobi@s!
Imagine, a not so annoying chime playing when your car starts up

 

[Tobi@s]

I actually like it

 

[Tobi@s]

Yes, it is possible in v0.2(not released yet). But you need the files as .pcm filetype.
Working everyday on it, almost finished the core functions, but I got one problem with building the FS section and I'm too cross eyed to find the faulty code... Maybe I'll solve that today

I'm a bit out of ideas now... I do create valid rfs files (at least I can unpack them correctly using different unpackers from different developers) but I still get ARM exceptions when I try to boot after flashing the fs.

pget_mpl() failed in mw_mpl_get, available 13507304 required 0 Ercd = -17
gobj_load_fonts_rom: allocate fail
pget_mpl() failed in mw_mpl_get, available 12779600 required 227346044 Ercd = -17
gobj_load_one_strtable_rom: allocate fail
pget_mpl() failed in mw_mpl_get, available 196808 required 699040 Ercd = -50
gobj_load_bitmaps_rom: allocate fail
pget_mpl() failed in mw_mpl_get, available 196808 required 460864 Ercd = -50
@@@@@@ (VOUT-0 SW. Scalar) Remain HEAP_MPLID: 196808 @@@@@@
pget_mpl() failed in mw_mpl_get, available 196808 required 1843264 Ercd = -50
@@@@@@ (VOUT-0 OSD Buffer) Remain HEAP_MPLID: 196808 @@@@@@
--- ARM ABORT EXCEPTION ---
Oops: CPU Exception!
pc : [<c033be78>]    lr : [<00000000>]
sp : c0421cec  ip : 00000000  fp : 00000000
r10: 00000000  r9 : 00000000  r8 : 00000000
r7 : 000002d0  r6 : 00000500  r5 : 001c2000
r4 : c04cdb98  r3 : 00000000  r2 : 00000000
r1 : 000e0fe0  r0 : 00000000
Flags: nzCv
IRQs on  FIQs on  Mode SVC_32

There are two differences to the original rfs: The order of the packed files and the space after éach included file. Seems I have to do more testing.

 

[Tobi@s]

Manual analysis of the first 3(4) files of RFS:

fonts.bin
    length:        611094    0x00095316
    offset:        6144    0x00001800
    calcedend-1:617237    0x00096B15
    paddingend:    618495    0x00096FFF
    space:        1258    0x000004EA
bitmaps.bin
    length:        597355    0x00091D6B
    offset:        618496    0x00097000
    calcedend-1:1215850    0x00128D6A
    paddingend:    1216511    0x00128FFF
    space:        661        0x00000295
 
strings.bin
    length:        106968    0x0001A1D8
    offset:        1216512    0x00129000
    calcedend-1:1323479    0x001431D7
    paddingend:    1325055    0x001437FF
    space:        1576    0x00000628
xxxxx
    offset:        1325056    0x00143800
 
bitmaps.offset     -     fonts.offset     =    612352    0x00095800 <-total length
strings.offset     -     bitmaps.offset    =    598016    0x00092000 <-total length
xxxxx.offset    -    strings.offset    =    108544    0x0001A800 <-total length

Seems we always have a "nice" number/amount for data + padding, but how is it calculated? Maybe I'll find the answer in the A2 SDK, just got a newer version from 02/2013