yashsingh1/xdaforums huggingface dataset:
[Android Software Development] YuriRM:
GPIO pin numbers in the Circuit Board of EStar Takee 1

I hope there is a solution for camera bugs introduced by luckasfb in his latest kernel of EStar Takee 1.

Some KitKat kernels share both cameras (Sony imx135_mipi_raw and OmniVision ov5645_mipi_yuv) with EStar Takee 1.

However, it may be down to GPIO pin numbers in the Circuit Board. That is why I want to know the Circuit Board ID number, the physical address number of each component and GPIO pin numbers of camera sensors of those devices.

That info is included in the kernel source code of BQ Aquaris E5 FHD.

[MENTION=7386826]giotogo[/MENTION] can you find this information inside your EStar Takee 1 device, please?

Circuit Board ID number

GPIO pin numbers of camera sensors in the Circuit Board

Take detailed photos of internal components

Take detailed photos of internal numbers printed in the motherboard.

This information may help find other devices that share an identical Circuit Board ID number. This list of most compatible devices is useful. Hopefully, It will enable to choose the easiest Android 7.1.2 Nougat ROM to port into EStar Takee 1.

It also provides crucial information for changing the GPIO pin numbers of both cameras in the KitKat kernel source code of EStar Takee 1.

Bug in power for cameras GPIO pins in codegen - EStar Takee 1

https://xdaforums.com/showpost.php?p=79024675&postcount=1361

The video below shows how to open a device and find the Circuit Board ID number.

However, my guess is that it boils down to the physical address number of each component and GPIO pin numbers in the motherboard. This enables to direct each camera driver (front and back cameras) to a specific address in the Circuit Board (GPIO pin number). This is the info that luckasfb tried so hard to find, trying by hand hundreds of combinations for GPIO pins. He did not open the case of his EStar Takee 1 device.

How to Find and download Firmware file for chinese tablets

https://www.youtube.com/watch?v=XZqLoxpbUSA
[Android Software Development] YuriRM:
How to fix a bootloop after installing a Custom ROM like Viper OS

[MENTION=6026343]io2345[/MENTION] how are you doing? It has been a long time since we last talked.

I may have found a solution for the bootloop of the Viper ROM ported by [MENTION=5128870]Mik-el[/MENTION].

Can you test this method, please?

Have you watched this video by the clever german guy, Christoph Zahradnik ?

His Viper ROM is used in this explanation... Viper SC2_5.2.1.zip ?

How to fix a bootloop after installing a Custom ROM like Viper OS (07/03/2015)

By Christoph Zahradnik

https://www.youtube.com/watch?v=cgYXy2XC1SM

Below find what happened on the previous day.

HTC Sensation (Snapdragon S3) and Viper ROM - installing a Custom ROM and entering a bootloop (06/03/2015)

By Christoph Zahradnik

https://www.youtube.com/watch?v=-Snab4bsnzQ
[Android Software Development] giotogo:
Here is photos. i hope, you find what you want :)

https://ibb.co/3Nc72LG

https://ibb.co/NZpGbPm

https://ibb.co/Sf2bnL6

https://ibb.co/ygg1jWq

https://ibb.co/0sRmXKy

https://ibb.co/vqRcg8P
[Android Software Development] io2345:
Found the time today and tried the method via fastboot. Sadly to say, it doesn't change anything. Phone keeps bootlooping.
[Android Software Development] Mik-el:
[MENTION=6026343]io2345[/MENTION] [MENTION=7386826]giotogo[/MENTION]

I'm chatting with [MENTION=7119029]blacklisted.rock[/MENTION] on telegram. He said he'll send me a better porting guide.

Me and [MENTION=7147494]YuriRM[/MENTION] have already chosen a new and better rom to use as port rom.

The failed installation/ updater-binary errors were already solved in my last viperOS port.

Hopefully this time we'll get a booting Android 7 rom.

Regards
[Android Software Development] giotogo:
{Mod edit: Quoted post has been deleted}

why you need this damned phone?
[Android Software Development] snapss:
Hi everyone, I am also the owner of takee1.

I haven't used it for a long time, but when I saw that someone was doing something to bring it back to life, it gave me hope.

I would be interested in updating it with a more current rom, since 4.2 is no longer compatible with anything!

I hope it will be possible soon.

These Chinese continually churn out new models, but never firmware updates!....shamefull!
[Android Software Development] Mik-el:
June 2020 Updates: Rom ported! Now we need a recovery!

