MK808 "all models" Finless 1.7

[t-bon3]

Re: NEW - MK808 "all models" Finless 1.7

Sometimes I must to change manually (depending of the network connection) because the Auto (use network-provided values) doesn’t have effect.

Try clocksync from the market with auto set on boot or set every 15 minutes enabled

https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync

[haynz]

Whether my Logitech M185 nor my Microsoft Mobile Mouse 4000 does the Pich-to-Zoom (Google-Earth) ...
I'm at 1.7b.
Can pls somebody else test this?

[Finless]

Hang tight guys. I am looking into the mouse scroll wheel zoom thing.

I never even knew that was there before

Learn something new every day!

Bob

[entonjackson]

Hang tight guys. I am looking into the mouse scroll wheel zoom thing.

I never even knew that was there before

Learn something new every day!

Bob

This dude is a genius!

[Finless]

Shit

You guys are right. Mouse wheel zoom does not work on 1.7B.
Now I have to figure out why and fix that

Stay tuned. I will either have a patch and a update 1.7C ROM.

Man.... I wish we could find all this stuff before I make a final release

Bob

[haynz]

Good boy
What would this little piece be without u ...

[niabi]

Shit

You guys are right. Mouse wheel zoom does not work on 1.7B.
Now I have to figure out why and fix that

Stay tuned. I will either have a patch and a update 1.7C ROM.

Man.... I wish we could find all this stuff before I make a final release

Bob

we (or you, hehe) should come up with a check list for future beta testers

OT: I am amazed at how you guys use the MK808... most of you use it as a tablet... while I just use it as a media player... maybe I am missing on a lot of stuff time to log into the play store! :P

[long2know]

Partitioning

I was looking at the parameter file:

CMDLINE: console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00002000@0x00002000(misc),0x 00004000@0x00004000(kernel),0x00008000@0x00008000( boot),0x00008000@0x00010000(recovery),0x000C0000@0 x00018000(backup),0x00040000@0x000D8000(cache),0x0 0400000@0x00118000(userdata),0x00002000@0x00518000 (kpanic),0x00100000@0x0051A000(system),-@0x0061A000(user)

Would it be possible to modify this such that the /sdcard partition is completely removed? I'd like to make all of the space allocated for the internal /sdcard to be moved to (userdata) or /data. I'm not sure if (user) or (userdata) corresponds to the /data mount point.

Also, do you know if something else in /system (beyond vold.fstab) has to be modified so that external_sd is treated as /sdcard and /mnt/sdcard natively?

[Finless]

(userdata) is the area I increase to give more APP space. This is later mounted as /data by the OS.
(user) is whatever NAND is left over and is mounted as internal sdcard.
As you take away space to increase (userdata) you decrease the amount of nand left over for (user).
But you cant take it away completely.

I have a 6GB parameter file I made for a guy that wanted it like this. This left about only 500mb left for internal sdcard. Then you just edit vold.fstab and do not mount internal sdcard. However some APPs will complain there is no sdcard! So the fix is to swap the mounts foer internal sdcard and external sdcard.

Bob

[long2know]

(userdata) is the area I increase to give more APP space. This is later mounted as /data by the OS.
(user) is whatever NAND is left over and is mounted as internal sdcard.
As you take away space to increase (userdata) you decrease the amount of nand left over for (user).
But you cant take it away completely.

I have a 6GB parameter file I made for a guy that wanted it like this. This left about only 500mb left for internal sdcard. Then you just edit vold.fstab and do not mount internal sdcard. However some APPs will complain there is no sdcard! So the fix is to swap the mounts foer internal sdcard and external sdcard.

Bob

I currently have vold.fstab to swap /sdcard and /external_sd .. It works fine for apps to use for their 'extra' data.. But it still acts funky for 'move app 2 sd.' It's as if /mnt/secure/asec doesn't get bound to /sdcard card properly with the vold.fstab switch.. If I manually bind /mnt/secure/asec to /sdcard, it will at least work until I reboot (for the most part).

Right now, my internal /sdcard mount shows about 600mb left.

If I wanted to increae the (userdata) by ~ 512mb, would it, roughly, expanding the end point by 0x00100000 and offsetting the everything else accordingly? Looking at the mtdpart command, it appears the format is "size:start," but I may be mistaken.

[Finless]

OK I fixed the mouse zoom issue.

For you guys that do not want to flash a ROM to fix it I will be providing you a new libinput.so file which you will replace using ES file explorer. I will provide instructions.

I will create a new 1.7C ROM for those people that have not flashed 1.7B yet.


Bob

[tatubias]

OK I fixed the mouse zoom issue.

For you guys that do not want to flash a ROM to fix it I will be providing you a new libinput.so file which you will replace using ES file explorer. I will provide instructions.

I will create a new 1.7C ROM for those people that have not flashed 1.7B yet.


Bob

if possible add the libstagefright rockchip udpate also. why not wcm :P

[Finless]

If I wanted to increae the (userdata) by ~ 512mb, would it, roughly, expanding the end point by 0x00100000 and offsetting the everything else accordingly? Looking at the mtdpart command, it appears the format is "size:start," but I may be mistaken.

In this thread I explain how to manipulate the parameter file.

http://www.freaktab.com/showthread.php?287-RockChip-ROM-Building-Tips-and-Tricks-by-Finless

The values must always be in even 512MB blocks.

Bob

[long2know]

In this thread I explain how to manipulate the parameter file.

http://www.freaktab.com/showthread.php?287-RockChip-ROM-Building-Tips-and-Tricks-by-Finless

The values must always be in even 512MB blocks.

Bob

Thanks for that link! So, does this look correct for adding 512MB to (userdata)?

Original:

0x00400000@0x00118000(userdata),0x00002000@0x00518 000(kpanic),0x00100000@0x0051A000(system),-@0x0061A000(user)

Modified:

0x00500000@0x00118000(userdata),0x00002000@0x00618 000(kpanic),0x00100000@0x0061A000(system),-@0x0071A000(user)

[niabi]

I love the work you've done so far, but I have some suggestions.
1) Could you possibly incorporate things like xbmc H/W acceration one (and add an .xml file with a backspace fix,) with the rom like Lewy's XTV 1.3???
2) Lewy used google's tv youtube app which is so much better than the regular youtube app; can you also include this in your rom? (i installed it on your firmware and it seems to work fine).

3) Change the boot animation again to something more like the one lewy used?

4) include apps like airpin (for airplay with ios devices).

5) is there anyway you can get miracast to work, or some kind of mirroing thing?????? Or is it incompatible with the wifi chipset in the mk808???????

6) apex launcher (customized)

>>>>Your rom is already great, and well polished, but adding these features would just make it even better.

No offense but, I still don't get why people complain about boot animations... my MK808 stays on almost 24/7 I hardly ever see the boot animation..., and even if I did saw it everyday, I would rather Bob spend more time on real issues than getting worked up for something so trivial... just my 2 cents

WimoRX is supposed to be for mirroring (but I have no idea how to use it ) but it would be cool to get some kind of mirroring, especially if we could use a tablet to simulate touch on the MK808