yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Mik-el:
Thank you for the early testing and reporting io2345!

Don't worry. It seems that I haven't tested intensively the v. 1.1.

A few minutes ago I powered up the phone and I resulted to use it for a few minutes... I noticed better some problems.

I can't do so much for now, let's wait for the compatible Zopo battery, but meanwhile I can upload the Bluetooth fix.

FIX: It didn't work because you didn't do the warm boot, keep reading.

This "0 space" problem, that denies any installation, was present in v1.0 too, but I thought that t was simply caused by my full sd card... now I cleaned my SD I noticed that the problem is still here!

Do you remember which was the size of the 4.4 rom, approximately?

Anyway,

FIX: Maybe I wrongly adjusted the mount point of the system partition in the updater-script file. If this one is the reason, it's an easy fix.

Otherwise this will require other studies since it's not an easy thing to solve.

Rom v 1.0: Developer option shows up.

Rom v 1.1: It seems that Developer option doesn't show up because of a modification I made to enable USB Debugging by default. (it' a really useful features for testing and development).

FIX: At this point the quickest thing to do would be to remove the "USB Debugging by default" feature. This way it will be possible to access Developer Options again, which will allow to do a warm/hot reboot again, and thus allow to use cameras.

This doesn't happen on my phone, as you can see from my youtube video.

FIX: Download Igorware Hasher for Windows and generate the hash keys for the .zip file of my 1.1 rom, then compare these keys with the one I put in the first post. (see "Integrity Info" paragraph). This will tell you if your file is corrupted or not.

Yes, was present in 1.0 too, as said before.

Don't install Gapps until we get a new stable situation.

FIX: Strange, anyway I'll add back the "one time initializer" app to v. 1.2 to see if this can fix this.

Again, don't worry, still caused by "usb debugging by default"

I'll upload the bluetooth fix as a flashable zip here. Applying it on v.1.0 or v.1.1 should be the same since the kernel is identical. Get ready for the test.

Regards :)
[Android Software Development] io2345:
Mikel, thank you so much for your support. Did you already upload the Bluetooth fix? Can't find it.

For the camera : I know how to start it, but warm reboot does only make sense as soon as the selfie cam is working. As long as you get error "couldn't start camera" it won't help to reboot hot.

Don't remember the size of system in 4.4. Wasn't one of your phones still on 4.4? If not I will install it again.

Did check the file with the hasher, values are OK.
[Android Software Development] Mik-el:
My other Takee has 4.2.

Don't install 4.4 again for now. Give me some time to upload the Bluetooth fix, then we'll fix the camera. :)
[Android Software Development] Mik-el:
@io2345 Try this one, completely untested, no double check on file permission. Next one will be more robust.
[Android Software Development] io2345:
Confirmed to work. Tried it on 1.0, I assume it will work on 1.1 as well (let me try later).

Perfect, thank you Mikel!

Update: Fix can be installed on Mik-el 1.1, other phones find the Takee but can't connect. On the Takee no other Bluetooth-Devices can be detected. Probably due to the existing error with user account
[Android Software Development] Mik-el:
Woah! I'm really happy! Nailed it on the first try! 😮😮:D:D

This fix could have taken 10+ attempts.

Now working Bluetooth on Android 7 is a reality!
[Android Software Development] io2345:
For being curious (and because I had a liitle spare time) I installed 4.2 (the AiO Pogo-Version). Partitions here are as follows:

/system is mmcblk0p5, total 2GB, used 740MB

/data is mmcblk0p7, total 4GB, used 437MB

Mount point for SD card internal is mmcblk0p8, total 22,9GB, used 5,9MB

Mount point for SD card external is mmcblk1p1 (size depends on the MicroSD that you use)

Lots of space in internal "card", perfect!

Next, let me try to install Android 6 (LuckasFB) to see, if this is the same layout.

Here we go:

/system mmcblk0p5, total 2GB, used 1,1GB

/data mmcblk0p7, total 4GB, used 1GB

/storage/<ID> and two more mount points for internal SD card, total 22,9GB, used 6,9MB

/storage/<ID> and one more mount point for external SD

RAM says: 1,9GB, 1010MB free

Now going from there to Mik-el 1.1, only doing a factory reset in TWRP

Can't install disk info, due to the "zero space" problem...
[Android Software Development] Mik-el:
Custom ROM 4.4 has the same mount points of the stock4.2 ROM.

/system is mmcblk0p5

/data is mmcblk0p7

I used the same mount points in my ROM, I still don't understand what is causing the problem...

