NEW - Lollipop - wasser firmware 3.0.6 for Minix Neo X7

[mrosys]

AW: UPDATE - Minix Neo X7 - wasser firmware - KitKat Android 4.4.2

Nobody using Play Music here? I can't get it to play multiple songs in a row; after one or two songs playback always stops. I can turn it on from the notification bar button, and all is fine, but one song later it will stop again. I dont't know where this bug originates; first I thought it had to do with the audio output device not sticking, but that's solved now so it must be something else.

i tested it and i have same issue here on wasser 1.0.3a firmware.

Gesendet von meinem Nexus 10 mit Tapatalk

[wasser]

Thanks wasser, we can update the old apk or is better to proceed with a fresh install?

i recommend fresh install

[wasser]

Nobody using Play Music here? I can't get it to play multiple songs in a row; after one or two songs playback always stops. I can turn it on from the notification bar button, and all is fine, but one song later it will stop again. I dont't know where this bug originates; first I thought it had to do with the audio output device not sticking, but that's solved now so it must be something else.

it's on my todo ist.

[radiolip]

[Pluto]

I'd rather have a newer kernel then a newer Android. KK was a giant leap for lower performing devices, and it has proven itself. 4.4.3 and 4.4.4 have barely any changes except some Heartbleed SSL patches. 4.4.3 was mostly concentrated on the Dialer changed.

[JustMe0815]

Hi Wasser,

i have a problem with tvheadend with your ROM, i guess it has something to do with the permissions.

http://www.freaktab.com/showthread.php?8508-live-TV-for-all-rk3188-using-XBMC-and-tvheadend&p=194377&viewfull=1#post194377

The Kernel Modules are loading fine, the DVB-T stick is recognized and successfully added.

But as soon as i start the tvheadend, i get an error:

[COLOR=#333333][I]ERROR unable to open /dev/dvb/adapter0/frontend0[/I][/COLOR]

the path is correct though. maybe permissions?

did work fine with 4.2.2.....
any ideas?

Thanks
Dennis

[vab.android]

OC Kernel

Hello,

Sorry for the Noob question.
I just flashed the Wasser 1.0.3a yesterday and I can say, its way much faster than the stock 010 I was using and the wasser xbmc included is just awesome (it solved my known problems). I still have to try wasser xbmc v2.

I wanted to flash the OC kernel and I was wandering how to do that.
Can I use the method from this link?

http://www.youtube.com/watch?v=kCBN-_zu5cY

Many thanks,
Vab

[mrosys]

Hello,

Sorry for the Noob question.
I just flashed the Wasser 1.0.3a yesterday and I can say, its way much faster than the stock 010 I was using and the wasser xbmc included is just awesome (it solved my known problems). I still have to try wasser xbmc v2.

I wanted to flash the OC kernel and I was wandering how to do that.
Can I use the method from this link?

http://www.youtube.com/watch?v=kCBN-_zu5cY

Many thanks,
Vab

1- install terminal app and launch it

1. copy the kernel.img file to /sdcard/

2. flash_image kernel /sdcard/kernel.img

wasser

you can use terminal to Flash oc kernel

[vab.android]

you can use terminal to Flash oc kernel

Thank you for the quick response. Does it mean I also have to rename my desired kernel as kernel.img?
And how much overclocking do you suggest for a faster and still stable ROM? I mainly do xbmc, youtube, occasional gaming and hi-res movies (in xbmc with subs).

Thanks a lot,
Vab

[iceberg]

Crazy screen flickering

Hi all,
just flashed the most recent 3.1a Rom onto my X7, but I'm having problems... I'm getting quite a lot of flicker, especially at the top of the screen, and when I enter the File Explorer, or any app with a white background, the screen goes crazy with flicker. Can anyone explain this?

Previously I was on Finless 1.6 Rom and flashed 3.1a directly "on top of" it... Should it have been done a different way?

Also, what use are the overclocked Kernals? Are the simply to add speed? If so, I don't need to experiment with them just yet, but if there are other practical reasons to give them a try, please let me know.

Thanks.

[vab.android]

Thank you for the quick response. Does it mean I also have to rename my desired kernel as kernel.img?
And how much overclocking do you suggest for a faster and still stable ROM? I mainly do xbmc, youtube, occasional gaming and hi-res movies (in xbmc with subs).

Thanks a lot,[ATTACH=CONFIG]6766[/ATTACH]
Vab

I tried flashing the kernel with three different terminal applications.
I got this error. I'll appreciate if somebody can help me flash the OC kernel. The file got attached in the quote by mistake.

Thanks,
Vab

[BTR11]

I tried flashing the kernel with three different terminal applications.
I got this error. I'll appreciate if somebody can help me flash the OC kernel. The file got attached in the quote by mistake.

Thanks,
Vab

You have to gain superuser permission first, so first command to run is:


su

[vab.android]

You have to gain superuser permission first, so first command to run is:


su

Thanks a lot ..... That worked for me....

Vab

[astral69]

I tried the XMBC v1.2 with the old 1.0.3 kernal
firstly overwriting the old XMBC ,then as a clean install

Same error in both cases, it just hangs on the screen to select Video/Music etc

Now downloading the 1.0.3a to see if it works with that


Anyone else having this problem?

OK it works on 1.0.3a, odd all the same

[iceberg]

You have to gain superuser permission first, so first command to run is:


su

I'm totally lost on this, so if someone could help, tat would be appreciated.
So, I flashed Wasser's 3.1a rom without any problems. I'm trying now to flash one of the Overclocked kernels.
I downloaded it and changed its name to "kernel.img" and saved it onto a blank SD card, in the root directory.

After inserting the SDCard into the X7, I opened the "Android Terminal Emulator" app and then typed out the commands listed below:

su
export PATH=/data/local/bin:$PATH
flash_image kernel /sdcard/kernel.img

All I got was a "error opening /sdcard/kernel.imgfailed with error: -1"

Any help would be greatly appreciated.

Thanks.