yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] Lukas+:
For the selfie camera the camera 2API support is type limited, for the first camera is complete.

10 fps is the refresh rate I read for a video with main camera at highest resolution, (ProCam X) at 1980*1080 (opened on a 30 meters large street in the sun with people, cars, threes and houses everywhere)

Moreover, but this is only speaking, there's the funny think that what you see in that moment in the screen is really bad (you see the pixels) but the video you are taking is sincerely good, even if, obviously, it's better moving the camera slowly!

Maximum fps I think it's 30, sometimes the focus is slow, sometimes the fotocamera seems to became crazy, but in general it's able to give good images and usable, sometimes nice, videos. That's all I remember now.

Bye!
[Upgrading, Modifying and Unlocking] x53:
@Lukas+: 10fps! Thats a pity. Why does Camera2 API Probe report other possible frame rates, e.g. fixed 30, variable fps between 5 - 30, 15-20, fixed 15 and at least fixed 10 fps. I always get videos with a variable frame rate between 10 and 15fps, more precisely 11.1 - 14.8. But that variable mode Camera2 API Probe doesn't even report. Maybe that app is wrong? Has anyone seen any technical specifications from cubot speaking of video fps and resolution? Why do you think max. fps is 30? Whats your reasoning? Would be nice. And yes, the focus is very slow. Thats a know feature :).
[Upgrading, Modifying and Unlocking] linusuli:
hello, IMG-e-0.22-q-20220226166118-dev-treble_a64_bvN.zip , This one also works, it carries microG, but I don't let it go ... the connection with google I mean. I try to enter gmail but it doesn't work. In addition, the internal files are encrypted, you can only see the files on the sd.
[Upgrading, Modifying and Unlocking] Lukas+:
@x53 Yes, it's true, and after your post I also recognized some discrepancies...

There's more: also at 720*480 I didn't go over 15 fps, and this really astound me. Camera 2API says 30, yes. I don't know if the application is wrong because some week ago I tried with another one also, Camera 2 Probe, the one you were speaking now, but it's always the same... It says 15, I've 10 (or 11, as you), it says 30, I've 14,7something.

Maybe, but I'm not sure, there's a bottleneck somewhere (Ram? Processor?), so you have the software but not the hardware. Probably, with an octacore or 6 GB of Ram we had somethink more. I could fix a lower fps, for example a 10 for a 720*480 (where I have 15), so I understand if something listen to me... but more then this, If you have not some other idea, I don't know, and I'm not sure it could depend from us.
[Upgrading, Modifying and Unlocking] Lukas+:
Maybe I don't understand, even because I've not much time, but if you digit "fastboot reboot fastboot" and you find yourself in recovery, so you're write. Ask someone else, but I think I remember you're write so, and that is the famous fastbootd. Then you do what you have to do and then you decide for rebooting via shell or via hardware buttons. I don't think is strange if you are in recovery after a "fastboot reboot fastboot".
[Upgrading, Modifying and Unlocking] linusuli:
Dear friend, I have a comprehension problem and I often work with the test + hit. That's why I didn't understand that the screen where to write "fastboot flash system ..." was where a menu came out. I understood that it had to be the black screen with small print in Fastboot mode ... I'm sorry. I use google translator to understand what you are explaining here.
[Upgrading, Modifying and Unlocking] linusuli:
Now I'm trying to find a way to unlock fbe to install the Gapps ...
[Upgrading, Modifying and Unlocking] Lukas+:
If you are with Android 9 Cubot KKM1 you flash system partition in fastboot, more or less where you was saying, while if you have Android 10 Cubot KKM2 you need to be in fastbootd mode. This change is through Android 9 and Android 10 devices out of the box, and everyone has been confused by this, not you only.

However, if you've got, there, platform tools 31 or latest (I've not here, now), with fastboot help you can access the meaning of every command and there is also one that tells you if you are in fastboot or in fastbootd.

For fbe there were something to flash in fastboot? Or it was a command option? I don't remember well, but @birdbird certainly knows, if we can disturb him.

If I can ask, which Custom Rom did you choose?

PS