@io2345 If you want to install diskinfo: Download it and be sure the file name does not contain spaces. Copy the apk to your SD card and use Total Commander to copy the apk in the /system/app folder (you should make a folder with the same name of the apk, see other apks there) or you can copy the apk in the data/app folder too (it should be easier). Reboot if needed.

EDIT: or flash this attached file from twrp
[Android Software Development] io2345:
Yes, one step ahead. We see, that the internal card isn't mounted in 1.1:

/system mmcblk0p5, 2GB total, 1,3GB free

/data mmcblk0p7, 4GB total, 3,6GB free

fat mmcblk0p8 22,9GB NOT MOUNTED

external SD card mmcblk1p1

RAM: 1,9GB total, 1,3GB free
[Android Software Development] Mik-el:
Thank you! Now the question is: how many partitions should we create on that 22,9GB space? and how should we format them since we already have /system and /data?

I think we should look at the partition scheme from sp flash tool (for stock 4.2)
[Android Software Development] io2345:
Meanwhile installed 1.0 again, to check there: Here it is the same, the 22,9GB are "Not mounted". But there these problems aren't present. So the cause has to be a different case. What to do with that ample free space is then the next question to be solved.

Can you get the info from 4.2, or do you want me to have something checked?
[Android Software Development] Mik-el:
on stock 4.2 I have this partition:

mmcblk0p8, mounted as "/storage/sdcard0, mnt/secure/asec". size is 22.9GB (5.8GB free and 17.1GB free).

Now I only have 2 doubts:

1)why the mount point has two parts?

2)the 4.4 rom by luckas has the same partition scheme of my ROM, and as my ROM it does not format nor mount the mmcblk0p8 partition. (but luckas rom doesn't have this storage bug).

At this point the only idea iI have now is to format and mount mmcblk0p8. I could make a flashable zip to do that. If you have other ideas let me know.
[Android Software Development] io2345:
Mikel, it would be a waste of resources, if you don't mount the free space. Internal Card is useful - not everybody has a spare SD-Card, or doesn't want to use it for privacy reasons.

I guess that the partition should be mounted under /storage/<ID> and the other two mounts are just "mount --bind"s to this path (in order to make it available under different names). What I don't know is, if the <ID> is specific for each phone, or if it's the same. Let me install 4.2 again on my phone, then we can check names on your phone and on mine.

------------------------------------

Found that for 4.2.2 it's different: The 22,9GB are simply mounted as /storage/sdcard1, File system vfat, Partition name mmcblk0p8, Nickname "SD card", Label "fat", Partition type "SD/MMC card", Device "Internal Storage (mmcblk0)", Device type "MMC"

-------------------------------------

Now checking again with Android 6, to find the other two mountpoint-names for the internal card:

/mnt/media_rw/3F21-08DE

/mnt/secure/asec

/storage/3F21-08DE

File system "vfat", Partition name "mmcblk0p8", Nickname "SD card", Label "fat", Partition type "SD/MMC card", Device "Internal Storage (mmcblk0)", Device type "MMC"

As far as I remember, Google has changed the way the SD-Card is treated in Android from time to time. Maybe this is true for the internal card as well. So it could be better to stick with the closest version, which would be 6 rather than 4.2
[Android Software Development] Mik-el:
Yes, this was obvious.

Anyway here's the fix I tought about.

reinstall Mik-el rom, v.1.0, no need to flash bletooth fix and so on

plug your phone to your pc

see if it's detected correctly in file explorer

see if it's detected correctly by "adb devices", if the answer is yes type "adb shell" and go to step 7

download this terminal app for Android

install the app through Total Commander

give the following command (in terminal app or adb prompt) fdisk -l /dev/block/mmcblk0p8

post output here

mount the partition giving this command (I hope it's right) mount -o rw /dev/block/mmcblk0p8 /storage/sdcard1

post output here

see if you can install apks

disconnect and reconnect your phone from your pc and see if it's correctly detected in file explorer
[Android Software Development] io2345:
reinstall Mik-el rom, v.1.0, no need to flash bletooth fix and so on

-> I installed 1.0 together with bluetooth fix (to avoid error messages), activated developer options and there ADB debugging.

plug your phone to your pc

see if it's detected correctly in file explorer

-> Selected "USB for file transfer". "Now phone is detected as "A311"

see if it's detected correctly by "adb devices", if the answer is yes type "adb shell" and go to step 7

-> is detected as "MT085DUYHAYRWUCD6GU unauthorized". After answering the Debugging promt it changes to "MT085DUYHAYRWUCD6GU device".

download this terminal app for Android

install the app through Total Commander

give the following command (in terminal app or adb prompt) fdisk -l /dev/block/mmcblk0p8

post output here

-> Did it in ADB shell:

A311:/ $ fdisk -l /dev/block/mmcblk0p8

fdisk: can't open '/dev/block/mmcblk0p8': Permission denied

DiskInfo shows mmcblk0p8 as "not mounted"

mount the partition giving this command (I hope it's right) mount -o rw /dev/block/mmcblk0p8 /storage/sdcard1

post output here

/storage/sdcard1 is available. Currently there are only

/storage/3338-3139

/storage/emulated

/storage/self

used.

But:

A311:/ $ mount -o rw /dev/block/mmcblk0p8 /storage/sdcard1

mount: bad /etc/fstab: No such file or directory

He's right, if I look into /etc there is no file fstab

see if you can install apks

I can install APKs, no problem. It's obviously not the question, if mmcblk0p8 is mounted or not. It's just, that then there would be more space available...

disconnect and reconnect your phone from your pc and see if it's correctly detected in file explorer

[/QUOTE]
[Android Software Development] Mik-el:
try to use "su" or "sudo" before the command to give the command as root user.

If this one does not work try to replace /storage/sdcard1 with another label, maybe sdcard0 . Or have you tried it yet?

fstab should be present, if it's not there it's somewhere else, or it has another name. Try the command again with /etc/fstab.mt6592

Oh, great, I didn't understand yet installations were OK on v1.0
[Android Software Development] io2345:
I already tried it with "su".

Using another destination doesn't change anything.

There is a fstab.mt6592 in / but I don't know how to specify the name of the fstab-File in the "mount..." command.

The file contains this:

# Android fstab file.

#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>

# The filesystem that contains the filesystem checker binary (typically /system) cannot

# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

/emmc@android /system ext4 ro,barrier=1 wait

/emmc@usrdata /data ext4 noatime,nosuid,nodev,barrier=1,nomblk_io_submit wait,check

/emmc@cache /cache ext4 noatime,nosuid,nodev wait,check

/emmc@protect_f /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check

/emmc@protect_s /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check

/devices/platform/mtk-msdc.1/mmc_host* auto auto defaults voldmanaged=sdcard1:auto,encryptable=userdata

/devices/platform/mt_usb auto auto defaults voldmanaged=usbotg:auto

I would assume, that the "mount" command tries to write the block-destination information into the fstab, but doesn't find it where it expects it to be.

==============================================

Found more information: If I boot only into recovery, there

is

a file /etc/fstab:

/etc # cat fstab

/dev/block/mmcblk0p5 /system ext4 rw 0 0

/dev/block/mmcblk0p6 /cache ext4 rw 0 0

/dev/block/mmcblk0p7 /data ext4 rw 0 0

/dev/block/mmcblk0p8 /emmc vfat rw 0 0

/dev/block/mmcblk1p1 /external_sd vfat rw 0 0

/sd-ext auto rw 0 0

/usb-otg auto rw 0 0
[Android Software Development] Mik-el:
@io2345 try this one ;)
[Android Software Development] io2345:
Mikel, process starts, but ends with "error 7" and says before that: "format() expects 3 args, got 5"

By the way: As far as I understand, the process tries to format it ext4. But shouldn't it be vfat? At least it was vfat in other versions.
[Android Software Development] Mik-el:
@io2345 I made a new one. This one does not format mmcblk0p8, it just mounts it as vfat partition. Let me know!
[Android Software Development] io2345:
Thank you, this time the installation is successful. But when I start the phone and open DiskInfo, it still says "mmcblk0p8 not mounted". BUT: if I look into "Settings" -> "Storage" it says: 25,92GB internal shared storage used of total 29,10GB. In details I see, that "system" has a size of 25,17GB. Now, back in DiskInfo-app I learn that "system" is mmcblk0p5, but has only a size of 2GB in total, 763MB of that used.

That makes no sense, does it? Also, there is no mountpoint /storage/sdcard1 in DiskInfo.
[Android Software Development] Mik-el:
@io2345 it seems that I had to edit the "fstab" or "fstab.mt6592" inside the kernel (boot.img of the rom).

I should improve my porting guide too at this point.

The problem should be fixed in the next release of the rom.

By the way can you find the fstab/fstab.mt6592 from total commander?
[Android Software Development] io2345:
Yes, the content of the fstab.mt6592 file is already posted - see post #84 of this thread.
[Android Software Development] io2345:
Mikel, did you remove the download link for the ROM? FileFactory says "File currently not available"...
[Android Software Development] Mik-el:
I did not remove it, the file is present in my Filefactoy filebox. It seems a maintenance problem of the servers.

By the way, do you need to download the Rom again?
[Android Software Development] Mik-el:
Ok before the partition thing, download this app on 1.0 and use it to do a hot reboot. Do cameras work?

Now for the partition,

The fstab file you see in Mik-el rom, "fstab.mt6592", is the fstab file from the PORT rom (ridon).

But I think we should have the stab file for the BASE rom (luckas) instead, "fstab".

You could try the following, but after reboot you could get a bootloop...

download the last archive I uploaded (post 89)

take the "fstab.mt6592" file from port/RIDON

use Sublime Text or NotePad++, delete its content and paste in it the content of the "fstab" file of the stock/LUCKAS folder

in Mikel rom, take note of the file permissions for "fstab.mt6592"

delete the "fstab.6592" in Mik-el rom, replacing it with the new "fstab.mt6592" you just edited

set the correct permission for the "fstab.mt6592" file
[Android Software Development] Mik-el:
@io2345 post updated, I fixed a thing in the step that could give you problems.

Anyway an advice for now and the future:

open File Explorer on Windows and set the option to clearly see the file extensions of every file. (there are guides on internet if you don't find the option).

If we mess up file extension nothing will ever work :ROFLMAO:
[Android Software Development] io2345:
It's just another tool for doing a warm reboot. Not better nor worse than any tool for this purpose. I prefer the "extended reboot menue" accessable from developer options.

Now for the partition,

I did it, but after reboot the altered file is replaced by the original one. I guess the partition information has to be edited in the boot.img to be permanent

Maybe something like that might do the trick? Edit Tool for boot.img
[Android Software Development] Mik-el:
@io2345 Thank you. Sorry if I'm confused sometimes, but I code too many things in a day:ROFLMAO: Ok so I'll send you v 1.2 with updated boot.img when possible
[Android Software Development] Mik-el:
Sorry for the late reply @io2345

Yes, everything is a mystery, since the kernel should be the same.

I found a thing that could fix the problem on v1.1, but I think I'll add the new 1.1 features to 1.0 again, since fixing 1.1 would require more time.

I'll post the updated ROM here.
[Android Software Development] Mik-el:
Mik-el Android v 1.2 just uploaded!

Download it from post 2.

Untested.

I uploaded it as .7z file to speed up your downloads. (so extract the zip file from the 7z file).

This version tries to fix the 0 space problems of v.1.1, at the same time it keeps the new things from v.1.1 except for the usb debugging by default.

@io2345
[Android Software Development] io2345:
Mikel, first test wasn't too succesful. The zero-space problem still exists, and Bluetooth remains not working (until I install the bluetooth-fix). Installer installs SuperSU, rather than letting system untouched.

With first start, ROM says "Music terminated". Probably due to the zero-space problem, F-Droid can not install new versions (not even for the app-store itself) - app just crashes when you try to install it's own update. For other apps it says "The new package couldn't be installed in the specified install location" (I didn't specify a location - should I?) Can't update "open camera", it says you would have to deinstall old version first, which isn't possible, as it is installed as system-app.

Wouldn't it be easier to use 1.0 as base and just add bluetooth-fix, adjust screen resolution and remove superSU ?
[Android Software Development] Mik-el:
That's what I' ve done! I started back from v 1.0 (20 june), I don't unerstand why the 0 space problem remains!

Yes, very probably these issued are caused by the 0 sapce problem

I forgot to add the bluetooth fix, my bad! It was late yesterday!

Again I didn't remove supersu, the priority was the 0 space problem.

The memory problem could only come from the updater-script, at this point.

Let me check it.
[Android Software Development] Mik-el:
@io2345 it seems that the 2 updater-script files do the exact same things when formatting and mounting partitions, at this point delete the boot file (with .img extension) in the root of my 1.2 rom and replace it with the boot file of my 1.0 rom. Then test again, sorry if I can't test
[Android Software Development] io2345:
@Mik-el

Deleted the boot.img from 1.2 and inserted the boot.img from 1.0, installed again with full wipe.

Error doesn't disappear, out-of-space problem is still there.
[Android Software Development] Mik-el:
@io2345

Woah! This makes absolutely no sense! The 2 releases are almost identical now!

The only 2 files that are different now are core-o.jar and services.jar in system/framework.

Do you remember when I asked you to patch these 2 files? That patch allowed me to customize the wallpaper and bootscreen starting from v.1.1.

Anyway I don' t think that this patch could be related to the storage problem. But we can try a thing...

You can take the 1.2 rom and use Total commander to replace these 2 files with the ones from v1.0

If you do this, 3 things can happen:

---no bootscreen / black screen, but in this case just let the boot process to finish

---bootloop

---storage problem fixed (I don't think so but at this point...)

Meanwhile I'll try to find another solution googling
[Android Software Development] Mik-el:
@io2345

Try this fix before, it's faster

Can't install apk from Package Installer

I have downloaded an apk from a site, but now I cannot install it; when I'm trying to install, it just returns me an alert / toast message with: Sorry, no application available The Package Installe...

android.stackexchange.com
[Android Software Development] io2345:
It's kind of a bootloop or more precise it hangs - you see the blue "Mik-el Android" logo forever, the red dot is running, but nothing happens. I stopped it after half an hour or so.

Couldn't try the other fix (have little hope in that also), as there is no "Package installer.apk" in /system/app
[Android Software Development] Mik-el:
@io2345

Ok so bootloop happened, I was hoping for the missing bootscreen only (that's why I said you to wait the boot even if you don't see the bootscreen).

Anyway for the next tests don't wait more than 15 minutes, it's useless, according to our experience.

For the other fix: Android 7 is a bit different, you have to look at this path instead system/priv-app/PackageInstaller/PackageInstaller.apk
[Android Software Development] zdomjus:
@Mik-el

Sorry to bother you, I really appreciate your efforts to revive the old Takee, but I can't download the TWRP you have loaded to FileFactory, the link seems broken. Can you check it? Saluti dal Veneto.

FileFactory

FileFactory is the best place to upload and share files with no limits since 2005. Send and receive any type of file up to a massive 5GB with unlimited file bandwidth.

www.filefactory.com
[Android Software Development] Mik-el:
@zdomjus

Ciao! :)

Don't worry, you're very welcome to the team!

Ok replaced TWRP links with downloads from xda so downloads won't expire anymore.
[Android Software Development] zdomjus:
@Mik-el

Thank you very much, I'll test your recovery and rom ASAP.
[Android Software Development] Mik-el:
A developer from Telegram is helping to make a new kernel for Takee 1.

Luckasfb didn't share the kernel he made.. but I'll upload everything on Github.

For the moment I need someone who can send me the config.gz file in /proc directory (you can take it from the 4.4 luckas rom).

I need this file to adapt the kernel. @io2345 @zdomjus

It can't be extracted from the rom, meanwhile this is the shipping of the new reliable ZOPO battery I bought for my Takee
[Android Software Development] Mik-el:
@io2345

Going back to the ported rom:

These are the steps I used to add 1.1 rom features in top of the 1.0 features to get the 1.2 rom. You can try to repeat the process if you want, hoping something will change...

Backup roms (1.0 and 1.1)

Extract them from the zip files.

delete the gapps folder

don't delete the supersu folder for now, since we need root during development

Delete the following files from 1.0 and replace them with the files from 1.1

all folders and files in system/apps

core-o.jar and services.jar in system/framework

framework-res.apk from system/framework

bootanimation.zip in system/media

open the bluetooth fix file. Inside it there's a system folder, extract it inside the system folder of the rom. So you'll basically extract/replace the files from the 3 folders (bin etc and lib). No need to extract the busybox file.

zip the whole rom without compression, just "store"

test it and if everything works send me the rom with wetransfer
[Android Software Development] YuriRM:
A new kernel for Takee 1 requires the drivers that I found in clones.

Android 4.4.2 KitKat kernel - BQ Aquaris E5 FHD

Official source code for BQ Aquaris E5 FHD

https://github.com/bq/aquaris-E5FHD

Have you acquired knowledge enough for including specific drivers of EStar Takee 1 into this Official Android 4.4.2 KitKat kernel of BQ Aquaris E5 FHD?

You will get a much better kernel (3.4.67) than luckasfb.

NOTE - hacked kernels often contain malicious code.

luckasfb had to remove heaps of malicious code from his kernel.

I hope that Mediatek supplied clean code for BQ Aquaris E5 FHD.
[Android Software Development] io2345:
Here you have the file from Android 4.4 and 6 ROMs (didn't check, but guess they are identical)