yashsingh1/xdaforums huggingface dataset:
[Android Software Development] :
Well, if you can find the exact name of your touch input device you can blacklist it and there will be no more touch. Try to see with dmesg wich is it. Or you can try to blacklist more than one, just use in BoardConfig something like this

TOUCH_INPUT_BLACKLIST := "[COLOR="Red"]devicename[/COLOR]\n[COLOR="Red"]devicename2[/COLOR]\n[COLOR="Red"]devicename3[/COLOR]"

It should be a name like "bma156" or "bts753" or something else in this format.

BTW, thanks for ad-free gift. :)
[Android Software Development] DeadSquirrel01:
I've foundthis about your wrong orientation problem
[Android Software Development] :
That isn't a complete kmsg log it's just a part of it. You should use [ adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log ] and then to look for a line like this:

[ 42.865263]<0> (0)[147:mtk-tpd]<<-GTP-DEBUG->> [3081]pre_touch:00, finger:81, pre_key = 0x00, last_key = 0x00

In device I tested that is {mtk-tpd}, and to be sure I run [ adb shell cat /proc/bus/input/devices ] and I get the list of all input devices and the one I spoted is here too:

I: Bus=0000 Vendor=0000 Product=9147 Version=1040
N: Name="mtk-tpd"
P: Phys=
S: Sysfs=/devices/virtual/input/input3
U: Uniq=
H: Handlers=event3 gpufreq_ib
B: PROP=2
B: EV=b
B: KEY=200000000000400 0 0 40000800 10004000000000 0
B: ABS=263000001000003

The touch input devices have ABS events too and usually something starting with 263xxxx.

Look, this is from other phone:

I: Bus=0018 Vendor=0000 Product=0003 Version=2000
N: Name="synaptics_dsx_i2c"
P: Phys=synaptics_dsx_i2c/input0
S: Sysfs=/devices/bus.2/11008000.I2C1/i2c-1/1-0020/input/input2
U: Uniq=
H: Handlers=event2 gpufreq_ib
B: PROP=2
B: EV=b
B: KEY=420 0 0 100040000800 10168000000000 4400001460000
B: ABS=263800000000000

but in the second one the device is not a "generic" one, it is a "synaptic" device.

Your tablet being from old CPU generation may have that mtk-tpd device too, or not...

Anyway you should try only devices from this command [ adb shell cat /proc/bus/input/devices ] to not mess up with other things.
[Android Software Development] globula_neagra:
This is what I got, the 5th one looks like one of yours. This is what I should put in the board now ?

TOUCH_INPUT_BLACKLIST := /devices/virtual/input/input4

cat /proc/bus/input/devices
I: Bus=0019 Vendor=2454 Product=6500 Version=0010
N: Name="mtk-kpd"
P: Phys=
S: Sysfs=/devices/platform/mtk-kpd/input/input0
U: Uniq=
H: Handlers=event0 cpufreq
B: PROP=0
B: EV=3
B: KEY=80 180000 0 40000800 1c0840 0 0 0

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="ACCDET"
P: Phys=
S: Sysfs=/devices/virtual/input/input1
U: Uniq=
H: Handlers=event1 cpufreq
B: PROP=0
B: EV=3
B: KEY=80 0 78 0 40c0000 0 0 0

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="hwmdata"
P: Phys=
S: Sysfs=/devices/virtual/input/input2
U: Uniq=
H: Handlers=event2 cpufreq
B: PROP=0
B: EV=5
B: REL=2

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="m_acc_input"
P: Phys=
S: Sysfs=/devices/virtual/input/input3
U: Uniq=
H: Handlers=event3 cpufreq
B: PROP=0
B: EV=9
B: ABS=107

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="mtk-tpd"
P: Phys=
S: Sysfs=/devices/virtual/input/input4
U: Uniq=
H: Handlers=mouse0 event4 cpufreq
B: PROP=2
B: EV=b
B: KEY=400 0 0 0 2000000 1000 40000800 0 0 0 0
B: ABS=2630000 1000003

