[project]Port android to meizu M8

i tried the image and dualboot fw, but wince works, but bootloader hangs when i want to start android....

Originally Posted by LVL

i tried the image and dualboot fw, but wince works, but bootloader hangs when i want to start android....

which one did you try? Where does it hang? There is a long pause where the shell is given. I probably could turn off the shell service to speed things up. That's one of few improvements that can be made to the last dual boot image I made. But without sound, it's a bit meaningless to publish them.

it hangs at uc login or something like that.
But more important, it seems as if it can not mount the image.
It could not create some directory like disk/mnt/system or mnt/disk/system, something like that. That's what i read on the boot log as far as i can remember.

I have a M8 FE 8Gb, i tried your dualboot 0.9.6.12 fw with the system.img (not the mdroid.img) from the wiki.
I am using your bootloader, since it asks for a system.img (which was unable to mount)

Any ideas, or do you want more information/boot log?

not been able to create system directory, etc are fine because they're already there. It looks like you have a shell prompt in the end, which is good. It's normal to wait for a while before the GUI part starts. But if it doesn't eventually, you might take a picture of the hung screen and post it.

Originally Posted by LVL

I have a M8 FE 8Gb, i tried your dualboot 0.9.6.12 fw with the system.img (not the mdroid.img) from the wiki.
I am using your bootloader, since it asks for a system.img (which was unable to mount)

Lang2, am I right that you only edited the .img file? If yes one can just rename the .img file to mdroid.img to be usefull with older dualboot packages?

There is a long pause where the shell is given. I probably could turn off the shell service to speed things up.

it hangs at uc login or something like that.
could not create some directory like disk/mnt/system or mnt/disk/system

There is indeed a very long pause, at first i thought android hanged whilest booting but after beeing patient it loaded normally. So disabling the shell would be nice to have a faster boot time.

So LVL, if you wait on this screen (could be aprox. 30 seconds) does it continu?

you might take a picture of the hung screen and post it.

Might be a good idea! But i do hope for LVL it continues loading, since he might be able to test the alsa audio patch. Would be nice to see the first one who can use sound in android!

What difference?

I'm not even sure what version it is. Just read some that there is an experimental tree that's supposed to be the latest.

I thought it was on .32, but i can not give you my word it is 100% sure.
But i can say for sure that 2.0/2.1 should need at least kernel .29 to run.
On the difference, i should look it up, i forgot

i would confirm that my android made alarm. I think it did but i didnt used andoird a longer time :9 wil install and see later.

I want to use the enableRadio function which writes to registers and this cant be done in userspace. therefore i want to make in the kernel.
Or can is acceess the regisers in userspace too?

Originally Posted by LVL

it hangs at uc login or something like that.
But more important, it seems as if it can not mount the image.
It could not create some directory like disk/mnt/system or mnt/disk/system, something like that. That's what i read on the boot log as far as i can remember.

I have a M8 FE 8Gb, i tried your dualboot 0.9.6.12 fw with the system.img (not the mdroid.img) from the wiki.
I am using your bootloader, since it asks for a system.img (which was unable to mount)

Any ideas, or do you want more information/boot log?

Same problem here



Sorry for the photo quality, without flash was worse xD
(I have same spec. that LVL: M8 FE 8Gb, firm 0.9.6.12, and I tried renaming to mdroid.img without any result)

I have the same, but then i get an error with system.img.

Any ideas, r3wdy/lang2/evow04 or somebody else?

nope i have no idea. the problem is that this is all beta beta alpha stuff and anyone wo plays around with this, should have a little understaning of whats going on (at least linux knowledge).
So without haveing the image u used or a better logfile i just cant help. Upliad your xip somewhere then i will have a look

Originally Posted by r3wDy

i would confirm that my android made alarm. I think it did but i didnt used andoird a longer time :9 wil install and see later.

I want to use the enableRadio function which writes to registers and this cant be done in userspace. therefore i want to make in the kernel.
Or can is acceess the regisers in userspace too?

I'd say so. User space can't access kernel memory but registers should be OK.

demon_heart, LVL: from looking at the picture it looks like the kernel is looking for mdroid.img, which means you're NOT using the xip.bin I provided. Only copying my system.img won't work. Please try upgrade the firmware with my xip.bin and try again.

evow04: renaming syste.img to mdroid.img probably won't work. The reason is that mdroid.img contains more stuff then system.img. But I never tried myself so I could be wrong. Even if would work, you'll be using an older kernel with SDCARD disabled which is kinda pointless.....

Originally Posted by LVL

Any ideas, r3wdy/lang2/evow04 or somebody else?

demon_heart, LVL: from looking at the picture it looks like the kernel is looking for mdroid.img,

it could be my fault, sorry for this!
I noticed that i did not explain it well on the wiki page so i updated it a bit to make it clear that loader+image needs to be a specific one., will be changing it to a better way asap.

evow04: renaming syste.img to mdroid.img probably won't work

and I tried renaming to mdroid.img without any result

ok thanks for the confirmation!

I have the same, but then i get an error with system.img.

LVL, could you try again to flash and place the right image?


EDIT

will be changing it to a better way asap.

updated the wiki to make it much more clear, also update info page on how to build dualboot package with the link to alsa kernel wich i supose contains support for mounting SD.?

jfyi:
Just regged @ the new wiki. i will create a page for the baseband software stuff so the information is not lost and anyone who is willing to puzzle with me gets the needed infos

Originally Posted by lang2

demon_heart, LVL: from looking at the picture it looks like the kernel is looking for mdroid.img, which means you're NOT using the xip.bin I provided. Only copying my system.img won't work. Please try upgrade the firmware with my xip.bin and try again.

evow04: renaming syste.img to mdroid.img probably won't work. The reason is that mdroid.img contains more stuff then system.img. But I never tried myself so I could be wrong. Even if would work, you'll be using an older kernel with SDCARD disabled which is kinda pointless.....

that's my problem, i use YOUR loader, your xip.bin and your system.img.
It says things like system.img can not mount, NOTHING ABOUT MDROID.IMG!
Can you post the links of the xip.bin and system.img you are talking about?
Maybe i have an older version of your loader that doesn't work or something like that???

I think the issue will be again M8FE versus M8SE... cause no one with an M8FE already confirmed it actually worked fine like on SE.

lvl,
here are the original download links from lang2

btw , leaf9999 pointed me to an interesting bug we should consider to resolve asap.. the power button to shut down :P

I have M8 FE and for me it works!

with sound?

no sound doesn't work but it boots properly and shows disk folders while booting

LVL: can you take a picture while it halts and post it? It might help figuring things out.

Punchlinegott: the pre-made xip.bin doesn't have sound turned on. I later on posted a kernel zImage that has it enabled. Unfortunately, you'll have to build your own dual-boot xip.bin out of it. I have a SE so I can't really test it. Please refer to the wiki page for links.

If somebody can confirm that sound works, I'll do some cleanup and roll another set of binaries and we can call that RC4 then.

im sure that sound worked for me. must got lost somewhere... i will try to install an older version and try myself

maybe get a stiffi :D