June 2020 Updates: Rom ported! Now we need a recovery!

Guys, I've really faced a lot of problems when trying to port this rom:

1) I had to wait 5 months to receive a working battery from China, thank you Corona Virus...

2) university... XD

3) porting guides on the web suck, I had to contact many people and study many articles and video guides... until I had to make

my own

porting guide...

4) some tools to extract boot.img files extract .img files, but with a wrong structure!! (and I discovered this just recently!)

5) I had to change the port rom, now I'm not using a ViperOS rom, but a RidonOS rom from a Micromax device much more similar to Takee 1 (more than 90%of the hardware is identical)

6) I want to thank you [MENTION=6026343]io2345[/MENTION] for helping me to test over 10 roms!! We had to exchange almost 100 mails to bring you a new and updated Rom!!

Anyway after all this FREE effort I think that I finally got a working Rom !! (correctly ported!!)

But we dhave another problem now...

We discovered that the custom recovery we use on Takee 1 (twrp 2.8.0.0. developed by [MENTION=4886266]luckasfb[/MENTION] ) is too old to support Android 7! We need a new custom recovery, probably a twrp 3.0 or above.

I've already researched new material and guides on the web. I found a guide that seems to clearly explain how to port a custom recovery to any device.

The process is simple, it consist in the extraction of the recovery from an Android kitchen in Linux, the rest is about replacing files.

Is this the end, or not?

Anyway the process is long and boring...

I'm quite busy with exams, life a few other projects...

I don't know if continuing this project is convenient for me at this point...

If someone wants to help me and [MENTION=6026343]io2345[/MENTION] please leave a message hereunder, I'll leave you links and infos about the recovery porting.

Cheers!
[Android Software Development] YuriRM:
A reward of 20 euro is awaiting your delivery of a fully working Android 7 ROM + custom recovery.

I expect [MENTION=6026343]io2345[/MENTION] to reward you as well:

Regarding TWRP-3.1 custom recoveries for EStar Takee 1, I did some porting attemps from 5-19 November 2017.

https://xdaforums.com/showpost.php?p=74410087&postcount=1201

https://xdaforums.com/showpost.php?p=74434705&postcount=1202

https://xdaforums.com/showpost.php?p=74482513&postcount=1203

https://xdaforums.com/showpost.php?p=74488944&postcount=1205

https://xdaforums.com/showpost.php?p=74540282&postcount=1206

https://xdaforums.com/showpost.php?p=74564282&postcount=1207

TWRP for BQ Aquaris E5FHD

https://twrp.me/bq/bqaquarise5fhd.html

Current version

twrp-3.4.0-0-vegetafhd.img
[Android Software Development] io2345:
Any news about the new Kernel?
[Android Software Development] Mik-el:
Here I am. Here's a recap.

1) Kernel Source.

I made a Repository on Github. The starting point is a kernel for BQ Aquaris E5FHD, which I forked.

As you know, I found a developer that offered their help. I sent to her the config.gz file from the Luckas and Valdjocker ROMs, she said the Luckas one is better. Then I lost contact with her cause for some reason she deleted her telegram account. Now she's back and we still have to keep talking about the kernel adapting process.

Anyway, I think that with a ready device three and ready vendor blobs, she'll be more interested in the project.

2) Device Tree.

Can be made by extracting some files from a device tree of a similar device on Github, or extracting some files from the stock ROM (in this case I think we'll have to use Luckas ROM since the original ROM has a 3.4.39 kernel and Android 7 requires 3.4.67).

Going for the 2nd solution, I found a guide on the internet that seems reliable. The steps can be applied starting from any GitHub Repo that contains Android Source code (I think I'll go with AOSP since it's smaller and more battery-friendly than LineageOS).

After this choice, I should reflash Luckas ROM on my device and extract the required files for the Device Tree, which I'll upload to another GitHub repo.

3) Vendor Blobs.

I found another guide. I have to extract vendor from the stock ROM (again the Lucaks one) and a device tree is required.

I'll upload these vendor files in another Github Repo too.

All my 3 Github Repos will have a link to the other 2 Repos.

So now we should finally have adapted kernel source + extracted device tree + extracted vendor + AOSP source code.

If the material is clean and organized, hopefully, any developer will be able to compile a ROM for Takee 1 form Source. :)

When

