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.
Related
This is my own compiled kernel for NEXUS ONE based on the latest source from stock git (http://android.git.kernel.org/)
The branch I use is: android-msm-2.6.35
As I am using my own compiled ROM (PureFroyo) daily, and I am using the stock Froyo camera, I cannot use the IR's kernel (as it is merged with 720p)
Therefore, this triggers my initiative to compile my own kernel. Referenced from intersectRaven's ; Wildmonks ; pershoot ; cyanogen and some other kernels, I have made various adjustments (merge as well). So, here are the features of this ROM:
- intersectRaven's suggested frequency table in acpuclock-qsd8x50.c
- UV to 950mV
- OC to 1152MHz
- All CPU power governors
- 21 MB memory hack (thanks to coolbho3k)
- Target for stock camera, no 720p camera
- No audio boost
- Some minor changes referenced from wildmonks and intersectRaven (thanks!)
- Wifi, Froyo portable hotspot and camera work perfectly
- Not HAVS, but SVS instead
- Battery life is good for my nexus one
- Best match with stock / AOSP ROM
So, here is the link to the kernel, I would be grateful if you could help to test it and feedback whether it works for you (thanks~ ^_^)
Change Log:
2010-12-25 (Merry X'mas )
======================
- Rename to PureGinger
- Tested under AOSP gingerbread for a few days, very stable!
- Changed back to 950mV because 925mV seems not stable in Gingerbread
- Cherry-pick many commits... refer to my github
Link: http://www.mediafire.com/?dawr4f99t4fwc35
Mirror: http://www.4shared.com/file/6pNfdRiQ/PureGinger_26359_AXI_UV_SVS_12.html
File: PureGinger_2.6.35.9_AXI_UV_SVS_122110_223513.zip
MD5: 775007F8C1B549AAF5E18E40B0C704F5
2010-11-26
=========
- Changed to 925mV (UV). Seems running smooth for a few days
- Cherry-pick many commits from various sources (thanks stock, pershoot, raven, redstar, cyanogen, etc...)
- Enhanced ds2784 battery driver
- Other changes could be seen from my github
Link: http://www.mediafire.com/?52aa1h265w1tfau
Mirror: http://www.4shared.com/file/eqA2z7nW/PF_26357_AXI_UV_SVS_112610_014.html
File: PF_2.6.35.7_AXI_UV_SVS_112610_014525.zip
MD5: B17904841A9114BBB453FF4A94676CF2
2010-11-17
=========
- Cherry-pick many commits from various sources
- Kernel scheduler improvement (http://forum.xda-developers.com/showthread.php?t=841599)
Link: http://www.mediafire.com/?lw7mfll6b88qtqx
File: PF_2.6.35.7_AXI_UV_SVS_111710_215623.zip
MD5: 3CD0C4976F5DA7BBFBD42FE95C6A44CE
2010-11-05
=========
- Apply IR's latest oom modifications
- Cherry-pick some latest IR's, pershoot's, cyanogen's & experimental commits
Link: http://www.mediafire.com/?vpb49te3rxpf11z
File: PF_2.6.35.7_AXI_UV_SVS_110510_230204.zip
MD5: F2C2DEE6DF9485B52A5973B243602F6D
2010-11-02
=========
- Merge with a few latest IR's & Wildmonk's commits
- Source push to github
Link: http://www.mediafire.com/?m407xyaub6wuiby
File: PF_2.6.35.7_AXI_UV_SVS_110310_002259.zip
MD5: 3CBF9EFD6A11680FB46253111941CE1E
2010-10-31
=========
- Fix USB mount problem
- Added AXI rate tweak for performance and battery savings (IR's commit: 03ca24721e278eca034f)
Link: http://www.mediafire.com/?xx2sf66sntcrf2r
File: PF_2.6.35.7_AXI_UV_SVS_103110_000825.zip
MD5: 5F4D54E6E3BA63CDA0D35DE4756CC82B
2010-10-27
=========
- First version
Link: http://www.mediafire.com/?t9w73l8qi773qm3
File: PF_2.6.35.7_UV_SVS_signed_102710_012826.zip
MD5: D1EEEA92276BE7965679B1AB173B10B2
---------------------------------------------------------------
Installation procedures are just like what you are flashing with any other kernels (please make backup first):
Instructions:
1.) Reboot to recovery and flash the update zip directly.
OR
Instructions for zImage and bcm4329.ko driver extracted from the update.zip(from command line):
1.) adb remount
2.) adb push bcm4329.ko /system/lib/modules
3.) adb reboot bootloader
4.) fastboot flash zimage zImage
5.) fastboot reboot
---------------------------------------------------------------
Last thing: Please flash the kernel at your own risk Enjoy it.
---------------------------------------------------------------
* I am using my own compiled ROM: PureFroyo
* Source finally push to github: http://github.com/ardatdat/PureFroyo-Kernel
* (OLD) - Link to the 1st version kernel source code:
Part 1
http://www.mediafire.com/?a4q78ux2yy8r8j4
Part 2
http://www.mediafire.com/?yy7t2i9hotq5hg5
---------------------------------------------------------------
You need to post a link to your source code, or make it available for people somehow, according to this.
http://www.xda-developers.com/android/general-public-license-gpl-for-android-kernels/
wdfowty said:
You need to post a link to your source code, or make it available for people somehow, according to this.
http://www.xda-developers.com/android/general-public-license-gpl-for-android-kernels/
Click to expand...
Click to collapse
This is true. Please comply.
EDIT: Thank you. Great work!
wdfowty said:
You need to post a link to your source code, or make it available for people somehow, according to this.
http://www.xda-developers.com/android/general-public-license-gpl-for-android-kernels/
Click to expand...
Click to collapse
overground said:
This is true. Please comply.
Click to expand...
Click to collapse
Just get myself in front of the computer ~
Sure, I am packing the source now and will post the link soon.
Thanks for your prompting
Thank you so much. Since several weeks my wifi at home didn't work very well. I try some kernel with the nightly. Your kernel solved my problem
Source codes finally uploaded to mediafire
THANKSS
Amazing Kernel, just what I was looking for. This overclocks it to 1.152 AWESOME while undervolted and stock!!! The best!
Everyone trying this new kernel, PLEASE REPORT WHICH ROM & VERSION YOU ARE USING?
atlast a custom-kernel for us non 720p, will try when i get home from work iam runnning Geo411´s FRG83 rom.
ardatdat said:
Just get myself in front of the computer ~
Sure, I am packing the source now and will post the link soon.
Thanks for your prompting
Click to expand...
Click to collapse
No problem, wouldn't want your thread to get locked/removed for something like that.
mrdemo007 said:
atlast a custom-kernel for us non 720p, will try when i get home from work iam runnning Geo411´s FRG83 rom.
Click to expand...
Click to collapse
Interested to hear your experience. This kernel seems like a great match for Geo's ROM.
wdfowty said:
No problem, wouldn't want your thread to get locked/removed for something like that.
Click to expand...
Click to collapse
thanks, source already uploaded and link updated in #1 post
Arcarsenal said:
Interested to hear your experience. This kernel seems like a great match for Geo's ROM.
Click to expand...
Click to collapse
Me too, waiting for your report
Arcarsenal said:
Interested to hear your experience. This kernel seems like a great match for Geo's ROM.
Click to expand...
Click to collapse
just flashed it on Geo's ROM it seems everything is fine just need a little more time for testing....
Edit : excellent with Geo's ROM
Rom become more responsive and snappy and battery life is little improved
Been running this kernel with a rooted stock FRG83 ROM for a day now. So far VERY NICE!
One thing...I seem to have a problem with WiFi cutting out for a couple seconds every minute or so when I'm in Airplane mode. I work in a basement and I use airplane mode to keep the radio from killing my battery.
I know this is probably somewhat unique to me, but thought I would let you know.
This is exactly what I'm looking for! Thanks a lot!
Edit: I'm using Geo's Completely Stock Deodexed with busybox, FRG83. I cannot connect to wifi after flashing this kernel, here are my logcat.
D/Tethering( 96): eth0 is not a tetherable iface, ignoring
D/WifiService( 96): ACTION_BATTERY_CHANGED pluggedType: 2
D/WifiService( 96): acquireWifiLockLocked: WifiLock{NetworkLocationProvider ty
pe=2 [email protected]}
V/WifiStateTracker( 96): Connection to supplicant established, state=DISCONNEC
TED
D/NetworkStateTracker( 96): setDetailed state, old =DISCONNECTED and new state
=DISCONNECTED
D/LocationMasfClient( 96): getNetworkLocation(): Location not found in cache,
making network request
I/wpa_supplicant( 686): CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00
:00:00
I/wpa_supplicant( 686): WPS-AP-AVAILABLE
W/wpa_supplicant( 686): Failed to initiate AP scan.
V/WifiStateTracker( 96): Changing supplicant state: DISCONNECTED ==> SCANNING
D/NetworkStateTracker( 96): setDetailed state, old =DISCONNECTED and new state
=SCANNING
V/WifiMonitor( 96): Event [WPS-AP-AVAILABLE ]
D/ConnectivityService( 96): Dropping ConnectivityChange for WIFI: DISCONNECTED
/SCANNING
V/WifiMonitor( 96): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:0
0:00:00:00]
D/dalvikvm( 96): GC_FOR_MALLOC freed 24258 objects / 1295032 bytes in 118ms
D/NativeCrypto( 96): Freeing OpenSSL session
D/LocationMasfClient( 96): getNetworkLocation(): Number of prefetched entries
1
D/LocationMasfClient( 96): getNetworkLocation(): Returning network location wi
th accuracy 1467.0
D/WifiService( 96): releaseWifiLockLocked: WifiLock{NetworkLocationProvider ty
pe=2 [email protected]}
I/wpa_supplicant( 686): WPS-AP-AVAILABLE
V/WifiMonitor( 96): Event [WPS-AP-AVAILABLE ]
W/wpa_supplicant( 686): Failed to initiate AP scan.
I/wpa_supplicant( 686): WPS-AP-AVAILABLE
V/WifiMonitor( 96): Event [WPS-AP-AVAILABLE ]
D/SntpClient( 96): request time failed: java.net.SocketTimeoutException: Conne
ction timed out
W/wpa_supplicant( 686): Failed to initiate AP scan.
I/wpa_supplicant( 686): WPS-AP-AVAILABLE
V/WifiMonitor( 96): Event [WPS-AP-AVAILABLE ]
D/AK8973 ( 75): Compass Start
I/power ( 96): *** set_screen_state 0
D/WifiService( 96): ACTION_SCREEN_OFF
D/WifiService( 96): setting ACTION_DEVICE_IDLE timer for 120,000 ms
D/SurfaceFlinger( 96): About to give-up screen, flinger = 0x125b18
D/AK8973 ( 75): Compass CLOSE
W/wpa_supplicant( 686): Failed to initiate AP scan.
D/StatusBar( 96): DISABLE_EXPAND: yes
D/GoogleLoginService( 204): onBind: Intent { act=android.accounts.AccountAuthen
ticator cmp=com.google.android.gsf/.loginservice.GoogleLoginService }
I/wpa_supplicant( 686): WPS-AP-AVAILABLE
V/WifiMonitor( 96): Event [WPS-AP-AVAILABLE ]
D/dalvikvm( 204): GC_EXPLICIT freed 2276 objects / 120416 bytes in 70ms
D/dalvikvm( 411): GC_EXPLICIT freed 35 objects / 2000 bytes in 60ms
BTW, I hide the SSID of my wifi, and the encryption method is WPA2-PSK with AES. And when I connect my nexus one to laptop, there is no notification to ask me to mount the phone as a usb device or something like that. There should be an android, green or orange, depends on mounted or not, but I notice nothing happens when I connect.
Interesting.. Which radio are you using at the moment?
Using Geo411's latest ROM I get no USB SD mount notification, anyone else having this issue? I am using the latest Korean radio ROM as well.
Arcarsenal said:
Interesting.. Which radio are you using at the moment?
Click to expand...
Click to collapse
32.50.00.32U_5.12.00.08, the latest Korean radio.
niftydl said:
Using Geo411's latest ROM I get no USB SD mount notification, anyone else having this issue? I am using the latest Korean radio ROM as well.
Click to expand...
Click to collapse
Me.
For those of you with USB mount and WiFi issues are you all using the latest Korean radio? Have you tried downgrading the radio and seeing if the issues are resolved?
Is swap enabled or disabled?
I'm working on a device directory to get CM7 building for the Galaxy Player 5.0 USA. I'm using Entropy512's kernel and copying some things out of vzwtab mostly, but there's some parameters in the BoardConfig.mk that I'm not sure how to find out. The Galaxy Player 5.0 seems to be unique among the example galaxy-based devices I could find in having only mmc partitions. So does anyone know what the proper values should be for:
BOARD_KERNEL_BASE
BOARD_NAND_PAGE_SIZE
BOARD_FLASH_BLOCK_SIZE
BOARD_PAGE_SIZE
As far as I can tell the BOARD_KERNEL_BASE is supposed to be the offset into the boot.img where the kernel can be found? But Samsungs don't use the boot.img so does this paremeter make sense? The various samsung devices all define this value though, and with different values, so maybe it means something else..
I found this in the make file in arch/arm of Entrophy512's code.
I think this is what you need for BOARD_KERNEL_BASE ...
HTML:
# The byte offset of the kernel image in RAM from the start of RAM.
TEXT_OFFSET := $(textofs-y)
Above that textofs-y was defined as
HTML:
textofs-y := 0x00008000
textofs-$(CONFIG_ARCH_CLPS711X) := 0x00028000
# We don't want the htc bootloader to corrupt kernel during resume
textofs-$(CONFIG_PM_H1940) := 0x00108000
# SA1111 DMA bug: we don't want the kernel to live in precious DMA-able memory
ifeq ($(CONFIG_ARCH_SA1100),y)
textofs-$(CONFIG_SA1111) := 0x00208000
endif
I think your value should be 0x00008000 ...
Thanks for that! A bit of googling on TEXT_OFFSET led me to PHYS_OFFSET, which is defined in arch/arm/mach-*/include/mach/memory.h, I think that's the value I need, it matches up in a couple of other kernels anyway. At least it matches up for galaxys2, but for mach-s5pv210 products, the PHYS_OFFSET is 0x30000000 but the kernel base is 0x32000000, I'm not sure why they don't match but I think one of those values should be galaxy player kernel base.
A quick grep turns this up...
./mach-s5pc100/include/mach/memory.h:#define PHYS_OFFSET UL(0x20000000)
s5pc100 is the name of the board for the Galaxy Player 5.0 right?
---------- Post added at 06:50 PM ---------- Previous post was at 06:08 PM ----------
HTML:
> As long as the zImage is placed within the 256MB range from the
> start of the memory, ZRELADDR (Address where the decompressed
> kernel will be placed, usually == PHYS_OFFSET + TEXT_OFFSET)
I think I may have it. It seems like we need both values PHYS_OFFSET +TEXT OFFSET.
So if that is what the BOARD_KERNEL_BASE is supposed to be then the value should be 0x20008000.
It would be nice to find a way to get the address off of our currently running devices. I'm going to look for some command or app that will say what it is.
References
http://www.spinics.net/lists/arm-kernel/msg89507.html
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-June/017614.html
Meticulus said:
A quick grep turns this up...
./mach-s5pc100/include/mach/memory.h:#define PHYS_OFFSET UL(0x20000000)
s5pc100 is the name of the board for the Galaxy Player 5.0 right?
Click to expand...
Click to collapse
According to /proc/config.gz from Entropy512's kernel it's the s5pv210.
Come on Meticulous, get back in the game! We need you!
Sent from my cm_tenderloin using Tapatalk
ambrice said:
According to /proc/config.gz from Entropy512's kernel it's the s5pv210.
Click to expand...
Click to collapse
According to the build.prop (ro.build.platform) it's s5pc110. I'm betting the boards are pretty close. I'm just trying to help out. This is all new to me...
Meticulus said:
I think I may have it. It seems like we need both values PHYS_OFFSET +TEXT OFFSET.
So if that is what the BOARD_KERNEL_BASE is supposed to be then the value should be 0x20008000.
It would be nice to find a way to get the address off of our currently running devices. I'm going to look for some command or app that will say what it is.
Click to expand...
Click to collapse
The source for the unpackbootimg is at system/core/mkbootimg/unpackbootimg.c, and it has the line:
printf("BOARD_KERNEL_BASE %08x\n", header.kernel_addr - 0x00008000);
So I think in the boot.img header header.kernel_addr is the ZRELADDR and the BOARD_KERNEL_BASE is supposed to be ZRELADDR - TEXT_OFFSET, which would be the PHYS_OFFSET.
Meticulus said:
According to the build.prop (ro.build.platform) it's s5pc110. I'm betting the boards are pretty close. I'm just trying to help out. This is all new to me...
Click to expand...
Click to collapse
I definitely appreciate the help! It's all new to me too..
They are very close:
http://odroid.foros-phpbb.com/t198-differences-between-s5pc110-and-s5pv210
I downloaded the official samsung released YP-G70 sources, and the defconfig has CONFIG_ARCH_S5PV210=y. So maybe they're close enough as far as the build.prop is concerned? I'm not sure what ro.build.platform is used for..
HTML:
./unpackbootimg -i zImage
BOARD_KERNEL_CMDLINE
BOARD_KERNEL_BASE e19f8000
BOARD_PAGE_SIZE 24061976
Segmentation fault
It looks like that code can not unpack Entrophy512's kernel...
Also regarding the board name, look in "/system/lib/hw/". All the filenames are like "*.s5pc110.so"
I think that "s5pv210" is also the same board as the galaxy s...
I think, but am not sure, but some of those values there are placeholders on Samsung-based devices.
I was a dumbass and accidentally nuked my device tree so I need to rebuild it. I may instead just fork ambrice's to redo it.
Looks like this week/weekend will consist of some fun decobwebbing.
I would appreciate the help. My current state is that it builds an image but an assert fails when flashing the boot.img.
I've done some updates, I have a working kernel and recovery.
When I boot CM7 system_server crashes with this error:
Code:
I/Zygote ( 165): Accepting command socket connections
I/sysproc ( 223): Entered system_init()
I/sysproc ( 223): ServiceManager: 0x76d18
I/SurfaceFlinger( 223): SurfaceFlinger is starting
I/SurfaceFlinger( 223): dithering enabled
I/SurfaceFlinger( 223): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
E/HAL ( 223): load: module=/system/lib/hw/gralloc.s5pc110.so
E/HAL ( 223): Cannot load library: reloc_library[1311]: 165 cannot locate '__android_log_print'...
E/FramebufferNativeWindow( 223): Couldn't get gralloc module
system_server is linked against liblog.so which defines the __android_log_print, I think maybe this error is misleading. /system/lib/hw/gralloc.s5pc110.so is a library I pulled off the stock image as part of the vendor proprietaries.
stack trace in log shows it's crashing in android:isplayHardware::init(unsigned int) in libsurfaceflinger.so
Any ideas of things to try?
I'm just throwing this stuff out there but, assuming that "gralloc.s5pc110.so" is in the location specified, perhaps the "gralloc.s5pc110.so" is trying to locate "liblog.so" and it is "liblog.so" that is in the incorrect location (from stock). If "__android_log_print" is what it can not find and that is defined in "liblog.so" then that leads me to believe that it's not loaded and may be in the wrong location. So, you could compare the location from stock and put a duplicate there and see if that gets you any further. Maybe it's the "PATH" var in init.rc does not include the path for liblog.so...?
As a last resort you could try pulling a "gralloc.aries.so" and renaming it to match since the boards are so similar and see what that gets you?
In a couple days, I may join you on your quest to get a cm7 port. This is your project and you seem to be doing quite well but maybe I can get lucky help out.
Hello all,
I have problem with NFC on CM9 and CM10. On boot I see this in logcat:
Code:
I/NfcService( 2340): Starting NFC service
D/NFC JNI ( 2340): NFC Service : loading JNI
D/NfcService( 2340): checking on firmware download
D/NfcService( 2340): NFC is on. Doing normal stuff
I/NfcService( 2340): Enabling NFC
D/NFC JNI ( 2340): Start Initialization
D/NFC JNI ( 2340): NFC capabilities: HAL = 8150100, FW = b10106, HW = 620003, Model = 12, HCI = 1, Full_FW = 1, Rev = 6, FW Update Info = 249
D/NFC JNI ( 2340): Download new Firmware
W/NFC JNI ( 2340): Firmware update FAILED
D/NFC JNI ( 2340): Download new Firmware
W/NFC JNI ( 2340): Firmware update FAILED
D/NFC JNI ( 2340): Download new Firmware
W/NFC JNI ( 2340): Firmware update FAILED
E/NFC JNI ( 2340): Unable to update firmware, giving up
D/NFC JNI ( 2340): Terminating client thread...
W/NfcService( 2340): Error enabling NFC
Does NFC work for you under CM9/CM10? When I enable NFC in settings, the option remains greyed until reboot.
NFC WORKS ON SAMSUNG ROMs (latest OMEGA 23 JB VERSION)
Thanks!
I tried cm10 for a while and nfc was working fine, my friend has a s3 too with cm10 running and we could share with nfc without a problem.
[SOLVED]
OK, I fixed it by flashing ICS Samsung ROM back (ICS version of OMEGA ROM), enabled NFC and then CM9/CM10.
NFC now works fine
bmansvk1 said:
Hello all,
I have problem with NFC on CM9 and CM10. On boot I see this in logcat:
Code:
I/NfcService( 2340): Starting NFC service
D/NFC JNI ( 2340): NFC Service : loading JNI
D/NfcService( 2340): checking on firmware download
D/NfcService( 2340): NFC is on. Doing normal stuff
I/NfcService( 2340): Enabling NFC
D/NFC JNI ( 2340): Start Initialization
D/NFC JNI ( 2340): NFC capabilities: HAL = 8150100, FW = b10106, HW = 620003, Model = 12, HCI = 1, Full_FW = 1, Rev = 6, FW Update Info = 249
D/NFC JNI ( 2340): Download new Firmware
W/NFC JNI ( 2340): Firmware update FAILED
D/NFC JNI ( 2340): Download new Firmware
W/NFC JNI ( 2340): Firmware update FAILED
D/NFC JNI ( 2340): Download new Firmware
W/NFC JNI ( 2340): Firmware update FAILED
E/NFC JNI ( 2340): Unable to update firmware, giving up
D/NFC JNI ( 2340): Terminating client thread...
W/NfcService( 2340): Error enabling NFC
Does NFC work for you under CM9/CM10? When I enable NFC in settings, the option remains greyed until reboot.
NFC WORKS ON SAMSUNG ROMs (latest OMEGA 23 JB VERSION)
Thanks!
Click to expand...
Click to collapse
bmansvk1 said:
OK, I fixed it by flashing ICS Samsung ROM back (ICS version of OMEGA ROM), enabled NFC and then CM9/CM10.
NFC now works fine
Click to expand...
Click to collapse
This does not make any sense. It's another ROM! Are there more clues?
bobeirasa said:
This does not make any sense. It's another ROM! Are there more clues?
Click to expand...
Click to collapse
there's a easier way, look for NFCFix.zip that's floating around this forum
Trying to get the Call Recording Mod to work for Sprint and other variants as well.
The exact the change I've made in this thread.
The file modded is SecPhone.apk.
This is the Sprint MDL Stock SecPhone.apk
This is the modified one. (Again this doesn't work properly yet...)
The mod itself does what it's intended to do, which is to add the Record button, but the actual recording itself doesn't work properly. The time never increases (On the phone call screen) and the call is never recorded. On top of that it locks up when you try to Stop it or End the call, and it eventually reboots the entire system. (full instant reboot)
Here's the logcat messages that believe are important:
Code:
D/alsa_ucm( 223): Set mixer controls for Capture Call Uplink Downlink enable 1
D/alsa_ucm( 223): Setting mixer control: MultiMedia1 Mixer VOC_REC_UL, value: 1
D/alsa_ucm( 223): Setting mixer control: MultiMedia1 Mixer VOC_REC_DL, value: 1
D/ALSADevice( 223): close: handle 0x43aab7a8 h 0x0
D/ALSADevice( 223): open: handle 0x43aab7a8, format 0x2
D/ALSADevice( 223): Device value returned is hw:0,0
V/ALSADevice( 223): flags 11000000, devName hw:0,0
V/ALSADevice( 223): pcm_open returned fd 59
D/ALSADevice( 223): handle->format: 0x2
D/ALSADevice( 223): setHardwareParams: reqBuffSize 320 channels 1 sampleRate 8000
D/ALSADevice( 223): setHardwareParams: buffer_size 640, period_size 320, period_cnt 2
E/alsa_pcm( 223): cannot prepare channel: errno =-22
D/AudioStreamInALSA( 223): pcm_read() returned n < 0
D/AudioStreamInALSA( 223): standby
D/AudioStreamInALSA( 223): standby
D/AudioStreamInALSA( 223): into standby, stop record
Here is the kmsg output that continuously repeats:
Code:
[ 1601.856506] voice_cvs_stop_record: apr_cvs is NULL.
[ 1601.856658] voice_cvs_stop_record: apr_cvs is NULL.
[ 1601.856719] voice_cvs_stop_record: apr_cvs is NULL.
[ 1601.856872] voice_cvs_stop_record: apr_cvs is NULL.
[ 1601.864715] voice_cvs_stop_record: apr_cvs is NULL.
[ 1601.864868] voice_cvs_stop_record: apr_cvs is NULL.
[ 1601.864929] voice_cvs_stop_record: apr_cvs is NULL.
[ 1601.865020] voice_cvs_stop_record: apr_cvs is NULL.
[ 1601.865386] soc-audio soc-audio.0: can't get BE for INCALL_RECORD_RX
[ 1601.865447] MSM8960 Media1: no BE found for INCALL_RECORD_RX
[ 1601.865600] soc-audio soc-audio.0: can't get BE for INCALL_RECORD_TX
[ 1601.865753] MSM8960 Media1: no BE found for INCALL_RECORD_TX
[ 1601.871398] MSM8960 Media1: dpcm: no backend DAIs enabled for MSM8960 Media1
Anyone know much about the audio API's that can help out here?
errno -22 is EINVAL or Invalid Argument... So something with the recording function in the actual apk seems like it's not setup properly? But yet it works on the International versions without issue... So I'm not sure...
Have you check out the libs and seen if any are missing that the international version has? Maybe a CSC line. Hmm...
clark44 said:
Have you check out the libs and seen if any are missing that the international version has? Maybe a CSC line. Hmm...
Click to expand...
Click to collapse
Ahhh, good point didn't even think about that... I'll compare them when I get time tonight.
Unknownforce said:
Ahhh, good point didn't even think about that... I'll compare them when I get time tonight.
Click to expand...
Click to collapse
Good thread, will try and help as much as possible
On that note, what does the last_kmsg have to say about the reboot? Maybe its kernel related? If im not mistaken, believe there had to be a kernel tweak for the S3...
last_kmsg says same thing as what's listed above, nothing extra... just repeats that over and over.
One thing I can say is that it's not anything in the apk file that makes it work properly, because I was able to flash the international SecPhone.apk and it produced the same results.
So nothing special in there, so it's definitely a library or a kernel thing...
Unknownforce said:
last_kmsg says same thing as what's listed above, nothing extra... just repeats that over and over.
One thing I can say is that it's not anything in the apk file that makes it work properly, because I was able to flash the international SecPhone.apk and it produced the same results.
So nothing special in there, so it's definitely a library or a kernel thing...
Click to expand...
Click to collapse
If it's in the kernel try looking at the variant defconfigs and see if something's included/excluded.
garwynn said:
If it's in the kernel try looking at the variant defconfigs and see if something's included/excluded.
Click to expand...
Click to collapse
I'm leaning towards kernel..
Sent from my SGH-M919 using Tapatalk 2
The ROM I'm using (Mine) is using KT SGS4's latest...
I'm not too familiar with kernel development, but I'll decompile it and take a look... does you guys know what I would need to modify in the kernel?
Unknownforce said:
The ROM I'm using (Mine) is using KT SGS4's latest...
I'm not too familiar with kernel development, but I'll decompile it and take a look... does you guys know what I would need to modify in the kernel?
Click to expand...
Click to collapse
No need to decompile. Kt shoukd have a repo posted. Just look in arch/arm/configs for jf defconfig and the variants. Sprint is spr, for example
Sent from my SPH-L900 using Tapatalk 2
This guy figured out how to do the Call Recorder mod and it works on our Sprint GS4. He has both an odex and deodexed version. I flashed the odex version on stock, odex, rooted MF9 and it works perfectly.
http://forum.xda-developers.com/showthread.php?t=2352797
No issues with the ktoonsez kernel and the Viper4Android mod.
Not sure what I am doing wrong here. Even after I get it booted, with gapps. No baseband. I flashed the dev pre 5 baseband through recovery and it succeeds. When I try to use fastboot to send the same files, it says pre flash validation failed. I'm confused as I have a working build sans baseband, which is kinda important.
shamu_Baseband_D4.01-9625-05.34+FSG-9625-02.111
shamu_Bootloader_moto-apq8084-71.21
Not sure what more information you need about my environment, but I'm happy for any discussion to help me get this resolved so I can share my work.
(MODS: if this is the wrong place, please place it in the right section)
It appears I was missing libxml2
running a new build now. Will remove this post, if that fixes it.
added libxml2-dev and it still recompiled without a baseband. I am not sure what i am doing wrong here. :/
Stramondroid said:
added libxml2-dev and it still recompiled without a baseband. I am not sure what i am doing wrong here. :/
Click to expand...
Click to collapse
I've been trying to figure this out for a week still a no go.
Stramondroid said:
added libxml2-dev and it still recompiled without a baseband. I am not sure what i am doing wrong here. :/
Click to expand...
Click to collapse
The good news is you aren't doing anything wrong!
Wondered why there is no 7.0 OTA or Factory Images for the Nexus 6 yet? Baseband issues!
Unfortunately, this makes AOSP almost useless on the Nexus 6.
did you extract the binary blobs into the source?
https://developers.google.com/android/nexus/blobs-preview
Right now there are two N AOSP ROMS in the N6 forum, one in general and one in development.
I tried both, one has the issue you described with my N6, no signal and no asking for SIM-card PIN. The other had working baseband and it was also shown correctly in About Phone. I think the one not working was the one from the guy konrad, not sure though.
Have you tried both? Maybe get in touch with those guys and find out what they did differently in their builds.
Stramondroid said:
added libxml2-dev and it still recompiled without a baseband. I am not sure what i am doing wrong here. :/
Click to expand...
Click to collapse
was you able to figure this out yet ? Thanks
hedgehogmd said:
was you able to figure this out yet ? Thanks
Click to expand...
Click to collapse
I stopped trying, everyone I talked too said to attempt a compile of the M branch, which was successful, so I know my dev box is good. It has to do with the source. I have no clue.
A solution
I'm the author of the 7.0 ROM in General. On a closer look, it seems that my initial build is actually not a clean 7.0.0_r1 build. I checked out the master branch for a handful of repositories when playing around, and that mistake coincidentally made RIL work.
tl;dr The ICU library is the culprit. Do "cd external/icu && git fetch aosp master && git checkout aosp/master" and rebuild.
Full explanation:
I did a couple of proper builds first, since I got branches messed up in my build:
Proper 7.0.0_r1 build: No baseband
Proper AOSP master build: Working
That gave me a little hope Apparently 7.0.0_r1 has issues preventing RIL from working. Relevant logs:
Code:
01-02 04:51:11.207 D/RILD ( 319): **RIL Daemon Started**
01-02 04:51:11.207 D/RILD ( 319): **RILd param count=1**
01-02 04:51:11.352 E/RILD ( 319): dlopen failed: dlopen failed: cannot locate symbol "UCNV_FROM_U_CALLBACK_STOP_57" referenced by "/system/lib/libxml2.so"...
01-02 04:51:15.371 D/RILD ( 833): **RIL Daemon Started**
01-02 04:51:15.371 D/RILD ( 833): **RILd param count=1**
01-02 04:51:15.420 E/RILD ( 833): dlopen failed: dlopen failed: cannot locate symbol "UCNV_FROM_U_CALLBACK_STOP_57" referenced by "/system/lib/libxml2.so"...
(and so on)
At the first glance it may be related to libxml2, but UCNV_FROM_U_CALLBACK_STOP is actually related to Unicode conversion. It appears in platform/external/icu.
Building 7.0.0_r1 with external/icu at AOSP master solves the issue. Does that work for you? Hope it helps!
---------- Post added at 04:06 PM ---------- Previous post was at 04:05 PM ----------
Zhaofeng Li said:
I did a couple of proper builds first, since I got branches messed up in my build
Click to expand...
Click to collapse
... And yes, I'll update my ROM to a clean build.