yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] bigrammy:
Haa yes I understand that bro but while I am booted in recovery I used adb shell to see all activated input devices with

cat /proc/bus/input/devices

the mtk-tpd is not there as an option so from my understanding the recovery tries to use the next best thing :confused:

Thats why I thought mtk-tpd may be getting blocked because the limit was reached :o

The recovery log also see's only the same loaded/active input devices

No mtk-tpd :(

DEVICE NAME: m_alsps_input - /sys/board_properties/virtualkeys.m_alsps_input
EV ST: minX: -32768 maxX: 32767 minY: 0 maxY: 0
EV MT: minX: 0 maxX: 0 minY: 0 maxY: 0

DEVICE NAME: m_acc_input - /sys/board_properties/virtualkeys.m_acc_input
EV ST: minX: -32768 maxX: 32767 minY: -32768 maxY: 32767
EV MT: minX: 0 maxX: 0 minY: 0 maxY: 0

DEVICE NAME: ACCDET - /sys/board_properties/virtualkeys.ACCDET
EV ST: minX: 0 maxX: 0 minY: 0 maxY: 0
EV MT: minX: 0 maxX: 0 minY: 0 maxY: 0

DEVICE NAME: hwmdata - /sys/board_properties/virtualkeys.hwmdata
EV ST: minX: 0 maxX: 0 minY: 0 maxY: 0
EV MT: minX: 0 maxX: 0 minY: 0 maxY: 0

DEVICE NAME: mtk-kpd - /sys/board_properties/virtualkeys.mtk-kpd
EV ST: minX: 0 maxX: 0 minY: 0 maxY: 0
EV MT: minX: 0 maxX: 0 minY: 0 maxY: 0

The adb shell did not work in TWRP so I can't see what is active in that or seem to be able get a detailed recovery log. Got it working now :D See adb outputs below. PS: /sys/board_properties/virtualkeys.mtk-kpd is NOT there in recovery please see adb output :eek:

As said I am just trying to understand how the touch function works :laugh:

If blocking the other input devices works then :cool:

So the logic is that once the recovery finds an input device that gives it the desired info all other devices are stopped from loading in the device list :confused:

Now I sound like a total nooob :laugh:

ADB OUTPUT IN RECOVERY

ls /sys/devices/virtual/
BOOT
CAM_CALdrv
EEPROMdrv
MJC
MTK_SMI
MT_pmic_adc_cali
accdet
actuatordrv_dw9714af
actuatordrv_fm50af
android_usb
bdi
block
btif
camera-fdvt
ccci_node
devmap
flashlightdrv
gpsdrv
input
ispdrv
mem
misc
mtk-adc-cali
mtk_almk
mtk_cmdq
mtk_disp_mgr
net
pmic_ftm
ppp
scheddrv
sensordrv
sensordrv2
sound
switch
thermal
timed_output
tty
wmtdetect
workqueue
xt_idletimer
~ # ←[6nls /sys/devices/virtual/input/
ls /sys/devices/virtual/input/
input1
input2
input3
input4 [COLOR="red"]Note no input5 = mtk-tpd[/COLOR]
mice
~ # ←[6n
ls /sys/
autok
block
bootinfo
bus
class
custom_camera
custom_date
dev
devices
firmware
fs
hwm_info
kernel
module
mtk_rgu
mtk_ssw
mtuart
power
[COLOR="red"]Note No board_properties folder [/COLOR] :rolleyes:
~ # ←[6n
[Miscellaneous Android Development] yuweng:
Found out it seems MTK do use Bosch sensors after all . . . :cowboy: Further digging found it at P6000 ueventd.rc or for that matter, it exists on my old MT6577 too so there is still hope for P6000 . . . :fingers-crossed:

/dev/akm8976_daemon 0640 compass system
/dev/akm8976_aot 0640 compass system
/dev/akm8973_daemon 0640 compass system
/dev/akm8973_aot 0640 compass system
/dev/[COLOR="blue"]bma150[/COLOR] 0640 compass system
/dev/cm3602 0640 compass system
/dev/akm8976_pffd 0640 compass system
/dev/lightsensor 0640 system system

Now need to determine what to blacklist . . . :fingers-crossed:

TW_INPUT_BLACKLIST := "[COLOR="Blue"]akm8976_daemon[/COLOR]\x0a[COLOR="blue"]akm8976_aot[/COLOR]\x0a[COLOR="blue"]akm8973_daemon[/COLOR]\x0a[COLOR="blue"]akm8973_aot[/COLOR]\x0a[COLOR="blue"]bma150[/COLOR]\x0a[COLOR="blue"]cm3602[/COLOR]\x0a[COLOR="blue"]akm8976_pffd[/COLOR]\x0a[COLOR="blue"]lightsensor"[/COLOR]

or

TW_INPUT_BLACKLIST := "[COLOR="blue"]m_acc_input[/COLOR]\x0a[COLOR="blue"]m_alsps_input[/COLOR]"
[Miscellaneous Android Development] bigrammy:
Thanks bro,

I have found a nice little excerpt from a book Here that explains very well what happens. :good:

It may well be just the Touch screen driver not reporting itself to the kernel :fingers-crossed: so it may get fixed after all so it's over to goodix :laugh:
[Miscellaneous Android Development] :
Ok, let's see. I built two twrp with my friend yuweng's suggestions. Try to see if any of them works:

twrp test 1

twrp test 2

And here is a CTR repacked with Ulephone BePro kernel, for testing purposes only, if someone is brave enough to try it in elephone p6000:

ctr bepro test
[Miscellaneous Android Development] Santhosh M:
TWRP test 2 touch doesn't work and Ulephone kernel packed CTR doesn't boot :)
[Miscellaneous Android Development] bigrammy:
Thanks carliv :good:

But I think we are wasting our time for sure bro :(

I have checked and tested with adb and the recovery does not even get the touch screen offered as an option to choose from as it's simply not turned on or identifying itself and therefore never gets loaded. :crying:

They are saying android 5.0 will be here very soon so maybe they will have fixed the Driver's or Kernel for that release :fingers-crossed:

I did already try various kernels in the recoverys without any change so thats kinda why I think it's a system side driver issue :fingers-crossed:

This touch on this phone has had problems from the very start so for them to screw up the driver reporting is not beyond belief :laugh:

Also the vendor id of 0000 seems to suggest all is not as it should be. :rolleyes:

Thanks Santhosh M I can confirm your findings.

For general info and interest.

Reading the documentation I posted above the first drivers that register get an entry in /sys/class/input first this is before ueventd takes over things.

As seen in the readout below our touch screen (input5 event5) is not listed.

I tried getevent (which fails in recovery) to see if we could get the touch screen loaded.

~ # ←[6nls /sys/class/input
ls /sys/class/input
event0
event1
event2
event3
event4
input0
input1
input2
input3
input4
mice
~ # ←[6ngetevent_main
getevent_main
/sbin/sh: getevent_main: not found
~ # ←[6ngetevent
getevent
/sbin/sh: getevent: not found
~ # ←[6n
[Miscellaneous Android Development] yuweng:
Bro, before moving on to the next conclusion, best is close this one first . . . :cowboy: Fyi, i've built with TW_INPUT_BLACKLIST := "mtk-kpd" then only aroma log listed mtk-tpd then i built with TW_INPUT_BLACKLIST := "mtk-tpd" & guess what, Touch is disabled on my MT6577 . . .

Now we don't even know if the correct sensors is disabled on your P6000 . . . :cowboy: Conclusion : P6000 owners need to identify, build & test with various sensors name to make sure that the correct accelerometer, proximity, light sensor is disabled, i strongly believe Teamwin wouldn't have added this build flag to disable sensors if it doesn't interfere with Touch for various android devices & i strongly believe there is no reason for MTK to disable Touch while at recovery, idk . . . :o
[Miscellaneous Android Development] bigrammy:
Sorry bro I just dont get it :confused:

So Blacklisting one sensor or another will force our touch screen to start and register as available :confused:

Or are you saying our touch screen is there but labeled wrong :confused:
[Miscellaneous Android Development] yuweng:
Summary again - Bosch BMA150/ 250 accelerometer has been found to be interfere/ blocking Touch while at TWRP & by blacklisting/ blocking it with build flag, Touch works after that & i'm suspecting the same for your P6000, concluded is accelerometer & proximity as listed at aroma log, it could be either or both, idk . . . :cowboy:

Therefore, the correct sensor name needs to be identify/ block but i have completely no idea what is the name of your accelerometer/ proximity so you guys have to identify it, i think the same command adb shell su -c "ls -R" > myP6000.txt shall give some clues as it lists out all but again, there are hell alot of names there & no one found out mtk-tpd is really the Touch as you've suspected . . . :laugh:

Updates

Overlook the whitelist & that might solve Touch problem on P6000 instead of blacklisting sensors, idk . . . :o

TW_WHITELIST_INPUT := "mtk-tpd"

Updates

accelerometer's name is gsensor & proximity's name is als_ps, i think . . .:o Further ref here & here . . .
[Miscellaneous Android Development] :
Based on the ProjectConfig that bigrammy sent to me, these are listed:

CUSTOM_KERNEL_ACCELEROMETER = da213 bma222E-new
CUSTOM_KERNEL_ALSPS = ap3xx6_mtk
CUSTOM_KERNEL_TOUCHPANEL = GT9XX_hotknot_SCP

You need to check if they are in your phone, because I saw also that GPU is SGX351_110 in ProjectConfig, and in specs on the web is mali760 or something. Also the egl.cfg is for mali.

So, I don't know how they built this phone, but there are so many discrepancies....
[Miscellaneous Android Development] HypoTurtle:
Looking through the strings of the kernel, there's reference to both GT9XX and GT91XX (it's a GT917S).

