yashsingh1/xdaforums huggingface dataset:
[Touch Dual, MDA Touch Plus ROM Development] wmn79:
Installed your rom but it doesn't do the autoconfig after the initial startup. Even after a hard reset it doesn't do it. So I still have the green theme and no htc home. Rom is V2 by the way.

Is with toucflo also the scrolling removed because scrolling in Gmail email doesn't work. It only works with the scroll bar on the side. Not by using your finger in the mail message.

Update:

Just read your post and changed it in Today to HTC default and add the HTC home in Item. Now it looks like the pictures and works correctly.

One request: for the frequent flashers/testers it would be great if you can make the rom UC capable. You can learn how to do that here. It is quite easy though. To learn more on UC (user customization) check this post.

Thanx in advance.
[Touch Dual, MDA Touch Plus ROM Development] GlenH:
That wasn't there on the first post earlier. It's been edited since I asked;)
[Touch Dual, MDA Touch Plus ROM Development] Blackdragon_860:
yes glenh, you have right.

i forgott to post this..

sorry

and to all other peoples, test this rom.

i test it since 1 month and i doesnt have found one bug..
[Touch Dual, MDA Touch Plus ROM Development] kerrance76:
fair enough, sorry about that.

Blackdragon, another nice rom with no apparent bugs so far. And if you dont get any feedback look on the bright side, it must mean there is nothing wrong
[Touch Dual, MDA Touch Plus ROM Development] i486:
Again, excellent work, seems great so far... ;)

Only one tweak, make an 0 byte .txt and rename it to StartUpBiotouch.exe and place it in the ROM. Because the Cube is disabled, you don´t need to run Biotouch.exe in the background, and you will gain more ~ 5MB of disponible RAM.

;)
[Touch Dual, MDA Touch Plus ROM Development] Blackdragon_860:
hey @i486

very good tweak. thx very much. i would include this in the next rom.
[Touch Dual, MDA Touch Plus ROM Development] jarob10:
Has anyone had problems synchronizing with this ROM?

I can get WMDC to connect, but the syncing progress bar stay at 0
[Touch Dual, MDA Touch Plus ROM Development] neotekgeek:
NEON300

I'd like to test this ROM for you. Unfortunately I'm rather new to the flashing scene ... heh. I've searched high and low for an RUU that will allow me to install this. I'm not even certain if that's the right thing to do. I can only imagine there's some sort of shell installer (not certain if RUU is the correct nomenclature). If anyone could offer some advice on how to install this ROM, or even provide a link or a specific search I should do on these forums.

Thanks in advance!
[Touch Dual, MDA Touch Plus ROM Development] Blackdragon_860:
@neotekgeek

you must use this ruu:

http://xdaforums.com/showthread.php?t=356259

download it and put the file of my rom (nbh) in the same ruu folder..

then start the CustomRuu.exe

Dont forgett to put your niki in bootloader modus.
[Touch Dual, MDA Touch Plus ROM Development] neotekgeek:
Will try it now thanks!
[Touch Dual, MDA Touch Plus ROM Development] wmn79:
What device do you have a Niki or a NEON? Your title says NEON 300 if that is your device I won't try this rom if i where you. This rom is specially made for Niki.

Try one of the roms Seth did he makes them specially for NEON here is a link to the Seths' latest diamond rom for NEON: http://xdaforums.com/showthread.php?t=403436.
[Touch Dual, MDA Touch Plus ROM Development] neotekgeek:
Yeah, NEON300...

Thanks for all the assistance anyway!
[Touch Dual, MDA Touch Plus ROM Development] i486:
This is by far the best ROM available for NIKI(no ofence to the others, they are good too)...

Clean, stable(very stable build), no bugs(so far), without those pesky splash/boot screens(please keep it that way).

Just need to be a little cleaned of some unnecessary .exes and resources(.png, .jpeg, .bmp, .brn).

Just a tip, search on your dump/oem folder for .brn files, then delete them all. They are the resource files for the HTC Cube, so you will not need them. On the process you will gain about 10MB of storage wich is most welcome :D

There are some junk entries on the registry too, if you don´t want to work directly on hive/rgu files you can use an XML provision file to do it for you.

Just use on of the empty .provxml files in the dump folder, and add the correspondent changes. On mine I did this:

<wap-provisioningdoc>

<characteristic type="Registry">
<nocharacteristic
type="HKLM\Software\HTC\Biotouch"/>

<nocharacteristic
type="HKLM\Software\HTC\StratUpBiotouch"/>

<nocharacteristic
type="HKLM\Software\HTC\QuickDial"/>

<nocharacteristic
type="HKLM\Software\HTC\AudioBooster"/>

<nocharacteristic
type="HKLM\Software\HTC\EnlargeMenu"/>

<nocharacteristic
type="HKLM\Software\HTC\Streaming"/>

<nocharacteristic
type="HKLM\Software\HTC\TaskManager"/>

<nocharacteristic
type="HKLM\Software\Microsoft\Today\Items\Windows Live"/>

<nocharacteristic
type="HKLM\Software\Microsoft\Today\Items\Windows Live Search"/>

<nocharacteristic
type="HKLM\Software\Microsoft\Today\Items\HTC Home"/>

<nocharacteristic
type="HKLM\System\SQM"/>

<nocharacteristic
type="HKLM\Drivers\BuiltIn\SqmEngine"/>

<nocharacteristic
type="HKLM\System\Uptime"/>

<nocharacteristic
type="HKLM\Services\SqmUpload"/>

<nocharacteristic
type="HKLM\ControlPanel\MyCpl\12"/>

<nocharacteristic
type="HKLM\ControlPanel\MyCpl\25"/>

<nocharacteristic
type="HKLM\Software\HTC\HTCHome"/>

<nocharacteristic
type="HKLM\Software\HTC\AudioManager"/>

<nocharacteristic
type="HKLM\Services\LargeTitleBar"/>

<nocharacteristic
type="HKLM\Services\Windows Live"/>

<nocharacteristic
type="HKLM\Software\HTC\HTCAlbum"/>

</characteristic>

<characteristic type="FileOperation">
<characteristic type="%CE2%\Start Menu\Programs\Calculator.lnk" translation="install">
<characteristic type="Delete">
<parm name="ForceDelete"/>
</characteristic>
</characteristic>

</characteristic>

</characteristic>

</wap-provisioningdoc>

Continue your excellent work ;)
[Touch Dual, MDA Touch Plus ROM Development] Blackdragon_860:
hey i486

thx very much for your feedback. i waited a lot of something like this and now i can complete my rom.

i dont work more after this update (i test it and uploading it),

and will work to make a german one.

for the new update i have removed the *brn files and other not needet files. i dont have make changes at the registry because i dont like to change somethin that works good.

the rom is now 10mb smaller and i have pached the pagepool with 18mb.

i will write a feedback and post the update soon.

blackdragon
[Touch Dual, MDA Touch Plus ROM Development] Blackdragon_860:
people, can someone tell me why the things i change in my default.rgu and user.rgu file dont take changes on the phone.

i have converted the rgu's in hv files and it has no failures...
[Touch Dual, MDA Touch Plus ROM Development] chartreux:
perhaps you may take a look the 1st XIP section, there are default.hv and user.hv too. :D
[Touch Dual, MDA Touch Plus ROM Development] kerrance76:
New bug found:

Nothing serious but in comm manager when you change any of the settings the text is blurred, it looks like it writes the new text over the old text insted of removing it. I dont know if this is just your rom or a WM6.1 issue.

When you restart comm manager it is back to normal.

See screen shot
[Touch Dual, MDA Touch Plus ROM Development] Blackdragon_860:
@ chartreux

thx for your answer, but i dont understund what you means..
[Touch Dual, MDA Touch Plus ROM Development] i486:
What tools are you using to build the ROM? A complete kitchen(BuildOS + packages) or the IMGFS tools + G Reloc?

About the hive/rgu files, I sujest you to leave them stock, and then to modify/change something in it just use a .xml file with your modifications via UI AutoRun.

It´s the simplier/less bogus way... ;)
[Touch Dual, MDA Touch Plus ROM Development] chartreux:
yeah I'm agree with you.

Blackdragon_860: the HTC touch dual have 2 XIP section.

the one that you mod normally is the 2nd one.

but the 1st XIP more likely untouchable (.hv cannot be decode)

so the best you can follow i486 method or use MortScript/dotfred taskManger to remove the registry.
[Touch Dual, MDA Touch Plus ROM Development] Blackdragon_860:
ok, i have solved the problem on a other way..i will work on v3 on the next days...
[Touch Dual, MDA Touch Plus ROM Development] DaVince:
Haven't tried this yet.. but after reading the posts here.. I'd rather wait for the v3. Keep up the good work. :D
[Touch Dual, MDA Touch Plus ROM Development] Blackdragon_860:
@ daVince

you dont have reed right this thread..

scho what i486 say..

i dont know when i release v3, but when you woold a GOOD rom, you must test v2...
[Touch Dual, MDA Touch Plus ROM Development] RickCain:
I hate asking this but is there a link to download touchflo?
[Touch Dual, MDA Touch Plus ROM Development] TangerineTractor:
V2 Works brilliantly, but there is one BIG issue for me - the daller skin - it doesn't have a 'hide keypad' option, so it really loses the point of the slide if the keypad is on the screen as well. Tom's ROMS have the better dialler, as does Gollum's Throttle ROM, but I can't get any of the dual dialler cabs to install on this rom.

If you could update the dialler to one that shows the smartdial full screen when the slide is open, it would be perfect! If anyone has a cab that will do this, it would be a workaround!
[MTCD  Android Head Units Q&A] plugugly:
Hi all

I’ve recently bought a BMW E38 and it came with an android head unit. I’ve tried to connect to my iPhone to use it as a hotspot and it connects but only for a few seconds. Radios not working either but I think it’s not been fitted correctly.

I’ve tried researching online but can’t see any solutions. Really appreciate any help.

The details:

Model- PX5 (1024x600)

Android 8

MCU- MTCE_GS_V2.78_3

CPU- 8 core 64bit CPU coretex a53 @ 1.5g
[MTCD  Android Head Units Q&A] marchnz:
What did the reseller suggest and has that been tried with anything else?
[MTCD  Android Head Units Q&A] Zakotaa:
I had similar issue where HU's wifi turns off automatically after few seconds. Is your HU doing the same?
[MTCD  Android Head Units Q&A] BRS1878:
WiFi problems

I also have the same issue WiFi will either connect and disconnect repeatedly, or will just not find my network at all?? Either 4g dongle or tethered to iPhone. Although my phone will find the single and connect so I know they work so it must be something to do with the HU it’s nearly new running android 8.1. So far I’m stumped with finding a solution.
[MTCD  Android Head Units Q&A] Zakotaa:
mine turned out to be the antenna problem. If I take off the small wifi antenna then wifi stays connected. this has reduced the wifi range considerably. I know it sucks but only thing that has worked for me so far.
[MTCD  Android Head Units Q&A] Dev0882:
Yeah I’ve had the same issues with my unit, I find sometimes it stays connected if I power up the iPhone hotspot a few seconds before powering up the head unit. If I forget and the head unit powers on first usually it refuses to obtain an IP from the phone.
[Thinkpad Tablet Android Development] yener90:
Just disable the modules, the kernel wont build it anymore. It's also not urgently required.
[Thinkpad Tablet Android Development] Yahoo Mike:
Thanks for the neat suggestion.

I disabled signed module enforcement (CONFIG_MODULE_SIG_FORCE) so we can use stock modules. That means no need to update system or vendor partitions.

I left in *_SIG_ALL in the defconfig, so you can compile and sign modules if you really want to. But I haven't included any modules in the new update zip. If you've used the old version of the update zip, then restore stock boot, system and vendor images before using this new update zip.
[Thinkpad Tablet Android Development] Yahoo Mike:
I've released a new version. Main changes are:

rebased kernel to 3.18.120

merge CAF LA.UM.5.5.r1-05300-8x96.0

added DT2W

fixed "adb reboot". The rebase fixed it.

added a defconfig for LineageOS

included signed modules in zip file (including wlan)

I've updated the OP.

I've added a new (default) branch called msm-3.18.120 in the github repo: Yahoo-Mike/android_kernel_lenovo_x605f.

The camera auto-focus is still not working. I haven't looked at it. Lenovo have not released the source code. It looks like the P10 uses different cameras. The main camera is a hynix hi556 variant called: hi556_m10. I'll have a look at this soon. One of the ASUS Zenfone Max Pro (M1) variants uses the hi556. That might have a usable driver. There's also a new video driver for the hi556 (CONFIG_VIDEO_HI556) released by intel for the linux kernel.

If anyone wants me to rebase to 3.18.140, just ask.
[Thinkpad Tablet Android Development] Yahoo Mike:
Latest version fixes camera issues. Camera (Hynix hi556) is now recognised and autofocus works.

I copied the Hynix (eeprom OTP) code from the Lenovo Tab4 kernel source. The code in the P10 kernel source never worked - probably because the P10 was never released with Hynix hi556. The P10 uses OmniVision ov8856 (8MP) and GalaxyCore gc5025 (5MP). Whereas the M10 uses Hynix hi556 (5MP) and Superpix sp2519 (2MP).

This kernel is stable. I can't find anything wrong with it. I've tested it using stock ROM with no issues. So I guess it's safe to load up with the stock ROM (Android Pie)...at your own risk. Just be sure to backup the system & vendor images, plus the boot image in TWRP. You'll need these when an OTA comes along, anyway. The updater-script in the OTA will refuse to apply, because it won't recognise this kernel.

So until someone finds some issues with this kernel, I guess it's time to polish up some LineageOS code...
[Thinkpad Tablet Android Development] Yahoo Mike:
Two exciting announcements:

prima drivers added to staging

I've added prima drivers to the kernel github repository. It's used by the lineageos_X605F_defconfig to build the wlan.ko module (CONFIG_WLAN_PRONTO).

Lenovo released official kernel source yesterday

The official kernel source for the X605F and X605L has just appeared on Lenovo's support site.

I'll have a closer look over the next few weeks, but here's some preliminary observations:

it is released at msm 3.18.120. This is the stock kernel version. (Lenovo released 3.18.71 for the P10.)

there is only one download for both X605F and X605L. This might be good news.

the autofocus camera drivers for the Hynix appear to be included. I'll take a closer look.

kernel compiles without any changes. I haven't loaded it yet to test it.

edit: I've added the official source to the Yahoo-Mike/android_kernel_lenovo_X605F repo in the official-3.18.120 branch.
[Thinkpad Tablet Android Development] Yahoo Mike:
The opensource drop for the X605F from last week includes code for the kernel at msm-3.18.120. Surprisingly, it includes a defconfig for the P10. This confirms that the M10 (X605F/L) and P10 (X705F/L) are very similar.

I'm going to test Lenovo's kernel source on my TB-X605F this weekend. Is there anybody with a TB-X705F/L and the skills to build and test this code on their P10 ? PM me and we can coordinate.

The only differences I can see are:

m10_msmcortex_defconfig | p10_msmcortex_defconfig | Kconfig definition
----------------------- | ----------------------- | ------------------
| CONFIG_BATTERY_BQ27x00=y | drivers/power
CONFIG_CAMERA_TAB5_M10=y | | drivers/media/platform/msm/camera_v2
| CONFIG_CAMERA_TAB5_P10=y | drivers/media/platform/msm/camera_v2
| CONFIG_FOUR_PA=y | sound/soc/codecs & sound/soc/msm
| CONFIG_SENSORS_HALL=y | drivers/input
CONFIG_TP_MP_DIFF=y | | arch/arm64

The TP_MP_DIFF setting is used to load different firmware for the touchscreen drivers: one set for the M10s; another for the P10s.
[Thinkpad Tablet Android Development] greipfrut:
Deleted
[Thinkpad Tablet Android Development] Yahoo Mike:
Glad to hear it compiled for P10.

I use AnyKernel3 to inject the kernel for me. It can also load kernel modules, if you build any.

I use these properties in the AK3 mod script. Modify it to suit your purposes:

# begin properties
properties() { '
kernel.string=X605F kernel built by Yahoo Mike @ xda-developers
do.devicecheck=1
do.modules=1
do.cleanup=1
do.cleanuponabort=0
device.name1=X605F
supported.versions=9
supported.patchlevels=- 2020-06
'; } # end properties

Then in my script I copy the kernel to AK3 root directory and modules to ./modules/system/lib/modules directory (or vendor equivalent) & zip it all up.

# zip it all up, ready for installing in TWRP
# this zip will replace kernel, plus any modules you included (if any)
# don't forget to TWRP-backup boot, system and vendor images
# also good idea to copy /system/lib/modules/* and /vendor/lib/modules/pronto/*
cd ~/tools/AK3
zip -r9 update_X605F_kernel.zip * -x .git README.md *placeholder
adb push update_X605F_kernel.zip /external_sd/

Optionally, you can also create a "version" file with something like this (before zipping):

MY_KERNEL_IMG="$(pwd)/out/arch/arm64/boot/Image.gz-dtb"
MY_KERNEL_VERSION="$(make kernelversion)"
cd ~/tools/AK3

# create a "version" file
MY_ZIP_DATE=$(date +'%Y-%m-%d %H:%M:%S')
MY_BUILD_DATE=$(stat ${MY_KERNEL_IMG} --format=%y | cut -c1-19)
echo "**************************************************" > $MY_ANYKERNEL_DIR/version
echo "unofficial kernel for Lenovo Smart Tab M10 (TB-X605F)" >> $MY_ANYKERNEL_DIR/version
echo " version: $MY_KERNEL_VERSION"	>> $MY_ANYKERNEL_DIR/version
echo "compiled: $MY_BUILD_DATE"	>> $MY_ANYKERNEL_DIR/version
echo " zipped: $MY_ZIP_DATE"	>> $MY_ANYKERNEL_DIR/version
echo "**************************************************" >> $MY_ANYKERNEL_DIR/version
[Thinkpad Tablet Android Development] Yahoo Mike:
The Lenovo opensource seems to be working on the TB-X605F. The modules are also building and installing ok.

There is something odd about the device tree, so make sure you use Image, not Image-dtb.gz. When I used the dtb kernel, I kept getting the dreaded "Qualcomm HS-USB Diagnostics 900E" mode.

I'll add a "lineage-17.1" branch to the github repo. It includes an M10_lineageos_defconfig for building the kernel and modules, and wlan.ko source from CAF for Android 10:

June 01, 2020 LA.UM.8.6.2.r1-07600-89xx.0 msm8953_64 LA.UM.8.6.2.r1-07600-89xx.0.xml 10.00.00
[Thinkpad Tablet Android Development] Yahoo Mike:
I can get the dtb kernel to work by replacing the arch/arm/boot/dts/qcom/ directory from Lenovo's opensource with the same directory from the "msm-3.18.120" branch of the repo. It boots fine with the stock ROM and LOS.

The "msm-3.18.120" branch is based on the original P10 opensource from January 2019.

So yes, there is definitely something screwy about the dt blobs from the June 2020 codedrop.
[Thinkpad Tablet Android Development] dustofdeath:
Not sure if this would be a valid kernel or not - On the back it says model is TB-X605F. I

In settings it says hardware is TB-X606F and so is the software.

It's the m10 gen 2 tablet. I believe Mediatek chipset.
[Thinkpad Tablet Android Development] Yahoo Mike:
If you have the gen 2, then this is the wrong kernel.

Lenovo has published the TBX606F/X kernel.

The CPU-Z app from the playstore will tell you which SOC you have.
[Thinkpad Tablet Android Development] Yahoo Mike:
I added pstore/ramoops support on branch msm-3.18.120. I have no idea why Lenovo never configured pstore/ramoops in the first place.

The ramoops device will dump console-ramoops, dmesg-ramoops-0, pmsg-ramoops-0 into /sys/fs/pstore/.

I'll add pstore support to TWRP for the TB-X605F in the next update. I'll use this branch (msm-3.18.120) to build the kernel.

I'm hoping pstore will tell me why GSI images fail to boot when installed over stock Pie.
[Thinkpad Tablet Android Development] saizzou38:
Hello and thanks to all of you to invest so much time and effort. I'm not the best in this android world so forgive me if I ask something stupid :) Recently I got a Lenove Tab M10 TB-X605L and well I rooted it (with magisk) to use Linux on it. As I said I don't use android so much and I just got this product as present so when I saw this post I thought If I can put a new Kernel why not compile it with NetHunter Kernel and give it a try. After some effort (I'm not sure if it will work) I made the kernel. My problem is:

1st I rooted my Tablet with Magisk (as the same way you mentioned in another post) after the rooting I download twrp from google play. Till here all is good. Now:

TWRP is working when I boot it. But asks for a Password. I tried some swipe data, cache etc. but still I see that PASSWORD field. I can't pass it. (And when I pass it without Password I can't see the kernel neither yours nor mine)

I don't care what happens to my Tablet as I said I'm not a android user. I would even would try a crazy Idea even if its end with a dead tablet :D but I would really wanna check if the compiled NetHunter kernel works.
[Thinkpad Tablet Android Development] Yahoo Mike:
TWRP will ask for a password if you have a password, PIN or pattern set on your tablet, and/or your data partition is encrypted.

If you have a password or PIN set on your tablet, try entering that. If you had a pattern, try this.

You can unencrypt the data partition by reformatting it and then installing Disable_Dm-Verity_ForceEncrypt.zip (created by Zackptg5). Just be aware that this wipes all your data and breaks OTA updates. (Magisk also needs to be uninstalled before OTAs work.)

Remember: android recovery (twrp) uses the kernel in the recovery partition, not the boot partition.

So, where are you injecting your kernel?

If you are injecting your kernel into TWRP's recovery image, which kernel do you see when you issue this command?

adb shell uname -r

If you are injecting your kernel into the system ROM's boot.img, then you won't see your kernel in TWRP. You'll see the kernel with which twrp was compiled.

BTW...interesting project. Good luck. Let us know if you get it working.
[Thinkpad Tablet Android Development] 浅香ジュン:
Hi there,

I just compiled your kernel source you've uploaded on the Github (official branch) with m10_msmcortex_defconfig. Then, I flashed it to my device with anykernel 3, also included all modules, but the wifi does not work(It cannot be turned on). Before I flash it, my device was running well at the stock firmware, so I wonder what's wrong with my compilation.

After that, I also tried to compile the lineage branch, with lineageos_tbx605_defconfig. I flashed it to my device running well on AOSP 10(project treble), but the problem was same as the official source.

Could you please tell me that what's wrong with my compilation or how to compile it to work well? Thanks a lot :).

Jun ASAKA

2021/02/03 (CST)
[Thinkpad Tablet Android Development] Yahoo Mike:
It sounds like the wlan_pronto.ko module is not loading. That's why wifi is not working.

It might be easier to build the msm-3.18.120 branch with YM_x605f_deconfig. That should work.

It does not force module signature checks (CONFIG_MODULE_SIG_FORCE=n). So the stock wlan module (/vendor/lib/modules/pronto/wlan_pronto.ko) should load ok.

If that fails, check the kernel log (dmesg) for errors loading the wlan module. Let me know what the errors are.

official source

The stock wifi module won't work with the kernel from the official branch because CONFIG_MODULE_SIG_FORCE=y. You'll have to download the wlan source from CAF and build it with the same signature. That's a lot of work.

I also had some DT and dm-verity issues with the official source.

lineage-17.1

The lineage-17.1 branch includes the CAF wlan module (in drivers/staging/prima) for Android 10.0. I'm not sure why it's not working for you. Check the kernel log for wlan load errors.

The included CAF wlan module (and your GSI system) are Android 10. Your vendor is Android 9.0 or 8.1. Maybe there's a compatibility issue ? I'm guessing. I haven't tried that kernel with a GSI ROM.
[Thinkpad Tablet Android Development] 浅香ジュン:
It's working! thanks a lot！
[Thinkpad Tablet Android Development] uschipower:
Would you be so kindly and build the kernel for TB-X605L too?

Chipset is SDA450

I am using LOS 20 Treble GSI from AndyYan on the device. Both Cameras do not work.

Thanks a lot.