Related
Got a strange problem....
If I press up/down volume when the phone is supposed to be locked it turns the screen on. Obviously if my phone is in my pocket this is going to happen all the time and waste the battery etc.
Any ideas how I can prevent this from happenning?
cheers.
Thats a feature, not a bug
I know on MIUI-rom you can turn it off in settings, which rom are you using?!
I'm using Shadow Hawk v2.1
Looked everywhere for a setting, just can't find it.
I never tried that rom, but in the thread where to download shadow hawk you should have a look in the feature list
Code:
*Wake phone with volume keys (thanks to lowveld)
tangerine0072000 said:
Got a strange problem....
If I press up/down volume when the phone is supposed to be locked it turns the screen on. Obviously if my phone is in my pocket this is going to happen all the time and waste the battery etc.
Any ideas how I can prevent this from happenning?
cheers.
Click to expand...
Click to collapse
Hmmm...Maybe you can turn off this option from within RCMix tweaks, if you enabled it from there. I've never used that ROM, but i understand that it uses RCMix tweaks and it would do you good to find out if there is a volume wake setting in there. If there isn't, i have the fix for it, and i can give it to you if you're willing to try it. First let me know if you can find anything in the RCMix tweaks.
Cheers
thanks chaps, I had a look in RC tweaks initially before posting, but there is nothing in there that refferences the volume controls.
by the way, what was the fix ?
tangerine0072000 said:
by the way, what was the fix ?
Click to expand...
Click to collapse
Well, the solution is to replace android.policy.jar with the attached file.
This is located in system/framework
Use root explorer or es file explorer with root access, mount system as r/w and replace the said file in the above folder with the one below. Reboot. That's it...your volume buttons will just function as normal volume rocker, and will not wake the phone up anymore.
P.S. : While i don't expect any problem at all, i would highly recommend taking a nandroid backup, and also backing up your original android.policy.jar in case something goes wrong, or you want to revert back to volume rocker wake... Do post back if it works for you.
CLICK TO DOWNLOAD
thanks for the info, I got the download. I tried mounting through these apps, but can't find an option for it. Do I need to mount read/write via the ADB ?
Not done this procedure before.
thanks,
I managed to replace the file using 'root explorer'. Did a reboot, but still got the problem with the volume switching the screen on.
so in my infinate wisdom I thought I might as well put the orignal file back which I did and rebooted. Then the phone wouldn't boot, stuck on HTC logo.
Then I thought I would restore my nandroid back (which I made last night). Phone will only still boot to HTC screen. Doh !
Did this serveral times, formating, clearing cache, restoring backup, but still no joy.
You should read this thread!
edit:
another guide
think I have corrupted cache as I know get....
E:Can't open /cache/recovery/log comming alot when trying to do anything in recovery mode.
tangerine0072000 said:
think I have corrupted cache as I know get....
E:Can't open /cache/recovery/log comming alot when trying to do anything in recovery mode.
Click to expand...
Click to collapse
did you read the guides of my last post? they are may solving your problems!
really wiered.
when I do 'dmesg | grep mmc0' I just get the command prompt...
~ # dmesg | grep mmc0
dmesg | grep mmc0
~ #
I contined to perform 'mke2fs /dev/block/mmcblk0p27'
~ # mke2fs /dev/block/mmcblk0p27
mke2fs /dev/block/mmcblk0p27
mke2fs 1.40.8 (13-Mar-2008)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
76912 inodes, 307196 blocks
15359 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67633152
38 block groups
8192 blocks per group, 8192 fragments per group
2024 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185
Writing inode tables: done
Writing superblocks and filesystem accounting information:
done
This filesystem will be automatically checked every 36 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override
~ #
then tried to install my rom which failed part way through.
I am now getting some response from ADB, no errors that I can see.
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 6.994781] mmc0: No card detect facilities available
<6>[ 6.995300] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 6.995544] mmc0: Platform slot type: MMC
<6>[ 6.995666] mmc0: 4 bit data mode disabled
<6>[ 6.995819] mmc0: 8 bit data mode enabled
<6>[ 6.996032] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 6.996154] mmc0: Slot eject status = 0
<6>[ 6.996398] mmc0: Power save feature enable = 1
<6>[ 6.996520] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c2c8000
<6>[ 6.996765] mmc0: DM cmd busaddr 0x0c2c8000, cmdptr busaddr 0x0c2c8300
<6>[ 7.150024] mmc0: new high speed MMC card at address 0001
<6>[ 7.151672] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
No WiFi - wlan0 device can't be found. "dhdsdio_probe_attach: si_attach failed!".
Hi all,
I have a UK Sensation XE that I've had for 18 months. My WiFi has not worked for many months, maybe a year. I am pretty sure the problem first started on GB, because I remember doing an OTA update to stock ICS and hoping it would fix the problem and it didn't.
I just started trying to seriously fix the problem a few days ago. Since then, I have researched on here and Google for hours and hours, and tried every suggestion I could find. I have done lots of diagnostics.
What I've discovered is that the WiFi driver does load, but it reports in dmesg that it can't find the device. Therefore it does not create wlan0. Therefore wpa_supplicant cannot load.
Everything else on the phone works OK - 2G/3G, Bluetooth, USB, etc. Just WiFi is broken.
I am wondering if maybe my WiFi hardware is bust. But then again, I do see the same symptoms on other posts - like this one and this one. The first of those two posts reported it worked for him when he went back to Stock 2.2, suggesting there was some software cause.
dmesg shows the following (I've edited a bit in the middle so to not make this message too long - full dmesg output is in attached txt) :
Code:
gannet_setup
gannet initialized OK
[WLAN] ## wifi_probe
[WLAN][WRN] wifi_set_power = 1
pyramid_wifi_power: 1
EXT4-fs (mmcblk0p22): re-mounted. Opts: user_xattr,barrier=0,data=ordered
[WLAN] wifi_set_carddetect = 1
pyramid_wifi_set_carddetect: 1
mmc2: Slot status change detected (0 -> 1)
[WLAN] Dongle Host Driver, version 5.90.125.120
mmc2: queuing unknown CIS tuple 0x91 (3 bytes)
mmc2: new high speed SDIO card at address 0001
[WLAN] alloc static buf at cf9c0000!
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
EXT4-fs (mmcblk0p22): re-mounted. Opts: user_xattr,barrier=0,data=ordered
mmc2: CMD53: Data timeout
mmc2: SDCC PWR is ON
mmc2: SDCC clks are ON, MCLK rate=48000000
mmc2: SDCC irq is enabled
===== SDCC-CORE: Register Dumps @base=0xd08a6000 =====
.. cut a bunch of Reg= values ..
mmc2: PIO mode
mmc2: xfer_size=4, data_xfered=0, xfer_remain=4
mmc2: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0
[COLOR="Red"][WLAN][WRN] dhdsdio_probe_attach: si_attach failed!
[WLAN][WRN] dhdsdio_probe: dhdsdio_probe_attach failed
[WLAN][WRN] dhd_module_init: wifi_fail_retry is true
[WLAN] ## wifi_remove
[WLAN][WRN] wifi_set_power = 0
pyramid_wifi_power: 0
[WLAN] wifi_set_carddetect = 0
pyramid_wifi_set_carddetect: 0
mmc2: Slot status change detected (1 -> 0)
mmc2: card 0001 removed
[WLAN] ## wifi_remove leave
[WLAN] module init fail, try again!
[/COLOR]pyramid_wifi_power: 1
pyramid_wifi_set_carddetect: 1
mmc2: Slot status change detected (0 -> 1)
[WLAN] Dongle Host Driver, version 5.90.125.120
I have attached a longer section of dmesg output, starting at boot and going a bit past the last reference to WLAN. The above dmesg snippet starts on line 760 of the attached dmesg txt file. I attached the fuller log in case the dmesg output shows some other error, not tagged WLAN, that I don't recognise as being a problem.
The bcmdhd.ko module is loaded OK:
Code:
# lsmod
tun 14813 0 - Live 0xbf091000
bcmdhd 483764 0 - Live 0xbf005000
kineto_gan 4230 0 - Live 0xbf000000
In logcat, there are various errors from wpa_supplicant and other, which all basically just indicate that it can't find wlan0. Here's a small sample:
Code:
E/wpa_supplicant( 5847): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 5847): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 5847): wlan0: Failed to initialize driver interface
This is confirmed from shell:
Code:
# ip link ls wlan0
ip: can't find device 'wlan0'
The problem started on stock, I think stock GB. I do not know of any trigger for it happening.
Around that time I was playing around with rooting for the first time, and I tried Revolution S-OFF which I recall changed my HBOOT from 1.19 to 1.17 or something. But that's as far as I got at the time, I just ran Revolution S-Off, I remember it changed my HBOOT version on phone startup, and then I never tried anything more with flashing/rooting.
I do not know if the Wifi problem started at the same time I tried that hboot change. I cannot remember exactly when the WiFi broke, I don't know if anything triggered it.
All I am pretty sure of is that the problem started on stock GB, and then it was not resolved when I OTA updated to stock ICS (the stock ICS upgrade then changed my hboot to 1.29).
So I know the problem existed on Stock ICS. I think it happened also on stock GB. Then this is what I have also tried recently, in the last week, since I first started flashing/rooting/customising my phone:
Full phone wipe - used 4Ext to do complete wipe of all partitions, before installing new ROMs
Tried with a) no SD card at all, b) two different SD cards, c) did a complete format of one SD card
Tried without sim-card, also tried WiFix to set country code - doubt this has anything to do with it though as there's not even a wlan0 device.
Stock 3.33 FW, and then XDA-Dev 3.32 FW and XDA-Dev 3.33 FW
Stock HTC ICS release as per OTA update
Android Revolution HD 7.1 ROM 4.0.3 ICS
Elegancia ROM 3.70 ROM 4.0.4 ICS
Stock, Faux, Sebastian and Bricked kernels
Originally HTCDev locked, and now unlocked
Originally S-On, and now S-Off (Hboot 1.27)
Flashing boot.img separately with fastboot flash boot boot.img
Flashing ROM with 4Ext SmartFlash (even though I had S-OFF) - and then turning it off again and re-flashing.
Deleting wpa_supplicant.conf (not that this should work as issue is before supplicant. I've put the conf back now.)
So right now my phone is:
HTCDev unlock
S-Off, HBoot 1.27 (I used Juopunutbear-off with the 'wire trick')
4Ext Flash Recovery
Elegancia Rom 3.70 with Bricked kernel
I have searched so much and tried so many things, so I would be super grateful for any help at all. Maybe it's just a HW fault, but I have seen other people with the same symptoms of dmesg reporting it can't find the device, and some of those people did have the issues caused by SW problems, so I am hoping there is still some chance it's resolvable.
Thanks in advance!
No thoughts from anyone?
Would be great to get any thoughts or feedback - even if it's just to say that the HW is broken.
I've been looking all over for a solution for this problem myself. WiFi 'died' with an OTA a while back, none of the suggestions found all over work.
WiFix (basically changing the region) doesn't apply, wlan0 doesn't even start properly.
You mentioned BT is working, but I can see devices, not connect to them, so for me BT is partially working.
What I tried so far:
Different FWs/RUUs, even going back to Gingerbread!
Different RIL - FW/Radio combos
Different ROMs on Universal 3.33 FW as well as FWs from RUUs
I even put a Z710e RUU on it to see if that might work.
Device:
Sensation XE Z715e, currently on: HBoot 1.27.1100, FW 3.33.401.153 Radio11.76C.3504.00U_11.29A.3504.18_M
Stock Rom lsmod:
Code:
bcm4329 225933 0 - Live 0xbf03c000
kineto_gan 4190 0 - Live 0xbf000000
CM10.1 lsmod:
Code:
bcmdhd 444356 0 - Live 0x00000000
I see the same errors as OP in my logcat and dmesg.
I'm starting to suspect the chip is fritzed and needs to be replaced (I can't heat it as suggested here: http://forum.xda-developers.com/showpost.php?p=38165494&postcount=66 )
My other Z715e is unaffected.
Hi,
My Ray sometimes reboots due to what I suspect is an undervolt error situation (cpu/ram).
Is there any log file that I can look into after rebooting, in order to understand what was the cause of the reboot ?
Tks
---------------------------------------------------------------
Xperia Ray
Smart Xperia SX.03.1.B.2.495
VDS Kernel 2.6.32.9 Dec 1 2012
Boost My Xperia 2.0.1 : Multitasking Mode
Sandisk 32GB Class 10 UHS-1
If your kernel support "Ram console" there should be a file named "/proc/last_kmsg" which holds the last kernel log.
Otherwise you can do an "adb logcat" on your PC but that is inconvenient if you can't reproduce manually the problem.
muczy said:
If your kernel support "Ram console" there should be a file named "/proc/last_kmsg" which holds the last kernel log.
Otherwise you can do an "adb logcat" on your PC but that is inconvenient if you can't reproduce manually the problem.
Click to expand...
Click to collapse
Thanks muczy. Will check that.
Will need to investigate further, since these messages seem to be related with a modem module (similar reboot on an Xperia S).
Anyone got similar situation ?
------------- /proc_lastamsslog (snipet) ---------------
ERR crash log report. Version 3.
Error in file mdspasync.c, line 2486
Time of crash (m-d-y h:m:s): 04-16-2013 13:30:04
Uptime (h:m:s): 97:52:24
Build ID: M7630A-ABBQMAZM-2.0.3028DT
REX_TCB ptr: 0x067a1614
tcb.task_name: IST0
Coredump ARCH type is: ERR_ARCH_ARM
Register values from coredump:
ARM_SVC_R0 : 0x00000090
...
Dog Report Information (dog_state_table)
[idx] Task Name Pri Timeout Count Is_Blocked
[ 0] fmrds 0 60 59 0
[ 1] bt_ftm 0 60 59 0
[ 2] time_ipc 0 60 59 0
[ 3] ds_sig 0 60 59 0
[ 4] loc_middlew 0 60 59 0
[ 5] snd 0 4 4 0
[ 6]
------------------------------------------------------------------
----------- /proc/last_kmsg (snipet) ------------------
...
[36005.036865] msmrtc_tod_proc_result: 04/16/2013 13:29:29 (01)
[36005.050659] msmrtc_tod_proc_result: 04/16/2013 13:29:29 (01)
[36005.050781] pm_op(): platform_pm_suspend+0x0/0x54 returns -16
[36005.050842] PM: Device alarm failed to suspend: error -16
[36005.050872] PM: Some devices failed to suspend
[36005.053375] Restarting tasks ... done.
[36005.074340] suspend: exit suspend, ret = -16 (2013-04-16 13:29:29.187896746 UTC)
[36005.074401] active wake lock alarm_rtc, time left 198
[36005.074432] suspend: abort suspend
[36005.887847] suspend: enter suspend
[36005.887878] PM: Syncing filesystems ... done.
[36005.967803] Freezing user space processes ...
[36005.973999] AKM8975 AKECS_GetOpenStatus returned (0)
[36005.982086] (elapsed 0.01 seconds) done.
[36005.982116] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
[36005.983398] Suspending console(s) (use no_console_suspend to debug)
------------------------------------------------------------------
Well, this mdspasync.c seems to be hard to find...
Looked in the androidxref dot com for both Android and Kernel sources, but had no luck.
If someone knows what is this for (seems to be related with modem), that would be great.
I flashed AndroPlusKernel on my z3 and i could not charge my phone.
This is what I did
Install RZWX Rom v15.00
Flash OTA 16.00
Flash XZDR remove package
Flash AndroPlusKernel 72 permissive
When I tried to charge my phone, it did not charge while it was turned on, I had to turned it off to charge it. I tried to restore the rom in order to verify if the problem could disappear but it still had the problem, so I decided to wipe all the system and reinstall the rom but that doesn't work so I did this
Flash without wipes ZyxxOS because I was on 1%
Reboot
and now when I turn it on a message appear saying “The device is corrupt…” and I cannot enter into the recovery… I can enter on the fastboot (blue light) but my PC does not recognize my z3 and it says “The last USB device you connected to this computer malfunction and windows does not recognize it” and I have the drivers installed correctly. I don’t know what to do, I have try to many times to enter into recovery but the message does not allow me to do it. Please help me, I use my device a lot because I am Social media Manager on Venezuela and I cannot buy another smartphone at this moment.
My device does not show the notification of USB debugging, It is like my z3 does not recognize anything connected by the charger/usb port.
UPDATE1
The message "your device is corrupt" has disappeared
UPDATE2
I could get root with KingRoot but I can't enter into recovery with any app.
any idea?
My device is D6653
My bootloader is oemandroidboot.s1boot=1286-7314_S1_Boot_MSM8974AC_LA3.0_52-2
EDIT: There's a capture of the error shows by the computer
JuanMnz93 said:
UPDATE1
The message "your device is corrupt" has disappeared
UPDATE2
I could get root with KingRoot but I can't enter into recovery with any app.
any idea?
Click to expand...
Click to collapse
Seems your usb cable is broken. Did you try another one?
Can you tell me if your bootloader is upgraded:
Code:
[email protected]:/ $ su
[email protected]:/ # cat /proc/cmdline
androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3b7 ehci-hcd.park=3 androidboot.bootdevice=msm_sdcc.1 vmalloc=300M dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y display_status=on androidboot.emmc=true androidboot.bootloader=s1 oemandroidboot.s1boot=1286-7314_S1_Boot_MSM8974AC_LA3.0_L_37 androidboot.serialno=xxxxxxxxx ta_info=1,16,256 startup=0x00000001 warmboot=0x77665501 oemandroidboot.imei=xxxxxxxxxxxxx oemandroidboot.phoneid=0000:xxxxxxxxxxxxx oemandroidboot.security=0 oemandroidboot.babe08b3=50000000 oemandroidboot.securityflags=0x00000003 lcdid_adc=0x6C12A display_status=on androidboot.baseband=msm
The part with the oemandroidboot.s1boot=1286-7314_S1_Boot_MSM8974AC please.
If your bootloader is (as mine): LA3.0_L_37 the only way entering recovery is:
- power the device off
- press volume down & power until sony logo appears.
Soft reboot won't work.
If your bootloader is the older one (can't remember the version), to boot into recovery your kernel need to have one or include the extract_elf_ramdisk. See the this post for more information.
Edit: Have you a backup of your 'ta partition'? Maybe the 'device corrupt' is related to the 'ta partition' or even the 'tz partition' (trust zone).
nailyk said:
Seems your usb cable is broken. Did you try another one?
Can you tell me if your bootloader is upgraded:
The part with the oemandroidboot.s1boot=1286-7314_S1_Boot_MSM8974AC please.
If your bootloader is (as mine): LA3.0_L_37 the only way entering recovery is:
- power the device off
- press volume down & power until sony logo appears.
Soft reboot won't work.
If your bootloader is the older one (can't remember the version), to boot into recovery your kernel need to have one or include the extract_elf_ramdisk. See the this post for more information.
Click to expand...
Click to collapse
[email protected]:/ $ su
[email protected]:/ # at /proc/cmdline
k_shell/10245:18896: at: not found
127|[email protected]:/ # cat /proc/cmdline
androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3b7 ehci-hcd.park=3 androidboot.bootdevice=msm_sdcc.1 vmalloc=300M dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y androidboot.emmc=true androidboot.bootloader=s1 oemandroidboot.s1boot=1286-7314_S1_Boot_MSM8974AC_LA3.0_52-2 androidboot.serialno=CB5A24S161 ta_info=1,16,256 startup=0x00000001 warmboot=0x6f656d46 oemandroidboot.imei=3550980659309700 oemandroidboot.phoneid=0000:3550980659309700 oemandroidboot.security=0 lcdid_adc=0x6A96E display_status=off androidboot.baseband=msm
[email protected]:/ #
nailyk said:
Seems your usb cable is broken. Did you try another one?
Can you tell me if your bootloader is upgraded:
Code:
[email protected]:/ $ su
[email protected]:/ # cat /proc/cmdline
androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3b7 ehci-hcd.park=3 androidboot.bootdevice=msm_sdcc.1 vmalloc=300M dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y display_status=on androidboot.emmc=true androidboot.bootloader=s1 oemandroidboot.s1boot=1286-7314_S1_Boot_MSM8974AC_LA3.0_L_37 androidboot.serialno=xxxxxxxxx ta_info=1,16,256 startup=0x00000001 warmboot=0x77665501 oemandroidboot.imei=xxxxxxxxxxxxx oemandroidboot.phoneid=0000:xxxxxxxxxxxxx oemandroidboot.security=0 oemandroidboot.babe08b3=50000000 oemandroidboot.securityflags=0x00000003 lcdid_adc=0x6C12A display_status=on androidboot.baseband=msm
The part with the oemandroidboot.s1boot=1286-7314_S1_Boot_MSM8974AC please.
If your bootloader is (as mine): LA3.0_L_37 the only way entering recovery is:
- power the device off
- press volume down & power until sony logo appears.
Soft reboot won't work.
If your bootloader is the older one (can't remember the version), to boot into recovery your kernel need to have one or include the extract_elf_ramdisk. See the this post for more information.
Edit: Have you a backup of your 'ta partition'? Maybe the 'device corrupt' is related to the 'ta partition' or even the 'tz partition' (trust zone).
Click to expand...
Click to collapse
I have tried to many USB cables and the message from computer it's the same. Yes I have my TA Partition backup but that message disappeared. (The device is corrupt....)
JuanMnz93 said:
oemandroidboot.s1boot=1286-7314_S1_Boot_MSM8974AC_LA3.0_52-2
Click to expand...
Click to collapse
So your bootloader is upgraded (v52)
Now the only way entering recovery is the process I describe earlier.
Flash a new one with the process I answer you.
Seems only your kernel is wrong for now.
Good luck!
nailyk said:
So your bootloader is upgraded (v52)
Now the only way entering recovery is the process I describe earlier.
Flash a new one with the process I answer you.
Seems only your kernel is wrong for now.
Good luck!
Click to expand...
Click to collapse
How can I reflash the kernel? I'm on ZyxxOS v1.2. On the zip there isn't a recovery.img or boot.img.. There are only boot.sin and partition-image.sin. I can't enter into recovery, I flashed the twrp 3.0 for new bootloader but I can't enter. There's not light or vibration when I press power button.
I read on a threat that the kernel manages the energy and the way the device charges and I think andropluskernel broke that part of my device. I connect and OTG and my Z3 doesn't recognize it.
JuanMnz93 said:
How can I reflash the kernel? I'm on ZyxxOS v1.2. On the zip there isn't a recovery.img or boot.img.. There are only boot.sin and partition-image.sin. I can't enter into recovery, I flashed the twrp 3.0 for new bootloader but I can't enter. There's not light or vibration when I press power button.
I read on a threat that the kernel manages the energy and the way the device charges and I think andropluskernel broke that part of my device. I connect and OTG and my Z3 doesn't recognize it.
Click to expand...
Click to collapse
You are right, kernel does the offline charge an the usb connectivity.
I'm looking about sin files.
To enter recovery (with new bl) turn off your phone, wait a few seconds, then press volume down and power at the same time until the sony logo appears.
---------- Post added at 20:00 ---------- Previous post was at 19:52 ----------
Is your phone a d6603 or a d6633?
nailyk said:
You are right, kernel does the offline charge an the usb connectivity.
I'm looking about sin files.
To enter recovery (with new bl) turn off your phone, wait a few seconds, then press volume down and power at the same time until the sony logo appears.
---------- Post added at 20:00 ---------- Previous post was at 19:52 ----------
Is your phone a d6603 or a d6633?
Click to expand...
Click to collapse
I can't enter into recovery, there's not a vibration or light, I have tried too many times to enter using that combination of bottoms.
My device is D6653. I was looking into the ZIP file of the ZyxxOS ROM which is 6.0 and there's a zip that is called CORE.ZIP and extracted that zip called CORE and there's a file with the name boot.img.
I have sent a message to the developer of ZyxxOS ROM in order to get more information to try to identify the problem... I invited him to look at my threat
nailyk said:
I'm looking about sin files.
Click to expand...
Click to collapse
I test sin2raw and with flashtool: no luck.
After reading this I truncate the boot.sin file provided by this zyxxos v1.2 it is in attachement in a dirty way. I can not guarantee it will work! As the kernel is the first thing started on your phone a wrong flash could result in a really bad soft brick.
The boot.img provided in the core.zip seems to be the 'dual-recovery' provided by the rom.
I thing you can restart with a fresh install with emma if something goes really wrong.
Good luck.
(or try another kernel specially build for your phone/rom)
nailyk said:
I test sin2raw and with flashtool: no luck.
After reading this I truncate the boot.sin file provided by this zyxxos v1.2 it is in attachement in a dirty way. I can not guarantee it will work! As the kernel is the first thing started on your phone a wrong flash could result in a really bad soft brick.
The boot.img provided in the core.zip seems to be the 'dual-recovery' provided by the rom.
I thing you can restart with a fresh install with emma if something goes really wrong.
Good luck.
(or try another kernel specially build for your phone/rom)
Click to expand...
Click to collapse
The problem is not restart with a fresh install, the problem is that I can't use any program on PCs because my device is recognized as an USB unknown malfunctioned device.
I think I have to solve first the problem with the kernel (boot.img???) in order to make work the USB part of my phone, it could be by having recovery I think, reinstalling the rom with all the wipes in order to clean the system.
EDITED:
Can you check this zip? It's the XZDR remove package to make work AndroPlusKernel
https://www.androidfilehost.com/?fid=24269982086991761
I flashed that file before flashing andropluskernel but I had recovery. I lost the recovery when I flashed ZyxxOS ROM
JuanMnz93 said:
The problem is not restart with a fresh install, the problem is that I can't use any program on PCs because my device is recognized as an USB unknown malfunctioned device.
I think I have to solve first the problem with the kernel (boot.img???) in order to make work the USB part of my phone, it could be by having recovery I think, reinstalling the rom with all the wipes in order to clean the system.
Click to expand...
Click to collapse
Even in download mode? So the computer should be the problem
As I know download mode is unbreakable. I format all my partitions (d6603): fotakernel, boot, system and reflash from download.
Yes the kernel is the boot.img (go to the boot partition) and the recoveries goes to the fotakernel partitions.
nailyk said:
Even in download mode? So the computer should be the problem
As I know download mode is unbreakable. I format all my partitions (d6603): fotakernel, boot, system and reflash from download.
Yes the kernel is the boot.img (go to the boot partition) and the recoveries goes to the fotakernel partitions.
Click to expand...
Click to collapse
I tried another computer and it is recognized as USB unknown device, I installed the drives and nothing happened.
I have used my PC too many times to use flashtool and I could use it perfectly. After flashing these zips, my pc doesn't recognize my z3, for that reason I think it's something relative to the kernel and the way it manages connections through the USB port
JuanMnz93 said:
I tried another computer and it is recognized as USB unknown device, I installed the drives and nothing happened.
I have used my PC too many times to use flashtool and I could use it perfectly. After flashing these zips, my pc doesn't recognize my z3, for that reason I think it's something relative to the kernel and the way it manages connections through the USB port
Click to expand...
Click to collapse
You are right, the kernel manage the usb connection, but only when this kernel is started (system booted or off mode charging).
You test different cables, another computer and no fastboot, no download!?
I can't understand.
What I believe to know:
When you start in fastboot, the bootloader (aboot partition) manage your usb and when you start in download mode another part of the phone (don't know which one) manage the usb.
So, I think, the only way you have, in all of these boot mode, a 'bad device' is a hardware problem: broken usb port on the phone or maybe the integrated usb controller...
nailyk said:
You are right, the kernel manage the usb connection, but only when this kernel is started (system booted or off mode charging).
You test different cables, another computer and no fastboot, no download!?
I can't understand.
What I believe to know:
When you start in fastboot, the bootloader (aboot partition) manage your usb and when you start in download mode another part of the phone (don't know which one) manage the usb.
So, I think, the only way you have, in all of these boot mode, a 'bad device' is a hardware problem: broken usb port on the phone or maybe the integrated usb controller...
Click to expand...
Click to collapse
I have tried different USB cables and PCs and nothing happened. The thing is that the problem happened after flashing andropluskernel, before that my PC recognized my Z3 and my Z3 used to charge perfectly with the charger. I don't understand, I'll wait for the developers answers in order to know a little more.
Thank you friend, I really appreciate your effort to help me! I'm getting crazy with this! :crying:
I would like at least make the recovery work
I found this:
On my computer:
Code:
[email protected] :) % lsusb
Bus 006 Device 006: ID 0fce:51ba Sony Ericsson Mobile Communications AB
then on the phone:
Code:
[email protected]:/ # cat /sys/devices/virtual/android_usb/android0/idProduct
51ba
[email protected]:/ # cat /sys/devices/virtual/android_usb/android0/idVendor
0fce
and my usb is enabled:
Code:
[email protected]:/ # cat /sys/devices/virtual/android_usb/android0/enable
1
Can you check on your phone please?
Also:
Code:
127|[email protected]:/ # dmesg | grep usb
<6>[ 1.429210] usbcore: registered new interface driver usb-storage
<6>[ 1.429239] usbcore: registered new interface driver usb_ehset_test
<6>[ 1.430480] gadget: android_usb ready
<6>[ 1.430910] usbcore: registered new interface driver xpad
<6>[ 1.430934] usbcore: registered new interface driver usb_acecad
<6>[ 1.430958] usbcore: registered new interface driver aiptek
<6>[ 1.430989] usbcore: registered new interface driver gtco
<6>[ 1.431014] usbcore: registered new interface driver hanwang
<6>[ 1.431039] usbcore: registered new interface driver kbtab
<6>[ 1.431062] usbcore: registered new interface driver wacom
<6>[ 2.426336] usbcore: registered new interface driver usbhid
<6>[ 2.426341] usbhid: USB HID core driver
<6>[ 2.427194] usb_bam_ipa_create_resources: Failed to create USB_PROD resource
<6>[ 2.428933] usbcore: registered new interface driver snd-usb-audio
<6>[ 2.471332] qpnp_charger_probe: success chg_dis = 0, bpd = 1, usb = 0, dc = 0 batt_present = 1 b_health= 1
<3>[ 3.805914] enable_store: android_usb: already disabled
<6>[ 3.852097] qpnp_chg_rb_work: stopping worker usb/dc disconnected
<6>[ 1300.274689] android_usb gadget: high-speed config #1: fe8050c8.android_usb
We see the usb drivers are loaded and (at 1300sec after booting) my usb was plugged-in and ok.
Maybe you can check this on your phone too?
---------- Post added at 22:30 ---------- Previous post was at 22:16 ----------
JuanMnz93 said:
My device is D6653. I was looking into the ZIP file of the ZyxxOS ROM which is 6.0 and there's a zip that is called CORE.ZIP and extracted that zip called CORE and there's a file with the name boot.img.
Click to expand...
Click to collapse
I test the boot.img on the core.zip and a twrp 2.8.7.0 is included. My cyanogen doesn't start on my d6603 but the twrp seems to be working.
The uname -a return:
3.4.0-perf-gc42d8a9-02192-g20ae1c7 #1 SMP PREEMP tue Oct 13 12:04:26 CEST 2015
Not sure that is the good one.
nailyk said:
I found this:
On my computer:
Code:
[email protected] :) % lsusb
Bus 006 Device 006: ID 0fce:51ba Sony Ericsson Mobile Communications AB
then on the phone:
Code:
[email protected]:/ # cat /sys/devices/virtual/android_usb/android0/idProduct
51ba
[email protected]:/ # cat /sys/devices/virtual/android_usb/android0/idVendor
0fce
and my usb is enabled:
Code:
[email protected]:/ # cat /sys/devices/virtual/android_usb/android0/enable
1
Can you check on your phone please?
Also:
Code:
127|[email protected]:/ # dmesg | grep usb
<6>[ 1.429210] usbcore: registered new interface driver usb-storage
<6>[ 1.429239] usbcore: registered new interface driver usb_ehset_test
<6>[ 1.430480] gadget: android_usb ready
<6>[ 1.430910] usbcore: registered new interface driver xpad
<6>[ 1.430934] usbcore: registered new interface driver usb_acecad
<6>[ 1.430958] usbcore: registered new interface driver aiptek
<6>[ 1.430989] usbcore: registered new interface driver gtco
<6>[ 1.431014] usbcore: registered new interface driver hanwang
<6>[ 1.431039] usbcore: registered new interface driver kbtab
<6>[ 1.431062] usbcore: registered new interface driver wacom
<6>[ 2.426336] usbcore: registered new interface driver usbhid
<6>[ 2.426341] usbhid: USB HID core driver
<6>[ 2.427194] usb_bam_ipa_create_resources: Failed to create USB_PROD resource
<6>[ 2.428933] usbcore: registered new interface driver snd-usb-audio
<6>[ 2.471332] qpnp_charger_probe: success chg_dis = 0, bpd = 1, usb = 0, dc = 0 batt_present = 1 b_health= 1
<3>[ 3.805914] enable_store: android_usb: already disabled
<6>[ 3.852097] qpnp_chg_rb_work: stopping worker usb/dc disconnected
<6>[ 1300.274689] android_usb gadget: high-speed config #1: fe8050c8.android_usb
We see the usb drivers are loaded and (at 1300sec after booting) my usb was plugged-in and ok.
Maybe you can check this on your phone too?
Click to expand...
Click to collapse
On my phone:
Code:
t /sys/devices/virtual/android_usb/android0/idProduct <
51dc
t /sys/devices/virtual/android_usb/android0/idVendor <
0fce
USB enabled:
Code:
t /sys/devices/virtual/android_usb/android0/enable <
1
On this part I think there is a problem...
Code:
# dmesg | grep usb:
[email protected]:/ $ su
[email protected]:/ # dmesg | grep usb
[ 1928.571892] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 1929.080038] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[email protected]:/ #
Edited:
I tried again the last part, I connected the phone to the computer
Code:
[email protected]:/ $ su
[email protected]:/ # dmesg | grep usb
[ 1928.571892] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 1929.080038] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2361.900773] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2414.187768] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2414.719516] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2419.700808] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[email protected]:/ #
Edited 2:
I tried with a different cable
Code:
[email protected]:/ $ dmesg | grep usb
[ 2660.822263] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2662.760351] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2664.695660] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2666.630532] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2668.571292] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2670.518925] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2733.714283] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2733.829405] dwc3 f9200000.dwc3: gadget android_usb data soft-disconnect
[ 2734.189998] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2735.154361] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2735.421464] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2737.360361] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2748.249766] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2748.369898] dwc3 f9200000.dwc3: gadget android_usb data soft-disconnect
[ 2748.769762] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2750.402083] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2750.691646] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2752.634542] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2754.584895] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2756.530012] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2758.477175] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2760.414030] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2769.675397] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2769.789545] dwc3 f9200000.dwc3: gadget android_usb data soft-disconnect
[ 2770.219536] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2784.570479] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2785.341245] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[email protected]:/ $
JuanMnz93 said:
[email protected]:/ # dmesg | grep usb
[ 1928.571892] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 1929.080038] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2361.900773] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2414.187768] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2414.719516] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2419.700808] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[email protected]:/ #
Click to expand...
Click to collapse
With your error I found some kernel patch (in cyanogen tree).
Anyway it seems the usb_gadget is broken on this kernel. You can try combination of booting with/without adb enabled but I think it wont change anything.
Did you see my last post about core.zip/boot.img?
When I try the boot.img I provide a few post earlier my phone was frozen. As I don't like open the access cover of my phone so I use the 'volume-up + power' (with usb plugged-in) disaster-recovery and my phone reboot in download mode. Is it working for you?
Did you try turning your phone off completely by pushing the power off buton (near the sdcard) then entering download mode or other things? (turn off this way without usb cable, press volume up or down while plugin the cable)
---------- Post added at 22:52 ---------- Previous post was at 22:50 ----------
JuanMnz93 said:
I tried with a different cable
Code:
[ 2760.414030] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[ 2769.675397] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2769.789545] dwc3 f9200000.dwc3: gadget android_usb data soft-disconnect
[ 2770.219536] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2784.570479] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2785.341245] dwc3 f9200000.dwc3: gadget android_usb data soft-connect
[email protected]:/ $
Click to expand...
Click to collapse
There is a real connectivity problem with this cable
But maybe the usb port of the phone is broken? Did you clean it up?
edit:
you kernel configuration is ok: vendorId/productId and usb enabled.
nailyk said:
With your error I found some kernel patch (in cyanogen tree).
Anyway it seems the usb_gadget is broken on this kernel. You can try combination of booting with/without adb enabled but I think it wont change anything.
Did you see my last post about core.zip/boot.img?
When I try the boot.img I provide a few post earlier my phone was frozen. As I don't like open the access cover of my phone so I use the 'volume-up + power' (with usb plugged-in) disaster-recovery and my phone reboot in download mode. Is it working for you?
Did you try turning your phone off completely by pushing the power off buton (near the sdcard) then entering download mode or other things? (turn off this way without usb cable, press volume up or down while plugin the cable)
---------- Post added at 22:52 ---------- Previous post was at 22:50 ----------
There is a real connectivity problem with this cable
But maybe the usb port of the phone is broken? Did you clean it up?
edit:
you kernel configuration is ok: vendorId/productId and usb enabled.
Click to expand...
Click to collapse
I just tried those methods and my PC recognized it as USB not recognized".
The USB port problem could be, the thing is that I don't understand why this happened after flashing andropluskernel...
I see the post about boot.img but I'm so scared about flashing the boot and lost my phone if it doesn't boot :crying:
PD: My phone shows blue light when I press volume up when I connect the USB cable while it is off (fastboot mode) and it shows a red and green light when I press volume down but my PC doesn't recognize it
EDITED: I think my solution for now it's making the recovery works in order to try to change the rom with all the wipes
JuanMnz93 said:
I just tried those methods and my PC recognized it as USB not recognized".
The USB port problem could be, the thing is that I don't understand why this happened after flashing andropluskernel...
I see the post about boot.img but I'm so scared about flashing the boot and lost my phone if it doesn't boot :crying:
Click to expand...
Click to collapse
For now your phone is almost working so I understand.
JuanMnz93 said:
PD: My phone shows blue light when I press volume up when I connect the USB cable while it is off (fastboot mode) and it shows a red and green light when I press volume down but my PC doesn't recognize it
Click to expand...
Click to collapse
It is really strange! The phone detect the usb connection well: blue light = fastboot and the 'red/green/off' = download.
Try to connect on a usb 2.0 port directly on the motherboard (not in the front panel), without usb hub, without extension cable (right word?)
Any chance you can plug this phone on a linux computer and get the dmesg output? (dmesg | tail -50)
JuanMnz93 said:
EDITED: I think my solution for now it's making the recovery works in order to try to change the rom with all the wipes
Click to expand...
Click to collapse
Time to switch to cyanogenMod
I reflect on it but as you can't boot with the new key combination your bootloader seems to be the old one. So the only way to get a recovery is a working kernel as I know...
nailyk said:
For now your phone is almost working so I understand.
It is really strange! The phone detect the usb connection well: blue light = fastboot and the 'red/green/off' = download.
Try to connect on a usb 2.0 port directly on the motherboard (not in the front panel), without usb hub, without extension cable (right word?)
Any chance you can plug this phone on a linux computer and get the dmesg output? (dmesg | tail -50)
Time to switch to cyanogenMod
I reflect on it but as you can't boot with the new key combination your bootloader seems to be the old one. So the only way to get a recovery is a working kernel as I know...
Click to expand...
Click to collapse
I connected to USB 2.0
Code:
[email protected]:/ $ dmesg | grep usb
[ 2322.831931] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2323.359519] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2336.244450] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2383.710482] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2384.259534] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2385.188135] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2392.669067] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2393.209843] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2393.725163] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2414.634684] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2415.139530] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2416.047791] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2436.343992] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2436.859542] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2438.512870] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[ 2458.806967] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=0
[ 2459.340378] qpnp_chg_rb_work: stopping worker usb/dc disconnected
[ 2460.763578] msm-dwc3 msm_dwc3: dwc3_msm_power_set_property_usb: set bsv=1
[email protected]:/ $
I guess I don't have the new bootloader because when I flashed the ZyxxOS rom I used Phil recovery using volume up bottom after press power bottom and a purple light appear, (the light used to change to orange when I pressed volume up to enter into recovery)
EDITED: I lost the recovery after flashing ZyxxOS rom.
Hello there!
I am struggling to get the Silead GSL5680 Touchscreen to work, the driver that android has for silead seems to not support the GSL5680. (https://github.com/hardkernel/linux/blob/odroidg12-4.9.y/drivers/input/touchscreen/silead.c#L543)
Specs:
-> Device: Odroid C4
-> OS: Android 9.0
-> Kernel Version: 4.9.113
The touchscreen is connected via I2C, I installed I2C-tools to check:
130|odroidc4:/ # i2cdetect -l
i2c-1 i2c Meson I2C adapter I2C adapter
i2c-0 i2c Meson I2C adapter I2C adapter
For i2c-0 I get:
odroidc4:/ # i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: 40 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
(The touchscreen should always reply on 0x40 regarding to the datasheet, so it should be connected right)
odroidc4:/ # i2cget 0 0x40
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will read from device file /dev/i2c-0, chip address 0x40, current data
address, using read byte.
Continue? [Y/n] y
0xfa
I downloaded the full android source and tried to build the system with this driver I found online:
I had to edit gslx680_ds.c (using <linux/gpio.h> instead of <asm/gpio.h> and added <linux/module.h>) so it would compile successfully.
linux_kernel/gslx680_ds.h at 9deb1afd3fd2328cb3f6b1ee99dc607aaa0dab3e · hansiglaser/linux_kernel
Kernel Linux Repository for UDOO. Contribute to hansiglaser/linux_kernel development by creating an account on GitHub.
github.com
linux_kernel/gslx680_ds.inc.c at 9deb1afd3fd2328cb3f6b1ee99dc607aaa0dab3e · hansiglaser/linux_kernel
Kernel Linux Repository for UDOO. Contribute to hansiglaser/linux_kernel development by creating an account on GitHub.
github.com
linux_kernel/gslx680_ds.c at 9deb1afd3fd2328cb3f6b1ee99dc607aaa0dab3e · hansiglaser/linux_kernel
Kernel Linux Repository for UDOO. Contribute to hansiglaser/linux_kernel development by creating an account on GitHub.
github.com
And put them in common/drivers/input/touchscreen/GSL5680
Also created a Makefile and Kconfig:
Makefile:
obj-$(CONFIG_TOUCHSCREEN_GSL5680) += gslx680_ds.o
Kconfig:
#
# Touchscreen driver configuration
#
config TOUCHSCREEN_GSL5680
tristate "gsl5680 touchscreen driver"
depends on INPUT && I2C
default m
help
gsl5680 touchscreen driver
I added obj-$(CONFIG_INPUT_TOUCHSCREEN) += gsl5680/ to the Makefile in common/drivers/touchscreen and the source in Kconfig in .../touchscreen
I added gslx680-i2c.dts in common/arch/arm64/boot/dts/amlogic/overlays/odroidc4/ (maybe that is wrong?):
/dts-v1/;
/plugin/;
#include <dt-bindings/gpio/meson-g12a-gpio.h>
#include <dt-bindings/gpio/gpio.h>
/ {
[email protected] {
// i2c3 aliased with i2c1.
target = <&i2c3>;
__overlay__ {
status = "okay";
#address-cells = <1>;
#size-cells = <0>;
touchscreen: [email protected] {
compatible = "silead,gslx680";
reg = <0x40>;
interrupt-parent = <&gpio1>;
power-gpios = <&gpio1 15 GPIO_ACTIVE_LOW>;
pinctrl-0 = <&pinctrl_gslx680>;
pinctrl-names = "default";
};
};
};
};
Then I added it in the Makefile.
Then I edited the odroidc4_android_defconfig with make menuconfig and enabled the GSL5680 driver with 'y'
After building the image and installing it on a sdcard, I booted the system, but could not see the driver with lsmod or dmesg.
When I then tried to manually add the gslx680_ds.ko with insmod gslx680_ds.ko, the response was that this module is already loaded.
I would be very thankful for any ideas and help!
I have a Onda Obook tablet with this touch screen and I want to know also about this. Do you have success?