• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Deleted post

Search This thread
Hello @Tsumetaay
Maybe you can use this? ruben15pdr found these when available on the Samsung site.
Samsung released files for 4.4 update:
There isnt anything related to the 4.4 update from samsung, same happened with the J4+. Even that it has T210 stuff, it will be useful... I'm setting up a VPS for 4.4 building with ProjectT110 tree on Github and soon i will start my tests.
 

TriDiscord

Senior Member
May 15, 2021
113
11
There isnt anything related to the 4.4 update from samsung, same happened with the J4+. Even that it has T210 stuff, it will be useful... I'm setting up a VPS for 4.4 building with ProjectT110 tree on Github and soon i will start my tests.
ProjectT110 device tree will soon be deprecated FYI
 

Jespert

Member
Dec 28, 2020
48
6
1. Closed souce CPU, we are basically working blindfolded
2. No official KK update from Samsung
3. Any AOSP roms on T210 (which shares the same hardware) have several bugs and stuttering
4. The low effort from the small community of devs for t110 because it is a "forgotten" device since launch.
Maybe we can work together with the active T210 devs to fix these bugs? Is it possible to request the source of the CPU?
 

adryyy

Senior Member
Nov 3, 2012
99
50
Here is a boot image with a newly build kernel, with GCC4.7 and the same initramfs for CM11. Also include the new compiled modules.

The kernel configs can be seen in the attached files.
I've managed to boot pmOS with these configs, and it works also for stock ROM, so it should be better to have as much options active as possible.
I've tested it and it still boot CM11.

Seems to be a bit more stable with this.

Source used.
 

Attachments

  • boot_cm_new_kernel_n2.zip
    8.8 MB · Views: 8
  • kernel_configs_used.zip
    17.6 KB · Views: 5
Last edited:
  • Like
Reactions: Jespert

adryyy

Senior Member
Nov 3, 2012
99
50
Ok, got updates:
🟩 Audio works, without volume control, just mute/unmute
🟩 Wireless works using command lines, it connects and load pages
🟩 Boot way faster now

📛Still can't get to make HW Acceleration to work, didn't tried yet with the new compiled kernel, the GEU and Galcore .ko are loaded so HW Acceleration should be manageable to work.

Seems to get IP allocation, but doesn't remain.
Code:
adb shell
su
/system/bin/load_prod_8787.sh
#Note: you need a network without password, e.g. mobile hotspot without password
iwconfig mlan0 mode Managed essid 'YourNetworkName'
netcfg mlan0 dhcp
mount -o rw,remount /system
echo "nameserver 1.1.1.1" > /etc/resolv.conf
dnsmasq -d

Updated CM11 TWRP backup in the same folder.
 
Last edited:
  • Like
Reactions: Jespert

adryyy

Senior Member
Nov 3, 2012
99
50
Ok, I've rebuild from source the ROM using I8200 repo files and Wifi board cfg. from LT023G.


I'll make a git with sources these days, maybe I'll be able to fix Wi-Fi at last.
 

TriDiscord

Senior Member
May 15, 2021
113
11
Ok, I've rebuild from source the ROM using I8200 repo files and Wifi board cfg. from LT023G.


I'll make a git with sources these days, maybe I'll be able to fix Wi-Fi at last.
That's amazing!!!! Will the repositories be on GitHub or GitLab?
 

adryyy

Senior Member
Nov 3, 2012
99
50
Ok.
I found this: https://github.com/orgs/T210-dev/repositories
Now it boots with hwcomposer.mrvl.so included, but doesn't load UI for some reason.
Settings and other apps opens with the hwcomposer lib.
Also, if Developer options -> Disable HW overlay is enabled, seem that the UI appears to works again.
 
Ok.
I found this: https://github.com/orgs/T210-dev/repositories
Now it boots with hwcomposer.mrvl.so included, but doesn't load UI for some reason.
Settings and other apps opens with the hwcomposer lib.
Also, if Developer options -> Disable HW overlay is enabled, seem that the UI appears to works again.
IIRC thats gr8nole's old repo, he couldnt get HW overlays to work since he dropped the project back in 2015/16.
getting other hardware stuff to work should be the top priority, since HW is mostly related to mrvl junk.
my attempts at fixing it just throws me at a glitched bootanim or the yellow bootlogo.
 

TriDiscord

Senior Member
May 15, 2021
113
11
I think we could fix that using https://github.com/boundarydevices/android-manifest/tree/boundary-imx-kk4.4.3-ga
as Nitrogen6X uses GC2000 with drivers compatible with the GC2000.
I've tried to push libs from kk443-nitrogen6x-20171213.img.gz but I think they are compilled a bit different, however, EGL works, load the driver for the GPU and give the 'proper' black screen, then surfaceflinger throw errors.
What are the errors? Also, if you could upload the repositories used to GitHub real quick, it would be much easier to help. Maybe even just a fork?
 