Unfortunately the time that I can dedicate to XDA is increasingly hard to find.

If anyone besides @io2345 wants to help with the extraction of the device tree and vendor, just let me know, I'll send you the guides and you could ask me questions in case you need.

About the 3D Porting

I run the 3D Takee apps on my Android 7 Rom copying a few obvious 3D libraries, but as expected, it wasn't enough.

I then decompiled the 3D apps with the help of the great @mozzafar alali , I reverse-engineered the required stuff and documented what I discovered on a .txt file.

Now I'll add and replace the files in my last Rom file and we'll see if holographic 3D works :)

Cheers to all of you!
[Android Software Development] mozzafar alali:
Great job.

Keep it up.

Best Developer
[Android Software Development] Mik-el:
Here's one of the projects that took the place of the Takee 1 ROM, lately.​

In March under the guise of a contest, I learned a bit about Unity and C#.

I made a video game that can be played in stereoscopic 3D on any monitor, without expensive 3D screens or glasses!

This post is still on topic here, since Takee 1 owners love 3D.

The Londoner developers of HoloSDK have done their evaluation... and my app is in the top 5!

Now to win and get first place, we need the public rating!

​

How to help me win with one click:

➡️Facebook : https://fb.watch/v/27m_uWtkO/

👉1 Like = 1 point

👉1 Share = 5 points

➡️Twitter :

https://twitter.com/i/web/status/1410915449756258312

👉1 Like = 1 point

👉1 Share = 5 points

Winning the contest would be awesome, not so much for the first prize (a super Alienware computer), but for the fact that it could open the way to new perspectives of work/collaborations with HoloSDK programmers! 😊

Let's spam the FB and Twitter links with our friends to get tons of Likes and Shares and win!✌

Thanks for your support. 🙂
[Android Software Development] Mik-el:
⚠️Warning! Do not flash any Takee 1 ROM before doing this or you'll lose the 3D effect forever!​

I discovered that every Takee 1 unit has a slightly different 3D screen, that's why every unit comes with its specific software calibration.

The 3D calibration is set in 2 files which you can find in the stock ROM that originally came with your unit.

You must backup the 2 calibration files of your original stock ROM before flashing any ROM, right now.

In the worst case, you could end up using calibration files shared by other users, but your 3D effect will be messed up.

So you must backup these 2 files:​

Internal memory -> "Android" folder -> "HolographyProfile" file and "Matrix" file.

If you have already flashed a custom ROM (files lost forever): don't worry. You could still find the "HolographyProfile" and "Matrix" files into the external MicroSD cards you used on your Takee 1. Backup:

External SD card -> "Android" folder -> "HolographyProfile" file and "Matrix" file.

That's it.

That's why the calibration files shared by @pogodancer caused a bad 3D effect on other devices! And that's why Takee 1 units haven't been touched by developers/3D enthusiasts perform better 😅😆

Update​

It seems to me that "HolographyProfile" is the only (and little) file required to calibrate the 3D screen. I noticed that if I delete the big "Matrix file" and I re-open any 3D app, the "Matrix" file gets regenerated every time.

So very probably "HolographyProfile" is the only calibration file, that would make sense!

Calibration Files shared by other users and I​

In the next post, I'm sharing with you an archive with calibration files from both my device and Pogodancer device. If you've lost your calibration files forever, you could test which one performs better, maybe you're lucky.

I also tried to edit the calibration files to try to manually adjust 3D calibration on every device and get the max from every one of them. (This could be the next level! 💪).

Unfortunately, the files are compiled and I didn't find any way to edit them, If anyone of you has experience with hex editors and programs to open strange file formats, could help in this sense.

Last words:​

Well, I've talked enough. Remember to do this:

1) backup the calibration files from Internal and External memory

2) share them on XDA

3) wait for my archive (pogodancer calibration and Mik-el calibration)

4) if you have experience in opening compiled files, try to open the calibration files and let us know

Cheers!
[Android Software Development] Mik-el:
A quick guide to adapt a compatible and more powerful battery on your Takee 1.​

LINK HERE
[Android Software Development] Mik-el:
​

FIX for error 5054 on SP Flash Tool​

Premise: Preloader and Bootloader are the same thing. If your preloader is corrupted, your phone won't even turn on the led and show the battery indicator on the screen when shut down and plugged to a power source.