I believe these are all the drivers:

BMA222

AP3426

dummy_cam_cal

dummy_eeprom

leds-RT4505

kd_camera_hw

kd_camera_hw_bus2

DW9714AF

FM50AF

akm8963

gt9xx

sky_i2c_test

mt6306

tps6128x

mt6311

spi-ut​

On comparing to the Ulefone kernel there is two differences 1. There is a focaltouch driver (ft5406) - but I don't think it's being used and 2. There are no <<-GTP-DEBUG->> entries in the P6000 strings. In the kernel I'm seeing a malit6xx.

Edit. In dumpsys; it's a Mali-T760 as reported
[Miscellaneous Android Development] bayad:
Many thanks to all the developers who still continue to work on our P6000 :good:...and good luck for the continuation :fingers-crossed:
[Miscellaneous Android Development] Santhosh M:
The GPU of this device is Mali and not SGX. The projectconfig usually found in data/misc of stock rom isn't updated or they simply throw something in that folder.

The actual Projectconfig you can have a look as said in PM :)

Regards

Santhosh
[Miscellaneous Android Development] :
Yes ;) I checked. It's the same (in BoardConfig too):

MTK_GPT_SCHEME_SUPPORT=yes
MTK_GPU_CHIP=[COLOR="Red"]SGX351_110[/COLOR]
MTK_GPU_SUPPORT=yes
[Miscellaneous Android Development] HypoTurtle:
Attached boot and recovery from Beta Lollipop ROM, from needrom.com, scatter is different - so need to back up data/charge first.
[Miscellaneous Android Development] greekfragma:
Just read thread and subscribed. Thanks so much all of you for your hard work. I have a general knowledge but nothing much to understand all things I read. Just keep it up and I will try to catch up the sooner possible. :good:
[Miscellaneous Android Development] bigrammy:
Hi greek did you manage fix your flashtool and mount issues (Drivers) I read about on the other p6000 thread?

If not see my OP and follow those tuts I linked in.

The id for the mass storage comes from your build.prop file so can change if the build.prop changes.

ro.product.model=[COLOR="Blue"]Elephone P6000[/COLOR]

Elephone P6000 is how mine is displayed when I plug the phone into the PC.

