[ROM][UNOFFICIAL] Testing LineageOS 14.1 Image for Dell Venue 8 3830

Search This thread

ptrtoptr

Member
Jan 23, 2019
8
2
Thanks a ton for this Rom. I have tried it on my Dell Venue 8 pro (HSPA+) and works fine. I am trying to integrate modem functionality as well so that the mobile network also works. Any pointers? Thanks again
 
  • Like
Reactions: pstglia

pstglia

Senior Member
Apr 21, 2019
53
55
Moto G5S Plus
Thanks a ton for this Rom. I have tried it on my Dell Venue 8 pro (HSPA+) and works fine. I am trying to integrate modem functionality as well so that the mobile network also works. Any pointers? Thanks again
Hi,

There are several steps you should consider to enable radio support:

I) I'd start reverting all commits did on device tree (device/dell/P801_NoModem) that disables radio features (commits 3c098608638930590225a7812fc8f5f786942f89, 998fa5f69272daa0ba8029e3a7e9214ca7298e81 and many others)

I suggest you take a look at Zenfone device tree on github as base (https://github.com/zenfone-legacy/android_device_asus_T00F) and use it as base to figure out which settings related to radio need to be enabled. Zenfone T00F (branded as Zenfone 5 in some markets) is a similar device in terms of SOC used (of course all other devices are different like sensors, wi-fi/bluetooth chip...)

II) After that, ensure you copy all necessary vendor libs/firmware related to radio from a stock rom to vendor/dell/P801_NoModem subdirs (editing also P801_NoModem-vendor-blobs.mk to copy them to right places)

III) You'll probably need to create shim's for vendor libs to work with nougat. Take a look at unresolved symbols and errors from logcat/dmesg to help on this.

IV) Mininal knowledge in programming (java, C, C++, shell script ) is required/welcome.

V) StackOverflow, Github and Youtube are your friends :)

Good luck!

Pstglia
 

ptrtoptr

Member
Jan 23, 2019
8
2
Hi,

There are several steps you should consider to enable radio support:

I) I'd start reverting all commits did on device tree (device/dell/P801_NoModem) that disables radio features (commits 3c098608638930590225a7812fc8f5f786942f89, 998fa5f69272daa0ba8029e3a7e9214ca7298e81 and many others)

I suggest you take a look at Zenfone device tree on github as base (https://github.com/zenfone-legacy/android_device_asus_T00F) and use it as base to figure out which settings related to radio need to be enabled. Zenfone T00F (branded as Zenfone 5 in some markets) is a similar device in terms of SOC used (of course all other devices are different like sensors, wi-fi/bluetooth chip...)

II) After that, ensure you copy all necessary vendor libs/firmware related to radio from a stock rom to vendor/dell/P801_NoModem subdirs (editing also P801_NoModem-vendor-blobs.mk to copy them to right places)

III) You'll probably need to create shim's for vendor libs to work with nougat. Take a look at unresolved symbols and errors from logcat/dmesg to help on this.

IV) Mininal knowledge in programming (java, C, C++, shell script ) is required/welcome.

V) StackOverflow, Github and Youtube are your friends :)

Good luck!

Pstglia
Hello. Thanks for such a detailed response. I will try and report if there is any success (though time is a constraint)! Let's see
 

pstglia

Senior Member
Apr 21, 2019
53
55
Moto G5S Plus
where from we can start from because i didn't find source tree and device driver nothing found and no android source code or any other rom
Hi

I) root your device and, using adb, copy config files , firmware files, init files, vendor files, kernel modules. I'd also copy entire /system directory

II) With rooted device, after a fresh boot, collect these using adb:
"dmesg" cmd
"logcat -d" cmd
"lsmod" cmd
"lsof" cmd
"mount" cmd
"df" cmd
"getprop" cmd
/dev files (at least list it - later I'll need to boot stock again to check certain files )
/sys files (at least list it - later I'll need to boot stock again to check certain files )
/proc files (/proc/asound/cards * others)

These will be important to compare with your custom boot generated info.
Specially on dmesg/logcat, you can figure out which error/warning messages are specific to your custom code and those that already logged with stock one.

II) You may start and environment (Android source + device tree) cloning my repo for 3830 (see 1st post)


III) After that, download kernel sources for your device.As I could check, you can download it from here:

Read all documentation available with it.

Note: These intel based devices do not boot custom images by default.
With these sources, they provide FW files to allow booting custom stuff.
You have to flash it using fastboot (documentation has some valuable information)

