Hi, I try to import and this Library in Eclipse:
https://github.com/JakeWharton/Android-ViewPagerIndicator
But there is a problem with the Maven installer because
he cannot resolve all the Depencies. From the "issue" tab
on github I got the info that I have update the depencies
from r4 to r6 in the pom.xml of the project. I tried this
but everytime I try to install the Library with "mvn install"
I get the following error:
Code:
c:\JakeWharton-Android-ViewPagerIndicator-3db7585>mvn install
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
com.viewpagerindicator:library:apklib:2.2.0
[WARNING] 'build.plugins.plugin.version' for com.jayway.maven.plugins.android.ge
neration2:maven-android-plugin is missing. @ line 36, column 12
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
com.viewpagerindicator:sample:apk:2.2.0
[WARNING] 'build.plugins.plugin.version' for com.jayway.maven.plugins.android.ge
neration2:maven-android-plugin is missing. @ line 48, column 12
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten t
he stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support buildin
g such malformed projects.
[WARNING]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Android-ViewPagerIndicator (Parent)
[INFO] Android-ViewPagerIndicator
[INFO] Android-ViewPagerIndicator Sample
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Android-ViewPagerIndicator (Parent) 2.2.0
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ parent ---
[INFO] Installing c:\JakeWharton-Android-ViewPagerIndicator-3db7585\pom.xml to C
:\Users\Cracksoldier\.m2\repository\com\viewpagerindicator\parent\2.2.0\parent-2
.2.0.pom
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Android-ViewPagerIndicator 2.2.0
[INFO] ------------------------------------------------------------------------
Downloading: http://r.jakewharton.com/maven/release/android/support/compatibilit
y-v4/r4/compatibility-v4-r4.pom
Downloading: http://repo1.maven.org/maven2/android/support/compatibility-v4/r4/c
ompatibility-v4-r4.pom
[WARNING] The POM for android.support:compatibility-v4:jar:r4 is missing, no dep
endency information available
Downloading: http://r.jakewharton.com/maven/release/android/support/compatibilit
y-v4/r4/compatibility-v4-r4.jar
Downloading: http://repo1.maven.org/maven2/android/support/compatibility-v4/r4/c
ompatibility-v4-r4.jar
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Android-ViewPagerIndicator (Parent) ............... SUCCESS [0.204s]
[INFO] Android-ViewPagerIndicator ........................ FAILURE [1.636s]
[INFO] Android-ViewPagerIndicator Sample ................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.953s
[INFO] Finished at: Thu Dec 22 18:29:20 CET 2011
[INFO] Final Memory: 10M/108M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project library: Could not resolve dependencie
s for project com.viewpagerindicator:library:apklib:2.2.0: Could not find artifa
ct android.support:compatibility-v4:jar:r4 in com.jakewharton (http://r.jakewhar
ton.com/maven/release) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyReso
lutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :library
c:\JakeWharton-Android-ViewPagerIndicator-3db7585>
I am new to Maven and I cant get it working. I also tried to import
it as a normal Android Project and then assing the library to the
sample project but then I get 1053 error(s).
I changed the depencies in the pom.xml files so that it looks
likes this:
Code:
android.support
compatibility-v6
${android.support.version}
I also tried:
compatibility-r6
compatibility-v4-r6
and I also tried to change this:
Code:
r4
to this:
Code:
r6
But nothing worked.
I hope anybody can help me because I am desperated right now
I tried everything in the last 2 days.
Edit:// Problem is solved
Best Regards
Hey guys,
I'm trying to port TWRP to my phone Samsung Galaxy S Advance, GT-I9070.
To do that I switched the stock recovery files inside the Initramfs with TWRP files and compiled the kernel using samsung's source.
So, now twrp is booting and working fine, but I have an issue with the J4FS driver.
the module loads but the j4fs partition is not mounting.
here's the error I noticed in dmesg
Code:
<4>[ 14.585052] j4fs: module license 'unspecified' taints kernel.
<4>[ 14.585144] Disabling lock debugging due to kernel taint
<4>[ 14.597229] FlashDevMount : filp_open() OK....!
<3>[ 14.597991] init: SEC_DEVENC ***[/dev/block/mmcblk0p1][0]
<4>[ 14.620117] fsd_reclaim 1291: MST is not recognized(mst.magic=0x00000000)
<4>[ 14.620178] fsd_reclaim 1292: MST is not recognized
<4>[ 14.629272] [<c07b484c>] (unwind_backtrace+0x0/0xf0) from [<c0c9d51c>] (dump_stack+0x10/0x24)
<4>[ 14.629425] [<c0c9d51c>] (dump_stack+0x10/0x24) from [<bf003ac8>] (fsd_reclaim+0x3bc/0xe40 [j4fs])
<4>[ 14.629608] [<bf003ac8>] (fsd_reclaim+0x3bc/0xe40 [j4fs]) from [<bf0017bc>] (j4fs_fill_super+0x2e0/0x364 [j4fs])
<4>[ 14.629730] [<bf0017bc>] (j4fs_fill_super+0x2e0/0x364 [j4fs]) from [<c08916c8>] (get_sb_bdev+0x110/0x16c)
<4>[ 14.629852] [<c08916c8>] (get_sb_bdev+0x110/0x16c) from [<bf0002f8>] (j4fs_get_sb+0x58/0x6c [j4fs])
<4>[ 14.629974] [<bf0002f8>] (j4fs_get_sb+0x58/0x6c [j4fs]) from [<c08904a0>] (vfs_kern_mount+0x58/0x108)
<4>[ 14.630065] [<c08904a0>] (vfs_kern_mount+0x58/0x108) from [<c0890594>] (do_kern_mount+0x34/0xd8)
<4>[ 14.630187] [<c0890594>] (do_kern_mount+0x34/0xd8) from [<c08a7b94>] (do_mount+0x7a4/0x848)
<4>[ 14.630279] [<c08a7b94>] (do_mount+0x7a4/0x848) from [<c08a7cbc>] (sys_mount+0x84/0xc4)
<4>[ 14.630371] [<c08a7cbc>] (sys_mount+0x84/0xc4) from [<c07ad740>] (ret_fast_syscall+0x0/0x30)
<4>[ 14.630554] fsd_reclaim 1607: Error(nErr=0x00000000)
<4>[ 14.630615] fsd_reclaim 1612: j4fs_rw_start is set to default value(128KB)
<4>[ 14.630737] j4fs_fill_super 1311: Error(nErr=0x40000000)
<6>[ 14.641357] param_init
<3>[ 14.641448] lfs_param_op: filp_open failed. (-2)
<3>[ 14.641510] param_init(358): Loading parameters failed. Parameters have been initialized as default.
and the compilation warnings
Code:
LD drivers/samsung/built-in.o
LD drivers/samsung/j4fs/built-in.o
CC [M] drivers/samsung/j4fs/j4fs_kernel.o
drivers/samsung/j4fs/j4fs_kernel.c: In function 'j4fs_write_begin':
drivers/samsung/j4fs/j4fs_kernel.c:237: warning: format '%d' expects type 'int', but argument 4 has type 'loff_t'
drivers/samsung/j4fs/j4fs_kernel.c:237: warning: format '%d' expects type 'int', but argument 5 has type 'long unsigned int'
drivers/samsung/j4fs/j4fs_kernel.c: In function 'j4fs_fill_super':
drivers/samsung/j4fs/j4fs_kernel.c:1224: warning: unused variable 'len'
drivers/samsung/j4fs/j4fs_kernel.c:1224: warning: unused variable 'tmp'
drivers/samsung/j4fs/j4fs_kernel.c: At top level:
drivers/samsung/j4fs/j4fs_kernel.c:1499: warning: initialization from incompatible pointer type
drivers/samsung/j4fs/j4fs_kernel.c: In function 'j4fs_readdir':
drivers/samsung/j4fs/j4fs_kernel.c:806: warning: the frame size of 1040 bytes is larger than 1024 bytes; see http://go/big_stack_frame
CC [M] drivers/samsung/j4fs/llid_kernel.o
drivers/samsung/j4fs/llid_kernel.c: In function 'FlashDevRead':
drivers/samsung/j4fs/llid_kernel.c:98: warning: passing argument 1 of 'printk' makes pointer from integer without a cast
include/linux/kernel.h:346: note: expected 'const char *' but argument is of type 'int'
drivers/samsung/j4fs/llid_kernel.c:65: warning: unused variable 'part_id'
drivers/samsung/j4fs/llid_kernel.c:63: warning: unused variable 'nVol'
drivers/samsung/j4fs/llid_kernel.c: In function 'FlashDevWrite':
drivers/samsung/j4fs/llid_kernel.c:156: warning: passing argument 1 of 'printk' makes pointer from integer without a cast
include/linux/kernel.h:346: note: expected 'const char *' but argument is of type 'int'
drivers/samsung/j4fs/llid_kernel.c:123: warning: unused variable 'part_id'
drivers/samsung/j4fs/llid_kernel.c:121: warning: unused variable 'nVol'
CC [M] drivers/samsung/j4fs/fsd_common.o
drivers/samsung/j4fs/fsd_common.c: In function 'fsd_write':
drivers/samsung/j4fs/fsd_common.c:300: warning: ISO C90 forbids mixed declarations and code
drivers/samsung/j4fs/fsd_common.c: In function 'fsd_reclaim':
drivers/samsung/j4fs/fsd_common.c:1270: warning: ISO C90 forbids mixed declarations and code
LD [M] drivers/samsung/j4fs/j4fs.o
LD drivers/samsung/param/built-in.o
CC [M] drivers/samsung/param/param.o
drivers/samsung/param/param.c:58: warning: 'param_check' defined but not used
drivers/samsung/param/param.c: In function 'param_show_info':
drivers/samsung/param/param.c:234: warning: the frame size of 1032 bytes is larger than 1024 bytes; see http://go/big_stack_frame
how can I fix this error?
my kernel sources are here: http://github.com/diego-ch/android_kernel_samsung_janice
You need cyanogen source to properly compile twrp...
It's pretty easy, all you do is switch out the bootable/recovery with redo bootable/recovery
Change a few lines in your board config and then*compile the kernel*
Here's the official guide:*http://rootzwiki.com/index.php?/topic/23903-How-to-Compile-TWRP-from-Source
And you can apply the recovery without flashing a whole kernel using this:*https://github.com/smasher816/Team-Win-Recovery-Project-Samsung/blob/master/injectTWRP-template.zip*
Just click on the "raw" button to download
Then add your ramdisk-recovery and your good!
When flashing you must mount system before hand because that is a universal script and does not include mount points for mounting system*
Sent from my HTC PH39100 using Tapatalk 2
mg2195 said:
You need cyanogen source to properly compile twrp...
It's pretty easy, all you do is switch out the bootable/recovery with redo bootable/recovery
Change a few lines in your board config and then*compile the kernel*
Here's the official guide:*http://rootzwiki.com/index.php?/topic/23903-How-to-Compile-TWRP-from-Source
And you can apply the recovery without flashing a whole kernel using this:*https://github.com/smasher816/Team-Win-Recovery-Project-Samsung/blob/master/injectTWRP-template.zip*
Just click on the "raw" button to download
Then add your ramdisk-recovery and your good!
When flashing you must mount system before hand because that is a universal script and does not include mount points for mounting system*
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for answering mg2195!
I already got TWRP running,
the only issue I have is the j4fs driver that doesnt work.
I also dont have the board config files for this device as there are no other devs working on it,
unless samsung's open source platform code could help.
Hallo, any one know whats wrong with Jelly Bean AOSP netd, here is logcat:
Code:
I/Netd (10975): Netd 1.0 starting
E/BandwidthController(10975): runIptablesCmd(): failed /system/bin/iptables -t raw -N bw_raw_PREROUTING res=256
E/BandwidthController(10975): runIptablesCmd(): failed /system/bin/ip6tables -t raw -N bw_raw_PREROUTING res=256
D/MDnsDS (10975): MDnsSdListener::Hander starting up
D/MDnsDS (10975): MDnsSdListener starting to monitor
D/MDnsDS (10975): Going to poll with pollCount 1
E/Netd (10975): Unable to start MDnsSdListener (Success)
E/SocketListener(10975): Obtaining file descriptor socket 'mdns' failed: Success
E/NetdConnector( 2399): Communications error: java.io.IOException: No such file or directory
E/NetdConnector( 2399): Error in NativeDaemonConnector: java.io.IOException: No such file or directory
I/Netd (11140): Netd 1.0 starting
E/BandwidthController(11140): runIptablesCmd(): failed /system/bin/iptables -t raw -N bw_raw_PREROUTING res=256
E/BandwidthController(11140): runIptablesCmd(): failed /system/bin/ip6tables -t raw -N bw_raw_PREROUTING res=256
D/MDnsDS (11140): MDnsSdListener::Hander starting up
D/MDnsDS (11140): MDnsSdListener starting to monitor
E/Netd (11140): Unable to start MDnsSdListener (Success)
E/SocketListener(11140): Obtaining file descriptor socket 'mdns' failed: Success
Is these related to kernel or something related to android, many thanks for any hint!!!
Look this - same prob?
...add this section at the end of init.rc:
Code:
service mdnsd /system/bin/mdnsd
class main
user mdnsr
group inet net_raw
socket mdnsd stream 0660 mdnsr inet
disabled
oneshot
https://groups.google.com/forum/#!msg/android-platform/faAcGG4QOPo/MDMBeGuF8BkJ
akkufix said:
Look this - same prob?
...add this section at the end of init.rc:
Code:
service mdnsd /system/bin/mdnsd
class main
user mdnsr
group inet net_raw
socket mdnsd stream 0660 mdnsr inet
disabled
oneshot
https://groups.google.com/forum/#!msg/android-platform/faAcGG4QOPo/MDMBeGuF8BkJ
Click to expand...
Click to collapse
Yes I added already to init.rc before opened our thread! Not working! Seems something about iptables missing in kernel (see error about res=256 !)... res=256cause wrong command to iptables! Without these "res=256" command to iptables is ok, so what mean these "res"?
munjeni said:
Yes I added already to init.rc before opened our thread! Not working! Seems something about iptables missing in kernel (see error about res=256 !)... res=256cause wrong command to iptables! Without these "res=256" command to iptables is ok, so what mean these "res"?
Click to expand...
Click to collapse
Don't know either what "res" means. Maybe reserved, resolution, received... seems to be a buffer, frame or location.
So, but what i noticed is, you have command "-N bw_raw_PREROUTING", while the guy in my link used "-D bw_raw_PREROUTING".
As man-page of iptable says for -N, --new-chain chain "There must be no target of that name already".
And for command -D --delete chain rule-specification and --delete chain rulenum
"Delete one or more rules from the selected chain. There are two versions of this command: the rule can be specified as a number in the chain (starting at 1 for the first rule) or a rule to match."
This makes the difference, cause "res=256" is already "loaded"??
Or i don't understand anything? :silly:
For reference:
http://ipset.netfilter.org/iptables.man.html
Here http://ipset.netfilter.org/iptables.man.html I can not see anything related to "res" have no idea what these part of the command mean! For example:
/system/bin/iptables -t mangle -D bw_mangle_POSTROUTING res=256
munjeni said:
Here http://ipset.netfilter.org/iptables.man.html I can not see anything related to "res" have no idea what these part of the command mean! For example:
/system/bin/iptables -t mangle -D bw_mangle_POSTROUTING res=256
can not see any reference to these res in iptables
Click to expand...
Click to collapse
I'm looking around for this res and only saw that it is sometimes 256 or 756.
No description at all, yet.
I also found some other guys, having same problems with "Netd 1.0 starting", after putting that lines above into init.rc
This one - https://groups.google.com/forum/?fromgroups=#!topic/renesas-emev-osp/XSdLmPgD9Og
sayed
Code:
BTW - Kernel needs a rebuild too.
And another one - https://groups.google.com/forum/?fromgroups=#!topic/android-building/3qDAbPjnHJc
Code:
1. fastboot -w flashall # This was my initial full system flash after changing the kernels.
2. adb reboot-bootloader
3. fastboot flash system
Step 3 seemed to have done it.
Will try with Tuna JB kernel (quota2)...
Edit:
Think I found a problem, maybe? See:
~ # strace -c netd
strace -c netd
iptables: Chain already exists.
iptables: Chain already exists.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
ip6tables: Bad rule (does a matching rule exist in that chain?).
iptables: Bad rule (does a matching rule exist in that chain?).
ip6tables: Bad rule (does a matching rule exist in that chain?).
iptables: Too many links.
iptables: Too many links.
ip6tables: Too many links.
iptables: Too many links.
ip6tables: Too many links.
iptables: Chain already exists.
iptables: Chain already exists.
iptables: Chain already exists.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
iptables v1.4.11.1: Couldn't find target `penalty_box'
Try `iptables -h' or 'iptables --help' for more information.
ip6tables v1.4.11.1: Couldn't find target `penalty_box'
Try `ip6tables -h' or 'ip6tables --help' for more information.
Click to expand...
Click to collapse
Found some posts on google about "res", these res comming after part of command "--penalty_box res=blabla" so I think "res" is part of subcomand penalty_box ? Will research more, curently nothing found for penalty_box in kernel... researching...
Ok. But what are those "chain already exist" and "no chain/target/match by this name" ? Is there something running in circle?
Edit:
This "already exist" normaly indicates you are try to create the chain more than once. (iptables -N chain name)
For the other prob, maybe it helped to look what tables exists with "iptables -L" ?
Sent from my MT27i using xda app-developers app
Got it!!!
http://img850.imageshack.us/img850/5403/device20121209123052.png
http://img231.imageshack.us/img231/3299/device20121209123124.png
http://img803.imageshack.us/img803/4497/device20121209123143.png
http://img838.imageshack.us/img838/2312/device20121209123024.png
http://img545.imageshack.us/img545/4383/device20121209123117.png
munjeni said:
Got it!!! Problem was missing part of netd in init.rc... finally:
JellyBean... booted!!!
http://img850.imageshack.us/img850/5403/device20121209123052.png
http://img231.imageshack.us/img231/3299/device20121209123124.png
http://img803.imageshack.us/img803/4497/device20121209123143.png
http://img838.imageshack.us/img838/2312/device20121209123024.png
http://img545.imageshack.us/img545/4383/device20121209123117.png
Click to expand...
Click to collapse
Great news. Will you share your sources? I would like to try JB on my U.
Source code is bassed on FXP CM9, but I have no working source because there was a lot of fails so I fixed these things by manyally copying libs, headers ...etc, I am not able to colect all changes, its on my computer! Android source I used is AOSP jb-dev branch! If something fail on your build ask me I will help you to get these rom booted! Android build is not useable in any way because have missing audio, missing sdcard ...etc, we can not do more without help by Sony! We need to ask Sony to give us new brebuilts compatible with JellyBean, ot to give us source code for these things, for example libhardware, libsensors, libaudio, at_core, libril, ste_omxcomponents...!
munjeni said:
Source code is bassed on FXP CM9, but I have no working source because there was a lot of fails so I fixed these things by manyally copying libs, headers ...etc, I am not able to colect all changes, its on my computer! Android source I used is AOSP jb-dev branch! If something fail on your build ask me I will help you to get these rom booted! Android build is not useable in any way because have missing audio, missing sdcard ...etc, we can not do more without help by Sony! We need to ask Sony to give us new brebuilts compatible with JellyBean, ot to give us source code for these things, for example libhardware, libsensors, libaudio, at_core, libril, ste_omxcomponents...!
Click to expand...
Click to collapse
Thanks a lot. Yes, I know that a lot of things missing for jb, but i would like to try cm10 in my U. Could be better if sony give us sources, but i think we won't get it. And i think we can't use new prebuilts while we don't get the first official jb rom.
munjeni said:
Got it!!!
http://img850.imageshack.us/img850/5403/device20121209123052.png
http://img231.imageshack.us/img231/3299/device20121209123124.png
http://img803.imageshack.us/img803/4497/device20121209123143.png
http://img838.imageshack.us/img838/2312/device20121209123024.png
http://img545.imageshack.us/img545/4383/device20121209123117.png
Click to expand...
Click to collapse
Hi,
facing the same problem...
Can you please share the solution? Tired of searching for it.
Thanks in advance.
Hello,
As most threads are full of thanks posts or non development related posts, I am making a new one.
A note to everyone: This is a DEV thread, every post not related to this project will be removed!
What is the current status?
Currently the kernel is booting, but touchscreen isn't working.
What's working:
Booting into Android
Screen (Showing things, not touch)
Sound
What's not working or not tested because of touchscreen:
Everything else
Sources:
https://github.com/nickholtus/msm7x30-3.4.x-nAa
Credits:
NobodyAtAll for the initial source
MikeNG for a lot of fixes
DooMLoRD For giving me the device and a lot of work on the source
Mikeioannina A lot of work on the sources
Again: Please keep this thread development related!
If I helped you, please press thanks or consider donating to me!
Current status on touchscreen:
Still investigating for the problem, can't really find anything yet.
Threads with some more info:
http://forum.xda-developers.com/showthread.php?t=2563508
Is the driver crashing? Post dmesg
Sent from my C6902 using xda app-developers app
DooMLoRD said:
Is the driver crashing? Post dmesg
Sent from my C6902 using xda app-developers app
Click to expand...
Click to collapse
Will post this evening, am at work right now.
Bakisha posted a dmesg here http://forum.xda-developers.com/showpost.php?p=48869177&postcount=20
Although it is not from the most recently updated test kernel.
I've posted even full bugreport from zImage(4), wich i think is latest test version. I'll copy paste dmesg from there and attach it here
Bakisha said:
I've posted even full bugreport from zImage(4), wich i think is latest test version. I'll copy paste dmesg from there and attach it here
Click to expand...
Click to collapse
ok so here is what i see from the dmesg:
Code:
<6>[ 5.784790] synaptics_touchpad: product 1, firmware revision 13, bootloader date 2011-02-16
<6>[ 5.785827] input: synaptics_touchpad as /devices/virtual/input/input4
<6>[ 5.786254] synaptics_touchpad 4-0020: synaptics_touchpad_set_power: powered 1, activated 0, users 0, standby 0
<7>[ 5.786834] CY8CTMA300_TOUCH: V0.9b-mt built Jan 14 2014 22:15:21
<7>[ 5.787200] CY8CTMA300_TOUCH: SPI setup (requesting 1000000Hz) OK
...
<6>[ 5.949859] CY8CTMA300_TOUCH: TP_REG_FW 0x00
<6>[ 6.109924] CY8CTMA300_TOUCH: Bootloader FW Ver 0.0
<6>[ 6.129882] CY8CTMA300_TOUCH: Application FW Ver 0.0
<6>[ 6.149902] CY8CTMA300_TOUCH: Silicon Revision E
<6>[ 6.169891] CY8CTMA300_TOUCH: Customer ID 0
<6>[ 6.189880] CY8CTMA300_TOUCH: old FW version, applying reset workarounds
<6>[ 6.330108] input: cy8ctma300_touch as /devices/platform/spi_qsd.0/spi_master/spi0/spi0.0/input/input5
<6>[ 6.334136] CY8CTMA300_TOUCH: invalid data?
then...
Code:
<6>[ 33.252838] CY8CTMA300_TOUCH: invalid data?
<6>[ 33.651550] CY8CTMA300_TOUCH: invalid data?
<6>[ 34.024230] synaptics_touchpad 4-0020: synaptics_touchpad_set_power: powered 0, activated 0, users 1, standby 0
...
<6>[ 34.026611] synaptics_touchpad 4-0020: synaptics_touchpad_set_power: powered 0, activated 0, users 0, standby 0
<6>[ 34.027099] synaptics_touchpad 4-0020: synaptics_touchpad_set_power: powered 0, activated 0, users 1, standby 0
<6>[ 34.027130] synaptics_touchpad 4-0020: synaptics_touchpad_set_power: powered 0, activated 0, users 0, standby 0
<6>[ 34.050384] CY8CTMA300_TOUCH: invalid data?
<6>[ 34.491516] CY8CTMA300_TOUCH: invalid data?
<6>[ 34.890441] CY8CTMA300_TOUCH: invalid data?
see that the "set_power" is powered 0... something is powering down the touchpad, may be due to "invalid data?"
can u give me exact time stamp from bootup when the touchscreen stops working? post the corresponding dmesg...
DooMLoRD said:
see that the "set_power" is powered 0... something is powering down the touchpad, may be due to "invalid data?"
can u give me exact time stamp from bootup when the touchscreen stops working? post the corresponding dmesg...
Click to expand...
Click to collapse
I;ll attach dmesg that i just made, but i don't think that lines have something to do with touchscreen because line with that "powered 0" is even in dmesg logs of GB and ICS kernels for Play (i've checked on Lupus kernels for GB and ICS and on those touchpads and touchscreen works normally)
But i noticed difference in next lines:
Code:
<7>[ 5.525909] CY8CTMA300_TOUCH: V0.9b-mt built Jan 14 2014 22:15:21
<7>[ 5.526306] CY8CTMA300_TOUCH: SPI setup (requesting 1000000Hz) OK
<6>[ 5.584747] Charging with 0mA current
<6>[ 5.584960] entering into lpm
<6>[ 5.585144] msm_otg_suspend: Turn on phy comparators
<6>[ 5.585449] msm_otg_suspend: usb in low power mode
<6>[ 5.685119] CY8CTMA300_TOUCH: TP_REG_FW 0x00
<6>[ 5.845153] CY8CTMA300_TOUCH: Bootloader FW Ver 0.0
<6>[ 5.865142] CY8CTMA300_TOUCH: Application FW Ver 0.0
<6>[ 5.885192] CY8CTMA300_TOUCH: Silicon Revision E
<6>[ 5.905181] CY8CTMA300_TOUCH: Customer ID 0
<6>[ 5.925170] CY8CTMA300_TOUCH: old FW version, applying reset workarounds
<6>[ 6.065368] input: cy8ctma300_touch as /devices/platform/spi_qsd.0/spi_master/spi0/spi0.0/input/input5
<6>[ 6.071472] CY8CTMA300_TOUCH: invalid data?
<6>[ 6.084808] CY8CTMA300_TOUCH: Device registered OK
And in other kernels (even in Wedgess's 2.6 kernel for his test release JB4.2) it is like:
Code:
<7>CY8CTMA300_TOUCH: V0.9b-mt built Feb 5 2014 22:14:40
<7>CY8CTMA300_TOUCH: SPI setup (requesting 1000000Hz) OK
<6>CY8CTMA300_TOUCH: TP_REG_FW 0x00
<6>CY8CTMA300_TOUCH: Bootloader FW Ver 0.1
<6>CY8CTMA300_TOUCH: Application FW Ver 0.114
<6>CY8CTMA300_TOUCH: Silicon Revision E
<6>CY8CTMA300_TOUCH: Customer ID 5
<6>CY8CTMA300_TOUCH: SSD firmware [Project ID 7]
<3>CY8CTMA300_TOUCH: firmware versions match.
<6>input: cy8ctma300_touch as /devices/platform/spi_qsd.0/spi0.0/input/input3
<6>CY8CTMA300_TOUCH: Device registered OK
<6>GPIO Input Driver: Start gpio inputs for keypad-zeus in interrupt mode
<6>GPIO Input Driver: Start gpio inputs for keypad-zeus in interrupt mode
<6>GPIO Input Driver: Start gpio inputs for keypad-zeus in interrupt mode
<6>GPIO Input Driver: Start gpio inputs for keypad-zeus in interrupt mode
<6>GPIO Input Driver: Start gpio inputs for keypad-zeus in interrupt mode
<6>input: keypad-zeus as /devices/virtual/input/input4
i think probably is touchpad related also..seems like kernel is powering down the touchpads and touchscreen. @nickholtus and if you try kernel like NEOL as the board is the same, but kernel wont look for touchpads..and maybe we can flash on play without touchpads support..just a test,we can flash neol kernel and vice versa..only touchpads and camera inverted..but maybe its possible to make it work.
Personally I think the problem is here:
<6>[ 5.845153] CY8CTMA300_TOUCH: Bootloader FW Ver 0.0
<6>[ 5.865142] CY8CTMA300_TOUCH: Application FW Ver 0.0
<6>[ 5.885192] CY8CTMA300_TOUCH: Silicon Revision E
<6>[ 5.905181] CY8CTMA300_TOUCH: Customer ID 0
<6>[ 5.925170] CY8CTMA300_TOUCH: old FW version, applying reset workarounds
Click to expand...
Click to collapse
Because it can't get the right fw versions, it says old FW version, applying reset workarrounds.
In other kernel this isn't the case.
nickholtus said:
Personally I think the problem is here:
Because it can't get the right fw versions, it says old FW version, applying reset workarrounds.
In other kernel this isn't the case.
Click to expand...
Click to collapse
To add to this - it also applies a different file after realizing the FW version doesn't match up.
In Wedgess 2.6 Kernel is uses 'input3':
Code:
cy8ctma300_touch as /devices/platform/spi_qsd.0/spi_master/spi0/spi0.0/input/input3
Whereas in this Kernel is uses 'input5'
Code:
cy8ctma300_touch as /devices/platform/spi_qsd.0/spi_master/spi0/spi0.0/input/input5
I doubt it's as simple as this, but if this is referencing different files why not try copying/renaming 'input3' to 'input5' and trying again?
Edit: Yeah, it doesn't look like it's as simple as this. xD
Either that or try changing the FW versions? Since for some reason they are currently '0.00', we'd just need to somehow change them to:
Code:
<6>CY8CTMA300_TOUCH: Bootloader FW Ver 0.1
<6>CY8CTMA300_TOUCH: Application FW Ver 0.114
Another thing to note is that 'input3' is identified as 'pm8xxx-keypad'
Code:
<6>[ 5.400421] input: pm8xxx-keypad as /devices/platform/msm_ssbi.0/pm8058-core/pm8xxx-keypad/input/input3
Is this the same in the 2.6 Kernel?
@Bakisha - Would you be able to post the dmesg for the 2.6 Kernel please? I don't have the means to get it myself unfortunately - I was going to see if there were any other discrepancies between the two.
Spizzy01 said:
@Bakisha - Would you be able to post the dmesg for the 2.6 Kernel please? I don't have the means to get it myself unfortunately - I was going to see if there were any other discrepancies between the two.
Click to expand...
Click to collapse
It's little bit old and it don't have timestamp, but untill i can make new one, it will do. Attaching (it is copy-pasted from previous bugreport i posted in other thread)
As for myself, i'll look in differences in source code between Nick's and Wedgess's kernel, to see if there is any differences
Hi all,
I hav some news, but it's not directly related to the kernel.
The play I have is going to Achotjan for some time, he is going to develop for it.
We are going to develop together on this kernel. After a while i will get the play back.
So hopefully progress will go a bit faster now we have a new developer.
Regards,
Nick
I'm trying to rebuild my Linux development/kernel environment and compile the Kernel in preparation for helping nick/nAa if required.
Has anyone ever ran into this before
Code:
CHK include/generated/utsrelease.h
/home/spizzy/android/msm7x30/scripts/gcc-version.sh: line 25: arm-eabigcc: command not found
/home/spizzy/android/msm7x30/scripts/gcc-version.sh: line 26: arm-eabigcc: command not found
HOSTCC scripts/conmakehash
CC scripts/mod/empty.o
Generating include/generated/mach-types.h
arm-eabigcc: No such file or directory
Is your PATH set correctly?
make[2]: *** [scripts/mod/empty.o] Error 2
make[1]: *** [scripts/mod] Error 2
make[1]: *** Waiting for unfinished jobs....
CC kernel/bounds.s
arm-eabigcc: No such file or directory
Is your PATH set correctly?
make[1]: *** [kernel/bounds.s] Error 2
make: *** [prepare0] Error 2
make: *** Waiting for unfinished jobs....
make: *** [scripts] Error 2
I'm using nAa's sources and the paths are set correctly... I can't understand why it's saying it's not. Unless I'm missing something else? oO
I'll look into it more tonight if I can't work it out soon, but if anyone can help or if anyone is able to talk me through it that'd be great.. (Y)
Edit: Nvm. Fixed. xD
Spizzy01 said:
I'm using nAa's sources and the paths are set correctly... I can't understand why it's saying it's not. Unless I'm missing something else? oO
I'll look into it more tonight if I can't work it out soon, but if anyone can help or if anyone is able to talk me through it that'd be great.. (Y)
Click to expand...
Click to collapse
Wich toolchain are you using to build zImage?
Or post link to source that you are trying to compile and i'll look into it too...
Bakisha said:
Wich toolchain are you using to build zImage?
Or post link to source that you are trying to compile and i'll look into it too...
Click to expand...
Click to collapse
I fixed that issue now... Had issues with the filesystem/Linux itself lol.
Now I'm getting this though:
Code:
drivers/gpu/msm/adreno.c: In function 'adreno_iommu_setstate':
drivers/gpu/msm/adreno.c:425: warning: the frame size of 1040 bytes is larger than 1024 bytes; see http://go/big_stack_frame
error, forbidden warning: adreno.c:425
make[3]: *** [drivers/gpu/msm/adreno.o] Error 1
make[2]: *** [drivers/gpu/msm] Error 2
make[1]: *** [drivers/gpu] Error 2
make: *** [drivers] Error 2
make: *** Waiting for unfinished jobs....
Hopefully an easy fix.. Working on it now lol.
Oh Linux... Y U DO DIS! O_O
FYI: I'm using this toolchain:
Code:
github.com/AndroidUnited/Android_Toolchains
Spizzy01 said:
FYI: I'm using this toolchain:
Code:
github.com/AndroidUnited/Android_Toolchains
Click to expand...
Click to collapse
Maybe to try with 4.7?
I'm using the one from
https://github.com/DooMLoRD/android_prebuilt_toolchains/tree/master/arm-linux-androideabi-4.7
Bakisha said:
Maybe to try with 4.7?
I'm using the one from
https://github.com/DooMLoRD/android_prebuilt_toolchains/tree/master/arm-linux-androideabi-4.7
Click to expand...
Click to collapse
I changed the toolchain as you suggested... It's building currently, I'll let you know if it gets further
Thanks for the replies Bakisha. Much appreciated!
Edit: Sadly it died... And funnily enough, on the touchscreen.
By the way, I haven't modified anything in the source yet. At least, not for this installation. I do however hopefully have a fix which I want to try once I get this working correctly.
Code:
drivers/input/touchscreen/cy8ctma300_touch.c: In function 'cy8ctma300_touch_probe':
drivers/input/touchscreen/cy8ctma300_touch.c:1354:35: error: expected ')' before ';' token
drivers/input/touchscreen/cy8ctma300_touch.c:1382:1: error: expected ')' before '}' token
drivers/input/touchscreen/cy8ctma300_touch.c:1382:1: error: expected ')' before '}' token
drivers/input/touchscreen/cy8ctma300_touch.c:1382:1: error: expected expression before '}' token
drivers/input/touchscreen/cy8ctma300_touch.c:1329:3: error: label 'err_gpio_setup' used but not defined
drivers/input/touchscreen/cy8ctma300_touch.c:1382:1: warning: control reaches end of non-void function [-Wreturn-type]
error, forbidden warning: cy8ctma300_touch.c:1382
make[3]: *** [drivers/input/touchscreen/cy8ctma300_touch.o] Error 1
make[2]: *** [drivers/input/touchscreen] Error 2
make[1]: *** [drivers/input] Error 2
make: *** [drivers] Error 2
make: *** Waiting for unfinished jobs....
Could you by any chance upload your 'cy8ctma300_touch.c' file please? I have a feeling the file I have has been modified somehow... Which makes no sense as it was cloned straight from github... oO
I've found an older file myself, I'll try this one too...
Edit: OK... I'm pretty sure this is the problem...? Can someone try to compile the Kernel again, and select only '2' workers (aka -j2). If I put a large amount of workers then it'll most likely compile as it waits for the rest of the tasks to finish... But in actual fact, the kernel isn't compiling correctly because of the error above...? Unless of course I'm the only one getting this error... But as I said, I've not made any changes yet.
I'm gonna go through the file and see if I can work out what the issue is, most likely it's just a missing expression or something. I'll also try sourcing the file from somewhere else, see if it helps..
Spizzy01 said:
By the way, I haven't modified anything in the source yet. At least, not for this installation. I do however hopefully have a fix which I want to try once I get this working correctly.
Code:
drivers/input/touchscreen/cy8ctma300_touch.c: In function 'cy8ctma300_touch_probe':
drivers/input/touchscreen/cy8ctma300_touch.c:1354:35: error: expected ')' before ';' token
drivers/input/touchscreen/cy8ctma300_touch.c:1382:1: error: expected ')' before '}' token
drivers/input/touchscreen/cy8ctma300_touch.c:1382:1: error: expected ')' before '}' token
drivers/input/touchscreen/cy8ctma300_touch.c:1382:1: error: expected expression before '}' token
drivers/input/touchscreen/cy8ctma300_touch.c:1329:3: error: label 'err_gpio_setup' used but not defined
drivers/input/touchscreen/cy8ctma300_touch.c:1382:1: warning: control reaches end of non-void function [-Wreturn-type]
error, forbidden warning: cy8ctma300_touch.c:1382
make[3]: *** [drivers/input/touchscreen/cy8ctma300_touch.o] Error 1
make[2]: *** [drivers/input/touchscreen] Error 2
make[1]: *** [drivers/input] Error 2
make: *** [drivers] Error 2
make: *** Waiting for unfinished jobs....
Click to expand...
Click to collapse
I found a workaround for that.
To me it looks like number of opened "(" doesn't match with closed ")", so I copied code from Lupus kernel:
Change:
Code:
while (((err = reset_device(this);
to
Code:
while (((err = reset_device(this)) < 0) && reset_retries--) {
DEBUG_PRINTK(KERN_DEBUG
"CY8CTMA300_TOUCH: retrying reset_device()\n");
msleep(100);
}
Don't ask why, i don't understand what it does, but for me it fixed problem with compiling (in case few more errors, compare this file with file from lupus jb 2.6 kernel )