I Just faced error 5054 again (corrupted preloader), I solved it by flashing the preloader again, I had to use a ROM backup I made with MTK droid tools years ago, because the Stock ROMs for SPFlashTools by Pogodancer (and their scatter files) do not include preloader.bin. (so once your preloader is gone, you can still save your phone, but not with a Pogodancer ROM).

Anyway, this is how I reflashed the preloader, any recent SP Tool version is ok:

Format tab > flags on "Auto Format Flash" and "Format whole flash except bootloader" > press Start ) I had to do this cause I was using a scatter that is different from the one on the phone, this step allows to "refresh" the scatter/partitions layout deleting everything on your phone, except preloader, if you can)

Download tab > flash only the preloader, and then flash everything except preloader. If your phone turns on its led and shows the battery image on the screen when plugged in, this means the preloader works and your phone is not dead anymore

if it doesn't work: Download tab > "Format all + Download". (basically SP tool will do "format all", "download preloader", "download")

Fix for corrupted Internal memory​

The only problem I have now with my Takee is that, for some strange reasons, the internal memory is almost completely full (just 7Mb free) and I can't even write on internal memory,

I think this has nothing to do with the preloader because it happened with 2 different stock ROMs (my old backup and Pogodancer one).

Android shows me a notification saying that the internal memory is corrupted and asks me if I want to format it to fix. I confirmed, Android formatted both internal and external storage, Now I can write on internal storage (hooray!) but still, the internal memory is almost full while I have nothing on my phone! (and I don't know why)
[Android Software Development] Mik-el:
Finally the Android 7 ROM with Holographic 3D support!​

Mik-el Android v. 3.0 --->Download<---​

⚠️Warning: Do not install this ROM before doing --->THIS<---, or you'll lose the 3D effect forever! (UPDATED)

​

Features:​

Holographic 3D with eye-tracking = working, but not totally as expected (keep reading!)

cameras do not work = this bug is inherited from the LuckasFB ROM used as the base. We tried to replace camera .so libraries with the ones from the stock ROM, but the stock ROM is based on a different kernel and these libs don't seem to solve the bug.

Everything else works perfectly, of course! 😁

​

How to test 3D:​

The ideal viewing distance is 50-55 cm.

The ideal viewing angle is 70°.

When 3D is working you'll see a sort of grid pattern showing on the screen.

If 3D looks flat, this means your calibration file "HolographyProfile" is missing, or you're using the wrong one for your device (again, read this).

Tilt your screen or your head to see if the 3D effect changes, if it works, this means that eye-tracking is working!

​

3D Apps included:​

3D gallery

3D models app: Holoshow

3D video player (stock version, already in ROM).

3D video player (by Mikel, you can download it from the bundle and use it to replace the stock one, here you can read the improvements).

Holohub

3D content included:​

3D Images

a new 3D video

3D models

​

3D libs included:​

this ROM includes all the required 3D libraries and their dependencies (which I discovered reverse-engineering the stock ROM)

the ROM also includes Airtouch libraries and Apks that could interact with the 3D apps

​

How to fix problems that could arise when using 3D Apps:​

Disabled Permissions:

Fix: Enable all permissions for the 3D apps​

Can't access 3D contents from External SD:

3D apps work, but they crash if you try to read files on the external memory.​

Usually, apps try to look for files on the external memory when they boot, so a crash is very probable.​

Why: they're apps intended for Android 4.2, Starting from Android 6, Google changed the way the apps handle reads and writes on the external memory. We're using Android 4 apps on an Android 7 ROM, and I can't even recompile them because they're closed source.

Fix 1: you can browse your 3D files on the external SD with Total Commander. When opening a file select the right 3D app, the apps won't crash!

Fix 2: use this Magisk module. (https://www.journeybytes.com/enable-external-storage-write-access-android-app/) 3D apps will detect the "modern" external storage as an "old" external storage. The module didn't work for @io234 and it caused a bootloop on his device, but you can test!

Missing 3D effect and eye-tracking

Fix 1: use the right 3D calibration files you backed up from your original stock ROM. Read more here

Fix 2: Test the stock 3D video player. If you don't like the 3D effect of the player, replace the player with my updated player (it is in the download bundle) and let me know. (You can only have one of them installed at a time!)

That's all folks, this is the 3D ROM, enjoy it, and let me if it works for you 😃😎​
[Android Software Development] Mik-el:
I made 3 Repositories on GitHub that will help you to build new Android ROMs for Takee 1 from Source.​

3 Organized repos for: Kernel, Device Tree, and Vendor Blobs.

I added information and links so anyone can easily "fill" these repos.

If you want to contribute to the Takee 1 source code, make a request on GitHub and I'll give you write access to the repos.

Link HERE
[Android Software Development] io2345:
Not really working for me: 3D-Player and 3D-Gallery close after startup with error message. The globe in HoloShow is visible, but doesn't move nor has a noticeable 3D effect. Is that only on my Takee, or do others have the same issue?
[Android Software Development] BareBeginner:
Hi, I'm using the latest ROM (3.0). I have an issue that WiFi-connections keep disconnected once they disconnect (by timeout or range). How can I set "automatic reconnect"? There is no tick-box for this when creating a new Wifi-connection.
[Android Software Development] io2345:
Welcome. You're probably right, I remember I had the same behaviour with 3.0

My solution was to go back to version 2.01 unrooted (as I don't need the 3D-stuff anyway).
[Android Software Development] Mik-el:
Hi, sorry for the late reply, and thanks for installing the ROM. I hope you backed up your 3D files! :)

I don't remember about this reconnection problem, I suppose you didn't find any option in the Advanced WIfi settings, right?

Otherwise maybe an Exposed module for automatic Wifi reconnection could exist, we could check.

Kind regards!

PS And thanks for subscribing to XDA and making your first about this Rom :D
[Android Software Development] Mik-el:
Today I talked with a friend about using home banking apps on custom Roms.

His suggestion:

1) Install Magisk 24 or newer

2) in Magisk, use the new Zygisk feature to hide root status (https://xiaomiui.net/how-to-use-zygisk-5640/) to the following apps:

home banking apps

the Magisk app itself

Hide Google play store and play services too!

3) remove safety net from your device using this magisk module (https://github.com/kdrag0n/safetynet-fix)

Home banking apps now working!
[Android Software Development] Mik-el:
EStar Takee 1 in 2023. A Quick summary.​

I'm making this post since the CES 2023 proved that 2023 will be the year of 3D screens, and people are getting interested in the Takee 1 again.

The last ROM for Takee 1 is Mik-el Android 7.1.2 version 3.0.

(This is the link for this XDA Thread with downloads, screenshots and a Youtube video)

The cameras don't work. 3D partially works.

Beside that... everything else works!

Includes air-touch and 3D libraries/ dependencies.

Includes all the stock 3D apps: 3D image Gallery, updated "Mik-el 3D VideoPlayer" and HoloShow.

3D apps will start, but random crashes may occur and the 3D effect is not working as well as the stock firmware.

Includes a tutorial app for 3D and air-touch.

(Stock 3D apps with dead servers, such as the 3D store, are not included to keep the ROM lighter).

It Includes other performance/longevity hacks of Mik-el Android.

My guide to port Android 7 to any Android 4 device is ready even if I haven't posted it yet.

The improved and unfinished new kernel for Takee is still on my Github here

Latest updates, never released, include: a patch to pass safety checks (thus allowing to use mobile-banking apps on this "magisk-rooted" ROM) and the updated "Mik-el 3D VideoPlayer" WITH WORKING 3D.

As you know, I can't develop stuff for this device anymore, but @io2345 put together and release some pieces I left to him before I stopped developing for this fantastic device.

For any info, suggestions, or anything, you can send me a message on Telegram or leave a comment here.

Thank you, Mik-el
[Android Software Development] Mik-el:
Hi YuriRM, recently io2345 wanted to thank my effort donating 10€, moreover he's also helping me testing ROMs on his device and he's following my instructions when needed
[Android Software Development] io2345:
After many attempts finally got TWRP 3.1.1.0 working on the Takee - find it attached (had to split it, as size exeeds 8MB, rename parts to .001 and .002). Probably not yet perfect, but installation attempt of Mikel's ROM succeded. ROM is working and shows Android 7.1.2 (Ridon ROM)

Congratulations to Mikel. He really made it !

Update : Files deleted, see Mikels Upload further down here
[Android Software Development] Mik-el:
I'm fu**ing happy!!

After 2 years of work we finally made it!!

Porting Android 7 to an Android 4 device is really a suicide! But, hey... Mission Accomplished!!

Thank you for helping me testing everything [MENTION=6026343]io2345[/MENTION]

[MENTION=7147494]YuriRM[/MENTION] ... about your last message... XD :D