What's test + hit? I don't know.
[Upgrading, Modifying and Unlocking] linusuli:
hello, good morning, I have kkm2. I've tried LeOS, LineageOS, Havoc (I think) and | e |. They all have one thing in common with the inability to access Gmail, either through microG or the Play Store app. Those who play play store say that the mobile is not certified and those who enter through microG or third-party Goggle app receive it as an attack and will not let you in. Test + hit means I try to do the things until they come out well. I don't know if I explain well.:unsure:
[Upgrading, Modifying and Unlocking] linusuli:
What is really impressive is how strong this kkm2 is. For all the bull**** I do, he has only bricked once ...:ROFLMAO::ROFLMAO::ROFLMAO::ROFLMAO::ROFLMAO::ROFLMAO:
[Upgrading, Modifying and Unlocking] linusuli:
This is a copy of all the fastboot commands I've been able to get from other people ...

adb reboot bootloader

fastboot flashing unlock

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot reboot fastboot

fastboot flash system SYSTEM.img

mes:

- under developer options enable oem unlocking

- adb reboot bootloader

- fastboot flashing unlock

- fastboot flashing unlock_critical

- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

- fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img

- fastboot reboot fastboot

fastboot delete-logical-partition product

fastboot flash system system.img

fastboot reboot recovery

format in TWRP

mes:

fastboot devices

fastboot --disable-verification flash vbmeta vbmeta.img

fastboot reboot fastboot

fastboot getvar is-userspace

fastboot erase system

fastboot delete-logical-partition product_insertslothere

Example

fastboot delete-logical-partition product_a

fastboot delete-logical-partition productb

fastboot flash system system.img

fastboot reboot recovery

mes

adb reboot bootloader

fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img

fastboot reboot fastboot

fastboot delete-logical-partition product_a

fastboot delete-logical-partition system_ext_a

fastboot erase system

fastboot flash system system.img(dynamic gsi ROM flash)

fastbo -w

fastboot reboot

Twrp recovery does not work properly for us, so some of these commands will not work well.

the word "mes" means more.
[Upgrading, Modifying and Unlocking] Lukas+:
Hi man, good morning too. I had Lineage, Leo's and Corvus. I've not been able to install gapps in Lineage, and then I decided for Corvus instead of a "ready for" Lineage. There should be a Lineage for you: for example, I've not been able to install gapps via sideload on Lineage, but I also made one or two tries only.

I can ensure you that with Corvus Os, Magisk and Micro-G everything is write (I did it), and you can also buy applications on play store and so on (internet banking), Gmail, even if I skipped for Lightning email (by Edison) where I can add and delete my Gmail account folders better then with Gmail.
[Upgrading, Modifying and Unlocking] Lukas+:
After

fastboot flash boot boot.img

I think is better

fastboot boot boot.img

or it's possible you loose the new flashed partition for a reason I don't remember, but really it could happen.

fastboot getvar is-userspace

tells you if you're in fastboot or fastbootd (no or yes: the command I was writing in the other post).

You use also commands I never used.

The Play services problem I'm sure you will solve easily, even if without TWRP is more difficult and maybe, maybe, Magisk + Micro-G way is easier, but this is opinion and habit.

Time ago I used SuperSu, and was a most stable system, but if everyone is using Magisk there is a reason, and at the end I also skipped to.

Fastboot -w

after

fastboot flash system system.img

I've never saw it, but it's interesting. I usually do:

fastboot -w

fastboot reboot fastboot

fastboot erase system

fastboot flash system system.img

fastboot reboot

The SPflashtool from Cubot site doesn't work for me too. You have to download another, even if a bit older.
[Upgrading, Modifying and Unlocking] linusuli:
Hi,

I use a flashtool for Linux ...SP_Flash_Tool-5.1916_Linux

The problem with the custom roms I've used is that the internal storage is locked and even though it works I don't keep anything I do. But I also know that the stock rom is not so bad ...
[Upgrading, Modifying and Unlocking] linusuli:
Ah! I see, make a boot patch with magisk and install from the flashtools ... and then you have access to internal storage ?, thank you.
[Upgrading, Modifying and Unlocking] linusuli:
Twrp does not work well on kkm2, Do not format date ...is encrypted and does not allow gapps to be installed.
[Upgrading, Modifying and Unlocking] gfsLuc:
Anybody compared Stock Rom vs custom ROM?

How about battery life and system fluidness?

Which custom works best for the KKM2?

Thanks in advance
[Upgrading, Modifying and Unlocking] linusuli:
hello, good morning, I have kkm2. I've tried LeOS, LineageOS, Havoc (I think) and | e |. They all have one thing in common with the inability to access Gmail, either through microG or the Play Store app. Those who play play store say that the mobile is not certified and those who enter through microG or third-party Goggle app receive it as an attack and will not let you in. Test + hit means I try to do the things until they come out well. I don't know if I explain well.:unsure:

unfortunately i think the stock rom is already good enough. I have not found any fully operational custom ...
[Upgrading, Modifying and Unlocking] linusuli:
Better wait for more opinions, I think there are people who know more than me. If instead of posting a post, you answer someone, they will know and answer you. if you don't have to wait for someone to look at the thread. thanks.:)
[Upgrading, Modifying and Unlocking] x53:
I'm sorry, I disagree. TWRP works well and it's possible to use unencrypted data partition. I'm using it right now to backup and restore data partition.

@fiftytwo: fastboot flash system ../LeOS-R-RW-a64-bvN.img.xz can't work. You have to flash extracted img not the packed xz.
[Upgrading, Modifying and Unlocking] linusuli:
thank you very much X, and how is that possible? how is it done?
[Upgrading, Modifying and Unlocking] fiftytwo:
x53, that did it, I can't thank you enough. The last time I did some flashing was with Samsung Phones (Galaxy S6, which overheated some months ago...) and before that my loved Galaxy S4 Mini which just became too slow. I worked to get to know the hows and dos and don'ts for the KKM2 for the last two or three months from time to time when I had the time. Thanks to you I got the small, google-free phone I wanted. Gonna check it out now.

Thanks again, I owe you one.
[Upgrading, Modifying and Unlocking] linusuli:
Custom rom system-roar-arm32_binder64-ab-vndklite-gogapps.img you don't have a device certificate to run the play store ... when you want to sign up for your google account you get this warning.
[Upgrading, Modifying and Unlocking] linusuli:
Havoc (A10) play store port installed, you can register, but it doesn't download apps or play store updates ... the navbar buttons only work the go back triangle.
[Upgrading, Modifying and Unlocking] linusuli:
Bliss-2019-04-11-arm64-ab-stock.img , these stay in fastboot, don't start.
[Upgrading, Modifying and Unlocking] linusuli:
please X53 what twrp do you use that goes so well ... thanks.
[Upgrading, Modifying and Unlocking] x53:
@linusuli: I've answered your question already. Look at post #372 at page 19.
[Upgrading, Modifying and Unlocking] linusuli:
thank you my friend..:)(y)
[Upgrading, Modifying and Unlocking] gfsLuc:
I wrote with Cubot support, they told me that this is not KKM3 -> They'll launch a Kingkong Mini 2 Pro soon. But battery life would be the same :-(
[Upgrading, Modifying and Unlocking] x53:
@Lukas+ I've tried Open Camera and Camera Raw (an Open Camera Fork). With both you can set video format to 3GPP (gear-symbol -> video-settings... -> video-format). With that both apps popup the message "1920x1080@30FPS (3gp)". That would be nice. But after recording MediaInfo says as always 12FPS. But at another forum someone said it will work with both apps and the 3gp setting. Maybe he tested it with KKM1 (Android 9). Would you do a test please, again? I did the recording with my KKM2 under lineageos 18.x. Maybe with stock it works?

@gfsLuc : Cubot's facebook site says cubot pocket?
[Upgrading, Modifying and Unlocking] linusuli:
unfortunately not doing this from twrp but i have installed system-squeak-arm32_binder64-ab-vndklite-gogapps-secure.img and everything seems to be working fine, even google play.
[Upgrading, Modifying and Unlocking] linusuli:
Hi again, with twrp I didn't get anything. But I found this rom system-squeak-arm32_binder64-ab-vndklite-gogapps-secure.img rom which I think is pretty good. With google play and all. I need to put the sims and see how it goes.View attachment 5576523View attachment 5576525View attachment 5576527
[Upgrading, Modifying and Unlocking] Lava79:
@linusuli : I use this rom : https://xdaforums.com/t/unofficial-lineageos-r-mod-lir.4237683/page-9

Based on Lineage and everything works fine since I installed it for a few months.

You need to download the Gapp's version included.
[Upgrading, Modifying and Unlocking] linusuli:
Well, at the moment I'm back in stock rom. the ringing sound distorts a bit and I don't know if it's my device that looks like the nav-bar doesn't work square and round. otherwise pretty good.
[Upgrading, Modifying and Unlocking] Cobus089:
Note to moderators : we have been polluting the Kingkong Mini / Kingkong Mini 2 thread with news, speculations and comments on the Cubot Pocket since April 23rd.

I think, both KKM / KKM2 and Pocket lovers would benefit from a split of the thread…