I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="mtk-tpd-kpd"
P: Phys=
S: Sysfs=/devices/virtual/input/input5
U: Uniq=
H: Handlers=event5 cpufreq
B: PROP=0
B: EV=3
B: KEY=2000000 1000 40000800 0 0 0 0
[Android Software Development] :
No, you need the name, like this:

TOUCH_INPUT_BLACKLIST := "mtk-tpd"
[Android Software Development] bigrammy:
[MENTION=1862539]globula_neagra[/MENTION]

Total guess here :eek:

I might be tempted to try Blacklist "mtk-tpd-kpd" first and see what happens. :confused:

Carliv will know better but I think mtk-tpd-kpd is for separate virtual and or physical Home Back & Menu buttons which are not needed in recovery. :confused:
[Android Software Development] :
Well, he wants to turn off the touch completely and so it has to be a device that produce ABS events (touch) not only keys.
[Android Software Development] bigrammy:
Hi carliv, I hope you don't think I was trying to interfere :o

You are 100% correct for disabling the touch altogether :good:

I was just reading through the posts and noticed he did get some touch response

This made me wonder if the recovery was using only the soft touch keys if that makes sense :laugh:
[Android Software Development] :
:laugh: No problem at all! Anyone who can help is welcome!

That post you read was about twrp. In my recovery touch works but is screwed up (touch up and the response is down). It seems that the swap touch recovery flags couldn't help and as someone posted on the other page a link, that was a problem in PhilZ recovery too for some devices -fixed only at kernel level, but I don't think he has access to kernel source.
[Android Software Development] DeadSquirrel01:
The old CWM hadn't touch support, but personally I prefer to use touch, so, I don't break my keys for pressing them too much times (thanks google translate for this comment)

---------- Post added at 08:18 PM ---------- Previous post was at 08:08 PM ----------

On internet i found this
[Android Software Development] bigrammy:
Thanks carliv I should've read further back :o
[Android Software Development] :
Yes, but that device is not on the list. Being a Mediatek powered one isn't a surprise.

No problem my friend, :) it happens to all of us. ;)
[Android Software Development] DeadSquirrel01:
[MENTION=1862539]globula_neagra[/MENTION]

If your device has cwm touch, I think u can use his kernel
[Android Software Development] globula_neagra:
I`v looked for some paths in terms of kernel. Archos is pretty rubbish at releasing the source code. The closest relative to this tablet is the Acer A3 A20 that has a MT8127 chipset but on this tablet a cwm was never achieved (not even what I have now) so compared to them I am pretty advanced. The Acer has the source code released and I was thinking if I could use the graphics.c from it to sort something out with my touchscreen. I will have a look when I have some days of.

@ DeadSquirrel01 To what kernel are you referring ? I don`t have a working CWM (it compiles ok but I get a black screen upon flashing), just TWRP and carliv where visible till now. carliv`s is fully functional besides the touch.

This tablet is really strange, I had some really strange outputs in terms of touchscreen, where just a region of it was working. it was inversed in all the possible ways and many more. Now I am trying just to get something working. Me personally I don`t need the touch so for me should suffice just the hard buttons.

The TOUCH_INPUT_BLACKLIST := "mtk-tpd" has not worked under TWRP, will try it tonight under carliv rec to see if I have better success rate:)
[Android Software Development] DeadSquirrel01:
[MENTION=1862539]globula_neagra[/MENTION] on the link I posted you can find

ARCHOS Generation 6/7/8/9... Source Code, but I don't know if they are for your device, too, since I never had an archos mobile and only one of my friends have an archos device
[Android Software Development] globula_neagra:
Gen9 are 2012-2013 devices. The rest even older.

I will try the kernel from the acer to see if the recover boots with it.
[Android Software Development] :
update

CHANGELOG 14-07-2016:

- add adopted storage support for marshmallow;