IV) adapt device/dell/P801_NoModem device tree to match config for your device (comparing with init & info you collected from your device)

V) At first I suggest you try to compile your kernel with no changes following instructions on documentation available with kernel sources you downloaded (some changes on build script will be required - you may use mine as reference [1]

VI) Be prepared to suffer with countless hours of debugging, attempts and pain! :)


Good luck!

[1] - https://github.com/pstglia/linux/blob/DELL_VENUE_LOS_14.1/kernel_build.sh
 
  • Like
Reactions: pkvce

pkvce

Member
May 27, 2015
28
2
Rohtak
Google Pixel 6a
Hi

I) root your device and, using adb, copy config files , firmware files, init files, vendor files, kernel modules. I'd also copy entire /system directory

II) With rooted device, after a fresh boot, collect these using adb:
"dmesg" cmd
"logcat -d" cmd
"lsmod" cmd
"lsof" cmd
"mount" cmd
"df" cmd
"getprop" cmd
/dev files (at least list it - later I'll need to boot stock again to check certain files )
/sys files (at least list it - later I'll need to boot stock again to check certain files )
/proc files (/proc/asound/cards * others)

These will be important to compare with your custom boot generated info.
Specially on dmesg/logcat, you can figure out which error/warning messages are specific to your custom code and those that already logged with stock one.

II) You may start and environment (Android source + device tree) cloning my repo for 3830 (see 1st post)


III) After that, download kernel sources for your device.As I could check, you can download it from here:

Read all documentation available with it.

Note: These intel based devices do not boot custom images by default.
With these sources, they provide FW files to allow booting custom stuff.
You have to flash it using fastboot (documentation has some valuable information)

IV) adapt device/dell/P801_NoModem device tree to match config for your device (comparing with init & info you collected from your device)

V) At first I suggest you try to compile your kernel with no changes following instructions on documentation available with kernel sources you downloaded (some changes on build script will be required - you may use mine as reference [1]

VI) Be prepared to suffer with countless hours of debugging, attempts and pain! :)


Good luck!

[1] - https://github.com/pstglia/linux/blob/DELL_VENUE_LOS_14.1/kernel_build.sh
Ok will do that today and can I also grab these files from update zip available on Dell open-source website for comparison
 

pkvce

Member
May 27, 2015
28
2
Rohtak
Google Pixel 6a
Hi

I) root your device and, using adb, copy config files , firmware files, init files, vendor files, kernel modules. I'd also copy entire /system directory

II) With rooted device, after a fresh boot, collect these using adb:
"dmesg" cmd
"logcat -d" cmd
"lsmod" cmd
"lsof" cmd
"mount" cmd
"df" cmd
"getprop" cmd
/dev files (at least list it - later I'll need to boot stock again to check certain files )
/sys files (at least list it - later I'll need to boot stock again to check certain files )
/proc files (/proc/asound/cards * others)

These will be important to compare with your custom boot generated info.
Specially on dmesg/logcat, you can figure out which error/warning messages are specific to your custom code and those that already logged with stock one.

II) You may start and environment (Android source + device tree) cloning my repo for 3830 (see 1st post)


III) After that, download kernel sources for your device.As I could check, you can download it from here:

Read all documentation available with it.

Note: These intel based devices do not boot custom images by default.
With these sources, they provide FW files to allow booting custom stuff.
You have to flash it using fastboot (documentation has some valuable information)

IV) adapt device/dell/P801_NoModem device tree to match config for your device (comparing with init & info you collected from your device)

V) At first I suggest you try to compile your kernel with no changes following instructions on documentation available with kernel sources you downloaded (some changes on build script will be required - you may use mine as reference [1]

VI) Be prepared to suffer with countless hours of debugging, attempts and pain! :)


Good luck!

[1] - https://github.com/pstglia/linux/blob/DELL_VENUE_LOS_14.1/kernel_build.sh
everything is downloaded and ready what will be the next step
 

pstglia

Senior Member
Apr 21, 2019
53
55
Moto G5S Plus
everything is downloaded and ready what will be the next step
As I mentioned, If you already configured your build environment to compile Android source code (II), I suggest you adapting your device tree fist (step IV)
You can get some hints here: https://forum.xda-developers.com/t/guide-how-to-make-a-device-tree-for-your-phone.3698419/

Keep in mind that this is not a "step by step" procedure. This doesn't exist here. Every device is unique, and requires lots of research and coding.

