[WIP] Building a custom ROM for the LeapFrog Epic (CM/LOS)

[blakegriplingph]

Hi @blakegriplingph
I was looking at the latest logcat that you sent in this thread (logcat_UYT2_46.zip) and found interesting things.
Your problem is that the ROM boots up but you can only see wallpaper.
This is related to graphics stuff for sure.
I had a quick peak at the logcat and found you're missing a few graphics libs from the stock ROM.

Failed to open libwvm.so: dlopen failed: library "libWVStreamControlAPI_L1.so" not found
Failed to open FACTORY_LIB Error : dlopen failed: library "libdashplayer.so" not found

I don't know if it has to do since dashplayer is for qcom
btw your hwcomposer crashes a lot so I think it can be the problem too.
Regards.

Edit: First error that I can see from hwcomposer:

E/hwcomposer(  123): [HWC] Failed to get display attributes (dpy=1 is not connected)

Also as hwcomposer is not working correctly, other stuff like audio/camera hal or memtrack is not working too:

E/memtrack(  147): Couldn't load memtrack module (No such file or directory)

The two libraries you mentioned doesn't appear to be present on the stock ROM dump I have atm. And I may be wrong but I think the "Failed to get display attributes (dpy=1 is not connected)" error might be of even greater importance.
@Matty1993 - Have you by any chance encountered this issue? Well since you were able to port Android 5 and later to a 3.4.67 kernel and all...

 

[Rortiz2]

The two libraries you mentioned doesn't appear to be present on the stock ROM dump I have atm. And I may be wrong but I think the "Failed to get display attributes (dpy=1 is not connected)" error might be of even greater importance.

@Matty1993 - Have you by any chance encountered this issue? Well since you were able to port Android 5 and later to a 3.4.67 kernel and all...

So you can try to compile them
Regarding to hwcomposer it stills crashes a lot and that's not good.
Also, I noticed you are missing sensors.mt8127.so that is needed to have all sensors working.
Definelety the stock ROM has missing libs for LP.
Regards.

 

[blakegriplingph]

So you can try to compile them
Regarding to hwcomposer it stills crashes a lot and that's not good.
Also, I noticed you are missing sensors.mt8127.so that is needed to have all sensors working.
Definelety the stock ROM has missing libs for LP.
Regards.

Hmm, if only that LeapFrog would just suck it up and do at least an LP ROM for the Epic; Kitkat in 2019 (or 2020 for that matter) is plain stupid no matter how you patch it.

The stock ROM doesn't appear to have sensors.mt8127.so but what about sensors.default.so? Would that suffice?

 

[blakegriplingph]

So I compiled a new build lately; not much has changed except for the missing sensors library being thrown in. Didn't expect it to boot properly but I flashed it anyway to see if anything has changed at least in the logs.
@Matty1993 Think we could arrange for the demo tablet to be sent your way soon?

 

[Rortiz2]

So I compiled a new build lately; not much has changed except for the missing sensors library being thrown in. Didn't expect it to boot properly but I flashed it anyway to see if anything has changed at least in the logs.

@Matty1993 Think we could arrange for the demo tablet to be sent your way soon?

Cool.
Sad to say but it's kinda the same...

E/hwcomposer(  123): [HWC] ION is invalid (handle=0xb6073580, num=-1, idx=-1) !!
W/hwcomposer(  123): [HWC] Failed to get ION fd !! (handle=0xb6073580) !!

Basically warnings/errors from hwcomposer..
Now asking for more libs lol:

E/WVMExtractor(  134): Failed to open libwvm.so: dlopen failed: library "libft.so" not found

Also ffmpeg keeps crashing. Easy fix is use this sources:
https://github.com/CM12-1-Douglas/android_frameworks_av

PS: If you are missing libs, borrow them from the Amazon Fire
Cheers.

 

[blakegriplingph]

Cool.
Sad to say but it's kinda the same...

E/hwcomposer(  123): [HWC] ION is invalid (handle=0xb6073580, num=-1, idx=-1) !!
W/hwcomposer(  123): [HWC] Failed to get ION fd !! (handle=0xb6073580) !!

Basically warnings/errors from hwcomposer..
Now asking for more libs lol:

E/WVMExtractor(  134): Failed to open libwvm.so: dlopen failed: library "libft.so" not found

Also ffmpeg keeps crashing. Easy fix is use this sources:
https://github.com/CM12-1-Douglas/android_frameworks_av

PS: If you are missing libs, borrow them from the Amazon Fire
Cheers.

The "ION is invalid" error appears to be fence/VSYNC related, but I recall trying a few things pertaining to that to no avail.