adryyy

Senior Member
Nov 3, 2012
99
50
What are the errors? Also, if you could upload the repositories used to GitHub real quick, it would be much easier to help. Maybe even just a fork?
I didn't compile or pull repo yet from boundary. Seems that ssh can't connect to their git.
However, I've found that Nitrogen6x line 41 uses gpu-viv/fsl-gpu.mk which are in fact the proprietary .so according to gpu-viv.

Here's the default.xml for their 4.4 build.
 

PanosT

Senior Member
Jul 20, 2020
83
4
I also have the device but I'm not a developer. Can I help you in any way?
 

adryyy

Senior Member
Nov 3, 2012
99
50
Hi! I've made some changes to the device tree, and I made a pull request. Please check it out.

Looks fine. I've merged them.
I've also modified MarvellWirelessDaemon so please sync.
Yet can't get wireless to work directly from Ui.
I send you an invitation.
 

adryyy

Senior Member
Nov 3, 2012
99
50
I thinks it's possible to use MESA driver as it includes Vivante GPU now.


It looks like there's active development, that's nice.

 

TriDiscord

Senior Member
May 15, 2021
113
11
Hey! I can't seem to be compiling CM11 without errors. Could you help me? They are mostly related to the actual source code itself.

EDIT: Nevermind, just had to edit some stuff!
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I've remember I've tried it a while ago, got CM11 booting in KitKat, 4.4, but it was laggy due to the incompatibility of graphic driver with 4.4.

    Some useful info:
    Here's TWRP 3.0 for T110 / T111:
    L.E: You find it in the links bellow.

    I've used @gr8nole TWRP for T210 to port it to T110 / T210, so thanks to his work.

    Flash it with Odin, remember to uncheck Auto Reboot. After flash, first time boot in Android, and then try to boot in recovery using vol up + home + power.
    It will take about 10 seconds to boot (black screen)
    Files I've still got from then:

    Here's backup of the SD Card I've used to flash the ROM and so on. It contains multiple boot image, which from what I've remember contains a combinations of modules from T210 boot images with the T110 boot images, also TWRP backup for CM11:

    I remember I've been trying to copy the libs from the KitKat build of the T210 in order to get the ROM to boot, copy, test, copy, test, using the ADB Debugger to read the logcat while booting, search errors, copy, test, rebuild from source, copy, test, and so on.

    Don't know if I've archived the source which I've used to build Android from source, but what I think I've used an modified the files that are provided from some users for T210:
    I'm sure you can find compatible ones with these search:
    Can't remember which git, exactly.

    I would like to get some new version of Android, even now, on this tab just to use it as casually split screen / same screen multiplayer gaming device.

    Also, ramdisk, can't remember what exactly I've done to it.

    You can find all tools you need to extract the boot image on the XDA, but probably on some old threads, can't remember what I've used. Or probably there are new and better tools to do so, like https://forum.xda-developers.com/t/...y-of-ota-images-from-various-vendors.4078159/ don't remember if I've used it or not.

    Links expires at end of year. If you want them again, ask via PM or replay. Also if the download is too slow for you.
    1
    Update: I've put all the info and files you need in that folder (Tutorial Install 4.4 T110).
    You need to flash boot4.zip in order to get the 4.4 TWRP backup to boot.

    Also, it will take like 2-5 minutes to boot up.

    It have adb debugging enabled during the boot-up, so you can connect USB cable and read adb logcat at boot if you want to resolve some errors, like wifi mediaserver, audio and so on.
    1
    Use adb logcat. It works well on my tablet. May be your USB cable.
    Also, would be nice to merge all these posts in one on the forums.
    I've uploaded a file with output of adb logcat if you can't get it properly. You can see various errors.

    Also, don't really know if the slow interface is due to some errors in grafic configurations or other errors that interfere and create lag.

    If you got stuck in recovery and have runStockRec on your SD Card, you can go to TWRP -> Advanced -> Terminal and type /external_sd/runStockRec then chose reboot system now . This should get you out from recovery bootloop.
    1
    Here is a boot image with a newly build kernel, with GCC4.7 and the same initramfs for CM11. Also include the new compiled modules.

    The kernel configs can be seen in the attached files.
    I've managed to boot pmOS with these configs, and it works also for stock ROM, so it should be better to have as much options active as possible.
    I've tested it and it still boot CM11.

    Seems to be a bit more stable with this.

    Source used.