Cobus.
[Upgrading, Modifying and Unlocking] Timmmmaaahh!:
Hi! Please make this request here: *** New Device Forum Requests ***

I suggest adding a few links to show examples.

Moderators can't create and don't decide on forum sections.

Kind regards

Timmy

Senior Moderator
[Upgrading, Modifying and Unlocking] TNSMANI:
I have moved the posts relating to the Pocket HERE. You can continue the conversation there. As and when development takes place for this device, you can make a request for a new forum as described by my colleague @Timmmmaaahh! above.
[Upgrading, Modifying and Unlocking] Cobus089:
Request posted ! Thank you Timmmmaaahh! !

Thank you for the move TNSMANI !

Too late about the request (already made ! :LOL: ) !
[Upgrading, Modifying and Unlocking] birdibird:
I see that there are all kinds of instructions floating around in this thread with all kind of extra commands that you do not need to use at all.

Here is my comprehensive HowTo for our King Kong Mini 2:

For the KKM2 we need a A64 or A64binder32 image.

It can be either VNDK or VNDKLITE.

VNDKLITE is only needed if you want to use a read/write system.

If you use a systemless root version, e.g. Magisk, you do not need VNDKLITE necessarily but you can always choose it if you want.

I am using LeOS Android 12.1 on my kkm2 as I want to be as degoogled as possible.

https://leos-gsi.de/

Because it is so light, the battery time is quite good.

- download and unpack the gsi.img.xz file you chose

- put the unpacked .img together with the vbmeta.img file (attached below) in e.g. your home folder

- in Linux make sure the android-tools package is installed, in Windows make sure platform-tools is installed

- Boot into your phone, go to settings, about phone and tick 7 times on build number. Developer options will be activated

- In settings again there will now be Developer options (probably under system). Switch on OEM/bootloader unlocking and USB debugging

- connect your phone with the cable to the computer

- open a terminal or command prompt in the folder of the .img files and tick these commands:

- adb devices

(the phone should give a message to trust the computer)

- adb reboot bootloader

(phone reboots into bootloader/fastboot mode)

- fastboot flashing unlock

(you will be asked on the phone to confirm unlocking it)

- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

-fastboot reboot fastboot

(phone reboots in fastbootd mode)

-fastboot flash system GSI-VNDK(lite)-a64-bvN.img

(on the phone choose):

-Enter recovery

-Wipe data/factory reset

-Reboot system now

That's all.

when upgrading your gsi, you only need to flash system again in fastbootd and don't need to data/factory reset (dirty flashing). Sometimes this also works between gsi's, but not always.

(ps:

you can skip the adb part by booting into bootloader/fastboot mode:

-hold volume up button while long pressing the power button on the phone

-in the little menu move with volume up to fastboot and select it with volume down)

It is known that with some PHH based gsi's the sound sometimes crackles a bit on some Mediatek devices. It is not yet clear what causes it.

I am playing around with these settings, somehow the crackling is being influenced by the brightness settings. The weird thing is that on our KKM1 with LineageOS A11, we don't have these crackling problems. Please share your experiences with this.

Phh Treble settings

Misc features

tick:

-Use linear screen brightness

-Force Enable Camera2APIHAL3

-Bluetooth workarounds / Mediatek

in developer options I changed:

-Animator duration scale .5x

happy flashing!
[Upgrading, Modifying and Unlocking] x53:
What do you mean with "crackling". I know KKM2 speaker and ear peace is not the best and not loud enough compared to my previous mobiles. Especially the speaker at loudest setting is opaque and almost useless in noisy environments. And you think I can do something about it using your mentioned settings, e.g.

-linear screen brightness

-Force Enable Camera2APIHAL3

-Bluetooth workarounds / Mediatek

-Animator duration scale .5x ?
[Upgrading, Modifying and Unlocking] moonraver:
I have to confirm that LEOS's GSI are absolutely great! I tried A10, A11 and now I have A12 June updated version (based on AOSP) installed on my KKM2. With A12 May version I had 6-7 days battery life (phone calls, sms, navigation and some music).

I'm having only 2 problems with LEOS ROM:

1. appearance of clock on lockscreen is wrong with all A10 and A11 ROMs (lineage version included). The sign that separates hours and minutes (":") is shown as "?" or crossed rectangle. In A12 ROMs there is no problem with lockscreen clock.

2. KKM2 has only USB-C port and no audio jack. I bought 3 types of "USB-C to audio jack" dongles and none of them work for calling (playing music with dongles works well). When I try to make or receive a call via any dongle and earphones, I can not hear anything. Switching to speakerphone and back it makes a loud echo of myself in earphones. On stock A10 ROM everything works perfect. I wrote this problem to LeOS creator and he said that it is a general problem with USB-C drivers in GSI ROMs. Stock ROM have better solution for drivers in this case.

3. as mentioned before - camera in video mode still gives about 15 fps, no matter if there is sunny weather, forced 30 fps, manual mode or Camera2API enabled. I have tried many camera apps with Stock Rom, Lineage or LeOS and results are still the same. Maybe there is a problem with camera device itself. I think front camera gives a little bit more fps. Actually I use HedgeCam2.

4. back speaker for calls is still weak - it needs some boost option. I don't use earpiece and still haven't found any app that can help with this.

BTW: I made update from May to June version as mentioned above (without wiping anything) and everything seems to work fine. Only some apps are requesting for permissions again. So just:

- adb devices

- adb reboot bootloader

- fastboot reboot fastboot

- fastboot flash system LeOS-xxxxxxxxx.img

- fastboot reboot

Done.
[Upgrading, Modifying and Unlocking] birdibird:
I think you misunderstand, I am not speaking about the speaker quality.

When notifications come in sometimes it is a clean notification sound and sometimes it 'crackles' a bit.

Playing around with PHH settings can help, but it isn't fully clear yet what causes it. It is not only a problem on our device. This is a known problem with PHH based GSI's on some Mediatek devices.
[Upgrading, Modifying and Unlocking] birdibird:
FYI: you can skip the adb part by booting into bootloader/fastboot mode:

-hold volume up button while long pressing the power button on the phone

-in the little menu move with volume up to fastboot and select it with volume down
[Upgrading, Modifying and Unlocking] badcodelab:
fyi

update for stock rom

CUBOT_KINGKONG MINI2_A061C_V10_20220119

CUBOT_CUBOT_KINGKONG MINI2_A061C_V10_20220119_CUBOT Firmware

Cubot Offical Website for Smartphones and Wearables. Simple and Trust, Cubot aims to be a credit worthy high-tech corporation in the world.

cubot.net
[Upgrading, Modifying and Unlocking] birdibird:
For anyone who wants to upgrade to the lastest software of Cubot and has currently a GSI installed, follow these instructions:

-Download and unpack the rom (you will see a mt6761 folder)

-Download the patched lk, which I attached below, to the mt6761 folder (I removed the Orange State warning)

-Switch off your phone

-Open SPFlashtool

-choose the scatter file from the mt6761 folder

-untick super, cache and userdata

-doublecheck you unticked super, cache and userdata and there is written above "Download Only"

-click the Download arrow button to start

-plug the usb cable in your pc and phone, the tool will start flashing

-after flashing, take the cable out of your phone

-untick everything (tick left top box twice)

-double click after lk on the folder name and choose lk-patched.img

-the same with lk2

-check if only lk and lk2 are ticked and "Download Only" is written above

-click the Download arrow button to start

-plug the usb cable back into your phone, the tool will start flashing

-you will see a checksum error at the end, this is correct as I patched the file

-after flashing, take the cable out of your phone

-hold volume up button while long pressing the power button on the phone

-in the little menu move with volume up to fastboot and select it with volume down

(the phone enters bootloader/fastboot mode)

-open a terminal or command prompt in the mt6761 folder

-fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

-fastboot reboot fastboot

(phone reboots in fastbootd mode)

-fastboot flash vendor vendor.img

(on the phone choose):

-Reboot system now

done

ps, if you had Magisk installed, you will need to repatch the boot.img and flash it with spflashtool or fastboot
[Upgrading, Modifying and Unlocking] moonraver:
What do you mean "who wants to upgrade to the lastest software of Cubot and has currently a GSI installed"? If you want Cubot latest software just visit cubot download site, download image with appropriate software and follow their instructions - it is pretty simple. Did you mean returning from GSI to Stock ROM without loosing personal files or data?
[Upgrading, Modifying and Unlocking] birdibird:
If you have stock installed, yes, you can just upgrade with the new downloaded rom.

If you have a GSI installed, you cannot do that, as you will loose your GSI installation.

So, if you want to keep your GSI installation and want to upgrade everything else besides the system to the newest cubot version, follow my instructions.
[Upgrading, Modifying and Unlocking] moonraver:
Is it necessary to upgrade "everything else" to newest cubot version? What is it for and what is the difference? Thank you