I presume you're referring to the Fire whose codename is "ford", yes? If you have a ROM dump of the device, kindly let me know.
@Matty1993 You there mate? Just wanted to ask so I could arrange for the Epic to be sent your way.

 

[blakegriplingph]

@Matty1993 You OK mate? Haven't heard from you in quite a while.

 

[Matty1993]

Hey man sorry not been on had to deal with some stuff should hopefully be back on next week sometime ended up dropping and breakin my phone :crying: so havent been able to login finally got it fixed today so that a plus moving into a new place in a day or two so will be able to get settled and back into it again

---------- Post added at 01:25 PM ---------- Previous post was at 01:19 PM ----------

Hi @blakegriplingph
I was looking at the latest logcat that you sent in this thread (logcat_UYT2_46.zip) and found interesting things.
Your problem is that the ROM boots up but you can only see wallpaper.
This is related to graphics stuff for sure.
I had a quick peak at the logcat and found you're missing a few graphics libs from the stock ROM.

I don't know if it has to do since dashplayer is for qcom
btw your hwcomposer crashes a lot so I think it can be the problem too.
Regards.

Edit: First error that I can see from hwcomposer:

Also as hwcomposer is not working correctly, other stuff like audio/camera hal or memtrack is not working too:

That hwcomposer error wont stop the gpu or cpu from rendering the display had the same issue on my lineage 13 build via logcat but display still rendered fine, i also receive alot of hwcoposer related errors but surfaceflinger still starts and gui etc etc all still boot and work fine the only thing i could think of was as was mentioned before that the vendor libwvm libraries are not present but ehen i mentioned this to blake orginally he says there not in stock so if there no in stock then they rightfully shouldnt be needed foe the new build, im thinking its mali related somehow, blake whats your egl.config got written in /system/lib/egl/ this could possibly have something to do with it as well

 

[blakegriplingph]

Hey man sorry not been on had to deal with some stuff should hopefully be back on next week sometime ended up dropping and breakin my phone :crying: so havent been able to login finally got it fixed today so that a plus moving into a new place in a day or two so will be able to get settled and back into it again

---------- Post added at 01:25 PM ---------- Previous post was at 01:19 PM ----------




That hwcomposer error wont stop the gpu or cpu from rendering the display had the same issue on my lineage 13 build via logcat but display still rendered fine, i also receive alot of hwcoposer related errors but surfaceflinger still starts and gui etc etc all still boot and work fine the only thing i could think of was as was mentioned before that the vendor libwvm libraries are not present but ehen i mentioned this to blake orginally he says there not in stock so if there no in stock then they rightfully shouldnt be needed foe the new build, im thinking its mali related somehow, blake whats your egl.config got written in /system/lib/egl/ this could possibly have something to do with it as well

The egl.cfg file in my build looks to be the same as the stock one:

# NOTICE: This is an autogenerated file, do not edit\n
0 0 android
0 1 mali

It could be Mali-related, but there are plenty more factors to take into account here. All that's certain is that we get an ANR in RenderThread, and something's making it gobble up way too many CPU cycles than it should.

Oh and do you have any leads on whether you'd get your hands on an Epic dev unit soon?

 

[Matty1993]

The egl.cfg file in my build looks to be the same as the stock one:


It could be Mali-related, but there are plenty more factors to take into account here. All that's certain is that we get an ANR in RenderThread, and something's making it gobble up way too many CPU cycles than it should.

Oh and do you have any leads on whether you'd get your hands on an Epic dev unit soon?

Hmmm i thought it may look like that as suspected your egl is set ti render via mali as default

Set this as the config this will clear most mali issues up should clear some other graphics problems up aswell,

0 0 android
0 0 mali
0 1 gpu

As for the cpu cycles ill see what values are set for the cpu in init.mt8127.rc and init.rc to see how its being scaled, same for graphics aswell ill check the services make sure they are all there, ill have to dig through my packing boxes today and get the lappy out if i got some free time

Still working on a leapfrog unfortunately due ti moving house again and breaking my phone had to save up a bit for lease bond and replacement screen to be sent out to me, when im all settled in though ill be back on the hunt for one

 

[blakegriplingph]

Hmmm i thought it may look like that as suspected your egl is set ti render via mali as default

Set this as the config this will clear most mali issues up should clear some other graphics problems up aswell,

0 0 android
0 0 mali
0 1 gpu

As for the cpu cycles ill see what values are set for the cpu in init.mt8127.rc and init.rc to see how its being scaled, same for graphics aswell ill check the services make sure they are all there, ill have to dig through my packing boxes today and get the lappy out if i got some free time

Still working on a leapfrog unfortunately due ti moving house again and breaking my phone had to save up a bit for lease bond and replacement screen to be sent out to me, when im all settled in though ill be back on the hunt for one

Moving to a new place sure is no small expense, ain't it?