And just to be clear: The hints I pointed are just the very basic to build an Android image from "scratch".
Not for modding an existing img/package.
You should know a bit of C/C++, Java, Shell Scripting and be familiar with procedure to build AOSP/Lineage.
 

pstglia

Senior Member
Apr 21, 2019
53
55
Moto G5S Plus
Hi,
libhoudini and some other configs are already present on this image.

However, most apps area crashing. Crashes seems to be related to video/gpu related calls
If you are going to investigate, try focusing and debugging an arm app you want to work.
Maybe some overrides / shims need to be implemented...

Before you ask "can you do this for me?" the answer is no unfortunatelly :)
 

BrunoS2

New member
Sep 21, 2023
2
0
Hi,
libhoudini and some other configs are already present on this image.

However, most apps area crashing. Crashes seems to be related to video/gpu related calls
If you are going to investigate, try focusing and debugging an arm app you want to work.
Maybe some overrides / shims need to be implemented...

Before you ask "can you do this for me?" the answer is no unfortunatelly :)
Thanks for the fast response. I will see if I can make it work
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    where from we can start from because i didn't find source tree and device driver nothing found and no android source code or any other rom
    Hi

    I) root your device and, using adb, copy config files , firmware files, init files, vendor files, kernel modules. I'd also copy entire /system directory

    II) With rooted device, after a fresh boot, collect these using adb:
    "dmesg" cmd
    "logcat -d" cmd
    "lsmod" cmd
    "lsof" cmd
    "mount" cmd
    "df" cmd
    "getprop" cmd
    /dev files (at least list it - later I'll need to boot stock again to check certain files )
    /sys files (at least list it - later I'll need to boot stock again to check certain files )
    /proc files (/proc/asound/cards * others)

    These will be important to compare with your custom boot generated info.
    Specially on dmesg/logcat, you can figure out which error/warning messages are specific to your custom code and those that already logged with stock one.

    II) You may start and environment (Android source + device tree) cloning my repo for 3830 (see 1st post)


    III) After that, download kernel sources for your device.As I could check, you can download it from here:

    Read all documentation available with it.

    Note: These intel based devices do not boot custom images by default.
    With these sources, they provide FW files to allow booting custom stuff.
    You have to flash it using fastboot (documentation has some valuable information)

    IV) adapt device/dell/P801_NoModem device tree to match config for your device (comparing with init & info you collected from your device)

    V) At first I suggest you try to compile your kernel with no changes following instructions on documentation available with kernel sources you downloaded (some changes on build script will be required - you may use mine as reference [1]

    VI) Be prepared to suffer with countless hours of debugging, attempts and pain! :)


    Good luck!

    [1] - https://github.com/pstglia/linux/blob/DELL_VENUE_LOS_14.1/kernel_build.sh
  • 4
    Testing ROM for Dell Venue 8 3830 (LineageOS 14.1)


    Most of resources are available. But has some bugs.
    It could be used for fun (Retroarch, E-book readers, etc)


    Was build using as base Asus T00F lineage source files

    I'm posting here asking for help to implement/fix missing features (if anyone still interested on such old device)
    All source code to build is available on github (links bellow).


    Working
    Boots
    Display
    Touchscreen
    Wi-FI
    Virtual Navigation Buttons
    Sound
    Rotation
    Bluetooth (since 2023-05-10)

    Not working:
    Camera

    Known issues:

    - ARM apps not working due mismatches with libraries (Houdini)

    - Observed battery is draining quicker than expected.


    # Testing Image (should be flash using FASTBOOT)
    # updated 2023-06-13
    # WARNING: MAY BRICK YOUR DEVICE PERMANENTLY! USE AT YOUR OWN RISK!!!!


    Boot tablet in fastboot mode (volume down + Power) and use "flash_cmds.sh" (Linux) / "flash_cmds.bat" (Windows) to flash files through fastboot (note that proper driver drivers and fastboot must be installed)

    If you wish to submit cmds manually:

    fastboot oem start_partitioning fastboot flash /tmp/partition.tbl partition.tbl fastboot oem partition /tmp/partition.tbl fastboot erase system fastboot erase cache fastboot erase config fastboot erase data fastboot erase logs fastboot erase factory fastboot oem stop_partitioning fastboot flash dnx CLVP_CYAB_P801_FwDnX_vF9.6C_ww42_005.bin fastboot flash ifwi CLVP_CYAB_IFWI_vF9.6C_ww42_005_P801_wifi_uos.bin fastboot flash boot boot.img fastboot flash recovery recovery.img fastboot flash system system_img.img.gz


    Source Files


    # LOCAL MANIFEST


    Init a NEW repo
    (repo init -u https://github.com/LineageOS/android.git -b cm-14.1)

    Copy local manifest to .repo/local_manifests and sync it.
    repo sync -c --no-tags --no-clone-bundle -j$(nproc --all)


    # Kernel
    NOTE: must be build using gcc 4.7 [1]. Checkout commit c7931763d41be602407ed9d71e2c0292c6597e00, update prebuilts link to this gcc
    and build using kernel_build.sh script. If everything goes as expected, You'll have a new_boot.img created

    # device/dell/P801_NoModem

    # vendor/dell/P801_NoModem

    # hardware/libaudio

    # external/boringssl

    # system/core

    # external/tinyalsa

    # external/icu

    # external/external/apache-http

    NOTES:

    - openssl 3.0 (Mint 21.1 - Vera) will not generate a compatible x509 sign key for kernel modules.
    OpenSSL 1.1.1f generates an accepted key


    Credits / Thanks:
    - The LineageOS Team
    - Android-x86 Team / Chih-Wei Huang for the amazing project and repositories (used one of them here so far)
    - vampirefo for providing CWM recovery and valuable information
    - Social-Design-Concepts for providing unlocked firmwares (required to boot custom Image)
    - Fabio Júnior Chaves da Silva (again, owner of this tablet)
    - Dell for providing kernel source (wouldn't hurt to include some AOSP code also, but it's better than nothing )
    - AlaskaLinuxUser AKLU from Youtube. Lot's of explanations about Android & Lineage.



    [1] - https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.7/
    1
    When I flash this rom, I get to the Lock Screen and it hard freezes. Anyone else get this problem? Thanks for all your work @pstglia
    You are able to boot it but when locking screen you can't return to operation, having to boot it again.

    Is this your issue?

    If so, it's a known issue where backlight bright level goes to zero. If you blindly move the bright slider, you can have image again (or changing bright values bellow /sys using adb)
    1
    Wow, thanks for your quick reply! I was just dumb and didn't wipe my android 4.4 data before installing; that fixed it. I have been tinkering trying to get GAPPs installed but run into error 70 in CWM when I do. Have you had success?
    I have installed opengapps (x86, 7.1, pico). Don't remember having issues installing it.
    But makes tablet really slow most of time.
    1
    Thanks a ton for this Rom. I have tried it on my Dell Venue 8 pro (HSPA+) and works fine. I am trying to integrate modem functionality as well so that the mobile network also works. Any pointers? Thanks again
    1
    where from we can start from because i didn't find source tree and device driver nothing found and no android source code or any other rom
    Hi

    I) root your device and, using adb, copy config files , firmware files, init files, vendor files, kernel modules. I'd also copy entire /system directory

    II) With rooted device, after a fresh boot, collect these using adb:
    "dmesg" cmd
    "logcat -d" cmd
    "lsmod" cmd
    "lsof" cmd
    "mount" cmd
    "df" cmd
    "getprop" cmd
    /dev files (at least list it - later I'll need to boot stock again to check certain files )
    /sys files (at least list it - later I'll need to boot stock again to check certain files )
    /proc files (/proc/asound/cards * others)

    These will be important to compare with your custom boot generated info.
    Specially on dmesg/logcat, you can figure out which error/warning messages are specific to your custom code and those that already logged with stock one.

    II) You may start and environment (Android source + device tree) cloning my repo for 3830 (see 1st post)


    III) After that, download kernel sources for your device.As I could check, you can download it from here:

    Read all documentation available with it.

    Note: These intel based devices do not boot custom images by default.
    With these sources, they provide FW files to allow booting custom stuff.
    You have to flash it using fastboot (documentation has some valuable information)

    IV) adapt device/dell/P801_NoModem device tree to match config for your device (comparing with init & info you collected from your device)

    V) At first I suggest you try to compile your kernel with no changes following instructions on documentation available with kernel sources you downloaded (some changes on build script will be required - you may use mine as reference [1]

    VI) Be prepared to suffer with countless hours of debugging, attempts and pain! :)


    Good luck!

    [1] - https://github.com/pstglia/linux/blob/DELL_VENUE_LOS_14.1/kernel_build.sh