- fix zip and wipe menu;

- fix backup to internal sdcard

- other improvements.
[Android Software Development] BouyaPK:
Thanks for the update [emoji122]
[Android Software Development] DeadSquirrel01:
[MENTION=5186178]carliv[/MENTION]

Thanks for the update, now the data backup problem is solved :) .

And... for sideload, do I need an external SD card, because if i type "adb devices" I don't find my device. I see in your github page that I need the lun file path in ctr.fstab, to connect my device to my pc, but it's only for SD card, so, do I need an external SD card to use sideload or it's a device tree problem (you can find it here, if you want to take a look)
[Android Software Development] globula_neagra:
1) Sort the adb devices issue

You could try to add the init.recovery.usb.rc and init.whateverisyournameofthesoc.rc to your board or just unpack the stock recovery and copy them two files in the new one. Or you could just edit them, depends what suits you better. Anyway carliv mentioned in some porting posts of his how to sort this out.

2) adb sideload

The adb sideload command is to be used to load firmwares from your computer in the format of zip updates or full firmwares in zip format, is worth mentioning that if you activate adb sideload from your recovery some adb commands will not work, as the recovery get`s in this download state where is expecting a zip file to come not some random commands. With other words, the internal storage or any sdcard is not involved.

Is there anyone that has a cm11 build environment that builds older carliv recoveries ? I keep trying with mine but I get this

bootable/recovery/mmcutils/mmcutils.c:388:1: note: expected 'struct MmcPartition *' but argument is of type 'const struct MmcPartition *'

target asm: libpixelflinger_static <= system/core/libpixelflinger/t32cb16blend.S

bootable/recovery/minui/graphics.c: In function 'gr_fb_blank':

bootable/recovery/minui/graphics.c:542:15: error: expected expression before '/' token

bootable/recovery/minui/graphics.c:542:15: error: too few arguments to function 'open'

In file included from bootable/recovery/minui/graphics.c:22:0:

bionic/libc/include/fcntl.h:60:5: note: declared here

build/core/binary.mk:512: recipe for target '/home/globula/cm-11/out/target/product/ac101cpl/obj/STATIC_LIBRARIES/libminui_intermediates/graphics.o' failed

make: *** [/home/globula/cm-11/out/target/product/ac101cpl/obj/STATIC_LIBRARIES/libminui_intermediates/graphics.o] Error 1

make: *** Waiting for unfinished jobs....

make: *** wait: No child processes. Stop.

Can one of you waste 10 min and see if it compiles on yours ? the device tree is here https://github.com/globula/device_Archos_ac101cpl/tree/android-5.1
[Android Software Development] :
Here's your problem:

TARGET_RECOVERY_LCD_BACKLIGHT_PATH := /sys/devices/platform/leds-mt65xx/leds/lcd-backlight/brightnes

for older recoveries this should be:

TARGET_RECOVERY_LCD_BACKLIGHT_PATH := \"/sys/devices/platform/leds-mt65xx/leds/lcd-backlight/brightnes\"

escaping quotes.

[MENTION=7511870]DeadSquirrel01[/MENTION] your problem is drivers or udev rules related.
[Android Software Development] DeadSquirrel01:
[MENTION=7511870]DeadSquirrel01[/MENTION] your problem is drivers or udev rules related.[/QUOTE]

i use TWRP kernel. Here's my unpacked recovery.

[MENTION=1862539]globula_neagra[/MENTION]

Now I'm compiling :)

EDIT: now i compiled it, the size of recovery.img is 6.7MB (in kali linux) if you need it, i'll upload tomorrow or tonight on github, now i have to go out with my friends
[Android Software Development] :
No need to check the ramdisk or kernel, I said drivers (windows) or udev rules (linux)... in your PC to be more clear.
[Android Software Development] DeadSquirrel01:
I posted unpacked recovery.img because globula_neagra told me to insert 2 files, but when I use stock recovery and use sideload it works, now I try on debian
[Android Software Development] needromlatino:
Port MT6580M?

how I can compiled MT6580?
[Android Software Development] DeadSquirrel01:
To compile it for your device, you need a linux machine, cm12.1 or cm13 source, a buildable device tree and a recovery to unpack, then you can buid it by typing

1). build/envsetup.sh

2)lunch full_yourdevicename-eng

3)make -j# recoveryimage (change # with your number of cpu cores), or simply type make recoveryimage and u will find on out/target/product/yourdevicename a file called recovery.img

EDIT: [MENTION=5186178]carliv[/MENTION]

On debian sideload works
[Android Software Development] globula_neagra:
check under what pid id the phone appears in debian, it might be how carliv suggested just a problem of delete the old drivers and install them again

to list the usb devices use the command

lsusb

globula@glob:~$ lsusb

Bus 002 Device 040: ID 05dc:a81d Lexar Media, Inc.

Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 005 Device 003: ID 1038:136f SteelSeries ApS

Bus 005 Device 002: ID 2109:0811 VIA Labs, Inc. Hub

Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

if your usb id coincides with what you have in the init files in the recovery you should be fine and just need to adjust the windows drivers.
[Android Software Development] DeadSquirrel01:
Now works, on debian, probably it's a problem of wondows drivers

[MENTION=5186178]carliv[/MENTION]

Now that the recovery works fine, can I create a thread on galaxy A series section, obviusly i'll put u in credits :)?
[Android Software Development] danyldft:
[MENTION=5186178]carliv[/MENTION], thank you very much for recovery to speed 7 [emoji6] [emoji106] [emoji106] [emoji122] [emoji122] .

Enviado desde mi ZP951 mediante Tapatalk
[Android Software Development] DarkHeart Z:
Android one support will be added ? Glad to see you back man .
[Android Software Development] globula_neagra:
[MENTION=5186178]bluefirebird[/MENTION] why the name change, liked more carliv :)
[Android Software Development] :
Well, it is something I wanted to do for a long time but only now I thought it's the right time. I know there will be some adjusting time for those that know me as carliv but in the end I think it will be ok. When I was a kid I saw an animation movie (japanese) "Phoenix 2772" and I liked that very much. I used to draw scenes I remembered or imaginated from that movie years after. So I wanted to use firebird username but it is already taken so I added blue because it is my favorite color.
[Android Software Development] DeadSquirrel01:
[MENTION=5186178]bluefirebird[/MENTION] Now, that I found the time to upload the recovery you can add this to the second post. The recovery is for galaxy A5.

ah, personally I prefer this name to carliv, because birds are my favourite pets :). (I've got 2 canaries)
[Android Software Development] BouyaPK:
Next update Please add a Home button :o

thank you [MENTION=777546]carli[/MENTION]v [MENTION=5186178]bluefirebird[/MENTION]
[Android Software Development] bigrammy:
Just for Info

Hi [MENTION=5186178]bluefirebird[/MENTION]

I saw some guys have pre-build cm, aosp and other sources for direct download which could be useful for building the recovery without cloning the entire repo's.

The way I understand it we would only require the Non repo versions to build the recovery?? Can you confirm if this is the case as your understanding is greater than mine :confused:

Thread here http://xdaforums.com/android/software/sources-android-sources-highly-t3231109 :cowboy:

The thread is is been updated just now so some stuff has gone for the moment until they get it sorted.
[Android Software Development] kirito9:
I'm sure [MENTION=5186178]bluefirebird[/MENTION] will confirm that it can work and I can too. This is what I used to make my recovery builds. Keep checking that thread, it's getting better ;)
[Android Software Development] :
I personally didn't tried that way - I'm using full repo sources, but I'm sure it will work (this is the way mtk leaked sources work, because they don't use repo).

Only thing that has to be taken carefully is the method to unpack since this can break some symlinks and permissions (try to use tar or tar.gz archives).
[Android Software Development] bigrammy:
Thanks for the replies and tips :good:

This will save me a good few gigs of space and also time :D

I will give it a shot on my next set of days off work :fingers-crossed:
[MENTION=5186178]bluefirebird[/MENTION] I notice Jiayu have released the full source Kernel, Device and Vendor codes for the mt6752 mt6753 5.1 and 6.0 just incase it got past you :laugh:

https://github.com/MediatekAndroidDevelopers
[Android Software Development] kirito9:
I thought they were gonna keep it to themselves :P and that thread also has a way of unpacking the tar.gz file. I got an error while unpacking Omni 6.0 source tho so I had to re download so be careful of that.
[Android Software Development] DeadSquirrel01:
Personally, I use CM12.1 compressed sources, the .repo folder isn't needed for building only recoveries

EDIT: [MENTION=5186178]bluefirebird[/MENTION]

you added my recovery in marshmallow section, but I built it using cm12.1 sources/device tree (sorry, for haven't told it)
[Android Software Development] :
No, it is in QCOMM section with no differentiate lollipop or marshmallow because there are only two devices.
[Android Software Development] DeadSquirrel01:
[MENTION=5186178]bluefirebird[/MENTION] can U add this in lollipop section? I've built it for a guy that told me to port on his device. It's tested and working (It's an mtk device). the device vendor is Nous and the name is ns5511

EDIT: If you need sources here's the github link
[Android Software Development] bigrammy:
CM13

Hi,

I just did a build against cm13 repo and seem to be missing a file or files :confused:

Stock cm recovery compiled without issue.

HOSTLD scripts/kconfig/conf
scripts/kconfig/conf -s Config.in
can't find file Config.in
make[4]: *** [silentoldconfig] Error 1
make[3]: *** [silentoldconfig] Error 2
make[2]: *** [include/autoconf.h] Error 2
make[1]: *** [prepare] Error 2
make[1]: Leaving directory `/home/bigrammy/cm13-0/no-repo/bootable/recovery/busybox'
make: *** [/home/bigrammy/cm13-0/no-repo/out/target/product/zm1/obj/busybox/minimalctr/.config] Error 2
make: *** Deleting file `/home/bigrammy/cm13-0/no-repo/out/target/product/zm1/obj/busybox/minimalctr/.config'
make: *** Waiting for unfinished jobs....

#### make failed to build some targets (03:43 (mm:ss)) ####

I know it's probably me and totally obvious :silly:

But any pointers

I checked and there is no Config.in in that folder.
[Android Software Development] :
Hi. I guess you downloaded a zip from github. Don't do that. Do a clone repo and the problem will be solved.
[Android Software Development] DeadSquirrel01:
I had the same problem (I've cloned sources) and I fixed it by building in cm 12.1 with cm12.1 sources, maybe try adding this in busybox folder
[Android Software Development] bigrammy:
I done repo clone and make clean but I guess I am still missing somthing. :o

Compile error First

After make clean

Stock CM Recovery successful build

:eek:

Thanks :good: I may need to build it against 12.1 or maybe another 6.0 OS we will see what bluefirebird.
[Android Software Development] :
That Config.in should be generated by a script but maybe the permissions are messed up in your cloned version. Anyway if you want to add it manually use this: https://github.com/omnirom/android_external_busybox/blob/android-6.0/Config.in.
[Android Software Development] bigrammy:
Hi,

I did a full rom build and it built but would not boot past the logo screen and I then had to do a restore but the sim was not detected so did a full wipe and restore with spflashtool using stock rom (what would we do without that tool :laugh:)

Also the stock cm recovery was acting kinda strange so obviously something is not right in the source or more likely my setup. :eek:

I think I will just wipe the cm source and build against omnirom or some other OS.

Back to the drawing board for me :laugh:
[Android Software Development] DeadSquirrel01:
There are about 99999 causes for your device that won't boot. At 99,99 %the cause is the device tree but it can be the kernel (need to be cm, not aosp or touchwiz) or the proprietary files
[Android Software Development] bigrammy:
Yes I agree. :good:

Clearly I have a long way to go before building full roms but for now I will concentrate on getting the recovery to compile correctly. :fingers-crossed:
[Android Software Development] DeadSquirrel01:
So, good luck with porting the recovery :)
[Android Software Development] kirito9:
[MENTION=5186178]bluefirebird[/MENTION] I've compiled CTR 5.7 for two devices that you can add to your list :)

Here are the links:

Bmobile AX810

DiaglogOptima TC-A7
[Android Software Development] kirito9:
Hello guys,

I'm compiling CTR 6 for another device (Pixi 4 4034) and I'm getting this build error. I tried manually making the folder then running the build but it still appears. I'm using CM13 to compile. If you want to see the device tree just ask. Thanks.

http://pastebin.com/hCReMvp0
[Android Software Development] DeadSquirrel01:
Yes, post the link of the device tree

EDIT: Go to external directory from cm repo directory and type

$ git clone https://github.com/CyanogenMod/android_external_ntfs-3g.git -b cm-13.0

and rename the folder to ntfs-3g
[Android Software Development] kirito9:
Thanks I will try it. Ran out of thanks.
[Android Software Development] kirito9:
Hey thanks, your fix worked but now I got a new error.

http://pastebin.com/VTRvcKW5
[Android Software Development] DeadSquirrel01:
Can you post the device tree?
[Android Software Development] kirito9:
Here you go : https://github.com/kirito96/android_device_alcatel_4034
[Android Software Development] DeadSquirrel01:
Try to remove TARGET_USES_NTFS := true from BoardConfig.mk or comment the line with #
[Android Software Development] kirito9:
Tried it but same error as before the ntfs-3g fix. What I will do is try to build with AICP or Resurrection Remix.
[Android Software Development] :
If you still build with partial source repo, then you're missing /system/vold folder: this one.
[Android Software Development] kirito9:
Ahh thanks, I figured this partitial repo was gonna give me some problems. Would AICP MM work better than CM13 to compile? Less errors I mean.
[Android Software Development] DeadSquirrel01:
[MENTION=5186178]bluefirebird[/MENTION] can I compile on the new cm 14?
[Android Software Development] kirito9:
[MENTION=7511870]DeadSquirrel01[/MENTION] [MENTION=5186178]bluefirebird[/MENTION]

Can either of you compile the CTR 6 using CM13? I want to see if it's my source or the device tree that's giving problems. When you have time of course thanks.

EDIT: It builds now o.O. I didn't change a thing.

EDIT 2: Same error, was using CM recovery source LOL. It compiles with CM recovery but not CTR, might CTR source be the problem?
[Android Software Development] DeadSquirrel01:
Ctr 6 is for cm-13 and ctr 5 is for cm 12.1. Btw what is the error?
[Android Software Development] kirito9:
I get this error when trying to compile CTR 6 with CM13 - http://pastebin.com/VTRvcKW5

CTR5.7 compiles fine with CM12 non repo partial source.
[Android Software Development] DeadSquirrel01:
If on cm12 it compiles, just compile on cm version, the recovery is the same
[Android Software Development] kirito9:
Oh? Thought devices with MM kernel had to be compiled on CM13.
[Android Software Development] DeadSquirrel01:
Oh, yes, i've forgot that :D. Can you push the updated device tree (with prebuilt kernel included) that I'll build tomorrow, coz in Italy it' 02.00 am and I don't wont to turn on my pc?
[Android Software Development] kirito9:
Ohh sure, I will do that. Thanks :)
[Android Software Development] DeadSquirrel01:
hi, I've resolved the build error. Now it compiles on my pc and if on your pc you'll get error, the problem is your cm repo. I've opened a pull request in your device tree sources in github with the working one, with some changes
[Android Software Development] kirito9:
Thanks, I will test.
[Android Software Development] DeadSquirrel01:
Ok and let me know if it works :)