I'll see if that egl stuff would get things done on my end. Doubt that it would imho but eh...

What I meant about CPU cycles is that RenderThread ate up way too much resources than it should, similar to how an errant process or application in Windows is taking up a hundred percent CPU as shown in Task Manager. Something must be throwing things out of whack hence the issue.

As for the Epic, you mind if I sent you an invite to the Discord server my friends and I are maintaining? We have discussions on MTK tablets from Amazon and whatnot there, and I may be able to pull some strings there so you could get a cheapo Epic.

 

[Matty1993]

Moving to a new place sure is no small expense, ain't it?

I'll see if that egl stuff would get things done on my end. Doubt that it would imho but eh...

What I meant about CPU cycles is that RenderThread ate up way too much resources than it should, similar to how an errant process or application in Windows is taking up a hundred percent CPU as shown in Task Manager. Something must be throwing things out of whack hence the issue.

As for the Epic, you mind if I sent you an invite to the Discord server my friends and I are maintaining? We have discussions on MTK tablets from Amazon and whatnot there, and I may be able to pull some strings there so you could get a cheapo Epic.

Sorry for late reply new screen went dodge on me had to get a replacement express sent out lucky im a certified technician eyy cost me nothing next time ill be buying genuine if this one stuffs up

Tell me bout rental housing is so expensive in Australia daylight robbery if you ask me new place is $350 a week not my cup of tea at all but house is a house i guess lol,

Ahhh i see what you mean now by cpu being eaten by something i doubt this would be ramdisk related but ill double check when i find my laptop ive been through 10 boxes of stuff already its here some where,

Yeah send me the invite would be happy to join more mtk based forums

 

[Rortiz2]

Sorry for late reply new screen went dodge on me had to get a replacement express sent out lucky im a certified technician eyy cost me nothing next time ill be buying genuine if this one stuffs up

Tell me bout rental housing is so expensive in Australia daylight robbery if you ask me new place is $350 a week not my cup of tea at all but house is a house i guess lol,

Ahhh i see what you mean now by cpu being eaten by something i doubt this would be ramdisk related but ill double check when i find my laptop ive been through 10 boxes of stuff already its here some where,

Yeah send me the invite would be happy to join more mtk based forums

Here we go:
https://discord.gg/HjmKbM
Cheers.

Enviado desde mi WAS-LX1A mediante Tapatalk

 

[blakegriplingph]

Sorry for late reply new screen went dodge on me had to get a replacement express sent out lucky im a certified technician eyy cost me nothing next time ill be buying genuine if this one stuffs up

Tell me bout rental housing is so expensive in Australia daylight robbery if you ask me new place is $350 a week not my cup of tea at all but house is a house i guess lol,

Ahhh i see what you mean now by cpu being eaten by something i doubt this would be ramdisk related but ill double check when i find my laptop ive been through 10 boxes of stuff already its here some where,

Yeah send me the invite would be happy to join more mtk based forums

New screen for your phone? Reminds me of those aftermarket iPhone displays which for some reason (besides the MTK SOCs used on them clones not supporting the resolutions or something) hasn't been used by Goophones.

I guess I should consider myself lucky here in the Philippines lol.

Did you check out the Discord invite? Let me know as you'd be more than welcome there.

 

[Matty1993]

New screen for your phone? Reminds me of those aftermarket iPhone displays which for some reason (besides the MTK SOCs used on them clones not supporting the resolutions or something) hasn't been used by Goophones.

I guess I should consider myself lucky here in the Philippines lol.

Did you check out the Discord invite? Let me know as you'd be more than welcome there.

Yep second one now first one i had to wait and save for but wasnt genuine parts seems the digitiser decided to stop working all of a sudden ao got a free replacement sent out as im registered phone tech didnt have to pay sqaut for the second thankfully,

Yeah thosse iphone clones and what not use standard lcm drivers but the display reslutions on them are 9/10 set to 854×480 same case on my ubifs took a bit to adjust resolution so everything wasnt so bad on my lineage build as is also is using a standard techsun_x6572 lcm driver with 854x480 res shocking i have to say but it works i guess lol

Found my laptop also hidden right at the very bottom of all the bloody packing boxes haha

---------- Post added at 08:03 AM ---------- Previous post was at 08:02 AM ----------

Here we go:
https://discord.gg/HjmKbM
Cheers.

Enviado desde mi WAS-LX1A mediante Tapatalk

Awesome thanks heaps mate cheers for that

 

[blakegriplingph]

Yep second one now first one i had to wait and save for but wasnt genuine parts seems the digitiser decided to stop working all of a sudden ao got a free replacement sent out as im registered phone tech didnt have to pay sqaut for the second thankfully,

Yeah thosse iphone clones and what not use standard lcm drivers but the display reslutions on them are 9/10 set to 854×480 same case on my ubifs took a bit to adjust resolution so everything wasnt so bad on my lineage build as is also is using a standard techsun_x6572 lcm driver with 854x480 res shocking i have to say but it works i guess lol

Found my laptop also hidden right at the very bottom of all the bloody packing boxes haha

That's the perks of being a certified technician lol.

Assuming they were somehow able to use an original or at least a 1:1 work-alike display assembly, some conversion circuitry may be required - I recall a cheap Vivo clone by my uncle that ran off an MT6572; iirc the chip only supported displays up to 960x540, and since the Vivo's LCD appears to be a higher-resolution unit, it appears as though some upscaling was being done behind the scenes judging from the slightly blurry output.

 

[Matty1993]

That's the perks of being a certified technician lol.

Assuming they were somehow able to use an original or at least a 1:1 work-alike display assembly, some conversion circuitry may be required - I recall a cheap Vivo clone by my uncle that ran off an MT6572; iirc the chip only supported displays up to 960x540, and since the Vivo's LCD appears to be a higher-resolution unit, it appears as though some upscaling was being done behind the scenes judging from the slightly blurry output.

Grr no notification sorry man,

Haha yeah they tried to say it was my fault at first till i quite calmly told them hey hey hey i got a magic number haha,

They look quite the part though touch isnt to bad aswell as resolution juts they stinged on the actual quality of display id say its pushing SD drivers on a low end display, does the job though haha just pushing an update for my ubifs lineage 13 rom and will jump on the leapfrog forum soon as im done now ive got link

had to reconfigure my entire ramdisk but i think ive pushed all the lag out of it now hopefully only the beta test will tell

 

[blakegriplingph]

Grr no notification sorry man,

Haha yeah they tried to say it was my fault at first till i quite calmly told them hey hey hey i got a magic number haha,

They look quite the part though touch isnt to bad aswell as resolution juts they stinged on the actual quality of display id say its pushing SD drivers on a low end display, does the job though haha just pushing an update for my ubifs lineage 13 rom and will jump on the leapfrog forum soon as im done now ive got link

had to reconfigure my entire ramdisk but i think ive pushed all the lag out of it now hopefully only the beta test will tell

So I presume you're close to getting your hands on an Epic as well, yes?

 

[TheDeveloperDude95]

telegram group i suppose

So I presume you're close to getting your hands on an Epic as well, yes?

You guys want to make a telegram group for development of this device?

 

[Matty1993]

So I presume you're close to getting your hands on an Epic as well, yes?

Sorry for late reply i got abit huffy cause i couldnt fix the charging on my 6.0 build still so ive been determined to at least get something out that does work mostly Haha

Couldnt get lineageOS 14.1 to make boot nearly got it though goes as far as internal goes to start via zygote then f***ing BAM media_player died media_service died i got no idea why though as i was only able to get it this far by painstaking adding each service to the init.rc from /system/etc/init and everything is defined as it should be so i just cant figure out why its doing this to me,

So ive spent the last week rebuilding my old old CM 12.1 i did before 6.0 and f**k me what a headache that was storage was an easy fix but symlinks dont work like they do from 6.0 up weirdly even for vendor so ive got /system/vendor which has /lib /bin and / ive got my vendor partition which ive allocated to a swap partition which is made through recovery and set in recovery.fstab for it to be ext4 after formatting it and contains all my vendor apps BUT it wont link to system/vendor even though ive set it out as follows

On init
# Vendor lives on same filesystem as system
Symlink /system/vendor /vendor

#Tmp custom nand filesystem structuring
Mkdir /vendor 0755 system system

# Mount vendor partition start
On fs
Write /proc/bootprof "INIT:vendor start"
Mount ext4 /dev/block/mmcblk0p3 /vendor noatime nosuid nodev noauto_da_alloc discard wait check
Write /proc/bootprof "INIT:vendor end"
# Mount vendor partition end

On post-fs
# chown/chmod vendor so as to run as system:system
chown system system /vendor
chmod 0755 /vendor

# Tmp backwards compatibility
symlink /vendor /system/vendor

# Set SELinux Contexts on upgrade
restorecon /vendor

And added it to factory_init, init.charging.rc, init.mt6572.rc, init.rc and meta_init.rc but vendor still dosent link even when dir are empty in system weirdly my root vendor will only read /app and not /bin or /lib other than that i got it stable i fixed charging finally on it and also fixed my camera problem not capturing images, sadly i wish i could say the same for lineage 13 but i digress,

Anyhow still havent gotten a leapfrog yet sadly they seem hard to come by here in aus but when i see one ill be onto it anyhows any progress with build rendering display ?