For the cdc gadget and preloader drivers use the one's from Elephone forum and for adb use this CWM Universal adb Drivers Here
[Miscellaneous Android Development] greekfragma:
Hey brother, thanks for your interest on my problems.

This will be a long night. I have a customer computer next to me for setup with Windows7 as OS, so I will experiment there since there will be no headaches for incompatibility of drivers etc.

For sure tomorrow I will be back with results. For now I managed to access my SD card through the modded Recovery.

I can't wait for your work on P6000. Keep an eye on your donations soon. I am kinda short at the moment but I will aid with something really soon. If you ask me, I prefer to give my "thanks" to you that really put an effort on a device instead of a factory company that gives a product different than advertized and does 0 to fix things.
[Miscellaneous Android Development] bigrammy:
No problem bro I am just happy to help where I can Thanks but no need for any donations to me a simple thanks is cool for me but you can send your gratitude to [MENTION=5186178]carliv[/MENTION] and [MENTION=4478781]yuweng[/MENTION] who do a whole lot more work than I for the MTK SoC community in general and not just our phone as said we would be nowhere without guys like these trust me ;)

Elephone drivers are Here this is the Direct Link. Gadget Preloader etc

Be sure to follow all the steps as discribed in the OP Here regarding the driver installation. :good:

Do not be tempted to skip any as this will lead to failed installs and I speak from experience :laugh:

There is plenty of instruction regarding the adb drivers which have been confirmed to work with windows 8.1 64bit :good: Just follow the links through for that.

I suspect everything will work correctly then :fingers-crossed:
[Miscellaneous Android Development] xenonism:
Quick FYI, the Dropbox link is dead. Also, thanks for all your work!
[Miscellaneous Android Development] bigrammy:
Not sure why the killed the link :confused:

Anyway I uploaded the one I got from there to my account. It's double packed for some reason (Same files twice) maybe just a mistake on their part not mine. :)
[Miscellaneous Android Development] ac0935p:
xPosed Framework Works on P6000

All

Some good news, following [MENTION=304314]popeye0[/MENTION], I have found that the xPosed framework operates successfully on the P6000 despite the Aliyun warning. I did de-odex using TiBu Pro first, but I suspect even that is not strictly required.

Gravity Box KK works perfectly too. There is a short thread here

http://xdaforums.com/xposed/aliyun-bleak-t3025225
[Miscellaneous Android Development] mrsim:
not sure is this will help anybody here but someone just posted a source leak for the P6000 on the forum i moderate on,i downloaded the file and it did take a while to unpack so could be the whole source code or maybe just the kernel

i am no developer so do not know for sure which is why i am posting this into the thread

http://www.china-devices.com/Thread-Leaked-Elephone-P6000-maybe-source-code
[Miscellaneous Android Development] bayad:
Yes, it's works perfectly for me too despite the Aliyun warning :D:victory:

---------- Post added at 07:05 PM ---------- Previous post was at 07:03 PM ----------

Hopefully the developers will get something out of this leak :fingers-crossed:
[Miscellaneous Android Development] bigrammy:
Leaked source

Hi if someone who is a member of China Devices could post the actual link to the alleged source code it would be very helpful :good:

I have been quite of late due to being busy trying to port some rom's although there is not much choice really that's any different to what we have already :(

Maybe someone would care to start a Themer thread for the p6000 now we have xposed because this maybe a better than porting more of the same which is proving difficult and kind of pointless really. :laugh:
[Miscellaneous Android Development] HypoTurtle:
Straight from the guy himself,

http://xdaforums.com/showpost.php?p=59015163&postcount=241

Now just to check that it's the full kernel source.
[Miscellaneous Android Development] HypoTurtle:
Any chance of adding sd-ext support; sdcard partitioning etc.

Currently either recovery doesn't boot when the sdcard is partitioned or it just doesn't mount. (I've forgotten which - tried it a week ago)
[Miscellaneous Android Development] rene90:
New version of beta 5.0 is there: http://bbs.elephone.hk/thread-2443-1-1.html#.VPROrfmG_kU

Still some bugs
[Miscellaneous Android Development] rene90:
What's the best to do when i receive my elephone p6000? I think there is v8.3 on there, and i read about problems with the home notification light on v8.4

So just stay on v8.3 and use the apk fix for the touch screen issue?
[Miscellaneous Android Development] superdragonpt:
Kernel P6000

Im going to compile and check The provided source code, but i can tell you right now that some things are incompleted.

One of The sources that the Author posted on GitHub, with The device code-name "bird92" is from another device.

I've spoke about this source last year, this target is from an old source., and belongs to another device.

The other target products ( devices code-names ), i'll check them later.

Regards
[Miscellaneous Android Development] bayad:
For me, I'm still on v8.3. I used the apk fix for the touch screen issue but I have not seen any significant change.

I'll try later this evening or tomorrow the new Flyme_4.2.0.3C_ElePhone_P6000_V3 ROM (http://bbs.elephone.hk/thread-2569-1-1.html#.VPShWvmsW1I) to see if it's better than the current v8.3 stock ROM :)
[Miscellaneous Android Development] superdragonpt:
This isnt an official build. In fact its a ported ROM, with severe issues and it'll corrupt your NVRAM , dbpt/modem/imeis.

If you dont know what your doing, stay away from this ROM.

Regards
[Miscellaneous Android Development] HypoTurtle:
Yea he found two source trees mt6592 and mt6732 - and just added them together on github. The 6592 side has no bearing for the P6000.

It hasn't broken my imei's - but I like to think I know what I'm doing. The issues I would have is the lack of adb - and not knowing the reason why the port was done from the M1 Note rather than the M1 (perhaps the M1 ROM hadn't been released) - and I haven't had the time/patience to fix my port yet.
[Miscellaneous Android Development] superdragonpt:
HI

yes i know, i just don't understand why adding several sources from diff MTK SOC's into the same repo, even the kernel common isn't the same...

I was just trying to add some warnings, to the new users, that don't know/*understand how to fix broken IMEIs.

Several guys had issues with that rom.

Regards
[Miscellaneous Android Development] bayad:
Did you mean the V3 version or previous versions because the author of this port says there is no problem with the IMEI ? :confused:

Another thing I would like to have confirmation of the presence of the Arabic language in this ROM.

Thank you in advance for all.
[Miscellaneous Android Development] Santhosh M:
I think the people in the other two threads know. There is no problems in p6000 source code. I have compiled the kernel long back and it boots good. There is nothing messy and works cool.
[Miscellaneous Android Development] superdragonpt:
There's a lot of bad symbols there, if it boots, thats sweet.

It needs several clean.

There's also a lot of conflicts on the license headers APACHE vs GPL,(the same old MTK stuff...) if you take out all the MTK proprietary stuff, you can upload the rest to Github, without having any issue.

;)

Xeers
[Miscellaneous Android Development] HypoTurtle:
Fair enough I've added some IMEI recovery to my thread (imei.exe seems to be the handiest - if you don't have a backup)

I think adding the two together was simply an effort to get the source up somewhere before MTK/Elephone could attempt to plug the leak; bit of a null point as it's been mirrored in various places now. If you / a kernel dev wants to rehouse it on it's own as the offical repo of reference I don't think [MENTION=4830320]BachMinuetInG[/MENTION] would mind.

All that said the kernel has been bumped a bit for the L release and I'd say the chances of getting access to the now are very slim.

I can't see arabic in there (there's 24 languages) - you can get some Arabic with Locale More or locale selector etc. from the playstore
[Miscellaneous Android Development] superdragonpt:
HI

Yes, don't worry i saved the repo on local, and on private repo ;)

But those sources can be used, you just need to keep the MTK proprietary things away from repo.

Kernel is under GPL License.

Regards
[Miscellaneous Android Development] HypoTurtle:
Would it be possible/feasible to turn the proprietary stuff into blobs? Would that be acceptable do you think?
[Miscellaneous Android Development] superdragonpt:
Nope

Just Keep the Mediatek stuff out of your repo, and your good to go.

Everything else falls under GPL, aka the, common /kernel.

