I have opened up my phone and found that the chip is labelled NXP+ 44501, which is the same model as the one found on the Crespo. My findings from bug reports suggest that the problems when using the proper drivers (so I assume) is probably a framework issue directly reflecting the way the chip uses the battery.
When enabling NFC on the phone logcat messages spit out:
Code:
10-06 19:48:12.345 W/System.err(2927)java.io.IOException: NFC adapter is disabled
10-06 19:48:12.345 W/System.err(2927)at com.android.nfc_extras.NfcExecutionEnvironment.throwBundle(NfcExecutionEnvironment.java:183)
10-06 19:48:12.345 W/System.err(2927)at com.android.nfc_extras.NfcExecutionEnvironment.open(NfcExecutionEnvironment.java:137)
10-06 19:48:12.345 W/System.err(2927)at l.j(SourceFile:152)
10-06 19:48:12.345 W/System.err(2927)at l.a(SourceFile:202)
10-06 19:48:12.345 W/System.err(2927)at l.i(SourceFile:56)
10-06 19:48:12.345 W/System.err(2927)at l.c(SourceFile:84)
10-06 19:48:12.345 W/System.err(2927)at k.a(SourceFile:144)
10-06 19:48:12.345 W/System.err(2927)at i.a(SourceFile:27)
10-06 19:48:12.345 W/System.err(2927)at c.run(SourceFile:42)
10-06 19:48:12.345 W/System.err(2927)at java.lang.Thread.run(Thread.java:1019)
Code:
10-06 02:52:18.825 D/NFC JNI (2792)NFC Service : loading JNI
10-06 02:52:18.845 I/NfcService(2792)Starting NFC service
10-06 02:52:18.860 I/RegisteredComponentCache(2792)ComponentInfo: ResolveInfo{40521050 com.android.apps.tag.TagViewer p=0 o=0 m=0x108000}, techs: android.nfc.tech.Ndef,
10-06 02:52:18.935 D/NfcService(2792)checking on firmware download
10-06 02:52:18.935 D/NfcService(2792)NFC is off. Checking firmware version
10-06 02:52:18.935 D/NfcService(2792)prev modtime: 1204252426000
10-06 02:52:18.935 D/NfcService(2792)new modtime: 1317003468000
10-06 02:52:18.935 D/NfcService(2792)Perform Download
10-06 02:52:18.985 W/NFC_i2c (2792)sleeping a little longer...
10-06 02:52:19.145 D/NFC JNI (2792)Download new Firmware
10-06 02:52:19.195 W/NFC JNI (2792)Old-style firmware not installed on top of new-style firmware. Using existing firmware in the chip.
10-06 02:52:19.235 W/NFC_i2c (2792)sleeping a little longer...
10-06 02:52:19.325 W/NFC_i2c (2792)sleeping a little longer...
10-06 02:52:19.375 D/NFC JNI (2792)phLibNfc_Mgt_UnConfigureDriver() returned 0x0000[NFCSTATUS_SUCCESS]
10-06 02:52:19.375 D/NfcService(2792)Download Success
10-06 02:52:50.550 D/NFC JNI (2792)Start Initialization
10-06 02:52:50.590 W/NFC_i2c (2792)sleeping a little longer...
10-06 02:52:54.730 D/NFC JNI (2792)Download new Firmware
10-06 02:54:54.730 W/NFC JNI (2792)Firmware update FAILED
10-06 02:54:54.795 D/NFC JNI (2792)Download new Firmware
netchip full build and kernel; waiting for clarification what the Kernel is directly for and will report back:
http://forum.xda-developers.com/showpost.php?p=18149376&postcount=101 - Kernel
http://forum.xda-developers.com/showpost.php?p=18148173&postcount=97 - Full build
Current findings:
Flashing this mod on top of the current CM7 beta brings the necessary APK's and settings in the "Wireless & Networks" menu.
http://forum.xda-developers.com/showthread.php?t=1286315
Possibly the galaxys2att.mk found in TeamHacksungs github may need modification to properly build with NFC enabled
https://github.com/teamhacksung/android_device_samsung_galaxys2att
Here is the proposed modification.
https://github.com/wesbalmer/androi...mmit/ff4d513fa661b44dae167df47b9ba162dabb8ab3
Found that the NP544 device in team hacksungs kernel is enabled under there defconfig:
https://github.com/teamhacksung/sam...5.7/arch/arm/configs/c1_galaxys2att_defconfig
Questions:
What hardware does the ATT SGS2 use for NFC? Is it the NXP NP544?
What type of debuging can we do to determine the raw elements of the communication to this bus?
What else should we ask to further development?
Sorry guys, I'm a total noob... I'm looking to help out though anyway that I can. I've been screwing around with this for a whole 24 hours now trying to figure it out. From what I can see there is an updated Nfc.apk and lib from codeaurora that may not be merged into the current beta build... again not sure...
https://www.codeaurora.org/gitweb/quic/la/?p=platform/packages/apps/Nfc.git;a=summary
https://www.codeaurora.org/gitweb/quic/la/?p=platform/external/libnfc-nxp.git;a=summary
Has anyone got that kernel to flash? I keep getting errors in odin?
alton987 said:
Has anyone got that kernel to flash? I keep getting errors in odin?
Click to expand...
Click to collapse
off topic...
the file is archived in a .tar, extract and rename file to zImage
Stock kernel has NFC - no need to play with kernels for this until there is any evidence that the kernel-level support is broken somehow.
codeworkx's kernel and my Daily Driver also have NFC.
It is, however, partially missing from the framework, so I'm going to poke around at the userland packages posted.
Some preliminary work in my posts in this thread - http://forum.xda-developers.com/showthread.php?t=1289344&page=2
If I add the following files from a Nexus S Cyanogenmod dump, I don't have NFC in settings, but NFC apps can turn it on, and tapping my credit card against the phone results in lots of messages in logcat. I'll try to find an NFC tag with less "private" data in it so I can post some logcats.
Code:
/system/framework/com.android.nfc_extras.jar
/system/etc/permissions/android.hardware.nfc.xml
/system/etc/permissions/com.google.android.nfc_extras.xml
/system/app/NfcGoogle.apk
These files were pulled from the "Full CM7 download at http://forum.xda-developers.com/showthread.php?t=1270118
Edit: Ooops, should've been clear, I was trying to do this on the stock firmware.
Entropy512 said:
Stock kernel has NFC - no need to play with kernels for this until there is any evidence that the kernel-level support is broken somehow.
codeworkx's kernel and my Daily Driver also have NFC.
It is, however, partially missing from the framework, so I'm going to poke around at the userland packages posted.
Some preliminary work in my posts in this thread - http://forum.xda-developers.com/showthread.php?t=1289344&page=2
If I add the following files from a Nexus S Cyanogenmod dump, I don't have NFC in settings, but NFC apps can turn it on, and tapping my credit card against the phone results in lots of messages in logcat. I'll try to find an NFC tag with less "private" data in it so I can post some logcats.
Code:
/system/framework/com.android.nfc_extras.jar
/system/etc/permissions/android.hardware.nfc.xml
/system/etc/permissions/com.google.android.nfc_extras.xml
/system/app/NfcGoogle.apk
These files were pulled from the "Full CM7 download at http://forum.xda-developers.com/showthread.php?t=1270118
Click to expand...
Click to collapse
Cool, didn't notice NfcGoogle.apk in the v4 update.
I've pulled the code aurora libnfc files but have no idea how to merge this into kernel source and going off what you're saying maybe we're not having a kernel related issue. But without hesitance, here is the updated lib. Maybe we can somehow build this into a kernel ( I have no idea how )
http://terminalw.es/libnfc-nxp.tar.gz
not sure if y'all noticed but in Titanium Backup scrolling through the list I found a item that says Nfc Service 2.3.4
will post a screenshot is y'all want
That's probably Nfc.apk, which is in our stock firmware.
Entropy512 said:
Stock kernel has NFC - no need to play with kernels for this until there is any evidence that the kernel-level support is broken somehow.
codeworkx's kernel and my Daily Driver also have NFC.
It is, however, partially missing from the framework, so I'm going to poke around at the userland packages posted.
Some preliminary work in my posts in this thread - http://forum.xda-developers.com/showthread.php?t=1289344&page=2
If I add the following files from a Nexus S Cyanogenmod dump, I don't have NFC in settings, but NFC apps can turn it on, and tapping my credit card against the phone results in lots of messages in logcat. I'll try to find an NFC tag with less "private" data in it so I can post some logcats.
Code:
/system/framework/com.android.nfc_extras.jar
/system/etc/permissions/android.hardware.nfc.xml
/system/etc/permissions/com.google.android.nfc_extras.xml
/system/app/NfcGoogle.apk
These files were pulled from the "Full CM7 download at http://forum.xda-developers.com/showthread.php?t=1270118
Edit: Ooops, should've been clear, I was trying to do this on the stock firmware.
Click to expand...
Click to collapse
About your idea for framework, I have implement it in cyanogenmod.
So it must be working, check my github repo: github.com/galaxys2hackthathing.
There you see a repo called android.
If you repo sync it on a ubuntu computer, you have cyanogenmod source, with nfc added.
Sent from my GT-I9100
netchip said:
About your idea for framework, I have implement it in cyanogenmod.
So it must be working, check my github repo: github.com/galaxys2hackthathing.
There you see a repo called android.
If you repo sync it on a ubuntu computer, you have cyanogenmod source, with nfc added.
Sent from my GT-I9100
Click to expand...
Click to collapse
in your galaxys2att.mk in the repo can you force jni checks?
PRODUCT_PROPERTY_OVERRIDES += \
ro.kernel.android.checkjni=1 \
dalvik.vm.checkjni=true
wesbalmer said:
in your galaxys2att.mk in the repo can you force jni checks?
PRODUCT_PROPERTY_OVERRIDES += \
ro.kernel.android.checkjni=1 \
dalvik.vm.checkjni=true
Click to expand...
Click to collapse
The reason I ask this, is that the logcats I've read through on my device have failures downloading updated firmware by the NFC JNI pid.
Currently parsing through Korean firmware to get this worked out.... who here has confidence that flashing the korean firmware won't brink my phone? I don't mean soft-brick; to where I can install an OS on top, I mean full frontal paperweight.
wesbalmer said:
in your galaxys2att.mk in the repo can you force jni checks?
PRODUCT_PROPERTY_OVERRIDES += \
ro.kernel.android.checkjni=1 \
dalvik.vm.checkjni=true
Click to expand...
Click to collapse
I go do that
Sent from my GT-I9100
wesbalmer said:
Currently parsing through Korean firmware to get this worked out.... who here has confidence that flashing the korean firmware won't brink my phone? I don't mean soft-brick; to where I can install an OS on top, I mean full frontal paperweight.
Click to expand...
Click to collapse
Do it not.
You flash bootloaders and have a paper weight.
Sent from my GT-I9100
If you can find a Korean ROM, if you make sure the zip for it doesn't have bootloaders and you replace the kernel/modem with one of ours, it MIGHT work - it will at least not brick our phone.
Someone actually flashed a full Korean package to an I9100 I think.
Entropy512 said:
If you can find a Korean ROM, if you make sure the zip for it doesn't have bootloaders and you replace the kernel/modem with one of ours, it MIGHT work - it will at least not brick our phone.
Someone actually flashed a full Korean package to an I9100 I think.
Click to expand...
Click to collapse
I know, I IM'd a bunch of M250S users on the latest firmware asking for some help. There is yet to be a dump anywhere online... All I think we need is libnfc_jni.so ; from reviewing source and modifying the com.android.nfc3.xml to be on, I deduced that this file version may be failing to relay the proper firmware to the device for init.
I've posted the following in the main 9100 general forum.
http://forum.xda-developers.com/showthread.php?t=1291690
wesbalmer said:
I know, I IM'd a bunch of M250S users on the latest firmware asking for some help. There is yet to be a dump anywhere online... All I think we need is libnfc_jni.so ; from reviewing source and modifying the com.android.nfc3.xml to be on, I deduced that this file version may be failing to relay the proper firmware to the device for init.
Click to expand...
Click to collapse
libnfc_jni.so is working fine on my device, no errors about firmware here. But I'm working the stock ROM angles here and not CM7.
Entropy512 said:
libnfc_jni.so is working fine on my device, no errors about firmware here. But I'm working the stock ROM angles here and not CM7.
Click to expand...
Click to collapse
Are you seeing anything close to this?
10-06 02:52:18.825 D/NFC JNI (2792)NFC Service : loading JNI
10-06 02:52:18.845 I/NfcService(2792)Starting NFC service
10-06 02:52:18.860 I/RegisteredComponentCache(2792)ComponentInfo: ResolveInfo{40521050 com.android.apps.tag.TagViewer p=0 o=0 m=0x108000}, techs: android.nfc.tech.Ndef,
10-06 02:52:18.935 D/NfcService(2792)checking on firmware download
10-06 02:52:18.935 D/NfcService(2792)NFC is off. Checking firmware version
10-06 02:52:18.935 D/NfcService(2792)prev modtime: 1204252426000
10-06 02:52:18.935 D/NfcService(2792)new modtime: 1317003468000
10-06 02:52:18.935 D/NfcService(2792)Perform Download
10-06 02:52:18.985 W/NFC_i2c (2792)sleeping a little longer...
10-06 02:52:19.145 D/NFC JNI (2792)Download new Firmware
10-06 02:52:19.195 W/NFC JNI (2792)Old-style firmware not installed on top of new-style firmware. Using existing firmware in the chip.
10-06 02:52:19.235 W/NFC_i2c (2792)sleeping a little longer...
10-06 02:52:19.325 W/NFC_i2c (2792)sleeping a little longer...
10-06 02:52:19.375 D/NFC JNI (2792)phLibNfc_Mgt_UnConfigureDriver() returned 0x0000[NFCSTATUS_SUCCESS]
10-06 02:52:19.375 D/NfcService(2792)Download Success
10-06 02:52:50.550 D/NFC JNI (2792)Start Initialization
10-06 02:52:50.590 W/NFC_i2c (2792)sleeping a little longer...
10-06 02:52:54.730 D/NFC JNI (2792)Download new Firmware
10-06 02:54:54.730 W/NFC JNI (2792)Firmware update FAILED
10-06 02:54:54.795 D/NFC JNI (2792)Download new Firmware
Just opened mine up and found that it has the nxp 44501.
i am trying build a custom rom everything is working execpt camera ...can anyone help
here is logcat
E/AKMD2 (10488): akmd2 : Device can't be opened.
E/AKMD2 (10493): akmd2 : Device can't be opened.
E/QualcommCameraHardware( 290): ***read_camera_id: open CAM_ID_FILE failed!No such file or directory
E/QualcommCameraHardware( 290): Unable to determine the target type. Camera will not work
E/QualcommCameraHardware( 290): createInstance: startCamera failed!
E/CameraHolder(10495): fail to connect Camera
E/CameraHolder(10495): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder(10495): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder(10495): at android.hardware.Camera.<init>(Camera.java:110)
E/CameraHolder(10495): at android.hardware.Camera.open(Camera.java:90)
E/CameraHolder(10495): at com.android.camera.CameraHolder.open(CameraHolder. java:100)
E/CameraHolder(10495): at com.android.camera.Camera.ensureCameraDevice(Camer a.java:2019)
E/CameraHolder(10495): at com.android.camera.Camera.access$6900(Camera.java: 105)
E/CameraHolder(10495): at com.android.camera.Camera$4.run(Camera.java:1133)
E/CameraHolder(10495): at java.lang.Thread.run(Thread.java:1096)
W/Process ( 339): Unable to open /proc/10466/status
E/AKMD2 (10505): akmd2 : Device can't be opened.
W/InputMethodManager(10507): Ignoring onBind: cur seq=217, given seq=216
E/AKMD2 (10517): akmd2 : Device can't be opened.
E/AKMD2 (10523): akmd2 : Device can't be opened.
P500 device doesnt have a akmd2 sensor, you need to replace the sensor files
and camera libs.
Thanks andy i will try that now.....
Hi,
Internation Pardus v15 image on rooted i9300, works very well except for this really odd USB connection error when connecting it to my Sony BT3900u car stereo, it was previously connecting without issue on the v15 Pardus build but for unknown reasons to myself now always presents an error.
Does anyone have any ideas as to what might be causing this issue? Any help would be greatly appreciated.
After getting this issue the first time, I ran through a full rebuild, wiped phone/cache/dalvick and error still persisted post rebuild.
Model:
GT-i9300
Android Version:
4.2.2
Baseband
I9300XXEMA5
Kernel version:
3.0.31-702147
Build Number:
Pardus HD Rom XV XXUDME7
Logcat:
E/MTPRx ( 8982): Read Error Came false
E/ ( 8982): read error [0] [Success]
E/MTPRx ( 8982): state from USB_STATE eventDISCONNECTED
E/MTPRx ( 8982): /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt: open failed: ENOENT (No such file or directory)
E/MTPRx ( 8982): stop observing and calling usbRemoved
E/MTPRx ( 8982): In usbRemoved Status bar enabled
E/MTPRx ( 8982): Sending Broadcast
E/MtpService( 8982): onDestroy.
E/MtpService( 8982): Unregister Mtp disable Receiver
E/MtpService( 8982): Receiver not registered: [email protected]
E/MtpService( 8982): unregistering mtpMediaReceiver in UnregisterAllIntent
E/MtpService( 8982): Receiver not registered: [email protected]
E/MTPJNIInterface( 8982): noti = 3
E/ ( 8982): ****** [mtp_usb_mtp_finalize] mtp_close_fd Calling
E/ ( 8982): [mtp_close_fd] fd = 50...
E/ ( 8982): [mtp_close_fd] USB endpoint [50] closed...
E/ ( 8982): ****** [mtp_usb_mtp_finalize] Updating the gInitializeFlag Flag to FALSE
E/ ( 8982): ****** [mtp_usb_mtp_finalize] Calling mtp_stop_io
E/SEC PowerHAL( 2447): sysfs_write : Error opening /sys/class/input/input1/enabled: No such file or directory
E/SEC PowerHAL( 2447): sysfs_write : Error opening /sys/class/input/input8/enabled: No such file or directory
E/videowall-TranscodeReceiver(10572): broadcastMSG : android.intent.action.ACTION_POWER_DISCONNECTED
E/MTPRx (10600): In MtpReceiverandroid.hardware.usb.action.USB_STATE
E/MTPRx (10600): check value of boot_completed is1
E/MTPRx (10600): check booting is completed_sys.boot_completed
E/MTPRx (10600): Sd-Card path/storage/extSdCard
E/MTPRx (10600): Status for mount/Unmount :mounted
E/MTPRx (10600): SDcard is available
E/MTPRx (10600): The value of first_boot is 1
E/MTPRx (10600): [ 662] The value of first_boot is 1NORMAL SEQUENCE
E/MTPRx (10600): Received USB_STATE with sdCardLaunch = 0
E/MTPRx (10600): configured is false
I'm guessing this is the correct part of the log that pretains to the MTP/USB part. If not I have attached a full log.
Try typing this in a terminal window or adb shell on your phone:
Code:
touch /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt
Or, make a txt file called gadgetDisconnectAndConnect and place it in /data/data/com.samsung.android.MtpApplication folder.
xpmode said:
Try typing this in a terminal window or adb shell on your phone:
Code:
touch /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt
Or, make a txt file called gadgetDisconnectAndConnect and place it in /data/data/com.samsung.android.MtpApplication folder.
Click to expand...
Click to collapse
Hi, thanks for the reply.
I did that as quoted, nothing seems to have changed, What should I be looking for?
Thanks!
Hi,
I developed a native process that uses ScreenshotClient to capture the device screen ( rooted devices only )
I have a loop where ScreenshotClient does update() every cycle. everything works well until 4.3.
when I run it on 4.3 the first call to update succeeds, but in the second call the call result is -2 , and I get these erros in logcat:
E/BufferQueue( 8166): [ScreenshotClient] connect: already connected (cur=1,req=1)
E/libEGL ( 2463): EGLNativeWindowType 0x4116d5f8 already connected to another API
E/libEGL ( 2463): eglCreateWindowSurface:376 error 300b (EGL_BAD_NATIVE_WINDOW)
E/SurfaceFlinger( 2463): captureScreenImplLocked: eglCreateWindowSurface() failed 0x300b
Any idea what changed in 4.3 that causes this, or what these errors mean.
Can someone put this on the thread for the CM11 nightly build for Galaxy S4 i9505, unofficial I believe. I don't have the post count required. ROM is very good and works fine apart from the following issue, at least so far.
HDR won't save pictures from stock 4.4 camera app. It shows as a blank square on the gallery. Turning off HDR works fine. Logcat (first time so let me know if it's wrong and I'll do another):
--------- beginning of /dev/log/main
I/dalvikvm(16916): Enabling JNI app bug workarounds for target SDK version 11...
E/Term (16916): onCreate
D/Term (16916): TermService started
I/TermService(16916): Activity called onBind()
I/Term (16916): Bound to TermService
I/TermService(16916): Activity binding to service
D/dalvikvm(16916): Trying to load lib /data/app-lib/jackpal.androidterm-1/libjackpal-androidterm4.so 0x418e9ae8
D/dalvikvm(16916): Added shared lib /data/app-lib/jackpal.androidterm-1/libjackpal-androidterm4.so 0x418e9ae8
I/libjackpal-androidterm(16916): JNI_OnLoad
I/Term (16916): waiting for: 16941
I/Term (16916): Subprocess exited: 129
W/IInputConnectionWrapper(16916): showStatusIcon on inactive InputConnection
E/Term (16916): onCreate
D/Term (16916): TermService started
I/TermService(16916): Activity called onBind()
I/Term (16916): Bound to TermService
I/TermService(16916): Activity binding to service
I/Term (16916): waiting for: 17246
I/Term (16916): waiting for: 17402