Everything thats Mediatek related (MTK configs/ pmt partition/ platform and even the main config file - projectconfig.mk ...) doesn't fall under GPL, as there's Proprietary headers everywhere... It's an mess.

Xeers
[Miscellaneous Android Development] bayad:
Ok, thank you for your answer. I think I'll wait for the stable version of Lollipop or another better ROM :)
[Miscellaneous Android Development] HypoTurtle:
Just a heads up...

Recovery and gapps working with Android L.

We do need a TWRP recovery port now - due to the encrypted data partition.
[Miscellaneous Android Development] bigrammy:
Hi All,
[MENTION=4830320]BachMinuetInG[/MENTION]

Has put up the kernel source code to another repository for the Elephone P6000 so that you can better fix bugs and communicate source code. :good:

Please see his post http://xdaforums.com/showpost.php?p=59213195&postcount=40

Just incase anyone has missed it or is not following that thread.
[Miscellaneous Android Development] :
GitHub's wanting to verify that I'm a human, so my profile has been taken offline in the meantime. I'll update anything on my blog, and the archive link is still there if you want to modify the source code first, then commit later!
[Miscellaneous Android Development] yuweng:
Bro, i really salute you for not giving up until now & keep on sharing your findings . . . :laugh: :good: Based on your findings earlier, you said goodix touchpanels use calibration data & i found some evidence to that, may be that is the cause as data partition is not mounted at recovery so i guess you can try mounting data at start-up while at recovery . . . :fingers-crossed:

Evidence

#define GUP_SEARCH_FILE_TIMES 50
#define UPDATE_FILE_PATH_1 "/data/_goodix_update_.bin"
#define UPDATE_FILE_PATH_2 "/sdcard/_goodix_update_.bin"

#define CONFIG_FILE_PATH_1 "/data/_goodix_config_.cfg"
#define CONFIG_FILE_PATH_2 "/sdcard/_goodix_config_.cfg"

gt9xx_update.c

#define GTP_BAK_REF_PATH "/data/gtp_ref.bin"
#define GTP_MAIN_CLK_PATH "/data/gtp_clk.bin"

tpd_custom_gt9xx.h

Attach is the source built at $out folder.
[Miscellaneous Android Development] codelover:
What yuweng said about dependency on /data/ could be relevant, but kind of inappropriate, as /data/ might get wiped during full format.

If that is the case, maybe one should rebuild kernel, replace the dependency paths with ramdisk path, pull the files and put in ramdisk instead.

Btw, bigrammy, when you said touch event was not loaded in recoveries, have you checked

stock recovery

too?

If not, can you check the touch event with below repacked 4.4

stock recovery

, i added getevent binary (i hope it work), check:

dmesg > dmesg.log
ls -la /sys/board_properties/virtualkeys.*
cat /proc/bus/input/devices

EDITED:

The reason why a stock recovery check is needed:

1) with stock, devices get mounted by init instead of recovery, at earlier stage, just like when the device booted with working touch.

2) Permissions check - to minimize error that's caused by custom recovery, eg, some custom permissions are set by stock init.

I do understand that the output could be the same, but we can take it as a confirmation.
[Miscellaneous Android Development] bigrammy:
Haahaa,

Hi yuweng my understanding is that the /data and /sd file paths are checked by the goodix driver to get any driver updates goodix push out or the manufacturer wishes to use if that feature has been enabled. :confused:

I can't remember exactly where I read it but It was in some Goodix guide about updating the driver.

As this method was not used by Goodix to fix the laggy touch problem in scroll I assume it's not implemented in our build and would still need the driver turned on as it were which ours is not sadly. :(

I mount data with cwm but still no go bro :(

Hi codelover,

I said some other place I got geteven sendevent etc working by entering AromaFM through cm recovery but thanks anyway bro :good:

We need to workout what triggers the /sys/kernel/uevent_helper as I believe things like bluetooth and maybe the wifi module ping this to get a Kernel registrar when they are tuned on :confused:

Or if anyone knows of a adb cmd we could use to check it :confused: